1 To: "__ENCODED_REALNAME__" <__EMAIL__>
4 Content-Type: text/plain; charset="utf-8"
5 Content-Transfer-Encoding: 8bit
6 Subject: New ud-ldap account for __ENCODED_REALNAME__
7 Cc: new-maintainer@debian.org
8 Reply-To: new-maintainer@debian.org
10 User-Agent: nm-create script run by __WHOAMI__
12 Content-Type: text/plain; charset="utf-8"
13 Content-Transfer-Encoding: 8bit
15 [ This is a long (automatically-generated) mail, but it contains
16 important information, please read it all carefully. ]
20 An account has been created for you on master.debian.org and
21 va.debian.org with username '__LOGIN__'. The password for this
22 account can be found encrypted with your PGP key and appended to this
25 You have been subscribed to the debian-private mailing list as
26 <__PRIVATE__> (you should receive seperate confirmation of this from
27 smartlist). Please respect the privacy of that list and don't forward
28 mail from it elsewhere. E-mail to <__LOGIN__@debian.org> will be
29 forwarded to <__EMAIL__>. To change this, edit the file '.qmail' in
30 your home directory on master to point to the new address (don't
31 forget the '&' character at the beginning of the line). Please
32 subscribe to debian-devel-announce, if you haven't done so already.
34 We strongly suggest that you use your __LOGIN__@debian.org address for
35 the maintainer field in your packages, because that one will be valid
36 as long as you are a Debian developer, even if you change jobs, leave
37 university or change Internet Service providers. If you do so, please
38 add that address to your PGP key (using `pgp -ke "YOUR USER ID"'), if
39 you have one, and your GnuPG key (using `gpg --edit-key "YOUR USER ID"')
40 and send it to <keyring-maint@debian.org>.
42 You can find more information useful to developers at
43 <URL:http://www.debian.org/devel/> (in particular, see the subsection
44 titled "Debian Developer's reference").
46 We suggest that you subscribe to debian-mentors@lists.debian.org.
47 This list is for new maintainers who seek help with initial packaging
48 and other developer-related issues. Those who prefer one-on-one help
49 can also post to the list, and an experienced developer may volunteer
50 to help you. You can get online help on IRC, too, if you join the
51 channel #debian-devel on irc.debian.org. Take a look at the support
52 section on www.debian.org in order to find out more information.
54 You should have read these documents before working on your packages.
56 o The Debian Social Contract
57 <URL:http://www.debian.org/social_contract.html>
59 o The Debian Policy Manual
60 <URL:http://www.debian.org/doc/debian-policy/>
62 o The Debian Packaging Manual
63 <URL:http://www.debian.org/doc/packaging-manuals/packaging.html>
65 If you have some spare time and want to contribute it to Debian you
66 may wish to take a look at the "Work-Needing and Prospective Packages
67 for Debian GNU/Linux" also known as WNPP that can be found at
68 <URL:ftp://ftp.debian.org/doc/package-developer/prospective-packages.html>
70 If you plan to make a Debian package from a not yet packaged piece of
71 software you *must* announce your intention on the debian-devel mailing
72 list to make sure nobody else is working on them.
74 The machine master.debian.org is our main archive server. Every
75 uploaded package finds it's way there (except for Packages covered by
76 US crypto laws which go to non-us.debian.org) eventually. That
77 machine is also the home of our web pages and our bug tracking system.
78 The second machine va.debian.org is supposed to take over some of the
81 Both machines were sponsored by companies (Novare Inc. for master and
82 VA Linux Systems for va). Please don't over-stress them and use your
85 You should use ssh to log into the machines instead of regular telnet
86 or rlogin. We have installed ~/.ssh directories and authorized_keys
87 files with appropriate permissions on both machines. If you want to
88 ssh to them without typing the password, run ssh-keygen on your
89 machine and add the contents of ~/.ssh/identity.pub into the
90 authorized_keys files in ~/.ssh on master and va. But please be aware
91 of the security implications of doing this.
93 Welcome to the project!
96 The Debian New Maintainer Team