-=| gregor herrmann, Sat, Sep 06, 2008 at 01:47:22AM +0200 |=-
> On Wed, 06 Aug 2008 18:01:21 -0300, gregor herrmann wrote:
>
> > > When: Wednesday, 2008-08-06, 11:00 (UTC-3)
> > > Where: Salón de Mar ("larger talk room", 7th floor)
> > And the meeting has happened!
https://gallery.debconf.org/v/debconf8/gwolf/080820081028.jpg.html
> A short followup:
Thanks for that, I have only some tiny (or not so tiny) notes to add,
everything else looks OK.
> > Should we package only modules or also applications?
> > ----------------------------------------------------
> > * Some people might be interested in packaging perl applications too.
> > * The consensus was to put applications "somewhere separate".
> > * Someone [tm] needs to start the initiative.
>
> This probably needs a bit more work by interested parties.
> AFAIK there's an "apps" branch in the svn-repo and maybe also an
> empty git repo somewhere on alioth but I think not more.
I guess that's me. I did create the apps area in svn (I wouldn't call
it a branch, as it has trunk/, branches/ and tags/ beneath it), but:
1) I find git superior in general, and particularly for apps, as the
application packages naturally won't be that similar as the module
ones. So my first app-packaging attempts would be with git perhaps.
There is /git/pkg-perl on alioth, ready to serve.
2) I already did some work on Padre (a GUI editor, based on wx,
written in Perl) and should push that to alioth. The barrier for
moving it on right now is the amount of unpackaged modules it uses. I
need to compile a list and send an RFH.
3) I suffer from chronic lack of time/concentratiob lately thus no
much progress. This should change after some, er, 10-6- months,
hopefully.
( 4) yes, my vim paragraph autoformat configuration sucks)
> > debian/rules again
> > ------------------
> > * For mass-updates it would be nice to have the information about
> > which debian/rules-template is used. Ideas:
> > - add a "header" to debian/rules, containing some unique identifier
> > e.g. the version number of dh-make-perl
> > - save the md5sum of the used template somewhere
It seems natural for this place to be debian/rules itself, but I guess
calculating the checksum, including the checksum itself can be tricky
:). How about ignoring the lines before and including the line
containing the checksum? Some sed magic should be able to provide
that. And dh-make-perl should place the checksum in the generated
rules on create/refresh.
> > debian/copyright
> > ----------------
> > * The group is no legal entity and therefore cannot be the copyright
> > holder.
right.
> > * "The superset of the module license and the Perl license" seems
> > like a good default licensing for debian/*.
> > * Create a boilerplate that refers to changelog for the contributors.
>
> That needs to be created. Maybe someone who speaks en_LEGAL can
> propose a nice wording for "Files: debian/*\nCopyright: $foo\n
> License: $bar"?
(without claiming anything about en_LEGAL): "The full list of
contributors can be found in /usr/share/doc/$PKG/changelog.Debian.gz"
This does not say anything about © holders, thugh. We keep them as it
is now? (i.e. 'significant' contributions lead to addition to
copyright holders, 'significant' evaluated by the individual
contributor)
> > * Ask contributors when joining the group to accept the "default
> > mechanism" and keep gpg-signed mails.
>
> AFAIK there was no work on that task yet.
I think this is because the "default mechanism" needs to be sorted out
first :)
> > Adopting packages
> > -----------------
> ..
> > * Todo: Write a "How to adopt a package".
>
> My draft:
> http://pkg-perl.alioth.debian.org/howto/adopt.html
> (in svn/website)
Draft? It looks OK to me :)
Please anyone having suggestions about the text, send them.
Should that page be linked from, say subversion.html or policy.html?
> > Bugs
> > ----
> > * We have many old minor bugs open, we need somebody to triage them.
>
> Yes.
>
> And upgrade 3 dozens of packages ...
ack ack
Ready for upload: 0
Damn, we need more people/time, otherwiise the nice "they cope with
hundrets of packages" propaganda in Sledge's teams survey results
would be false :)
> > debian/watch
> > ------------
> > * qareport could show a warning if debian/watch uses a non-dist URL.
>
> Tincho?
I think such a check belongs to packagecheck, now that PET is not
group-specific. What do we do with the few packages that are not on
CPAN, although they are perl modules?
--
dam JabberID: dam@jabber.minus273.org
Attachment:
signature.asc
Description: Digital signature