Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

On 03/14/2017 12:03 PM, Alex Perez wrote: I would think ASLO could simply be made to inspect the contents of an activity, upon upload, (since it’s just a zip file), and look for the necessary string within activity.info , such that it could be displayed under a

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, Walter On 03/14/2017 11:02 AM, Alex Perez wrote: ASLO is not a source code repository. It’s a convenience to end users. I know you think they should be one and the same, and in theory they could be, but I don’t necessarily see the benefit. The source code repository for a Sugar activity

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, Walter and Alex Alex, if you are referring to maintaining ASLO, +1. My point was not about either gitorious or github but the fact that by design the source code for every activity (with some binary exceptions) is in the bundle. It is always clear where the source is located, in the

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony/Walter, > On Mar 13, 2017, at 7:28 PM, Walter Bender wrote: > > Tony, > > Not sure I agree about your asserts regarding github vs gitroious. Count me in here.. > > (1) the were/are many activities that were not hosted in gitorious long > before we switched to

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony, Not sure I agree about your asserts regarding github vs gitroious. (1) the were/are many activities that were not hosted in gitorious long before we switched to github, so it wasn't obvious where to find the source repo *before* the switch. This is one of the reasons I started add the repo

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi James, Your book is a wonder and should be much more actively promoted. It is one of the major contributions of Sugar to constructive learning. I believe the use of git.sugarlabs.org and github are major steps backwards from the original conception of Sugar activities as something which

[Sugar-devel] Minor update to Make Your Own Sugar Activities!

All, I have been neglecting the manual *Make Your Own Sugar Activities!* ever since I first wrote it. However, I did manage to make one needed update in the laziest way possible. Since Sugar Labs has moved away from git.sugarlabs.org in favor of GitHub since I wrote the version control chapter I

Re: [Sugar-devel] GSoC 2017 proposal

On Mon, 2017-03-13 at 23:18 +0530, Melnita Dabre wrote: > I noticed that the existing website is deployed on WordPress. Do I > have to make a site that is deploy-able on WP? No. It is not necessary that it is on Wordpress. You can if you want, but it is not necessary. If you have a creative idea

Re: [Sugar-devel] GSoC 2017 proposal

On Mon, 2017-03-13 at 20:23 +0530, Melnita Dabre wrote: > 1. The expected results for the project mentions creation of a > website. What kind of a website is expected? Any type of website is okay as long as it takes the user through the various important features of Music Blocks as well as

[Sugar-devel] GSoC 2017 proposal

Dear Sir/Ma'am, The User Manual for Music Blocks project Idea for GSoC 2017 interests me. I wish to work on that project. However I have a few queries regarding the same: 1. The expected results for the project mentions creation of a website. What kind of a website is expected? 2. What kind

Re: [Sugar-devel] Fwd: Proposal for GSoC 2017

Looking forward for the same project... On Mar 13, 2017 7:16 PM, "Rajeev Ravindran" wrote: > > -- Forwarded message -- > From: Rajeev Ravindran > Date: Mon, Mar 13, 2017 at 7:15 PM > Subject: Proposal for GSoC 2017 > To:

[Sugar-devel] Fwd: Proposal for GSoC 2017

-- Forwarded message -- From: Rajeev Ravindran Date: Mon, Mar 13, 2017 at 7:15 PM Subject: Proposal for GSoC 2017 To: wal...@sugarlabs.org Hello I'm a student developer from India. I would like to work on the Sugarizer server dashboard as a GSoC 2017