Re: [Sugar-devel] Where shall I start contributing?

[Tony Anderson]

So let's discourage his help. I would be happy to work with him on 
coming up with a reasonable protocol.


Tony

On Saturday, 12 May, 2018 11:52 AM, James Cameron wrote:

On Sat, May 12, 2018 at 07:23:21AM +0530, Jaskirat Singh wrote:

Hello !

One of the GSOC aspirant is working on the "Beginner guide for new comers"
along with the mentors. So i think this will soon help us in providing an
appropriate path to the new contributors.

Thanks.  You are talking about Pratul Kumar,
https://medium.com/@pratulkumar/gsoc-introduction-to-the-community-ed47e04e3051

Pratul should become an activity maintainer before being trusted to guide
beginner developers to that same goal.

Back on 14th February, when Pratul first mentioned their interest in
the project, I mentioned several risks and gave links to our existing
beginner guides written by Rahul, pipix51, Walter, and I.  These
guides continue to be updated.

Perhaps the mentors might help?  I don't think so.  Mentors that
Pratul met with are Jaskirat Singh, Divyanshu Rawat, Abdulazeez
Abdulazeez and Shivang Shekhar.  None of these are an activity
maintainer.

Perhaps the other mentors might help?  I don't think so.  Wiki page
also mentions Hrishi Patel, Rishabh Thaney and Samson Goddy.  None of
these are an activity maintainer, though Hrishi has had a go at making
changes to Sugar Toolkit documentation.

What will Pratul do about the problem of our collective failure to
maintain Sugar activities?  There's a challenge.  ;-)



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Where shall I start contributing?

[James Cameron]

On Sat, May 12, 2018 at 07:23:21AM +0530, Jaskirat Singh wrote:
> Hello !
> 
> One of the GSOC aspirant is working on the "Beginner guide for new comers"
> along with the mentors. So i think this will soon help us in providing an
> appropriate path to the new contributors.

Thanks.  You are talking about Pratul Kumar,
https://medium.com/@pratulkumar/gsoc-introduction-to-the-community-ed47e04e3051

Pratul should become an activity maintainer before being trusted to guide
beginner developers to that same goal.

Back on 14th February, when Pratul first mentioned their interest in
the project, I mentioned several risks and gave links to our existing
beginner guides written by Rahul, pipix51, Walter, and I.  These
guides continue to be updated.

Perhaps the mentors might help?  I don't think so.  Mentors that
Pratul met with are Jaskirat Singh, Divyanshu Rawat, Abdulazeez
Abdulazeez and Shivang Shekhar.  None of these are an activity
maintainer.

Perhaps the other mentors might help?  I don't think so.  Wiki page
also mentions Hrishi Patel, Rishabh Thaney and Samson Goddy.  None of
these are an activity maintainer, though Hrishi has had a go at making
changes to Sugar Toolkit documentation.

What will Pratul do about the problem of our collective failure to
maintain Sugar activities?  There's a challenge.  ;-)

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Where shall I start contributing?

[Tony Anderson]

I am not 'surprised' by this - I am shocked! There are only 10 
activities installed on the Ubuntu Sugar. The rest must be obtained from 
ASLO. Ubuntu 18.04 does not support GTK. The net effect is that few of 
the activities on ASLO will work in Sugar on Ubuntu.


We have wasted precious technical resources to perform the port and then 
failing to deliver the results to our users. Fixing this would seem to 
be within the scope of the 'Say no to GTK' project.


The purpose of the spreadsheet is to make our status visible. We need to 
operate in the real world. I believe we should clearly distinguish 
between ASLO (the activities in activities.sugarlabs.org/activities/ and 
ASLO the addon interface. Our problem with ASLO is primarily the poor 
state of the activities/ and not the interface (which has its own 
problems, of course). The spreadsheet is based on activities/. During my 
professional life, it was considered mandatory to collect the facts and 
make a plan before implementation. I think you will be pleasantly 
surprised when a contributor has a specific task that is clearly needed 
and clearly defined.


Even if I had time to maintain activities, I would probably still not 
consider that a good use of my time. The update procedure is 
inappropriate to the task. Contributing an update to an activity does 
not require the procedures appropriate for Sugar itself. A problem with 
an activity only affects that activity so the maximum risk for error is 
limited. In the original ASLO procedure, the registered contributor 
updates the version with each change. Each submitted change was reviewed 
- normally by Walter Bender - before being added to ASLO. I shudder to 
think the time that would be required to update the version number for 
Hello World from 6 to 7.


Tony


On Saturday, 12 May, 2018 09:15 AM, James Cameron wrote:

Yes, and that's in my linked guide to contributing.

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities

Don't be surprised at the "not the same" situation.  Changes (commits)
to activities are made on GitHub without updating the version number
and making a release.  This is so that changes can be combined and
tested before a release, instead of making a release after every
change.  But at the moment, without activity maintainers, the changes
don't get tested, changes don't get released, bundles don't get made,
and upload isn't happening.  These steps are missing;

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer

Incidentally, I'm certain ASLOv3 won't help with that; because it
won't do anything to combine and test changes; the human intelligence
step in making a release.  Barking up the wrong tree.

Thanks for the spreadsheet views, but I fear they will do nothing
except to make our human problem so much larger by making it more
visible.  ;-)

Could you be an activity maintainer instead?  I'm maintaining Record
at the moment, and have nearly finished porting to GTK+ 3 and
GStreamer 1.14.  I've been at it on and off since 2016, and it has
consumed most of my week.

On Sat, May 12, 2018 at 08:30:58AM +0800, Tony Anderson wrote:

I believe our immediate need is maintenance on ASLO
(Acitivities.SugarLabs.org). It is going to take another day or two to
complete reviewing the bundles from http://github.com/SugarLabs; however, it
is evident that a large number have the name version number as the version
on ASLO but are not the same. Sadly, this means that many of the conversions
to GTK3 are not available to users with Sugar on Ubuntu.

When finished I will post an updated spreadsheet showing the problem
bundles.

Tony

On Saturday, 12 May, 2018 08:19 AM, James Cameron wrote:

Someone asked me privately how they might contribute.  My answer may
be useful to others.

Someone said;

where should I start?

Thanks for your question.

1.  don't ask this question privately if you don't need to; Sugar Labs
is an open community project, and this kind of question is best asked
in public on sugar-devel@ mailing list, so that you get the most
complex of responses, from which you can average or integrate.

2.  my recent post "How to get started as a Sugar Labs developer" may
be helpful; rather than quote it here, I'll link to it;

http://lists.sugarlabs.org/archive/sugar-devel/2018-April/055284.html

3.  our documentation for new contributors suggests many things, so be
sure to read these documents;

https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md

4.  you might follow along behind the GSoC teams, and read their
meeting minutes, use http://meeting.sugarlabs.org/ to watch for new
meetings, to learn how others work,

5.  you will know from my GitHub activity that my contribution is
coding.  If you do coding, you will talk to me quite a bit.  If you do
something other than coding, I might not answer much.  Someone else

Re: [Sugar-devel] Where shall I start contributing?

[Jaskirat Singh]

Hello !

One of the GSOC aspirant is working on the "Beginner guide for new comers"
along with the mentors. So i think this will soon help us in providing an
appropriate path to the new contributors.

Thanks
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Where shall I start contributing?

[James Cameron]

Yes, and that's in my linked guide to contributing.

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities

Don't be surprised at the "not the same" situation.  Changes (commits)
to activities are made on GitHub without updating the version number
and making a release.  This is so that changes can be combined and
tested before a release, instead of making a release after every
change.  But at the moment, without activity maintainers, the changes
don't get tested, changes don't get released, bundles don't get made,
and upload isn't happening.  These steps are missing;

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer

Incidentally, I'm certain ASLOv3 won't help with that; because it
won't do anything to combine and test changes; the human intelligence
step in making a release.  Barking up the wrong tree.

Thanks for the spreadsheet views, but I fear they will do nothing
except to make our human problem so much larger by making it more
visible.  ;-)

Could you be an activity maintainer instead?  I'm maintaining Record
at the moment, and have nearly finished porting to GTK+ 3 and
GStreamer 1.14.  I've been at it on and off since 2016, and it has
consumed most of my week.

On Sat, May 12, 2018 at 08:30:58AM +0800, Tony Anderson wrote:
> I believe our immediate need is maintenance on ASLO
> (Acitivities.SugarLabs.org). It is going to take another day or two to
> complete reviewing the bundles from http://github.com/SugarLabs; however, it
> is evident that a large number have the name version number as the version
> on ASLO but are not the same. Sadly, this means that many of the conversions
> to GTK3 are not available to users with Sugar on Ubuntu.
> 
> When finished I will post an updated spreadsheet showing the problem
> bundles.
> 
> Tony
> 
> On Saturday, 12 May, 2018 08:19 AM, James Cameron wrote:
> >Someone asked me privately how they might contribute.  My answer may
> >be useful to others.
> >
> >Someone said;
> >>where should I start?
> >Thanks for your question.
> >
> >1.  don't ask this question privately if you don't need to; Sugar Labs
> >is an open community project, and this kind of question is best asked
> >in public on sugar-devel@ mailing list, so that you get the most
> >complex of responses, from which you can average or integrate.
> >
> >2.  my recent post "How to get started as a Sugar Labs developer" may
> >be helpful; rather than quote it here, I'll link to it;
> >
> >http://lists.sugarlabs.org/archive/sugar-devel/2018-April/055284.html
> >
> >3.  our documentation for new contributors suggests many things, so be
> >sure to read these documents;
> >
> >https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
> >https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md
> >
> >4.  you might follow along behind the GSoC teams, and read their
> >meeting minutes, use http://meeting.sugarlabs.org/ to watch for new
> >meetings, to learn how others work,
> >
> >5.  you will know from my GitHub activity that my contribution is
> >coding.  If you do coding, you will talk to me quite a bit.  If you do
> >something other than coding, I might not answer much.  Someone else
> >would help you instead.
> >
> >--
> >
> >Disclosure statement; I'm a contributor to Sugar Labs and am paid by
> >One Laptop per Child.  It is in my interest if you work on Sugar
> >activities that OLPC uses.
> >
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Where shall I start contributing?

[Tony Anderson]

I believe our immediate need is maintenance on ASLO 
(Acitivities.SugarLabs.org). It is going to take another day or two to 
complete reviewing the bundles from http://github.com/SugarLabs; 
however, it is evident that a large number have the name version number 
as the version on ASLO but are not the same. Sadly, this means that many 
of the conversions to GTK3 are not available to users with Sugar on Ubuntu.


When finished I will post an updated spreadsheet showing the problem 
bundles.


Tony

On Saturday, 12 May, 2018 08:19 AM, James Cameron wrote:

Someone asked me privately how they might contribute.  My answer may
be useful to others.

Someone said;

where should I start?

Thanks for your question.

1.  don't ask this question privately if you don't need to; Sugar Labs
is an open community project, and this kind of question is best asked
in public on sugar-devel@ mailing list, so that you get the most
complex of responses, from which you can average or integrate.

2.  my recent post "How to get started as a Sugar Labs developer" may
be helpful; rather than quote it here, I'll link to it;

http://lists.sugarlabs.org/archive/sugar-devel/2018-April/055284.html

3.  our documentation for new contributors suggests many things, so be
sure to read these documents;

https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md

4.  you might follow along behind the GSoC teams, and read their
meeting minutes, use http://meeting.sugarlabs.org/ to watch for new
meetings, to learn how others work,

5.  you will know from my GitHub activity that my contribution is
coding.  If you do coding, you will talk to me quite a bit.  If you do
something other than coding, I might not answer much.  Someone else
would help you instead.

--

Disclosure statement; I'm a contributor to Sugar Labs and am paid by
One Laptop per Child.  It is in my interest if you work on Sugar
activities that OLPC uses.



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Where shall I start contributing?

[James Cameron]

Someone asked me privately how they might contribute.  My answer may
be useful to others.

Someone said;
> where should I start?

Thanks for your question.

1.  don't ask this question privately if you don't need to; Sugar Labs
is an open community project, and this kind of question is best asked
in public on sugar-devel@ mailing list, so that you get the most
complex of responses, from which you can average or integrate.

2.  my recent post "How to get started as a Sugar Labs developer" may
be helpful; rather than quote it here, I'll link to it;

http://lists.sugarlabs.org/archive/sugar-devel/2018-April/055284.html

3.  our documentation for new contributors suggests many things, so be
sure to read these documents;

https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md

4.  you might follow along behind the GSoC teams, and read their
meeting minutes, use http://meeting.sugarlabs.org/ to watch for new
meetings, to learn how others work,

5.  you will know from my GitHub activity that my contribution is
coding.  If you do coding, you will talk to me quite a bit.  If you do
something other than coding, I might not answer much.  Someone else
would help you instead.

--

Disclosure statement; I'm a contributor to Sugar Labs and am paid by
One Laptop per Child.  It is in my interest if you work on Sugar
activities that OLPC uses.

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOBS] [Sur] [IAEP] [SLOB] Action required: Devin Ulibarri travel/stipend

[Adam Holt]

+1

On Fri, May 11, 2018, 7:44 PM Claudia Urrea  wrote:

> + 1
>
> On Thu, May 10, 2018 at 6:18 PM, rosamel norma ramirez mendez <
> rosano...@hotmail.com> wrote:
>
>> +1
>>
>> Descarga Outlook para iOS 
>> --
>> *From:* olpc-Sur  on behalf of Walter
>> Bender 
>> *Sent:* Thursday, May 10, 2018 2:01:59 PM
>> *To:* Lionel Laské
>> *Cc:* Sugar-dev Devel; OLPC para usuarios, docentes, voluntarios y
>> administradores; SLOBs; Samson Goddy; iaep
>> *Subject:* Re: [Sur] [SLOBS] [Sugar-devel] [IAEP] [SLOB] Action
>> required: Devin Ulibarri travel/stipend
>>
>>
>>
>> On Thu, May 10, 2018 at 12:32 PM Lionel Laské 
>> wrote:
>>
>>>
>>> +1
>>>
>>> BTW I'm agree with Caryl, the idea is to use this "honorarium" to defray
>>> his costs. Not considering it as a payment/salary/reward.
>>> I'm not at all a big fan of the use of word "honorarium", it's not the
>>> philosophy of SugarLabs to giving money to someone to represent SugarLabs.
>>> It's even dangerous: in few months a guy could ask us to pay him because
>>> he represented SugarLabs during a conference.
>>>
>>
>> I don't know what the proper term should be, but this "honorarium" was
>> not solicited by Devin, but rather, it was offered by the school. It is
>> quite customary for this sort of thing in some cultures. Devin asked that
>> the money be routed through the SFC so that at least some of it would go
>> towards the support of SFC/SL.
>>
>> regards.
>>
>> -walter
>>
>>>
>>> Lionel.
>>>
>>>
>>>
>>> 2018-05-10 3:55 GMT+02:00 Carlos mauro :
>>>
 +1

 El mié., 9 may. 2018 1:41 p. m., Walter Bender 
 escribió:

> +1
>
> On Wed, May 9, 2018 at 2:11 PM Ignacio Rodríguez 
> wrote:
>
>> +1
>> ___
>> SLOBs mailing list
>> sl...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/slobs
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>

 ___
 SLOBs mailing list
 sl...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/slobs


>>>
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>>
>> ___
>> SLOBs mailing list
>> sl...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/slobs
>>
>>
> ___
> SLOBs mailing list
> sl...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/slobs
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOBS] [Sur] [IAEP] [SLOB] Action required: Devin Ulibarri travel/stipend

[Claudia Urrea]

+ 1

On Thu, May 10, 2018 at 6:18 PM, rosamel norma ramirez mendez <
rosano...@hotmail.com> wrote:

> +1
>
> Descarga Outlook para iOS 
> --
> *From:* olpc-Sur  on behalf of Walter
> Bender 
> *Sent:* Thursday, May 10, 2018 2:01:59 PM
> *To:* Lionel Laské
> *Cc:* Sugar-dev Devel; OLPC para usuarios, docentes, voluntarios y
> administradores; SLOBs; Samson Goddy; iaep
> *Subject:* Re: [Sur] [SLOBS] [Sugar-devel] [IAEP] [SLOB] Action required:
> Devin Ulibarri travel/stipend
>
>
>
> On Thu, May 10, 2018 at 12:32 PM Lionel Laské 
> wrote:
>
>>
>> +1
>>
>> BTW I'm agree with Caryl, the idea is to use this "honorarium" to defray
>> his costs. Not considering it as a payment/salary/reward.
>> I'm not at all a big fan of the use of word "honorarium", it's not the
>> philosophy of SugarLabs to giving money to someone to represent SugarLabs.
>> It's even dangerous: in few months a guy could ask us to pay him because
>> he represented SugarLabs during a conference.
>>
>
> I don't know what the proper term should be, but this "honorarium" was not
> solicited by Devin, but rather, it was offered by the school. It is quite
> customary for this sort of thing in some cultures. Devin asked that the
> money be routed through the SFC so that at least some of it would go
> towards the support of SFC/SL.
>
> regards.
>
> -walter
>
>>
>> Lionel.
>>
>>
>>
>> 2018-05-10 3:55 GMT+02:00 Carlos mauro :
>>
>>> +1
>>>
>>> El mié., 9 may. 2018 1:41 p. m., Walter Bender 
>>> escribió:
>>>
 +1

 On Wed, May 9, 2018 at 2:11 PM Ignacio Rodríguez 
 wrote:

> +1
> ___
> SLOBs mailing list
> sl...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/slobs
>


 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

>>>
>>> ___
>>> SLOBs mailing list
>>> sl...@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/slobs
>>>
>>>
>>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
>
> ___
> SLOBs mailing list
> sl...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/slobs
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC Project: Migration of Activities wiki-pages to GitHub

[Glide]

Hey Vipul,

Let me know when you get the code. I would love to go through it.

Thanks


On Sat, May 12, 2018 at 1:30 AM, Vipul Gupta 
wrote:

> Great, as discussed in the meeting on Friday it would be very helpful if I
> get an idea of your migration process.
> Hence if you could upload your script on GitHub or send it here. It would
> be much appreciated. Thanks.
>
> Happy Contributing !!
>
> On Fri, May 11, 2018 at 8:07 PM Rudra Sadhu  wrote:
>
>> Hello!
>>
>> We are done with our second weekly meeting discussing the project. (this
>> was a very short meeting)
>> Please find the logs at http://meeting.sugarlabs.
>> org/sugar-meeting/meetings/2018-05-11T14:09:25
>>
>> And we will be doing the next meeting on next Friday at the same time 1600
>> CET.
>>
>> thanks,
>> Rudra Sadhu
>>
>> On Tue, May 8, 2018 at 2:43 PM, Rudra Sadhu  wrote:
>>
>>> I realise I've not explained the project as well as I could/should have.
>>> This blog post[1] is an attempt to better define the same.
>>>
>>> We can discuss more about this in the sugar-devel meeting today, if
>>> required.
>>>
>>> Regards,
>>> Rudra Sadhu
>>>
>>> [1] : https://rdrsadhu.github.io/blog/gsoc2018/2018-05-08-
>>> project-details/
>>>
>>>
>>> On Mon, May 7, 2018 at 4:10 AM, James Cameron  wrote:
>>>
 Yes, we do seem to be talking to ourselves.

 The goal remains, though the mentors in that meeting didn't mention
 it; give them some slack, they haven't been especially heavy
 contributors to Sugar Labs.  Of the three mentors present, Divyanshu,
 Onuwa, and Ibiam, only Ibiam has been a recently active contributor,
 and not to the Wiki, Help activity or https://help.sugarlabs.org/

 Re: Hello World.  It is a coding example, has no use otherwise, so it
 should not be in activities.sugarlabs.org; I've disabled it.  Version
 will be incremented when a release is made.  Repository has no release
 tags.  We need an activity maintainer for it.  A checklist for
 maintaining an activity is here;

 https://github.com/sugarlabs/sugar-docs/blob/master/src/
 contributing.md#checklist---maintainer

 Across the activity set, we have very few activity maintainers.  This
 will change as the GSoC coding period begins; particularly as Yash and
 Rahul begin working.

 Back on topic; Rudra's project has a purpose; it is a subset of
 activity maintenance, but the coding is automation that will be used
 _once_.  Possibly a brain-numbing exercise, akin to road construction
 during the Irish potato famine.

 I've been a reviewer for the pull requests so far; four of them just
 now.  Mentors, Walter, Tony, and others could help by reviewing
 Rudra's pull requests as they are made rather than leaving it to me.
 ;-)

 @Rudra, my recommendation is to set an order of work; start with the
 demonstration set of activities (Fructose), because we keep these
 maintained well, then work on the activities that Tony has listed as
 working with Ubuntu 18.04 or Thomas has listed as working with Fedora
 28.

 @Rudra, also think through the whole ecosystem from coding to user,
 and propose changes to your project in response to your reading of
 the current mailing list thread.  We're not expecting you to be a
 compliant robot, but an imaginative student.  Situation reminds me of
 something I saw in the student guide;

 https://google.github.io/gsocguides/student/finding-
 the-right-project.html

 "Don’t be that person: Cut and pasting an idea from the organization
 page and turning that in as your project’s description is a big no-no.
 You’ll be expected to research and submit your own ideas about how to
 accomplish the project your way, not just state the end result."

 On Sun, May 06, 2018 at 10:44:06AM +0800, Tony Anderson wrote:
 > Hi, Walter
 >
 > Sadly, I saw no comment in the meeting that suggests the project
 includes this
 > goal. As you know, a common outcome to GSOC projects is that they are
 not
 > completed in the available time. Perhaps the project could be more
 explicit as
 > an update to the help activity than as a migration of wiki pages to
 github.
 >
 > Tony
 >
 > On Sunday, 06 May, 2018 09:55 AM, Walter Bender wrote:
 >
 > On Sat, May 5, 2018 at 9:04 PM Tony Anderson <[1]
 t...@olenepal.org> wrote:
 >
 > SugarLabs is our site to communicate with our users and
 prospective
 > users. GitHub is our site to support SugarLabs development.
 In this
 > meeting it is pointed out that maintaining two versions of the
 > wikipages will be difficult (obvious, since we are unable to
 maintain
 > even one). The evil word 'deprecation' was used (I would have

Re: [Sugar-devel] GSoC Project: Migration of Activities wiki-pages to GitHub

[Vipul Gupta]

Great, as discussed in the meeting on Friday it would be very helpful if I
get an idea of your migration process.
Hence if you could upload your script on GitHub or send it here. It would
be much appreciated. Thanks.

Happy Contributing !!

On Fri, May 11, 2018 at 8:07 PM Rudra Sadhu  wrote:

> Hello!
>
> We are done with our second weekly meeting discussing the project. (this
> was a very short meeting)
> Please find the logs at
> http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-11T14:09:25
>
> And we will be doing the next meeting on next Friday at the same time 1600
> CET.
>
> thanks,
> Rudra Sadhu
>
> On Tue, May 8, 2018 at 2:43 PM, Rudra Sadhu  wrote:
>
>> I realise I've not explained the project as well as I could/should have.
>> This blog post[1] is an attempt to better define the same.
>>
>> We can discuss more about this in the sugar-devel meeting today, if
>> required.
>>
>> Regards,
>> Rudra Sadhu
>>
>> [1] :
>> https://rdrsadhu.github.io/blog/gsoc2018/2018-05-08-project-details/
>>
>>
>> On Mon, May 7, 2018 at 4:10 AM, James Cameron  wrote:
>>
>>> Yes, we do seem to be talking to ourselves.
>>>
>>> The goal remains, though the mentors in that meeting didn't mention
>>> it; give them some slack, they haven't been especially heavy
>>> contributors to Sugar Labs.  Of the three mentors present, Divyanshu,
>>> Onuwa, and Ibiam, only Ibiam has been a recently active contributor,
>>> and not to the Wiki, Help activity or https://help.sugarlabs.org/
>>>
>>> Re: Hello World.  It is a coding example, has no use otherwise, so it
>>> should not be in activities.sugarlabs.org; I've disabled it.  Version
>>> will be incremented when a release is made.  Repository has no release
>>> tags.  We need an activity maintainer for it.  A checklist for
>>> maintaining an activity is here;
>>>
>>>
>>> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
>>>
>>> Across the activity set, we have very few activity maintainers.  This
>>> will change as the GSoC coding period begins; particularly as Yash and
>>> Rahul begin working.
>>>
>>> Back on topic; Rudra's project has a purpose; it is a subset of
>>> activity maintenance, but the coding is automation that will be used
>>> _once_.  Possibly a brain-numbing exercise, akin to road construction
>>> during the Irish potato famine.
>>>
>>> I've been a reviewer for the pull requests so far; four of them just
>>> now.  Mentors, Walter, Tony, and others could help by reviewing
>>> Rudra's pull requests as they are made rather than leaving it to me.
>>> ;-)
>>>
>>> @Rudra, my recommendation is to set an order of work; start with the
>>> demonstration set of activities (Fructose), because we keep these
>>> maintained well, then work on the activities that Tony has listed as
>>> working with Ubuntu 18.04 or Thomas has listed as working with Fedora
>>> 28.
>>>
>>> @Rudra, also think through the whole ecosystem from coding to user,
>>> and propose changes to your project in response to your reading of
>>> the current mailing list thread.  We're not expecting you to be a
>>> compliant robot, but an imaginative student.  Situation reminds me of
>>> something I saw in the student guide;
>>>
>>>
>>> https://google.github.io/gsocguides/student/finding-the-right-project.html
>>>
>>> "Don’t be that person: Cut and pasting an idea from the organization
>>> page and turning that in as your project’s description is a big no-no.
>>> You’ll be expected to research and submit your own ideas about how to
>>> accomplish the project your way, not just state the end result."
>>>
>>> On Sun, May 06, 2018 at 10:44:06AM +0800, Tony Anderson wrote:
>>> > Hi, Walter
>>> >
>>> > Sadly, I saw no comment in the meeting that suggests the project
>>> includes this
>>> > goal. As you know, a common outcome to GSOC projects is that they are
>>> not
>>> > completed in the available time. Perhaps the project could be more
>>> explicit as
>>> > an update to the help activity than as a migration of wiki pages to
>>> github.
>>> >
>>> > Tony
>>> >
>>> > On Sunday, 06 May, 2018 09:55 AM, Walter Bender wrote:
>>> >
>>> > On Sat, May 5, 2018 at 9:04 PM Tony Anderson <[1]t...@olenepal.org>
>>> wrote:
>>> >
>>> > SugarLabs is our site to communicate with our users and
>>> prospective
>>> > users. GitHub is our site to support SugarLabs development. In
>>> this
>>> > meeting it is pointed out that maintaining two versions of the
>>> > wikipages will be difficult (obvious, since we are unable to
>>> maintain
>>> > even one). The evil word 'deprecation' was used (I would have
>>> preferred
>>> > - improved). It is logical to maintain markdown pages
>>> describing the
>>> > technical design of an activity (such as Browse or Turtle
>>> Blocks).
>>> > However, we need documentation for users with screenshots
>>> showing the
>>> > intended 

Re: [Sugar-devel] GSoC Project: Migration of Activities wiki-pages to GitHub

[Rudra Sadhu]

Hello!

We are done with our second weekly meeting discussing the project. (this
was a very short meeting)
Please find the logs at
http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-05-11T14:09:25

And we will be doing the next meeting on next Friday at the same time 1600
CET.

thanks,
Rudra Sadhu

On Tue, May 8, 2018 at 2:43 PM, Rudra Sadhu  wrote:

> I realise I've not explained the project as well as I could/should have.
> This blog post[1] is an attempt to better define the same.
>
> We can discuss more about this in the sugar-devel meeting today, if
> required.
>
> Regards,
> Rudra Sadhu
>
> [1] : https://rdrsadhu.github.io/blog/gsoc2018/2018-05-08-project-details/
>
>
> On Mon, May 7, 2018 at 4:10 AM, James Cameron  wrote:
>
>> Yes, we do seem to be talking to ourselves.
>>
>> The goal remains, though the mentors in that meeting didn't mention
>> it; give them some slack, they haven't been especially heavy
>> contributors to Sugar Labs.  Of the three mentors present, Divyanshu,
>> Onuwa, and Ibiam, only Ibiam has been a recently active contributor,
>> and not to the Wiki, Help activity or https://help.sugarlabs.org/
>>
>> Re: Hello World.  It is a coding example, has no use otherwise, so it
>> should not be in activities.sugarlabs.org; I've disabled it.  Version
>> will be incremented when a release is made.  Repository has no release
>> tags.  We need an activity maintainer for it.  A checklist for
>> maintaining an activity is here;
>>
>> https://github.com/sugarlabs/sugar-docs/blob/master/src/cont
>> ributing.md#checklist---maintainer
>>
>> Across the activity set, we have very few activity maintainers.  This
>> will change as the GSoC coding period begins; particularly as Yash and
>> Rahul begin working.
>>
>> Back on topic; Rudra's project has a purpose; it is a subset of
>> activity maintenance, but the coding is automation that will be used
>> _once_.  Possibly a brain-numbing exercise, akin to road construction
>> during the Irish potato famine.
>>
>> I've been a reviewer for the pull requests so far; four of them just
>> now.  Mentors, Walter, Tony, and others could help by reviewing
>> Rudra's pull requests as they are made rather than leaving it to me.
>> ;-)
>>
>> @Rudra, my recommendation is to set an order of work; start with the
>> demonstration set of activities (Fructose), because we keep these
>> maintained well, then work on the activities that Tony has listed as
>> working with Ubuntu 18.04 or Thomas has listed as working with Fedora
>> 28.
>>
>> @Rudra, also think through the whole ecosystem from coding to user,
>> and propose changes to your project in response to your reading of
>> the current mailing list thread.  We're not expecting you to be a
>> compliant robot, but an imaginative student.  Situation reminds me of
>> something I saw in the student guide;
>>
>> https://google.github.io/gsocguides/student/finding-the-righ
>> t-project.html
>>
>> "Don’t be that person: Cut and pasting an idea from the organization page
>> and turning that in as your project’s description is a big no-no. You’ll be
>> expected to research and submit your own ideas about how to accomplish the
>> project your way, not just state the end result."
>>
>> On Sun, May 06, 2018 at 10:44:06AM +0800, Tony Anderson wrote:
>> > Hi, Walter
>> >
>> > Sadly, I saw no comment in the meeting that suggests the project
>> includes this
>> > goal. As you know, a common outcome to GSOC projects is that they are
>> not
>> > completed in the available time. Perhaps the project could be more
>> explicit as
>> > an update to the help activity than as a migration of wiki pages to
>> github.
>> >
>> > Tony
>> >
>> > On Sunday, 06 May, 2018 09:55 AM, Walter Bender wrote:
>> >
>> > On Sat, May 5, 2018 at 9:04 PM Tony Anderson <[1]t...@olenepal.org>
>> wrote:
>> >
>> > SugarLabs is our site to communicate with our users and
>> prospective
>> > users. GitHub is our site to support SugarLabs development. In
>> this
>> > meeting it is pointed out that maintaining two versions of the
>> > wikipages will be difficult (obvious, since we are unable to
>> maintain
>> > even one). The evil word 'deprecation' was used (I would have
>> preferred
>> > - improved). It is logical to maintain markdown pages
>> describing the
>> > technical design of an activity (such as Browse or Turtle
>> Blocks).
>> > However, we need documentation for users with screenshots
>> showing the
>> > intended method of use and providing challenges to show advanced
>> > capabilities. ASLO needs more help to enable users to make
>> informed
>> > decisions on which activities to download and install.
>> >
>> > Our current direction seems to lead to us talking only to
>> ourselves.
>> >
>> > Part of this effort is to update/expand/improve the Help Activity.
>> It seems
>> > that this would make the documentation