lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GOP-PROP 13: patch management tools (probable withdraw)


From: Janek Warchoł
Subject: Re: GOP-PROP 13: patch management tools (probable withdraw)
Date: Sun, 25 Sep 2011 22:53:13 +0200

2011/9/25 Colin Campbell <address@hidden>:
> FWIW, Janek's bit above is just what I've been saying, and I believe it is
> also what James has been suggesting.  The meta-problem seemas to be that
> there are developers who see the world as patches submitte4d and discussed
> by email, and there are Frogs, newer developers, Bug Squad volunteers and a
> patch meister who just want to have the whole picture in one place.  Sure,
> patches *can* be managed in either, both, or neither of the two
> special-purpose tools we use, and sure, *someone* favours each permutation,
> but speaking as a relatively new, relatively unskilled contributor, I can't
> see why locating and implementing a code management system which handles the
> process as well as centralising the discussion, is a Bad Thing.

I don't suppose that he meant it's a bad thing.  I think Graham's
concern is that we've not moved forward.  In order to choose a better
tool, someone must investigate the alternatives and describe pros and
cons of each of them - then we can actually do something.

cheers,
Janek
  Part of the
> reason Graham found those "lost" patches is that we're not using the right
> tool for the job: an issue tracker which has no knowledge of any resulting
> patches is severely limited.  A code review tool which requires knowing a
> specific issue number or developer's 'nym in order to find a patch, is
> useful only on a single host, where no other projects have access.
>
>
> There are dead horses being beaten here, and perhaps this is one, but I
> firmly believe that lilypond is in the big leagues, with a big league
> community of developers and supporters, and it is time to move to a
> specialised code management tool, and leave behind the collection of ad hoc
> generic tools held together with unenforceable manual procedures that
> serverd a small community several years ago.
>
> I speak bluntly, I realise, and I apologise for any offence given, but my
> opinion is firm and based not just on what I've seen in the lilypond
> community, but on general organisational principles, observed over a 35-year
> career.
>
> Cheers,
> Colin
>
> --
> I've learned that you shouldn't go through life with a catcher's mitt on
> both hands.
> You need to be able to throw something back.
> -Maya Angelou, poet (1928- )
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]