Re: Contributing

2024-04-29 Thread Dan Eble
On 2024-04-29 17:39, Steph Phillips wrote: Hi there! I'm an experienced Python developer with some additional background in C# and C++ and would be really excited to contribute to LilyPond. It's definitely hard to decide where to begin though, so I'm hoping you can point me at the starting l

Re: Contributing

2024-04-29 Thread Stephanie Phillips
Oh wow, that's actually very good to know. I noticed while perusing the developer documentation that it's implemented in PyQT4 which I figure has issues or is depreciated by now. I'll look into this! Thanks a lot! ~Steph On Mon, Apr 29, 2024, 3:12 PM Tom Brennan wrote: > Hi > > I'm not the ri

Re: Contributing

2024-04-29 Thread Tom Brennan
Hi I'm not the right person by any means to delegate any work, but I've been lurking on the lilypond user list, and noticed they uncovered a serious issue in Frescobaldi (implemented in Python) with an old Qt dependency that has reached EOL, and is starting to cause serious issues. It seems fairly

Re: contributing instructions are misleading!

2014-01-04 Thread Jean-Charles Malahieude
Le 01/01/2014 20:45, James disait : On 01/01/14 17:50, Jean-Charles Malahieude wrote: I compile on native Fedora. I don't know by how would be multiplied a 90 minutes "make -j3 && make -j3 doc" on my dual-core with 2gigs RAM when launched in a VM. Probably not as much as you think. Assuming you

Re: contributing instructions are misleading!

2014-01-03 Thread ul
Zitat von Graham Percival : On Wed, Jan 01, 2014 at 07:45:15PM +, James wrote: If you are comfortable with making patches and compiling, LilyDev is probably not for you. If you are not or want a ready-to-go environment and don't care that it's on some 'old' Linux release (i.e. not new and

Re: contributing instructions are misleading!

2014-01-03 Thread Graham Percival
On Wed, Jan 01, 2014 at 03:47:32PM +0100, Janek Warchoł wrote: > 2014/1/1 Graham Percival : > > Not quite. 1) is obvious, but equally important is 1.5) update > > incorrect info. Remember this latest iteration of interest in the > > CG happened because one or two new contributors tried to follow

Re: contributing instructions are misleading!

2014-01-03 Thread Graham Percival
On Wed, Jan 01, 2014 at 07:45:15PM +, James wrote: > If you are comfortable with making patches and compiling, LilyDev is > probably not for you. If you are not or want a ready-to-go > environment and don't care that it's on some 'old' Linux release > (i.e. not new and shiny) then LilyDev is pe

Re: contributing instructions are misleading!

2014-01-01 Thread James
On 01/01/14 17:50, Jean-Charles Malahieude wrote: Le 01/01/2014 18:07, Urs Liska disait : Am 01.01.2014 18:02, schrieb Phil Holmes: - Original Message - From: "Urs Liska" But you're led to believe that LilyDev is the canonical environment for working on LilyPond, and if you dare to g

Re: contributing instructions are misleading!

2014-01-01 Thread Phil Holmes
- Original Message - From: "Jean-Charles Malahieude" To: "Urs Liska" ; "Phil Holmes" ; Sent: Wednesday, January 01, 2014 5:50 PM Subject: Re: contributing instructions are misleading! Le 01/01/2014 18:07, Urs Liska disait : Am 01.01.2014 18:02, schrie

Re: contributing instructions are misleading!

2014-01-01 Thread Jean-Charles Malahieude
Le 01/01/2014 18:07, Urs Liska disait : Am 01.01.2014 18:02, schrieb Phil Holmes: - Original Message - From: "Urs Liska" But you're led to believe that LilyDev is the canonical environment for working on LilyPond, and if you dare to go another route you'll be on your own and heading f

Re: contributing instructions are misleading!

2014-01-01 Thread Phil Holmes
- Original Message - From: "Urs Liska" To: "Phil Holmes" ; Sent: Wednesday, January 01, 2014 5:07 PM Subject: Re: contributing instructions are misleading! Well - since you're the only one running your specific environment, that's generally true. With

Re: contributing instructions are misleading!

2014-01-01 Thread David Kastrup
Urs Liska writes: > Am 01.01.2014 18:02, schrieb Phil Holmes: >> - Original Message - From: "Urs Liska" >> >>> But you're led to believe that LilyDev is the canonical environment >>> for working on LilyPond, and if you dare to go another route you'll be >>> on your own and heading for tr

