| 43 |
discussions on this topic. |
discussions on this topic. |
| 44 |
|
|
| 45 |
This makes it very painful to change/switch the Maintainer field because |
This makes it very painful to change/switch the Maintainer field because |
| 46 |
people have to update their PTS subscriptions accordingly. |
people have to update their PTS subscriptions accordingly. |
| 47 |
|
|
| 48 |
#### Duplication of work / inconsistency between the DDPO and the PTS |
#### Duplication of work / inconsistency between the DDPO and the PTS |
| 49 |
|
|
| 97 |
that cannot be well maintained because the set of maintainers do not cover |
that cannot be well maintained because the set of maintainers do not cover |
| 98 |
all the tasks that must be assumed to have a properly maintained package. |
all the tasks that must be assumed to have a properly maintained package. |
| 99 |
|
|
| 100 |
#### Replacing maintenance mailing lists |
#### Replace maintenance mailing lists |
| 101 |
|
|
| 102 |
Packaging teams often separate the mailing list that gets the bug traffic and |
Packaging teams often separate the mailing list that gets the bug traffic and |
| 103 |
other notifications from their main discussion mailing list. This new |
other notifications from their main discussion mailing list. This new |
| 111 |
all of them are MIA or marked as not being available for Debian (busy/in |
all of them are MIA or marked as not being available for Debian (busy/in |
| 112 |
vacation). |
vacation). |
| 113 |
|
|
| 114 |
|
#### Provide new services to packaging teams |
| 115 |
|
|
| 116 |
|
Given that this infrastructure would have native support for packaging |
| 117 |
|
teams, it would also be a good place to offer some standardized services |
| 118 |
|
for them. |
| 119 |
|
|
| 120 |
|
For example, one of the central tool for teams are their VCS and it can be |
| 121 |
|
useful for teams to be able to monitor the state of their package in the |
| 122 |
|
VCS. The [PET](http://pet.alioth.debian.org/) tool could be adapted, |
| 123 |
|
integrated and made available to all teams by default. |
| 124 |
|
|
| 125 |
|
#### Replace WNPP's RFH, RFA, O |
| 126 |
|
|
| 127 |
|
Since the infrastructure already stores the information about who is |
| 128 |
|
maintaining what, it only makes sense to extend it to provide the |
| 129 |
|
list of orphaned packages (i.e. packages without maintainers). |
| 130 |
|
|
| 131 |
|
RFH should be replaced by a system where the help request is better |
| 132 |
|
formalized so that we can better direct new contributors in places |
| 133 |
|
where their skills would be well used. Instead of just requesting |
| 134 |
|
help, you could request: |
| 135 |
|
- a new maintainer (to replace you, i.e. RFA) |
| 136 |
|
- a supplementary co-maintainer |
| 137 |
|
- a bug triager |
| 138 |
|
- a C/Python/Perl/… programmer (you should be able to choose the programming |
| 139 |
|
language) |
| 140 |
|
|
| 141 |
|
Each request also documents whether there's an associated offer of |
| 142 |
|
"mentorship" associated to the help request. Of course, there would |
| 143 |
|
also be a free form description to give more details about what's |
| 144 |
|
expected. |
| 145 |
|
|
| 146 |
|
#### Replace the LowThresholdNmu list |
| 147 |
|
|
| 148 |
|
The [LowThresholdNmu](http://wiki.debian.org/LowThresholdNmu) wiki page |
| 149 |
|
is a hack to let people know when NMU are welcome and not frowned |
| 150 |
|
upon. This information should be properly stored in the database |
| 151 |
|
and it should be associated to each package. |
| 152 |
|
|
| 153 |
|
|
| 154 |
High-level design of the new infrastructure |
High-level design of the new infrastructure |
| 155 |
------------------------------------------- |
------------------------------------------- |
| 188 |
### Using a modern framework for web development |
### Using a modern framework for web development |
| 189 |
|
|
| 190 |
DDPO is implemented in PHP. The PTS uses a mix of Perl, Python, XSLT and |
DDPO is implemented in PHP. The PTS uses a mix of Perl, Python, XSLT and |
| 191 |
shell scripts. While both works very well and are reliable, we can do much |
shell scripts. While both works very well and are reliable, the diversity |
| 192 |
better by using a modern framework for web development (starting with |
of the tools and the fact that some are not widely known (e.g. XSLT) |
| 193 |
internationalization of the web interface). |
seriously limit the set of contributors who are able to hack on all the |
| 194 |
|
parts of the infrastructure. |
| 195 |
|
|
| 196 |
|
With a modern framework for web development, we enlarge the set of people |
| 197 |
|
who are able to help us develop and maintain this infrastructure. It also |
| 198 |
|
offers us a proper separation between presentation and code, so that it's |
| 199 |
|
easier to let web designers integrate this service with the general |
| 200 |
|
look&feel of the various Debian websites. On top of this, we get a fully |
| 201 |
|
internationalized website for free. |
| 202 |
|
|
| 203 |
### API for data export |
### API for data export |
| 204 |
|
|
| 244 |
* BTS: [Bug Tracking System](http://bugs.debian.org) |
* BTS: [Bug Tracking System](http://bugs.debian.org) |
| 245 |
* UDD: [Ultimate Debian Database](http://udd.debian.org) |
* UDD: [Ultimate Debian Database](http://udd.debian.org) |
| 246 |
* DD: Debian Developer |
* DD: Debian Developer |
| 247 |
|
* WNPP: [Work Needing and Prospective Packages](http://www.debian.org/devel/wnpp/) |
| 248 |
|
* RFH: Request For Help |
| 249 |
|
* RFA: Request For Adoption |
| 250 |
|
* O: Orphaned |
| 251 |
|
* NMU: Non-Maintainer Upload |
| 252 |
|
|
| 253 |
Changes |
Changes |
| 254 |
------- |
------- |
| 255 |
|
|
| 256 |
* 2011-01-13: Initial draft by Raphaël Hertzog. |
* 2011-01-13: Initial draft by Raphaël Hertzog. |
| 257 |
|
* 2011-01-28: Integrate feedback from debian-qa@lists.debian.org. |