[Sugar-devel] GSoC '018 Project Report
Project: Migration of activity wiki-pages to GitHub (and simultaneously help-activity) Final Report: https://github.com/rdrsadhu/beta-migration-script Please share your suggestions and feedback. Thanks, Rudra Sadhu [rdrsadhu] ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [FEATURE] Add a reset button to Sugar
+1 I believe this feature will be very useful. Just that there should be checkpoints so that users don't reset their sugar by mistake. On Sun, Jun 10, 2018 at 6:04 PM Rahul Bothra < f2016...@pilani.bits-pilani.ac.in> wrote: > Hi all, > > Feature: Add a "reset sugar" button > > Button action: > - Remove additional activities installed by the user, leaving only the > pre installed set > - Remove all journal entries > - Remove the user account; user should get the "create new user" prompt > on logging in the next time > > Possible use case: > - While transfer of computer from one user to another > > Please share your opinions on the same. > > Thanks > Rahul Bothra (Pro-Panda) > ___ > 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] GSoC Project: Migration of Activities wiki-pages to GitHub
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 >> >
Re: [Sugar-devel] GSoC Project: Migration of Activities wiki-pages to GitHub
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-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 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 more rather than less > accessible, > > especially for our users w
Re: [Sugar-devel] GSoC Project: Migration of Activities wiki-pages to GitHub
Lets start this Friday. 1600 CET. > sure, I'll be present. All community members are invited to join as well. Nice article by the way, I made some corrections regarding some typos. > thanks a lot! I've rectified them in the blog. regards, Rudra Sadhu On Mon, Apr 30, 2018 at 2:51 PM, Onuwa Nnachi Isaac wrote: > Greetings from Nigeria, > > Welcome to Sugar Labs. > > Lets start this Friday. 1600 CET. > > We'll use the #sugar IRC. > > Nice article by the way, I made some corrections regarding some typos. > > Link to the correction > <https://docs.google.com/document/d/14GpTc9JMuCZ6SIZ04Do9i_DAemGOcw8DIqjBUADRRzo/edit?usp=sharing> > > Warm Regards > > > > Nnachi Isaac Onuwa > [image: https://]about.me/iamonuwa > <https://about.me/iamonuwa?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel> > > On Sat, Apr 28, 2018 at 12:54 PM, Rudra Sadhu wrote: > >> Greetings! >> >> Thank You for the opportunity to work with Sugar Labs under the banner of >> Google Summer of Code this year. >> >> I recently published an introductory blog post[1], describing my GSoC >> 2018 journey. >> Hope you'll love giving it a read. >> >> To my mentors (Divyanshu Rawat and Onuwa Nnachi Isaac) : >> Let me know your preferences to set up a regular set of meeting times to >> discuss the project. >> I would prefer them to be on #sugar so that other community members could >> possibly join. >> >> >> >> Looking forward to a great summer. :) >> >> Thanks, >> Rudra Sadhu >> >> [1] https://rdrsadhu.github.io/blog/gsoc2018/ >> > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] GSoC Project: Migration of Activities wiki-pages to GitHub
Greetings! Thank You for the opportunity to work with Sugar Labs under the banner of Google Summer of Code this year. I recently published an introductory blog post[1], describing my GSoC 2018 journey. Hope you'll love giving it a read. To my mentors (Divyanshu Rawat and Onuwa Nnachi Isaac) : Let me know your preferences to set up a regular set of meeting times to discuss the project. I would prefer them to be on #sugar so that other community members could possibly join. Looking forward to a great summer. :) Thanks, Rudra Sadhu [1] https://rdrsadhu.github.io/blog/gsoc2018/ ___ 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:
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 > > archive
Re: [Sugar-devel] Introduction and review request of GSoC Proposal:
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 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 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: https://github.com/sugar > labs/activity-abacus/pull/13 > > Please review > > > On Wed, Mar 21, 2018 at 4:32 AM, James Cameron 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 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 file, which is converted to HTML >> > and rendered in a tiny browser. >> > >> > Many of these source files came from the Wiki pages of activities, and >> > have been updated since then. >> > >> > Please review and integrate the Help activity into your proposal; for >> > instance; >> > >> > - avoid duplicating user documentation into activity repositories, >> > because that would make for unncessary maintenance burden, or; >> > >> > - move some of the Help activity files into activity repositories and >> > provide a way to update the Help activity from the subject >> > activities. >> > >> > Please review the discussion on these two pull requests; >> > >> > https://github.com/sugarlabs/activity-abacus/pull/12 >> > https://github.com/sugarlabs/sugar-docs/pull/137 >> > >> > And then ask any questions to clarify, thanks. >> > >> > -- >> > James Cameron >> > http://quozl.netrek.org/ >> >> -- >> 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] Introduction and review request of GSoC Proposal:
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: https://github.com/sugarlabs/activity-abacus/pull/13 Please review On Wed, Mar 21, 2018 at 4:32 AM, James Cameron 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 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 file, which is converted to HTML > > and rendered in a tiny browser. > > > > Many of these source files came from the Wiki pages of activities, and > > have been updated since then. > > > > Please review and integrate the Help activity into your proposal; for > > instance; > > > > - avoid duplicating user documentation into activity repositories, > > because that would make for unncessary maintenance burden, or; > > > > - move some of the Help activity files into activity repositories and > > provide a way to update the Help activity from the subject > > activities. > > > > Please review the discussion on these two pull requests; > > > > https://github.com/sugarlabs/activity-abacus/pull/12 > > https://github.com/sugarlabs/sugar-docs/pull/137 > > > > And then ask any questions to clarify, thanks. > > > > -- > > James Cameron > > http://quozl.netrek.org/ > > -- > James Cameron > http://quozl.netrek.org/ > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Introduction and review request of GSoC Proposal:
Hello everyone! My name is Rudra Sadhu, and this is my first email to the sugar-developer mailing list. I've been learning about the Sugar Labs community since the past one month. lurking in IRC channels, using the sugar desktop environment, reading mailing-list archives, exploring different parts of the wiki and codebase, to better understand this community. Application window for GSoC 2018 has opened and I'm interested to work with Sugar Labs this summer. For the project: 'Migration of wiki activity pages to git' I've drafted a well thought implementation workflow, with all necessary details. Please find the proposal at https://wiki.sugarlabs.org/go/Summer_of_Code/2018/attentive_migration_of_wiki_activity_pages_to_git I would love to discuss a lot more about different aspects of the proposal in detail. Let me know of everything you feel about the proposal, pointers on how it could be improved and please point out any mistakes you find. Your review and valuable feedback is important for the success of this project. Thanks, Rudra Sadhu email : rdrsa...@gmail.com IRC : rdrsadhu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
