Re: improving our workflow with better tools - let's test things.

[James]

Hello,

On 19/10/13 23:18, Joseph Rushton Wakeling wrote:
> On 19/10/13 10:16, James wrote:
> > The point is that when I am managing 15 patch reviews I don't (won't) 
> > read the
> > email thread [1] I look at tracker, see what has been said, I click 
> > on Rietveld
> > see what has been said; it's all there in front of me, no extra 
> > windows to click
> > or open, one single application (web browser) to use, it's two tabs 
> > on my
> > browser. Quick, easy, simple. Anyone who can read English can do it.
>
> Would the kind of thing you see here be acceptable to you?
>
> https://github.com/D-Programming-Language/phobos/pull/1332
> https://github.com/D-Programming-Language/phobos/pull/1533

Yes, although I don't want to be considered arrogant that it should only 
be 'acceptable to me'; but when the last Patch-nanny decided he was 
going 'spend more time with his family' (so to speak speaking) and 
wanted to pass on the role to someone else, the silence from the 
LilyPond community was deafening. I know that real developers would 
pitch in if need be, but it has taken me away from doing documentation 
patches - my original role - as I simply do not have time to do this and 
any documentation that is of any significant size or that may require a 
lot of back-and-forth as we polish and refine some explanatory section 
that needs an overhaul.

> Note that the GitHub comment threads can also include extracts from 
> the patch(es) under consideration, with comments directly under 
> relevant lines of code.
>
> As per previous discussion, GitHub itself shouldn't be used for 
> Lilypond, but I'm reasonably confident we can get similar 
> functionality out of other tools.

Good, let's hope so. Then *if* we ever need someone else to do this 
role, it will be a relatively flat learning curve (no programming 
experience necessary) and just one purely of process.

James