Differences between revisions 36 and 37
Revision 36 as of 2009-07-30 15:20:12
Size: 3608
Editor: ?GregorHerrmann
Comment: link to minutes 2nd BOF debcamp 2009
Revision 37 as of 2009-07-30 15:27:13
Size: 3191
Editor: ?GregorHerrmann
Comment: remove completed tasks, add some names
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 * 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. → gregoa has done it in the past, should be a periodic rite
 * Review the "Newer upstream available - Work in Progress" section in PET and file ITPs for missing packages etc. → Add a section for packages that are pending and that have not been touched for too long
 * Rename all source packages to lib*-perl. → Check with ftp-masters whether it is as easy as uploading the new packages. Seems basically trivial.
 * Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl)
 * Create the header/identifier for debian/rules that allows mass-updates. (diocles)
 * Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl) (jeremiah)
Line 32: Line 29:
  * maybe we need a tool?   * we need a tool for easy editing of patch headers according to [[http://dep.debian.net/deps/dep3/|DEP3]]
Line 35: Line 32:
 * Unify the various debian/repack.{sh,pl} scripts.  * Change to the unified debian/repack.sh script.

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

Policy/discussion

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

  • Investigate possible migration from Subversion to Git. → Going forward, although nobody here has really worked on a project with thousands of Git submodules
  • (build-)depending on perl or perl-modules → We should drop the >=5.6 version requirement on perl (cf. #525190), and just specify the version where there is a real requirement. The oldest available release (in oldstable) is 5.8.8 or so

  • "Letter to the Perl Community" about Module::Install?

Packages/tools

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

  • Create the header/identifier for debian/rules that allows mass-updates. (diocles)
  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl) (jeremiah)
  • Patches:
    • forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers → This can follow DEP3 once it is accepted
    • we need a tool for easy editing of patch headers according to DEP3

  • Fix common lintian-errors repo-wide (e.g. errors from pod2man, missing patch descriptions, ...)
  • Policy 3.8.2: mass update packages? → Very old standards-versions might warrant (just for QA work) to be updated, as they were built with very old toolchains. We should at least check packages that have not been updated since Sarge release.
  • Change to the unified debian/repack.sh script.
  • After squeeze: remove (?) B-D on "perl-modules (>= 5.10) | libFOO-perl"

  • Upload all half-adopted packages (rationale: old maintainers don't want to get bug reports, we do) → Every adopted package should warrant an immediate upload, as it carries important informations.

dh-make-perl

  • continue breaking it to isolated modules
  • make POD coverage pass (by completing the docs)
  • TODO

  • bugs

→ Damyan is "slowly" (quoting him) but steadily achieving this; he strongly invites us all to participate