[Sugar-devel] Issue tracking on Github?

[James Cameron]

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, and creates an
environment where instead of there being one place to report tickets,
the place to report will depend on diagnosis (isolation to component),
thus requiring diagnosis to occur before reporting.  Hopefully by
bringing diagnosis into a mailing list somewhere.  Quality of the
problem description will increase.  There will be many closed issues
"not caused by this component." which will look good when it comes
time to say how many issues were closed.

Solution 2 is further disruptive.

On Wed, Apr 20, 2016 at 06:51:50PM +0530, Vishal Batchu wrote:
> 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 among the members between the 2 solutions proposed,
> 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?
> That way we would also know about the problems that each of them would give
> rise to (if there are any), and could help us decide better.
> 
> Personally, I prefer solution 1.
> 
> Thanks,
> Vishal
> 
> On Wed, Apr 20, 2016 at 6:34 PM, Dave Crossland <[1]dave at lab6.com> wrote:
> 
>     Hi
> 
>     On 20 April 2016 at 08:35, Walter Bender <[2]walter.bender at gmail.com>
>     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 discussion to date and ask for a thumbs up
>         /down from active developers?
> 
>    
>     Problem:
> 
>     Sugar's software development is scattered across trac, gitorious (which is
>     now unmaintained), and github. I think this is harmful to Sugar primarily
>     because it pushes away new contributors - love's email is a great example -
>     and secondarily because it makes existing contributor's lives more painful
>     as - as Sam said - everything should be in 1 place; and also because - as
>     Walter said - the systems team is spending needless time on these systems.
>     2 proposals emerged from the discussion:
>      
>     Solution 1:
> 
>     Consolidate on Github. Set trac and gitorious read only, and then making it
>     a static html archive, while moving all issue tracking and git hosting of
>     each sugar repo to Github. 
> 
>     Solution 2:
> 
>     Abandon Github. Consolidate on our own systems; I guess this means setting
>     up gogs or gitlab to replace gitorious, and perhaps something else to
>     replace trac, and then removing each sugar repo from Github that we
>     control, and regularly encouraging all sugar activities on github to move
>     to our infrastructure.
> 
>     Conflict:
> 
>     It seems that myself, Walter and James are in favour of (1), and Devin and
>     Sam are in favour of (2)
> 
>     How to decide?
> 
>     Cheers
>     Dave
>    
>     _______________________________________________
>     Sugar-devel mailing list
>     [3]Sugar-devel at lists.sugarlabs.org
>     [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:dave at lab6.com
> [2] mailto:walter.bender at gmail.com
> [3] mailto:Sugar-devel at lists.sugarlabs.org
> [4] http://lists.sugarlabs.org/listinfo/sugar-devel

> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
James Cameron
http://quozl.netrek.org/