Difference between revisions of "DeveloperWiki:Internal Projects"

From ArchWiki
Jump to: navigation, search
(Mirror Control)
(Orphan Team)
(45 intermediate revisions by 15 users not shown)
Line 1: Line 1:
 +
[[Category:DeveloperWiki]]
 
= Introduction =  
 
= Introduction =  
 
This article is part of the [[DeveloperWiki]].
 
This article is part of the [[DeveloperWiki]].
Line 13: Line 14:
 
* [[User:Snowman|Eric Bélanger]]
 
* [[User:Snowman|Eric Bélanger]]
 
* [[User:Firmicus|François Charette]]
 
* [[User:Firmicus|François Charette]]
 +
* [[User:Pierre|Pierre Schmitz]]
 +
* [[User:hdoria|Hugo Doria]]
 +
 +
 +
=== TODO Items ===
 +
 +
* dbscripts: Rewrite db-move to allow multiple packages, getting rid of the testing2* convienence scripts
 +
* dbscripts: Add community repo support to db-move to let us move packages from community to core/extra and vice versa.
 +
* dbscripts: Add community support to the sourceballs script - needs additional logic to use alternate SVN repos
 +
* dbscripts: When a package is completely removed from repo, e.g. amarok-base, its sourceball remains on the server. '''I have a script for that. Will send it soon. [[User:Snowman|Snowman]] 04:32, 6 October 2009 (EDT) '''
 +
* dbscripts/devtools: Add support for using different compression types for packages. This way we could migrate to xz compression while keeping the old gz compressed packages.
 +
* dbscripts/devtools: Implement a common storage dir for packages and just link from the repo dirs. This way mirrors wont need to download every package again when it is moved from testing to extra/core.
  
 
== Mirror Control ==
 
== Mirror Control ==
 
Keep track of existing mirrors and ensure they are doing their job as good as possible (e.g. staying current). Ensure we have up to date contact information for as many mirrors as possible. Work on a tiered mirror system to relieve some stress from our primary rsync server.
 
Keep track of existing mirrors and ensure they are doing their job as good as possible (e.g. staying current). Ensure we have up to date contact information for as many mirrors as possible. Work on a tiered mirror system to relieve some stress from our primary rsync server.
 
* [[User:Romashka|Roman Kyrylych]]
 
* [[User:Romashka|Roman Kyrylych]]
 +
* [[User:Gerbra|Gerhard Brauer]]
 
=== Automated tests ===
 
=== Automated tests ===
 
* sync state: http://users.archlinux.de/~gerbra/mirrorcheck.html
 
* sync state: http://users.archlinux.de/~gerbra/mirrorcheck.html
Line 26: Line 40:
 
Automatic package generation based on changes in svn trunk. Errors should be reported to some mailing list, successful builds moved to a staging directory. Some guidelines of package moving into [extra]/[testing] should be created, for [core] we can use the current signoff procedure.   
 
Automatic package generation based on changes in svn trunk. Errors should be reported to some mailing list, successful builds moved to a staging directory. Some guidelines of package moving into [extra]/[testing] should be created, for [core] we can use the current signoff procedure.   
 
* [[User:pressh|Ronald van Haren]]
 
* [[User:pressh|Ronald van Haren]]
 +
* [[User:ise|Daniel Isenmann]]
 +
* [[User:hdoria|Hugo Doria]]
  
 
== Server Administration ==
 
== Server Administration ==
 
* [[User:Brain0|Thomas Bächler]]
 
* [[User:Brain0|Thomas Bächler]]
 
* [[User:Phrakture|Aaron Griffin]]
 
* [[User:Phrakture|Aaron Griffin]]
* Jan de Groot
+
* [[User:JGC|Jan de Groot]]
 
* [[User:Toofishes|Dan McGee]]
 
* [[User:Toofishes|Dan McGee]]
 +
* [[User:Pierre|Pierre Schmitz]]
 +
* Loui Chang (sigurd)
  
 
== Developer Communication Team ==
 
== Developer Communication Team ==
 
This isn't quite infrastructure, but it almost belongs here. Responsible for organizing developer meetings and making sure people attempt to be present; you newer guys might have no idea, but we used to actually schedule and have 80% of the developer staff present in IRC for 1-2 hour meetings. Responsible for any other coordination between developers, TUs, and maybe even the front page news.
 
This isn't quite infrastructure, but it almost belongs here. Responsible for organizing developer meetings and making sure people attempt to be present; you newer guys might have no idea, but we used to actually schedule and have 80% of the developer staff present in IRC for 1-2 hour meetings. Responsible for any other coordination between developers, TUs, and maybe even the front page news.
* TBA
+
* [[User:Phrakture|Aaron Griffin]]
 +
* [[User:Iphitus|James Rayner]] -I can work on the Status Reports too if Aaron doesn't have time. I'll do dev meetings if nobody steps up.
  
 
= Packaging Projects =
 
= Packaging Projects =
Line 42: Line 61:
 
Responsible for assigning bugs to package maintainers. If something is trivial and a fix can be easily made, then goes and does it. Organizes bug squashing days.
 
Responsible for assigning bugs to package maintainers. If something is trivial and a fix can be easily made, then goes and does it. Organizes bug squashing days.
 
* Andrea Scarpino
 
* Andrea Scarpino
* ...
+
* [[User:pjmattal|Paul Mattal]]
 +
* [[User:Romashka|Roman Kyrylych]]
 
* ...
 
* ...
 
* (needs several people)
 
* (needs several people)
Line 49: Line 69:
 
Responsible for communicating and determining what rebuilds will cycle through [testing] and in what order. They are probably also the people doing large portions of the rebuilds.
 
Responsible for communicating and determining what rebuilds will cycle through [testing] and in what order. They are probably also the people doing large portions of the rebuilds.
 
* [[User:Allan|Allan McRae]] (because my packages seem to cause big rebuilds...)
 
* [[User:Allan|Allan McRae]] (because my packages seem to cause big rebuilds...)
* (more)
+
* [[User:Snowman|Eric Bélanger]]
 +
* [[User:Iphitus|James Rayner]] - may be able to do some building for rebuilds if it's not near exams/assessment.
 +
* Andreas Radke - when OpenOffice is done all the rest is fun - quad core + tmpfs ftw :)
  
 
== Package Review Team ==
 
== Package Review Team ==
 
Some packages in our repos receive little attention due to not being updated frequently.  These need to be checked for being able to build (especially after major toolchain updates) and compliance with current packaging standards.  It would be good for packages that have not been rebuilt in a long time to be rebuilt to take advantage of new optimisations.
 
Some packages in our repos receive little attention due to not being updated frequently.  These need to be checked for being able to build (especially after major toolchain updates) and compliance with current packaging standards.  It would be good for packages that have not been rebuilt in a long time to be rebuilt to take advantage of new optimisations.
* TODO fill me out please
+
* Andrea Scarpino
  
 
== Orphan Team ==
 
== Orphan Team ==
 
Responsible for caring for those packages that no one seems to want and are being neglected. This may involve adoption by themselves or finding a foster caregiver, moving them to a willing maintainer in [community], or sending them to the AUR (or the trash).
 
Responsible for caring for those packages that no one seems to want and are being neglected. This may involve adoption by themselves or finding a foster caregiver, moving them to a willing maintainer in [community], or sending them to the AUR (or the trash).
* [[User:Snowman|Eric Bélanger]]
+
* [[User:Snowman|Eric Bélanger]] (for trivial upstream update)
 
+
* Andrea Scarpino
== The "I package more than the rest of you combined" Team ==
+
* [[User:Giovanni|Giovanni Scafora]]
Because I felt bad leaving him off any list and he does a hell of a job.
+
* [[User:Ghost1227|Daniel Griffiths]]
* [[User:Snowman|Eric Bélanger]]
+
  
 
= Web Projects =
 
= Web Projects =
  
 
This is meant to be a quick overview of the web projects we have and who works on them. For more technical details, you will want to check out the [[DeveloperWiki:Gudrun (web)]] and [[:Category:DeveloperWiki:Server Configuration]] pages.
 
This is meant to be a quick overview of the web projects we have and who works on them. For more technical details, you will want to check out the [[DeveloperWiki:Gudrun (web)]] and [[:Category:DeveloperWiki:Server Configuration]] pages.
 +
* [[User:Pierre|Pierre Schmitz]]
  
 
== AUR ==
 
== AUR ==
 
Responsible for coding and deploying the AUR.
 
Responsible for coding and deploying the AUR.
 
* [[User:Louipc|Loui Chang]]
 
* [[User:Louipc|Loui Chang]]
 +
* Andrea Scarpino
  
 
== BBS ==
 
== BBS ==
Line 77: Line 100:
 
== Flyspray (bugtracker) ==
 
== Flyspray (bugtracker) ==
 
Responsible for keeping our flyspray install up to date and secure.
 
Responsible for keeping our flyspray install up to date and secure.
* TBA?
+
* [[User:Romashka|Roman Kyrylych]]
  
 
== Main Site ==
 
== Main Site ==
 +
There are a lot of issues, things that need cleaned up, etc. Take a look at the bug tracker [http://bugs.archlinux.org/index.php?project=1&cat%5B%5D=7&status%5B%5D=open&do=index Web Site] category.
 +
 
* [[User:Dusty|Dusty Phillips]]
 
* [[User:Dusty|Dusty Phillips]]
 +
* [[User:Toofishes|Dan McGee]]
 +
* [[User:pjmattal|Paul Mattal]]
  
 
== Planet ==
 
== Planet ==
 
Responsible for keeping the planet scripts updated and running.
 
Responsible for keeping the planet scripts updated and running.
 
* Andrea Scarpino
 
* Andrea Scarpino
 +
* Hugo Doria
  
 
== Wiki ==
 
== Wiki ==
Line 96: Line 124:
 
* [[User:Brain0|Thomas Bächler]]
 
* [[User:Brain0|Thomas Bächler]]
 
* [[User:Phrakture|Aaron Griffin]]
 
* [[User:Phrakture|Aaron Griffin]]
 +
* [[User:Romashka|Roman Kyrylych]]
  
 
== Arch Linux Release Engineering (Installer) ==
 
== Arch Linux Release Engineering (Installer) ==
Line 106: Line 135:
 
* [[User:Brain0|Thomas Bächler]]
 
* [[User:Brain0|Thomas Bächler]]
 
* [[User:Phrakture|Aaron Griffin]]
 
* [[User:Phrakture|Aaron Griffin]]
 +
 +
== namcap ==
 +
Responsible for maintaining and adding features to namcap.
 +
* Hugo Doria
 +
 +
== netcfg ==
 +
Network connection and profiles
 +
* [[User:Iphitus|James Rayner]]
 +
 +
== srcpac ==
 +
* Andrea Scarpino
  
 
== Pacman ==
 
== Pacman ==
Line 119: Line 159:
 
=== Translation Team ===
 
=== Translation Team ===
 
Pacman, as of September 2009, has been translated to 15 languages. The upkeep and maintenance of these translations is pretty much a job in itself, with the times immediately preceding a release being the busiest. Ideally this team is responsible for creating a translations branch when a string freeze is set, and then takes incoming translations, ensures they are valid, and merges them into their branch. When a release is not imminent, their focus may be on improving clarity and usefulness of existing messages.
 
Pacman, as of September 2009, has been translated to 15 languages. The upkeep and maintenance of these translations is pretty much a job in itself, with the times immediately preceding a release being the busiest. Ideally this team is responsible for creating a translations branch when a string freeze is set, and then takes incoming translations, ensures they are valid, and merges them into their branch. When a release is not imminent, their focus may be on improving clarity and usefulness of existing messages.
* Giovanni Scafora ?
+
* [[User:Giovanni|Giovanni Scafora]]

Revision as of 22:34, 26 January 2011

Introduction

This article is part of the DeveloperWiki.

This page is meant to list a lot of the projects Arch developers keep busy with. Yes, there are things to do outside of packaging. If you are interested in anything, this page should help you get in contact with the right people. If you are looking for something to do, this is always a good place to start.

Some of these projects have dedicated discussion areas, such as the release engineering and pacman development mailing lists. Other ones are less formal- some of the communication may just be person to person emails or on the arch-dev lists if it appeals to a larger crowd. Remember that if you are interested in these less-formal projects, you should let the names listed below know so they will include you on any communication regarding the project.

Infrastructure Projects

Developer Tooling

Primarily developer-side tools (devtools, namcap) and server-side (db-scripts) work.


TODO Items

  • dbscripts: Rewrite db-move to allow multiple packages, getting rid of the testing2* convienence scripts
  • dbscripts: Add community repo support to db-move to let us move packages from community to core/extra and vice versa.
  • dbscripts: Add community support to the sourceballs script - needs additional logic to use alternate SVN repos
  • dbscripts: When a package is completely removed from repo, e.g. amarok-base, its sourceball remains on the server. I have a script for that. Will send it soon. Snowman 04:32, 6 October 2009 (EDT)
  • dbscripts/devtools: Add support for using different compression types for packages. This way we could migrate to xz compression while keeping the old gz compressed packages.
  • dbscripts/devtools: Implement a common storage dir for packages and just link from the repo dirs. This way mirrors wont need to download every package again when it is moved from testing to extra/core.

Mirror Control

Keep track of existing mirrors and ensure they are doing their job as good as possible (e.g. staying current). Ensure we have up to date contact information for as many mirrors as possible. Work on a tiered mirror system to relieve some stress from our primary rsync server.

Automated tests

Packaging Automation

Automatic package generation based on changes in svn trunk. Errors should be reported to some mailing list, successful builds moved to a staging directory. Some guidelines of package moving into [extra]/[testing] should be created, for [core] we can use the current signoff procedure.

Server Administration

Developer Communication Team

This isn't quite infrastructure, but it almost belongs here. Responsible for organizing developer meetings and making sure people attempt to be present; you newer guys might have no idea, but we used to actually schedule and have 80% of the developer staff present in IRC for 1-2 hour meetings. Responsible for any other coordination between developers, TUs, and maybe even the front page news.

  • Aaron Griffin
  • James Rayner -I can work on the Status Reports too if Aaron doesn't have time. I'll do dev meetings if nobody steps up.

Packaging Projects

Bug Squashing

Responsible for assigning bugs to package maintainers. If something is trivial and a fix can be easily made, then goes and does it. Organizes bug squashing days.

Rebuild Team

Responsible for communicating and determining what rebuilds will cycle through [testing] and in what order. They are probably also the people doing large portions of the rebuilds.

  • Allan McRae (because my packages seem to cause big rebuilds...)
  • Eric Bélanger
  • James Rayner - may be able to do some building for rebuilds if it's not near exams/assessment.
  • Andreas Radke - when OpenOffice is done all the rest is fun - quad core + tmpfs ftw :)

