Differences between revisions 1 and 24 (spanning 23 versions)
Revision 1 as of 2008-01-25 13:32:36
Size: 1055
Editor: ?GregorHerrmann
Comment: first draft
Revision 24 as of 2009-04-18 21:08:02
Size: 2370
Editor: ?GregorHerrmann
Comment: one item for patches is enough
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

##||<tablestyle="width: 100%;" style="border: 0px hidden">~-[:DebianWiki/EditorGuide#translation:Translation(s)]: none-~||<style="text-align: right;border: 0px hidden"> (!) [:/Discussion:Discussion]||
##||
Line 5: Line 4:

## If your page gets really long, uncomment this Table of Contents 
[[TableOfContents(2)]]
## If your page gets really long, uncomment this Table of Contents
<<TableOfContents(2)>>
Line 10: Line 8:
This page collects ideas for tasks within the [:Teams/DebianPerlGroup:DebianPerlGroup]. These tasks can be worked on at DebCamp or might be tackled by volunteers "at home". 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".
Line 12: Line 10:
== Packages ==
List of tasks that need to be performed on all/many of our packages.
== History ==
 * 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 [[http://lists.debian.org/debian-perl/2008/08/msg00029.html|debian-perl mailing list]].
Line 15: Line 13:
 * dpkg-shlibdeps: warnings about linking to unused libs == Policy/discussion ==
List of issues that affect our work mode and need discussion.
Line 17: Line 16:
== Policy ==
List of issues that affect of work mode and need discussion.
 * -
Line 20: Line 18:
 * build systems ("one debian/rules fits them all"?)
 * patch systems (quilt vs. just using a RCS)
 * RCS (svn vs. git)
== Packages/tools ==
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"

=== dh-make-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)

== Others ==
Topics that don't fit in the above categories.

 * debian/copyright:
  * boilerplate for reference to changelog
  * mechanism for members to accept this procedure
Line 26: Line 51:
##See also:  ##See also:

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".

History

  • 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.

Policy/discussion

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

  • -

Packages/tools

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"

dh-make-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)

Others

Topics that don't fit in the above categories.

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