announce.mbox 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176
  1. Date: Tue, 7 Jun 2016 10:43:10 +0200
  2. From: Enrico Zini <enrico@enricozini.org>
  3. To: debian-devel-announce@lists.debian.org
  4. Subject: Changes in the New Member process
  5. Message-ID: <20160607084310.GA23145@enricozini.org>
  6. MIME-Version: 1.0
  7. Content-Type: multipart/signed; micalg=pgp-sha256;
  8. protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V"
  9. Content-Disposition: inline
  10. User-Agent: Mutt/1.6.0 (2016-04-01)
  11. Status: RO
  12. Content-Length: 6329
  13. --xHFwDpU9dbj6ez1V
  14. Content-Type: text/plain; charset=utf-8
  15. Content-Disposition: inline
  16. Content-Transfer-Encoding: quoted-printable
  17. Hello,
  18. Traditionally, the NM process was about having a number of people go
  19. through several steps to collect all the information that we require to
  20. trust people as new Debian members.
  21. I have been reimplementing the New Member Process workflow on
  22. nm.debian.org. The site is now self-service for most of the bureaucratic
  23. steps, allowing applicants, advocates, AMs and any DD to provide input
  24. and review it autonomously.
  25. The NM process is now more of a collaborative work of the Debian
  26. community, with Debian Account Managers (who have responsibility over
  27. membership decisions) and Front Desk members (helpers of DAM) mostly
  28. just taking care of the final review and decision.
  29. =C2=A0* Changes for applicants
  30. To become a Debian Developer (uploading or not), log into the site[1],
  31. find[2] or create[3] your profile, click on the "request new status"
  32. link and then follow the instructions.
  33. [1] https://wiki.debian.org/DebianSingleSignOn
  34. [2] https://nm.debian.org/public/findperson
  35. [3] https://nm.debian.org/public/newnm
  36. You will need to=C2=A0
  37. =C2=A0- provide a gpg-signed statement saying that you really want to become
  38. a Debian Developer. The statement will automatically be posted to
  39. debian-newmaint@lists.debian.org to introduce you as a prospective
  40. new member.
  41. =C2=A0- provide a gpg-signed statement saying that you agree to uphold the
  42. Social Contract, the Debian Free Software Guidelines and the Debian
  43. Machine Usage Policy in your Debian work.
  44. =C2=A0- spend some time talking with an Application Manager who will ask you
  45. a few questions and send you a few pointers to make sure you are on
  46. the same page as the rest of the project.
  47. And that should be it. The site allows you to follow how things are
  48. going, and to make sure that your personal information like your name,
  49. gpg key, and short bio are correct.
  50. You can see the ongoing (new) processes at https://nm.debian.org/process
  51. =C2=A0* Changes for advocates
  52. As an advocate, you have a page where you can upload a gpg-signed
  53. statement of advocacy that will be automatically posted to
  54. debian-newmaint@lists.debian.org.
  55. Here[4] you can find some guidelines for writing good advocacy messages.
  56. If you write a poor advocacy message like "$NAME's a good friend of mine
  57. lol", any DD can use the site or the debian-newmaint list to ask you to
  58. do better than that.
  59. [4] https://lists.debian.org/debian-devel-announce/2010/05/msg00003.html
  60. =C2=A0* Changes for Application Managers
  61. Confirmation of the AM assignment is gone: if you rather not take the
  62. applicant, you can unassign yourself at any moment. You can also
  63. unassign yourself if you run out of time and you'd like another AM to
  64. take over the process from you.
  65. ID check is gone: the site takes care of it automatically, including
  66. running keycheck to check the number of DD signatures and the properties
  67. of the key.
  68. Philosophy & Procedures and Tasks & Skills are just one of the ways in
  69. which you can interact with your applicants. Remember that T&S can be
  70. skipped entirely if there is a decent technical track record of the
  71. applicant in Debian. nm.debian.org provides the minechangelogs tool and
  72. links to portfolio.debian.net, DDPO and contributors.debian.org.
  73. The result of your work is a gpg-signed statement saying whether you
  74. think that the applicant should be a Debian Developer right now, or not.
  75. Many parts of the mail templates=C2=A0 are now obsolete: there has been no
  76. review of them yet in light of these changes. The templates are in
  77. collab-maint, though [5], so both you and your applicants (or anyone
  78. else, really) can help with that.
  79. [5] https://anonscm.debian.org/cgit/collab-maint/nm-templates.git
  80. =C2=A0* Changes for everyone else
  81. Anyone can now add comments in any part of the current processes in the
  82. site, and they will get recorded in the log of the application.
  83. If you are a Debian Developer, you can review the statements that
  84. applicants and advocates have uploaded to the site, and mark the
  85. requirement as not fulfilled if you think that there is something wrong
  86. with it.
  87. Many pages in nm.debian.org now have a "Wiki Help" link at the top,
  88. which points to a wiki.debian.org page where anyone can write help and
  89. tips for other users of the site.
  90. =C2=A0* Migration from the old-style processes
  91. I have now disabled the advocacy links that started processes the old
  92. way; there is no migration procedure, so the existing processes continue
  93. as they are. When all the old-style processes will be done and closed,
  94. I'll refactor[6] the site codebase to only support viewing, so that the
  95. history of all the processes in Debian remains.
  96. [6] http://devopsreactions.tumblr.com/post/143934692418/old-code-refactoring
  97. =C2=A0* Up and coming
  98. This new implementation of the NM process is flexible enough that it can
  99. deal with all sort of other processes: asking for a guest account to
  100. porter machines, becoming Debian Maintainer, getting upload rights, and
  101. returning from emeritus, can now all be managed through the same
  102. interface. These processes will soon become almost fully automated. More
  103. road testing is still needed and will happen in the near future.
  104. For the Debian Account Manager / Front Desk team,
  105. Enrico Zini
  106. --=20
  107. GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.o=
  108. rg>
  109. --xHFwDpU9dbj6ez1V
  110. Content-Type: application/pgp-signature; name="signature.asc"
  111. -----BEGIN PGP SIGNATURE-----
  112. Version: GnuPG v1
  113. iQIcBAEBCAAGBQJXVokbAAoJEAPWVoyDcnWp7t8QAJmCTfrqyQR4X+H7XkpTkvKL
  114. NLXQ1jUY5zSfSZNb3XoabpA1W2UXcTe64xsPRAROGrpnJXeJFwFeeRuaEi0uPkiZ
  115. kkImy7RCDYb5HEKazbtjoX1ocrww+KhIn+/DsrgS0cNTfy3H7WTLyRwcI/NlICZs
  116. +V7r6mMQ9ln+xur/vye1xG76LIxsQ7BTmGTs2T1nEvOQXjegqzJmfpvXGDUoNgrs
  117. 5Qd6St1F/8g/PhCDlVuFg1tcudY9cup7Rx8IArLvCj308dcmhyjg5nymYDWQFM5H
  118. vJKau9yaLbb1Y8K69fdJCi9uxw2DCvRxu3Ng84iqq3xHUq5agnC+QgsPFdCUhTDX
  119. uONLVb5+COiZ7BeqivVysRdjYEVNdUINPf2RAhxibtI+YZf8jw74WETLNodorpTh
  120. 6jKSCIJkHQxWd0iPYDeITNPjeIqi31dLLRbYcOco6x1Q/Kbi3xpqkdL5tSbd76XP
  121. jJhZHSruR0Nef8eMD/TI4iH/eCr8dAM7BgbumwEYxKJR1sE65/SSn07ot7K2FdaI
  122. DY8l6sDm5LtMDH6UgfEsoNY68hHySS/7ztyXuiZTh1T3M3aTp8muKN8yOxoFbGib
  123. k9vbl0O7DPTTwKw4S4kwaM/kp/djre9stexg2K1oe0dj6tA+Dz6O99czU1y6lDdI
  124. yqb9xaeB1AWvGIoOToBi
  125. =ZcPA
  126. -----END PGP SIGNATURE-----
  127. --xHFwDpU9dbj6ez1V--