DCT
Differences between revisions 1 and 13 (spanning 12 versions)
|
Size: 4229
Comment:
|
Size: 2754
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| =Collaboration with Debian : a balanced proposal= == Introduction / Rationale == There is a lot of disagreement between Debian and Ubuntu regarding the way Ubuntu "gives back" to Debian. * Debian developers would like Ubuntu developers to file bug reports on the Debian BTS about issues they fix in Ubuntu. * Ubuntu developers, especially MOTUs, are already very busy and understaffed, and can't really handle additional work. * Debian developers feel that Ubuntu "steals" the Debian packages by taking them and only rarely giving back. * Ubuntu developers feel that the bugs they submitted on the BTS are often left unanswered and ignored, or not dealt with promptly enough. |
This is the home of the '''Debian Collaboration Team'''. |
| Line 9: | Line 3: |
| == Scope of this proposal == This proposal deals with packages which are (or might be in the future) slightly modified in Ubuntu, not those which are closer to a fork in Ubuntu. The packages which are only slightly modified most likely reside in the universe and multiverse components of Ubuntu[0], but some of the packages in main can qualify too. |
'''For the DCT proposal, read ["DCT/Proposal"].''' |
| Line 12: | Line 5: |
| [0] https://wiki.ubuntu.com/UbuntuDemystification | == What is the DCT ? == ||<tablestyle="float:right;" style="padding:0.5em; border: 0px;">[http://tiber.tauware.de/~lucas/dct/logos/dct_logo_big.png]|| |
| Line 14: | Line 8: |
| Some packages are largely modified in Ubuntu (think of GNOME, for example) and can't be easily fed back. The feedback process must then be handled directly by the Ubuntu developer who made the changes. Such changes mostly are in ''main'' packages, and ''main'' Ubuntu developers have been quite good at feeding patches back to Debian. If needed, the Debian maintainer can contact the Ubuntu developer responsible for the changes to find a way to import the changes in the Debian package. |
The Debian Collaboration Team (or DCT) is an Ubuntu team aiming at improving collaboration between Ubuntu and Debian by tracking changes in Ubuntu's packages. |
| Line 17: | Line 10: |
| The goal of this proposal is to make collaboration a win-win process for both Debian and Ubuntu. To achieve this, we ask the Debian maintainers to choose between two ''modes'' for their packages. | === From the Debian maintainer point of view === If you are a Debian maintainer, you can ask the DCT to monitor your packages. The DCT will then file bugs in the Debian BTS about your packages for all relevant issues. On the other hand, you agree to act promptly regarding those bugs : * Reply to them within days (not weeks) * Close them by uploading a new version within weeks (not months), when applicable |
| Line 19: | Line 15: |
| We also introduce a team called DCT (Debian Collaboration Team) here. Members of this team are Ubuntu Developers (or would-be developers) interested in collaborating with Debian. | Note that you don't have to accept all changes proposed by the DCT, but it means that you have to explain in the BTS why you think that a specific change isn't of interest to Debian. |
| Line 21: | Line 17: |
| === Mode 1 : Passive giving back === This is what is currently in place. Debian maintainers have access to patches[1] for their packages as soon as the modified packages get into Ubuntu. |
This will allow for efficient collaboration between Ubuntu and Debian. |
| Line 24: | Line 19: |
| Ubuntu developers file bugs on the Debian BTS on a volunteer basis (when they have time, and not for every issue). | === From the Ubuntu developer point of view === You can help the DCT in two ways : * [https://launchpad.net/people/dct Join it] and help to take care of those packages. * Provide better (more verbose) changelog entries, thus simplifying the work of reviewing the changes you make, and ping a DCT member when you make changes relevant to Debian. |
| Line 26: | Line 24: |
| [1] http://people.ubuntu.com/~scott/patches/ | === What about other packages ? === For packages which aren't monitored by the DCT: * Patches are available from http://people.ubuntu.com/~scott/patches/ , and Ubuntu developers file bugs in the Debian BTS on a volunteer basis. * If the team has spare resources while already keeping up with monitored packages, some members may choose other diverged packages to work on. |
| Line 28: | Line 29: |
| === Mode 2 : Feedback handled by the Debian Collaboration Team (DCT) === | == Members == || '''Name''' || '''IRC nick''' || '''Launchpad ID''' || '''Packages of interest''' || || Lucas Nussbaum || lucas || [https://launchpad.net/people/lucas lucas] || Ruby, Instant Messaging (esp. Jabber) || |
| Line 30: | Line 33: |
| Debian maintainers willing to have a more fruitful collaboration with Ubuntu contact the DCT to switch to this collaboration mode for all or some of their packages. This mode includes duties for both parties. ==== Rights and Duties for the DCT ==== * The DCT reports all valuable changes (for Debian) in the Ubuntu package to the Debian BTS, in a reasonable time (depending on the team workload and manpower). * The DCT has the right to refuse to monitor a package if it considers the package has been ''forked'' in Ubuntu (changes wouldn't be of interest anymore to the Debian maintainer). |
== "Job offers" == If you are an Ubuntu developer, or willing to become an Ubuntu developer (MOTU Hopeful, etc), feel free to join the DCT and help us! |
| Line 35: | Line 36: |
| ==== Rights and Duties for the Debian maintainer ==== * The Debian maintainer reacts promptly to all input by the DCT. This mean acknowledging bug reports and commenting them in days, not weeks. * The Debian maintainer has to upload a new package with the changes as soon as possible to keep the divergence between Debian and Ubuntu as low as possible. This means weeks, not months. * The Debian maintainer can refuse patches from Ubuntu. However, of course, he must make the reasons clear in the bug log. |
== Links == * [https://launchpad.net/people/dct DCT Launchpad Team] * [http://utnubu.alioth.debian.org Utnubu]: a Debian team aiming at improving collaboration between Ubuntu and Debian. |
| Line 40: | Line 40: |
| Rights and Duties for the DCT and for Debian maintainers are of course subject to the usual rules: * We all are volunteers, and have lives. This sometimes creates additional delays. * Delays indicated above are subject to conditions (waiting for a testing transition or freeze in Debian, holidays, UpstreamVersionFreeze or FeaturesFreeze in Ubuntu ...). |
== TODO List == * Recruit some Ubuntu developers ('''DCT is a nice idea, but we won't do anything without manpower''') * Improve wiki page * Write the needed tools (spec needed) * Find a few "test" Debian maintainers willing to debug the process ;) |
| Line 44: | Line 46: |
| == How would the DCT work ? == * By monitoring new versions of the Ubuntu packages being uploaded to Ubuntu and reviewing the changes in them. * By being pinged by other Ubuntu developers about specific issues. (by IRC or mail, making it as easy as possible for the Ubuntu developer. Note that pinging DCT is not mandatory for Ubuntu developers.) |
== "Test" Debian maintainers == * Hamish Moffatt <hamish at debian dot org> |
This is the home of the Debian Collaboration Team.
For the DCT proposal, read ["DCT/Proposal"].
What is the DCT ?
The Debian Collaboration Team (or DCT) is an Ubuntu team aiming at improving collaboration between Ubuntu and Debian by tracking changes in Ubuntu's packages.
From the Debian maintainer point of view
If you are a Debian maintainer, you can ask the DCT to monitor your packages. The DCT will then file bugs in the Debian BTS about your packages for all relevant issues. On the other hand, you agree to act promptly regarding those bugs :
- Reply to them within days (not weeks)
- Close them by uploading a new version within weeks (not months), when applicable
Note that you don't have to accept all changes proposed by the DCT, but it means that you have to explain in the BTS why you think that a specific change isn't of interest to Debian.
This will allow for efficient collaboration between Ubuntu and Debian.
From the Ubuntu developer point of view
You can help the DCT in two ways :
[https://launchpad.net/people/dct Join it] and help to take care of those packages.
- Provide better (more verbose) changelog entries, thus simplifying the work of reviewing the changes you make, and ping a DCT member when you make changes relevant to Debian.
What about other packages ?
For packages which aren't monitored by the DCT:
Patches are available from http://people.ubuntu.com/~scott/patches/ , and Ubuntu developers file bugs in the Debian BTS on a volunteer basis.
- If the team has spare resources while already keeping up with monitored packages, some members may choose other diverged packages to work on.
Members
Name |
IRC nick |
Launchpad ID |
Packages of interest |
Lucas Nussbaum |
lucas |
Ruby, Instant Messaging (esp. Jabber) |
"Job offers"
If you are an Ubuntu developer, or willing to become an Ubuntu developer (MOTU Hopeful, etc), feel free to join the DCT and help us!
Links
[https://launchpad.net/people/dct DCT Launchpad Team]
[http://utnubu.alioth.debian.org Utnubu]: a Debian team aiming at improving collaboration between Ubuntu and Debian.
TODO List
Recruit some Ubuntu developers (DCT is a nice idea, but we won't do anything without manpower)
- Improve wiki page
- Write the needed tools (spec needed)
Find a few "test" Debian maintainers willing to debug the process
"Test" Debian maintainers
Hamish Moffatt <hamish at debian dot org>
DCT (last edited 2008-09-21 08:18:02 by ip56500cfb)