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

On 6 June 2016 at 19:30, Devin wrote: > the published code is not very mature so it does not yet matter if it has a > license Right; if it _is_ code (which it probably isn't) then it is probably not very useful for anything, and if you do want a license for it, you can

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

I am certainly more mindful of this issue; I came across https://github.com/mortenjust/cleartext-mac/ today and saw there was no license, and after my bleeting the developed added GPLv3 :) https://github.com/mortenjust/cleartext-mac/issues/3 ___

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

On 06/06/2016 07:08 PM, Dave Crossland wrote: > First, I think there must be a large fraction of all github repos that > have less than 10 commits with almost nothing in them and are > essentially worthless. If those don't have a LICENSE file, I don't > mind :) I think this way of looking at the

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

On 6 June 2016 at 16:16, Devin wrote: > (This is long, gnarly thread, but I just like to think about this sort of > stuff, what can I say...) :D To say Github is a failed state seems rather absurd to me, compared to the other 2 large code hosting sites, SourceForce and

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

On 06/06/2016 06:34 PM, Walter Bender wrote: >> This is interesting: http://250bpm.com/blog:82 >> > >> > Not sure I buy into the failed-state hypothesis, but it is interesting > nonetheless. The person who sent the link was not certain the information is entirely correct, so I do think it would

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

On Mon, Jun 6, 2016 at 6:16 PM, Devin wrote: > (This is long, gnarly thread, but I just like to think about this sort of > stuff, what can I say...) > > On 05/27/2016 09:05 AM, Walter Bender wrote: > > This has been the topic of a lot of discussion on the FOSS foundation

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

(This is long, gnarly thread, but I just like to think about this sort of stuff, what can I say...) On 05/27/2016 09:05 AM, Walter Bender wrote: > This has been the topic of a lot of discussion on the FOSS foundation list > of late. I think there is a movement afoot to push them towards a default

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

Hi On 27 May 2016 at 11:16, Devin Ulibarri wrote: > On 05/27/2016 09:03 AM, Dave Crossland wrote: > > > > On 27 May 2016 at 08:59, Devin Ulibarri > > wrote: > > > > Notice from the ethics article that one big

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

On 05/27/2016 11:16 AM, Devin Ulibarri wrote: > Having no license, if someone accidentally downloads and uses the code > without express permission, since the default US copyright law would > have it "All Rights Reserved" it puts the people who have access to the > code at risk of possible

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

On 05/27/2016 09:03 AM, Dave Crossland wrote: > > On 27 May 2016 at 08:59, Devin Ulibarri > wrote: > > Notice from the ethics article that one big deal with GitHub is it > allows developers to upload code without a license (thus

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

On 27 May 2016 at 09:05, Walter Bender wrote: > This has been the topic of a lot of discussion on the FOSS foundation list > of late. I think there is a movement afoot to push them towards a default > FOSS license. > Which list is that?

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

On Fri, May 27, 2016 at 8:59 AM, Devin Ulibarri wrote: > On 05/27/2016 08:55 AM, Dave Crossland wrote: > > I think its pretty clear that Github's business model _depends_ on it > > hosting the world's libre licensed code: That's how they get developers > > into their

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

Hi On 27 May 2016 at 08:59, Devin Ulibarri wrote: > Notice from the ethics article that one big deal with GitHub is it > allows developers to upload code without a license (thus being > proprietary by default, even though we can all see the code). > I don't think a

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

On 05/27/2016 08:55 AM, Dave Crossland wrote: > I think its pretty clear that Github's business model _depends_ on it > hosting the world's libre licensed code: That's how they get developers > into their conversion funnel. Notice from the ethics article that one big deal with GitHub is it

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

Hi On 27 May 2016 at 08:29, Devin Ulibarri wrote: > (I found this in my drafts folder and am sending it out. I know a > decision was made about this, but am sending for continued reference.) Thank you! :) > > On 05/16/2016 11:13 PM, Dave Crossland wrote: > > Hi > > >

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

(I found this in my drafts folder and am sending it out. I know a decision was made about this, but am sending for continued reference.) On 05/16/2016 11:13 PM, Dave Crossland wrote: > Hi > > Does anyone want to discuss any more objections with me, or can I > migrate the issue tracking to Github

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

On 18 May 2016 at 11:59, Bert Freudenberg wrote: > On 18.05.2016, at 17:01, Dave Crossland wrote: > > On 18 May 2016 at 10:54, Bert Freudenberg wrote: > >> On 18.05.2016, at 16:26, Dave Crossland wrote: >> >> >> Hi >>

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

On 18.05.2016, at 17:01, Dave Crossland wrote: > On 18 May 2016 at 10:54, Bert Freudenberg > wrote: > On 18.05.2016, at 16:26, Dave Crossland > wrote: >> >> Hi >> >> On 18 May 2016 at

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

On 18 May 2016 at 10:54, Bert Freudenberg wrote: > On 18.05.2016, at 16:26, Dave Crossland wrote: > > > Hi > > On 18 May 2016 at 09:57, Tony Anderson wrote: > >> Its an educational project. An example is >>

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

On 18.05.2016, at 16:26, Dave Crossland wrote: > > Hi > > On 18 May 2016 at 09:57, Tony Anderson > wrote: > Its an educational project. An example is > https://github.com/ezequielpereira/Bridge >

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

Hi On 18 May 2016 at 09:57, Tony Anderson wrote: > Its an educational project. An example is > https://github.com/ezequielpereira/Bridge. This version of the > Bridge-activity was developed as part of GCI. > The zip downloaded from github is named Bridge-master.zip. I

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

Hi, Dave Its an educational project. An example is https://github.com/ezequielpereira/Bridge. This version of the Bridge-activity was developed as part of GCI. The zip downloaded from github is named Bridge-master.zip. I copied the zip to an XO-1.75, unzipped, and ran setup.py dist_xo. The

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

Hi, Dave As I understand it, what you are trying to do is make github the place where Sugar activities are kept. Currently, ASLO provides for upload of an activity (new or new version) as an xo bundle from the user's file system. What would be needed is a way to release an xo bundle from the

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

Hi On 18 May 2016 at 04:29, Tony Anderson wrote: > Sugar activities from the beginning identified versions by version number. > For some activities we have tens of versions in ASLO. Switching version > control from a version number to git branches may be non-trivial. It

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

Sugar activities from the beginning identified versions by version number. For some activities we have tens of versions in ASLO. Switching version control from a version number to git branches may be non-trivial. It would certainly be helpful to view changes to activities over time. I still

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

On Tue, May 17, 2016 at 12:35 PM, Dave Crossland wrote: > > On 17 May 2016 at 09:46, Walter Bender wrote: > >> we need to send out a clear description of what is expected of App >> developers ("transfer" their repos to sugarlabs) and how to manage issues

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

On 17 May 2016 at 11:44, Walter Bender wrote: > > On Tue, May 17, 2016 at 11:03 AM, Dave Crossland wrote: > >> >> On 3 April 2016 at 20:36, James Cameron wrote: >> >>> > >>> > Is wiki.sugarlabs.org used for tracking release engineering

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

On 17 May 2016 at 09:46, Walter Bender wrote: > we need to send out a clear description of what is expected of App > developers ("transfer" their repos to sugarlabs) and how to manage issues > once the switch-over has occurred.

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

AFAIK, Martin is still the release manager. -walter On Tue, May 17, 2016 at 11:03 AM, Dave Crossland wrote: > > On 3 April 2016 at 20:36, James Cameron wrote: > >> > >> > Is wiki.sugarlabs.org used for tracking release engineering work? >> >> I'm not the

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

On 3 April 2016 at 20:36, James Cameron wrote: > > > > Is wiki.sugarlabs.org used for tracking release engineering work? > > I'm not the release engineer for Sugar, sorry. Who will manage the 0.110 release? https://wiki.sugarlabs.org/go/Development_Team/Contacts seems stale

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

+1 for migrating. But... I think we need to send out a clear description of what is expected of App developers ("transfer" their repos to sugarlabs) and how to manage issues once the switch-over has occurred. -walter On Mon, May 16, 2016 at 11:13 PM, Dave Crossland wrote: > Hi >

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

