Re: ’Pond Jobs & Their Descriptions

Am Mittwoch, den 05.02.2020, 22:26 -0500 schrieb Kieren MacMillan: > Hi Graham, > > > Oh, that would definitely be a good idea! > > Okay, then! I’ll start with your suggestion to [paraphrasing:] > "summarize the jobs described in the CG", and prepare a skeleton > document where each entry is like

PATCHES - Countdown for February 6th

Hello, Here is the current patch countdown list. The next countdown will be on February 8th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ *** Push: 5732 Use unique_ptr in layout code - Dan Eble https://so

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On Feb 5, 2020, at 20:26, Thomas Morley wrote: > So to repeat myself, everyone should take his post literal, not offending! > > I'd love to see a community bearing different personalities, even > personalities with problematic conversation skills. > For me it's like strange english from a non-na

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

I've been following Lilypond mailing lists since 2016 or so. I'd describe my most common role as "entry-level tech support," answering the most basic mailing list questions so better-skilled people don't have to deal with them. I can point to the exact thread(s) that drew me into the Lilypond comm

Re: ’Pond Jobs & Their Descriptions

Hi Graham, > Oh, that would definitely be a good idea! Okay, then! I’ll start with your suggestion to [paraphrasing:] "summarize the jobs described in the CG", and prepare a skeleton document where each entry is like that one. > (I'm not quite certain about the "Receives From" and "Passes To"

Re: development process

Hi again, > Let's pick one person: Han-Wen. He's said that he has a few hours > to spend on LilyPond on Friday afternoon. Would he prefer to work > on resolving comments about his latest patch on scheme internals > (or whatever he's working on) ? Or would he prefer to spend time > communicating

Re: ’Pond Jobs & Their Descriptions

On Wed, Feb 05, 2020 at 09:24:37PM -0500, Kieren MacMillan wrote: > Job: Patch Formatter > Tasks: Ensure that a submitted patch conforms to the Lilypond code standards > (found and and ). > Requirements: a text editor; working knowledge of the programming language(s) > used in a given patch (po

Re: development process

Hi Graham, > Thought experiment: suppose that a complete newcomer posts to the > email list tomorrow, saying that he was interested in working on >bug #5542 cross-staff slur hides text in eps backend > (I picked randomly). > > Would anybody jump up and say "great! Let me help you get > start

Re: development process

On Wed, Feb 05, 2020 at 08:59:33PM -0500, Kieren MacMillan wrote: > > LilyPond has had a lot of patches get dropped because > > nobody feels comfortable reviewing / shepherding them. > > Seems to me like one solution to that problem might be a subtle > variant on extreme programming: All features/

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

David, > [...] the principal impact to be expected on LilyPond development > appears to have an official body entitled to censure my behavior and > eventually, out of a sense of duty, remove me. I won't definitely do that. > The general stance of the GNU project on its internal lists is to >

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

[Being on the return from Hawaii I'm late with everything, so please don't be surprised if I answer to stuff that has already been discussed to death.] > The preamble and intent is one thing; adding a corrective committee > with the authority to enact punishments based on anonymous reports > i

Re: ’Pond Jobs & Their Descriptions

Hi again, Graham: More concretely… Where can I go, in the CG or elsewhere, to find something that looks like this: Job: Patch Formatter Tasks: Ensure that a submitted patch conforms to the Lilypond code standards (found and and ). Requirements: a text editor; working knowledge of the programm

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Am Do., 6. Feb. 2020 um 02:55 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > I'd like to recommend that everyone argues with him, if you think he is > > wrong. > > Otherwise take his posts literal and _not_ offending. > > Not everybody likes to argue. So yes, I felt in a comfortable

Re: development process

Hi Graham (et al.), > LilyPond has had a lot of patches get dropped because > nobody feels comfortable reviewing / shepherding them. Seems to me like one solution to that problem might be a subtle variant on extreme programming: All features/fixes must be signed out for "patch-ing" by two devel

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Thomas Morley writes: > As an example look at the review of one of my own patches > https://codereview.appspot.com/270640043 > Quoting dak: > "This looks like a total mess." > "Total waste of effort." > "Aaand another one." Ouch. Fortunately in context this looks less dire ("Aaand another one."

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On Wed, Feb 5, 2020 at 7:37 PM Thomas Morley wrote: > > Hi all, > > Being on the lists for many years now I remember only a few posts > which were inappropriate: > > Long time ago. there was a user with a post others felt uncomfortable > with. But Graham denied a problem. But there was a followup

Re: ’Pond Jobs & Their Descriptions

Hi Carl, > More sources: > http://lilypond.org/doc/v2.19/Documentation/contributor/meisters > http://lilypond.org/doc/v2.19/Documentation/contributor/the-bug-squad Thanks! Very helpful links. Cheers, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www

Re: ’Pond Jobs & Their Descriptions

Hi David, > My own current concern, as explained in Salzburg I enjoyed your talk very much. > is to facilitate completely independent "zones of genius" for the kind of > half-user/half-programmer that embodies "power users" on the user list, > people developing complex solutions and engravers in

Re: ’Pond Jobs & Their Descriptions

Hi Graham, > If you want "extreme granularity", then wouldn't that be the whole > Contributor's Guide? Well, (a) for starters 'no'… ;) and (b) even if 'yes', it sure wouldn’t be best presented in that format. ;) > I suspect that you want a "less extremely granular" list No. I want what I ask

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Hi all, Being on the lists for many years now I remember only a few posts which were inappropriate: Long time ago. there was a user with a post others felt uncomfortable with. But Graham denied a problem. But there was a followup which definitely was. And Graham told the user that it was not appr

Re: ’Pond Jobs & Their Descriptions

On Wed, Feb 05, 2020 at 06:55:38PM -0500, Kieren MacMillan wrote: > I’m curious as to all the various jobs/tasks required to keep > Lilypond development moving forward at the fastest possible pace > and in the most efficient possible way. Is there a single list > compiled anywhere, written with an

Re: ’Pond Jobs & Their Descriptions

On 2/5/20, 4:55 PM, "lilypond-devel on behalf of Kieren MacMillan" wrote: Hello all! I’m curious as to all the various jobs/tasks required to keep Lilypond development moving forward at the fastest possible pace and in the most efficient possible way. Is there a single list com

Re: ’Pond Jobs & Their Descriptions

Kieren MacMillan writes: > Hello all! > > I’m curious as to all the various jobs/tasks required to keep Lilypond > development moving forward at the fastest possible pace and in the > most efficient possible way. Is there a single list compiled anywhere, > written with an eye to extreme granulari

Re: development process

On Wed, Feb 05, 2020 at 12:11:48AM +0100, David Kastrup wrote: > Han-Wen Nienhuys writes: > > For context, I have a busy daytime job. I work 80% so I can set aside > > a couple of hours of concentrated hacking time on Friday. Yes. I expect that most people knowledgeable about lilypond code are i

’Pond Jobs & Their Descriptions

Hello all! I’m curious as to all the various jobs/tasks required to keep Lilypond development moving forward at the fastest possible pace and in the most efficient possible way. Is there a single list compiled anywhere, written with an eye to extreme granularity? (The closest I can find is

Remaining sprint for the release of version 2.20

Whatever else may be on the plate, the immediate problem to be put behind us right now is the release of 2.20. I put specifically the translation team and Werner into Cc. The translation team should check what changes of the recent release of 2.19.84 they still need to get track of. Werner bas

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

śr., 5 lut 2020 o 23:47 Kieren MacMillan napisał(a): > I guess what confuses me about this whole discussion/thread — starting > with the Salzburg "roundtable", really — is how quickly it appears to > escalate from "let’s collaboratively design an ecosystem where everyone can > be in their Zone(s)

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

I'll try to speak only on the most pressing points to avoid bloating the discussion unnecessarily. śr., 5 lut 2020 o 14:41 David Kastrup napisał(a): > Janek Warchoł writes: > > In short, it's been found (I think Mike will be able to give you specific > > examples) that having code of conduct en

Re: Grow heap aggressively during music interpretation (issue 561390043 by hanw...@gmail.com)

Han-Wen Nienhuys writes: > On Wed, Feb 5, 2020 at 12:33 PM wrote: > > when you see things like: > > World-stopped marking took 187 msecs (77 in average) > In-use heap: 51% (40071 KiB pointers + 6357 KiB other) > > it means it took 187ms for GC, and then reclaimed 49% of the memory. > > If you of

Re: Grow heap aggressively during music interpretation (issue 561390043 by hanw...@gmail.com)

On Thu, Feb 6, 2020 at 12:19 AM Han-Wen Nienhuys wrote: > Um, that outputs a lot. Anything in particular? >> > > when you see things like: > > World-stopped marking took 187 msecs (77 in average) > In-use heap: 51% (40071 KiB pointers + 6357 KiB other) > > it means it took 187ms for GC, and then

Re: Grow heap aggressively during music interpretation (issue 561390043 by hanw...@gmail.com)

On Wed, Feb 5, 2020 at 12:33 PM wrote: > > Can you do some timings with different values for GC_MAXIMUM_HEAP_SIZE > , eg. > > > > GC_MAXIMUM_HEAP_SIZE=100M > > Not sure if you actually mean GC_MAXIMUM_HEAP_SIZE or rather > GC_INITIAL_HEAP_SIZE? > > I mean maximum, it sets the total amount of mem

Re: development process

Dear developers, tl;dr: * please continue those discussions to a constructive end * my experience as a non successful contributor after more than a year of (relative) abstinence from LilyPond, I enjoy reading the current drive in both commits and discussions in the aftermath of the Salzburg co

Issue 5740: Add \post to defer context actions to end of time step (issue 581600043 by nine.fierce.ball...@gmail.com)

Hi Dan, I've difficulties to understand what this is about. And my lack of C++-knowledge hinders my to deduce it. Could you give a ly-code-example which is not possible with current possibilities or where using current possibilities leads to some uglyness? https://codereview.appspot.com/5816000

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Hi David (et al.), > I am afraid that to some degree I am oblivious of > out-of-line behavior unless it hits me in the face. Which simply means that calling other people in on potentially problematic behaviour shouldn’t fall under your job description. No biggie! > There are multiple factors at

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Kieren MacMillan writes: > Here are my thoughts, in stream-of-consciousness order: > > 1. There were times ca. 2014–2017 (which was a rather tough time in my > life) in which my list behaviour should certainly have triggered an > "issue" under any reasonably-constructed CoC. Looking back, I wish

Re: [RFC] switch to GitLab / gitlab.com

Am Mittwoch, den 05.02.2020, 21:02 + schrieb pkx1...@posteo.net: > On 05/02/2020 16:13, Dan Eble wrote: > > On Feb 5, 2020, at 10:09, Jonas Hahnfeld < > > hah...@hahnjo.de > > > wrote: > > > required to synchronize the review and the associated issue. I propose > > > to start using GitLab hoste

Re: Documentation suggestions.

Dear Peter, it would be nice if you could register yourself at Rietveld. If you already have a Google account it should be straightforward, I think. Please see the updated issue at: https://codereview.appspot.com/579280043/ I didn't give you a very good patch - I really should have said "Note-n

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Hi all, I was just lurking, but now feel I should comment. Here are my thoughts, in stream-of-consciousness order: 1. There were times ca. 2014–2017 (which was a rather tough time in my life) in which my list behaviour should certainly have triggered an "issue" under any reasonably-constructed

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

David Kastrup writes: > Yes. Even given better communication by my side. If there are obvious > recipes to follow to place and extend and use one's own plugin package, > and if one so desires, submit it in a manner where other users may > install it on-demand, I hope that the option to abandon

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Urs Liska writes: > Am Mittwoch, den 05.02.2020, 21:21 +0100 schrieb David Kastrup: >> Urs Liska writes: >> >> > I must say that I haven't actually expressed an opinion about it so >> > far, and I don't know which I have. >> > >> > I don't feel uncomfortable without and wouldn't mind adding it

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Am Mittwoch, den 05.02.2020, 21:21 +0100 schrieb David Kastrup: > Urs Liska writes: > > > Am 5. Februar 2020 20:08:28 MEZ schrieb > > nine.fierce.ball...@gmail.com: > > > On 2020/02/05 18:17:25, c_sorensen wrote: > > > > I recognize that Mike Solomon has a different opinion. I mean > > > > no >

Re: Doc: Some miscellaneous suggestions from Peter Toye (issue 579280043 by michael.kaepp...@googlemail.com)

On 2020/02/05 14:51:03, lemzwerg wrote: > A nit. > > https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/input.itely > File Documentation/notation/input.itely (right): > > https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/input.itely#newcode

Issue 5736: Fix input/regression/context-find-parent.ly (issue 559460043 by nine.fierce.ball...@gmail.com)

Reviewers: , Message: Regtest differences attached to the ticket are expected. I would appreciate independent confirmation; is anyone interested in taking a little time to understand the case? After that, I think it will make sense to push this, since the code was reviewed last week and is just e

Re: Doc: Some miscellaneous suggestions from Peter Toye (issue 579280043 by michael.kaepp...@googlemail.com)

On 2020/02/05 14:14:47, Dan Eble wrote: > https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/rhythms.itely > File Documentation/notation/rhythms.itely (right): > > https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/rhythms.itely#newcode3325 >

Re: [RFC] switch to GitLab / gitlab.com

On 05/02/2020 16:13, Dan Eble wrote: On Feb 5, 2020, at 10:09, Jonas Hahnfeld wrote: required to synchronize the review and the associated issue. I propose to start using GitLab hosted on gitlab.com [4] for all of this: Repository, Issues, and Merge Requests (MR) for reviews. It was evaluated '

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

From: Mike Solomon Date: Wednesday, February 5, 2020 at 12:27 PM To: "janek.lilyp...@gmail.com" , "pkx1...@gmail.com" , "d...@gnu.org" , "karlinh...@gmail.com" , "jonas.hahnf...@gmail.com" , Carl Sorensen , "david.nales...@gmail.com" Cc: "lilypond-devel@gnu.org" , "re...@codereview-hr.apps

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

"Phil Holmes" writes: > I've kept out of this debate for a long time because a) I've only been > peripherally involved lately and b) there's been too much > communication for me to read, but > > As one of the earlier regular committers, and as the only person who > makes builds and updates the we

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Urs Liska writes: > Am 5. Februar 2020 20:08:28 MEZ schrieb nine.fierce.ball...@gmail.com: >>On 2020/02/05 18:17:25, c_sorensen wrote: >>> I recognize that Mike Solomon has a different opinion. I mean no >>disrespect to >>> Mike, Janek, Han-Wen, or any other member of the LilyPond team. I >>hig

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

- Original Message - From: To: ; ; ; ; ; ; ; Cc: ; Sent: Wednesday, February 05, 2020 7:08 PM Subject: Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com) On 2020/02/05 18:17:25, c_sorensen wrote: I recognize that Mike Solomon has a different opinion. I mean

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Am 5. Februar 2020 20:08:28 MEZ schrieb nine.fierce.ball...@gmail.com: >On 2020/02/05 18:17:25, c_sorensen wrote: >> I recognize that Mike Solomon has a different opinion. I mean no >disrespect to >> Mike, Janek, Han-Wen, or any other member of the LilyPond team. I >highly value >> the team sp

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On 2020/02/05 18:17:25, c_sorensen wrote: > I recognize that Mike Solomon has a different opinion. I mean no disrespect to > Mike, Janek, Han-Wen, or any other member of the LilyPond team. I highly value > the team spirit of the LilyPond team. >Well said. Here's the current tally as I understan

