Re: [Sugar-devel] GSOC proposal review

[James Cameron]

Organisation name is "Sugar Labs" not "Sugarlabs".

Changes to the user interface of Chat activity are unlikely to take
less than a week, due to pull request review.  You should plan to
start them sooner.

On Mon, Apr 01, 2024 at 12:34:55AM +0530, Sanjay Srikanth wrote:
> Hello and thanks for reviewing my proposal. I have made the necessary changes
> and I am looking for your feedback on the updated proposal.
> 
> I have attached the file below.
> 
> Thank you


> ___
> 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] Proposal Feedback : Refactor the Infoslicer Activity to generate plain-language summaries

[James Cameron]

Also you have the option to _not_ post proposals for public review, or
posting a different version to GSoC.  I'm not a mentor this year, but
if I recall correctly it is the version posted to GSoC that mentors
are to rely on for selecting.  Proposals posted earlier do indicate
community engagement, but they also make for competition, which isn't
always a positive experience.  Choose wisely.

On Sun, Mar 31, 2024 at 01:16:16PM +0530, Dhruvin Kavathiya wrote:
> Hello Harsh, GSOC proposals should not be posted as Google Docs instead 
> provide
> in form of PDF or github markdown as described in the guidelines : [1]https://
> github.com/sugarlabs/GSoC?tab=readme-ov-file
> 
> On Sun, Mar 31, 2024 at 1:55 AM Harsh Kasat <[2]harsh.kasa...@gmail.com> 
> wrote:
> 
> I want feedback on my GSOC proposal for the project "Refactor the
> Infoslicer Activity to generate plain-language summaries." Please use this
> Google Docs link to comment and suggest improvements. Project mentors are
> Walter Bender and Ibiam Chihurumnaya.
> [3]https://docs.google.com/document/d/
> 1uCYg1G3v1U71OQlwohg9d6xIsNBesKBaSYg-EZDTNgo/edit?usp=sharing
> ___
> Sugar-devel mailing list
> [4]Sugar-devel@lists.sugarlabs.org
> [5]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] https://github.com/sugarlabs/GSoC?tab=readme-ov-file
> [2] mailto:harsh.kasa...@gmail.com
> [3] 
> https://docs.google.com/document/d/1uCYg1G3v1U71OQlwohg9d6xIsNBesKBaSYg-EZDTNgo/edit?usp=sharing
> [4] mailto:Sugar-devel@lists.sugarlabs.org
> [5] http://lists.sugarlabs.org/listinfo/sugar-devel

> ___
> 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] Google Summer Of Code

[James Cameron]

Hello,

Perhaps in your document the word Sugarizer should be Sugar?

On Sun, Mar 31, 2024 at 10:24:40AM +0530, Sanjay Srikanth wrote:
> Hello, this is Sanjay Srikanth and I have made my project proposal for the
> following problem statement: Add an AI chatbot to the Chat Activity.
> 
> Here is the proposal attachment and I await your review and feedback. 
> 
> Thank you.
> 


> ___
> 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] Submission of Proposal and Video for GSoC Application

[James Cameron]

Hello Soham,

Hopefully someone will read your draft proposal.

For your interest, in the Sugar Labs guide for participating in Google
Summer of Code, we have this text;

"should not be posted to our sugar-devel@ mailing list as a Google Docs (a 
document can change after you send the link, a document can disappear, the 
export feature may be turned off, and we don't want to require our members to 
use Google Docs)."

Please read the remainder of the page to learn more.

https://github.com/sugarlabs/GSoC#want-to-work-with-us-

On Thu, Mar 28, 2024 at 07:46:40PM +0530, SOHAM SARODE wrote:
> Dear Sugar Labs Community,
> 
> I trust this message finds you in good spirits. I am reaching out to formally
> present my draft proposal for the Google Summer of Code (GSoC) program,
> specifically focusing on the Sugarizer project. Enclosed with this email is 
> the
> link to my draft proposal, which includes the completion of the Pawn tutorial
> along with short videos. These materials are available in the dedicated 
> channel
> for the GSoC project I am keenly interested in.
> 
> I kindly request members of the Sugar Devel mailing list to take a moment to
> review my draft proposal and offer your valuable feedback. Your insights and
> suggestions will significantly contribute to refining and enhancing my 
> proposal
> as I progress toward its finalization for the GSoC application.
> 
> Thank you for considering my proposal, and I eagerly anticipate your
> constructive feedback.
> 
> Best regards,
> Soham Sarode
> 
> [1]Proposal Link
> *
> 
> References:
> 
> [1] 
> https://docs.google.com/document/d/16v8GwYTv09d3RkTvMMd3SYb-LLilxoYIjVCbKJEU7aw/edit?usp=sharing

> ___
> 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] Proposal for Flatpak port project

[James Cameron]

I agree with Martín.  Porting from GTK 2 to GTK 3 is complex, and to
do it right requires building a GTK 2 environment so as to compare
behaviour before and after porting.  Porting from Python 2 to Python 3
is relatively straightforward by comparison.

On Thu, Mar 28, 2024 at 09:38:37AM -0400, Martin Abente wrote:
> Hi !
> 
> Thanks for sharing your proposal, I have read through it.
> 
> My recommendation is that you reconsider the activities you selected.
> Especially those that require ports to Python 3 and GTK 3.
> 
> The reason is simple; porting these activities to Python 3 and GTK 3 is a 
> whole
> project in itself. Note that porting activities to Python 3 and GTK 3 requires
> more than just writing the code, e.g., testing, reviews, releases, etc. That
> would take a significantly longer time (than a week, as per the proposal) for 
> a
> large activity such as TamTam.
> 
> Plus, you have to account for the time required to port these to Flatpak.
> 
> So, try to find activities that are already ported to Python 3 and GTK 3 and
> then analyze the project complexity to come up with a schedule that would fit
> in the GSoC duration.
> 
> Regards,
> Martín.
> 
> On Wed, Mar 27, 2024 at 5:26 PM Tech Shubham <[1]shubhamtiwari71...@gmail.com>
> wrote:
> 
> Hi everyone,
> I am attaching here my draft proposal for maintaining and porting Flatpak
> activities. Before finalizing it, I want to know your opinion on the
> selection of activities I've chosen to port. Please take a moment to 
> review
> the proposal and share your thoughts.
> Thank you for your time and input.
> ___
> Sugar-devel mailing list
> [2]Sugar-devel@lists.sugarlabs.org
> [3]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:shubhamtiwari71...@gmail.com
> [2] mailto:Sugar-devel@lists.sugarlabs.org
> [3] http://lists.sugarlabs.org/listinfo/sugar-devel

> ___
> 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 2024] Request for Proposal Review: Transition to GTK4 Exploration Project

[James Cameron]

The GTK3 toolkit is in the sugar-toolkit-gtk3 repository.

I would imagine a GTK4 toolkit may be required, or the gtk3 repository
may be conditionally compiled and renamed.  Which?

On Thu, Mar 28, 2024 at 11:52:47AM +, Ahmed Fatthi wrote:
> Hello,
> 
> I hope you're doing well. I've decided to switch my project focus from 
> "Porting
> 12 Activities to Flatpak" to "GTK4 Exploration." I believe this project aligns
> better with my skills and interests.
> 
> Could you please review my updated proposal for the GTK4 Exploration project?
> Your feedback would be greatly appreciated.
> 
> Thank you for your continued support.
> 
> Best regards,
> 
> Ahmed
> 


> ___
> 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 2024 : questions about wikipedia activity

[James Cameron]

The GSoC/Ideas-2024.md "Refactor the Wikipedia Activity to generate
plain-language summaries"
https://github.com/sugarlabs/GSoC/blob/master/Ideas-2024.md#refactor-the-wikipedia-activity-to-generate-plain-language-summaries

says "the Wikipedia activity is designed to help teachers extract
content from the Wikipedia in order to create lesson plans".

Actually, that feature set is implemented by the InfoSlicer activity.
https://github.com/sugarlabs/infoslicer

The Wikipedia activity is an offline viewer for Wikipedia pages.
https://github.com/sugarlabs/wikipedia-activity

It does not make sense to use the Wikipedia activity when online,
instead use the Browse activity, which is the web browser.

The workflow for teachers to use the Wikipedia activity is to run the
extraction process across the most popular articles, filter to remove
sensitive articles, and then generate a (very large) Sugar activity
bundle, which the students in a class can install.  It isn't used for
lesson plans, but as a general offline cache, especially for students
that have no internet while taking their class laptop home.  A very
special use case.

If the aim of the GSoC idea is to use AI to craft lesson plans from
Wikipedia content, then I suggest using the Browse activity instead.

On Wed, Mar 27, 2024 at 07:16:16PM +0100, Chihurumnaya Ibiam wrote:
> The Wikipedia activity isn't part of the activities that comes with Sugar, so
> you'll have to
> clone and run the activity yourself.
> 
> Our [1]contributing doc contains some helpful info.
> 
> --
> 
> Ibiam Chihurumnaya
> [2]ibiamchihurumn...@gmail.com
> 
> On Wed, Mar 27, 2024 at 7:04 PM Archit Agrawal <[3]architagrawal...@gmail.com>
> wrote:
> 
> Hi Walter,
> I set up the sugar env on VirtualBox, fedora OS. But I don't see Wikipedia
> activity in activity list.
> 
>
> [4]Mailtrack  Sender notified by  27/03/24, 10:59:55
>   [5]Mailtrack
> 
> *
> On Tue, Mar 26, 2024 at 4:00 PM Walter Bender <[6]walter.ben...@gmail.com>
> wrote:
> 
> On Tue, Mar 26, 2024 at 6:41 PM Ruxue Jin <[7]ruxueji...@gmail.com>
> wrote:
> 
> Hello, 
> 
> I am interested in wikipedia activities: [8]Refactor the Wikipedia
> Activity to generate plain-language summaries
> 
> But I did not see this activity in the web application. 
> 
> By web application, I assume you mean Sugarizer. The Wikipedia App is 
> a
> Python app written for the Sugar Desktop.
> 
> In this activity repo: [9]sugarlabs/wikipedia-activity 
> (github.com)
> , the last commit is 2015 and there are many websites returning 
> 404
> error. 
> 
> I don't imagine it has been updated in a long time. That is part of
> what motivates this project.
> 
> I wonder if there is an instruction on how to set up the
> environment and check the code. 
> 
> Please follow the instructions on how to set up the Sugar env.
> 
> Thank you!
> Ruxue
> ___
> Sugar-devel mailing list
> [10]Sugar-devel@lists.sugarlabs.org
> [11]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> Walter Bender
> Sugar Labs
> [12]https://www.sugarlabs.org
> [13]
> ___
> Sugar-devel mailing list
> [14]Sugar-devel@lists.sugarlabs.org
> [15]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> ___
> Sugar-devel mailing list
> [16]Sugar-devel@lists.sugarlabs.org
> [17]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] 
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#contributing
> [2] mailto:ibiamchihurumn...@gmail.com
> [3] mailto:architagrawal...@gmail.com
> [4] 
> https://mailtrack.io/?utm_source=gmail_medium=signature_campaign=signaturevirality11;
> [5] 
> https://mailtrack.io/?utm_source=gmail_medium=signature_campaign=signaturevirality11;
> [6] mailto:walter.ben...@gmail.com
> [7] mailto:ruxueji...@gmail.com
> [8] 
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2024.md#Refactor-the-Wikipedia-Activity-to-generate-plain-language-summaries
> [9] https://github.com/sugarlabs/wikipedia-activity
> [10] mailto:Sugar-devel@lists.sugarlabs.org
> [11] http://lists.sugarlabs.org/listinfo/sugar-devel
> [12] https://www.sugarlabs.org/
> [13] http://www.sugarlabs.org/
> [14] mailto:Sugar-devel@lists.sugarlabs.org
> [15] http://lists.sugarlabs.org/listinfo/sugar-devel
> [16] mailto:Sugar-devel@lists.sugarlabs.org
> [17] 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-2024 Proposal Review For "Sugar on Raspberry Pi" Project

[James Cameron]

Reviewed.  Looks good, thanks.

On Tue, Mar 26, 2024 at 02:53:09AM +0530, Anurag Singh wrote:
> Respected Mentors,
> This is my preliminary draft proposal for the "Sugar on RPi" project. I would
> appreciate it if you could review it and provide any necessary changes or
> insights. 
> Thank you.
> Regards
> Anurag singh



> ___
> 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] Seeking Insights on GSOC Project Proposal

[James Cameron]

On Mon, Mar 25, 2024 at 09:12:02PM +0530, Mukund Choudhary 21bcs055 wrote:
> Dear Mentors,
> 
> I hope you are doing well. My name is Mukund Choudhary, and I am a prospective
> GSOC student interested in participating in the program this year. I am
> particularly enthusiastic about contributing to adding an AI assistant to the
> Pippy Activity.
> 
> As the deadline for project proposal submissions approaches on March
> 18th,

Actually, it is 2nd April.

https://developers.google.com/open-source/gsoc/timeline

> [...] I am
> seeking your valuable insights and feedback on my project proposal. I have
> outlined my proposed project, titled "AI Assistant for the Pippy Activity". I
> believe that your expertise and experience could provide valuable guidance in
> refining and enhancing my proposal.

Your proposal shows experience in Sugarizer, but not Sugar.  You may
wish to adjust.

> Additionally, I wanted to mention that I will be providing you with an editor
> role in the project proposal document, which I have created in Google Docs.
> This will allow you to directly review and provide comments or suggestions on
> the proposal. I hope that this will facilitate our collaboration and enable 
> you
> to provide more detailed feedback.
> 
> I would greatly appreciate the opportunity to discuss my project proposal with
> you in more detail. Your feedback and suggestions would be instrumental in
> ensuring that my proposal aligns with the goals and expectations of the GSOC
> program and the Sugar Labs community.
> 
> Please let me know if you would be available for a brief discussion at your
> earliest convenience. I am flexible and can accommodate your schedule.
> Alternatively, if you prefer to provide feedback via email, I would be 
> grateful
> for any insights you could offer.
> 
> Thank you for considering my request. I look forward to hearing from you soon
> and potentially collaborating on this exciting project.
> 
> Warm regards,
> 
> Mukund Choudhary
> [1]21bcs...@smvdu.ac.in
> GitHub: hackorlyf
> 
> References:
> 
> [1] mailto:21bcs...@smvdu.ac.in


> ___
> 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] PROPOSAL SUBMISSION FOR ADDING AI CHAT BOT TO CHAT ACTIVITY

[James Cameron]

I'd also like it to work in a group of students sharing ad-hoc
wireless without internet connection.  That's a feature of Sugar.

On Thu, Mar 21, 2024 at 07:02:53PM +0100, Chihurumnaya Ibiam wrote:
> We're leaning towards using FOSS tools so a FOSS LLM would be preferable - 
> OpenAI isn't FOSS -.
> 
> "I plan on using a few prompting techniques to do this. I can provide some
> prompts also."
> 
> I don't understand what you plan to achieve with a few prompting techniques.
> 
> For the things you've mentioned about improving the UI, it sounds like you're
> yet to use Sugar and the chat activity,
> if that's the case then you should do that first.
> 
> --
> 
> Ibiam Chihurumnaya
> [1]ib...@sugarlabs.org
> 
> On Thu, Mar 21, 2024 at 4:25 PM Atiene Jonathan <[2]bemijonat...@gmail.com>
> wrote:
> 
> Hi Chigurumnaya, cc Walter, 
> 
> Thanks for the feedback,
> 
> I took the chat from the context of a personal chat and a group chat, 
> where
> multiple user can be involved in the chat with the bot, if that is
> beyond the scope, Rate Limiting and Queue is actually important for an
> ordered system in times of high traffic its possible to get a rate 
> limiting
> issue as open ai imposes this on every [3]client.
> 
> Feasibility of multiple bots for different age grades and group chat.
> you are right, after rethinking this i think it's over complex to follow
> this approach, one Bot with several prompts for the different age grade,
> and group chat, looks feasible its More scalable and easier to maintain.  
> i
> will also be using the set of age Range. (3-8)  (Ages 8 - 16)  (16 and
> above) we can further break this down with time.
> 
> I plan on using a few prompting techniques to do this  i can provide some
> prompts also.
> 
> [4]https://www.promptingguide.ai/techniques
> 
> - Ensure safe and appropriate interactions 
> - Balance discussion with Educational value
> 
> - Improve user interface. 
>   i will be providing a tiny mockup ui to improve the experience things we
> can work on include 
>  - Dark mode , 
>  - Chat bubbles
>  - Softer colors
>  - Introduce a more modern font,
> - I am not sure of the feasibility of a new icon tray
> -  Nice shadows for the input field.
> 
> - Optimize for performance
> involves implementing a queue system for ordered messages in group chat 
> 
> - Ensure security.
> Just as @Walter said if we do not need to retain any user data, and just
> need only the uploaded info then it's ok we can work with that, i insisted
> on saving the conversation so we can always have a context to look up to. 
> 
> If you agree with me on this,
> then I can continue to produce the final proposal.
> 
> Regards.
> Jonathan.
> 
> On Wed, Mar 20, 2024 at 4:43 PM Walter Bender <[5]walter.ben...@gmail.com>
> wrote:
> 
> To Ibiam's point, we need to be very careful in terms of ensuring
> privacy for our users (children) so we do not retain any user data
> (with the exception of anonymized project data that our users might
> upload to one of our servers).
> 
> On Wed, Mar 20, 2024 at 12:40 PM Chihurumnaya Ibiam <[6]
> ib...@sugarlabs.org> wrote:
> 
> Thanks for sharing!
> 
> "Here we will introduce multiple bots for each of the
> age range that will be determined by a simple fuzzy logic for
> determining the age range
> of the greater number of participants in call."
> 
> Multiple bots for each age range doesn't seem feasible, but I'm
> curious, what are the age ranges you'd
> like to implement it for and what would be the uniqueness of each?
> 
> Some deliverables are vague;
> 
> - Ensure safe and appropriate interactions
> - Balance discussion with Educational value
> - Improve user interface.
> - Optimize for performance
> - Ensure security.
> 
> It'll be great to know how you plan on implementing these.
> 
> Some of the things mentioned in Further Enhancement are also 
> vague.
> 
> "Chatbot Interaction Analytics Develop a dashboard to monitor
> chatbot interactions and user
> engagement." 
> 
> This is beyond the scope of the project idea.
> 
> Rate limiting isn't something that really fits into the idea as 
> the
> interactions with the chatbot would usually
> happen with one user, except they're collaborating and even then I
> still don't see why it's needed.
> 
> Hope this helps!
> 
> --
> 
> Ibiam Chihurumnaya
> [7]ib...@sugarlabs.org
>
> 
> On Tue, Mar 19, 2024 at 9:05 PM Atiene Jonathan <[8]
> 

Re: [Sugar-devel] Sugar Commander release checklist

[James Cameron]

Release, thanks!

