Hey,
Most probably I am late but can we still add tasks or volunteer for
mentoring?
Apologies for being late,
Aarti
On Mon, Oct 28, 2013 at 9:22 PM, Quim Gil <q...@wikimedia.org> wrote:
> We have applied to Google Code-in and we will know whether we have been
> accepted or not this Friday. Thank you to all the contributors that have
> helped so far listing tasks and volunteering as mentors!
>
> We can keep improving
> https://www.mediawiki.org/**wiki/Google_Code-In<https://www.mediawiki.org/wiki/Google_Code-In>
>
>
> On 10/26/2013 02:07 AM, Jiabao Wu wrote:
>
>> I am very keen to help the Code-ins.
>>
>
> Very good!
>
>
> I have posted a quite general task on
>> https://www.mediawiki.org/**wiki/Google_Code-In#Code<https://www.mediawiki.org/wiki/Google_Code-In#Code>.
>> Shall I split the
>> task to smaller ones (similar to the size as annoying_little_bugs) and
>> define them before 28 October?
>>
>
> Yes, splitting into digestible, self-contained bites is necessary. You can
> still list those tasks in the Code-in page. It is a good exercise to
> complete that feature anyway.
>
>
> I was GSoC 2013 participant and work on [bug 43058] VisualEditor Math.
>> I think this is a perfect chance for GSoCers. It will help us to
>> review our work as well as furthering the development.
>>
>
> I fully agree. I pinged most of the GSoC projects in the past days, and I
> will do it again if we get accepted in this program.
>
> Also, being a GCI mentor right after being a GSoC student must be very
> exciting. To me it shows a degree of success that the GSoC project delivery
> alone can't measure.
>
> Thank you Jiabao and Liangent for setting this precedent. I hope you will
> inspire other former GSoC students to follow.
>
>
> On Thu, Oct 24, 2013 at 8:39 PM, Guillaume Paumier
>>
>>> This was the perfect opportunity to create the long-overdue task list
>>>
>>> around tech communications:
>>> https://www.mediawiki.org/**wiki/Technical_communications/**
>>> What_you_can_do<https://www.mediawiki.org/wiki/Technical_communications/What_you_can_do>
>>>
>>
> Exactly, Google Code-in can be a very good excuse to publish those
> backlogs of little tasks that most of us have in mind, or even documented,
> but never find the time to crunch ourselves, or find someone to work on
> them.
>
> I have also took several tasks that were sitting untouched in my backlog,
> and they are now under Outreach/Research.
>
>
> --
> Quim Gil
> Technical Contributor Coordinator @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/**User:Qgil<http://www.mediawiki.org/wiki/User:Qgil>
>
> ______________________________**_________________
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
>
--
Aarti K. Dwivedi
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