Re: contributing instructions are misleading!

2014-01-01 Thread Urs Liska
Am 01.01.2014 18:02, schrieb Phil Holmes: - Original Message - From: "Urs Liska" To: Sent: Wednesday, January 01, 2014 4:41 PM Subject: Re: contributing instructions are misleading! That's a point I'd like to say something about. The CG's insistence o

Re: contributing instructions are misleading!

2014-01-01 Thread Phil Holmes
- Original Message - From: "Urs Liska" To: Sent: Wednesday, January 01, 2014 4:41 PM Subject: Re: contributing instructions are misleading! That's a point I'd like to say something about. The CG's insistence on Lilydev can be somewhat offputting. I didn'

Re: contributing instructions are misleading!

2014-01-01 Thread Urs Liska
Am 01.01.2014 15:47, schrieb Janek Warchoł: 2014/1/1 Graham Percival : On Tue, Dec 31, 2013 at 06:35:36PM +0100, Janek Warchoł wrote: 2013/12/12 Graham Percival : Sorry, this awoke Grumpy Graham. I should have expected that. Yes, you should have. :P Happy new year, BTW. And you too!

Re: contributing instructions are misleading!

2014-01-01 Thread David Kastrup
Janek Warchoł writes: > Ah, you're absolutely right! > My point is The Golden Rule: he who does the work, makes the rules ;-) If you define "does the work" as "makes any change" which includes _undoing_ previous work, then this can be more succinctly expressed as "there are no rules". -- David

Re: contributing instructions are misleading!

2014-01-01 Thread Janek Warchoł
2014/1/1 Graham Percival : > On Tue, Dec 31, 2013 at 06:35:36PM +0100, Janek Warchoł wrote: >> 2013/12/12 Graham Percival : >> > Sorry, this awoke Grumpy Graham. >> >> I should have expected that. > > Yes, you should have. :P Happy new year, BTW. And you too! >> Anyway, there are two parts to

Re: contributing instructions are misleading!

2013-12-31 Thread Graham Percival
On Tue, Dec 31, 2013 at 06:35:36PM +0100, Janek Warchoł wrote: > 2013/12/12 Graham Percival : > > Sorry, this awoke Grumpy Graham. > > I should have expected that. Yes, you should have. :P Happy new year, BTW. > Anyway, there are two parts to this cg cleanup: > 1) removing obsolete info > 2)

Re: contributing instructions are misleading!

2013-12-31 Thread Janek Warchoł
Hi, 2013/12/12 Graham Percival : > On Wed, Dec 11, 2013 at 01:48:54PM +0100, Janek Warchoł wrote: >> PS ccing to Graham because he might be interested to know that >> Someone(TM) is doing Something(TM) to help new contributors! > > Sorry, this awoke Grumpy Graham. I should have expected that. Qui

Re: contributing instructions are misleading!

2013-12-12 Thread Urs Liska
Am 12.12.2013 10:02, schrieb David Kastrup: This is exactly the kind of information I'd need now too. (And being >in that situation I can't offer doing anything about it.) >One particular question I have could be answered in this thread. >If I'm not completely wrong the CG insists on installing a

Re: contributing instructions are misleading!

2013-12-12 Thread David Kastrup
Urs Liska writes: > Am 12.12.2013 05:26, schrieb Carl Peterson: >> 1) You need to be running Linux. >>1.1: If you aren't using Linux, you can run Linux within your >> current operating system with LilyDev by following these >> instructions [link] >>1.2: If you're already running Linux, g

Re: contributing instructions are misleading!

2013-12-12 Thread Urs Liska
Am 12.12.2013 09:42, schrieb Urs Liska: One particular question I have could be answered in this thread. If I'm not completely wrong the CG insists on installing and using git-cl for uploading patches. But if I'm not mistaken hardly anyone currently uses it. So _if_ there is a way to upload a p

Re: contributing instructions are misleading!

2013-12-12 Thread Urs Liska
Am 12.12.2013 05:26, schrieb Carl Peterson: On Wed, Dec 11, 2013 at 10:35 PM, Graham Percival mailto:gra...@percival-music.ca>> wrote Fixing this doesn't require a reorganization. It requires deleting the two incorrect bits, dumping a @ref{Submitting a patch} or whatever the @node

