hping2 orphaned? Joining Extras

Pete Toscano pete-fedora-extras at verisignlabs.com
Sun Jun 19 05:40:54 UTC 2005


Michael Schwendt wrote:

> First a bit of background: When initially we filled Fedora Extras CVS with
> packages, we transferred all packages from fedora.us and created bugzilla
> component entries for them, looking up their package owners' bugzilla
> account e-mail addresses. Additionally, with the procedure for getting CVS
> access, the fedora.us packagers needed to sign the Fedora Contributor
> Licence Agreement (CLA) and send it to Red Hat. A few people did not react
> on notifications done via e-mail or bugzilla comments or probably lost
> interest in their packages earlier. Others were so nice to declare their
> packages as unmaintained.
> 
> Now to the details. To take over the package, there are only a few things
> to do:
> 
>  1) sign up at https://admin.fedora.redhat.com/accounts/

Done.  Will sign the CLA on Monday, when I'm in the office.

>  2) query http://bugzilla.redhat.com for possibly open bug reports
>     which call for your attention as package maintainer, and present
>     an updated package if necessary (for urgent fixes, it can be
>     imported and built quickly by an existing contributor before
>     your cvs account would be ready)

Done.  Found one report
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149776).  I
haven't investigated this much yet, so I could be wrong, but it looks to
me that this guy's beef is with Salvatore Sanfilippo, the hping2
maintainer.  He should probably report a problem such as this on the
hping2 development lists, shouldn't he?  That said, it looks like it
wouldn't be that hard of a problem to fix, so I might just submit a
patch to Salvatore.

I want to be sure I understand where our responsibilities lie as package
maintainers.  It's our job to take the releases (and possibly useful
patches too) and bundle them up in RPMs for release in Extras, right?
If a bug report comes in asking for code fixes or extra features
(possibly aside from already-existing patches) that don't involve the
packaging, the it's best to refer the submitter to the program's
development list, right?  We're not expected to actively participate in
the program's development (although that wouldn't hurt).  We should be
monitoring the programs we maintain for new releases and possibly for
some important patches.  Does this about sum it up?

>  3) state your bugzilla account e-mail address here, so the bugzilla
>     component for "hping2" could be transferred to you when your
>     cvs account is ready

My bugzilla account's e-mail address is the same as the one I'm sending
from now:  pete-fedora-extrasATverisignlabsDOTcom

Thanks for helping.

pete




More information about the fedora-extras-list mailing list