Jean-Marc Lasgouttes wrote:
Le 13/01/2015 01:42, Cyrille Artho a écrit :
The downside is that we have yet another tag, and that many developers
may not recognize GCI (but perhaps know about GSoC). For the latter,
tasks that take 2 - 3 hours for a relatively inexperienced young
developer are ideal.
We could use code-in as flag (codein looks weird to me :).
I am not sure that we have so may tasks that take 2-3 hours to a newbie.
I do not really understand what GCI is about.
We are going to spend almost as much time coming up with tasks than people
will need to accomplish them.
JMarc
GCI is about letting high school students participate in open source
projects, using "bite-sized" tasks. A student is expected to complete
several such tasks over a certain time (I don't remember what the usual
number of tasks per student is, maybe about ten?).
You are right that many tasks are needed to participate as an organization.
100 tasks are the recommended minimum. We have also seen that it's not
feasible to come up with many tasks within a few weeks before the deadline.
What other organizations do is to gather such tasks over the year. If we do
this while filing/reviewing bugs and issues, we can do this on the side
without requiring much extra time. If we have more than about 70 tasks by
fall, then I think we can come up with enough additional tasks to fill the
gap. If not, we can still try next year when we have more tasks.
--
Regards,
Cyrille Artho - http://artho.com/
The chief danger in life is that you may take too many precautions.
-- Alfred Adler
