okay, i've been mostly reviewing patches, thanks to all those pull requests. i did a quick investigation in a replacement for the record activity, which is a huge gtk2 to gtk3 port yet to be done, but nothing definite yet.

octamois: i expect sugar, datastore, and core activities to run as python 3. i expect some activities not yet ported to python 3 will continue to run as python 2 using the sugar toolkit. that means sugar toolkit has to be both 2 and 3.

yashagrawal3: you could, but you will need a working port of the toolkit first before you can test them. also, it would be unwise of us to have master branch contain code that won't run on current sugar, so a branch "python3" should be used for the moment.

octamois: with respect to "who will be mentoring", if your question is about gsoc, just don't ask me. if it's about porting, don't ask me because i've not done it. if it's about project management or sugar release or github behaviours, i'm someone to ask.

Pro-Panda: the main aim of this port is to be able to continue having Sugar desktop available on Linux distributions; who are soon to deprecate python2 because python project is planning to withdraw security support.

Pro-Panda: however, if you want to port an activity to python3 before the toolkit is released, and you want somewhere to hold the port so that other people don't repeat the work, then push it to a branch named python3 in the activity repository.

octamois: yes, it's been done before, that's what sugar-build and stuff was all about, but it was not maintained and failed, with departure of volunteer daniel narvaez. i hope he didn't die suddenly, but we never found out what happened!

octamois: continuous integration is very useful in some projects; i'm interested to know what it will do for us in sugar labs for the sugar desktop. there's a bit of debate in the wider world about benefits and what changes it brings.

octamois: thanks; i see some very different repository types; there's the sugar shell, toolkit, and there's activities. what we lack is activity maintainers, and i'd have to be sure that CI doesn't make their job any harder.