Re: contributing instructions are misleading!

2013-12-11 Thread Carl Peterson
On Wed, Dec 11, 2013 at 11:56 PM, Graham Percival wrote: > On Wed, Dec 11, 2013 at 11:26:55PM -0500, Carl Peterson wrote: > >In my searching, I didn't find a page that really did this. Section > 1.2 of > >the current CG should theoretically do this (based on the title), but > it > >mos

Re: contributing instructions are misleading!

2013-12-11 Thread Graham Percival
On Wed, Dec 11, 2013 at 11:26:55PM -0500, Carl Peterson wrote: >In my searching, I didn't find a page that really did this. Section 1.2 of >the current CG should theoretically do this (based on the title), but it >mostly just talks philosophically about git. Sounds good. I've never li

Re: contributing instructions are misleading!

2013-12-11 Thread Carl Peterson
On Wed, Dec 11, 2013 at 10:35 PM, Graham Percival wrote > > Fixing this doesn't require a reorganization. It requires > deleting the two incorrect bits, dumping a @ref{Submitting a > patch} or whatever the @node is called. On a similar note, > there's at least 2 "checklists before submitting a pa

Re: contributing instructions are misleading!

2013-12-11 Thread Graham Percival
On Wed, Dec 11, 2013 at 10:20:22PM -0500, Carl Peterson wrote: > I was able to connect to git with minimal fuss, and currently > use the lily-git.tcl tool to handle commits and patches. Great! This suggests that the introduction in the CG is ok. >All that said, where things got interesting f

Re: contributing instructions are misleading!

2013-12-11 Thread Carl Peterson
On Wed, Dec 11, 2013 at 9:54 PM, Graham Percival wrote: > On Wed, Dec 11, 2013 at 01:48:54PM +0100, Janek Warchoł wrote: > > PS ccing to Graham because he might be interested to know that > > Someone(TM) is doing Something(TM) to help new contributors! > > Sorry, this awoke Grumpy Graham. > > Reor

Re: contributing instructions are misleading!

2013-12-11 Thread Graham Percival
On Wed, Dec 11, 2013 at 01:48:54PM +0100, Janek Warchoł wrote: > PS ccing to Graham because he might be interested to know that > Someone(TM) is doing Something(TM) to help new contributors! Sorry, this awoke Grumpy Graham. Reorganizing the CG is very much a "something should be done, this is som

Re: contributing instructions are misleading!

2013-12-11 Thread Janek Warchoł
2013/12/10 Janek Warchoł : > 2013/12/7 Janek Warchoł : >> i'm infuriated. A new contributor had turned up, read CG and sent his >> patch to the "frogs" mailing list, which, as far as i know, is dead >> (and since lilynet is down, i'm not sure it's actually working at >> all). >> I'm so angry that

Re: contributing instructions are misleading!

2013-12-09 Thread David Kastrup
Janek Warchoł writes: > a first "hotfix" was already pushed > (http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=fcad9f183bb05f7206427bf5fc1b95fd8209d26e) > and i'm working on a bigger cleanup of first 3 chapters now. > Misleading information, fear me! > > best > j > > PS it seems tha

Re: contributing instructions are misleading!

2013-12-09 Thread Janek Warchoł
2013/12/7 Janek Warchoł : > i'm infuriated. A new contributor had turned up, read CG and sent his > patch to the "frogs" mailing list, which, as far as i know, is dead > (and since lilynet is down, i'm not sure it's actually working at > all). > > This is absolutely unacceptable. Not only is our

Re: contributing instructions are misleading!

2013-12-07 Thread Phil Holmes
- Original Message - From: "Janek Warchoł" To: "LilyPond Development Team" Sent: Saturday, December 07, 2013 5:15 PM Subject: contributing instructions are misleading! hi, i'm infuriated. A new contributor had turned up, read CG and sent his patch to the "frogs" mailing list, which

Re: contributing instructions are misleading!

2013-12-07 Thread James
On 07/12/13 17:15, Janek Warchoł wrote: hi, i'm infuriated. A new contributor had turned up, read CG and sent his patch to the "frogs" mailing list, which, as far as i know, is dead (and since lilynet is down, i'm not sure it's actually working at all). This is absolutely unacceptable. Not on