Am 19.04.2013 13:24, schrieb David Kastrup:
Francisco Vila <paconet....@gmail.com> writes:
2013/4/19 Urs Liska <lilyli...@googlemail.com>:
I presume the reason emails weren't there was because of the extra spam
they could generate.
- Should email addresses be exposed on lilypond.org?
Would somebody please create a tracker about this?
The current behaviour is not acceptable. We can't direct potential
contributors to the Meisters page and leave them there without any contact
information.
Another idea to protect the privacy of the meisters would be to create
'anonymous' email accounts like bug-meis...@lilypond.org that forward to a
personal mailbox.
If I had my email address clearly exposed in the project page, it
would be only tangentially more prone to spam than it currently is. I
do not oppose to show it, possibly with a minimal obfuscation such as
'at' 'dot' and the like, which spambots can already decypher anyway.
I think if we can manage long-running "project aliases" like
bug-meis...@lilypond.org, that would be preferable. We have
responsibilities shifting not infrequently, and people just _love_ to
consult documentation that has been outdated for decades and/or that is
corresponding to the software version they have installed.
Alternatively, point people directly to the mailing lists.
Attached is a patch that adds four alias addresses to the Meisters page.
In order to be applied someone should have created the email addresses
bug-meis...@lilypond.org
doc-meis...@lilypond.org
translation-meis...@lilypond.org
frog-meis...@lilypond.org
and set them up to forward to the real persons.
Urs
>From a96bdf73107494324065058d1b73a310bcc04729 Mon Sep 17 00:00:00 2001
From: Urs Liska <g...@ursliska.de>
Date: Mon, 15 Apr 2013 14:30:18 +0200
Subject: [PATCH] Add contact info on Meisters page
Willing to contribute I was directed to the Meisters page - only to get stuck there without any contact information.
This patch supplies alias email addresses.
Someone with the privileges to do so should set up the mail accounts and corresponding forwards before applying this patch
---
Documentation/contributor/administration.itexi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 8be1d90..8baeb31 100644
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -118,7 +118,7 @@ Bug Meister: trains new Bug Squad volunteers, organizes who works
on which part of their job, checks to make sure that everything is
running smoothly, and has final say on our policy for Issues.
-Currently: Colin H
+Currently: Colin Hall (bug-meister@@lilypond.org)
@item
Doc Meister: trains new doc editors/writers, organizes who works
@@ -126,14 +126,14 @@ on which part of the job, checks to make sure that everything is
running smoothly, and has final say on our policy for
Documentation. Also includes LSR work.
-Currently: Graham
+Currently: Graham Percival (doc-meister@@lilypond.org)
@item
Translation Meister: trains new translators, updates the
translation priority list, and handles merging branches (in both
directions).
-Currently: Francisco
+Currently: Francisco Vila (translation-meister@@lilypond.org)
@item
Frog Meister: is responsible for code patches from (relatively)
@@ -146,7 +146,7 @@ finally pushes the patches once they're accepted. This person is
would be far too much work -- his/her job is @qq{only} to guide
completed patches through our process.
-Currently: Mike Solomon
+Currently: Mike Solomon (frog-meister@@lilypond.org)
@end itemize
--
1.7.9.5
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
