Difference between revisions of "DeveloperWiki:Developer Checklist"

From ArchWiki
Jump to: navigation, search
(For the new developer)
(use https for links to archlinux.org)
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
[[Category:DeveloperWiki]]
 
= New developer setup and checklist =
 
= New developer setup and checklist =
  
Line 5: Line 6:
  
 
* adduser on gerolde
 
* adduser on gerolde
 +
** Delete the user's password (passwd -d)
 +
** Upload the user's public ssh key
 
* add to svn-extra, ftp-extra (and possibly ftp-arch for core)
 
* add to svn-extra, ftp-extra (and possibly ftp-arch for core)
 
* upgrade to a "developer" on flyspray
 
* upgrade to a "developer" on flyspray
 
* upgrade to a "developer" on the forums
 
* upgrade to a "developer" on the forums
* upgrade to a "developer" on the AUR
+
* upgrade to a "developer" on AUR
 +
* upgrade to a "Administrator" on the wiki: [[Special:Userrights]]
 
* subscribe them to arch-dev and arch-dev-public Mailing lists
 
* subscribe them to arch-dev and arch-dev-public Mailing lists
 
* add to https://dev.archlinux.org/admin users table
 
* add to https://dev.archlinux.org/admin users table
Line 15: Line 19:
  
 
== For the new developer ==
 
== For the new developer ==
* Add your email address to ~/.forward (so exim can forward mail)
+
* Add your email address to ~/.forward- the file should just be one plain line with an email address (so postfix can forward mail)
 
* Make sure to checkout svn over ssh (See [[DeveloperWiki:HOWTO_Be_A_Packager]])
 
* Make sure to checkout svn over ssh (See [[DeveloperWiki:HOWTO_Be_A_Packager]])
 
* Install devtools and namcap. You may also want the base-devel package if you do not have it
 
* Install devtools and namcap. You may also want the base-devel package if you do not have it
* git projects are "fenced in" to prevent people from pushing code willy-nilly. If you think you should have push access to a git repo, talk to the owner of the repo (listed on [http://projects.archlinux.org projects]). If they accept, any admin can add you to the proper group
+
* git projects are "fenced in" to prevent people from pushing code willy-nilly. If you think you should have push access to a git repo, talk to the owner of the repo (listed on [https://projects.archlinux.org projects]). If they accept, any admin can add you to the proper group
 +
* The core repo is typically disabled for newer developers. This is just a safeguard. If you feel, at some point in the future, that you'd make a good maintainer of a given core package, send an email to the arch-dev mailing list requesting access

Revision as of 00:14, 6 December 2012

New developer setup and checklist

For the admin

To add a new user:

  • adduser on gerolde
    • Delete the user's password (passwd -d)
    • Upload the user's public ssh key
  • add to svn-extra, ftp-extra (and possibly ftp-arch for core)
  • upgrade to a "developer" on flyspray
  • upgrade to a "developer" on the forums
  • upgrade to a "developer" on AUR
  • upgrade to a "Administrator" on the wiki: Special:Userrights
  • subscribe them to arch-dev and arch-dev-public Mailing lists
  • add to https://dev.archlinux.org/admin users table
  • give password to #archlinux-dev
  • give password to #archlinux64-dev (for x86_64 developers)

For the new developer

  • Add your email address to ~/.forward- the file should just be one plain line with an email address (so postfix can forward mail)
  • Make sure to checkout svn over ssh (See DeveloperWiki:HOWTO_Be_A_Packager)
  • Install devtools and namcap. You may also want the base-devel package if you do not have it
  • git projects are "fenced in" to prevent people from pushing code willy-nilly. If you think you should have push access to a git repo, talk to the owner of the repo (listed on projects). If they accept, any admin can add you to the proper group
  • The core repo is typically disabled for newer developers. This is just a safeguard. If you feel, at some point in the future, that you'd make a good maintainer of a given core package, send an email to the arch-dev mailing list requesting access