Debathena uses Trac for bug tracking, the developer wiki, and other project coordination. This Trac instance is also used for several projects related to Debathena, including:
Logging In: In order to edit wiki pages or open bug reports, you need to Log in to Trac using your MIT Certificate. If you already have a certificate in your browser, click the Login link at the top right of the page to log in.
Trac organizes bug reports into Tickets, and we have further grouped them into Milestones. Typically, a Milestone is created for each Ubuntu or Debian release.
- tickets in progress: 2
- open tickets (excluding "upstream" tickets): 411
- tickets closed in the last 60 days: 21
- all open tickets: 451
Opening a New Bug
To open a new bug, log in to Trac, and then click the "New Ticket" link in the top navigation bar. If the "New Ticket" link is not available, it means you're not logged in.
Joining The Project
Any member of the MIT Community is welcome to join the project. We periodically hold "cluedumps" or crash courses in Debathena development throughout the semester. Our next scheduled one is:
- Date: TBD (IAP 2014)
- Location: TBD
- Time: TBD
We also periodically hold "hackathons", where large groups of people get together to work on Debathena. These are ideal events for novice developers to attend, as there will often be a mentor who you can partner with to work on projects.
We have identified some tickets that are ideal for hackathon work.
Athena and Debathena Technical Overview
The Trac Wiki contains lots of technical information about Athena:
- Kerberos (the primary authentication system used)
- AFS (the global distributed file system where most data, including home directories, is stored)
- Hesiod (the name service used for user names, group names, locker names, and more)
- NSS ("Name Service Switch", allowing Linux systems to use multiple sources (e.g. /etc/passwd, Hesiod, LDAP) of information for system "names")
- PAM ("Pluggable Authentication Modules")
Debathena Project Policies
- The CollaborationPolicy outlines collaboration between SIPB and IS&T.
- The MetapackagePolicy provides guidelines concerning the functionality of each metapackage.
- The WorkflowPolicy describes how code is committed, tested, and deployed.
- The ReleaseSupport policy describes the timeline and guidelines for how long Ubuntu and Debian releases are considered "supported" by the Debathena project.
Building official packages
(Most of the things in this section require debathena-root level access)
- Technical Information:
- BootstrappingTheProjectInfrastructure (this article name sucks)
- UpdatingTheAPTRepository (do we even do this)?
- AddingOrRebuildingASuite (i.e. Supporting a new distro)