Hi Does anyone want to discuss any more objections with me, or can I migrate the issue tracking to Github now? :) Cheers Dave ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel

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

Hi On 25 April 2016 at 07:42, Devin wrote: > *If* GitLab and/or trac, for example, had the features of GitHub and had > a plugin that weeded out spam would it *then* be preferable to GitHub? > Not for me: The primary reason Github is preferable for me is that it is the

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

On 04/23/2016 11:26 PM, Dave Crossland wrote: > On 20 April 2016 at 09:04, Dave Crossland wrote: > >> > How to decide? > ? :) > /*If*/ GitLab and/or trac, for example, had the features of GitHub and had a plugin that weeded out spam would it */then/* be preferable to GitHub? If

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

On 20 April 2016 at 09:04, Dave Crossland wrote: > How to decide? ? :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel

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

Hi On 20 April 2016 at 19:58, James Cameron wrote: > Solution 1 is a change that may lose ticket reporters, > Hmm, do you mean people will refuse to report tickets because its Github? > and creates an > environment where instead of there being one place to report tickets, >

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

My rethink. Solution 1 might work, my estimate is 10% probability of it working. Solution 2 might work, my estimate is 5% probability of it working. Solution 0 is do nothing, the status quo, my estimate is 25% probability of it working. Solution 1 is a change that may lose ticket reporters,

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

On 20 April 2016 at 09:54, Justin Overton wrote: > - It would be easier for new developers to find and contribute if it were > on github I agree, this is my primary reason for proposing (1) also: I think the primary problem facing Sugar Labs is the small developer

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

Why I like GitHub best - It would be easier for new developers to find and contribute if it were on github - Support for "how to use git" would be mostly on github rather than SugarLab's systems - Getting existing developers to move their activities out of GitHub doesn't seem

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

On 20 April 2016 at 09:21, Vishal Batchu wrote: > is it possible to let the developer community know why you, Walter and > James are in favour of solution 1 whereas Devin and Sam are in favour of > solution 2? Please read the thread :)

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

Hi Dave, When I started contributing to SugarLabs initially, I faced a similar problem. Searching for activities on Github, gitorious and then searching for bugs on trac etc. It would be great if it could all be moved to a single place where it can be accessed easily. Since there is a conflict

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

Hi On 20 April 2016 at 08:35, Walter Bender wrote: > While SLOB can vote on this, personally I think it is up to the developer > community to decide. Sure, that's reasonable. How does the developer community resolve conflicts? > Can you summarize the recent

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

On Wed, Apr 20, 2016 at 8:30 AM, Dave Crossland wrote: > > On 4 April 2016 at 10:19, Walter Bender wrote: > >> FWIW, we have had a very hard time keeping hackers out of our trac >> system. Despite extreme measures, SCG still has to manually remove hacked

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

On Mon, Apr 4, 2016 at 10:08 AM, Dave Crossland wrote: > > Hi! > > On 4 April 2016 at 00:50, Devin Ulibarri wrote: > >> On 04/04/2016 12:35 AM, Dave Crossland wrote: >> > Here is why: >> > 1. Control. The community would be able to do what they

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

Hi! On 4 April 2016 at 00:50, Devin Ulibarri wrote: > 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) > > > >

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

On Mon, Apr 04, 2016 at 12:48:15AM -0400, Dave Crossland wrote: > 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

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] 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] 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] 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] 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)

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

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

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

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 at bugs.sugarlabs.org and not move to

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

On 2 April 2016 at 22:18, Tony Anderson wrote: > The Sugar activities, which represent 90% or more of the Sugar lines of > code, are being relocated to the github accounts of individual > developer/maintainers - not under a single Sugar account. > I think that is fine :)

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

I am sure this would be helpful. However, the situation seems a bit more muddled. The Sugar activities, which represent 90% or more of the Sugar lines of code, are being relocated to the github accounts of individual developer/maintainers - not under a single Sugar account. At the moment

[Sugar-devel] Issue tracking on Github?

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 at bugs.sugarlabs.org and not move to https://github.com/sugarlabs/sugar/issues ? I think it would be a good idea to move the issues, since pull requests