Hey there:

Posting again because I didn't hit reply-all (sorry, but would rather
advertise I"m available for help to the whole mailing list.)

I'm not a 'debian' maintainer or developer...total newbie to alioth -> but
I'm a c++ developer with over 10 years experience.  I'm experienced with
linux and more specifically debian development (just not officially).

That said I'd love to get involved with Debian development -> I love debian
and live by it. Anyone willing to lemme help out would be great. I check on
alioth often...projects never seem to be posted for help...as a newbie I'm
confused how to get started -> I've read documentation yet most of these
emails looking for helping or specifying a package to be orphaned require a
dev or maintainer....some of the packages I've looked into helping out with
either dont have a buglist or are severely old and have dozens of helpers
already.

I offer my help here because I tend to need the ICU packages for building
various things...if its gonna be orphaned I'd rather help out...


Samples of work can be provided if needed.

*Richard B. Winters*

Chairman & CEO
*Massively Modified, Inc.*
MMod | Kwaeri

*Phone*: (607) 431-8726
*Fax:  *(877) 267-0412

*WebGL Engine (In Progress):*
kwaeri Engine <http://kwaeri.mmogp.com/>

On Wed, Feb 11, 2015 at 11:01 AM, Jay Berkenbilt <q...@debian.org> wrote:

> I have four packages that I'd like to give away. If I don't find a new
> maintainer for them, I may orphan them after jessie is released since I
> no longer have time to maintain them. I have been maintaining these
> packages for a long time (over 10 years in some cases), and all four
> packages are in good shape. I have filed RFA bugs for each package.
>
> Two of the packages, tiff and icu, are important library packages with
> lots of reverse dependencies and frequent security issues. They are
> fairly low effort to maintain but require occasional surges of effort.
> In particular, ICU gets two non-binary-compatible (soname bump) upstream
> releases each year and requires regular coordination with the release
> team and often some of its downstream packages. The tiff packages are
> mostly inactive upstream but do get occasional upstream releases.
>
> The other two packages are relatively low-effort packages to maintain.
> The psutils package is dead upstream though there is someone out there
> who might be interested in taking over upstream. I would introduce him
> to any new maintainer. The xerces-c package is a library package but a
> pretty easy one as they go. It has few downstream packages within debian
> and gets very infrequent upstream releases.
>
> All four packages are maintained with git-buildpackage, but right now
> their repositories are in github because I switched all my packages over
> to git-buildpackage during a time when alioth had extended downtime.
> Pushing the repos over to a better/additional place is trivial, of
> course.
>
> I have provided additional information in the RFA bug reports:
>
> icu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777694
> tiff: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777695
> xerces-c: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777698
> psutils: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777699
>
> --
> Jay Berkenbilt <q...@debian.org>
>

Reply via email to