Hello, this is first draft of proposal. I don't include project schedule and my bio yet because i first want to hear response for my vision on task.<br> <br><br>Project: Debian<br>Summary: Collaborative Maintenance System
<br><br>Name: Pavel Vinogradov<br>Email: <a href="mailto:blaze.cs@gmail.com">blaze.cs@gmail.com</a><br>Project Title: Collaborative Maintenance System<br>Synopsis: Create development environment for collaborative maintenance
<br><br>Benefits to the Debian Community<br><br> Created infrastructure make easier for external contributors to help in the maintenance of Debian packages. It automatize applying and testing patches from registered external contributor. And simplify work of Debian QA-group and package mentors of build and review packages. Also it can help in adaptation new packages for inclusion in Official Debian repository and involves more people in Debian development.
<br><br>Deliverables<br> Deliverable 1<br> Analysis of current state of collaborative maintenance in Debian, Ubuntu and other distribution. Define rules for project inclusion in system, external contributor registration and sponsored by DD package uploads in Official repository.
<br> Deliverable 2<br> Implement infrastructure interaction with official source-package repositories. Included fetching latest packages source into VCS, filled project metadata information in DB and synchronization with changes in repositories.
<br> Deliverable 3<br> Implement development environment based on VCS for collaborative maintenance.<br> Included external contributor registration and accepting. Interact between contributor and mentors. Store additional metadata about contributors and their work in DB.
<br> Deliverable 4<br> Implement autobuild for packages maintain in VCS, lintian/linda check, generation aptable repository. Implement interaction with package maintainer/mentor for upload package in official repository.
<br> Deliverable 5<br> Implement web-interface for system. Included interface for registration and accepting external contributor, inclusion new package in VCS, web-frontend for VCS, status information about each package, contribution and people included in it maintenance.
<br> Deliverable 6<br> Implement closely integration infrastructure with Debian PTS, BTS, QA-team and Debian mentors(1).<br> Deliverable 7<br> Final code and report published.<br><br><br>Project Details (2)
<br> This project focused on maintenance packages which includes external contributions from non Debian Developers. It mostly be used for handling the maintenance of orphaned/unmaintained packages (3), but meant to be used in several other cases which have different expectations about such an infrastructure. Namely :
<br> * Usual co-maintenance with Debian developers and external contributors<br> * Co-maintenance of orphaned packages by the Debian QA Group<br> * Packages from future Debian developers who are currently in the NM process
<br> * Packages from future MOTU which are in the MOTU School<br> * Packages created by Ubuntu's MOTUs which must be integrated in Debian (to avoid divergence)<br> Ubuntu seem to be already on their way with Review Tool for MOTU's (4) and MultiDistroTools(5). Created infrastructure provided database with metadata information about maintained packages, its current status and history, involved Debian and external contributors. VCS used to handling package changes and automatic inclusion external contributions and fixes. Packages stores in VCS is automatically builded in aptables repository with all the latest version of the source packages maintained in the infrastructure. Resulted packages passed via lintian/linda check and available for testing and review by people.
<br> Realization of this infrastructure improved handling of orphaned packages and involves in packages co-maintenance more knowledgeable people willing to help but not pass througth NM to become a Debian Maintainer. It also simplify work of Debian QA-group and package mentors of build and review packages.
<br><br>1.-Debian metros site at<br><a href="http://mentors.debian.net/">http://mentors.debian.net/</a><br>2.-Project proposal Raphael Hertzog at <br><a href="http://wiki.debian.org/CollaborativeMaintenance">http://wiki.debian.org/CollaborativeMaintenance
</a><br>3.-Idea for maintaining packages up for adoption at<br><a href="http://lists.debian.org/debian-qa/2005/07/msg00035.html">http://lists.debian.org/debian-qa/2005/07/msg00035.html</a><br>4.-Ubuntu REVU2Spec at <br><a href="https://wiki.ubuntu.com/REVU2Spec">
https://wiki.ubuntu.com/REVU2Spec</a><br>5.-Ubuntu MultiDistroTools at <br><a href="https://wiki.ubuntu.com/MultiDistroTools">https://wiki.ubuntu.com/MultiDistroTools</a><br clear="all"><br>-- <br>Pavel 'Blaze' Vinogradov
<br>Beginner Linux Developer