Making mentors.debian.net a .org (was: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On 19.01.2012 05:54, Michael Gilbert wrote:
> On Wed, Jan 18, 2012 at 7:43 AM, Arno Töll wrote:
>> On 18.01.2012 08:40, Raphael Hertzog wrote:
>>> Dear DSA, do you think it's possible to have a CNAME mentors.debian.org
>>> pointing to mentors.debian.net? It's currently not hosted on a .d.o
>>> machine but AIUI the mentors.debian.net admins are interested to move it
>>> to DSA-managed host at some point.
>>
>> as a maintainer of mentors.d.n I can confirm our interest to make
>> mentors an official Debian service at some point. However, we are not in
>> a hurry to do so immediately and I believe that's something which needs
>> consensus among developers before we can seriously consider that.
>
> What consensus (and from whom) is required here? If I interpret
> things correctly, the DSA team [0] is the group that need to make the
> call. So lets start that discussion with them (well its already
> started with the CC's).
DSA is the team which makes a DNS CNAME record, or provides a hosting
facility. In my interpretation they are not making facts by that. Making
mentors.debian.net a .org makes the project official part of Debian,
just like any other core team, e.g. ftp-master, security team, release
team and so on. That's not something which should be decided without
consensus among Debian Developers and, perhaps, a DPL which delegates
some people to a "mentors task".
Thus, I am sending this mail to -devel again. Maybe anyone wants to
raise the voice on that matter.
>> Moreover, we're lacking Debian Developers interested to join our team
>> which is sort of a prerequisite to integrate a team into Debian's
>> organizational structure.
>
> I am not a DD quite yet, but I'm finishing the NM process right now,
> and as soon as I'm done, I will be very happy to join this team. I
> would hope there are quite a few other existing DDs willing to be
> officially part of the team as well. Is there a list of the current
> official members?
mentors.debian.net went through several generations of developers who
coded parts of it. These days only me (in NM too, but no DD yet) and
Asheesh Laroia (paulproteus) made notable code contributions in the
recent past. I provided Paul Wise (pabs) a root shell last week but I
guess his interest in participation is mostly front-desk-like, e.g. he
helps people in #debian-mentors or writing to our support address who
had technical problems.
I'd be more than happy finding _anyone_ interested to work on our
(Python/Pylon/sqlalchemy) code base. We have really long todo list.
> Anyway, I think if we can get people behind this, we would want to
> make it happen quickly, then the mentors.debian.org psuedo-package
> would be available, and we could straightforwardly implement the
> bug-based RFP process.
That's the plan, but again: tracking sponsor requests as bugs, and
integrate mentors.debian.net into Debian are unrelated problems. Any
proposal can be implemented without touching the status-quo of the other.
> The term "contributor" conveys a
> much more welcoming message as it says "this is the place where I can
> go to learn about start making contributions to debian", and "this is
> where we can go to help people become contributors".
That's the problem. A contributor can have many roles in Debian, it is
overbooked just like terms such as "DSA" and "maintainer" (albeit zack
suggested to come over the latter problem). That said, I don't mind any
other, better name than "debian-mentors" or "mentors.debian.tld", but
"contributor" probably isn't. YMMV.
- --
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPGALvAAoJEMcrUe6dgPNt8poQAIN14n/rxWcax7NQsYraW73c
2AILwLMuW3N8YKi4iri7+C+l7hCbWwA81yxQbVIZWx1bnOohN3PSKPAle4hO/L3X
19z4U3/4kq/r8T3YfS3wC39UX6MpI1VkfBhvF8Kr+qULo9t+Lra9l75ZI1L1BkEX
obdrkLGEbv0jVoc6b3lhGiFLpTHusUOp80/huAADI4ZG8c1vPO5+WeCh70CtEG80
W2tlgefHN4HP0c/h8J3QCR/fGdx/KVTWd6Ggh6gySs3unhz4sF8kA+jcBAyYZfvY
vyeZ13rcgL41Q772JnbndtDAghTCRmeuiVdqsYlCvG3+raFt0l3nqWeIGHhK6ySW
b5Gd+LBmsrWQvrBDLid83bF1IhlyOdNFfv5T3jQeaOnAJMcijgWsnWin7UpzGJC/
l+GWfuOjvrTsaxz82bIwsqycTJvwfqPCq/8qEUJjxKpvjxEGZWz4YN2hgkX4qOD9
8osFtkyn7AeWuNlEt2G4AuWkwTcOJte9Et1qvAsm7C2qrFsS7D1NYQr+XhJqJb8T
7zdtg1gdYmPbvt8HE9oWJqJuE2XN7pQo81AshBHoWGtOcFSz3J+NSRnAERSZPlg5
kvMSdEDUfLzu75l5IqVJ4pL4ZfMfDOXjuPk/FaJlJPw4IBSsj/vK/WIYnoBfnhKm
j96Vy09UryEzazWEQ7T9
=dVDg
-----END PGP SIGNATURE-----
Reply to: