[Sugar-devel] GSOC Plans

[Samuel Cantero]

On Wed, May 24, 2017 at 1:12 PM, Jatin Dhankhar <dhankhar.jatin at gmail.com>
wrote:

> Hey,
>
> So I cloned the SamToday's repo on digitalocean and ran only the web
> version and so far it works nicely. It can be accessed here
> http://139.59.78.102:5000. I really like that it's written in Flask,
> makes it easier to navigate between files, since there are few files and
> directories to look at.
>
Hi Jatin! Good job!

I also like Flask. It's very simple and can be extended easily. So let's
stick with it. We can add some changes to current web page. It's quite easy
to follow code IMO.


> I really don't understand the need of using Kafka.
>

Regarding Kafka, I'll take a look tomorrow so I can see what Sam was trying
to do. I haven't had time to take a look at Sam's code yet (due to work).


> It looks it uses a small subset of bundles for demo, which can be viewed
> at http://139.59.78.102:5000/update.json. But it doesn't use any database
> yet, not even Redis for  in-memory storage all the data is cached in memory
> of the running process.
>

Idea is to avoid database :) we want to use GitHub as our main database.
Redis is a key/value storage. What do you want to exactly use redis for?

I still don't fully understand the update.json file but I can see the
activity and download.sl.o are related here, but we still need to
understand how the URL is defined/generated. Please take a look. Format
looks simple though.

What do we know so far about the relationship with ASLO, GitHub and
download.sugarlabs.org?


> Also base64 encodes the images.
>
> Uses fully qualified package name of the activity to uniquely identify
> activity, which it becomes part of the url.
>

+1


> Some UI  changes are needed (like showing activity icon on the detail url)
>

We can improve UI as much as you like later. But I think now we should
focus in functionality/workflow.

> [image: Inline image 1]
>
> I also liked the idea of using Docker to containerize the ASLO, making it
> easier to run and deploy the app.
>

I'll probably run ASLO with a WSGI server like Unicorn inside a container
and then reverse proxy it with nginx.


