Re: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font)

2012-01-24 Thread Phil Holmes 
- Original Message - 
From: Graham Percival gra...@percival-music.ca

To: Janek Warchoł janek.lilyp...@gmail.com
Cc: lilypond-devel@gnu.org; lilypond-user lilypond-u...@gnu.org
Sent: Tuesday, January 24, 2012 11:57 AM
Subject: user vs. user (was: User vs Developer: Round 2 (and 
half-time?)(was: Re: music font)





Let's take a look at the current statistics, shall we?
http://lilypond.org/~graham/maybe-missing-emails.html
[from 2011 Dec 01 to 2012 Jan 24]

Response category Number Percent of total
Less than 24 hours 50 68.49%
24 to 48 hours6 8.22%
More than 48 hours 8 10.96%
Never replied  9 12.33%


FWIW, the script isn't always correct - some replies seem to get missed in 
the mail download.  I spent a few minutes looking at this earlier but 
couldn't work out why.  Anyway, let's look at the missed ones:


Issue 1377 should be pushed now?



10 Dec I replied I see James has now said it won't patch master, and so 
is back to needs work



Beam subdivision bug in 2.15.22




Xavier replied same day, Carl followed up.




hot potato bug handling




I replied 18 Dec




error: auto beaming in tuplets after dotted semiquaver




Carl replied same day




Engravers cannot be added at the StaffGroup level




Janek replied same day




PianoStaff, time and grace duplicates the time display




Xavier replied same day




Reorganize NR 1.3 Expressive marks




Fair cop - it was addressed directly to James, though




make doc-stage-1 barfs




Julien replied same day.




wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and 
semiquavers





Janek replied same day; Carl followed up.




We may need to add Janek and Xavier to the list of associates.


Of course, a 96-hour reponse rate isn't precisely fantastic, but it's a 
start.


Well - TBH time isn't of the essence as a general rule.  Whether a bug gets 
added to the tracker in one day or 3 rarely affects the overall development.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font)

2012-01-24 Thread Graham Percival 
On Tue, Jan 24, 2012 at 12:27:56PM -, Phil Holmes wrote:
 Of course, a 96-hour reponse rate isn't precisely fantastic, but
 it's a start.
 
 Well - TBH time isn't of the essence as a general rule.  Whether a
 bug gets added to the tracker in one day or 3 rarely affects the
 overall development.

Our published materials says 24 hours:
http://lilypond.org/bug-reports.html
(step 4: wait for a response)

If the norm is 72 hours, or 96, or 168 hours, we should update
that accordingly.  I don't mind what the number is, just as long
as we give users an honest appraisal of how long they should wait.
IMO taking a 95% cutoff is reasonable -- i.e. if 95% of emails are
replied to within 80 hours, let's publish please allow up to 80
hours.

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: user vs. user (was: User vs Developer: Round 2 (and half-time?)(was: Re: music font)

2012-01-24 Thread Janek Warchoł 
2012/1/24 Graham Percival gra...@percival-music.ca:
 Our published materials says 24 hours:

 [...] we should update that accordingly.

http://codereview.appspot.com/5575047/ and stop worrying.
:)

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel