Re: [Sugar-devel] Issue tracking on Github?

On 04/04/2016 12:35 AM, Dave Crossland wrote: > Here is why: > 1. Control. The community would be able to do what they wish with their > data. (the other benefits really come from this one) > > > Most of the data on Github servers, and all the data that is uploaded to > the servers

Re: [Sugar-devel] Issue tracking on Github?

Hi Tony! On 3 April 2016 at 02:02, Tony Anderson wrote: > You are proposing, appropriately, a new way to handle version control for > Sugar. > I'm not sure about that :) I didn't intend to :) > There is documented procedure to add new activities or to update >

Re: [Sugar-devel] Issue tracking on Github?

Hi Sam! On 3 April 2016 at 01:12, wrote: > Hi Dave, > > On Sun, Apr 3, 2016 at 11:36 AM, Dave Crossland wrote: > > > Hi > > When sugar git moved from http://git.sugarlabs.org/sugar-old to > https://github.com/sugarlabs/sugar in 2013, why did issue tracking stay >

Re: [Sugar-devel] Usage metrics

On 3 April 2016 at 22:06, James Cameron wrote: > > I'm curious though; how do they ship on some activities, not the > whole > > desktop? > > > > They are shipping Turtle Blocks, which will run in GNOME as well as > the > > Sugar Desktop. Not sure what

Re: [Sugar-devel] Usage metrics

On 3 April 2016 at 21:26, James Cameron wrote: > A wrapper to run activities outside Sugar may be quite useful. > I feel kind of like Android is Darth Vader, Sugar is Obi Wan, and Sugarizer is the Force Ghost Obi Wan ;) https://www.youtube.com/watch?v=fk3_-JSTdx0

Re: [Sugar-devel] Usage metrics

On Sun, Apr 03, 2016 at 09:57:41PM -0400, Dave Crossland wrote: > On 3 April 2016 at 21:04, Walter Bender <[1]walter.ben...@gmail.com> wrote: > > On Sun, Apr 3, 2016 at 9:00 PM, Dave Crossland <[2]d...@lab6.com> wrote: > > > On 3 April 2016 at 20:19, Walter Bender

Re: [Sugar-devel] Usage metrics

On 3 April 2016 at 21:04, Walter Bender wrote: > > > On Sun, Apr 3, 2016 at 9:00 PM, Dave Crossland wrote: > >> >> On 3 April 2016 at 20:19, Walter Bender wrote: >> >>> FWIW, Endless is shipping some Sugar activities :) >> >> >>

Re: [Sugar-devel] Issue tracking on Github?

On Sun, Apr 03, 2016 at 09:40:33PM -0400, Dave Crossland wrote: > [...] Either strategy of landing on Github (as I recommend) or > returning wholly to SL infrastructure (as Devlin has just proposed) > would meet that goal.  My preference is to move the remaining activities to GitHub and set the

Re: [Sugar-devel] Issue tracking on Github?

Hi Walter! On 3 April 2016 at 20:27, Walter Bender wrote: > This means we have no users engaging with Sugar Labs through bug >>> reporting; and that's been my observation for some time. >>> >> >> I feel anxious to read this, and for me this is the primary reason I >>

Re: [Sugar-devel] Usage metrics

On Sun, Apr 03, 2016 at 09:04:32PM -0400, Walter Bender wrote: > > On Sun, Apr 3, 2016 at 9:00 PM, Dave Crossland wrote: > > > On 3 April 2016 at 20:19, Walter Bender wrote: > > FWIW, Endless is shipping some Sugar activities :) > >

Re: [Sugar-devel] Issue tracking on Github?

On 3 April 2016 at 20:36, James Cameron wrote: > > Previous attempts at consolidation have had varying success, as can be > seen from the increase in fragmentation. > > The number of mailing lists, Wiki, Social Help, IRC channels, > Gitorius, GitHub, ... these are all being

Re: [Sugar-devel] Issue tracking on Github?

Hi, I have been following this thread. These are my two cents. If it were me, I would have opted to keep everything on a server within Sugar Labs' community's control. Here is why: 1. Control. The community would be able to do what they wish with their data. (the other benefits really come from

Re: [Sugar-devel] Usage metrics

On 3 April 2016 at 20:19, Walter Bender wrote: > FWIW, Endless is shipping some Sugar activities :) Awesome! Endless seems extremely aligned with Sugar :) I'm curious though; how do they ship on some activities, not the whole desktop?

Re: [Sugar-devel] Issue tracking on Github?

On Sun, Apr 03, 2016 at 08:15:26PM -0400, Dave Crossland wrote: > > Hi James! > > On 3 April 2016 at 18:35, James Cameron <[1]qu...@laptop.org> wrote: > > Because trac provides coverage across multiple repositories, and > nothing else gave us that feature at the time. > > This makes

Re: [Sugar-devel] Issue tracking on Github?

