[Sugar-devel] Development Team Meeting, 4th September 10PM UTC

[Rahul Bothra]

As an addition, we could conduct a "Adopt an Activity" campaign, probably
during GCI but not restricted to participants, since we are lacking in
activity maintainers

On Tue, Sep 4, 2018, 8:22 AM Rahul Bothra <f2016015 at pilani.bits-pilani.ac.in>
wrote:

> Thanks. I won't be able to join in for the meeting.
>
> > - what we have been working on,
>
> Testing and Reviewing pull requests
>
> > - ideas for GCI tasks, should Sugar Labs be accepted.
>
> I am in favor of Sugar Labs being accepted.
> Tasks for GCI could be:
>  - [Medium to Difficult] Continuing work on the Python 3 Project; Porting
> activities and/or telepathy porting etc
>  - [Easy to Medium] Porting activities to GTK+ 3;
>  - [Easy] Fix existing trivial bugs in activities (already open on GitHub
> or bugs.sugarlabs.org)
>  - [Easy to Medium] Improving sugar-docs in term of being beginner friendly
>  - [Easy to Medium] Implementing Features for activities (suggested via
> community feedback)
>
> Thanks
> Rahul Bothra
> (pro-panda)
>
> On Tue, Sep 4, 2018 at 6:21 AM, James Cameron <quozl at laptop.org> wrote:
>
>> Developers are invited to attend the next team meeting, on;
>>
>> - Tuesday 4th September at 6pm US/Eastern,
>> - Tuesday 4th September at 10pm UTC,
>> - Wednesday 5th September at 3:30am IST,
>> - Wednesday 5th September at 8am Australia/Sydney,
>>
>> Agenda to include
>>
>> - what we have been working on,
>>
>> - ideas for GCI tasks, should Sugar Labs be accepted.
>>
>> #sugar-meeting irc.freenode.net (no meeting 'bot expected; the spam
>> continues unabated in unprotected channels),
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20180904/c35b3a17/attachment-0001.html>