Re: Issue 5739: Add makefile targets for formatting all C++ code (issue 565620043 by nine.fierce.ball...@gmail.com)

On 2020/02/05 17:52:20, dak wrote: > configure.ac:367: STEPMAKE_PROGS(CLANG_FORMAT, clang-format-9 clang-format, > OPTIONAL, 9, 9) > Interesting. This gives a warning when it isn't installed? I think that we > don't usually flag dependencies of components not involved in either building or > runn

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On 2020/02/05 18:17:25, c_sorensen wrote: > I recognize that Mike Solomon has a different opinion. I mean no disrespect to > Mike, Janek, Han-Wen, or any other member of the LilyPond team. I highly value > the team spirit of the LilyPond team. Well said. Here's the current tally as I understand

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On 2020/02/05 18:17:25, c_sorensen wrote: > > On 2/5/20, 7:40 AM, "lilypond-devel on behalf of David Kastrup" > > wrote: > > Mike Solomon writes: > > > Janek Warcho

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On 2/5/20, 7:40 AM, "lilypond-devel on behalf of David Kastrup" wrote: Mike Solomon writes: > Janek Warchoł writes: > >> Hi, >> >> śr., 5 lut 2020, 00:34 użytkownik napisał: >> >>> What problem are we trying to solve here? >>> >> >> In shor

