Differences between revisions 24 and 25
Revision 24 as of 2009-04-18 21:08:02
Size: 2370
Editor: ?GregorHerrmann
Comment: one item for patches is enough
Revision 25 as of 2009-04-18 21:09:25
Size: 2424
Editor: ?GregorHerrmann
Comment: svn->git copy question from "tasks" to "discussion"
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 * -  * Investigate possible migration from Subversion to Git.
Line 30: Line 30:
 * Investigate possible migration from Subversion to Git  * Investigate possible migration from Subversion to Git.

Debian Perl Group - Open tasks

This page collects ideas for tasks within the Teams/DebianPerlGroup. These tasks can be worked on at DebCamp or might be tackled by volunteers "at home".


  • The previous list of tasks on this page has been discussed during DebCamp in August 2008. The minutes of the meeting are available in the archive of the debian-perl mailing list.


List of issues that affect our work mode and need discussion.

  • Investigate possible migration from Subversion to Git.


List of tasks that need to be performed on all/many of our packages; or maintainance tools ...

  • Work out how the applications "branch"/git repo really works.
  • Finish or just use the "unified" debian/rules (for packages with and without quilt).
  • Create the header/identifier for debian/rules that allows mass-updates.
  • Clean up the "New Packages - Work in Progress" (i.e. never uploaded) list of packages in PET.
  • Review the "Newer upstream available - Work in Progress" section in PET and file ITPs for missing packages etc.
  • Rename all source packages to lib*-perl.
  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl)
  • Forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers. Maybe we need a tool?
  • Fix common lintian-errors repo-wide (e.g. errors from pod2man, missing patch descriptions, ...)
  • Investigate possible migration from Subversion to Git.
  • Policy 3.8.1: mass update packages?
  • Lenny is out!
    • remove transitional dummy packages
    • remove (?) B-D on "perl-modules (>= 5.10) | libFOO-perl"


  • continue breaking it to isolated modules
  • make POD coverage pass (by completing the docs)
  • make --refresh also update (or at least check&warn) dependencies (and their versions)


Topics that don't fit in the above categories.

  • debian/copyright:
    • boilerplate for reference to changelog
    • mechanism for members to accept this procedure