DCT
|
Size: 4229
Comment:
|
← Revision 58 as of 2008-09-21 08:18:02 ⇥
Size: 5938
Comment: added link to relevant information page (and corrected Martin Albisetti's mail address)
|
| 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. |
The DCT team now has a '''mailing list'''. [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-dct|subscribe]] or [[https://lists.ubuntu.com/archives/ubuntu-dct/|read the archives]]. |
| Line 12: | Line 5: |
| [0] https://wiki.ubuntu.com/UbuntuDemystification | '''For the DCT proposal, read [[DCT/Proposal]].''' |
| Line 14: | Line 7: |
| 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. |
== Current Status == |
| Line 17: | Line 9: |
| 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. | Starting to re-draft most of the current documentation on both Ubuntu's and Debian's side. - MartinAlbisetti beuno@ubuntu.com |
| Line 19: | Line 11: |
| 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: it seems the most current documentation on this topic may now be found under [[Debian]] - Yung-Chin Oei |
| Line 21: | Line 13: |
| === 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. |
== 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 24: | Line 16: |
| Ubuntu developers file bugs on the Debian BTS on a volunteer basis (when they have time, and not for every issue). | 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 26: | Line 18: |
| [1] http://people.ubuntu.com/~scott/patches/ | === 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 28: | Line 23: |
| === Mode 2 : Feedback handled by the Debian Collaboration Team (DCT) === | 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 30: | Line 25: |
| 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). |
This will allow for efficient collaboration between Ubuntu and Debian. |
| Line 35: | Line 27: |
| ==== 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. |
=== From the Ubuntu developer point of view === You can help the DCT in two ways: |
| Line 40: | Line 30: |
| 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 ...). |
* [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 44: | Line 33: |
| == 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.) |
=== What about other packages ? === For packages which aren't monitored by the DCT: * Patches are available from http://patches.ubuntu.com/ , 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 || [[https://launchpad.net/people/lucas|lucas]] || Ruby, Instant Messaging (esp. Jabber)|| || Andrea Veri || Bluekuja || [[https://launchpad.net/people/bluekuja|Bluekuja]] || Soon || || Licio Fernando || licio || [[https://launchpad.net/people/licio|licio]] || gnome || || ZakElep || zakame || [[https://launchpad.net/people/zakame|zakame]] || perl || || JeremieCorbier || Toadstool || [[https://launchpad.net/people/jcorbier|jcorbier]] || python, net || || [[Nxvl|Nicolas Valcárcel]] || nxvl || [[https://launchpad.net/~nxvl|nxvl]] || perl, python, net || || LucaFalavigna || Dktrkranz || [[https://launchpad.net/~dktrkranz|dktrkranz]] || git-core || || RichardJohnson || nixternal || [[https://launchpad.net/~nixternal|nixternal]] || kde || || MarcoRodrigues || Kmos || [[https://launchpad.net/~gothicx|gothicx]] || games, python, gnome || || MichaelKoch || man-di || [[https://launchpad.net/~konqueror|konqueror]] || java || || Dario Minnucci || midget || [[https://launchpad.net/~midget|midget]] || perl (maybe others) || || Andrea Colangelo || warp10 || [[https://launchpad.net/~warp10|warp10]] || Science, games || === How do I join ? === * There's no restriction on who can join (you don't need to be a [[MOTU]]), a Debian developer, or even an Ubuntu member). * Just join the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-dctt|Mailing List]] (it's moderated). == Divergence explanation == This section lists common reasons for divergence, allowing the Debian Developers to understand better why such choices were made in Ubuntu. * DCT/DesktopFiles == Links == * DCT/FormLetters : examples of mails * [[https://launchpad.net/~dct|DCT Launchpad Team]] * [[http://people.debian.org/~mpalmer/debian-mentors_FAQ.html|Debian Mentoring FAQ]] to find out how to get your package included in Debian. == TODO List == * Recruit some Ubuntu developers ('''DCT is a nice idea, but we won't do anything without manpower''') * Improve our tools * Actually start working ;) == Current status of all this stuff == * There's currently not much going on. While I (Lucas Nussbaum) still think it's a good idea, I don't have enough time to work on all this alone, obviously. I plan to dedicate some time to work on this very soon now (next weeks/month). * We shouldn't start working on this before we have a clear workflow and the tools that will allow us to work '''efficiently'''. [[madduck]]: Sure, I don't want to pressure you, but generally I have bad experience with holding off work until tools and workflow have been defined; they never will be defined in a way that people want to work, unless they have been modelled based on the work done by people. Also, if you do not have time to work on this, maybe someone else does? Maybe Canonical will feel inclined to dedicate some resources? FWIW: http://blog.madduck.net/debian/2006.05.24-ubuntu-and-debian == Relevant Links == http://keithcu.com/wordpress/?p=27 == "Test" Debian maintainers == * Hamish Moffatt <hamish at debian dot org> * [[madduck|martin f. krafft]] <madduck at debian dot org> * michael ablassmeier <abi at debian dot org> * Thomas Viehmann <tv at beamnet dot org> * Adriaan Peeters <apeeters at lashout dot net> * Max Vozeler <xam at debian dot org> * Franz Pletz <fpletz at franz-pletz dot org> * Stefano Zacchiroli <zack at debian dot org> * Raphael Hertzog <hertzog at debian dot org> * Maxence Dunnewind <maxenced at ubuntu dot com> |
This is the home of the Debian Collaboration Team.
The DCT team now has a mailing list. subscribe or read the archives.
For the DCT proposal, read DCT/Proposal.
Current Status
Starting to re-draft most of the current documentation on both Ubuntu's and Debian's side. - MartinAlbisetti beuno@ubuntu.com
Note: it seems the most current documentation on this topic may now be found under Debian - Yung-Chin Oei
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:
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://patches.ubuntu.com/ , 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) |
|
Andrea Veri |
Bluekuja |
Soon |
|
Licio Fernando |
licio |
gnome |
|
zakame |
perl |
||
Toadstool |
python, net |
||
nxvl |
perl, python, net |
||
Dktrkranz |
git-core |
||
nixternal |
kde |
||
Kmos |
games, python, gnome |
||
man-di |
java |
||
Dario Minnucci |
midget |
perl (maybe others) |
|
Andrea Colangelo |
warp10 |
Science, games |
How do I join ?
There's no restriction on who can join (you don't need to be a MOTU), a Debian developer, or even an Ubuntu member).
Just join the Mailing List (it's moderated).
Divergence explanation
This section lists common reasons for divergence, allowing the Debian Developers to understand better why such choices were made in Ubuntu.
- DCT/DesktopFiles
Links
- DCT/FormLetters : examples of mails
Debian Mentoring FAQ to find out how to get your package included in Debian.
TODO List
Recruit some Ubuntu developers (DCT is a nice idea, but we won't do anything without manpower)
- Improve our tools
Actually start working
Current status of all this stuff
- There's currently not much going on. While I (Lucas Nussbaum) still think it's a good idea, I don't have enough time to work on all this alone, obviously. I plan to dedicate some time to work on this very soon now (next weeks/month).
We shouldn't start working on this before we have a clear workflow and the tools that will allow us to work efficiently.
madduck: Sure, I don't want to pressure you, but generally I have bad experience with holding off work until tools and workflow have been defined; they never will be defined in a way that people want to work, unless they have been modelled based on the work done by people.
Also, if you do not have time to work on this, maybe someone else does? Maybe Canonical will feel inclined to dedicate some resources?
FWIW: http://blog.madduck.net/debian/2006.05.24-ubuntu-and-debian
Relevant Links
http://keithcu.com/wordpress/?p=27
"Test" Debian maintainers
Hamish Moffatt <hamish at debian dot org>
martin f. krafft <madduck at debian dot org>
michael ablassmeier <abi at debian dot org>
Thomas Viehmann <tv at beamnet dot org>
Adriaan Peeters <apeeters at lashout dot net>
Max Vozeler <xam at debian dot org>
Franz Pletz <fpletz at franz-pletz dot org>
Stefano Zacchiroli <zack at debian dot org>
Raphael Hertzog <hertzog at debian dot org>
Maxence Dunnewind <maxenced at ubuntu dot com>
DCT (last edited 2008-09-21 08:18:02 by ip56500cfb)