Re: development process

"Jürgen Reuter" writes: >Hi all, > >I fully agree with Han-Wen. I also could now and then (maybe once a >week) set aside 2-3 hours work for lily. But the current development >process really makes it hard for me to keep up submitting a patch (as >part of currently 11 commits

Re: Issue 5739: Add makefile targets for formatting all C++ code (issue 565620043 by nine.fierce.ball...@gmail.com)

https://codereview.appspot.com/565620043/diff/549530043/GNUmakefile.in File GNUmakefile.in (right): https://codereview.appspot.com/565620043/diff/549530043/GNUmakefile.in#newcode319 GNUmakefile.in:319: ## TODO: This condition speeds up make when formatting targets are not I would not really work

Re: Code of Conduct

Han-Wen Nienhuys writes: > A couple of people (me, Janek, Werner), want to add a CoC to the LilyPond > project, and there were some questions about why we would want to do that: > > There is a definite advantage to having a community with gentle > interactions and without flames and personal att

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: > Mike Solomon writes: > >>> What does "implement" mean? >> >> Sorry, I wasn't clear. I meant merge the PR. > >> Uh, words have meanings. There would be no point of putting something > into our documentation that we are not going to follow through with. > > By merging it, t

Issue 5739: Add makefile targets for formatting all C++ code (issue 565620043 by nine.fierce.ball...@gmail.com)

Reviewers: , Description: https://sourceforge.net/p/testlilyissues/issues/5739/ These are not yet intended for routine use by contributors. They are meant to help explore the differences between astyle and clang-format. Please review this at https://codereview.appspot.com/565620043/ Affected f

Re: New build:

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Wednesday, February 05, 2020 3:50 PM Subject: Re: New build: "Phil Holmes" writes: The web site is now fairly up-to-date. I say "fairly" because "news" has not been updated. I believe this is because the web

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: >> What does "implement" mean? > > Sorry, I wasn't clear. I meant merge the PR. > Uh, words have meanings. There would be no point of putting something into our documentation that we are not going to follow through with. By merging it, the idea would be that the first comm

Re: Documentation suggestions.

Dear Michael, That's very kind of you. When my life gets sorted out I may return to the fray. I've got a few comments below. I don't have a Reitveld account so can't reply there. Should I get one? I have another small patch for LR: Section 1.1.4 the first example needs the version number corre

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: >> What does "implement" mean? > > Sorry, I wasn't clear. I meant merge the PR. Uh, words have meanings. There would be no point of putting something into our documentation that we are not going to follow through with. -- David Kastrup

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

> What does "implement" mean? Sorry, I wasn't clear. I meant merge the PR.

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: > One procedural question: what are acceptance procedures for a PR like > this? There is good debate and a variety of opinions, but at a certain > point we will need to make a decision - do we implement the CoC or > not? What does "implement" mean? > I doubt that any new ar

Re: [RFC] switch to GitLab / gitlab.com

On Feb 5, 2020, at 10:09, Jonas Hahnfeld wrote: > > required to synchronize the review and the associated issue. I propose > to start using GitLab hosted on gitlab.com [4] for all of this: > Repository, Issues, and Merge Requests (MR) for reviews. It was > evaluated 'C' in 2015 [5] and should be

Re: Code of Conduct

Trevor writes: > Dan Eble wrote 05/02/2020 14:25:26 > Subject: Re: Code of Conduct > >>On Feb 5, 2020, at 05:45, Han-Wen Nienhuys wrote: >>> >>> Having a CoC gives us a set of guidelines, a process and a set of >>> corrective actions to take to help keep things nice. >> >>I prefer the implicit

Re: [RFC] switch to GitLab / gitlab.com

Jonas Hahnfeld writes: [Not repeating well-thought considerations] > Closing thoughts > > > GitLab has a feature called 'Repository mirroring' [8], working in both > directions. During the switching period, we could maintain Savannah as > our main repository and let GitLab pull

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

One procedural question: what are acceptance procedures for a PR like this? There is good debate and a variety of opinions, but at a certain point we will need to make a decision - do we implement the CoC or not? I doubt that any new arguments will emerge on either side. David has made several

Re[2]: Code of Conduct

Dan Eble wrote 05/02/2020 14:25:26 Subject: Re: Code of Conduct On Feb 5, 2020, at 05:45, Han-Wen Nienhuys wrote: Having a CoC gives us a set of guidelines, a process and a set of corrective actions to take to help keep things nice. I prefer the implicit good-neighbour agreement we have n

Re: New build:

"Phil Holmes" writes: > The web site is now fairly up-to-date. I say "fairly" because "news" > has not been updated. I believe this is because the website is > actually built automatically from master, whereas I updated news in > stable/2.20. I guess the simplest option is to cherry-pick my up

Re: New build:

"Phil Holmes" writes: > - Original Message - From: "David Kastrup" > To: "Phil Holmes" > Cc: ; > Sent: Wednesday, February 05, 2020 3:05 PM > Subject: Re: New build: > > >> David Kastrup writes: >> >>> "Phil Holmes" writes: The build completed successfully, as did the uploa

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: > Mike Solomon writes: > >> The preamble and intent is one thing; adding a corrective committee >> with the authority to enact punishments based on anonymous reports >> is another. It implements hierarchies and institutions exerting >> coercive power based on incomplete and

Re: New build:

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: ; Sent: Wednesday, February 05, 2020 3:05 PM Subject: Re: New build: David Kastrup writes: "Phil Holmes" writes: The build completed successfully, as did the upload, so anyone looking at the manuals on lilypond.o

Re: development process

Kevin Barry writes: > I don't know if lurkers' opinions count, but on the subject of potential > replacements for Savannah/Sourceforge: I am part of a team that administer > both Gerrit and Gitlab in-house deployments. If choosing between them I > would advocate for Gitlab because it includes iss

RE: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: > The preamble and intent is one thing; adding a corrective committee with the > authority to enact punishments based on anonymous reports is another. It > implements hierarchies and institutions exerting coercive power based on > incomplete and secret information. That

Re: development process

Hi all, > I don't know if lurkers' opinions count I hope so, because I’m about to give another one… ;) > Gerrit is a good code review tool, but for various reasons > that may be our own fault, it is deeply unpopular where I work. I know very few of these tools — my deepest version control expe

[RFC] switch to GitLab / gitlab.com

(Note: I wrote this in ~1 hour, so some details are not thought through yet. I rather want this to serve as an example of a concrete proposal to change one thing at a time.) What this proposal is about === Right now, LilyPond's source code is hosted on Savannah [1], our is

Re: development process

I don't know if lurkers' opinions count, but on the subject of potential replacements for Savannah/Sourceforge: I am part of a team that administer both Gerrit and Gitlab in-house deployments. If choosing between them I would advocate for Gitlab because it includes issue tracking and CI/CD so perha

Re: New build:

David Kastrup writes: > "Phil Holmes" writes: >> >> The build completed successfully, as did the upload, so anyone looking >> at the manuals on lilypond.org will see 19.84 information. However, >> the website has not built, I think because VERSION in master has not >> been updated. I've pushed

Re: Doc: Some miscellaneous suggestions from Peter Toye (issue 579280043 by michael.kaepp...@googlemail.com)

A nit. https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/input.itely File Documentation/notation/input.itely (right): https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/input.itely#newcode464 Documentation/notation/input.itely:464: escaped

RE: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Janek Warchoł writes: > Hi, > > śr., 5 lut 2020, 00:34 użytkownik napisał: > >> What problem are we trying to solve here? >> > > In short, it's been found (I think Mike will be able to give you > specific > examples) that having code of conduct encourages contributions from > newcomers. > I r

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Another remark: Mike Solomon writes: > At the Salzburg meetup, one common thing a lot of people brought up > was a slow-down in development and a shrinking pool of contributors. > IMO we should do several experiments to fix this. The CoC I proposed > is used in over 40,000 projects including m

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Mike Solomon writes: > Janek Warchoł writes: > >> Hi, >> >> śr., 5 lut 2020, 00:34 użytkownik napisał: >> >>> What problem are we trying to solve here? >>> >> >> In short, it's been found (I think Mike will be able to give you >> specific >> examples) that having code of conduct encourages con

Re: Code of Conduct

On Feb 5, 2020, at 05:45, Han-Wen Nienhuys wrote: > > Having a CoC gives us a set of guidelines, a process and a set of > corrective actions to take to help keep things nice. I prefer the implicit good-neighbour agreement we have now. — Dan

Re: New build:

"Phil Holmes" writes: > - Original Message - From: "David Kastrup" > To: "Phil Holmes" > Cc: "Jonas Hahnfeld" ; "Dan Eble" ; > "Masamichi Hosoda" ; ; > > Sent: Tuesday, February 04, 2020 5:34 PM > Subject: Re: Inline assembler fallback for _FPU_SETCW() missing in > MINGW libraries (is

Re: Doc: Some miscellaneous suggestions from Peter Toye (issue 579280043 by michael.kaepp...@googlemail.com)

https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/rhythms.itely File Documentation/notation/rhythms.itely (right): https://codereview.appspot.com/579280043/diff/579290043/Documentation/notation/rhythms.itely#newcode3325 Documentation/notation/rhythms.itely:3325: bar

New build: was:Inline assembler fallback for _FPU_SETCW() missing in MINGW libraries (issue 577450043 by thomasmorle...@gmail.com)

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "Jonas Hahnfeld" ; "Dan Eble" ; "Masamichi Hosoda" ; ; Sent: Tuesday, February 04, 2020 5:34 PM Subject: Re: Inline assembler fallback for _FPU_SETCW() missing in MINGW libraries (issue 577450043 by thomasmorle...@gma

Re: Grow heap aggressively during music interpretation (issue 561390043 by hanw...@gmail.com)

Dan Eble writes: > On Feb 5, 2020, at 07:59, jonas.hahnf...@gmail.com wrote: >> >> and it seems stable, but I have yet to build a theory why OS thread >> migration actually improves performance… > > Educated guess: The core gets too hot. The OS is not allowed to move > the thread to a cooler co

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Janek Warchoł writes: > Hi, > > śr., 5 lut 2020, 00:34 użytkownik napisał: > >> What problem are we trying to solve here? >> > > In short, it's been found (I think Mike will be able to give you specific > examples) that having code of conduct encourages contributions from > newcomers. I rather

Re: Grow heap aggressively during music interpretation (issue 561390043 by hanw...@gmail.com)

On Feb 5, 2020, at 07:59, jonas.hahnf...@gmail.com wrote: > > and it seems stable, but I have yet to build a theory why OS thread > migration actually improves performance… Educated guess: The core gets too hot. The OS is not allowed to move the thread to a cooler core, so it throttles the clo

Re: development process

On Feb 5, 2020, at 06:57, David Kastrup wrote: > > Our current process is awkward technically, not because of the roles its > human players assume. +1(000) For a long time, the LilyPond project has needed these: 1. more and better automation to reduce the load on the (amazingly persever

Re: Documentation suggestions.

Hello Peter, Am 04.02.2020 um 10:44 schrieb Peter Toye: I'm posting this here, as no-one on the devel list has answered, although most of the discussion went on in that list. I think that many developers spend their effort on core topics like the guile-2/3 transition, or improving the contrib

Doc: Some miscellaneous suggestions from Peter Toye (issue 579280043 by michael.kaepp...@googlemail.com)

Reviewers: , Description: Doc: Some miscellaneous suggestions from Peter Toye Peter Toye suggested some additions/corrections to the manuals a while ago in https://lists.gnu.org/archive/html/lilypond-devel/2019-12/msg00191.html and https://lists.gnu.org/archive/html/bug-lilypond/2020-02/msg000

Re: Grow heap aggressively during music interpretation (issue 561390043 by hanw...@gmail.com)

Some more numbers: I took guile22-experiment and removed the following: * GC_set_free_space_divisor, * GC_INITIAL_HEAP_SIZE=40M * heap growing in Score_engraver This gives me: ~2m30s (although I saw one run in 1m55s?!?) GC_INITIAL_HEAP_SIZE=40M: ~2m10s (one run in 1m40s) GC_FREE_SPACE_DIVISOR=1

Re: Doc: Correct and extend infos about LilyDev setup (issue 561360043 by michael.kaepp...@googlemail.com)

Il giorno sab 1 feb 2020 alle ore 00:17 Michael Käppler ha scritto: > Am 30.01.2020 um 14:17 schrieb fedel...@gmail.com: > > > https://codereview.appspot.com/561360043/diff/565550050/Documentation/contributor/quick-start.itexi > > File Documentation/contributor/quick-start.itexi (right): > > > >

Re: development process

Thomas Morley writes: > Am Mi., 5. Feb. 2020 um 00:12 Uhr schrieb David Kastrup : >> >> Han-Wen Nienhuys writes: >> >> >Rietveld and my local commits are not linked. If I change my commits, I >> >update my commit message. I have to copy those changes out to Rietveld >> > by >> >hand

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

On 2020/02/05 09:03:22, hahnjo wrote: > In my opinion we should have a thread on lilypond-devel. In particular it should > lay out what the motivation is / which problem is to be solved. (see questions > by David and Karlin) Other questions: You're asking for agreement from "the whole LilyPond co

Re: Inline assembler fallback for _FPU_SETCW() missing in MINGW libraries (issue 577450043 by thomasmorle...@gmail.com)

Thomas Morley writes: > Am Di., 4. Feb. 2020 um 18:34 Uhr schrieb David Kastrup : >> >> "Phil Holmes" writes: >> >> > - Original Message - From: "David Kastrup" >> >> Wow. Ok, maybe I'll just apply this patch then (though I'll at >> >> least >> >> remove the conditioning on Apple here

  1   2   >