On Sun, Mar 10, 2024 at 05:20:06PM -0500, James Simmons wrote:
> I did a simple update of this Activity to make it run under Python 3.
> 
> Checklist - maintainer
> 
> * check version of latest tarball release in 
> [1]download.sugarlabs.org/sources/
> sucrose/fructose/ or [2]download.sugarlabs.org/sources/honey/,
>    
>     No tarball release for this Activity.
> 
> * check for a release version git tag, e.g. v34,
>    
>     There were no Git tags seen for this Activity
> 
> *  correlate with activity_version metadata in activity/[3]activity.info,
> 
>     Updated to version 11.
> 
> *  look for commits after any of these, in either;
>         master branch of repository at sugarlabs,
>         any other branches,
>         any other forks,
>         orphaned repositories with the same bundle_id value, using GitHub or
> Google Search,
>         deprecated repositories at [4]git.sugarlabs.org,
> 
>     Nothing like this found.
> 
> * review and merge all pull requests,
> 
>     No other pull requests.
> 
> * apply all desired commits, making pull requests if review is needed,
> 
>     Done. I made a new branch for the PR for release notes.
> 
> * apply any [5]translate.sugarlabs.org changes, e.g. using a download script,
>     if there is a po/*.pot file, regenerate using python setup.py genpot,
> review the changes, and commit,
>     notify our translation-community manager @leonardcj if the POT file 
> changes
> contain new or changed strings,
>    
>     No translated strings were affected by this update.
> 
> * update the README.md file if necessary,
> 
>     Not needed. No changes in functionality.
> 
> * write release notes for the NEWS file, change the activity_version metadata
> in activity/[6]activity.info, commit, and git tag the version,
> 
>     Done
> 
> * update the activity documentation in the help-activity repository,
> 
>     Not needed. The Activity works the same as it always did.
> 
> * for activities that include a tarball release, or where Fedora or Debian
> packages may be made, create a tarball using python setup.py dist_source, and
> upload tarball to [7]download.sugarlabs.org using shell account,
> 
>     I have no such account. I don't do enough Activity development to justify
> having one.
> 
> * create bundle using python setup.py dist_xo, and test that it can be
> installed by Browse,
> 
>     I have not tested this.
> 
> * rebase any other maintained branches or pull requests, such as those for 
> past
> or future versions of Python, or past releases of Fedora, Ubuntu or libraries.
> 
>     No other pull requests.
> 
> * for Python 3 Activities, copy the bundle to ~activities-v4/bundles, remove
> any other old versions of the bundle from ~activities-v4/bundles, and trigger 
> a
> rebuild of the static site using rebuild-aslo command, verify if your bundle 
> is
> visible on [8]https://v4.activities.sugarlabs.org . For more information, it 
> is
> recommended to take a look at the Activities4 wiki page
> 
>    I don't think this is something I have the ability to do.
>   
> Thanks,
> 
> James Simmons
> 
> References:
> 
> [1] http://download.sugarlabs.org/sources/sucrose/fructose/
> [2] http://download.sugarlabs.org/sources/honey/
> [3] http://activity.info/
> [4] http://git.sugarlabs.org/
> [5] http://translate.sugarlabs.org/
> [6] http://activity.info/
> [7] http://download.sugarlabs.org/
> [8] https://v4.activities.sugarlabs.org/

> ___
> 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] Read Activity release checklist

[James Cameron]

Released, see notes below.

On Sun, Mar 10, 2024 at 04:52:05PM -0500, James Simmons wrote:
> I would like to release a new version of the Read Activity containing a bug 
> fix
> needed so the Activity can start under Fedora 39:
> 
> Checklist - maintainer
> 
> * check version of latest tarball release in 
> [1]download.sugarlabs.org/sources/
> sucrose/fructose/ or [2]download.sugarlabs.org/sources/honey/,
>    
>     Latest version is 123.
> 
> * check for a release version git tag, e.g. v34,
>    
>     There were no Git tags seen for this Activity

You're doing something wrong in that check.  There are tags.  GitHub
shows them.

> *  correlate with activity_version metadata in activity/[3]activity.info,
> 
>     Updated to version 124
> 
> *  look for commits after any of these, in either;
>         master branch of repository at sugarlabs,
>         any other branches,
>         any other forks,
>         orphaned repositories with the same bundle_id value, using GitHub or
> Google Search,
>         deprecated repositories at [4]git.sugarlabs.org,
> 
>     Nothing like this found.
> 
> * review and merge all pull requests,
> 
>     I looked at the one other pull request. It isn't clear to me what it's
> doing. I was created
>     back in 2020 and never applied.

Reviewed and applied.  Coding standards, not critical.  A few more
need changing, but that can wait for someone interested in doing so.

> * apply all desired commits, making pull requests if review is needed,
> 
>     Done. I made a new branch for the PR for release notes.
> 
> * apply any [5]translate.sugarlabs.org changes, e.g. using a download script,
>     if there is a po/*.pot file, regenerate using python setup.py genpot,
> review the changes, and commit,
>     notify our translation-community manager @leonardcj if the POT file 
> changes
> contain new or changed
>     strings,
>    
>     No translated strings were affected by this update.

There were translation updates for languages mg and te.  We have to
apply these, they aren't applied automatically any more.

> * update the README.md file if necessary,
> 
>     Not needed. No changes in functionality.
> 
> * write release notes for the NEWS file, change the activity_version metadata
> in activity/[6]activity.info, commit, and git tag the version,
> 
>     Done
> 
> * update the activity documentation in the help-activity repository,
> 
>     Not needed. The Activity works the same as it always did.
> 
> * for activities that include a tarball release, or where Fedora or Debian
> packages may be made, create a tarball using python setup.py dist_source, and
> upload tarball to [7]download.sugarlabs.org using shell account,
> 
>     I have no such account. I don't do enough Activity development to justify
> having one.

Done.

> * create bundle using python setup.py dist_xo, and test that it can be
> installed by Browse,
> 
>     I have not tested this.
> 
> * rebase any other maintained branches or pull requests, such as those for 
> past
> or future versions of Python, or past releases of Fedora, Ubuntu or libraries.
> 
>     The other pull request appears to be abandoned. It could be
> closed.

I hadn't abandoned it.  Nobody bothered to review my work.  ;-)

> * for Python 3 Activities, copy the bundle to ~activities-v4/bundles, remove
> any other old versions of the bundle from ~activities-v4/bundles, and trigger 
> a
> rebuild of the static site using rebuild-aslo command, verify if your bundle 
> is
> visible on [8]https://v4.activities.sugarlabs.org . For more information, it 
> is
> recommended to take a look at the Activities4 wiki page
> 
>    I don't think this is something I have the ability to do.

Done.

>   
> Thanks,
> 
> James Simmons
> 
> References:
> 
> [1] http://download.sugarlabs.org/sources/sucrose/fructose/
> [2] http://download.sugarlabs.org/sources/honey/
> [3] http://activity.info/
> [4] http://git.sugarlabs.org/
> [5] http://translate.sugarlabs.org/
> [6] http://activity.info/
> [7] http://download.sugarlabs.org/
> [8] https://v4.activities.sugarlabs.org/

> ___
> 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] Does Sugar on XO-1 support Python 3?

[James Cameron]

Um, I disagree.  The XO-1 distribution of OLPC OS is not based on
Fedora 18 because of the large number of activities only available for
Python 2.

It is based on Fedora 18 because we couldn't get Fedora 20 to work
reliably in time for production of XO-1.75 and XO-4, in turn because
we didn't have enough engineering resources applied to the problem.
We turned instead to further stabilising the software at the Fedora 18
release point, and that was our strategy until the NL3 and ED2 models,
which used stable Ubuntu releases.

The number of still working OLPC XO-1 laptops is too tiny now to
consider it other than a hobby or enthusiast persuit.  It is great
that you found one working, but that is becoming rare.

If you want to counter the software age-related problems, one of the
cute methods is to add a piggy-back Raspberry Pi Zero {,2} configured
as a USB network interface.  Applications such as Firefox or Chrome
can be launched from the Pi onto the X display of the XO-1.

On Thu, Mar 14, 2024 at 03:12:43PM -0500, James Simmons wrote:
> Ibiam,
> 
> I just noticed that SoaS is based on Fedora 34 and the XO-1 distribution is
> based on Fedora 18. My guess is that this is because of the large number of
> Activities only available for Python 2.
> 
> James Simmons
> 
> On Thu, Mar 14, 2024 at 10:09 AM Chihurumnaya Ibiam <[1]ib...@sugarlabs.org>
> wrote:
> 
> Is Python3 installed and working as expected for the XO1?
> 
> --
> 
> Ibiam Chihurumnaya
> [2]ib...@sugarlabs.org
>
> 
> On Thu, Mar 14, 2024 at 3:59 PM James Simmons <[3]nices...@gmail.com>
> wrote:
> 
> One of the tasks in the deployment checklist is to use Browse to
> install the updated Activity and see if it works. I decided to dig out
> my XO-1 and update it to the latest version of Sugar and use Gmail to
> send my .xo files to the laptop for installation. I discovered two
> things:
> 
> 1. The Browse Activity cannot log into Gmail because it disables
> cookies. The version of Browse I can run on Fedora does not have this
> problem.
> 
> 2. When I copy the .xo files from a USB drive to the Journal they
> install OK but don't start. No messages whatsoever in the Log 
> Activity,
> but empty files are created for messages.
> 
> It looks like you cannot get a version of Sugar using Python 3 for an
> XO-1 laptop.
> 
> Thanks,
> 
> James Simmons
> ___
> Sugar-devel mailing list
> [4]Sugar-devel@lists.sugarlabs.org
> [5]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:ib...@sugarlabs.org
> [2] mailto:ib...@sugarlabs.org
> [3] mailto:nices...@gmail.com
> [4] mailto:Sugar-devel@lists.sugarlabs.org
> [5] http://lists.sugarlabs.org/listinfo/sugar-devel

> ___
> 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] Does Sugar on XO-1 support Python 3?

[James Cameron]

OLPC OS for the XO-1 does not have Python 3 support for activities.

If I recall correctly, it isn't the lack of Python 3, but a lack of everything 
else, such as gobject and GTK, all the way down the stack to the kernel.

If you want to release a Python 2 activity as an update, there are branches in 
some of the repositories, and the old activities.sugarlabs.org

On Thu, Mar 14, 2024 at 09:59:29AM -0500, James Simmons wrote:
> One of the tasks in the deployment checklist is to use Browse to install the
> updated Activity and see if it works. I decided to dig out my XO-1 and update
> it to the latest version of Sugar and use Gmail to send my .xo files to the
> laptop for installation. I discovered two things:
> 
> 1. The Browse Activity cannot log into Gmail because it disables cookies. The
> version of Browse I can run on Fedora does not have this problem.
> 
> 2. When I copy the .xo files from a USB drive to the Journal they install OK
> but don't start. No messages whatsoever in the Log Activity, but empty files
> are created for messages.
> 
> It looks like you cannot get a version of Sugar using Python 3 for an XO-1
> laptop.
> 
> Thanks,
> 
> James Simmons

> ___
> 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] Get Books ready to release

[James Cameron]

G'day Archit,

See https://github.com/sugarlabs/GSoC?tab=readme-ov-file#how-to-talk-to-us-

On Sat, Mar 09, 2024 at 10:09:13PM -0700, Archit Agrawal wrote:
> Hi,
> This is Archit Agrawal. I am interested in contributing to the SugarLabs
> project. I came across this project through GSOC. What medium would be best to
> reach out to mentors. I was only able to find the mailing list and hence I 
> have
> subscribed to it.
> 
> [1]Mailtrack  Sender notified by  09/03/24, 22:06:51
>   [2]Mailtrack
> 
> *
> On Sat, Mar 9, 2024 at 9:04 PM James Cameron <[3]qu...@laptop.org> wrote:
> 
> On Sat, Mar 09, 2024 at 07:51:08PM -0600, James Simmons wrote:
> > * check for a release version git tag, e.g. v34,
> >    
> >     There are no Git tags for this Activity
> 
> I've just checked, there are tags, perhaps your repository didn't have
> them pulled.
> 
> [4]https://github.com/sugarlabs/get-books-activity/tags
> ___
> Sugar-devel mailing list
> [5]Sugar-devel@lists.sugarlabs.org
> [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] 
> https://mailtrack.io/?utm_source=gmail_medium=signature_campaign=signaturevirality11;
> [2] 
> https://mailtrack.io/?utm_source=gmail_medium=signature_campaign=signaturevirality11;
> [3] mailto:qu...@laptop.org
> [4] https://github.com/sugarlabs/get-books-activity/tags
> [5] mailto:Sugar-devel@lists.sugarlabs.org
> [6] 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] Get Books ready to release

[James Cameron]

On Sat, Mar 09, 2024 at 07:51:08PM -0600, James Simmons wrote:
> * check for a release version git tag, e.g. v34,
>    
>     There are no Git tags for this Activity

I've just checked, there are tags, perhaps your repository didn't have
them pulled.

https://github.com/sugarlabs/get-books-activity/tags
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Get Books ready to release

[James Cameron]

Thanks James.  I've done the remaining steps.  My reply in context below.

Hopefully I've done everything, let me know if I've missed something.

On Sat, Mar 09, 2024 at 07:51:08PM -0600, James Simmons wrote:
> Here is my checklist for Get Books Activity:
> 
> Checklist - maintainer
> 
> * check version of latest tarball release in 
> [1]download.sugarlabs.org/sources/
> sucrose/fructose/ or [2]download.sugarlabs.org/sources/honey/,
>    
>     Latest version is 19.
> 
> * check for a release version git tag, e.g. v34,
>    
>     There are no Git tags for this Activity

After the translations update (see below) I did "git tag v20" then
"git push --tags".

> *  correlate with activity_version metadata in activity/[3]activity.info,
> 
>     Updated to version 20
> 
> *  look for commits after any of these, in either;
>         master branch of repository at sugarlabs,
>         any other branches,
>         any other forks,
>         orphaned repositories with the same bundle_id value, using GitHub or
> Google Search,
>         deprecated repositories at [4]git.sugarlabs.org,
> 
>     Nothing like this found.
> 
> * review and merge all pull requests,
> 
>     I looked at the other pull requests. There were two that attempted to make
> the application\
>     work under Python 3. They ran into the same problems with feedparser.py 
> and
> Python 3 not having
>     sgmllib that I did. I fixed those problems by using a later version (but
> not current) version
>     of feedparser that included its own version of sgmllib.

I've closed these pull requests, thanks.

> * apply all desired commits, making pull requests if review is needed,
> 
>     Done
> 
> * apply any [5]translate.sugarlabs.org changes, e.g. using a download script,
>     if there is a po/*.pot file, regenerate using python setup.py genpot,
> review the changes, and commit,
>     notify our translation-community manager @leonardcj if the POT file 
> changes
> contain new or changed
>     strings,
>    
>     No translated strings were affected by this update.

Some new Swedish translated strings arrived between 19 and 20, so I've
pushed them to master.

https://github.com/sugarlabs/sugar-tools has an activity-translations
script that I used.

> * update the README.md file if necessary,
> 
>     Just did that. This required a second pull request as the first was 
> already
> done.

Thanks, merged.

> * write release notes for the NEWS file, change the activity_version metadata
> in activity/[6]activity.info, commit, and git tag the version,
> 
>     Done
> 
> * update the activity documentation in the help-activity repository,
> 
>     Not needed. The Activity works the same as it always did.
> 
> * for activities that include a tarball release, or where Fedora or Debian
> packages may be made, create a tarball using python setup.py dist_source, and
> upload tarball to [7]download.sugarlabs.org using shell account,
> 
>     I have no such account.

I did copy the tarball release to
sunjammer:/upload/sources/honey/GetBooks/ and you can see it at
https://download.sugarlabs.org/sources/honey/GetBooks/?C=M;O=D

> * create bundle using python setup.py dist_xo, and test that it can be
> installed by Browse,
> 
>     I have not tested this.

I did the bundle create, but I didn't test it can be installed.

I also uploaded to
https://people.sugarlabs.org/~quozl/?C=M;O=D

> * rebase any other maintained branches or pull requests, such as those for 
> past
> or future versions of Python, or past releases of Fedora, Ubuntu or libraries.
> 
>     The other pull requests appear to be abandoned. They could be closed.

They are closed.  There are some issues open, in case you'd like to
respond to those.

> * for Python 3 Activities, copy the bundle to ~activities-v4/bundles, remove
> any other old versions of the bundle from ~activities-v4/bundles, and trigger 
> a
> rebuild of the static site using rebuild-aslo command, verify if your bundle 
> is
> visible on [8]https://v4.activities.sugarlabs.org . For more information, it 
> is
> recommended to take a look at the Activities4 wiki page
> 
>    I don't think this is something I have the ability to do.

I did copy the bundle to sunjammer:/srv/activities-v4/bundles/ then
ran rebuild-aslo, using my account on sunjammer.  Let me know if you'd
like an account.

After that, the https://v4.activities.sugarlabs.org site does list
GetBooks 20.

https://v4.activities.sugarlabs.org/app/org.laptop.sugar.GetBooksActivity.html

> I will make similar lists for the Read Activity (minor bug fix), GetIABooks,
> and Sugar Commander when I have time.
> 
> Thanks.
> 
> James Simmons
> 
> On Sat, Mar 9, 2024 at 2:04 PM Jam

Re: [Sugar-devel] Get Books ready to release

[James Cameron]

Thanks.  I've merged.

Steps for releasing are at
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer

Skip any you feel are not helpful.

Tell us of any you can't or won't proceed with.

On Sat, Mar 09, 2024 at 10:20:19AM -0600, James Simmons wrote:
> I have a pull request for the Get Books Activity ready to review.
> 
> Feedbooks is going out of business, so only Internet Archive is supported. I
> investigated several other OPDS feeds but they all had issues. The Activity
> runs under Python 3 now.
> 
> I think this is ready to release.
> 
> James Simmons
> 

> ___
> 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] Progress on getting sugar-runner working again

[James Cameron]

That's great.  When you're happy with the changes, you can make a pull request.

On Sun, Mar 03, 2024 at 09:39:29AM -0600, James Simmons wrote:
> James,
> 
> I didn't understand the purpose in forking before but now I do. A new fork 
> with
> my changes in a branch is here:
> 
> [1]https://github.com/jdsimmons/sugar-runner/tree/python3
> 
> I updated the README with suggestions on how to test.
> 
> I just tried:
> 
> sugar-activity3 GetIABooksActivity.GetIABooksActivity
> 
> and it worked. I had no idea it would. I haven't worked on Sugar Activities
> since 2014. After I wrote E-Book Enlightenment I went down a rabbit hole where
> I prepared lots of books for archive,org and Project Gutenberg, wrote and self
> published a memoir of my youth among the Hare Krishnas, figured out how to use
> LaTeX to bring public domain books back into print and self published a bunch
> of them until Amazon put a stop to it, and even started a novel.
> 
> I would have stayed in that rabbit hole if a bright eight year old boy had not
> decided that he wanted an old computer running Linux I had intended to give to
> his older brothers.
> 
> As for why I still want to get sugar-runner working, it is because it gives me
> the whole Sugar environment. After I use Get IA Books to download books I need
> to check the books out in the Journal and make sure they got in there OK and
> are readable. Activities using collaboration really need the whole environment
> working and making screenshots that look like what the Activity looks like on
> an XO laptop is easy with sugar-runner.
> 
> Thanks again,
> 
> James Simmons
> 
> On Sat, Mar 2, 2024 at 11:45 PM James Cameron <[2]qu...@laptop.org> wrote:
> 
> On Sat, Mar 02, 2024 at 08:14:20PM -0600, James Simmons wrote:
> > [...]
> > If someone wants to try this out I could post a branch with my
> > changes to GitHub if I was given needed permissions to do so.
> >
> > For now, I'm stuck.
> 
> Fork the repository, push your branch to your fork, then create a pull
> request with details on how to try it out.
> 
> Also, I'm curious, what does Sugar Runner get you that running
> "sugar-activity3" doesn't get you?
> 
> References:
> 
> [1] https://github.com/jdsimmons/sugar-runner/tree/python3
> [2] mailto:qu...@laptop.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Some thoughts on GetBooks activity

[James Cameron]

Yes, I remember some of this from when I last maintained those activities.

I felt that activities that depended on external APIs become difficult to 
maintain.  ;-)

On Mon, Mar 04, 2024 at 01:46:44PM -0600, James Simmons wrote:
> Back in 2009 I wrote the Get IA Books activity which uses the Advanced Search
> service of the Internet Archive to search their catalog and makes it possible
> to download these books to the Journal and put some metadata in there as well.
> 
> Shortly after I finished this Sayamindu Dasgupta made a similar Activity that
> used OPDS to search book catalogs. Specifically he was interested in using 
> OPDS
> to search [1]https://www.feedbooks.com, which had an OPDS server that included
> public domain books. He also made it possible for the Activity user to add an
> entry for his own OPDS server, but you had to edit a text file using the
> Terminal activity to do it.
> 
> I have just fixed my own Activity to work with Python 3 and wanted to try
> fixing this one too. I've run into a few problems which makes me think this
> Activity might not be fixable.
> 
> 1. Feedbooks.com is going out of business very soon. It is possible that their
> OPDS server is already not working: [2]https://www.feedbooks.com/catalog/
> public_domain
> 2. There are other ODPS servers, but not for public domain titles: [3]http://
> opdshome.uo1.net/
> 3. The Internet Archive has an OPDS server but this Activity doesn't use it.
> Instead it adapted code from my GetIABooks activity. Apparently the IA OPDS
> server had issues when this was written.
> 3. The Activity makes use of code from [4]http://feedparser.org/.
> Unfortunately, the latest version of this cannot be contained in just one 
> file.
> The old version depends on sgmllib.py, which was included with Python 2 but 
> not
> with 3. Somebody found the code for this and ran it through a Python 2 to 3
> converter. I added this to the project.
> 4. I managed to convert enough code in feedparser.py and sgmllib.py to get the
> Activity to run without generating diagnostic messages. I have no idea if it 
> is
> actually working.
> 
> Thoughts?
> 
> James Simmons
> 
> References:
> 
> [1] https://www.feedbooks.com/
> [2] https://www.feedbooks.com/catalog/public_domain
> [3] http://opdshome.uo1.net/
> [4] http://feedparser.org/

> ___
> 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] Progress on getting sugar-runner working again

[James Cameron]

On Sat, Mar 02, 2024 at 08:14:20PM -0600, James Simmons wrote:
> [...]
> If someone wants to try this out I could post a branch with my
> changes to GitHub if I was given needed permissions to do so.
> 
> For now, I'm stuck.

Fork the repository, push your branch to your fork, then create a pull
request with details on how to try it out.

Also, I'm curious, what does Sugar Runner get you that running
"sugar-activity3" doesn't get you?
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Willing to Contribute through GSoC

[James Cameron]

That's fairly difficult to predict.  Nothing about your skill map has
anything unique to open source.

I suggest you pick Sugarizer, Sugar, or Music Blocks.  Identify the
software license in whatever you have picked.

Then read the license, and if English is not your first language read
a translation of the license.  That will give you an idea of the scope
of work that we consider "open source".

Next, work towards writing, testing, and debugging open source
software, see http://www.catb.org/~esr/faqs/hacker-howto.html "Status
in the Hacker Culture".

For Sugar, which is based on Python, the document we maintain as
guidance to contributing is at
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md

Other software may have other guidance.

On Thu, Feb 22, 2024 at 10:57:46AM +0530, Vinay Tambey wrote:
> Thank you for the clarification. 
> 
> How do I start contributing to the Sugar Labs software as this is my 
> first-time
> to open-source ?
> 
> On Thu, Feb 22, 2024, 12:50 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Of the Sugar Labs software, nothing uses Java, Sugarizer uses HTML, CSS 
> and
> JavaScript, and Sugar uses Python.  I'm not sure if anything uses MERN.
> 
> Open source contribution is that your new code is written by you and you
> either assign copyright during commit, or you retain copyright and give it
> an open source license before we can accept it.
> 
> Welcome.
> 
> On Wed, Feb 21, 2024 at 10:49:56PM +0530, Vinay Tambey wrote:
> > Hi, to all the mentors and contributors.
> > I am Vinay Tambey, a Software Engineering student, preparing for GSoC
> 2024 to
> > gain professional real-world projects experience.
> > I am skilled in Java, front-end development (HTML, CSS, Bootstrap,
> JavaScript &
> > React), Python (basic) and currently learning MERN tech-stack.
> > I am here to start open-source contribution to this platform, therefore,
> please
> > guide me.
> 
> > ___
> > Sugar-devel mailing list
> > [2]Sugar-devel@lists.sugarlabs.org
> > [3]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] mailto:Sugar-devel@lists.sugarlabs.org
> [3] 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] Willing to Contribute through GSoC

[James Cameron]

Of the Sugar Labs software, nothing uses Java, Sugarizer uses HTML, CSS and 
JavaScript, and Sugar uses Python.  I'm not sure if anything uses MERN.

Open source contribution is that your new code is written by you and you either 
assign copyright during commit, or you retain copyright and give it an open 
source license before we can accept it.

Welcome.

On Wed, Feb 21, 2024 at 10:49:56PM +0530, Vinay Tambey wrote:
> Hi, to all the mentors and contributors.
> I am Vinay Tambey, a Software Engineering student, preparing for GSoC 2024 to
> gain professional real-world projects experience.
> I am skilled in Java, front-end development (HTML, CSS, Bootstrap, JavaScript 
> &
> React), Python (basic) and currently learning MERN tech-stack.
> I am here to start open-source contribution to this platform, therefore, 
> please
> guide me.

> ___
> 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] Advice needed on sugar-runner

[James Cameron]

I'll speculate.  Perhaps something changed in how GObject introspection 
packages are built and installed between the time that sugar-runner and 
sugar-toolkit-gtk3 were both supported, and the time now.  If so, then commits 
that change Makefile.am in sugar-toolkit-gtk3 may explain.

To not speculate, use strace -f on the sugar-toolkit-gtk3 build steps to find 
out when and why the SugarExt typelib is installed, figure out what source file 
is responsible, then deduce how to make similar effect on sugar-runner.

Hope that helps!

On Mon, Feb 19, 2024 at 04:50:44PM -0600, James Simmons wrote:
> James,
> 
> I am a novice with Make. I did look at the Make files for sugar-runner and I
> found that Makefile.in had some lines reported as Bad directive:
> 
> @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/
> libsugarrunner_la-sugar-runner-window.Plo@am__quote@ # am--include-marker
> 
> @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/
> libsugarrunner_la-sugar-runner.Plo@am__quote@ # am--include-marker
> 
> $(am__depfiles_remade):
> 
> @$(MKDIR_P) $(@D)
> 
> @echo '# dummy' >$@-t && $(am__mv) $@-t $@
> 
> am--depfiles: $(am__depfiles_remade)
> 
> .c.o:
> 
> @am__fastdepCC_TRUE@ $(AM_V_CC)$(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo 
> -c -o $@ $<
> 
> @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
> 
> @AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='$<' object='$@' libtool=no
> @AMDEPBACKSLASH@
> 
> @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
> @AMDEPBACKSLASH@
> 
> @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(COMPILE) -c -o $@ $<
> 
> .c.obj:
> 
> @am__fastdepCC_TRUE@ $(AM_V_CC)$(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo 
> -c -o $@ `$(CYGPATH_W) '$<'`
> 
> @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
> 
> @AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='$<' object='$@' libtool=no
> @AMDEPBACKSLASH@
> 
> @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
> @AMDEPBACKSLASH@
> 
> @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(COMPILE) -c -o $@ `$(CYGPATH_W) 
> '$
> <'`
> 
> The ones with red underlines are the ones. The generated Makefile does not
> report any errors.
> 
> I'm going to try generating a Makefile for sugar-toolkit-gtk3 and see if that
> suggests anything.
> 
> Thanks.
> 
> James Simmons
> 
> On Mon, Feb 19, 2024 at 1:42 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Make sure the typelib has been installed correctly.  Perhaps the install
> steps are also bit rot.
> 
> Compare the steps against the SugarExt typelib installed by the
> sugar-toolkit-gtk3 package.
> 
> In particular, I seem to recall an introspection scanner step is required,
> but not sure if it is part of "make install" or if it fails if the tool is
> not installed.
> 
> On Mon, Feb 19, 2024 at 09:47:36AM -0600, James Simmons wrote:
> > I've been preparing an old computer I just replaced as a gift for a
> bright
> > eight year old boy and his older brother. It will run Fedora 39. In
> addition to
> > the XFCE environment I want to give him a Sugar environment with
> Activities.
> >
> > In the process of setting this up I discovered that some of the
> Activities I
> > wrote years ago have succumbed to bit rot and needed updating. I was 
> able
> to do
> > this, but I was disappointed to find that I could not use sugar-runner 
> to
> run
> > the Sugar environment in a window because it had not been maintained.
> >
> > I thought I'd take a stab at getting sugar-runner working. I checked out
> the
> > project, installed all the dependencies autogen.sh asked for, updated 
> the
> > scripts to use python3, then ran what looked to be a successful make and
> sudo
> > make install. Then I tried to run
> >
> > sugar-runner
> >
> > and I got these Python errors:
> >
> > jamessimmons@unknownF4390913EB01:~$ sugar-runner
> > Traceback (most recent call last):
> >   File "/usr/local/bin/sugar-runner", line 28, in 
> >     gi.require_version('SugarRunner', '1.0')
> >   File "/usr/lib64/python3.12/site-packages/gi/__init__.py", line 126, 
> in
> > require_version
> >     raise ValueError('Namespace %s not available' % namespace)
> > ValueError: Namespace SugarRunner not available
> >
> > At this point I'm stuck. If any of you have any suggestions on how to
> pro

Re: [Sugar-devel] Advice needed on sugar-runner

[James Cameron]

Make sure the typelib has been installed correctly.  Perhaps the install steps 
are also bit rot.

Compare the steps against the SugarExt typelib installed by the 
sugar-toolkit-gtk3 package.

In particular, I seem to recall an introspection scanner step is required, but 
not sure if it is part of "make install" or if it fails if the tool is not 
installed.

On Mon, Feb 19, 2024 at 09:47:36AM -0600, James Simmons wrote:
> I've been preparing an old computer I just replaced as a gift for a bright
> eight year old boy and his older brother. It will run Fedora 39. In addition 
> to
> the XFCE environment I want to give him a Sugar environment with Activities.
> 
> In the process of setting this up I discovered that some of the Activities I
> wrote years ago have succumbed to bit rot and needed updating. I was able to 
> do
> this, but I was disappointed to find that I could not use sugar-runner to run
> the Sugar environment in a window because it had not been maintained.
> 
> I thought I'd take a stab at getting sugar-runner working. I checked out the
> project, installed all the dependencies autogen.sh asked for, updated the
> scripts to use python3, then ran what looked to be a successful make and sudo
> make install. Then I tried to run
> 
> sugar-runner
> 
> and I got these Python errors:
> 
> jamessimmons@unknownF4390913EB01:~$ sugar-runner
> Traceback (most recent call last):
>   File "/usr/local/bin/sugar-runner", line 28, in 
>     gi.require_version('SugarRunner', '1.0')
>   File "/usr/lib64/python3.12/site-packages/gi/__init__.py", line 126, in
> require_version
>     raise ValueError('Namespace %s not available' % namespace)
> ValueError: Namespace SugarRunner not available
> 
> At this point I'm stuck. If any of you have any suggestions on how to proceed
> I'd love to hear them.
> 
> Thanks,
> 
> James Simmons
> 

> ___
> 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] I think I need push access in GitHub for some Sugar Activities

[James Cameron]

Thanks.

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

On Fri, Feb 16, 2024 at 11:44:47PM -0600, James Simmons wrote:
> It turned out to be fairly simple to fix the Read Activity. It was complaining
> that it had no MICRO_VERSION attribute in the EvinceDocument object, so I just
> removed it from the _validate_min_version() method in evinceadapter.py:
> 
> def update_toc(self, activity):
> 
> if self._validate_min_version(3, 5):
> 
> # check version because does not work and crash with older evince
> 
> doc = self._model.get_document()
> 
> if not doc.has_document_links():
> 
> logging.error('The pdf file does not have a index')
> 
> return False
> 
> else:
> 
> self._job_links = EvinceView.JobLinks.new(document=doc)
> 
> self._job_links.connect('finished', self.__index_loaded_cb,
> 
> activity)
> 
> EvinceView.Job.scheduler_push_job(
> 
> self._job_links,
> 
> EvinceView.JobPriority.PRIORITY_NONE)
> 
> return True
> 
> else:
> 
> return False
> 
> def handle_link(self, link):
> 
> self._view.handle_link(link)
> 
> def _validate_min_version(self, major, minor):
> 
> """
> 
> Check if Evince version is at major or equal than the requested
> 
> """
> 
> evince_version = [EvinceDocument.MAJOR_VERSION,
> 
> EvinceDocument.MINOR_VERSION]
> 
> return evince_version >= [major, minor]
> 
> Now it works.
> 
> I was getting the same error from the version of Read Activity that shipped
> with Fedora 39.
> 
> I made a pull request for Get IA Books. It looks like I can do the merge
> myself. Not sure of what the procedure is to get the revised Activity
> published.
> 
> James Simmons
> 
> On Fri, Feb 16, 2024 at 5:47 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Thanks.  What about the activity provided by Fedora 39?
> 
> On Fri, Feb 16, 2024 at 05:28:35PM -0600, James Simmons wrote:
> > I just confirmed that the master branch of the Read Activity has this
> problem
> > with Evince when running on Fedora 39:
> >
> > Traceback (most recent call last):
> >   File "/usr/bin/sugar-activity3", line 5, in 
> >     activityinstance.main()
> >   File "/usr/lib/python3.12/site-packages/sugar3/activity/
> activityinstance.py",
> > line 230, in main
> >     instance = create_activity_instance(activity_constructor,
> activity_handle)
> >                
> ^^
> ^
> >   File "/usr/lib/python3.12/site-packages/sugar3/activity/
> activityinstance.py",
> > line 59, in create_activity_instance
> >     activity = constructor(handle)
> >                ^^^
> >   File "/home/jamessimmons/git/read-activity/readactivity.py", line 374,
> in
> > __init__
> >     self.read_file(self._jobject.file_path)
> >   File "/home/jamessimmons/git/read-activity/readactivity.py", line 747,
> in
> > read_file
> >     self._load_document('file://' + tempfile)
> >   File "/home/jamessimmons/git/read-activity/readactivity.py", line 
> 1054,
> in
> > _load_document
> >     self._update_toc()
> >   File "/home/jamessimmons/git/read-activity/readactivity.py", line 627,
> in
> > _update_toc
> >     if self._view.update_toc(self):
> >        ^^^
> >   File "/home/jamessimmons/git/read-activity/evinceadapter.py", line 
> 275,
> in
> > update_toc
> >     if self._validate_min_version(3, 5, 92):
> >        
> >   File "/home/jamessimmons/git/read-activity/evinceadapter.py", line 
> 301,
> in
> > _validate_min_version
> >     EvinceDocument.MICRO_VERSION]
> >     
> >   File "/usr/lib64/python3.12/site-packages/gi/module.py", line 126, in
> > __getattr__
> >     raise AttributeError("%r object has no attribute %r" % (
> > AttributeError: 'gi.repository.EvinceDocument' object has no attribute
> > 'MICRO_VERSION'. Did you mean: 'MINOR_VERSION'?
> > Exited with status 1, pid 106639 activity_id
> > 37db76336c5474c61078f525c28c1f9de48fab9a
> >
> > James Simmons
> >
> > On Fri, Feb 16, 2024 at 4:09 PM James 

Re: [Sugar-devel] I think I need push access in GitHub for some Sugar Activities

[James Cameron]

Thanks.  What about the activity provided by Fedora 39?

On Fri, Feb 16, 2024 at 05:28:35PM -0600, James Simmons wrote:
> I just confirmed that the master branch of the Read Activity has this problem
> with Evince when running on Fedora 39:
> 
> Traceback (most recent call last):
>   File "/usr/bin/sugar-activity3", line 5, in 
>     activityinstance.main()
>   File 
> "/usr/lib/python3.12/site-packages/sugar3/activity/activityinstance.py",
> line 230, in main
>     instance = create_activity_instance(activity_constructor, activity_handle)
>                ^^^
>   File 
> "/usr/lib/python3.12/site-packages/sugar3/activity/activityinstance.py",
> line 59, in create_activity_instance
>     activity = constructor(handle)
>                ^^^
>   File "/home/jamessimmons/git/read-activity/readactivity.py", line 374, in
> __init__
>     self.read_file(self._jobject.file_path)
>   File "/home/jamessimmons/git/read-activity/readactivity.py", line 747, in
> read_file
>     self._load_document('file://' + tempfile)
>   File "/home/jamessimmons/git/read-activity/readactivity.py", line 1054, in
> _load_document
>     self._update_toc()
>   File "/home/jamessimmons/git/read-activity/readactivity.py", line 627, in
> _update_toc
>     if self._view.update_toc(self):
>        ^^^
>   File "/home/jamessimmons/git/read-activity/evinceadapter.py", line 275, in
> update_toc
>     if self._validate_min_version(3, 5, 92):
>        
>   File "/home/jamessimmons/git/read-activity/evinceadapter.py", line 301, in
> _validate_min_version
>     EvinceDocument.MICRO_VERSION]
>     
>   File "/usr/lib64/python3.12/site-packages/gi/module.py", line 126, in
> __getattr__
>     raise AttributeError("%r object has no attribute %r" % (
> AttributeError: 'gi.repository.EvinceDocument' object has no attribute
> 'MICRO_VERSION'. Did you mean: 'MINOR_VERSION'?
> Exited with status 1, pid 106639 activity_id
> 37db76336c5474c61078f525c28c1f9de48fab9a
> 
> James Simmons
> 
> On Fri, Feb 16, 2024 at 4:09 PM James Simmons <[1]nices...@gmail.com> wrote:
> 
> James,
> 
> I'm using Fedora 39, a fresh install on a computer I just got and an older
> one I'm giving away. I'm using the version of Read that ships with Fedora.
> I just checked out the master branch of Read from Git and could run a
> python 3 setup.py dev on it to see if that version has the problem. I 
> won't
> be able to do that right away, but when I do I'll let you know if it 
> works.
> 
> James Simmons 
> 
> On Fri, Feb 16, 2024 at 3:42 PM James Cameron <[2]qu...@laptop.org> wrote:
> 
> That's surprising.  Thought we fixed that.
> 
> What Linux distribution and release are you doing this on?
> 
> On Fri, Feb 16, 2024 at 02:23:11PM -0600, James Simmons wrote:
> > James,
> >
> > I don't want to use Evince as part of Get IA Books. It is the Read
> Activity
> > itself that has a problem.
> >
> > When I tested opening books from the Journal the Read Activity would
> not start.
> > I thought the problem might be in the way Get IA Books was adding
> books to the
> > Journal, so as a sanity check I used the Browse activity to download
> some PDFs
> > to the Journal and also downloaded one EPUB. The Read Activity 
> opened
> the EPUB
> > just fine but not the PDFs. There was a stack trace (copied to an
> earlier
> > email) that made it look like the code Evince needs to interface 
> with
> Python
> > has changed. It was complaining about an Evince micro version 
> number.
> That was
> > the thing I wanted to look at in the Read Activity.
> >
> > I'll probably send an email to the wider group explaining the issue.
> >
> > Thanks.
> >
> > James Simmons
> >
> > On Fri, Feb 16, 2024 at 2:01 PM James Cameron 
> <[1][3]qu...@laptop.org
> > wrote:
> >
> >     There's also VScode and GitHub desktop if you want to try other
> >     methods.  It is difficult to keep up with GitHub's security
> posture
> >     lately.
> >
> >     The Read activity has the integration wi

Re: [Sugar-devel] CONTRIBUTOR INTRODUCTION

[James Cameron]

Welcome.

If you wish to use your MERN stack experience, then contribute to Music Blocks 
and Sugarizer.

If you wish to learn Python, GTK, and C, then contribute to the Sugar software.

Hope that helps!  See also the sugar-docs repository for advice.

On Mon, Jan 08, 2024 at 10:57:33AM +0530, Arush Bhatnagar wrote:
> Hello,
> my name is Arush and I am a second year student at IIT Delhi. I have recently
> started my opensource journey and really resonated well with the Sugarlabs
> codebase on Github and would love to contribute. I have reached in 
> intermediate
> level in MERN stack and learning something new everyday. I would really
> appreciate if you can guide me how to contribute/ good first issues to start 
> my
> journey here.
> 
> Thanks a lot

> ___
> 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] [ASLOv4] [RELEASE] Stick Hero - 8

[James Cameron]

This did not work.  The info page still lists version 7.

Also, the release date is not shown.
https://github.com/sugarlabs/aslo-v4/issues/78

On Sun, Sep 17, 2023 at 01:07:03PM -0400, activities...@sugarlabs.org wrote:
> Stick Hero-8 has been released
> 
> Version: 8
> Bundle ID: org.sugarlabs.stickhero
> Release time: 2023-09-17 11:21:58
> 
> You can download the latest release of this activity here:
>   - Info: https://v4.activities.sugarlabs.org/app/org.sugarlabs.stickhero.html
>   - Download: https://v4.activities.sugarlabs.org/bundles/StickHero-8.xo
> 
> 
> 
> NEW IN THIS VERSION
> ---
> 
> * Update Sugargame to fix arrow key not working (Riya Jain)
> * Bug Fix for the perfect Score (Riya Jain)
> * Corrected a comment (Riya Jain)
> * Bug Fix in Fruit score (Riya Jain)
> 
> 
> 
> If you have questions about this review, please answer to this e-mail
> or join #sugar:matrix.org or #sugar on irc.libera.chat
> 
> --
> Sugar Activity Library
> https://v4.activities.sugarlabs.org
> ___
> 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] Summary of 17.08 meeting with mentors

[James Cameron]

On Sat, Aug 19, 2023 at 10:04:22PM +0300, Dimitris20Cen wrote:
> SSH Connection for Testing
> - Ibiam suggested setting up an SSH connection between the host and
> the VM (using rsync or scp) to streamline the process of testing
> activities.

I agree.  Aim to reduce the time between editor save and activity test
to under a second.  Saving time can be easily justified once you
measure how many iterations you consume.  Developing from inside Sugar
is very unusual.

Some methods that I use;

1.  a keyed access via SSH, so no password prompts,

2.  run screen(1) inside Terminal, so commands can be typed on either
the target system or my development system,

3.  write a shell script that transmits the activity directory once,
then uses inotifywait -e close_write to detect when editor save
happens, so that transmit happens automatically,

4.  or use an editor with file access over SSH feature,

5.  or use a filesystem sharing such as sshfs, or nfs,

6.  add a temporary restarter to the activity class, triggered by
editor macro and the transmit script above, for example from my
fedora18 branch of the Record activity,

# testing restarter
def restarter():
if os.stat('go').st_ctime != ct:
self.close()
os.execv('/usr/bin/sugar-activity3', ['sugar-activity3'])
logger.error('== restarted ==')
return False
return True
try:
ct = os.stat('go').st_ctime
glib.timeout_add(233, restarter)
except:
pass

(this works by recording the creation time of a marker file, then
watching for a change to the time, then restarting the activity.)

7.  use xdotool to send keystrokes and mouse actions to the activity,
to bring it to the test case being developed for,

8.  use IDE or editor "compile" command to copy files and remote start
the activity.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Summary of 08.08 meeting with mentors

[James Cameron]

On Sat, Aug 12, 2023 at 04:33:00PM +0200, Dimitris20Cen wrote:
> Text Dungeon:
> 
> -   Licensing concerns:
> 
> -   As text dungeon is an existing activity, its licensing process is
> intricate.

Actually, the license is correctly defined as GPLv2+ in the metadata, the 
COPYING file is properly present, and two of the three Python source files have 
the correct license declaration with valid copyrights.  There's no problem with 
licensing of the existing activity, as at f7f53e2 ("Deanglify links to 
help.sugarlabs.org") on the master branch.

> -   Apart from licensing issues, the project is ready for release, if no 
> other issues come up.

What you are referring to here is your wholesale replacement for the activity, 
which is in the pull request yet to be merged.

I'd like wider consultation on this.  Would other developers please review the 
pull request and comments and give their opinion?  The key issue is that the 
entire source code is removed and replaced; which we would normally handle by 
adding a new activity repository with the new source code, with a new activity 
name.

https://github.com/sugarlabs/textdungeon/pull/14

Also, the existing issues have not been specifically addressed; presumably they 
are all fixed?
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fwd: Download of Trisquel On A Sugar Toast x86

[James Cameron]

https://archive.org/details/trisquel-sugar_9.0.1_i686

Otherwise question best put to Trisquel people.

On Mon, Jun 19, 2023 at 03:58:05PM -0400, Walter Bender wrote:
> Anyone have an old image kicking around?
> 
> -- Forwarded message -
> From: Ivan Zorzi <[1]ivanzo...@gmail.com>
> Date: Mon, Jun 19, 2023, 10:21 AM
> Subject: Download of Trisquel On A Sugar Toast x86
> To: <[2]wal...@sugarlabs.org>
> 
> Hello,
> hope you can help me. 
> Recently I downloaded ISO image of Trisquel sugar v. 9.0.2 i686. On the
> following page there is direct link for download:
> [3]https://wiki.sugarlabs.org/go/Trisquel_On_A_Sugar_Toast
> 
> Problem is that the link ([4]http://us.archive.trisquel.info/iso/
> trisquel-sugar_9.0.2_i686.iso) is no more valid. I think they suppressed
> support to x86. 
> Is there any chance to download again the version? I lost the live usb
> drive... 
> I need it for my daugther, x86 version works just well on an old netbook.
> Thank you in advance. 
> 
> Ivan Zorzi
> 
> References:
> 
> [1] mailto:ivanzo...@gmail.com
> [2] mailto:wal...@sugarlabs.org
> [3] https://wiki.sugarlabs.org/go/Trisquel_On_A_Sugar_Toast
> [4] http://us.archive.trisquel.info/iso/trisquel-sugar_9.0.2_i686.iso

> ___
> 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] Regarding the Sugar on Raspberry Pi project

[James Cameron]

G'day Simrann,

I'll reply in context below, please scroll down.

You wrote:
> While performing the testing on Sugar platform, almost all the
> activities 'failed to load' and were having erratic
> behavior. However, when I restarted Sugar, some of them started
> working fine, but after sometime again that erratic behavior showed
> up.

Yes, you may wish to investigate this.

When the shell starts an activity, a timer is initiated.  If the
activity has not started when the timer expires, the shell declares
"failed to start".  An activity that is slow to start may yet appear
after this message.

Raspberry Pi can be very slow, depending on the performance
(i.e. price) of the microSD or SD card being used.  You can measure
performance using "sudo apt install pv" and "sudo pv /dev/mmcblk0 >
/dev/null".  My test system, a Raspberry Pi Model B+ with an old 32GB
SD card, shows 20 MiB/s.

On first start, GStreamer populates a
.cache/gstreamer-1.0/registry.armv7l.bin file, Python must load all
modules, and Calculate import of matplotlib iterates over the
available styles.  All this takes time, and may cause the shell to
timeout and report "failed to start".

Graphics updates can also be very slow.  During activity launch a
pulsing icon in the shell process competes with the starting of the
activity.  Simultaneous processes making demands of the operating
system and hardware cause mutual slowdown.  You can see this using
top(1) over ssh(1).

sugar:src/jarabe/view/launcher.py sets a default launcher interval of
100 milliseconds.  On particularly slow systems we have set this to
500 milliseconds using gsettings.  You might try that, and if it fixes
the problem then you know it is the pulsing icon to blame.

```
gsettings set org.sugarlabs.desktop launcher-interval 1000
```

The pulsing icon should look much slower.  Perhaps Sugar should detect
Raspberry Pi and set it lower by default.

You can look through .sugar/default/logs for previous sessions, using
stat(1) to compare file birth (activity start), modify (last output),
and change (activity stop).  This may show you that some activities
did actually start later, but were not visible because you had gone on
to start something else.

> Also, I did try installing other activities by using the following
> command and had also listed the error in my testing report shared
> earlier with you: 
>
> sudo apt install sugar-{abacus,
> [...]

That command has been removed from my instructions.  It was out of
date.  Therefore the error is of no concern.

> As far as your second point is concerned, by Browse -> Activities
> (the library) you mean that installing activities via the Sugar
> Store ([1] https://activities.sugarlabs.org/en-US/sugar/) right? I
> will try that as well going further.

No, that's for Python 2 activities.  Debian, Ubuntu, Fedora, and
Raspberry Pi OS no longer provide Python 2.

For Python 3 activities the library is linked from Browse default page
to https://v4.activities.sugarlabs.org

The library is much smaller, because many activities have not been
released since the library was opened.

> I have also shared my GSoC proposal on mail and sugar-devel mailing
> list, I would request your suggestions and valuable feedback for
> improving the same.

That's really up to your mentors.

> Thanks a lot
> Simrann Arora
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Draft Proposal - improve & maintain 12 sugar activities

[James Cameron]

No worries.  I'm not a mentor this year, so your proposal is not
something I'll advise on.  My feedback was about Simulate, and the
normal workflow of the organisation.

On Sun, Apr 02, 2023 at 01:06:38PM +0530, Spandan Barve wrote:
> Thanks for the reply quozl, I understand now and this will also help me when
> porting simulate to python3 which is also a part of my proposal, I'll also
> specify sugargame in my proposal, thanks.
> 
> On Sat, Apr 1, 2023 at 4:54 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> On Sat, Apr 01, 2023 at 04:21:59PM +0530, Spandan Barve wrote:
> > Thanks for the feedback Ibiam.
> > [...]
> > > Simulate activity sometimes crashes Sugar, what do you mean by 
> crashing
> > Sugar?
> > I was not able to reproduce it but I do have the error saved. by
> > crash, I mean that the activity stops responding completely,
> > including the stop button and pressing CTRL+Q, I had to go back to
> > the journal and then remove the activity, after that I got an error
> > in the terminal. 
> > here is the error : [2]https://pastebin.com/1RcTvYHc 
> 
> It's a bug.
> 
> The error showed Python 2.7.  Simulate is yet to be ported to Python
> 3.  The traceback can be ignored until that port is done.
> 
> Simulate also needs a port to later Sugargame.  During the port of
> Sugargame a complete review of the event loop should be done, as
> Sugargame changed substantially.
> 
> Simulate contains many inner event loops, with calls to wait, update,
> and tick, yet without checking for the stop button or Control/Q.
> That's probably the bug you saw.
> 
> Simulate also uses an unconventional exit method.
> 
> The Sugargame sample code shows how to do it instead.
> 
> Simulate window can also vanish but the system process persist, which
> was first reported in 2018.
> 
> [3]https://github.com/devAbnull/simulate_sugargame/issues/1
> 
> I could not tell if you used git HEAD or the latest release of
> Simulate, which predates git HEAD by some years.
> 
> [4]http://activities.sugarlabs.org/en-US/sugar/addon/4778
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] https://pastebin.com/1RcTvYHc
> [3] https://github.com/devAbnull/simulate_sugargame/issues/1
> [4] http://activities.sugarlabs.org/en-US/sugar/addon/4778
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Draft Proposal - improve & maintain 12 sugar activities

[James Cameron]

On Sat, Apr 01, 2023 at 04:21:59PM +0530, Spandan Barve wrote:
> Thanks for the feedback Ibiam.
> [...]
> > Simulate activity sometimes crashes Sugar, what do you mean by crashing
> Sugar?
> I was not able to reproduce it but I do have the error saved. by
> crash, I mean that the activity stops responding completely,
> including the stop button and pressing CTRL+Q, I had to go back to
> the journal and then remove the activity, after that I got an error
> in the terminal. 
> here is the error : https://pastebin.com/1RcTvYHc 

It's a bug.

The error showed Python 2.7.  Simulate is yet to be ported to Python
3.  The traceback can be ignored until that port is done.

Simulate also needs a port to later Sugargame.  During the port of
Sugargame a complete review of the event loop should be done, as
Sugargame changed substantially.

Simulate contains many inner event loops, with calls to wait, update,
and tick, yet without checking for the stop button or Control/Q.
That's probably the bug you saw.

Simulate also uses an unconventional exit method.

The Sugargame sample code shows how to do it instead.

Simulate window can also vanish but the system process persist, which
was first reported in 2018.

https://github.com/devAbnull/simulate_sugargame/issues/1

I could not tell if you used git HEAD or the latest release of
Simulate, which predates git HEAD by some years.

http://activities.sugarlabs.org/en-US/sugar/addon/4778
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project

[James Cameron]

Thanks for that.  You found what I found, that most of Sugar is
working fine in Raspberry Pi OS.  In your logs, only the Write
activity tracebacks are concerning, the rest seems normal.  There may
be ways to solve the rest, but if I discovered them I would fix them
rather than consume time in explaining them.

You may widen your tests by installing any additional activities
using;

1.  sudo apt install sugar-*-activity

2.  Browse -> Activities (the library)

The activities installed on Fedora SoaS are more extensive, may not be
available in Browse -> Activities, and may not be packaged for Debian.

The first step is easily in our control, the second step requires
support from the Debian Project.

Modifying and releasing activities is described in our guide to
contributing, with the release to the library described in the last
item of the list;

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

For most activities, the role of activity maintainer is flexibly
assigned; i.e. developers now tend to take the role for a few days and
then release.

On Sat, Apr 01, 2023 at 02:48:13AM +0530, Simrann Arora wrote:
> Hello James,
> 
> Thanks a lot for the detailed response.
> 
> I have gone through the logs and prepared a log report of the bugs and broken
> activities that I encountered. I will be trying to find fixes and
> continue working on them during the GSoC period.
> 
> I would request you to review this and give your suggestions on how to fix
> these errors further.
> 
> Thanks and Best Regards
> Simrann Arora
> GitHub Handle: @simrann20
> 
> *
> On Fri, Mar 31, 2023 at 4:10 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Thanks for testing.
> 
> Some of the information we gave was out of date, please see the
> changes in [2]https://github.com/sugarlabs/sugar/commit/cc22632
> 
> The missing icon for the description is a known issue being tracked as
> [3]https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/465 but nobody
> seems to be working on it.
> 
> Reasons for fail to start of Calculator, Image Viewer, Chat, Pippy,
> Write and Log may be found in .sugar/default/logs
> 
> Please use copy and paste of terminal text rather than photographs or
> screenshots.  We cannot search them.
> 
> On Fri, Mar 31, 2023 at 03:14:12AM +0530, Simrann Arora wrote:
> > Hi Mentors,
> >
> > Hope you all are doing great!
> >
> > I have tested Sugar on Raspberry Pi and I have prepared a report based 
> on
> my
> > findings. I am attaching the same for your reference. I  am trying to 
> fix
> these
> > bugs and would request you all to review  and give your suggestions on
> how to
> > fix these issues going forward.
> >
> > Thanks and Best Regards
> > Simrann Arora
> > GitHub Handle: @simrann20
> > *
> > On Wed, Mar 29, 2023 at 2:10 AM James Cameron <[1][4]qu...@laptop.org>
> wrote:
> >
> >     G'day Simrann,
> >
> >     Running Sugar on Raspberry Pi OS to identify what needs fixing will
> be
> >     a good thing for Sugar Labs.  It will also feed into and affect the
> >     other proposals and ideas.  There is an opportunity to collaborate
> >     with many others.
> >
> >     Your proposal could include a list of Raspberry Pi focused Linux
> >     distributions you have tested Sugar on, along with the broad
> outcomes.
> >
> >     On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote:
> >     > Hello James,
> >     >
> >     > Thanks for your quick response.
> >     >
> >     > From what I understand, `rpi23-gen-image` repository is old so it
> cannot
> >     be
> >     > used for this project.
> >     > I think I should run Sugar on Raspberry Pi OS and identify what is
> broken
> >     /bugs,
> >     > so I can work on fixing them during my GSoC period.
> >     >
> >     > I will also check out other debian image builders for Raspberry Pi
> >     which can be
> >     > leveraged to create Sugar OS images.
> >     >
> >     > I would also request my mentors @walterbender and @alexperez  to
> see if
> >     my
> >     > understanding is correct and also discuss the hardware 
> requirements
> to
> >     extend
> >     > the functionalities of existing activities like Turtle Blocks,
> Measure,
> >     and
> >

Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project

[James Cameron]

Thanks for testing.

Some of the information we gave was out of date, please see the
changes in https://github.com/sugarlabs/sugar/commit/cc22632

The missing icon for the description is a known issue being tracked as
https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/465 but nobody
seems to be working on it.

Reasons for fail to start of Calculator, Image Viewer, Chat, Pippy,
Write and Log may be found in .sugar/default/logs

Please use copy and paste of terminal text rather than photographs or
screenshots.  We cannot search them.

On Fri, Mar 31, 2023 at 03:14:12AM +0530, Simrann Arora wrote:
> Hi Mentors,
> 
> Hope you all are doing great!
> 
> I have tested Sugar on Raspberry Pi and I have prepared a report based on my
> findings. I am attaching the same for your reference. I  am trying to fix 
> these
> bugs and would request you all to review  and give your suggestions on how to
> fix these issues going forward.
> 
> Thanks and Best Regards
> Simrann Arora
> GitHub Handle: @simrann20
> *
> On Wed, Mar 29, 2023 at 2:10 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> G'day Simrann,
> 
> Running Sugar on Raspberry Pi OS to identify what needs fixing will be
> a good thing for Sugar Labs.  It will also feed into and affect the
> other proposals and ideas.  There is an opportunity to collaborate
> with many others.
> 
> Your proposal could include a list of Raspberry Pi focused Linux
> distributions you have tested Sugar on, along with the broad outcomes.
> 
> On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote:
> > Hello James,
> >
> > Thanks for your quick response.
> >
> > From what I understand, `rpi23-gen-image` repository is old so it cannot
> be
> > used for this project.
> > I think I should run Sugar on Raspberry Pi OS and identify what is 
> broken
> /bugs,
> > so I can work on fixing them during my GSoC period.
> >
> > I will also check out other debian image builders for Raspberry Pi
> which can be
> > leveraged to create Sugar OS images.
> >
> > I would also request my mentors @walterbender and @alexperez  to see if
> my
> > understanding is correct and also discuss the hardware requirements to
> extend
> > the functionalities of existing activities like Turtle Blocks, Measure,
> and
> > Pippy.
> >
> > Thanks and Best Regards
> > Simrann Arora
> > GitHub Handle: @simrann20
> > *
> > On Tue, Mar 28, 2023 at 5:39 AM James Cameron <[1][2]qu...@laptop.org>
> wrote:
> >
> >     Hello Simrann,
> >
> >     I've just now tested [2][3]https://github.com/drtyhlpr/
> rpi23-gen-image on a
> >     Debian 10 Buster 64-bit system, and it got past the debootstrap
> stage,
> >     compiled a kernel, generated an image, but failed with "losetup:
> >     cannot find an unused loop device".  I did not see an exec format
> >     error.  The method was;
> >
> >     ```
> >     apt install -y git debootstrap debian-archive-keyring
> qemu-user-static
> >     binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus
> sudo
> >     crossbuild-essential-armhf crossbuild-essential-armel bison flex
> libssl-dev
> >     git clone [3][4]https://github.com/drtyhlpr/rpi23-gen-image.git
> >     cd rpi23-gen-image
> >     ./rpi23-gen-image.sh
> >     ```
> >
> >     I suggest making sure you are using the operating system versions
> >     described in the README.md file, and the HEAD of the master branch.
> >
> >     Do not use the Sugar Labs fork of the repository, as it is very old.
> >
> >     Do engage with the rpi23-gen-image project; it is not part of Sugar
> >     Labs, and we have not used it for a while.  Your problem with
> >     debootstrap is best answered there, or by reading the debootstrap
> >     or Linux source code.
> >
> >     I'm not a mentor for Google Summer of Code this year, but I've a few
> >     things to say.
> >
> >     I doubt that rpi23-gen-image is suitable for your project.  It is 
> for
> >     making images.  It is an external tool, and not part of the workflow
> >     of either the Raspberry Pi Foundation, Debian Project, or Fedora
> >     Project.  These projects use other tools to prepare their images,
> >     based on their package archives.
> >
> >   

Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project

[James Cameron]

G'day Simrann,

Running Sugar on Raspberry Pi OS to identify what needs fixing will be
a good thing for Sugar Labs.  It will also feed into and affect the
other proposals and ideas.  There is an opportunity to collaborate
with many others.

Your proposal could include a list of Raspberry Pi focused Linux
distributions you have tested Sugar on, along with the broad outcomes.

On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote:
> Hello James,
> 
> Thanks for your quick response.
> 
> From what I understand, `rpi23-gen-image` repository is old so it cannot be
> used for this project.
> I think I should run Sugar on Raspberry Pi OS and identify what is 
> broken/bugs,
> so I can work on fixing them during my GSoC period.
> 
> I will also check out other debian image builders for Raspberry Pi which can 
> be
> leveraged to create Sugar OS images.
> 
> I would also request my mentors @walterbender and @alexperez  to see if my
> understanding is correct and also discuss the hardware requirements to extend
> the functionalities of existing activities like Turtle Blocks, Measure, and
> Pippy.
> 
> Thanks and Best Regards
> Simrann Arora
> GitHub Handle: @simrann20
> *
> On Tue, Mar 28, 2023 at 5:39 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Hello Simrann,
> 
> I've just now tested [2]https://github.com/drtyhlpr/rpi23-gen-image on a
> Debian 10 Buster 64-bit system, and it got past the debootstrap stage,
> compiled a kernel, generated an image, but failed with "losetup:
> cannot find an unused loop device".  I did not see an exec format
> error.  The method was;
> 
> ```
> apt install -y git debootstrap debian-archive-keyring qemu-user-static
> binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus sudo
> crossbuild-essential-armhf crossbuild-essential-armel bison flex 
> libssl-dev
> git clone [3]https://github.com/drtyhlpr/rpi23-gen-image.git
> cd rpi23-gen-image
> ./rpi23-gen-image.sh
> ```
> 
> I suggest making sure you are using the operating system versions
> described in the README.md file, and the HEAD of the master branch.
> 
> Do not use the Sugar Labs fork of the repository, as it is very old.
> 
> Do engage with the rpi23-gen-image project; it is not part of Sugar
> Labs, and we have not used it for a while.  Your problem with
> debootstrap is best answered there, or by reading the debootstrap
> or Linux source code.
> 
> I'm not a mentor for Google Summer of Code this year, but I've a few
> things to say.
> 
> I doubt that rpi23-gen-image is suitable for your project.  It is for
> making images.  It is an external tool, and not part of the workflow
> of either the Raspberry Pi Foundation, Debian Project, or Fedora
> Project.  These projects use other tools to prepare their images,
> based on their package archives.
> 
> Sugar is available for Raspberry Pi on Debian, Fedora, and Raspberry
> Pi OS already.
> 
> Raspberry Pi OS does not include Sugar in the images, but it can be
> installed.  This is because Raspberry Pi OS is based on Debian.
> 
> The Fedora Sugar on a Stick images are available for Raspberry Pi.
> 
> The number of organisations involved that are not Sugar Labs makes
> your project a challenge.  Mentors working for Sugar Labs can't easily
> affect the other projects or make resources available for you.  You
> should ask your mentors to better define the scope, without creating
> work dependencies on other organisations.
> 
> Sugar on Raspberry Pi does have several bugs, and does not have
> Raspberry Pi specific extensions.
> 
> Fixing those bugs is a matter of either (a) fixing our software in a
> Sugar Labs repository, (b) fixing packaging in the Fedora or Debian
> Projects, and (c) waiting for the fixes to reach the released images.
> That wait always exceeds the time available for Google Summer of Code.
> 
> Adding features specific to the Raspberry Pi is important.  For that,
> you will need a Raspberry Pi, and electronics components and tools.
> If you've worked on Arduino previously, this will be easy.  You will
> write software in Sugar Labs repositories, such as Turtle Blocks,
> Measure, and Pippy.
> 
> References:
> 
> [4]https://arm.fedoraproject.org/
> [5]https://spins.fedoraproject.org/en/soas/
> [6]https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi
> [7]https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md
> [8]https://github.com/sugarlabs/sugar/blob/master/docs/rpi.md
> [9]https://github

Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project

[James Cameron]

Hello Simrann,

I've just now tested https://github.com/drtyhlpr/rpi23-gen-image on a
Debian 10 Buster 64-bit system, and it got past the debootstrap stage,
compiled a kernel, generated an image, but failed with "losetup:
cannot find an unused loop device".  I did not see an exec format
error.  The method was;

```
apt install -y git debootstrap debian-archive-keyring qemu-user-static 
binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus sudo 
crossbuild-essential-armhf crossbuild-essential-armel bison flex libssl-dev
git clone https://github.com/drtyhlpr/rpi23-gen-image.git
cd rpi23-gen-image
./rpi23-gen-image.sh
```

I suggest making sure you are using the operating system versions
described in the README.md file, and the HEAD of the master branch.

Do not use the Sugar Labs fork of the repository, as it is very old.

Do engage with the rpi23-gen-image project; it is not part of Sugar
Labs, and we have not used it for a while.  Your problem with
debootstrap is best answered there, or by reading the debootstrap
or Linux source code.

I'm not a mentor for Google Summer of Code this year, but I've a few
things to say.

I doubt that rpi23-gen-image is suitable for your project.  It is for
making images.  It is an external tool, and not part of the workflow
of either the Raspberry Pi Foundation, Debian Project, or Fedora
Project.  These projects use other tools to prepare their images,
based on their package archives.

Sugar is available for Raspberry Pi on Debian, Fedora, and Raspberry
Pi OS already.

Raspberry Pi OS does not include Sugar in the images, but it can be
installed.  This is because Raspberry Pi OS is based on Debian.

The Fedora Sugar on a Stick images are available for Raspberry Pi.

The number of organisations involved that are not Sugar Labs makes
your project a challenge.  Mentors working for Sugar Labs can't easily
affect the other projects or make resources available for you.  You
should ask your mentors to better define the scope, without creating
work dependencies on other organisations.

Sugar on Raspberry Pi does have several bugs, and does not have
Raspberry Pi specific extensions.

Fixing those bugs is a matter of either (a) fixing our software in a
Sugar Labs repository, (b) fixing packaging in the Fedora or Debian
Projects, and (c) waiting for the fixes to reach the released images.
That wait always exceeds the time available for Google Summer of Code.

Adding features specific to the Raspberry Pi is important.  For that,
you will need a Raspberry Pi, and electronics components and tools.
If you've worked on Arduino previously, this will be easy.  You will
write software in Sugar Labs repositories, such as Turtle Blocks,
Measure, and Pippy.

References:

https://arm.fedoraproject.org/
https://spins.fedoraproject.org/en/soas/
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi
https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md
https://github.com/sugarlabs/sugar/blob/master/docs/rpi.md
https://github.com/sugarlabs/sugar/blob/master/docs/debian.md
https://wiki.sugarlabs.org/go/Raspberry_Pi

On Tue, Mar 28, 2023 at 03:09:48AM +0530, Simrann Arora wrote:
> Hi Mentors, 
> 
> Hope you all are doing well!
> 
> My name is Simrann Arora and I am an aspiring GSoC 2023 contributor. I have
> been actively trying to contribute to the 'Sugar on Raspberry Pi' project that
> has been selected for GSoC this year. As far as my progress is concerned, till
> now I have completed the following tasks: 
> - Setting up Debian version 11(bullseye) VM on my mac using Parallels Desktop,
> earlier I had installed Ubuntu 23.04 using VMware Fusion
> - Cloning the rpi23-gen-image repo for building Sugar OS image.
> - I tried running the rpi23-gen-image builder script but I am getting this
> error:
> ```
>  chroot: failed to run command '/debootstrap/debootstrap': Exec format error.
> ```
> 
> I did some research to fix this, and found out that it might have occured due
> to the architecture mismatch of the chroot environment and the command that I
> am using to run the script, like suppose the chroot environment is 64-bit and
> the executable is 32-bit. Another reason could be that the executable is not
> compatible with the OS or the linux distro within the chroot environment.
> 
> - To fix this, I created a chroot environment of Debian version 9 (stretch)
> within my Debian 11 distro to make it compatible with the `rpi3stretch-sugar`
> template as given in the `rpi23-gen-image` repository and cloned it.
> However, when I ran the script, I encountered the same error:
> ```
>  chroot: failed to run command '/debootstrap/debootstrap': Exec format error. 
> ```
> 
> To further troubleshoot this, I tried installing the `binfmts support` and
> enabling qemu-arm within the chroot. 
> Again I got an error:  `update-binfmts: warning: qemu-arm not in database of
> installed binary formats. `
> 
> Now to fix this one I tried reinstalling qemu-user-static and enabling it but
> it 

Re: [Sugar-devel] Eager to work in fixing the UI of sugarizer.

[James Cameron]

Thanks.  I looked at the document previously and saw some of the proposed 
changes are immediately suitable for being proposed in our usual workflow, but 
I'm not the person who will be approving the changes, so I won't be specific 
about them.

I am maintainer of the GTK Implode activity, but your changes are for the 
Sugarizer version.

On Tue, Mar 14, 2023 at 02:03:05AM +0530, MR. OPTIMIST wrote:
> Hello James Cameron sir, 
>          Thanks for your feedback. I agree with you that sugar is an
> educational  platform and it does not look like flooding things on the 
> internet
> but user experience plays a vital role in any of the platforms be it 
> commercial
> or non profitable. Just a simple question: will you use a phone with no broken
> or no display, Same is user experience. So if we can improve, why shouldn't we
> improve ?   
> 
> Also I would be thankful if you kindly let me know which of the proposed
> changes seems to reasonable So that I can further proceed with further
> contribution.
> Proposed document link:-[1]click me to open
> 
> On Tue, Mar 14, 2023 at 1:29 AM James Cameron <[2]qu...@laptop.org> wrote:
> 
> Some of the changes proposed seem reasonable, but they aren't in the right
> form for review; they need to be pull requests against the appropriate
> repository.
> 
> I don't think we're using the older design review committee process any
> longer, and it should not be revived.  The pull request review process is
> sufficient.  In the case of Sugarizer, that's the process that Lionel has
> preferred.
> 
> However, as someone who works in science research, the proposal does not
> seem to have been researched, but is rather a collection of ideas that
> would be suitable for changing Sugarizer using A/B testing for the goal of
> increasing engagement and selling advertising.  Neither of these are
> intended, it's an educational project.  Sugar and Sugarizer don't have to
> look like everything else on the internet, and starting with that premise
> is an error.
> 
> On Mon, Mar 13, 2023 at 04:35:27PM +0530, MR. OPTIMIST wrote:
> > Thanks Alex Sir,
> >                         Your response to email is very much appreciated.
> Sorry
> > for the late reply.
> >
> > I love to mention that I have used sugarizer for many days and I also
> know that
> > its UI has been designed with the vision that it's gonna be used by
> childrens.
> > My point is that sugarizer was developed back in 2013 and the internet
> > revolution at the time was very less in comparison to 2023. The UI and 
> Ux
> terms
> > were not that considerable at that time and everyone didn't had access 
> to
> the
> > mobile phones and internet, But as of now in 2023 the childrens from 1 
> or
> even
> > less than that start using technical devices and the UX is what first
> thing
> > that they interact with like games and other applications.So the UI of
> > sugarizer is not matching with the need of today's generation which
> reduces the
> > user interest (research) to use the platform. So my point is we can work
> to
> > enhance its UI to meet today's need and increase the interaction time of
> the
> > users of our product.
> >
> > Considering my skills, I'm a second year engineering student and a self
> > learner, I have done multiple projects on AI based applications and
> developed 2
> > websites as of now. To authenticate my words hereby i have listed all my
> > projects in my github account and link of my github account is:- 
> > [1] [3]https://www.github/Anujverma89
> >
> > Considering what part of the product and UI can be modified to give new
> user
> > experience, I have done research and explained it in the given pdf you
> can view
> > it thoroughly.
> > Here is the link :-
> > [2]Click me to open !! 
> >
> > Your suggestions on changeable topics(UI) will be highly appreciated !! 
> > Thank You..
> >
> > On Sat, Mar 11, 2023 at 12:18 AM Alex Perez <[3][4]ape...@alexperez.com>
> wrote:
> >
> >     Anuj,
> >
> >     I appreciate your enthusiasm, and welcome. Before any UI re-design
> would be
> >     considered, we would require detailed written analysis of what the
> goals
> >     are for such a re-design, what's "wrong" with the current design, 
> and
> what
> >     your qualifications are for making what are 

Re: [Sugar-devel] Eager to work in fixing the UI of sugarizer.

[James Cameron]

Some of the changes proposed seem reasonable, but they aren't in the right form 
for review; they need to be pull requests against the appropriate repository.

I don't think we're using the older design review committee process any longer, 
and it should not be revived.  The pull request review process is sufficient.  
In the case of Sugarizer, that's the process that Lionel has preferred.

However, as someone who works in science research, the proposal does not seem 
to have been researched, but is rather a collection of ideas that would be 
suitable for changing Sugarizer using A/B testing for the goal of increasing 
engagement and selling advertising.  Neither of these are intended, it's an 
educational project.  Sugar and Sugarizer don't have to look like everything 
else on the internet, and starting with that premise is an error.

On Mon, Mar 13, 2023 at 04:35:27PM +0530, MR. OPTIMIST wrote:
> Thanks Alex Sir,
>                         Your response to email is very much appreciated. Sorry
> for the late reply.
> 
> I love to mention that I have used sugarizer for many days and I also know 
> that
> its UI has been designed with the vision that it's gonna be used by childrens.
> My point is that sugarizer was developed back in 2013 and the internet
> revolution at the time was very less in comparison to 2023. The UI and Ux 
> terms
> were not that considerable at that time and everyone didn't had access to the
> mobile phones and internet, But as of now in 2023 the childrens from 1 or even
> less than that start using technical devices and the UX is what first thing
> that they interact with like games and other applications.So the UI of
> sugarizer is not matching with the need of today's generation which reduces 
> the
> user interest (research) to use the platform. So my point is we can work to
> enhance its UI to meet today's need and increase the interaction time of the
> users of our product.
> 
> Considering my skills, I'm a second year engineering student and a self
> learner, I have done multiple projects on AI based applications and developed 
> 2
> websites as of now. To authenticate my words hereby i have listed all my
> projects in my github account and link of my github account is:- 
> [1] https://www.github/Anujverma89
> 
> Considering what part of the product and UI can be modified to give new user
> experience, I have done research and explained it in the given pdf you can 
> view
> it thoroughly.
> Here is the link :-
> [2]Click me to open !! 
> 
> Your suggestions on changeable topics(UI) will be highly appreciated !! 
> Thank You..
> 
> On Sat, Mar 11, 2023 at 12:18 AM Alex Perez <[3]ape...@alexperez.com> wrote:
> 
> Anuj,
> 
> I appreciate your enthusiasm, and welcome. Before any UI re-design would 
> be
> considered, we would require detailed written analysis of what the goals
> are for such a re-design, what's "wrong" with the current design, and what
> your qualifications are for making what are largely subjective changes.
> While everyone has opinions on UI design, engineers are often infamous for
> designing awful user interfaces. Please share with us what sorts
> qualifications you possess that would qualify you to make UI design 
> changes
> to Sugar/Sugarizer.
> 
> Have you ever used Sugar for more than a few hours, or a day? If so, which
> elements do you feel should be changed? If you have not used Sugar
> extensively, I would argue that you likely lack sufficient experience to
> propose such changes.
> 
> The Sugar/Sugarizer UI was primarily designed for children of a specific
> age range. Almost all design decisions stem from that basic premise. Have
> you considered this?
> 
> Regards,
> Alex Perez
> 
> MR. OPTIMIST wrote on 3/10/23 10:24 AM:
> 
> Hello everyone !
>                  I am Anuj Verma from Maharashtra, India majoring in
> computer science and engineering.  I have worked in multiple projects
> and web applications including AI projects.
> I have checked the sugarizer, it's pretty good but I believe it's UI
> can be improved. Like we 
> can add links to words as well as icons, we can improve icons as well
> which is less user friendly(in my opinion).I have experience of 
> working
> with many projects but have not worked on open source yet. I'm
> writing to seek further comments and be open to constructive feedback
> and criticism. Your response to this mail will be highly appreciated.
> 
> References:
> 
> [1] https://www.github/Anujverma89
> [2] 
> https://docs.google.com/document/d/1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing
> [3] mailto:ape...@alexperez.com

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

___

Re: [Sugar-devel] Creating a new Activity

[James Cameron]

That's great.  The mentors will look forward to seeing your proposal.

On Sat, Feb 25, 2023 at 08:48:03PM +0530, Joseph Raj Vishal wrote:
> Hello, My name is Joseph Raj Vishal, I am a student at Dayananda Sagar College
> of Engineering, Im in my third year of CS and I would like to apply for your
> organisation and submit an idea which is not there in the idea list.  I was
> wondering if I could create a new activity is MasterChef the name can be 
> worked
> on basically it is an activity where you are given a bunch of ingredients in
> random order and the an ingredient list , the child should add together the
> ingredients accordingly in order to complete a dish. The kid with the most
> points win , in this way they will learn vegetables and fruits.

> ___
> 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] (no subject)

[James Cameron]

You can find this on the Google Summer of Code web site, select Sugar Labs as 
an organisation then scroll down to the projects.

https://summerofcode.withgoogle.com/programs/2022/organizations/sugar-labs

On Fri, May 27, 2022 at 10:13:56PM +0530, Arham Hayat wrote:
> Hello there,
> I wanted to ask what are the projects that are selected for this year's GSOC
> and Who is selected for The Excerciser Evaluation Mode project. Is there any
> way i can contribute in them so that i can get to know more about open source
> projects?
> 

> ___
> 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] Trouble editing python scripts for sugar based games

[James Cameron]

What you are asking is how to edit files.  There are so many ways to
do this, that it is best that we leave that kind of documentation to
the projects that maintain your tools.  I can't afford the time to
support you in using the tool chain I'm using, so I'll speculate
instead.  I dislike speculating in engineering, as it leads quickly to
error.

I'm guessing you may be familiar with Visual Studio Code, a
source-code editor made by Microsoft for Windows, Linux, and macOS.  A
remote SSH extension is available for VS Code.  So an outline of
workflow could be;

1.  set up SSH keyed access into one of the virtual machines from your
development system, preferrably with keys that have no passphrase,
(see the SSH documentation for how to do this),

2.  set up SSH configuration (~/.ssh/config) so that the correct
username is applied, e.g.

Host vm
User guest

3.  test that you can SSH into the virtual machines, quickly and
easily, e.g.

ssh vm whoami

4.  log in using SSH, make the ~/Activities directory (it may already
be there), and clone an activity repository from GitHub, e.g.

ssh vm
mkdir ~/Activities
git clone https://github.com/sugarlabs/hello-world.git 
~/Activities/HelloWorld.activity

5.  restart Sugar, and verify that the activity is shown in the home
view,

6.  install Visual Studio Code, and the remote SSH extension,

7.  use the extension to open the directory, change the source code,
and run the activity in Sugar.

On Sat, May 21, 2022 at 12:47:28AM +0530, Shreyas Sukhdeve wrote:
> Respected sir/ma'am,
> 
> I am Shreyas Sukhadeve, a student of Computer Science and Engineering at 
> Indian
> Institute of Technology, Bhubaneswar (IIT BBS).
> 
> The reason for writing this mail is to seek your help regarding a trouble I am
> facing with editing python scripts in sugar based games on my linux virtual
> machine.
> 
> I do not have a good level of proficiency with using linux machines and have
> tried various steps to solve the issue in the past but failed to successfully
> implement the editable version of the activities.
> 
> The situation I am currently in is that I have installed a total of 4 Linux
> Distributions in my Virtual Box, apart from the Ubuntu 20.04 system that is 
> not
> supported by Sugar, the other 3(fedora, debian and SugarOS) end up allowing me
> to run the activities on sugar when I choose the option of starting with the
> sugar interface when entering password, but I am not able to make any edits to
> the code that will reflect on the sugar interface.
> 
> What I request from you is to help me set up at least one distribution of 
> linux
> or SugarOS where I can edit the code. Also I request you to please screen
> record a segment of your work when accessing sugar activities for editing so
> that I can understand how I need to edit the code when the linux distribution
> is all set for coding.
> 
> I acknowledge that I am requesting a lot but I plead with you to consider my
> situation where I am stuck at the same point from days trying to contribute 
> but
> failing to do so due to this problem.
> 
> Waiting for your reply
> 
> Thank you, 
> Yours Sincerely,
> Shreyas Sukhadeve.
> 
> Sent with [1]Right Inbox
> 
> References:
> 
> [1] https://www.rightinbox.com/?utm_source=signature

> ___
> 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

[Sugar-devel] [RELEASE] Sugar 0.119 unstable

[James Cameron]

Sugar 0.119 is released.

It has been a while since the last release.  This release contains
some fixes, especially for regressions following the Python 3 port.

sha256 checksums;

01a027b64c44e4f5fa27933d803ce8358d22c04bc882b689e797d36a85f13718  
sugar-artwork-0.119.tar.xz
c64a2a03bbd1a6b626006a650584645920b5ef376724d4fc68bc5719a94bea73  
sugar-toolkit-gtk3-0.119.tar.xz
3d1d90bd5676398db8355ba878485d322371dfd8e35491862ddb993a4f18d07c  
sugar-datastore-0.119.tar.xz
b9c00c0a8b5ddd7ebfcd590ad0fc85352f2159cf509f7649e164995689d67619  
sugar-0.119.tar.xz


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

Re: [Sugar-devel] Draft proposal review - Improve and maintain 12 activities

[James Cameron]

Another fantastic proposal, well done.  You're testing activities with
children, and you can write in Lua on NodeMCU.  Both are very helpful
skills for the work you have planned.  Good luck!

Your software development environment may cause problems.  You're
using Sugar 0.117, and the latest is 0.118, with some changes yet to
be released.  I suggest looking through the commits since 0.117 on the
sugar-toolkit-gtk3 repository, so you can handle known problems.

Also remember to keep whole of system backups, so that any accident
doesn't threaten your work.  On your chosen device, this is remarkably
easy, as you can duplicate the microSD card.

On Sun, Apr 17, 2022 at 06:37:25PM +0530, Sourabha G wrote:
> Greetings everyone,
> Here is my draft proposal on the project: Improve and maintain 12 activities.
> Thoughts and suggestions are welcome :)


> ___
> 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'22 Draft Proposal review (Sugarizer Vue.js UI)

[James Cameron]

A fantastic proposal, well done.  I like how you've built on your work
so far and described design changes in your plan.  Good luck!

One tiny english observation; "I vision to hone" is a way of using
these words I've never seen before.  I understand the intent, but my
reading stumbled.

On Sun, Apr 17, 2022 at 06:24:38PM +0530, Saumya Kushwaha wrote:
> Hello everyone!
> 
> I am Saumya Kushwaha a CSE 2nd Year undergraduate student at IIT BHU, India. I
> am applying as a contributor in GSoC'22 for the project Sugarizer Vue.js UI.
> Following is my proposal for this project. I would appreciate any feedback or
> comment from the community on this proposal.
> 
> Thanks and Regards,
> Saumya Kushwaha


> ___
> 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] sugar live boot is not persistent.

[James Cameron]

Perhaps you mean Sugar Live Build.

Sugar Live Build contains both Python 2 and Python 3 environment for
Sugar, which makes it very easy to port Python 2 activities to Python
3, because you can compare execution of the Python 2 activity with
your in-progress Python 3 port.  Python 2 is no longer available in
Fedora for using Sugar, so do not use SoaS unless you have finished
the porting.

It looks like you have been booting Sugar Live Build rather than
installing it.  That is just one of many ways to use Sugar Live Build.

To install Sugar Live Build, create a virtual machine with a virtual
disk, boot from the ISO file, and as soon as the virtual machine shows
the boot menu, be sure to select "Install".  See attached.

This will start installation of Debian on the virtual disk.  See
attached.

You will be asked a series of questions, such as language, location,
and keyboard.  Additional components will be loaded.  Then further
questions; host name, domain name, new root password, new user
account, and clock time zone.  Then for a virtual disk partitioning
question choose "Guided - use entire disk", "All files in one
partition", and "Finish partitioning and write changes to disk".

There are other questions, but these are normal Debian questions, so
the best way to answer them is to understand the question by reading
the Debian documentation.  They aren't Sugar questions.

Eventually the system will be installed on the virtual disk.

When the virtual machine is rebooted, log in with the new user
account, and Sugar will be started.

For development, set up an IDE on your main computer, set up SSH
access into the virtual machine, and begin editing files on the
virtual disk from your main computer.  Exactly how to do this depends
on the IDE you have chosen, and so we can't really go into detail
unless it is an IDE we use.

On Sat, Apr 16, 2022 at 11:37:41PM +0530, UMESH ARADHYA P wrote:
> Hello,
> I am Umesh, a contributor from India.
> 
> I have installed sugar on a virtual box using Sugar Live Boot and am working 
> on
> it. I have made changes to an activity. But, once I reboot sugar to the 
> virtual
> box, all the changes I made are no longer available. I’m not sure how to fix
> this issue, can the mentors kindly help me with this issue?
> 
> I started learning python in my first year of college. Python has been my 
> first
> priority over various programming languages.i am very much interested to work
> on port to python3 project.
> 
> Regards,
> 
> Umesh.
> 

> ___
> 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 2022 Draft Proposal (Maintaining 6 activities)

[James Cameron]

Thanks, that's interesting.  I have a few suggestions.

1.  your work so far indicates you are likely to be able to do much
more than what you have listed in the proposal; you may wish to add
stretch goals in case you have free time,

2.  you've mentioned release to ASLO v4 as something you want to
enable; you may instead include release in each of your goals,

3.  the organisation name has a space between Sugar and Labs; if
there's anywhere we aren't doing that (apart from the domain name,
GitHub organisation name, and a logo on our web site), please let us
know.

Good luck!

On Sun, Apr 17, 2022 at 12:38:29AM +0530, Sparsh Goenka wrote:
> Hi there!
> 
> Before submitting my final GSoC proposal, I would like to get some 
> suggestions from the community if there is something I need to add on.
> I decided to maintain 6 (or more) activities :D
> 
> Thanks,
> Sparsh
> 


> ___
> 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 2022

[James Cameron]

Welcome Arham,

Your selected task is

https://github.com/sugarlabs/GSoC/blob/master/Ideas-2022.md#exerciser-evaluation-mode

The mentor is Ashish Aggarwal .

I guess you have newly joined the mailing list.  Ashish has given
guidance already last week.  See our mailing list archives.

http://lists.sugarlabs.org/archive/sugar-devel/2022-April/059289.html

If you're not sure about how exerciser works now, please try using it,
and review the source code.

https://github.com/llaske/ExerciserReact

On Sat, Apr 16, 2022 at 03:10:11AM +0530, Arham Hayat wrote:
> Hey there,
> I am Arham Hayat, selected this org for GSOC'22, selected my task but needed
> some clarifications regarding that, need to know about Evaluation mode, It's
> not clear how it is working now, and it needed to show only scores or it is
> currently showing only scores and need to show the individual answers. Also, 
> If
> i may get to talk to the mentor regarding this project so that i can clarify 
> my
> small doubts too. 

> ___
> 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] Activities.

[James Cameron]

Because we have lost people from our community who were performing the
activity maintainer role.  An activity maintainer is a developer who
releases new versions of an activity.

We have a checklist for the role here;
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer

On Fri, Apr 15, 2022 at 12:49:17AM +0530, Sarthak Kinge wrote:
> Why are the activities mentioned in [1]https://help.sugarlabs.org/index.html
> not available on [2]https://v4.activities.sugarlabs.org/ ?
> 
> References:
> 
> [1] https://help.sugarlabs.org/index.html
> [2] https://v4.activities.sugarlabs.org/

> ___
> 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] My several activities are not running on my setup.

[James Cameron]

Read the log files and diagnose the failure cause?

On Tue, Apr 12, 2022 at 10:18:03PM +0530, Sarthak Kinge wrote:
> I've been trying to run these activities for 2-3 days. I am not able to open
> these activities. I did read the setup instructions and followed the steps as
> it is but still it is not working . What should I do?

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

Re: [Sugar-devel] GSOC 2022 Proposal

[James Cameron]

You also raised an issue on our GSoC repository.  I suggest that if Ashish is 
unresponsive, then contact Lionel Laske as next step.

On Sun, Apr 10, 2022 at 05:07:45PM +0530, Divyansh Agarwal wrote:
> Hi,
> 
> Myself Divyansh,
> I was going through the ideas for GSOC 2022 and I have created a proposal. I
> want to ask how to get the proposal reviewed by the mentor of the Sugarizer
> Exerciser Evaluation mode project.
> 

> ___
> 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] Many sugar activities are not getting started , how should I fix this?

[James Cameron]

Thanks for asking.

https://activities.sugarlabs.org/ is only for Python 2 activities, as
described in the checklist for maintainers;
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md

https://v4.activities.sugarlabs.org/ is for Python 3 activities.  If
you are using a Python 3 build of Sugar, then you should be using this
instead of activities.sugarlabs.org.

The Browse activity should have directed you to
https://v4.activities.sugarlabs.org/ automatically if you are using
v207.

For the Abacus activity, it looks like v61 was released on 21st
January 2020, and is available on download.sugarlabs.org, but it isn't
uploaded into v4.activities.sugarlabs.org yet.

For the Tam Tam activities, they are not yet ported to Python 3.

So please tell me how it was you decided to use
activities.sugarlabs.org?  It is important that we give accurate
guidance everywhere in our project, and if we slipped up we should fix
it.

In general, if you're not sure why an activity fails to start, you
should use the Log activity to read through the error messages.

On Fri, Apr 08, 2022 at 02:08:48PM +0530, Sarthak Kinge wrote:
> I downloaded sugar activities from  [1]activities.sugarlabs.org  but I'm not
> able to start the activity . What should I do?
> 
> References:
> 
> [1] http://activities.sugarlabs.org/



> ___
> 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] B2-7 dev laptop donation?

[James Cameron]

G'day Alex,

Contact Sameer Verma at OLPC SF.  That's where OLPC is currently
referring surplus XO-1 to.

The SKU1 may be unlocked with the new
https://wiki.laptop.org/go/Persistent_developer_key_firmware
and upgraded to OLPC OS 13.2.11
https://wiki.laptop.org/go/Release_notes/13.2.11

The B2-7 are a problem though, as we stopped sustaining the firmware a
long time ago.  Don't try to upgrade them.

On Tue, Jan 11, 2022 at 12:37:47PM -0800, Alex Polvi wrote:
> Hello, I hope this finds you well! Sorry if this is a little OT but I have
> a 2x B2-7 pre-production beta, and 1x SKU1 XO-1 OLPC laptop that I got when I
> was a developer on OLPC in 2007. 
> 
> I was curious if anyone knew of a place that might be a good home for these. 
> My
> understanding is that they are relatively rare. 
> 
> Thank you for any leads. I'm just hoping to donate them to a good home. 
> 
> Thanks,
> 
> -Alex

> ___
> 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

[Sugar-devel] TumbleBoy-1.xo walkthrough video

[James Cameron]

https://youtu.be/ucl0eN2kNdc is a walkthrough of the TumbleBoy-1.xo
game.

This game was published on olpcgames.org and was found using
Internet Archive wayback machine.

It is Python 2 game that relies on olpcgames, Pygame, and Pygtk
libraries.  Inside it is a smaller Python program TumbleBoy.py that
only relies on Pygame.

I've added it to
https://github.com/sugarlabs/tumbleboy-activity
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] The Legacy of OLPC and Charismatic Pitfalls in Teaching Programming Podcast

[James Cameron]

It's good.  I recommend it.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Unable to use shared clipboard in sugar live vm.

[James Cameron]

It's not really something I do.  It is easier to set up an SSH server
and use an SSH client to copy any text from the system, using the
script(1) command, a shared screen(1), or log files.

I don't know what you did wrong, sorry.  Unless you've kept detailed
notes, there's no way to guess.

However, you haven't shown that you have installed the VirtualBox
X11 guest utilities package on the Debian Sugar Live Build VM.

Sugar Live Build does not have VirtualBox packages preloaded.

You could install the Sugar Live Build to a virtual disk, then
install the Debian package virtualbox-guest-x11, then restart Sugar.

Or, you could install the Debian package
virtualbox-guest-additions-iso build-essential dkms and your kernel
headers, and then build the kernel module provided on the ISO.

Your question is about VirtualBox and Linux in general, not Sugar.
The article below shows some of the complexity of what you are asking
about.
https://superuser.com/questions/1318231/why-doesnt-clipboard-sharing-work-with-ubuntu-18-04-lts-inside-virtualbox-5-1-2

Hope that helps.

On Sun, May 09, 2021 at 10:32:42AM +0530, Shivam Rai wrote:
> I have installed virtualbox extension pack on virtual box and i confirmed it 
> on
> my vm by checking it in extensions option. 
> Is there anything I am supposed to do?
> Or I did something wrong while setting the vm? 
> 
> On Tue, May 4, 2021, 3:06 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> I agree.
> 
> On Tue, May 04, 2021 at 12:19:42PM +0300, [2]srevins...@sugarlabs.org
> wrote:
> > Its likely that you haven't installed Virtual Box Extension pack on the
> Debian
> > Sugar Live Build.
> >
> >
> > On Tuesday, May 4, 2021 11:51:30 AM +03 Shivam Rai wrote:
> > > Even after enabling bidirectional clipboard it doesnt work in
> > > sugarlivebuild vm.
> > > Have tried some change in settings but it didnt work.
> > > Although with the same settings there is no copy paste issue in other
> vm's
> > > i am using.
> > > I think its something from my side.
> > > What can be done to sort this out?
> > >
> >
> >
> >
> >
> > _______
> > Sugar-devel mailing list
> > [3]Sugar-devel@lists.sugarlabs.org
> > [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [5]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [6]Sugar-devel@lists.sugarlabs.org
> [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] mailto:srevins...@sugarlabs.org
> [3] mailto:Sugar-devel@lists.sugarlabs.org
> [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> [5] https://quozl.linux.org.au/
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel



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

Re: [Sugar-devel] Unable to use shared clipboard in sugar live build vm.

[James Cameron]

It isn't clear if you have yet installed Virtual Box Extensions on the
Sugar Live Build virtual machine.

On Tue, May 04, 2021 at 04:02:25PM +0530, Shivam Rai wrote:
> I have windows and i have installed debian sugar live build in it as a
> virtual machine through virtualbox. 
> I am unable to copy text from windows to my virtual machine or vice versa.
> 
> In any  virtual machine in virtual box we can enable the shared clipboard
> feature to enable host to guest or guest to host copy paste.
>  
> But its not working for me. 
> 
> On Tue, May 4, 2021, 3:06 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> I agree.
> 
> On Tue, May 04, 2021 at 12:19:42PM +0300, [2]srevins...@sugarlabs.org
> wrote:
> > Its likely that you haven't installed Virtual Box Extension pack on the
> Debian
> > Sugar Live Build.
> >
> >
> > On Tuesday, May 4, 2021 11:51:30 AM +03 Shivam Rai wrote:
> > > Even after enabling bidirectional clipboard it doesnt work in
> > > sugarlivebuild vm.
> > > Have tried some change in settings but it didnt work.
> > > Although with the same settings there is no copy paste issue in other
> vm's
> > > i am using.
> > > I think its something from my side.
> > > What can be done to sort this out?
> > >
> >
> >
> >
> >
> > _______
> > Sugar-devel mailing list
> > [3]Sugar-devel@lists.sugarlabs.org
> > [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [5]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [6]Sugar-devel@lists.sugarlabs.org
> [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] mailto:srevins...@sugarlabs.org
> [3] mailto:Sugar-devel@lists.sugarlabs.org
> [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> [5] https://quozl.linux.org.au/
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel

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

Re: [Sugar-devel] Unable to use shared clipboard in sugar live vm.

[James Cameron]

I agree.

On Tue, May 04, 2021 at 12:19:42PM +0300, srevins...@sugarlabs.org wrote:
> Its likely that you haven't installed Virtual Box Extension pack on the 
> Debian 
> Sugar Live Build. 
> 
> 
> On Tuesday, May 4, 2021 11:51:30 AM +03 Shivam Rai wrote:
> > Even after enabling bidirectional clipboard it doesnt work in
> > sugarlivebuild vm.
> > Have tried some change in settings but it didnt work.
> > Although with the same settings there is no copy paste issue in other vm's
> > i am using.
> > I think its something from my side.
> > What can be done to sort this out?
> > 
> 
> 
> 
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

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

Re: [Sugar-devel] How to modify the sugar?

[James Cameron]

Ibiam has answered you, but I'll just add a bit of context.

Sugar is a "desktop environment", which means it is a graphical shell
program and a suite of other programs activated from that shell.  It
is run (using python module jarabe) as the first and only program of a
graphical login session, e.g. through Xsession.

Sugar uses GNU conventions for software package building and
installing.  We know this as "configure, make, make install".  The
method works on pretty much every major Linux distribution.

Each Linux distribution may follow different conventions for how
programs, or Python programs in particular, are installed.

Sugar Live Build is built from the Debian distribution, and so most
closely tracks how Debian developers install software.

However, it does not exactly match.

The domain specific knowledge needed is operating system software
distribution internals, and specific knowledge about how Python
programs are installed by distribution packages on a Debian system.

Once you know how a Python program is installed on a system for all
users of that system to use, you have the first step of many.

On Sat, Apr 17, 2021 at 05:06:29PM +0530, Sourabha G wrote:
> Hi everyone, 
>  How to test the modified source of sugar from within Sugar DE? I cloned the
> sugar repo but not sure how to test the modification.
> 
> Thank you.

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


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

Re: [Sugar-devel] Apply Changes to Sugar live build.

[James Cameron]

That is an expected outcome.  Don't make a virtual hard disk from the
ISO.  That way you have a live build as a hard disk, without any
persistence.  Instead, follow the normal Debian procedures for
installing the operating system to a new virtual hard disk.

Sorry, I don't have a reference to the Debian documentation.

On Fri, Apr 16, 2021 at 05:42:24PM +0530, Shivam Rai wrote:
> I made virtual hard disk from  sugarlivebuild.iso file and Later booted my
> virtual machine from that virtual hard disk . Applied changes, but on restart
> the changes were not kept.
> 
> On Wed, Apr 14, 2021, 10:00 PM Srevin Saju <[1]srevins...@sugarlabs.org> 
> wrote:
> 
> On Wednesday, April 14, 2021 2:36:19 PM +03 Shivam Rai wrote:
> > In terminal activity,I changed to super user with su command. Then  cd/
> to
> > respective directory. Then, vi(command) module.py.
> > It opened the module.Switched to insert mode(i). Changed the code. Then
> > saved and exit it using (:wq! )
> > I confirmed the changes by reopening the module. They are there. But 
> when
> I
> > restarted it the changes were not kept. The module was in its original
> > state.
> 
> As you mentioned about using the live build, I hope you are aware that the
> sugar live build is not persistent. Live ISOs keep their changes only in
> the
> RAM. once they are shutdown, they no longer carry the old changes across,
> (unless you have installed the live build to a virtual hard disk ¯\_(ツ)_/
> ¯),
> but there is a great possibility that you are running it live from the ISO
> file
> itself.
> 
> Cheers.
> 
> >
> > And Yes, I will make sure to keep related queries in same thread.
> >
> >
> >
> >
> > On Wed, Apr 14, 2021, 4:20 PM Chihurumnaya Ibiam 
> <[2]ib...@sugarlabs.org>
> >
> > wrote:
> > > How did you apply the changes?
> > >
> > > And also, can you keep similar discussions to one particular thread as
> it
> > > makes it easier to
> > > find for future reference as you already opened a similar thread
> earlier.
> > >
> > > --
> > >
> > > Ibiam Chihurumnaya
> > > [3]ib...@sugarlabs.org
> > >
> > >
> > >
> > > On Wed, Apr 14, 2021 at 11:18 AM Shivam Rai <[4]
> shivamrai19042...@gmail.com>
> > >
> > > wrote:
> > >> I applied changes in a module through bash terminal in sugar live
> build.
> > >> I shutdown and started machine. The changes were not kept. What can 
> be
> > >> the reason?
> > >> ___
> > >> Sugar-devel mailing list
> > >> [5]Sugar-devel@lists.sugarlabs.org
> > >> [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:srevins...@sugarlabs.org
> [2] mailto:ib...@sugarlabs.org
> [3] mailto:ib...@sugarlabs.org
> [4] mailto:shivamrai19042...@gmail.com
> [5] mailto:Sugar-devel@lists.sugarlabs.org
> [6] http://lists.sugarlabs.org/listinfo/sugar-devel

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


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

Re: [Sugar-devel] Incorrect Information

[James Cameron]

Thanks for pointing that out.  Use of other people's work should be credited.

https://github.com/sugarlabs/GSoC#want-to-work-with-us-

Aditya will be expected to revise their proposal to add this, if appropriate.

On Mon, Apr 12, 2021 at 08:31:11AM +0530, Sarthak gupta wrote:
> Hi Aditya,
> I saw your proposal which you've sent on the mailing list. There are few wrong
> things which you've mentioned in your proposal:
> 
>   • You mentioned there is an incomplete implementation of mine but I've not
> raised any pull request for measure activity. I had only discussion with
> Lionel.
>   • The image which you've used is part of work on my private branch which 
> I've
> made for showing UI prototype for GSOC 2021. How did you find this branch,
> I've not mentioned it anywhere.
>   • You've shown the proposed UI same as my work with little changes.
>   • Time period scaling and Waveform settings are exactly same as mine.
>   • You've used my code of audioprocess event listener and drawWaveform.
> 
> Regards,
> Sarthak Gupta
> (Github handle: sarthak-g)

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


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

Re: [Sugar-devel] Port to python3

[James Cameron]

Ultimate test is to run the activity on a system that does not have
Python 2.  If it doesn't run, or doesn't run properly, then work is
needed, and some of that work may relate to porting to Python 3.

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

Re: [Sugar-devel] Measure Activity

[James Cameron]

Voltage and resistance sense features of Measure activity main branch
head can only be tested with hardware that supports a DC mode on the
audio input jack, and consequently ASLA.

Raspberry Pi 4 does not have an audio input jack; you can see from the
schematics that the A/V JACK has the input pin 2 grounded, and only
the output pins available, and they are buffered as outputs by U5.

https://www.raspberrypi.org/documentation/hardware/raspberrypi/schematics/rpi_SCH_4b_4p0_reduced.pdf

So you can't test all existing features using a Raspberry Pi 4.

Raspbian has many low-speed inputs that could be used to implement a
new feature similar to the existing features, but the underlying API
would likely be different.  Someone looking to implement those will
need to familiarise with relevant kernel modules and user-space data
acquisition modules.

For implementing in Javascript, you'll need to find how to write
against an API for low-level hardware access.  I don't know of one.  I
doubt it will be possible without making the resulting program
specific to a particular model of computer, and that is unlikely to be
interesting to Sugarizer project.

On Mon, Apr 05, 2021 at 10:45:27PM +0530, Aditya sinha wrote:
> Hi everyone. I hope you are doing good. I went through the Sugar Measure
> Activity. I found the voltage and resistance sense features. I am currently
> using Sugar on Raspberry Pi 4. I want to know how should I test this features
> and any suggestions on how to implement them in Javascript. I did not find any
> information regarding these features on GSOC Ideas page.
> 
> Regards
> Aditya Sinha

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


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

Re: [Sugar-devel] Sugar Labs GSoC 2021

[James Cameron]

Hey Shikhar,

Any student that demonstrates an understanding or commits to Telepathy above 
the level of other students will have an advantage over those that haven't 
demonstrated this.  You might even fix some of the problems before your 
proposal is reviewed.  It is up to you how much time you spend on it.

On Mon, Mar 29, 2021 at 02:09:06PM +0530, Shikhar Sharma wrote:
> Hey,
> I am Shikhar, I am eager to learn and contribute towards sugar labs.
> I came across sugar labs while I was teaching my sibling, I really liked the
> product and wanted to contribute my time to it.
>  
> For the project "Port Sugar and core activities to Python 3"
> I know python and javascript , but have negligible experience with telepathy
> binding.
> So is it advisable for me to learn this section starting from today ,so that I
> can be a better candidate for Gsoc 2021 and contribute to sugar labs as I have
> used the product first hand.
> 
> Eagerly waiting for your reply!!
> 
> Thank you for your time,
> Shikhar

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


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

Re: [Sugar-devel] Issue in adding activities in Sugar

[James Cameron]

No worries.  With the knowledge you won't be fixing any of the Sugar
activities and only want to run them, the simplest would be to install
Sugar Live Build as a virtual machine.

Then try running each activity from a GitHub clone.

However, you'll still see many activities not working.  That's because
we don't have enough people willing to fix any of them.

You will also see many of the Sugar Javascript activities not
working.  That's because we don't have enough people with knowledge of
Javascript willing to fix them or Sugar.

Good luck.

On Sun, Mar 28, 2021 at 11:11:08AM +, Saurabh Gupta wrote:
> Thanks James for your quick response.
> 
> Actually, I am a developer in javascript so not much aware of how Sugar is
> built. Can you please help me with what do I have to do to run the Sugar
> activity so that I can use them and build them for Sugarizer. 
> What is the best possible way to run Sugar activities? Do I have to change my
> Ubuntu version?
> 
> On Sunday, 28 March, 2021, 03:46:06 pm IST, James Cameron 
> wrote:
> 
> Yes, that's expected.  activities.sugarlabs.org is for Python 2
> activities, and Ubuntu 20.10 does not have a Python 2 build of Sugar
> Toolkit.
> 
> Sugar Live Build has Python 2 build of Sugar Toolkit included.
> 
> Also does OLPC OS 20.04.
> 
> On Sun, Mar 28, 2021 at 06:13:04AM +, Saurabh Gupta wrote:
> > Hi everyone,
> >
> > I have installed Sugar 0.117 on Ubuntu 20.10 (Groovy Gorilla). All
> > pre-installed activities are working fine (i.e. Chat, Calculate, Browse,
> Write)
> > but when I download other activities from [1][1]http://
> activities.sugarlabs.org/
> > en-US/sugar/ and run .xo file it shows "Activity Name unable to Start". I
> have
> > tried using 3 activities (i.e. Measure-53.1, Speak-54, Story-19) but the 
> > same
> > error is showing on all three. Is there anything else we have to set up to
> run
> > activity from the xo file, I have gone through the docs but nothing is
> > mentioned regarding installing new activities.
> >
> > Regards
> >
> > Saurabh Gupta
> >
> > References:
> 
> >
> > [1] [2]http://activities.sugarlabs.org/en-US/sugar/
> 
> > ___
> > Sugar-devel mailing list
> > [3]Sugar-devel@lists.sugarlabs.org
> > [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [5]https://quozl.linux.org.au/
> 
> References:
> 
> [1] http://activities.sugarlabs.org/
> [2] http://activities.sugarlabs.org/en-US/sugar/
> [3] mailto:Sugar-devel@lists.sugarlabs.org
> [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> [5] https://quozl.linux.org.au/

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

Re: [Sugar-devel] Issue in adding activities in Sugar

[James Cameron]

Yes, that's expected.  activities.sugarlabs.org is for Python 2
activities, and Ubuntu 20.10 does not have a Python 2 build of Sugar
Toolkit.

Sugar Live Build has Python 2 build of Sugar Toolkit included.

Also does OLPC OS 20.04.

On Sun, Mar 28, 2021 at 06:13:04AM +, Saurabh Gupta wrote:
> Hi everyone,
> 
> I have installed Sugar 0.117 on Ubuntu 20.10 (Groovy Gorilla). All
> pre-installed activities are working fine (i.e. Chat, Calculate, Browse, 
> Write)
> but when I download other activities from [1]http://activities.sugarlabs.org/
> en-US/sugar/ and run .xo file it shows "Activity Name unable to Start". I have
> tried using 3 activities (i.e. Measure-53.1, Speak-54, Story-19) but the same
> error is showing on all three. Is there anything else we have to set up to run
> activity from the xo file, I have gone through the docs but nothing is
> mentioned regarding installing new activities.
> 
> Regards
> 
> Saurabh Gupta
> 
> References:
> 
> [1] http://activities.sugarlabs.org/en-US/sugar/

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


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

Re: [Sugar-devel] GSOC 2021

[James Cameron]

Welcome Innocent,

https://github.com/sugarlabs/GSoC/blob/master/Ideas-2021.md#port-aslov1-to-php8
is a project idea that requires PHP skills.

Sugar Labs also has a Django web app at
https://translate.sugarlabs.org/ that needs some attention; updating
to latest Django to fix vulnerabilities.

On Fri, Mar 26, 2021 at 02:02:45PM +0100, Innocent Onwukanjo wrote:
> Hi! 
> My name is Innocent. I am a final year student in the Department of Computer
> Engineering. I would love to participate in this year's Google Summer of Code
> with Sugar Labs. I have subscribed to the sugar-devel list and I have been
> reading tonnes of information but I just don't know where to start.
> In brief, I am learning DevOps Engineering backend web development using PHP 
> 7.
> ^ and Django. Although I am a newbie using Django. I am super interested to
> move from PHP to Python. So how do I start?

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


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

Re: [Sugar-devel] Porting sugar codebase to python3

[James Cameron]

Thanks.  Yes, certainly helpful.  We don't yet know if the problems we
face are caused by the port to Python 3 or something else.

Next steps are to get a traceback of the failing Telepathy processes
using gdb, and diagnose all the way back to lines of code in Telepathy.

On Thu, Mar 18, 2021 at 03:55:18PM -0700, Diane Trout wrote:
> Hi,
> 
> (I was just passing through looking at sugarizer information when I saw
> this post about telepathy.)
> 
> I know that there's been some progress on porting parts of telepathy to
> python3 over at 
> https://github.com/TelepathyIM/
> 
> I don't know if it's enough for sugar but it might be helpeful.
> 
> Hope this is helpful,
> Diane
> 
> 

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

Re: [Sugar-devel] GSoC 2021 aspirant

[James Cameron]

Latest is Sugar 0.118.

For Sugar 0.117 and 0.118, activities should be downloaded from
v4.activities.sugarlabs.org rather than activities.sugarlabs.org.

Yes, you always require consent of author.  You should be able to read
the copyright to find the author, and read the license to find
consent.

Etoys activity has not been ported to new shell or Python 3, so not
surprising that it does not work yet.

On Mon, Mar 15, 2021 at 05:14:59PM +0530, Sourabha G wrote:
> Hey everyone,
> I installed Sugar 0.117,
> 1. I was able to change the cursor theme on Ubuntu using gsettings, @Ibiam
> Chihurumnaya  and @James Cameron thanks for the guidance.
> 2. Most activities which are downloaded from [1]https://
> activities.sugarlabs.org/en-US/sugar  failed to start since they are not 
> tested
> on version 0.117 or maintained.
> To migrate a few activities like Etoys to github, is it required to take the
> consent of the author?
> The log files of turtle blocks were empty(even after trying to start it 
> several
> times), the shell.log file and log of Etoys is attached below.
> 
> thanks.
> 
> On Sun, Mar 14, 2021 at 3:16 AM Chihurumnaya Ibiam <[2]ib...@sugarlabs.org>
> wrote:
> 
> Hi Sourabha,
> 
> 1. Could you share the shell.log file, the issue mentioned has been fixed
>     but you should be able to change your mouse back with "gsettings set
> org.gnome.desktop.interface cursor-theme 'Adwaita'".
>     The shell.log file can be found at "/home/user/.sugar/default/logs/
> shell.log".
> 
> 2. Could you share the logs of  the activities that fail to start, they 
> can
> be found same place as the shell.log file,
>     etoys activity hasn't been used for quite some time now and it's repo
> isn't in Sugar Labs github, it does seem to have a
>     [3]gitorious instance but it hasn't been moved to Sugar Labs github.
> You can clone and upload on github and I'll fork your clone.
> 
> --
> 
> Ibiam Chihurumnaya
> [4]ib...@sugarlabs.org
>
> 
> On Sat, Mar 13, 2021 at 4:03 AM Sourabha G <[5]sourabha.proj...@gmail.com>
> wrote:
> 
> Hey everyone!
>  I'm Sourabha G from India.I'm an open source enthusiast ,looking
> forward to contributing to Sugar Labs. I have decent experience in
> python and want to contribute by fixing issues of few activities.
>  I installed Sugar desktop from [6]here, on Ubuntu 20.10.I'm facing 
> few
> issues like,
> 1.  The cursor on the Ubuntu environment has changed to Sugar custom
> cursor.
> 2. Turtle blocks, etoys and neko activities failed to start.
> I have attached a few pictures below for more clarity.
> Please guide me with the same.
> 
> Regards, 
> Sourabha G.
> ___
> Sugar-devel mailing list
> [7]Sugar-devel@lists.sugarlabs.org
> [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] https://activities.sugarlabs.org/en-US/sugar
> [2] mailto:ib...@sugarlabs.org
> [3] http://git.sugarlabs.org/etoys
> [4] mailto:ib...@sugarlabs.org
> [5] mailto:sourabha.proj...@gmail.com
> [6] https://github.com/sugarlabs/sugar
> [7] mailto:Sugar-devel@lists.sugarlabs.org
> [8] http://lists.sugarlabs.org/listinfo/sugar-devel



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


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

Re: [Sugar-devel] GSoC 2021 aspirant

[James Cameron]

What version of Sugar did you install?  Ubuntu 20.10 includes Sugar
0.117, but the cursor fix was in 0.117, see 32bc78437 ("Restore GNOME
cursor-theme on exit").

Make sure you do not run Sugar from within the Ubuntu desktop.  It is
not intended for that.

On Sat, Mar 13, 2021 at 08:33:05AM +0530, Sourabha G wrote:
> Hey everyone!
>  I'm Sourabha G from India.I'm an open source enthusiast ,looking forward to
> contributing to Sugar Labs. I have decent experience in python and want to
> contribute by fixing issues of few activities.
>  I installed Sugar desktop from [1]here, on Ubuntu 20.10.I'm facing few issues
> like,
> 1.  The cursor on the Ubuntu environment has changed to Sugar custom cursor.
> 2. Turtle blocks, etoys and neko activities failed to start.
> I have attached a few pictures below for more clarity.
> Please guide me with the same.
> 
> Regards, 
> Sourabha G.
> 
> References:
> 
> [1] https://github.com/sugarlabs/sugar





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


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

Re: [Sugar-devel] Porting sugar codebase to python3

[James Cameron]

Thanks for your interest.

You've probably not understood the scale and scope of the problem.

You should use Sugar, and use the peer to peer activity collaboration
feature.  You can find some instructions for it at
https://help.sugarlabs.org/en/collaborating.html

Collaboration uses the Telepathy library, and has a few problems.  We
don't yet know if the problems are in Telepathy or in Sugar, or if
they are related to or not related to the recent port to Python 3.

By using Sugar, you will see for yourself some of the problems that
occur.

Specifically, static bindings are "import telepathy", but dynamic
bindings are "from gi.repository import TelepathyGLib".

Look at https://github.com/orgs/sugarlabs/projects and search in page
for Telepathy.

The problems may require work on Telepathy itself, rather than Sugar.

On Sun, Mar 14, 2021 at 01:16:36AM +0530, ADITYA VATS wrote:
> Hello everyone at sugar !!
> Hope you all are doing well.
> 
> I want to contribute to sugar on implementing porting to py3 along with 
> porting
> telepathy bindings to telepathyglib bindings during GSoC21. I have studied the
> related sugar docs and references. However, I am still not much clear about 
> the
> latter one, i.e. telepathy bindings. 
> 
> I want to try my hands on this idea, but I couldn't find any suitable issue 
> for
> this. Could anyone please direct me towards any related issue where I can try
> this or to any implementation in code, just for starting out? 
> 
> Please do share any insights or advices you have regarding this.
> 
> Thanks
> 
> Aditya Vats

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


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

[Sugar-devel] Activity idea; infant protection from hazards

[James Cameron]

Yesterday heard a podcast about the product safety issues with coin
cell batteries, which can lodge, cause pain, and breach aorta.

https://www.abc.net.au/radionational/programs/backgroundbriefing/tiny-battery-kills-kids/13145142

Imagine an activity for older children to protect the very young by
locating and isolating coin cells along with other dangerous items,
like rare earth magnets, pills, and throat-sized objects.

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

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

Thanks.  I agree.

Would a technical writer alone be suitable, or must a technical writer
be combined with a teacher?  There's a risk that by placing domain
specific limitations on the project, we make it harder for GSoD to
choose us.

What mode of delivery is best suited to teachers; written manuals,
lesson plans, onscreen walkthroughs, or stand up lectures?  There's a
risk that GSoD candidates will concentrate on written documentation.

How do we emphasise constructivism, constructionism, or constructivist
teaching methods?  Is there a degree or certification we can require?

On Mon, Feb 15, 2021 at 06:52:53PM -0500, Walter Bender wrote:
> Apologies for my late response to this thread.
> 
> Regarding documentation, I think we have a major hole to fill in
> Sugar, Music Blocks, and Sugarizer: supporting materials for teachers.
> While we have docs for the individual components, we could go a long
> ways towards giving some structure to a teacher who might want to
> build a comprehensive program out of any of our major subsystems.
> 
> -walter
> 
> On Wed, Feb 10, 2021 at 4:31 AM James Cameron  wrote:
> >
> > Yes.  Please make a list of content if none is available and content
> > that should be demystified?
> >
> > On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> > > Anyone can correct me if I am wrong. But the point of Season of Docs is
> > >
> > > 1. Generate content if none is available.
> > > 2. Very important is looking at the existing content and demystify it to 
> > > the
> > > nearest minimum (Sugar Labs needs this)
> > >
> > > The idea for a technical writer is to simplify and transfer information 
> > > between
> > > Sugar Labs and anyone consuming the content.
> > >
> > > To you, the content may look fine because you may not be the target, or 
> > > in this
> > > case, you are an author of some of the tools generated.
> > >
> > > Having great doc is a demanding requirement for onboarding in open 
> > > source, and
> > > unfortunately, I can't say Sugar Labs has one(simplifications).
> > >
> > > Also a completely different from GSoC.
> > >
> > > On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org> wrote:
> > >
> > > My first question was the most important.
> > >
> > > I can't think of any documentation Sugar Labs needs that we haven't
> > > already got in some form or other across our sprawling web presence.
> > >
> > > I recommend against proceeding unless some documentation is needed.
> > >
> > > On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > > > Hello James,
> > > >
> > > > I read the documentation, yes it looks like a grant based program 
> > > this
> > > time
> > > > around.
> > > >
> > > > Just as I mentioned last year, I would love to admin the program, 
> > > or be
> > > one of
> > > > the admins.
> > > >
> > > > I am working on a system in place already.
> > > >
> > > > Regards
> > > >
> > > > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]qu...@laptop.org>
> > > wrote:
> > > >
> > > > Indeed.  So the question becomes;
> > > >
> > > > - what documentation does Sugar Labs need (e.g. for Sugarizer, 
> > > Music
> > > >   Blocks, or Sugar); this forms part of a project proposal,
> > > >
> > > > - who will recruit, evaluate, and onboard a technical writer?
> > > >
> > > > - who will administer the program in Sugar Labs?
> > > >
> > > > 
> > > [2][3]https://developers.google.com/season-of-docs/docs/admin-guide
> > > >
> > > > On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > > > > It is being organized differently this year; we have to apply 
> > > for a
> > > grant
> > > > and
> > > > > then we find the writer we reach out directly to the writer 
> > > we want
> > > to
> > >     > work
> > > > > with, at least that is how I understood it.
> > > > >
> > > > > [1][3][4]https://opensource.googleblog.com/2021/02/
> > > >   

Re: [Sugar-devel] Issue with filename written in Spanish

[James Cameron]

Yes.  Please test
https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/457

On Fri, Feb 12, 2021 at 04:15:44AM +0100, Chihurumnaya Ibiam wrote:
> While creating the source file for flipsticks an error is thrown about certain
> files not being found; 
> 
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/home/ibiam/Activities
> /flipsticks/"lessons/es/Introducci\\303\\263n.txt"'
> 
> This file doesn't exist because the file that exists doesn't have those
> additions to it and it seems to be because of the accent added to "i" in files
> in lessons/es/, one easy solution would be to rename the files but that would
> mean we can't have files with certain names and it makes sense to have those
> files with the names they have.
> 
> git ls-files shows the files are stored as;
> 
> "lessons/es/Introducci\303\263n.txt"
> "lessons/es/Plan_de_Lecci\303\263n_1.txt"
> "lessons/es/Plan_de_Lecci\303\263n_2.txt"
> "lessons/es/Plan_de_Lecci\303\263n_3.txt"
> 
> The implication of this is the source file gets created but without some files
> like setup.py which is needed to build activities in SOAS.
> 
> Has anyone faced a similar problem before?
> 
> --
> 
> Ibiam Chihurumnaya
> [1]ibiamchihurumn...@gmail.com
> 
> References:
> 
> [1] mailto:ibiamchihurumn...@gmail.com

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


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

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

Yes.  Please make a list of content if none is available and content
that should be demystified?

On Wed, Feb 10, 2021 at 10:07:45AM +0100, Samson Goddy wrote:
> Anyone can correct me if I am wrong. But the point of Season of Docs is 
> 
> 1. Generate content if none is available. 
> 2. Very important is looking at the existing content and demystify it to the
> nearest minimum (Sugar Labs needs this)
> 
> The idea for a technical writer is to simplify and transfer information 
> between
> Sugar Labs and anyone consuming the content. 
> 
> To you, the content may look fine because you may not be the target, or in 
> this
> case, you are an author of some of the tools generated. 
> 
> Having great doc is a demanding requirement for onboarding in open source, and
> unfortunately, I can't say Sugar Labs has one(simplifications). 
> 
> Also a completely different from GSoC. 
> 
> On Wed, Feb 10, 2021, 9:59 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> My first question was the most important.
> 
> I can't think of any documentation Sugar Labs needs that we haven't
> already got in some form or other across our sprawling web presence.
> 
> I recommend against proceeding unless some documentation is needed.
> 
> On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> > Hello James,
> >
> > I read the documentation, yes it looks like a grant based program this
> time
> > around.
> >
> > Just as I mentioned last year, I would love to admin the program, or be
> one of
> > the admins. 
> >
> > I am working on a system in place already. 
> >
> > Regards
> >
> > On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1][2]qu...@laptop.org>
> wrote:
> >
> >     Indeed.  So the question becomes;
> >
> >     - what documentation does Sugar Labs need (e.g. for Sugarizer, Music
> >       Blocks, or Sugar); this forms part of a project proposal,
> >
> >     - who will recruit, evaluate, and onboard a technical writer?
> >
> >     - who will administer the program in Sugar Labs?
> >
> >     [2][3]https://developers.google.com/season-of-docs/docs/admin-guide
> >
> >     On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> >     > It is being organized differently this year; we have to apply for 
> a
> grant
> >     and
> >     > then we find the writer we reach out directly to the writer we 
> want
> to
> >     work
> >     > with, at least that is how I understood it. 
> >     >
> >     > [1][3][4]https://opensource.googleblog.com/2021/02/
> >     > 
> the-2021-season-of-docs-application-for-organizations-is-open.html?
> m=1
> >     >
> >     > [2][4][5]https://developers.google.com/season-of-docs/docs/
> tech-writer-guide
> >     >
> >     > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5][6]
> 2017...@iiitdmj.ac.in>
> >     wrote:
> >     >
> >     >     I think it is a great idea. Sugar labs should take part in
> GSoD.
> >     >
> >     >     Regards
> >     >     Saumya Mishra
> >     >
> >     >     On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4][6][7]
> qu...@laptop.org
> >     > wrote:
> >     >
> >     >         It's back.  Can we win a slot this year?  Ideas welcome.
> >     >
> >     >         [5][7][8]https://opensource.googleblog.com/2021/02/
> >     >       
> >      the-2021-season-of-docs-application-for-organizations-is-open.html
> >     >         [6][8][9]https://developers.google.com/season-of-docs
> >     >
> >     >         --
> >     >         James Cameron
> >     >         [7][9][10]https://quozl.linux.org.au/
> >     >         ___
> >     >         Sugar-devel mailing list
> >     >         [8][10][11]Sugar-devel@lists.sugarlabs.org
> >     >         [9][11][12]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     >
> >     >     ___
> >     >     Sugar-devel mailing list
> >     >     [10][12][13]Sugar-devel@lists.sugarlabs.org
> >     >     [11][13][14]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

My first question was the most important.

I can't think of any documentation Sugar Labs needs that we haven't
already got in some form or other across our sprawling web presence.

I recommend against proceeding unless some documentation is needed.

On Wed, Feb 10, 2021 at 09:42:40AM +0100, Samson Goddy wrote:
> Hello James,
> 
> I read the documentation, yes it looks like a grant based program this time
> around.
> 
> Just as I mentioned last year, I would love to admin the program, or be one of
> the admins. 
> 
> I am working on a system in place already. 
> 
> Regards
> 
> On Wed, Feb 10, 2021, 9:33 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Indeed.  So the question becomes;
> 
> - what documentation does Sugar Labs need (e.g. for Sugarizer, Music
>   Blocks, or Sugar); this forms part of a project proposal,
> 
> - who will recruit, evaluate, and onboard a technical writer?
> 
> - who will administer the program in Sugar Labs?
> 
> [2]https://developers.google.com/season-of-docs/docs/admin-guide
> 
> On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> > It is being organised differently this year, we have to apply for a 
> grant
> and
> > then we find the writer we reach out directly to the writer we want to
> work
> > with, at least that is how I understood it. 
> >
> > [1][3]https://opensource.googleblog.com/2021/02/
> > the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> >
> > 
> [2][4]https://developers.google.com/season-of-docs/docs/tech-writer-guide
> >
> > On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3][5]2017...@iiitdmj.ac.in>
> wrote:
> >
> >     I think it is a great idea. Sugar labs should take part in GSoD.
> >
> >     Regards
> >     Saumya Mishra
> >
> >     On Wed, Feb 10, 2021 at 7:05 AM James Cameron 
> <[4][6]qu...@laptop.org
> > wrote:
> >
> >         It's back.  Can we win a slot this year?  Ideas welcome.
> >
> >         [5][7]https://opensource.googleblog.com/2021/02/
> >       
>  the-2021-season-of-docs-application-for-organizations-is-open.html
> >         [6][8]https://developers.google.com/season-of-docs
> >
> >         --
> >         James Cameron
> >         [7][9]https://quozl.linux.org.au/
> >         ___
> >         Sugar-devel mailing list
> >         [8][10]Sugar-devel@lists.sugarlabs.org
> >         [9][11]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >     ___
> >     Sugar-devel mailing list
> >     [10][12]Sugar-devel@lists.sugarlabs.org
> >     [11][13]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] [14]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> > [2] [15]https://developers.google.com/season-of-docs/docs/
> tech-writer-guide
> > [3] mailto:[16]2017...@iiitdmj.ac.in
> > [4] mailto:[17]qu...@laptop.org
> > [5] [18]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html
> > [6] [19]https://developers.google.com/season-of-docs
> > [7] [20]https://quozl.linux.org.au/
> > [8] mailto:[21]Sugar-devel@lists.sugarlabs.org
> > [9] [22]http://lists.sugarlabs.org/listinfo/sugar-devel
> > [10] mailto:[23]Sugar-devel@lists.sugarlabs.org
> > [11] [24]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [25]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [26]Sugar-devel@lists.sugarlabs.org
> [27]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] https://developers.google.com/season-of-docs/docs/admin-guide
> [3] https://opensource.googleblog.com/2021/02/
> [4] https://developers.google.com/season-of-docs/docs/tech-writer-guide
> [5] mailto:2017...@iiitdmj.ac.in
> [6] mailto:qu...@laptop.org
> [7] https://opensource.googleblog.com/2021/02/
> [8] https://developers.google.com/season-of-docs
> [9] https://quozl.linux.org.au/
> [10] mailto:Sugar-devel@lists.sugarlabs.org
> [11] http://lists.sugarlabs.org/listinfo/sugar-devel
> [12] mailto:Sugar-devel@lists.sugarlabs.org
> 

Re: [Sugar-devel] Google Season of Docs

[James Cameron]

Indeed.  So the question becomes;

- what documentation does Sugar Labs need (e.g. for Sugarizer, Music
  Blocks, or Sugar); this forms part of a project proposal,

- who will recruit, evaluate, and onboard a technical writer?

- who will administer the program in Sugar Labs?

https://developers.google.com/season-of-docs/docs/admin-guide

On Wed, Feb 10, 2021 at 08:48:21AM +0100, Favour Kelvin wrote:
> It is being organised differently this year, we have to apply for a grant and
> then we find the writer we reach out directly to the writer we want to work
> with, at least that is how I understood it. 
> 
> [1]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> 
> [2]https://developers.google.com/season-of-docs/docs/tech-writer-guide
> 
> On Wed, 10 Feb 2021, 06:18 Saumya Mishra, <[3]2017...@iiitdmj.ac.in> wrote:
> 
> I think it is a great idea. Sugar labs should take part in GSoD.
> 
> Regards
> Saumya Mishra
> 
> On Wed, Feb 10, 2021 at 7:05 AM James Cameron <[4]qu...@laptop.org> wrote:
> 
> It's back.  Can we win a slot this year?  Ideas welcome.
> 
> [5]https://opensource.googleblog.com/2021/02/
> the-2021-season-of-docs-application-for-organizations-is-open.html
>     [6]https://developers.google.com/season-of-docs
> 
> --
> James Cameron
> [7]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [8]Sugar-devel@lists.sugarlabs.org
> [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> ___
> Sugar-devel mailing list
> [10]Sugar-devel@lists.sugarlabs.org
> [11]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] 
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html?m=1
> [2] https://developers.google.com/season-of-docs/docs/tech-writer-guide
> [3] mailto:2017...@iiitdmj.ac.in
> [4] mailto:qu...@laptop.org
> [5] 
> https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
> [6] https://developers.google.com/season-of-docs
> [7] https://quozl.linux.org.au/
> [8] mailto:Sugar-devel@lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel
> [10] mailto:Sugar-devel@lists.sugarlabs.org
> [11] http://lists.sugarlabs.org/listinfo/sugar-devel

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

[Sugar-devel] Google Season of Docs

[James Cameron]

It's back.  Can we win a slot this year?  Ideas welcome.

https://opensource.googleblog.com/2021/02/the-2021-season-of-docs-application-for-organizations-is-open.html
https://developers.google.com/season-of-docs

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

Re: [Sugar-devel] Sugar Sponsor

[James Cameron]

On Tue, Feb 09, 2021 at 10:19:30PM +, D. Joe wrote:
> On Wed, Feb 10, 2021 at 08:33:18AM +1100, James Cameron wrote:
> >  Ian hasn't made any commits to activities yet, so I
> > didn't think it likely he wanted a shell account.)
> 
> This goes to my main point: 
> 
> I suspect 
> 
> a) the requirements Ian faces might be satisfied by making commits
> and successful pull requests

I agree.

> and 
> 
> b) Ian might be better served by looking at, eg, the information
> provided under "Join Us" rather than whatever led us to talking
> about account creation.

Yes.  I also sent Ian a copy of
https://github.com/sugarlabs/sugar-docs/blob/master/src/sugar-labs-developer-howto.txt

> 
> Was it made clear in the email to the sysadmin@ alias that an
> account wasn't just requested, but would be required for work with
> sugarlabs to qualify for the course?

It was the same text.  It looks like normal preparatory work made
complicated by our sprawling web presence.  I know what that's like, I
see it in other institutions.

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

Re: [Sugar-devel] Sugar Sponsor

[James Cameron]

On Tue, Feb 09, 2021 at 06:49:49PM +, D. Joe wrote:
> On Thu, Feb 04, 2021 at 08:58:42AM -0500, Ian Dudderar wrote:
> > Greetings! 
> > I am working with the computer science department of the College
> > of Charleston.  For our class, me and my group members are
> > required to provide input on an open source project and we have
> > chosen sugar. We would like to contribute in any way possible, and
> > were wondering if we might be able to get access to a service
> > account. The website states we would need a sponsor from a
> > member. How can we get one?
> 
> Hi,
> 
> When you say "the website" could you be more specific? Sugar has a
> rather sprawling web presence some of which is more currently
> maintained than other parts.
> 
> For instance, on what I consider the "main" page,
> https://www.sugarlabs.org a search reveals no instances of the word
> "sponsor" at all.
> 
> I'd suggest, if you're truly open to offering any of a variety of
> contributions that you take a look at the Join Us section from the
> top of that page and see if something there might be helpful.
> 
> Looking through each page available from that menu I also did not
> find mention of sponsors. I don't doubt that there is mention of
> them somewhere (eg, accounts on sugarlabs machines to which James
> refers) but it's not clear to me why you'd drill all the way down to
> asking after that.

We also got a request via the sysadmin@ alias, but as the request was
made public on the mailing list I felt it was better to respond on the
mailing list.

https://wiki.sugarlabs.org/go/Service/Account is probably where Ian's
"service account" comes from.  It's an easy mistake to make;
assuming a Wiki page title is well understood across the sprawling web
presence.

The account types could be Wiki, Shell, or Mail.

(At the moment, people need shell accounts to publish Python 3 activity
releases to v4.activities.sugarlabs.org.  We could set up accounts
with preloaded commands in authorized_keys to do this, eventually.
But for the moment I've been avoiding creating accounts and doing the
releases myself.  Ian hasn't made any commits to activities yet, so I
didn't think it likely he wanted a shell account.)

> 
> -- 
> D. Joe
> 
> 
> _______
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

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

Re: [Sugar-devel] Jukebox activity collaboration UX review

[James Cameron]

Thanks Kunal.

I'm not sure if you've used collaboration in a Sugar activity before.
Points 1 to 3 of your list are already handled by Sugar and the
Toolkit, so they are out of scope for the issue.

Also, I think the most important collaboration feature would be to see
and hear the same thing at the same time.

I'll update the issue.

On Wed, Feb 10, 2021 at 02:31:41AM +0530, Kunal Sharma wrote:
> Hello maintainers, 
> I am Kunal Sharma and my Github is [1]dbzkunalss.
> With respect to the issue: [2]Add collaboration for sharing playlist items #22
> in [3]jukebox-activity, I would like to put forth my User Experience proposal
> for review.
> 
> Proposed UX:
> 
>  1. Ability to share jukebox activity to the neighborhood.
>  2. Ability to invite users to the activity.
>  3. Ability to accept the invitation.
>  4. Ability to collaborate on adding or removing tracks using "+" and "-"
> buttons on the top bar.
>  5. Ability to collaborate on rearranging the playlist items/tracks using up
> and down arrow buttons on the bottom bar.
> 
> Upon your confirmation, I would like to work on the implementation by getting
> the issue assigned to me. Please let me know if there are any changes.
> Thank you!
> 
> Regards,
> Kunal Sharma
> [4]Twitter | [5]Github | [6]LinkedIn
> 
> References:
> 
> [1] https://github.com/dbzkunalss
> [2] https://github.com/sugarlabs/jukebox-activity/issues/22
> [3] https://github.com/sugarlabs/jukebox-activity
> [4] https://twitter.com/dbzkunalss
> [5] https://github.com/dbzkunalss
> [6] https://www.linkedin.com/in/kunalsharma3300/

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


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

Re: [Sugar-devel] [ASLOv4] [RELEASE] Flappy - 5

[James Cameron]

Thanks.  Could you give a bit more detail, as an issue or pull
request?  Were you testing master branch HEAD or latest release v3q?
What operating system and release?  Did you see the known issues or
have they been fixed?
https://github.com/sugarlabs/flappy-birds-activity/issues

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities
and
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#testing
have a list of things you might check.

On Mon, Feb 08, 2021 at 05:07:42PM +0530, Aditya sinha wrote:
> I forgot to mention one thing. The other Flappy game was also working 
> perfectly
> and passed  all the tests. It is also ready for release.

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


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

Re: [Sugar-devel] Sugar Sponsor

[James Cameron]

Welcome.

You can contribute individually and as a group in many ways, through
GitHub accounts.  We have split Sugar Labs accounts now into multiple
services.  What specifically do you need a Sugar Labs account for, and
what service do you need access to?

On Thu, Feb 04, 2021 at 08:58:42AM -0500, Ian Dudderar wrote:
> Greetings! 
> I am working with the computer science department of the College of
> Charleston.  For our class, me and my group members are required to
> provide input on an open source project and we have chosen sugar. We
> would like to contribute in any way possible, and were wondering if
> we might be able to get access to a service account. The website
> states we would need a sponsor from a member. How can we get one?
> 
> Thanks,
> Ian Dudderar

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


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

Re: [Sugar-devel] Question about Criteria of GSoC'21 Ideas

[James Cameron]

Some of us know rocket-science.

No, it's all about the mentors.  Do we have coding mentors who have
the skills and willingness; i.e. the capacity to mentor the idea.

Because one of the steps during proposal evaluation is for a mentor to
select a proposal they are willing to mentor.

Remember also that a proposal could be for a project idea that is not
in our list of ideas.  We received several such last year.  We had to
think carefully about whether we could mentor them.

On Wed, Feb 03, 2021 at 12:11:39PM +0530, Aditya Pratap Singh wrote:
> So, the idea shouldn't be requiring rocket-science level knowledge and should
> lay down concrete guidelines on what is to be implemented?
> 
> On Wed, 3 Feb 2021, 12:08 pm James Cameron, <[1]qu...@laptop.org> wrote:
> 
> Sure.  I wrote it, as you can see from "git blame" on the previous
> years' iterations of the file.
> 
> [2]https://github.com/sugarlabs/GSoC/blame/master/Ideas-2019.md#L775
> 
> At Sugar Labs we have a long history with Google Summer of Code, and
> there are some anti-patterns in ideas that can lead to the idea
> failing to proceed, the project failing to deliver, or the software not
> being deployed.
> 
> 1.  an idea for which we do not have the skills; we can't explain to a
> student how to do it, and we can't easily help the student when they
> are blocked, which can leave the student feeling very uncertain and
> not finishing their work on time,
> 
> 2.  an idea that has not been fully developed as an idea; a sort of
> speculative idea; we then don't have the developers willing to test
> the design and implementation by the student, and so the project is
> completed without net benefit to Sugar Labs,
> 
> By the way, "can promise" does not mean "will promise"; it is about
> capacity of mentors.
> 
> Does that help explain my statement?
> 
> On Wed, Feb 03, 2021 at 11:51:46AM +0530, Aditya Pratap Singh wrote:
> > Can someone explain what this statement means?
> >
> >     Do we have a developer now who would be willing and able to do it if
> a
> >     student was not available, and who can promise to do it if a student
> is not
> >     selected; these are shown as a coding mentor,
> >
> > [1]Source
> >
> > References:
> >
> > [1] [3]https://github.com/sugarlabs/GSoC/blob/master/Ideas-2021.md#
> criteria-for-ideas
> 
>     > ___
> > Sugar-devel mailing list
> > [4]Sugar-devel@lists.sugarlabs.org
> > [5]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [6]https://quozl.linux.org.au/
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] https://github.com/sugarlabs/GSoC/blame/master/Ideas-2019.md#L775
> [3] 
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2021.md#criteria-for-ideas
> [4] mailto:Sugar-devel@lists.sugarlabs.org
> [5] http://lists.sugarlabs.org/listinfo/sugar-devel
> [6] https://quozl.linux.org.au/

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


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

Re: [Sugar-devel] Question about Criteria of GSoC'21 Ideas

[James Cameron]

Sure.  I wrote it, as you can see from "git blame" on the previous
years' iterations of the file.

https://github.com/sugarlabs/GSoC/blame/master/Ideas-2019.md#L775

At Sugar Labs we have a long history with Google Summer of Code, and
there are some anti-patterns in ideas that can lead to the idea
failing to proceed, the project failing to deliver, or the software not
being deployed.

1.  an idea for which we do not have the skills; we can't explain to a
student how to do it, and we can't easily help the student when they
are blocked, which can leave the student feeling very uncertain and
not finishing their work on time,

2.  an idea that has not been fully developed as an idea; a sort of
speculative idea; we then don't have the developers willing to test
the design and implementation by the student, and so the project is
completed without net benefit to Sugar Labs,

By the way, "can promise" does not mean "will promise"; it is about
capacity of mentors.

Does that help explain my statement?

On Wed, Feb 03, 2021 at 11:51:46AM +0530, Aditya Pratap Singh wrote:
> Can someone explain what this statement means?
> 
> Do we have a developer now who would be willing and able to do it if a
> student was not available, and who can promise to do it if a student is 
> not
> selected; these are shown as a coding mentor,
> 
> [1]Source
> 
> References:
> 
> [1] 
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2021.md#criteria-for-ideas

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


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

[Sugar-devel] linux.conf.au 2021

[James Cameron]

Talks and keynotes from linux.conf.au 2021 are being uploaded.

https://yewtu.be/channel/UCciKHCG06rnq31toLTfAiyw

I attended the conference remote along with everyone else.  What I've
seen so far that I can recommend for Sugar Labs members;

* keynotes by Cory Doctorow, Limor Fried (Adafruit) and Omoju Miller
  (GitHub).

* a talk by Neil McGovern, director of the GNOME Foundation, on a
  patent suit,

* a talk by Sumana Harihareswara, on how to get a project unstuck and
  fixing the skill gaps that got us here,

* by Katie Bell, "What even is code? Building a non-code coding
  interface"

* by Robin Willison, a tour of the Adelaide Makerspace, an adult
  learning environment,

* by Mars Buttfield-Addison, "Radio Astronomy for Programmers",
  dealing with unusual graphics coordinate systems,

* by Jeremy Kerr, "Server platforms: experiment with your expensive
  hardware too!",

* by Paul Gardner-Stephen, "Digital Sovereignty: We need devices we
  truly own more than ever",

* by Sanchayan Maity, "What's next for Bluetooth in PulseAudio?"

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

Re: [Sugar-devel] Entry to GSoC 2021

[James Cameron]

Thanks for your contribution.  I've forked your tictactoe into the
Sugar Labs organisation.

On Sun, Jan 31, 2021 at 09:35:30PM +0530, Aditya Pratap Singh wrote:
> Hello, My name is Aditya Pratap Singh, and I am a BTech fresher at 
> Indraprastha
> Institute of Information Technology, Delhi.
> 
> I have a decent experience in C++ and Python. I've been using Arch for over a
> year now.
> 
> I am very much interested in participating in GSoC 2021. The main reason for
> doing GSoC is to get exposure to the developer's world and work with new
> people. I hope that, despite me being a fresher, the SugarLabs community
> welcomes me.
> 
> This is my current contribution to SugarLabs:
> 1) Resolved [1]this issue.
> 2) Made a [2]SugarLabs extension.
> I am looking forward to working with SugarLabs.
> 
> Regards
> Aditya Pratap Singh
> 
> References:
> 
> [1] https://github.com/sugarlabs/iknowmyabcs/issues/15
> [2] https://github.com/devmrfitz/tictactoe

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


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

Re: [Sugar-devel] GSoC 2021 Ideas

[James Cameron]

GSoC 2021 is now accepting applications from mentoring organisations.

Sugar Labs has until 19th February to apply.

We still need ideas.

On Fri, Jan 15, 2021 at 06:50:55PM +1100, James Cameron wrote:
> We need ideas for GSoC this year.  Let's get started.
> 
> Change from last year; projects are 175 hours rather than 350 hours.
> 
> Use ideas from previous years, or make new ideas.
> 
> Make a new Ideas-2021.md file in our repository
> https://github.com/sugarlabs/GSoC using a pull request.
> 
> File README.md also needs a few changes.  You can read the commit
> history of changes to the file to see what changed last year.
> 
> Applications by organisations are from 29th January to 19th February.
> 
> Organisation administrators this year are Jui, Perrie and Lionel.
> 
> -- 
> James Cameron
> https://quozl.linux.org.au/

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

Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!

[James Cameron]

On Wed, Jan 27, 2021 at 08:04:41AM +0300, Srevin Saju wrote:
> reply inline.

me too.

> 
> On 1/27/21 3:09 AM, James Cameron wrote:
> > On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
> > > And now, (Thanks bernie_!), we can use
> > > https://v4.activities.sugarlabs.org/services/update-aslo.php for 
> > > supporting
> > > sugar's microformat update system as mentioned below:
> > > 
> > > >* support Sugar's microformat software upgrade feature in My
> > > >  Settings, (Sugar 0.116 is configured
> > > >  in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
> > > >  in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
> > > >  script|update-aslo.php|, and will instead be configured to
> > > >  use|src/jarabe/model/update/microformat.py|),
> > I've reviewed the output of update-aslo.php briefly.  For Implode it
> > gives a minVersion of 0.116 and a maxVersion of 0.117.  How does an
> > activity author specify these values?
> 
> Right now, its hardcoded into 
> https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55.
> Let me know what would be the best implementation.

I'm in doubt.  I had previously asked that we not be required to
change activity metadata, yet activity metadata is a great place to
put this.  What do you think?

Perhaps each new release should be interpreted as being for the
current version, if such metadata is missing.

https://developer.sugarlabs.org/sugar3/sugar3.bundle.html is our
activity metadata documentation.

https://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles
is also documentation.

In the history of edits to the Wiki, we had a host_version metadata
item to specify the version of Sugar, but it was not implemented.

So perhaps min_sugar_version and max_sugar_version are needed.

On the other hand, aslo.py does _not check_ the minVersion and
maxVersion values.

For the time being, you can set them both to 0.118.

With aslo.py not checking the value, it doesn't yet matter.

> 
> > 
> > http://www.w3.org/1999/02/22-rdf-syntax-ns#; 
> > xmlns:em="http://www.mozilla.org/2004/em-rdf#;>
> >   > about="urn:mozilla:extension:com.jotaro.ImplodeActivity">
> >  
> >  
> >   > resource="urn:mozilla:extension:com.jotaro.ImplodeActivity:20.1.1~quozl"/>
> >  
> >  
> >  
> >   > about="urn:mozilla:extension:com.jotaro.ImplodeActivity:20.1.1~quozl">
> >  20.1.1~quozl
> >  
> >  
> >  {9e5ecf85-6bb9-4403-bae8-d6865f19677b}
> >  0.116
> >  0.117
> >  
> > https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo
> >  198
> >  
> > https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html
> >  
> > sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe
> >  
> >  
> >  
> > 
> > 
> > 
> > > On 1/21/21 10:03 AM, Srevin Saju wrote:
> > > > Right. I will configure ASLO-v4 to email sugar-devel@ with release
> > > > notifications.
> > > > Thanks to all developers, mentors who helped me out with this. Had a
> > > > great experience working with it!!!
> > > > 
> > > > On 1/21/21 10:00 AM, James Cameron wrote:
> > > > > Thanks, great work.  Merged 204.
> > > > > 
> > > > > I've also updated Browse.
> > > > > 
> > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
> > > > > 
> > > > > 
> > > > > I would prefer new version notifications to go to
> > > > > sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
> > > > > previously.  a...@lists.sugarlabs.org was for handling by library
> > > > > editors, but we don't have any active, and we don't have the same
> > > > > process with v4.
> > > > > 
> > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
> > > > > > G'day!
> > > > > > 
> > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
> > > > > > ... with only
> > > > > > a few more minor tidying up, ASLO-v4 will be ready for production.
> > > > > &g

Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!

[James Cameron]

On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
> And now, (Thanks bernie_!), we can use
> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting
> sugar's microformat update system as mentioned below:
> 
> >   * support Sugar's microformat software upgrade feature in My
> > Settings, (Sugar 0.116 is configured
> > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
> > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
> > script|update-aslo.php|, and will instead be configured to
> > use|src/jarabe/model/update/microformat.py|),

I've reviewed the output of update-aslo.php briefly.  For Implode it
gives a minVersion of 0.116 and a maxVersion of 0.117.  How does an
activity author specify these values?


http://www.w3.org/1999/02/22-rdf-syntax-ns#; 
xmlns:em="http://www.mozilla.org/2004/em-rdf#;>








20.1.1~quozl


{9e5ecf85-6bb9-4403-bae8-d6865f19677b}
0.116
0.117

https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo
198

https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html

sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe






> > 
> On 1/21/21 10:03 AM, Srevin Saju wrote:
> > Right. I will configure ASLO-v4 to email sugar-devel@ with release
> > notifications.
> > Thanks to all developers, mentors who helped me out with this. Had a
> > great experience working with it!!!
> > 
> > On 1/21/21 10:00 AM, James Cameron wrote:
> > > Thanks, great work.  Merged 204.
> > > 
> > > I've also updated Browse.
> > > 
> > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
> > > 
> > > 
> > > I would prefer new version notifications to go to
> > > sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
> > > previously.  a...@lists.sugarlabs.org was for handling by library
> > > editors, but we don't have any active, and we don't have the same
> > > process with v4.
> > > 
> > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
> > > > G'day!
> > > > 
> > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
> > > > ... with only
> > > > a few more minor tidying up, ASLO-v4 will be ready for production.
> > > > 
> > > > Activity maintainers can now push their bundles to ASLO-v4 by
> > > > following the
> > > > instructions on
> > > > https://wiki.sugarlabs.org/go/Service/activities4 as well
> > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
> > > > Please feel free to reach out, so that I can improve the existing
> > > > documentation, or anything you think is too complex.
> > > > 
> > > > Next steps:
> > > > 
> > > >   * Connect services/update-aslo.php and deploy a flask server (I am
> > > >     trying to get a hold of some more good apache knowledge)
> > > >   * Sending "new version detected" emails to a...@lists.sugarlabs.org,
> > > >     or should we create a new mailing list?
> > > > 
> > > > -- 
> > > > Srevin Saju
> > > > https://srevinsaju.me
> > > > 
> > > pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
> > > 
> > > > sub   RSA 4096/14479587 2020-05-19
> > > > 
> > > 
> > > 
> > > 
> > > > ___
> > > > Systems mailing list
> > > > syst...@lists.sugarlabs.org
> > > > http://lists.sugarlabs.org/listinfo/systems
> > > 
> > > 
> > > ___
> > > Sugar-devel mailing list
> > > Sugar-devel@lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> -- 
> Srevin Saju
> https://srevinsaju.me
> 

pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) 

> sub   RSA 4096/14479587 2020-05-19
> 




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


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

Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!

[James Cameron]

On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
> And now, (Thanks bernie_!), we can use
> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting
> sugar's microformat update system as mentioned below:
> 
> >   * support Sugar's microformat software upgrade feature in My
> > Settings, (Sugar 0.116 is configured
> > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
> > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
> > script|update-aslo.php|, and will instead be configured to
> > use|src/jarabe/model/update/microformat.py|),

https://github.com/sugarlabs/sugar/pull/939

Needs testing.  I've used tcpdump and saw no evidence of connection to
port 443, so I'm yet to dig into how to reconfigure my Sugar install.

> > 
> On 1/21/21 10:03 AM, Srevin Saju wrote:
> > Right. I will configure ASLO-v4 to email sugar-devel@ with release
> > notifications.
> > Thanks to all developers, mentors who helped me out with this. Had a
> > great experience working with it!!!
> > 
> > On 1/21/21 10:00 AM, James Cameron wrote:
> > > Thanks, great work.  Merged 204.
> > > 
> > > I've also updated Browse.
> > > 
> > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
> > > 
> > > 
> > > I would prefer new version notifications to go to
> > > sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
> > > previously.  a...@lists.sugarlabs.org was for handling by library
> > > editors, but we don't have any active, and we don't have the same
> > > process with v4.
> > > 
> > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
> > > > G'day!
> > > > 
> > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
> > > > ... with only
> > > > a few more minor tidying up, ASLO-v4 will be ready for production.
> > > > 
> > > > Activity maintainers can now push their bundles to ASLO-v4 by
> > > > following the
> > > > instructions on
> > > > https://wiki.sugarlabs.org/go/Service/activities4 as well
> > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
> > > > Please feel free to reach out, so that I can improve the existing
> > > > documentation, or anything you think is too complex.
> > > > 
> > > > Next steps:
> > > > 
> > > >   * Connect services/update-aslo.php and deploy a flask server (I am
> > > >     trying to get a hold of some more good apache knowledge)
> > > >   * Sending "new version detected" emails to a...@lists.sugarlabs.org,
> > > >     or should we create a new mailing list?
> > > > 
> > > > -- 
> > > > Srevin Saju
> > > > https://srevinsaju.me
> > > > 
> > > pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
> > > 
> > > > sub   RSA 4096/14479587 2020-05-19
> > > > 
> > > 
> > > 
> > > 
> > > > ___
> > > > Systems mailing list
> > > > syst...@lists.sugarlabs.org
> > > > http://lists.sugarlabs.org/listinfo/systems
> > > 
> > > 
> > > ___
> > > Sugar-devel mailing list
> > > Sugar-devel@lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> -- 
> Srevin Saju
> https://srevinsaju.me
> 

pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) 

> sub   RSA 4096/14479587 2020-05-19
> 




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


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

[Sugar-devel] Spectrum

[James Cameron]

I was introduced to https://spectrum.chat/ while at
https://linux.conf.au/ for working with the open hardware
miniconference track.

Spectrum is open source.  https://github.com/withspectrum

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

Re: [Sugar-devel] Information about Idea Page GSOC2021.

[James Cameron]

You asked about SageMath.  Please contact the SageMath organisation
for all information about their involvement in GSoC.  Sugar Labs has
no relationship with SageMath.

For Sugar Labs and GSoC, we have no ideas list yet.  You can see last
year's ideas list on our repository;

https://github.com/sugarlabs/GSoC

We do not select students based on technologies and codebase knowledge
alone.  To work towards a better proposal, read the list of points in
our "Right fit" section;

https://github.com/sugarlabs/GSoC#right-fit

On Mon, Jan 25, 2021 at 11:51:39PM +0530, MAULIK VARSHNEY wrote:
> Hey,
> Can anyone please help me with the Idea List page for GSOC 2021?
> What all technologies and prior codebase knowledge is generally being 
> required/
> expected from the students participating in GSOC with Sage Math as parent
> Organisation?

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


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

Re: [Sugar-devel] Participation in GSOC 2021

[James Cameron]

Welcome Saurabh,

We are a permissionless community.  Why do you not add Hindi as a
language immediately?  There is no issue or pull request that mentions
Hindi.  There are closed pull requests that add other languages.  I
doubt Lionel has any reason to refuse a language, but if you think
that may be the case, and you see no reply from him here, then ask him
directly.

On Sat, Jan 23, 2021 at 02:30:57PM +, Saurabh Gupta wrote:
> Hi everyone,
> I hope you all are doing well
> By way of introduction, I am Saurabh, a 2nd-year student from IIT Roorkee. I 
> am
> contributing to Sugarizer for the last few months and have fixed some issues.
> During this journey, I gained some knowledge about sugarizer activities and 
> how
> sugarizer works.
> Here, I am just eager to know if sugarizer is planning to incorporate Hindi as
> a language in the coming future just like MusicBlocks has?
> Further, I am eagerly looking forward to participate in GSoC 2021 and make
> valuable contributions to Sugarlabs.
> 
> Regards 
> Saurabh Gupta

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


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

Re: [Sugar-devel] A show of excitement and source of motivation for everyone here

[James Cameron]

On Thu, Jan 21, 2021 at 09:23:18PM +0530, Sumit Srivastava wrote:
> Just came across this one-year-old comment of mine on a YouTube
> video titled "The Coolest Netbook You’ve Forgotten About: The OLPC
> XO-1" when someone commented on my comment about 2 hours ago. [Link
> to the video: [1]https:// youtu.be/UPP4ClRmVik]
> 
> I thought that I'd share it all of you on the mailing list since it
> shows that people are still excited to hear about the cool stuff
> that the people here have built and the impact you're delivering
> each and every day. All of you are awesome!
> 
> Sharing the whole YouTube comment transcript here, without any
> editing:

Thanks.  Reviewed.

Your answer about Browse is out of date.  You probably used Wiki pages
that have not been updated for over a decade.  Browse uses WebKit now.

When you copy text written by someone else, please do credit them
appropriately.

http://lists.sugarlabs.org/archive/sugar-devel/2019-June/056969.html
https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md#be-considerate

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

Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!

[James Cameron]

Thanks, great work.  Merged 204.

I've also updated Browse.

https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac

I would prefer new version notifications to go to
sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
previously.  a...@lists.sugarlabs.org was for handling by library
editors, but we don't have any active, and we don't have the same
process with v4.

On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
> G'day!
> 
> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! ... with only
> a few more minor tidying up, ASLO-v4 will be ready for production.
> 
> Activity maintainers can now push their bundles to ASLO-v4 by following the
> instructions on https://wiki.sugarlabs.org/go/Service/activities4 as well
> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
> Please feel free to reach out, so that I can improve the existing
> documentation, or anything you think is too complex.
> 
> Next steps:
> 
>  * Connect services/update-aslo.php and deploy a flask server (I am
>trying to get a hold of some more good apache knowledge)
>  * Sending "new version detected" emails to a...@lists.sugarlabs.org,
>or should we create a new mailing list?
> 
> -- 
> Srevin Saju
> https://srevinsaju.me
> 

pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) 

> sub   RSA 4096/14479587 2020-05-19
> 




> ___
> Systems mailing list
> syst...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/systems


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

Re: [Sugar-devel] GSoC 2021 Ideas

[James Cameron]

The project task checklist is not a good source of information.

There are 138 search results for "exec = sugar-activity ", and 173 for
"from sugar.activity".  Not all of these can be worked, but there's
plenty of opportunity without looking beyond GitHub for sources.

However, if we run out of GitHub sources that need work, we have
Gitorious at git.sugarlabs.org, and bundles at
activities.sugarlabs.org.

I've an idea for a blockchain learning app, using an intentionally
weak hash so as to avoid children depleting laptop batteries with
mining.

On Mon, Jan 18, 2021 at 02:46:00PM +0530, Saumya Mishra wrote:
> Hi,
> 
> Regarding `Port Sugar and core activities to Python 3` I think this is still
> relevant and does not require changes to last year's project.
> I also agree with Jui. As the number of hours is reduced, we can try to reduce
> the number of items given in the 'Project Task checklist'. As Port to 
> Telepathy
> ([1]https://github.com/orgs/sugarlabs/projects/4) here it shows it is almost
> completed except for one activity remaining, it requires minimal concern this
> year.
> Port to the latest sugargame and collabwrapper, Port to Python 3 requires 
> major
> importance this year according to me. "Reviewing the Sugar source code changes
> that were made for porting to Python 3" is also essential to include in the
> task list.
> 
> Thanks
> Saumya
> 
> On Mon, Jan 18, 2021 at 2:26 PM Jui Pradhan <[2]juipradha...@gmail.com> wrote:
> 
> Hi,
> We are yet to add Ideas-2021.md file.
> 
> - Given a change in the number of hours this year, any suggestions on
> changes to last year's projects are welcome.
> 
> - It would be great if people who are familiar with recent work on
> Sugarizer and Music Blocks could speak about the relevance of last year's
> project ideas.
> 
> - My opinion on last year's projects for Sugar (accepted projects for GSoC
> 2020) :
> `Improve and maintain Sugar Activities` is still relevant however the
> number of activities can be reduced to 15 (we can discuss the number)
> `Port Sugar and core activities to Python 3` I think this is still 
> relevant
> and does not require changes to last year's project.
> `Debian advocacy for Sugar` we should definitely keep this as long as 
> there
> is someone willing to mentor.
> 
> Thanks
> 
> On Fri, Jan 15, 2021 at 1:21 PM James Cameron <[3]qu...@laptop.org> wrote:
> 
> We need ideas for GSoC this year.  Let's get started.
> 
> Change from last year; projects are 175 hours rather than 350 hours.
> 
> Use ideas from previous years, or make new ideas.
> 
> Make a new Ideas-2021.md file in our repository
> [4]https://github.com/sugarlabs/GSoC using a pull request.
> 
> File README.md also needs a few changes.  You can read the commit
> history of changes to the file to see what changed last year.
> 
> Applications by organisations are from 29th January to 19th February.
> 
> Organisation administrators this year are Jui, Perrie and Lionel.
> 
> --
> James Cameron
> [5]https://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> [6]Sugar-devel@lists.sugarlabs.org
> [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> Regards,
> --
> Jui Pradhan
> ___
> Sugar-devel mailing list
> [8]Sugar-devel@lists.sugarlabs.org
> [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> *
> 
> References:
> 
> [1] https://github.com/orgs/sugarlabs/projects/4
> [2] mailto:juipradha...@gmail.com
> [3] mailto:qu...@laptop.org
> [4] https://github.com/sugarlabs/GSoC
> [5] https://quozl.linux.org.au/
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> [8] mailto:Sugar-devel@lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel

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

Re: [Sugar-devel] Compatibility report on latest Debian-based sugar live build - Xorg fails to load due to missing firmware

[James Cameron]

On Sun, Jan 17, 2021 at 06:18:14PM -0800, Alex Perez wrote:
> James Cameron wrote on 1/17/2021 6:12 PM:
> > It sounds like you share some of the same intentions as Martin Guy,
> > who needed i386 support.  He found what he needed with Trisquel.  Have
> > you tried that?
> No, I'm interested in running on x86_64, EFI-compliant hardware.  I
> have no need or desire for Trisquel.

Thanks.  That's my problem too; I'm not interested in i386, I'm not
interested in Trisquel, in Fedora, or SoaS.  In turn, because of how
I'm funded.

The situation reminds me of Jussi Pakkanen's talk at linux.conf.au
about this time last year, where he described several open source
project interations (iLN6wL7ExHU from 8:47 to 17:50), eventually
concluding that

"What does it say about the OSS community, if cooperating with people
using something other than your chosen tool is seen as an act of
desperation?"

https://lca2020.linux.org.au/schedule/presentation/87/

My perspective is that expanding to include i386 or non-free packages
is effectively a request to expand my scope of software maintenance,
and that I should instead reduce complexity to reduce cost of
maintenance.

A more correct solution within this perspective is for you to use
Fedora.

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