Hi Walter! On 3 April 2016 at 09:04, Walter Bender wrote: > > > On Sun, Apr 3, 2016 at 12:24 AM, Dave Crossland wrote: > >> >> On 2 April 2016 at 22:21, Walter Bender wrote: >> >>> I was just asking (again) the other day >>> >>

Re: [Sugar-devel] Issue tracking on Github?

On Sun, Apr 3, 2016 at 8:15 PM, Dave Crossland wrote: > > Hi James! > > On 3 April 2016 at 18:35, James Cameron wrote: > >> Because trac provides coverage across multiple repositories, and >> nothing else gave us that feature at the time. >> > > This makes good

Re: [Sugar-devel] Usage metrics

FWIW, Martin (who now works for endless) and I put together a metrics mechanism for Sugar for OLPC AU. Never got it committed upstream to Sugar master, in part because of security concerns, but a mash-up of sorts might make sense. Also, FWIW, Endless is shipping some Sugar activities :) -walter

Re: [Sugar-devel] Issue tracking on Github?

Hi James! On 3 April 2016 at 18:35, James Cameron wrote: > Because trac provides coverage across multiple repositories, and > nothing else gave us that feature at the time. > This makes good sense, and is good to know :) > I'm fine with closing down trac, because; > > (a)

[Sugar-devel] Usage metrics

Hi In the github thread, James Cameron mentioned Endless, which seems like "One Desktop Per Family" :) I was pleased to see that on https://endlessm.com/developer/ there is, between links to source code for "hardware" and "installation", a set of links to source code for *metrics* :) Since both

Re: [Sugar-devel] [IAEP] [SLOB] meeting reminder

Hi Tony! On 3 April 2016 at 01:45, Tony Anderson wrote: > I can't imagine the process is so simple. The overwritten translations > were probably on translate.sugarlabs.org. > Yes, that is the Pootle instance I referred to in my previous email, sorry that I wasn't clear

Re: [Sugar-devel] Issue tracking on Github?

Because trac provides coverage across multiple repositories, and nothing else gave us that feature at the time. I'm fine with closing down trac, because; (a) it isn't used in release engineering, (b) in the past 90 days there have been no tickets created or updated by anyone other than

Re: [Sugar-devel] Sugar-Server enhancement

The ticket is up to date. Your task would be to set up a server, e.g. XSCE, http://schoolserver.org/ and then register to it; which is a UI step. Then set up a second server, and register to it; which is a manual process. Then design a UI and UX for either switching registration or detecting

Re: [Sugar-devel] GSoC 2016 | Sugarizer Activity Set

Hi Shirsh, Just sent to you a PR on the French localization. I've opened too some issues. Best regards from France. Lionel. 2016-03-31 4:45 GMT+02:00 Shirsh Zibbu : > Sir. > > Here is the link to my repo: > https://github.com/zhirzh/sugarizer-activity-moon >

Re: [Sugar-devel] Screenshot feature [GSoC Project]

Hi Dave, Thanks for your appreciation. I think this feature isn't intrusive also because if the user wants to ignore or cancel the save, he can simply do so by pressing Esc key. Golden Rule- Giving the user a choice to do something but not force it. ;) Thanks, Utkarsh Tiwari On

Re: [Sugar-devel] Screenshot feature [GSoC Project]

I think this is a good change/feature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Issue tracking on Github?

On Sun, Apr 3, 2016 at 12:24 AM, Dave Crossland wrote: > > On 2 April 2016 at 22:21, Walter Bender wrote: > >> I was just asking (again) the other day >> > > Can you provide a URL for where you asked about this? :) > I was asking in a private email with

[Sugar-devel] Sugar-Server enhancement

Hello everyone, I was looking at this bug https://bugs.sugarlabs.org/ticket/362 , but I couldn't understand its status quite well. I am interested to work on this enhancement as it is related to my proposed GSoC 2016 proposal and would give me a head start on understanding the present

Re: [Sugar-devel] Proxy Settings Feature in the recent versions of sugar

Hi all, The proxy feature implementation looks complete now. https://github.com/sugarlabs/sugar/pull/665 Hence, please review it and provide suggestions. :) Shall I update the feature page for the same? https://wiki.sugarlabs.org/go/Features/Proxy_Settings Thanks. Regards Manash Pratim Das

Re: [Sugar-devel] Screenshot feature [GSoC Project]

Hi Sam, This feature will actually help the user modify the name of the screenshot at the very moment he captures it (like what happens in Ubuntu). In case of Journal, the user might forget later for what purpose he took that screenshot since the default name "Screenshot of X" doesn't

Re: [Sugar-devel] Issue tracking on Github?

Welcome to the Sugar community (and its growing entropy)! You are proposing, appropriately, a new way to handle version control for Sugar. There is documented procedure to add new activities or to update activities on ASLO. This procedure is working with update notifications in the ASLO