Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Should we import our old policy posts?

+6
−0

Over on codegolf.stackexchange.com, we have numerous meta posts outlining loopholes answers can't break, validity of output/input methods and other rule-type posts.

Some examples:

Here's a list of most faq/policy posts

My question is whether or not we leave these posts on SE or bring them over here for ease of access. More specifically (mainly for veterans of SE), do we keep what we have or start anew?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

2 answers

You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.

+3
−0

For a small number of posts, it will be easier to create them here than to import them. Your moderators (yes we need to get some) can create new help topics, which you can link to from question posting guidance, close reasons, or anywhere else you like. By making them help topics you can organize them for presentation, without having to use the Q&A format.

If they are copies (or largely copies) then we'll need to include attribution per the CC license, but that's ok -- "based on (link)" at the bottom of the topic would satisfy that.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+1
−0

I haven't been involved enough in SE Code Golf to really count for much. But I do think we need to have policies stated somewhere. One advantage we have here is that once policies get reasonably finalized in Meta, we have the opportunity to move a true FAQ section. That section is truly waiting for content - it currently refers to $sitename!

While the licensing used by SE should allow us to copy/paste everything, there are some real concerns both legally and practically. One possibility is to import the specific questions ( @ArtOfCode can help with that.) and use them as a starting point.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »