[Sugar-devel] Port from GStreamer Gst.Message.structure to get_structure()

[James Cameron]

GStreamer project removed or deprecated the structure field of Gst.Message, 
replacing it with a method get_structure().

Many activities are affected.

Code pattern to look for is a reference to message.structure, e.g.

bus = pipe.get_bus()
bus.connect('message', _cb)

def _cb(bus, message):
message.structure. ...

References:

https://github.com/orgs/sugarlabs/projects/3
https://lazka.github.io/pgi-docs/Gst-1.0/classes/Bus.html#Gst.Bus.signals.message
https://lazka.github.io/pgi-docs/Gst-1.0/classes/Message.html#Gst.Message.get_structure

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

[Sugar-devel] Please answer Impact of project on the community

[Ritwik Abhishek]

Hello,
Thanks for reviewing my proposal. I request you to please write something
in impact of project on the community.
link to my proposal is https://docs.google.com/document/d/
1w1QORVYpgXgDtovc67kNb2DJiG6kZAJ2oT5NjNy2klI/edit?usp=sharing

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

Re: [Sugar-devel] Review Request of GSoC Proposal: Making a Beginner Guide

[James Cameron]

Good question, Tony.  It is for developers.  Self-serving.

I don't agree with the project at all.  I think it is make-work.  It
doesn't help the children that Sugar is focused on.

None of the mentors have made ongoing or material contributions to our
existing developer documentation.  Very few of them have made
contributions to Sugar or Sugarizer.

Still, I'd be happy to see it succeed, but the risks I've mentioned
before are significant, and such ambitious plans require good
evidence.

The proposal is well formatted and clear.  It's just the project
itself which seems improbable.

On Mon, Mar 26, 2018 at 02:41:16PM +0200, Tony Anderson wrote:
> Is this a 'beginner' in the community of developers or a beginning user of
> Sugar?
> 
> Tony
> 
> On Monday, 26 March, 2018 09:09 AM, Pratul Kumar wrote:
> 
> *Hello,
> Thanks for the guidance, reviews and feedbacks.
> 
> Kindly help me with the answer to one of the questions of "You and
> Community".
> 
> Question:  If your project is successfully completed, what will its impact
> be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in
> length. The first one should be yours. The other two should be answers 
> from
> members of the Sugar Labs community, at least one of whom should be a 
> Sugar
> Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
> [1]https://docs.google.com/document/d/
> 1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing
>
> 
> Thanks,
> Pratul Kumar
> 
> On Tue, Mar 20, 2018 at 8:45 PM, Pratul Kumar 
> <[2]pratulkumar1...@gmail.com
> > wrote:
> 
> *
> Hello,
> 
> Thanks for providing feedback and guiding me in the right direction.
> I have worked on it and tried to add them and make things bit more
> refined.
> 
> [3]https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-
> RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing
> 
> Kindly have a look at it and if there is something which can be
> improved, kindly let me know,
> I will be more than happy to work on it.
> 
> Regards,
> Pratul Kumar
> 
> On Mon, Mar 19, 2018 at 1:02 PM, James Cameron <[4]qu...@laptop.org>
> wrote:
> 
> G'day Pratul,
> 
> Thanks for the opportunity to comment on your draft proposal.
> 
> Your proposal suffers from lack of measurable controls for risks. 
> In
> general, you've added responses to the risks which are mostly
> either
> aspirational, hopeful, or procedural.  Some of the responses don't
> address the risks.
> 
> For reference, here is what I had previously written on these
> risks;
> 
> [5]http://lists.sugarlabs.org/archive/sugar-devel/2018-February/
> 055030.html
> 
> Please do not use HTML for the beginner guide.  Instead, please 
> use
> Markdown.  Markdown has a wider audience of authors.  HTML should
> be
> generated automatically.
> 
> Please consider better controls for risk #3.  My post on 14th
> February
> gave some ideas.  Just claiming that you'd like to keep working on
> the
> project after GSoC ... doesn't seem probable.  It is aspirational.
>
> --
> James Cameron
> [6]http://quozl.netrek.org/
>
> 
> --
> ​
> Pratul Kumar | Sophomore LNMIIT | +91-8107525493
>
> GCI Mentor SugarLabs, Mentor & Beta Tester at Coursera, HKUST
> University
> Stanford Scholar Internship, Mozilla Club Captain LNMIIT, Head of
> Developers Group HackerEarth
>  _ [7]LinkedIn [s] [8]Github _  [s] 
>
> 
> --
> ​
> Pratul Kumar | Sophomore LNMIIT | +91-8107525493
> 
> GCI Mentor SugarLabs, Mentor & Beta Tester at Coursera, HKUST
> University
> Stanford Scholar Internship, Mozilla Club Captain LNMIIT, Head of
> Developers Group HackerEarth
>  [s] [9]LinkedIn [s] [10]Github [s]  [s] 
>
> 
>
> ___
> Sugar-devel mailing list
> [11]Sugar-devel@lists.sugarlabs.org
> [12]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] 
> https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing
> [2] mailto:pratulkumar1...@gmail.com
> [3] 
> https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing
> [4] mailto:qu...@laptop.org
> [5] http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055030.html
> [6] http://quozl.netrek.org/
> [7] https://www.linkedin.com/in/pratul1997/
> [8] https://github.com/Pratul1997
> [9] https://www.linkedin.com/in/pratul1997/
> 

Re: [Sugar-devel] Request to review GSoC proposal (Music Blocks)

[James Cameron]

Thanks for your proposal.  I've reviewed it.  I changed sugarlabs to
Sugar Labs.

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

[Sugar-devel] Development Team Meeting, 27th March 9PM UTC

[James Cameron]

Developers are invited to attend the next team meeting, on;

- Tuesday 27th March at 5pm US/Eastern,
- Tuesday 27th March at 9pm UTC,
- Wednesday 28th March at 2:30am IST,
- Wednesday 28th March at 8am Australia/Sydney,

Agenda to include

- what we have been working on,

- port from GConf to Gio.Settings,

- don't ask, just do,

#sugar-meeting irc.freenode.net

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

[Sugar-devel] Request to review GSoC Proposal [Sugar Labs Social]

[Samar Singh Karnawat]

Hello,

Please review and give suggestions on my proposal for Sugar Labs Social.

Also, anyone willing to answer the first question of "You and Community" is
welcome. Please reply to this thread or e-mail me back with the answer so
that I can add it to my proposal.
I also request the mentors for this project to send their answers.

Here is the link to the draft of my proposal:
https://docs.google.com/document/d/1zr-avki8SMAsjSShBBjZcs25pduJJb6JfvfpLcSt7WA/edit?usp=sharing
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Tomorrow is Student applications Deadline

[Carlos mauro]

March 27 16:00 UTC Student application deadline
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Activity-Team] Request to review GSoC Proposal

[Vipul Gupta]

Hi

On Mon, Mar 26, 2018 at 11:37 AM, Tony Anderson  wrote:

> As always, the question is the impact on our users. The traditional source
> of information for users is http://www.sugarlabs.org and
> http://www.laptop.org and, especially the wiki pages. The traditional
> source for activities is http://activities.sugarlabs.org (ASLO). So far
> the effect of gitHub has been to reduce the value of these two sources. In
> many cases the activities on ASLO have been superceded by ones on gitHub or
> other git repository but are not available to our users. The documentation
> of activities on ASLO has never been adequate but now no effort will be
> made to improve it. This continues the trend toward Sugar being a
> playground for the technical elite.
>
> Tony


I agree with all points that Tony put forward and especially where GitHub
either directly or indirectly resulted in the reduction of value of the two
sources mentioned. The world is changing, technology at present will become
obsolete at one point of time. The decision of Sugar Labs to keep with the
times, advance, grow, and get new developers associated by migrating its
documentation of activities is a critical for future opportunities and will
help everyone involved.

Like I mentioned in my proposal too that documentation is one of the most
important steps of any project specially if it is open-source. I know that
because of the experience of actually writing and reading it for years
myself. If for users, the documentation is easy to read, easy to edit and
accessible fast. Then I think that helps everybody. Be it users, members
and even developers looking to contribute.

Thanks for your comments, Tony. Will be sure to add them to my proposal. I
really think my project would be beneficial for the community and all its
users involved.

-- 
Cordially,
Vipul Gupta
Mixster  | Github

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

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[Frederick Grose]

On Mon, Mar 26, 2018 at 2:10 AM, James Cameron  wrote:

> I don't know.  I don't have administrator rights on the Wiki.  Hope
> Walter or someone else can answer.  Meanwhile, I've been replacing
> migrated pages with links to the new location, so that old links don't
> break.
>

​This method should be preferred.  It is easy and effective, doesn't
destroy history, and points toward where you want people to look.
​

>
> On Mon, Mar 26, 2018 at 11:31:49AM +0530, Rudra Sadhu wrote:
> > thanks James for the assessment.
> >
> > I've successfully migrated a few of the pages from [1]https://
> > wiki.sugarlabs.org/go/Activities to GitHub
> > Find the pull request at [2]https://github.com/
> godiard/help-activity/pull/38
> >
> > and now, the wiki-pages needs to be deprecated.
> > As to delete a page from the wiki, an user needs 'administrators' rights,
> >
> > thus,
> > Some possible ways to delete the pages are:
> > 1. create a bot account with restricted permissions which can delete
> pages(my
> > preferred choice)
> > 2. for a temporary period grant delete rights to me
> > 3. someone trusted deletes the pages
> > 4. something else and better (please suggest)
> >
> > It may not be convenient to delete the pages manually as there will be
> > thousands of those(including extra images/files attached to the pages)
> for the
> > 345 pages to be migrated
> > All of the deletion is preferred to be done by a script (which
> uses [3]https://
> > www.mediawiki.org/wiki/API:Delete), under close supervision
> > Do not worry, no damage(if at all) will be permanent; since it is
> possible to
> > always recover pages deleted by an user with 'administrators' rights.
> Read [4]
> > https://www.mediawiki.org/wiki/Help:Deletion_and_undeletion
> >
> > Please recommend the desired course of action
> >
> > thanks,
> > Rudra Sadhu
> >
> > On Mon, Mar 26, 2018 at 10:41 AM, James Cameron <[5]qu...@laptop.org>
> wrote:
> >
> > Thanks, I've reviewed your updated proposal.
> >
> > My assessment of project impact;
> >
> > Originally documentation was separate because we had non-coding
> > developers and tool chains that varied by type of developer.  Now we
> > use GitHub the tool chains are combined.
> >
> > With the project as described, documentation will be concentrated in
> > the source code repository for an activity, reducing ongoing
> > maintenance.
> >
> > We have less active Wiki contributors than we ever did, and in the
> > current threat environment a Wiki requires significant monitoring and
> > administration; we recently lost some system administrators and
> gained
> > new ones; using GitHub allows us to outsource system administration.
> >
> > On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> > > Thanks James, Carlos, Gonzalo and everyone for the insights
> > >
> > > Your inputs helped a lot, and I've updated my proposal accordingly.
> > > A lot of important stuff was added such as the working the Help
> Activity,
> > > keeping check on the activity bundle sizes and completing the
> > miscellaneous
> > > section.
> > >
> > > The proposal is available at [1][6]https://wiki.sugarlabs.org/go/
> > Summer_of_Code/
> > > 2018/attentive_migration_of_wiki_activity_pages_to_git
> > > I've also shared the same via the GSoC dashboard
> > > Please read, most importantly the 'About Project' section
> > >
> > > Let me know of the stuff I should add/remove/update to better
> justify the
> > > task.
> > >
> > > also It would help, if someone volunteers to answer the impact of
> this
> > project
> > > required to be filled in as an answer in the 'Project and the
> Community'
> > > section
> > >
> > > Thanks
> > > Rudra Sadhu
> > >
> > > On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2][7]
> rdrsa...@gmail.com>
> > wrote:
> > >
> > > Thanks James,
> > > the resources you mentioned were really helpful.
> > >
> > > I went ahead to migrate a few of the pages by the guidelines
> you
> > described.
> > > Find the Pull Request here: [3][8]https://github.
> com/sugarlabs/
> > activity-abacus
> > > /pull/13
> > >
> > > Please review
> > >
> > > On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4][9]
> > qu...@laptop.org> wrote:
> > >
> > > On IRC #sugar Vipul Gupta asked;
> > >
> > >  Hey, in the Activity task of migration.
> We need
> > to
> > > migrate content from activities page to their Githubs or
> their
> > git
> > > pages.
> > >
> > >  ?
> > >
> > >  Please clarify which one is it. Some
> pages don't
> > have
> > > the links of their repository
> > >
> > >  The organisations is not uniform. I have
> > included
> > > this in my 

Re: [Sugar-devel] Review Request of GSoC Proposal: Making a Beginner Guide

[Tony Anderson]

Is this a 'beginner' in the community of developers or a beginning user 
of Sugar?


Tony


On Monday, 26 March, 2018 09:09 AM, Pratul Kumar wrote:

Hello,
Thanks for the guidance, reviews and feedbacks.

Kindly help me with the answer to one of the questions of "You and 
Community".


Question: If your project is successfully completed, what will its 
impact be on the Sugar Labs community? Give 3 answers, each 1-3 
paragraphs in length. The first one should be yours. The other two 
should be answers from members of the Sugar Labs community, at least 
one of whom should be a Sugar Labs GSoC mentor. Provide email contact 
information for non-GSoC mentors.

https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing


Thanks,
Pratul Kumar

On Tue, Mar 20, 2018 at 8:45 PM, Pratul Kumar 
> wrote:


Hello,

Thanks for providing feedback and guiding me in the right direction.
I have worked on it and tried to add them and make things bit more
refined.


https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing



Kindly have a look at it and if there is something which can be
improved, kindly let me know,
I will be more than happy to work on it.

Regards,
Pratul Kumar

On Mon, Mar 19, 2018 at 1:02 PM, James Cameron > wrote:

G'day Pratul,

Thanks for the opportunity to comment on your draft proposal.

Your proposal suffers from lack of measurable controls for
risks.  In
general, you've added responses to the risks which are mostly
either
aspirational, hopeful, or procedural.  Some of the responses don't
address the risks.

For reference, here is what I had previously written on these
risks;

http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055030.html



Please do not use HTML for the beginner guide. Instead, please use
Markdown.  Markdown has a wider audience of authors.  HTML
should be
generated automatically.

Please consider better controls for risk #3.  My post on 14th
February
gave some ideas.  Just claiming that you'd like to keep
working on the
project after GSoC ... doesn't seem probable.  It is aspirational.

--
James Cameron
http://quozl.netrek.org/




-- 
*

​
Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at
*Coursera*,* HKUST University
**Stanford* Scholar Internship,* Mozilla* Club Captain LNMIIT,
*Head of Developers* Group *HackerEarth*
LinkedIn Github





--
*
​
Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at
*Coursera*,* HKUST University
**Stanford* Scholar Internship,* Mozilla* Club Captain LNMIIT,
*Head of Developers* Group *HackerEarth*
LinkedIn Github




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


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

Re: [Sugar-devel] Review Request of GSoC Proposal: Making a Beginner Guide

[Pratul Kumar]

Hello,
Thanks for the guidance, reviews and feedbacks.

Kindly help me with the answer to one of the questions of "You and
Community".

Question:  If your project is successfully completed, what will its impact
be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in
length. The first one should be yours. The other two should be answers from
members of the Sugar Labs community, at least one of whom should be a Sugar
Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing


Thanks,
Pratul Kumar

On Tue, Mar 20, 2018 at 8:45 PM, Pratul Kumar 
wrote:

> Hello,
>
> Thanks for providing feedback and guiding me in the right direction.
> I have worked on it and tried to add them and make things bit more refined.
>
> https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-
> RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing
>
> Kindly have a look at it and if there is something which can be improved,
> kindly let me know,
> I will be more than happy to work on it.
>
> Regards,
> Pratul Kumar
>
> On Mon, Mar 19, 2018 at 1:02 PM, James Cameron  wrote:
>
>> G'day Pratul,
>>
>> Thanks for the opportunity to comment on your draft proposal.
>>
>> Your proposal suffers from lack of measurable controls for risks.  In
>> general, you've added responses to the risks which are mostly either
>> aspirational, hopeful, or procedural.  Some of the responses don't
>> address the risks.
>>
>> For reference, here is what I had previously written on these risks;
>>
>> http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055030.html
>>
>> Please do not use HTML for the beginner guide.  Instead, please use
>> Markdown.  Markdown has a wider audience of authors.  HTML should be
>> generated automatically.
>>
>> Please consider better controls for risk #3.  My post on 14th February
>> gave some ideas.  Just claiming that you'd like to keep working on the
>> project after GSoC ... doesn't seem probable.  It is aspirational.
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>>
>
>
>
> --
> *​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*
>
> *GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
> * HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
> LNMIIT, *Head of Developers* Group *HackerEarth*
>   [image: LinkedIn]   [image:
> Github]  
>
>


-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]   [image:
Github]  
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[James Cameron]

I don't know.  I don't have administrator rights on the Wiki.  Hope
Walter or someone else can answer.  Meanwhile, I've been replacing
migrated pages with links to the new location, so that old links don't
break.

On Mon, Mar 26, 2018 at 11:31:49AM +0530, Rudra Sadhu wrote:
> thanks James for the assessment.
> 
> I've successfully migrated a few of the pages from [1]https://
> wiki.sugarlabs.org/go/Activities to GitHub
> Find the pull request at [2]https://github.com/godiard/help-activity/pull/38
> 
> and now, the wiki-pages needs to be deprecated.
> As to delete a page from the wiki, an user needs 'administrators' rights,
> 
> thus,
> Some possible ways to delete the pages are:
> 1. create a bot account with restricted permissions which can delete pages(my
> preferred choice)
> 2. for a temporary period grant delete rights to me
> 3. someone trusted deletes the pages
> 4. something else and better (please suggest)
> 
> It may not be convenient to delete the pages manually as there will be
> thousands of those(including extra images/files attached to the pages) for the
> 345 pages to be migrated
> All of the deletion is preferred to be done by a script (which uses 
> [3]https://
> www.mediawiki.org/wiki/API:Delete), under close supervision
> Do not worry, no damage(if at all) will be permanent; since it is possible to
> always recover pages deleted by an user with 'administrators' rights. Read [4]
> https://www.mediawiki.org/wiki/Help:Deletion_and_undeletion
> 
> Please recommend the desired course of action
> 
> thanks,
> Rudra Sadhu
> 
> On Mon, Mar 26, 2018 at 10:41 AM, James Cameron <[5]qu...@laptop.org> wrote:
> 
> Thanks, I've reviewed your updated proposal.
> 
> My assessment of project impact;
> 
> Originally documentation was separate because we had non-coding
> developers and tool chains that varied by type of developer.  Now we
> use GitHub the tool chains are combined.
> 
> With the project as described, documentation will be concentrated in
> the source code repository for an activity, reducing ongoing
> maintenance.
> 
> We have less active Wiki contributors than we ever did, and in the
> current threat environment a Wiki requires significant monitoring and
> administration; we recently lost some system administrators and gained
> new ones; using GitHub allows us to outsource system administration.
>
> On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> > Thanks James, Carlos, Gonzalo and everyone for the insights
> >
> > Your inputs helped a lot, and I've updated my proposal accordingly.
> > A lot of important stuff was added such as the working the Help 
> Activity,
> > keeping check on the activity bundle sizes and completing the
> miscellaneous
> > section.
> >
> > The proposal is available at [1][6]https://wiki.sugarlabs.org/go/
> Summer_of_Code/
> > 2018/attentive_migration_of_wiki_activity_pages_to_git
> > I've also shared the same via the GSoC dashboard
> > Please read, most importantly the 'About Project' section
> >
> > Let me know of the stuff I should add/remove/update to better justify 
> the
> > task. 
> >
> > also It would help, if someone volunteers to answer the impact of this
> project
> > required to be filled in as an answer in the 'Project and the Community'
> > section 
> >
> > Thanks
> > Rudra Sadhu
> >
> > On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2][7]rdrsa...@gmail.com>
> wrote:
> >
> >     Thanks James,
> >     the resources you mentioned were really helpful.
> >
> >     I went ahead to migrate a few of the pages by the guidelines you
> described.
> >     Find the Pull Request here: [3][8]https://github.com/sugarlabs/
> activity-abacus
> >     /pull/13
> >
> >     Please review
> >
> >     On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4][9]
> qu...@laptop.org> wrote:
> >
> >         On IRC #sugar Vipul Gupta asked;
> >
> >          Hey, in the Activity task of migration. We need
> to
> >         migrate content from activities page to their Githubs or their
> git
> >         pages.
> >
> >          ?
> >
> >          Please clarify which one is it. Some pages 
> don't
> have
> >         the links of their repository
> >
> >          The organisations is not uniform. I have
> included
> >         this in my proposal too.
> >
> >          vipulgupta2048: need to write a program that will
> migrate
> >         content from [5][10]wiki.sugarlabs.org activities page to
> respective GitHub
> >         repository README.md files, yet without duplicating what is
> there, and
> >         without duplicating user documentation in the help-activity, see
> >         recent posts to sugar-devel@ discussing the issue.
> >
> >      

