What recurring sections will we do in this post, or should we introduce those in a later post to keep this one from getting too long or messy?

It looks like there are 5 proposed: under-appreciated / low-visibility high-quality answers, rarely used but interesting esolangs, TNB Highlights / TNB History, history of code golf as a whole, and user spotlight

I think doing maybe 1/2 per post would be good

The answers one would be good to have in the first

Looks good

edoteric -> esoteric, first two !s -> .

but yeah it looks good

Why ! to .?

I don't like ! ! It makes things worse! I don't know why!

It makes things sound less dull.

I prefer more dull :)

When is the first one due?

And has anyone actually started?

I don't think we have a due date since we haven't posted #1, but once we do, we have a schedule to stick to

maybe it would be a good idea to draft up a schedule/routine for each time and then schedule #1 to be posted in 2 weeks from whenever we decide to start

and that way we can write the first one on the same strict timeline we'll be sticking to for the rest of them

what's our schedule anyway? biweekly?

I'mn't the right person to ask because idk the schedule

who's even organizing this anyway, lol (like do we have one person as the organizer of this thing)

we don't necessarily need just one person, we can have like a couple of people be the main organizers to determine the schedule and topics and whatever

@cairdcoinheringaahing who's organising this?

i think we should probably have an organization for roles for this thing first, and then from there we can determine a schedule, deadlines, and then think about starting the first one

Dibs not being an organiser

I think I'm mainly organising this? :P

given that you've written both discussion posts i think that would make sense :P

I'd be happy to draw up a general "schedule for writing a post" that covers 2 weeks to get ready for each new one

I said a couple of days ago that it'd be nice to get the first post ready for the weekend, but that's not looking likely

i'd be willing to count as an "official" (by whatever metric) organizer for this though i'd be fine to just author stuff every now and then

don't think this requires any mod overseeing or anything like that, unlike the election :P

I've updated the readme page to include a general schedule for one post per 2 weeks. Let me know what y'all think

I think this looks pretty good; we can always tweak it as we go but I think it's good for a general structure

what day of the week should we post on each time?

I'm thinking Mondays or Fridays

Mondays gets the users who browse during work, and Fridays catches the weekend crowd

I think that makes sense. Agreeing on a time might not work so well with timezones but we'll see

I can't be an author, and I probably don't have enough rep/experience to be an official/organizer/whatever, but I can help out with reviewing first drafts

(Btw @Lyxal I closed your issue because I kept getting notifications every time you commented on it)

@user Why can't you be an author?

That's the point

The point is that you get notified

Which is why it's open again

@RedwolfPrograms I don't know anything about making golfing languages, writing explanations, etc.

@Lyxal :=(

@user you know how to document golfing languages

I know how to turn text into markdown, but not how to actually document them

My projects are so poorly documented that I get lost in them after being away for a week :P

I think Wednesdays might actually be best for the posting date, because that puts everything that involves collaboration (editing and choosing topics) on weekdays when people are likely to be active

You just say what each command does

¯\_(ツ)_/¯

@RedwolfPrograms I also don't have school on Wednesday, so that works out great for me :P