[TWN team] Suggestion for new TWN section: easy development tasks to get involved

[Karsten Loesing]

On 17/05/14 18:58, harmony wrote:
> Karsten Loesing:
>> Lunar:
>>> harmony:
>>>> How many bugs should feature in each issue - just the one?
>>>
>>> I believe somewhere between 0 and 3 depending on the length of the
>>> newsletter and the amount of call for helps that are already in there.
>>>
>>> The latter because I feel that a newsletter that say “help on this,
>>> help on that, please, contribute to this, look at that” kind be
>>> demotivating. Yes, we have so many things to do, please let's not remind
>>> us too hard… :)
>>
>> Agreed.  0 to 3 seems like a fine interval to start with.
> 
> Personally, it was the repeated badgering at the end of TWN that got me
> involved...

Heh.

> I think the current items do a good job of targeting a particular group
> of people, e.g. 'if you're a Twisted fan/Python queen/R sorcerer, look
> at this tutorial then this bit of code', and giving them a way in. That
> probably makes the key difference between encouragement and
> despair-inducing blanket calls-for-review.

Sounds good.  Feel free to tweak the text towards making it even more
likely that people get involved.

> But the proof of the pudding will be in the plugging of the bugs. One or
> two per week is good to start with; if no one seems to respond we can
> increase or decrease the number as appropriate.

One or two sounds like a fine start.

How about the following process for deciding how many tasks to include
in the next issue:

We try to make sure that there are always two or three tasks under
"Queued up for next issue"
(https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/BugsToPlug#Queuedupfornextissue).

Whoever is the TWN editor decides how many tasks they want to include
and copies over that text.  This could happen right before the freeze
deadline, or whenever the editor does it.  I'm happy to clean up the
BugsToPlug page afterwards.

If this works for you, I wouldn't mess with the week's main TWN page.
So, I wouldn't add tasks that you'd have to remove later on, because
there's not enough space.  However, the editor would be responsible for
including the new section and shouldn't forget to do that *if* there's
enough space.  Does that work for you?

All the best,
Karsten