Re: [Sugar-devel] [Activity-Team] Request to review GSoC Proposal

[Tony Anderson]

As always, the question is the impact on our users. The traditional 
source of information for users is http://www.sugarlabs.org and 
http://www.laptop.org and, especially the wiki pages. The traditional 
source for activities is http://activities.sugarlabs.org (ASLO). So far 
the effect of gitHub has been to reduce the value of these two sources. 
In many cases the activities on ASLO have been superceded by ones on 
gitHub or other git repository but are not available to our users. The 
documentation of activities on ASLO has never been adequate but now no 
effort will be made to improve it. This continues the trend toward Sugar 
being a playground for the technical elite.


Tony


On Monday, 26 March, 2018 07:05 AM, James Cameron wrote:

My assessment of project impact;

Originally documentation was separate because we had non-coding
developers and tool chains that varied by type of developer.  Now we
use GitHub the tool chains are combined.

With the project as described, documentation will be concentrated in
the source code repository for an activity, reducing ongoing
maintenance.

We have less active Wiki contributors than we ever did, and in the
current threat environment a Wiki requires significant monitoring and
administration; we recently lost some system administrators and gained
new ones; using GitHub allows us to outsource system administration.

On Sat, Mar 24, 2018 at 01:43:01AM +0530, Vipul Gupta wrote:

Hello,

I have submitted the first draft of my GSoC proposal and shared it with edit
access permission on Google GSoC website with Sugar Labs. Please review,
comment and write a review how my proposal would help the community. Even if it
is just one line.

I would really like to work on this project under the activity team and
contribute further on Sugar Labs for a greater good.

If you do not have access to the Google GSoC website for Sugar Labs. Hit me up
on @vipulgupta2048 or reply to this thread. I will promptly reply with google
docs link of my proposal.

Thanking you

Cordially,
Vipul Gupta
[1]Mixster | [2]Github

References:

[1] https://mixstersite.wordpress.com/
[2] https://github.com/vipulgupta2048


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

Re: [Sugar-devel] Introduction and review request of GSoC Proposal:

[Rudra Sadhu]

thanks James for the assessment.

I've successfully migrated a few of the pages from
https://wiki.sugarlabs.org/go/Activities to GitHub
Find the pull request at https://github.com/godiard/help-activity/pull/38

and now, the wiki-pages needs to be deprecated.
As to delete a page from the wiki, an user needs 'administrators' rights,

thus,
Some possible ways to delete the pages are:
1. create a bot account with restricted permissions which can delete
pages(my preferred choice)
2. for a temporary period grant delete rights to me
3. someone trusted deletes the pages
4. something else and better (please suggest)