>
> Thanks,
> Jatin Dhankhar
>
> On Tue, May 23, 2017 at 10:33 PM, Jatin Dhankhar <dhankhar.jatin at gmail.com
> > wrote:
>
>> Hi,
>>
>> Yes, I also noticed it's on the SugarLabs Wiki (
>> https://wiki.sugarlabs.org/go/Summer_of_Code)  but not on the GSOC site.
>>
>> I looked at http://aslo.jatindhankhar.in/aslo/. Not much change there.
>>>
>>  Yes, I didn't make much progress in the direction. It will change soon,
>> now that my exams are over, I can dedicate a big day of my time for
>> development.
>>
>> Your images are missing. What I usually do is use the browser to display
>>> the image information. This shows the url where it thinks they are. Usually
>>> they are in in the static root and accessible by a relative path from
>>> there. The activities are shown in a vertical column. A simple css rule
>>> should fix that:
>>>
>>> display:inline-block
>>
>> Thanks, for the tips. I tried something similar by analyzing resources
>> requested in chrome network analyzer, issue indeed is related to
>> STATIC_ROOT_FOLDER. Will try out the css rule, will inline it with html for
>> the time being.
>>
>> I am still optimistic that the discussion on ASLO will converge. If so,
>>> there will be a lot of house-cleaning to do to enable ASLO to get its
>>> information from the bundles and enable us to dispense with the Developer
>>> Hub functionality.
>>
>> I am hoping for the same.
>>
>> When you are ready, you can create a repository on github and move the
>> prototype to Sunjammer. In the meantime, you can point folks to the url
>> above.
>>
>>> Once you have a github repository, we should be able to use its wiki
>>> capability to document the design. A lot can also be done with comments.
>>
>>  Sure thing :)
>>
>> Remember that L10N has two separate aspects. Localization of the ASLO
>>> site and the localization for the activity itself. As I understand the
>>> dialog, the text for the summary and description are in the POT file for
>>> some activities. This means that localization for specific activity screens
>>> can be done using this text from the bundle. With careful design, we may be
>>> able to use the same ASLO POT file for all activity screens getting the
>>> activity specific strings from the bundle. Luckily with Django Pootle and
>>> gettext are available. All you need to do is fetch the strings and send
>>> them to the template based on the locale of the user.
>>
>> Yes, will look into as well.
>>
>>  You'll probably need a widget on the main screen to allow the user to
>>> select a language.
>>
>> Something similar to what Django doc does ?
>>
>> Thanks,
>> Jatin Dhankhar
>>
>> On Tue, May 23, 2017 at 2:04 PM, Tony Anderson <tony_anderson at usa.net>
>> wrote:
>>
>>>
>>> Hi, Jatin
>>>
>>> Walter has designate Sam Cantaro as a co-mentor. Super news. He isn't
>>> yet listed as a mentor on the GSOC site, but I expect that will take place.
>>>
>>> I looked at http://aslo.jatindhankhar.in/aslo/. Not much change there.
>>>
>>> Your images are missing. What I usually do is use the browser to display
>>> the image information. This shows the url where it thinks they are. Usually
>>> they are in in the static root and accessible by a relative path from
>>> there. The activities are shown in a vertical column. A simple css rule
>>> should fix that:
>>>
>>> display:inline-block
>>>
>>> which applies to the tile class. Then the tiles are displayed by a <ul>
>>> with <li><div class='tile'>some text</li> Another option is <figure> which
>>> formats a tile with an image (icon) and a caption (name of activity). One
>>> design detail, the entire tile should be clickable to invoke the activity
>>> screen.
>>>
>>> I am still optimistic that the discussion on ASLO will converge. If so,
>>> there will be a lot of house-cleaning to do to enable ASLO to get its
>>> information from the bundles and enable us to dispense with the Developer
>>> Hub functionality.
>>>
>>> When you are ready, you can create a repository on github and move the
>>> prototype to Sunjammer. In the meantime, you can point folks to the url
>>> above.
>>> Once you have a github repository, we should be able to use its wiki
>>> capability to document the design. A lot can also be done with comments.
>>>
>>> Remember that L10N has two separate aspects. Localization of the ASLO
>>> site and the localization for the activity itself. As I understand the
>>> dialog, the text for the summary and description are in the POT file for
>>> some activities. This means that localization for specific activity screens
>>> can be done using this text from the bundle. With careful design, we may be
>>> able to use the same ASLO POT file for all activity screens getting the
>>> activity specific strings from the bundle. Luckily with Django Pootle and
>>> gettext are available. All you need to do is fetch the strings and send
>>> them to the template based on the locale of the user.
>>>
>>> You'll probably need a widget on the main screen to allow the user to
>>> select a language.
>>>
>>> Tony
>>>
>>> On 05/21/2017 01:48 PM, Jatin Dhankhar wrote:
>>>
>>> Yes, I asked Samuel and he said okay but I told him not to hurry since I
>>> have my DigitalOcean credits which will expire soon.
>>> I will add those who want to access the vm, just message me your Ssh
>>> public keys.
>>> If something else needs to be done, let me know.
>>>
>>> On Sun, May 21, 2017 at 6:49 AM, Tony Anderson <tony_anderson at usa.net>
>>> wrote:
>>>
>>>> As I understand it, flask and django are very similar. Flask is
>>>> supposed to be easier to set up. However, you have a django setup. I looked
>>>> at the code base, it looks like some of it can be incorporated.
>>>>
>>>> Are you making progress on getting a shell account?
>>>>
>>>>
>>>> Tony
>>>>
>>>>
>>>> On 05/21/2017 01:18 AM, Jatin Dhankhar wrote:
>>>>
>>>> Hi,
>>>> As discussed with Walter and Samuel on IRC. We decided to try out Sam
>>>> Today's version of aslo and re-use what is good for us and discuss the code
>>>> further. I will be studying the code this weekend and will report my
>>>> findings between Monday-Wednesday ( I have exam on Tuesday).
>>>>
>>>> Thanks,
>>>> Jatin Dhankhar
>>>>
>>>> On Wed, May 17, 2017 at 6:59 AM, Tony Anderson <
>>>> <tony_anderson at usa.net>tony_anderson at usa.net> wrote:
>>>>
>>>>> Hi Jatin
>>>>>
>>>>> I also missed the meeting - I forgot about it in trying to set up
>>>>> travel for the return to Kigali. I read the meeting minutes and there was
>>>>> not much happening. My sense is that many of the GSOC participants are in
>>>>> the midst of exams.
>>>>>
>>>>> I am happy with the way things are going and your communication is
>>>>> excellent.
>>>>>
>>>>> I had a similar problem with internet here in the Philippines - we
>>>>> finally switched vendors to resolve it.
>>>>>
>>>>> Tony
>>>>>
>>>>>
>>>>>
>>>>> On 05/15/2017 11:16 PM, Jatin Dhankhar wrote:
>>>>>
>>>>> I am really sorry for not making it to the weekly IRC meeting. It
>>>>> won't happen again. I was having issues with my ISP as I completed my
>>>>> monthly quota and my internet was capped to a minimum speed and there were
>>>>> issues with dialing up. I am really sorry, If there is anything I can do to
>>>>> make up for my absence, let me know.
>>>>>
>>>>> Thanks,
>>>>> Jatin Dhankhar
>>>>>
>>>>> On Fri, May 12, 2017 at 11:23 PM, Jatin Dhankhar <
>>>>> <dhankhar.jatin at gmail.com>dhankhar.jatin at gmail.com> wrote:
>>>>>
>>>>>> Hi Tony,
>>>>>>
>>>>>> Have you discussed a way to host ASLO with the Sugar team ?
>>>>>>
>>>>>> On Thu, May 11, 2017 at 8:13 PM, Jatin Dhankhar <
>>>>>> <dhankhar.jatin at gmail.com>dhankhar.jatin at gmail.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I wrote my weekly Journal of GSOC  <https://jatindhankhar.in/>
>>>>>>> https://jatindhankhar.in/blog/gsoc-sugar-labs-week-1/.
>>>>>>> Let me know if something needs to be changed.
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 11, 2017 at 12:31 PM, Jatin Dhankhar <
>>>>>>> <dhankhar.jatin at gmail.com>dhankhar.jatin at gmail.com> wrote:
>>>>>>>
>>>>>>>> How about 13 UTC, similar to the Monday Meetings ?
>>>>>>>>
>>>>>>>> On Thu, May 11, 2017 at 12:17 PM, Tony Anderson <
>>>>>>>> <tony_anderson at usa.net>tony_anderson at usa.net> wrote:
>>>>>>>>
>>>>>>>>> Hi, Walter
>>>>>>>>>
>>>>>>>>> That's 1am local here in the Philippines (UTC+8). I am usually
>>>>>>>>> asleep well before that.
>>>>>>>>>
>>>>>>>>> Tony
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 05/11/2017 10:53 AM, Walter Bender wrote:
>>>>>>>>>
>>>>>>>>> Tony: Does 17UTC work for you?
>>>>>>>>>
>>>>>>>>> On Wed, May 10, 2017 at 6:30 AM, Jatin Dhankhar <
>>>>>>>>> <dhankhar.jatin at gmail.com>dhankhar.jatin at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> I am very excited to work on a big project like ASLO and want it
>>>>>>>>>> to be a success :)
>>>>>>>>>> I am thinking about planning each week and trying to stick to the
>>>>>>>>>> weekly plan. I propose Friday every week at 17:00 UTC for weekly meetings.
>>>>>>>>>> We can use waffle or trello to pin tasks and tick them as necessary.
>>>>>>>>>> Suggest your views regarding the same. Can it be made more systematic and
>>>>>>>>>> approachable ?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Jatin Dhankhar
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Walter Bender
>>>>>>>>> Sugar Labs
>>>>>>>>> <http://www.sugarlabs.org>http://www.sugarlabs.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Sugar-devel mailing listSugar-devel at lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20170524/0d820462/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 94488 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20170524/0d820462/attachment-0001.png>