Re: issue classification: priority guidelines

2010-12-16 Thread Carl Sorensen
On 12/16/10 7:24 PM, "Janek Warchoł" wrote: > >> 3.  Don't start with the hardest / highest-priority issues.  Pick >> something tagged with "frogs" to get started on. > > Isn't that obvious? Along with the fact that i'd prefer to work on the > issues that bother me the most, no matter their diff

Re: issue classification: priority guidelines

2010-12-16 Thread Janek Warchoł
Hi, 2010/12/15 Phil Holmes : > Jan, > > I think I can fix your LilyBuntu problem - I had the same.  Try _installing_ > LB, not running _live_ (I'm guessing this is what's happening - it was for > me).  At the very initial text prompt, type install rather than live. 2010/12/15 Graham Percival : >

Re: issue classification: priority guidelines

2010-12-15 Thread Carl Sorensen
On 12/15/10 8:32 AM, "Janek Warchoł" wrote: > 2010/12/15 Graham Percival >>  Fighting about whether a bug should be high vs. low does NOTHING >> to get it fixed sooner or later.  This is a volunteer project, and >> lilypond developers do not appear to be motived based on an >> arbitrary "priorit

Re: issue classification: priority guidelines

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 09:58:42AM -0700, Carl Sorensen wrote: > Everything we have documented is in the Contributor's Guide. > Getting started in LilyPond development is hard. > Understanding how lilypond works is hard. > Understanding the C++ code is hard. I'll add the following: Carl started of

Re: issue classification: priority guidelines

2010-12-15 Thread James
Janek On 15/12/2010 15:32, Janek Warchoł wrote: but i struggle with unbelieveably low VirtualBox resolution - 800x600, it annoys me extremely on my big monitor. Maybe i'll find an answer on the web Look in the help. 9.6. Advanced display configuration James

Re: issue classification: priority guidelines

2010-12-15 Thread Phil Holmes
ssage - From: "Janek Warchoł" To: "Graham Percival" Cc: "Phil Holmes" ; "lilypond-devel" Sent: Wednesday, December 15, 2010 3:32 PM Subject: Re: issue classification: priority guidelines 2010/12/15 Graham Percival Look, the ugly truth is that t

Re: issue classification: priority guidelines

2010-12-15 Thread Graham Percival
2010/12/15 Janek Warchoł : > Ok, this means i have to fix some (lots of?) stuff myself (you got me > hooked perhaps, however i don't know how all this will turn out)... Yes. > The following is for anyone interested in helping me in this task. > I have some basic knowledge about C and a little exp

Re: issue classification: priority guidelines

2010-12-15 Thread Janek Warchoł
2010/12/15 Graham Percival > Look, the ugly truth is that the "priority" field -- other than > "critical" -- has no effect on lilypond development.  I've been > heavily involved since 2003 (before this issue tracker in 2006), > and that's my observation.  It has no statistically significant > affe

Re: issue classification: priority guidelines

2010-12-15 Thread Phil Holmes
ival" Cc: "Janek Warchoł" ; "lilypond-devel" Sent: Wednesday, December 15, 2010 2:56 PM Subject: Re: issue classification: priority guidelines 2010/12/15 Graham Percival : In the mean time, go ahead and twiddle the definitions of priorities (as long as you leave Critical alone).

Re: issue classification: priority guidelines

2010-12-15 Thread Valentin Villenave
On Wed, Dec 15, 2010 at 1:31 PM, Phil Holmes wrote: > * Priority-High: An issue which produces output which does not accurately > reflect the input (e.g where the user would expect an accidental, but none > is shown) or which produces aesthetically poor output in a situation which > could be expec

Re: issue classification: priority guidelines

2010-12-15 Thread Valentin Villenave
2010/12/15 Graham Percival : > In the mean time, go ahead and twiddle the definitions of > priorities (as long as you leave Critical alone).  But be aware > that you're "rearranging deck chairs on the titanic". ROTFL -- my point exactly :-) Cheers, V.

Re: issue classification: priority guidelines

2010-12-15 Thread Graham Percival
On Wed, Dec 15, 2010 at 12:31:02PM -, Phil Holmes wrote: > - Original Message - From: "Janek Warchoł" > >I've read Issue classification and i think it would be good to add one > >more guideline concerning priority: i believe that the priority should > >depend on how widespread the issue

Re: issue classification: priority guidelines

2010-12-15 Thread Phil Holmes
- Original Message - From: "Janek Warchoł" To: "lilypond-devel" Sent: Wednesday, December 15, 2010 11:53 AM Subject: issue classification: priority guidelines Hi, I've read Issue classification and i think it would be good to add one more guideline conce

Re: issue classification: priority guidelines

2010-12-15 Thread Dmytro O. Redchuk
On Wed 15 Dec 2010, 12:53 Janek Warchoł wrote: > Hi, Hi! > I've read Issue classification and i think it would be good to add one > more guideline concerning priority: i believe that the priority should > depend on how widespread the issue is. Even minor problems concernning > some basic elements

issue classification: priority guidelines

2010-12-15 Thread Janek Warchoł
Hi, I've read Issue classification and i think it would be good to add one more guideline concerning priority: i believe that the priority should depend on how widespread the issue is. Even minor problems concernning some basic elements (that will probably happen many times in even a single score)