Scheduling for PyWeek 22
While you all are potentially still here lurking, let's nail down a date for the next PyWeek so that there aren't any surprises or oh-$#%@ moments when you realize you only have 6 days to document and release your python library. Here are the results of the survey regarding scheduling.
Apologies for spamming a bunch of new threads, but I wanted to create a separate discussion here outside of the other survey results.
3 PyWeeks in 2016?
|LET'S DO THIS!||xxxxx (5)|
|Cautiously optimistic||xxxxx (5)|
|No, no, no, that's too much||xxxxxxx (7)|
I kind of have mixed feelings here. On one hand the solid no's win, and on the other hand there are a majority of people that are open to the idea. But also a majority of users that aren't completely sold on the idea. Since burnout is a major concern, I kind of want to err on the side of the no's (despite being in the LET'S DO THIS camp myself) since PyWeeks with low participation aren't very good for maintaining participation going forward and we're already kind of light on participation compared to several years ago.
When should the next PyWeek be if there are 3?
Again, this is sort of all over the board, however...
When should the next PyWeek be if there are 2?
There's a pretty solid consensus here. 10 votes for September and 6 votes for neighboring months
I feel like the other activity suggestions in the survey may appeal the LET'S DO THIS audience (PyWeekend or the post-PyWeek-polish sprint) sometime during the summer without burning out other participants. There was a pretty strong correlation between LET'S DO THIS and people interested in PyWeekend.
That said, my proposal is just having 2 PyWeeks this year, with the next one being September 4th-11th, additionally having PyWeekend in the summer for all the energetic folks, and possibly a polish sprint sometime soon (April?) before everyone forgets how their codebases work.
Thoughts? Concerns? Ideas?
(log in to comment)