Am Donnerstag, den 06.02.2020, 21:34 -0600 schrieb Karlin High:
> On Wed, Feb 5, 2020 at 9:09 AM Jonas Hahnfeld <
> hah...@hahnjo.de
> > wrote:
> > I propose
> > to start using GitLab hosted on gitlab.com [4] for all of this:
> > Repository, Issues, and Merge Requests (MR) for reviews.
>
> A
Il giorno gio 6 feb 2020 alle 23:04, Carl Sorensen
ha scritto:
I think that the presence (in the proposed CoC )of an enforcement
committee that has the power to sanction participants in response to
anonymous complaints is more than just a bit of prose. It's the
creation of a new structure
On 2/6/20, 6:28 PM, "lilypond-devel on behalf of Flaming Hakama by Elaine"
wrote:
Regarding the CoC.
If there is no enforcement, then it is not clear what is the point.
Perhaps the point is to provide a support system, so that somebody who feels
marginalized has others on
Hi Wol,
> Rather than jobs as in people, why not jobs as in tasks?
That’s really what I’m doing (though I may have failed to make that clearer): a
person can certainly take on more than one job/task.
> Take your list of jobs like "Patch Formatter", and change it into a list
> of stages a patch
Hi Elaine,
> * The current process relies too heavily on one contributor, and any
> improvements to the process will inherently invovle untangling the many
> hats being worn by the current BDFL, such that others can wear them--and
> probably also reconstituting the hat wardrobe.
>
> * Those who
On Wed, Feb 5, 2020 at 9:09 AM Jonas Hahnfeld wrote:
> I propose
> to start using GitLab hosted on gitlab.com [4] for all of this:
> Repository, Issues, and Merge Requests (MR) for reviews.
A thread in 2018 explored GitLab's feasibility for LilyPond.
Regarding the CoC.
If there is no enforcement, then it is not clear what is the point.
In the abstract, such a document could help to set expectations of
behavior, including clarifying types of behavior that is considered
unacceptable. Such that everyone/anyone in the community would be able to
On 2/6/2020 2:45 PM, David Kastrup wrote:
I am working on an Email signature that might be helping to convey the
message.
Nice idea, but sometimes drawing attention to a problem only makes
things worse. How about focusing on the success mode instead of the
failure mode?
"
I aim to
On 06/02/20 13:24, Kieren MacMillan wrote:
> Why not let someone less experienced — and thus less "valuable" — start with
> that job as a "softball" to ease their way into the development pool, freeing
> up higher-level developers to (as you say) spend your time where it matters?
> To me, doing
On Feb 6, 2020, at 18:35, Paolo Prete wrote:
>
> (I re-post this here, because it's a bug and maybe you have an easy fix for
> it)
Paolo,
I'm not sure where you're re-posting from, but the expected forum for bug
reports is https://lists.gnu.org/mailman/listinfo/bug-lilypond . The audience
(I re-post this here, because it's a bug and maybe you have an easy fix for
it)
Hello,
please consider this snippet:
%%%
{
\override Staff.TextSpanner.bound-details.left.text = \markup { \small
\bold "Rit." }
\once \override Slur.outside-staff-priority = 100
\once \override
On 2/6/20, 3:03 PM, "lilypond-devel on behalf of kieren_macmillan
kieren_macmillan" wrote:
We lost at least 30 [!!] person-years of extremely high-level programming
assistance because of the past tone in this community — yes, I can justify
that
claim with concrete data —
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Italian team of translators. The file is available at:
https://translationproject.org/latest/lilypond/it.po
(We can arrange things so
Hi James (et al.),
> Goodness gracious!
> Do all those who feel so positive about CoCs not see how that paragraph
> above is just so bloody soul destroying?
No. Please explain.
> I don't need a document written by a committee of people that I have no
> say over (i.e. what we do in the real
Hi
In lily/main.cc I read:
304/* Translators, please translate this string as
305 "Report bugs in English via %s",
306 or if there is a LilyPond users list or forum in your language
307 "Report bugs in English via %s or in YOUR_LANG via URI" */
308 printf ("%s", (_f ("You found a bug? Please
https://codereview.appspot.com/579280043/diff/563480043/Documentation/learning/common-notation.itely
File Documentation/learning/common-notation.itely (right):
https://codereview.appspot.com/579280043/diff/563480043/Documentation/learning/common-notation.itely#newcode162
On 2020/02/06 15:00:35, lemzwerg wrote:
> An important nit to check...
>
> Besides this, LGTM, thanks!
>
>
https://codereview.appspot.com/579280043/diff/567170044/Documentation/notation/input.itely
> File Documentation/notation/input.itely (right):
>
>
On 2/6/20, 1:46 PM, "lilypond-devel on behalf of David Kastrup"
wrote:
>
> Apple carts unfortunately get upset once in a while. That is just life.
Well, one can make them more robust, and that may be worth thinking
about.
--
David Kastrup
My replies
On 06/02/2020 15:37, David Kastrup wrote:
Werner LEMBERG writes:
I'd like to recommend that everyone argues with him [David K.], if
you think he is wrong. Otherwise take his posts literal and _not_
offending.
That's it.
But new contributors cannot be expected to know, and also it takes
James Lowe writes:
> On 06/02/2020 15:37, David Kastrup wrote:
>> Werner LEMBERG writes:
>>
I'd like to recommend that everyone argues with him [David K.], if
you think he is wrong. Otherwise take his posts literal and _not_
offending.
>>> That's it.
>> But new contributors
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the French team of translators. The file is available at:
https://translationproject.org/latest/lilypond/fr.po
(We can arrange things so
Jean-Charles Malahieude writes:
> Le 06/02/2020 à 20:10, Benkő Pál a écrit :
>> the News section at lilypond.org dates 2.19.84 to 2019. can I (or
>> anyone else) push a fix to staging?
>>
>
> I would prefer Phil or David to take care of this silly calendar not
> wanting to go ahead…
Hopefully
Le 06/02/2020 à 20:10, Benkő Pál a écrit :
the News section at lilypond.org dates 2.19.84 to 2019. can I (or
anyone else) push a fix to staging?
I would prefer Phil or David to take care of this silly calendar not
wanting to go ahead…
Cheers,
--
Jean-Charles
the News section at lilypond.org dates 2.19.84 to 2019. can I (or
anyone else) push a fix to staging?
Jean-Charles Malahieude ezt írta (időpont: 2020.
febr. 6., Cs, 18:46):
>
> Hi,
>
> Please find a new tarball for LilyPond at
>
>
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'lilypond' has been made available
to the language teams for translation. It is archived as:
Le 05/02/2020 à 23:30, Michael Käppler a écrit :
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/
You don't need a
Le 06/02/2020 à 00:44, David Kastrup a écrit :
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
Hi,
Please find a new tarball for LilyPond at
http://lilypond.org/download/source/v2.19/lilypond-2.19.84.tar.gz
Cheers,
--
Jean-Charles Malahieude
Jonas Hahnfeld writes:
> Hi David,
>
> Am Donnerstag, den 06.02.2020, 00:44 +0100 schrieb David Kastrup:
>> Whatever else may be on the plate, the immediate problem to be put
>> behind us right now is the release of 2.20.
>
> fantastic!
>
>> I put specifically the
>> translation team and Werner
Hi David,
Am Donnerstag, den 06.02.2020, 00:44 +0100 schrieb David Kastrup:
> Whatever else may be on the plate, the immediate problem to be put
> behind us right now is the release of 2.20.
fantastic!
> I put specifically the
> translation team and Werner into Cc. The translation team should
-
Thursday, February 6, 2020, 3:00:35 PM, you wrote:
> An important nit to check...
> Besides this, LGTM, thanks!
> https://codereview.appspot.com/579280043/diff/567170044/Documentation/notation/input.itely
> File Documentation/notation/input.itely (right):
>
On Feb 6, 2020, at 09:32, Kieren MacMillan
wrote:
>
>> So what I want to work on is some sort of ”Splittable Staff“.
This terminology looks at the use case from a point of view that might not be
very consistent with LilyPond. Let's think carefully about what we want to
call this, because
Werner LEMBERG writes:
>> I'd like to recommend that everyone argues with him [David K.], if
>> you think he is wrong. Otherwise take his posts literal and _not_
>> offending.
>
> That's it.
But new contributors cannot be expected to know, and also it takes time
until the emotional response
Hi David,
> No, the problem is that this solution to the problems of bad actors
> addresses a problem that we do not have to a relevant degree. At least
> I hope we can agree that my intent is not doling out damage to the
> project.
Your original quote
>>> The problem with an approach focused
> I'd like to recommend that everyone argues with him [David K.], if
> you think he is wrong. Otherwise take his posts literal and _not_
> offending.
That's it.
Werner
Kieren MacMillan writes:
> Hi David,
>
>> The problem with an approach focused on punishment and expulsion is that
>> it helps isolating and eventually ostracizing bad actors, limiting the
>> total damage they may cause.
>
> "Limiting the total damage they may cause" is a "problem"? You
>
Hi David,
> The problem with an approach focused on punishment and expulsion is that
> it helps isolating and eventually ostracizing bad actors, limiting the
> total damage they may cause.
"Limiting the total damage they may cause" is a "problem"? You definitely have
me confused on that one.
Federico Bruni writes:
> Il giorno mer 5 feb 2020 alle 10:20, Thomas Morley
> ha scritto:
>> FWIW,
>> cd gub
>> make LILYPOND_BRANCH=stable/2.20 lilypond
>> succeeded now on my machine, Ubuntu 18.04 64-bit
>
> I've run the same command in LilyDev, but the files generated are for
> 2.19.84. Is
An important nit to check...
Besides this, LGTM, thanks!
https://codereview.appspot.com/579280043/diff/567170044/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
Kieren MacMillan writes:
> Hi James,
>
>> I am still struggling to understand the point of a COC for the LP
>> project, other than some kind of ... what is the term ... virtue
>> signalling or something that a project does *after* someone says
>> something that happens to be offensive to someone
On 2020/02/06 09:59:26, hanwenn wrote:
> can you add a pointer to the commit that introduces the previous code?
I'm in
> the middle of a laptop switch , so I can't look it up right now.
I've added this link to the description of the current review.
Hi Karlin,
> 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.
That "job" is going on my list. :)
> I can
Hi James,
> I am still struggling to understand the point of a COC for the LP project,
> other than some kind of ... what is the term ... virtue signalling or
> something that a project does *after* someone says something that happens to
> be offensive to someone else - which is just, life
Il giorno mer 5 feb 2020 alle 10:20, Thomas Morley
ha scritto:
FWIW,
cd gub
make LILYPOND_BRANCH=stable/2.20 lilypond
succeeded now on my machine, Ubuntu 18.04 64-bit
I've run the same command in LilyDev, but the files generated are for
2.19.84. Is it normal?
Here's the tail of the
Hi Valentin,
> As it is I think one of the important features missing in Lilypond is the
> ability to split one staff into multiple staves, which is a feature quite
> nescessary for orchestral and choral settings.
The term "missing" is perhaps misleading: I do exactly this all the time. That
Reviewers: thomasmorley651, hanwenn,
Message:
The reviewers are turning the first question I asked around and asking
it back to me. I don't know if this is useful without other stuff I've
been working on. That's why I've posted it for review. I thought that
you (well, mainly I thought that
Hi David,
> The way I read the request I thought is was more about having an
> organizational document, not for the sake of getting a submission in,
> but rather for understanding where help in improving the processes (by
> code or manual labor) would be appreciated, and what kind of expertise
>
Valentin Petzel writes:
> Hello,
>
> As it is I think one of the important features missing in Lilypond is the
> ability to split one staff into multiple staves, which is a feature quite
> nescessary for orchestral and choral settings. There is an ”official“ hack to
> do
> it by using
David Kastrup ezt írta (időpont: 2020. febr. 6., Cs, 14:38):
>
> Benkő Pál writes:
>
> > Janek Warchoł ezt írta (időpont: 2020.
> > febr. 6., Cs, 0:32):
> >>
> >> I'll try to speak only on the most pressing points to avoid bloating the
> >> discussion unnecessarily.
> >>
> >> I stopped
Hi Jonas,
> certainly not a "Patch Formatter", that's part of the review process
> which is no job, every developer should participate.
The largest [commercial] programming project I was ever on had about 40
developers working on it. When I first joined, they put me on code formatting
[only]
Jonas Hahnfeld writes:
> Am Mittwoch, den 05.02.2020, 21:24 -0500 schrieb Kieren MacMillan:
>> 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
Benkő Pál writes:
> Janek Warchoł ezt írta (időpont: 2020.
> febr. 6., Cs, 0:32):
>>
>> I'll try to speak only on the most pressing points to avoid bloating the
>> discussion unnecessarily.
>>
>> I stopped contributing to LilyPond about 6 years ago. One cause of that
>> change was that I got a
Hi Han-Wen,
> I think this is going at it from the wrong direction.
I think you may not be the only one. =)
> The above tasks are what automation is for. For example, with clang-format,
> you can have a process that would automatically check if a patch is correctly
> formatted. The whole
Hi Urs,
> If I'm not mistaken such a list wouldn't/shouldn't imply that
> separating jobs relies on assigning one job per person
Correct. Someone *could* do just one of those things, but likely wouldn’t.
> It *might* be misleading someone to think your effort would go in that
> direction of a
Am Donnerstag, den 06.02.2020, 00:27 +0100 schrieb David Kastrup:
> Han-Wen Nienhuys <
> hanw...@gmail.com
> > writes:
>
> > On Wed, Feb 5, 2020 at 12:33 PM <
> > jonas.hahnf...@gmail.com
> > > wrote:
> >
> > when you see things like:
> >
> > World-stopped marking took 187 msecs (77 in average)
Hello,
As it is I think one of the important features missing in Lilypond is the
ability to split one staff into multiple staves, which is a feature quite
nescessary for orchestral and choral settings. There is an ”official“ hack to
do
it by using different staves and switching context, but
Janek Warchoł ezt írta (időpont: 2020.
febr. 6., Cs, 0:32):
>
> I'll try to speak only on the most pressing points to avoid bloating the
> discussion unnecessarily.
>
> I stopped contributing to LilyPond about 6 years ago. One cause of that
> change was that I got a job and suddenly had much less
Am Mi., 5. Feb. 2020 um 17:47 Uhr schrieb Phil Holmes :
>
> - 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
can you add a pointer to the commit that introduces the previous code?
I'm in the middle of a laptop switch , so I can't look it up right now.
https://codereview.appspot.com/559460043/
Hello,
I am still struggling to understand the point of a COC for the LP
project, other than some kind of ... what is the term ... virtue
signalling or something that a project does *after* someone says
something that happens to be offensive to someone else - which is just,
life isn't it?
I haven't looked in detail at the code, but I couldn't work out why you
want to add this, and that is probably the most important piece of
information to decide how to best go about implementing it.
>From a cursory reading, you want to set a context property at a specific
point in the engraver
On Thu, Feb 6, 2020 at 2:40 AM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> > I suspect that you want a "less extremely granular" list
>
> No. I want what I asked for: a hyper-granular list like
>
>Patch-Related Jobs:
>Patch Coding
>Patch Mentoring
>Patch
Werner,
czw., 6 lut 2020, 03:46 użytkownik Werner LEMBERG napisał:
>
> > 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
David,
czw., 6 lut 2020, 02:55 użytkownik David Kastrup napisał:
> Not everybody likes to argue. So yes, I felt in a comfortable space
> with you and it was a productive exchange where I was not aware of any
> potential for controversy. But I'll agree that it sends an awful
> message to
Am Mittwoch, den 05.02.2020, 21:24 -0500 schrieb Kieren MacMillan:
> 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
Let me write a clarification and a disclaimer. It was not the purpose of my
email to blame people. If someone (especially David) felt attacked, I
apologize. I wanted to express how I view the situation, and I may be
mistaken in my opinions. I don't claim to hold the objective truth.
czw., 6 lut
66 matches
Mail list logo