It may not be convenient to delete the pages manually as there will be
thousands of those(including extra images/files attached to the pages) for
the 345 pages to be migrated
All of the deletion is preferred to be done by a script (which uses
https://www.mediawiki.org/wiki/API:Delete), under close supervision
Do not worry, no damage(if at all) will be permanent; since it is possible
to always recover pages deleted by an user with 'administrators' rights.
Read https://www.mediawiki.org/wiki/Help:Deletion_and_undeletion

Please recommend the desired course of action

thanks,
Rudra Sadhu


On Mon, Mar 26, 2018 at 10:41 AM, James Cameron  wrote:

> Thanks, I've reviewed your updated proposal.
>
> My assessment of project impact;
>
> Originally documentation was separate because we had non-coding
> developers and tool chains that varied by type of developer.  Now we
> use GitHub the tool chains are combined.
>
> With the project as described, documentation will be concentrated in
> the source code repository for an activity, reducing ongoing
> maintenance.
>
> We have less active Wiki contributors than we ever did, and in the
> current threat environment a Wiki requires significant monitoring and
> administration; we recently lost some system administrators and gained
> new ones; using GitHub allows us to outsource system administration.
>
> On Sun, Mar 25, 2018 at 08:06:49PM +0530, Rudra Sadhu wrote:
> > Thanks James, Carlos, Gonzalo and everyone for the insights
> >
> > Your inputs helped a lot, and I've updated my proposal accordingly.
> > A lot of important stuff was added such as the working the Help Activity,
> > keeping check on the activity bundle sizes and completing the
> miscellaneous
> > section.
> >
> > The proposal is available at [1]https://wiki.sugarlabs.
> org/go/Summer_of_Code/
> > 2018/attentive_migration_of_wiki_activity_pages_to_git
> > I've also shared the same via the GSoC dashboard
> > Please read, most importantly the 'About Project' section
> >
> > Let me know of the stuff I should add/remove/update to better justify the
> > task.
> >
> > also It would help, if someone volunteers to answer the impact of this
> project
> > required to be filled in as an answer in the 'Project and the Community'
> > section
> >
> > Thanks
> > Rudra Sadhu
> >
> > On Wed, Mar 21, 2018 at 5:46 PM, Rudra Sadhu <[2]rdrsa...@gmail.com>
> wrote:
> >
> > Thanks James,
> > the resources you mentioned were really helpful.
> >
> > I went ahead to migrate a few of the pages by the guidelines you
> described.
> > Find the Pull Request here: [3]https://github.com/
> sugarlabs/activity-abacus
> > /pull/13
> >
> > Please review
> >
> > On Wed, Mar 21, 2018 at 4:32 AM, James Cameron <[4]qu...@laptop.org>
> wrote:
> >
> > On IRC #sugar Vipul Gupta asked;
> >
> >  Hey, in the Activity task of migration. We need
> to
> > migrate content from activities page to their Githubs or their
> git
> > pages.
> >
> >  ?
> >
> >  Please clarify which one is it. Some pages
> don't have
> > the links of their repository
> >
> >  The organisations is not uniform. I have
> included
> > this in my proposal too.
> >
> >  vipulgupta2048: need to write a program that will
> migrate
> > content from [5]wiki.sugarlabs.org activities page to
> respective GitHub
> > repository README.md files, yet without duplicating what is
> there, and
> > without duplicating user documentation in the help-activity, see
> > recent posts to sugar-devel@ discussing the issue.
> >
> >  vipulgupta2048: did you get the above?  if not, i'll
> have to
> > write a mail.
> >
> > My recent post is quoted below and can be found in the mailing
> list
> > archives.
> >
> > On Wed, Mar 14, 2018 at 06:04:02PM +1100, James Cameron wrote:
> > > G'day Rudra,
> > >
> > > Thanks for being at the meeting earlier, and for your proposal.
> > >
> > > A project for GSoC 2013 added context sensitive help, or user
> > > documentation, to the Sugar desktop, with alt+shift+h key.
> > >
> > > It works with the Help activity.  Metadata in the Help
> activity links
> > a
> > > subject activity to a markdown source