Package Review Team

Some packages in our repos receive little attention due to not being updated frequently. These need to be checked for being able to build (especially after major toolchain updates) and compliance with current packaging standards. It would be good for packages that have not been rebuilt in a long time to be rebuilt to take advantage of new optimisations.

  • Andrea Scarpino

Orphan Team

Responsible for caring for those packages that no one seems to want and are being neglected. This may involve adoption by themselves or finding a foster caregiver, moving them to a willing maintainer in [community], or sending them to the AUR (or the trash).

Web Projects

This is meant to be a quick overview of the web projects we have and who works on them. For more technical details, you will want to check out the DeveloperWiki:Gudrun (web) and Category:DeveloperWiki:Server Configuration pages.

AUR

Responsible for coding and deploying the AUR.

BBS

Responsible for keeping our BBS install up to date and secure.

  • Andrea Scarpino

Flyspray (bugtracker)

Responsible for keeping our flyspray install up to date and secure.

Main Site

There are a lot of issues, things that need cleaned up, etc. Take a look at the bug tracker Web Site category.

Planet

Responsible for keeping the planet scripts updated and running.

  • Andrea Scarpino
  • Hugo Doria

Wiki

Responsible for keeping our wiki install up to date and secure.

Coding Projects

Arch Linux Init Scripts

The all-important scripts that make your machine go when you turn it on

Arch Linux Release Engineering (Installer)

The Arch Linux Install Framework (AIF) and official installation ISOs

mkinitcpio

We have a program to create initrds for Arch systems.

namcap

Responsible for maintaining and adding features to namcap.

  • Hugo Doria

netcfg

Network connection and profiles

srcpac

  • Andrea Scarpino

Pacman

Development Team

This team is responsible for general development, including new features and bugfixes, for the package manager that is a core part of Arch. Although many people contribute patches and code, the people listed here are generally the people that will be reviewing patches and making the final say as to what gets in the codebase.

Translation Team

Pacman, as of September 2009, has been translated to 15 languages. The upkeep and maintenance of these translations is pretty much a job in itself, with the times immediately preceding a release being the busiest. Ideally this team is responsible for creating a translations branch when a string freeze is set, and then takes incoming translations, ensures they are valid, and merges them into their branch. When a release is not imminent, their focus may be on improving clarity and usefulness of existing messages.