Le 29/10/2022 à 06:34, Ian Kelling a écrit :
I have an update. A lists.gnu.org user from emacs helped me identify
some occasional backlogs that were happening, causing 2 - 3 hour delays
of some messages every once in a while. I've done a deep dive into the
performance of the system, identified so
Ian Kelling writes:
> Jean Abou Samra writes:
>
>> Hello, dear administrators of GNU list servers,
>>
>> Sorry for the possible double post, I was not sure which address to
>> send this to. This is to let you know that mailing lists related
>> to the GNU
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Thus I wrote to the general GNU list server admins and proposed
>> to step up for being an admin on these lists, just like I am
>> already an admin on lilypond-user-fr (the French-speaking equivalent
>> of lilypond-user, in case you didn't kno
> On Oct 7, 2022, at 4:47 PM, Dan Eble wrote:
>
> On Oct 7, 2022, at 16:45, Jean Abou Samra wrote:
>
>> Thus I wrote to the general GNU list server admins and proposed
>> to step up for being an admin on these lists, just like I am
>> already an admin on lilypond-user-fr (the French-speakin
Jean Abou Samra writes:
> Thus I wrote to the general GNU list server admins and proposed
> to step up for being an admin on these lists, just like I am
> already an admin on lilypond-user-fr (the French-speaking equivalent
> of lilypond-user, in case you didn't know).
>
> Is that OK with everyon
> Is that OK with everyone?
+1
Werner
On Oct 7, 2022, at 16:45, Jean Abou Samra wrote:
> Thus I wrote to the general GNU list server admins and proposed
> to step up for being an admin on these lists, just like I am
> already an admin on lilypond-user-fr (the French-speaking equivalent
> of lilypond-user, in case you didn't know).
>
Hi,
This email is cross-posted to lilypond-user, lilypond-devel
and bug-lilypond. The admin for these three lists (d...@gnu.org,
apparently David R. Linn) has not been active in the project for
a long time, and I have not been able to reach him by email.
This is problematic because you need an ad
Le 17/06/2022 à 18:44, Aaron Hill a écrit :
On 2022-06-17 9:36 am, Ian Kelling wrote:
Aaron Hill writes:
On 2022-06-17 9:07 am, Ian Kelling wrote:
Can confirm: no appreciable delay. Moderation could make sense here,
although it would not explain why regular users of the lists experience
this
On 2022-06-17 9:36 am, Ian Kelling wrote:
Aaron Hill writes:
On 2022-06-17 9:07 am, Ian Kelling wrote:
Can confirm: no appreciable delay. Moderation could make sense here,
although it would not explain why regular users of the lists
experience
this delay intermittently. Is there some compo
Aaron Hill writes:
> On 2022-06-17 9:07 am, Ian Kelling wrote:
> Can confirm: no appreciable delay. Moderation could make sense here,
> although it would not explain why regular users of the lists experience
> this delay intermittently. Is there some component that randomly
> selects emails f
Jean Abou Samra writes:
> Regarding listhelper, I didn't know about it. I'm not sure
> if it's enabled on lilypond-user or lilypond-devel, but judging
> from
> https://savannah.gnu.org/maintenance/ListHelperAntiSpam/,
> it is not enabled on lilypond-user-fr (there's no non-human address
> in th
On 2022-06-17 9:07 am, Ian Kelling wrote:
Aaron Hill writes:
In case it helps, your very message to the list was delayed
significantly.
I presume I hadn't posted to lilypond-devel before, so it was held for
moderation and the listhelpers were asleep, they approved it after they
woke up. So,
Le 17/06/2022 à 18:07, Ian Kelling a écrit :
Aaron Hill writes:
In case it helps, your very message to the list was delayed
significantly.
I presume I hadn't posted to lilypond-devel before, so it was held for
moderation and the listhelpers were asleep, they approved it after they
woke up. So
Ian Kelling writes:
> Aaron Hill writes:
>
>> In case it helps, your very message to the list was delayed
>> significantly.
>
> I presume I hadn't posted to lilypond-devel before, so it was held for
> moderation and the listhelpers were asleep, they approved it after they
> woke up. So, this w
Aaron Hill writes:
> In case it helps, your very message to the list was delayed
> significantly.
I presume I hadn't posted to lilypond-devel before, so it was held for
moderation and the listhelpers were asleep, they approved it after they
woke up. So, this was case #1. Again, I encourage the
Le 17/06/2022 à 16:15, Aaron Hill a écrit :
On 2022-06-16 7:54 pm, Ian Kelling wrote:
#3, least common: sometimes there is an issue with a specific mail
server which causes delays. This can often be fixed. I'm happy to check
if that is the case, just email the details of the message to
mail..
On 2022-06-16 7:54 pm, Ian Kelling wrote:
#3, least common: sometimes there is an issue with a specific mail
server which causes delays. This can often be fixed. I'm happy to check
if that is the case, just email the details of the message to
mail...@gnu.org. If it hasn't been posted, wait at lea
Jean Abou Samra writes:
> Hello, dear administrators of GNU list servers,
>
> Sorry for the possible double post, I was not sure which address to
> send this to. This is to let you know that mailing lists related
> to the GNU LilyPond project have recently been experi
On Jun 17, 2022, at 02:18, Jean Abou Samra wrote:
>
>> we do. Does lilypond want one or more of their lists to be one of the
>> initial group to move to mailman 3?
>
> Yes, I'd be in favor of doing that. Others, what do you
> think?
fine
—
Dan
>> Does lilypond want one or more of their lists to be one of the
>> initial group to move to mailman 3?
>
> Yes, I'd be in favor of doing that. Others, what do you
> think?
I support that, at least for 'lilypond-devel'.
Werner
Hi,
Thanks for your reply.
Le 17/06/2022 à 04:54, Ian Kelling a écrit :
Jean Abou Samra writes:
Hello, dear administrators of GNU list servers,
Sorry for the possible double post, I was not sure which address to
send this to. This is to let you know that mailing lists related
to the GNU
Hello, dear administrators of GNU list servers,
Sorry for the possible double post, I was not sure which address to
send this to. This is to let you know that mailing lists related
to the GNU LilyPond project have recently been experiencing abnormal
distribution delays. Even though this has been
/html/lilypond-devel/2010-11/msg00076.html
** Other projects
The idea of private mailing lists is hardly uncommon in
open-source software. For example,
http://lwn.net/Articles/394660/ about debian-private
http://subversion.apache.org/mailing-lists.html private@
http://www.freebsd.org/admini
2011/7/27 Graham Percival :
> Most people seem to like the status quo.
>
> http://lilypond.org/~graham/gop/gop_6.html
>
> ** Proposal summary
>
> Potentially sensitive or private matters will be referred to
> Graham. He will then decide who should discuss the matter on an
> ad-hoc basis, and forwar
://lists.gnu.org/archive/html/lilypond-devel/2010-09/msg00178.html
http://news.lilynet.net/spip.php?article121
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00076.html
** Other projects
The idea of private mailing lists is hardly uncommon in
open-source software. For example,
http
2011/7/22 Graham Percival
> ** Proposal summary
>
> What should we do with potentially sensitive or private matters in
> lilypond? I see two possible solutions:
>
> 1. Pick one person to manage private discussions.
> 2. Have a private mailing list with a known list of people who
> will discuss
Graham Percival writes:
> I'll reiterate that I don't think this is a great long-term
> solution -- I view the "private CCing" idea as a temporary
> compromise for the next 12-18 months. Once we've gotten into the
> habit of regular releases, a more firm set of development
> proposals+guidelines
On Fri, Jul 22, 2011 at 08:20:04PM +0200, Valentin Villenave wrote:
> Once again, you make some excellent points.However if said list has to
> be limited to *five* people, I do question the need for a mailing list
> at all, rather than merely CCing whomever needs to be CCed.
For clarity: assuming
Valentin Villenave wrote Friday, July 22, 2011 7:20 PM
On Fri, Jul 22, 2011 at 10:49 AM, Trevor Daniels
wrote:
I would be in favour of a fixed private mailing list with
publicly
known members to decide a publicly known list of issues,
including the obvious granting/withdrawing git push ac
o *five* people, I do question the need for a mailing list
at all, rather than merely CCing whomever needs to be CCed.
The whole point of mailing lists, in my opinion, is archives: if this
list's archives are not meant to be made public, ever, then I'm
certainly missing the point (assuming there&
>> If we want to pursue a private mailing list, rather than “whoever
>> Graham thinks/remembers to cc”, then the obvious question is “who
>> should be on it?”.
>
> I actually like the solution "whoever Graham thinks/remembers to
> cc."
Me too. I'v
Graham Percival wrote Friday, July 22, 2011 12:59 AM
What should we do with potentially sensitive or private matters in
lilypond? I see two possible solutions:
1. Pick one person to manage private discussions. Whenever
there is a potentially sensitive topic, send an email to that
person. He
On Jul 22, 2011, at 10:21 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Jul 22, 2011, at 1:59 AM, Graham Percival wrote:
>>
>>> ** Private list membership?
>>>
>>> If we want to pursue a private mailing list, rather than “whoever
>>> Graham thinks/remembers to cc”, then th
"m...@apollinemike.com" writes:
> On Jul 22, 2011, at 1:59 AM, Graham Percival wrote:
>
>> ** Private list membership?
>>
>> If we want to pursue a private mailing list, rather than “whoever
>> Graham thinks/remembers to cc”, then the obvious question is “who
>> should be on it?”.
>>
>> My init
On Jul 22, 2011, at 1:59 AM, Graham Percival wrote:
> ** Private list membership?
>
> If we want to pursue a private mailing list, rather than “whoever
> Graham thinks/remembers to cc”, then the obvious question is “who
> should be on it?”.
>
> My initial thought is to keep it small – say, 5 peo
http://lists.gnu.org/archive/html/lilypond-devel/2010-09/msg00178.html
http://news.lilynet.net/spip.php?article121
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00076.html
** Other projects
The idea of private mailing lists is hardly uncommon in
open-source software. For example,
http
> Does it really make sense to have a separate bug-lilypond list?
Yes. Bug reports sent to this address eventually get collected into
the lily-bugs CVS repository after confirmation.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Does it really make sense to have a separate bug-lilypond list?
David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
39 matches
Mail list logo
