@Qgil Why would we make year specific GSOC tags/projects? seems like a rolling tag used from year to year makes more sense?

Good question, I haven't made my mind yet. And in any case the point is very diluted right now that we will have in Phabricator only the first round of these programs, and therefore FOSS-OPW == OPW-9. But maybe in the next round we want to identify the tasks that were developed during a specific round? This would allow to provide some metrics specific for each round, compare data...

In the case of OPW now, there is also a special situation where we might need a team restricted to interns and candidates of this round, see T834: Conpherence for FOSS OPW round 9 participants.

In T561#18587, @Aklapper wrote:

Would probably be a good idea if we define it as "GoogleCode-in tasks that are already listed on Wikimedia's Google Code-in planning page or in Google Melange" to avoid random usage as "potential candidates that have no mentor defined" (that would be pretty much covered by good first task already IMO).

ok

Google-Code-in-2014 ?

With hashtag GCi-2014, works for me.

But first, any comments to Jared's very valid question about avoiding projects for specific editions?

In T1148#20398, @Jaredzimmerman-WMF wrote:

@Qgil Why would we make year specific GSOC tags/projects? seems like a rolling tag used from year to year makes more sense?

Considering Google-Code-in-2014 a "sprint", a year/number later we could go back to see what was being worked on in the last edition. I myself am not entirely convinced we need umbrella projects without years/numbers in their names at all as we can always archive the project for that year when the project is over.

Having a year/number in the project name might reduce potential confusion when taking a look at open tasks in the project "OPW" - is this task proposed for this edition of the program? Or was it created for the last edition of the program and not finished or forgotten to resolve?

Also cf. discussion in T1049.

So #Outreach-Program-for-Women-Round9 and Outreach-Program-For-Women-9 as additional hashtag, to start with?

I have started with the creation of Outreach-Program-For-Women-9 in order to unblock T834 and have a project available for Wednesday, when the new interns will be announced. It is a sprint project that can only be joined by invitation, because the test of Conpherence is restricted to these members.

I think it would make sense to have also a team project for OPW in general, but we can leave that for later since now team and sprint is basically the same.

I don't think we need to keep this task open for GCi. @Aklapper can just create a sprint project Google-Code-in-2014 if and when Wikimedia is accepted.

Pywikibot has one person already doing a microtask for Google Summer of Code 2015. Are we going to be part of it; is there a project for it, etc?

We will know whether Wikimedia has been accepted to GSoC 2015 by February 20. For updates and questions, please go to T921: Apply to GSoC 2015 and FOSS OPW round 10