Re: packages for adoption: icu, tiff, xerces-c, psutils

[Richard Winters]

Hello Kamaraju,


Thank you for that information I am checking it out at this time!

Best,



*Richard B. Winters*

On Sat, Feb 14, 2015 at 10:51 AM, kamaraju kusumanchi <
raju.mailingli...@gmail.com> wrote:

> On Wed, Feb 11, 2015 at 12:02 PM, Richard Winters  wrote:
> >
> > 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 maintainersome 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...
> >
>
> Take a look at the how-can-i-help package to identify potential areas
> where you can contribute. For example,
>
> % how-can-i-help --show newcomer,RFH
> % how-can-i-help --old | less
>
> More details can be found in "man how-can-i-help". You can install
> this by "apt-get install how-can-i-help".
>
> raju
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> https://lists.debian.org/CABpbYaeBavGAkiY1HzO_a3majhfZgQU2m3Z=0wbth3w56ya...@mail.gmail.com
>
>

Re: packages for adoption: icu, tiff, xerces-c, psutils

[kamaraju kusumanchi]

On Wed, Feb 11, 2015 at 12:02 PM, Richard Winters  wrote:
>
> 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 maintainersome 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...
>

Take a look at the how-can-i-help package to identify potential areas
where you can contribute. For example,

% how-can-i-help --show newcomer,RFH
% how-can-i-help --old | less

More details can be found in "man how-can-i-help". You can install
this by "apt-get install how-can-i-help".

raju


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CABpbYaeBavGAkiY1HzO_a3majhfZgQU2m3Z=0wbth3w56ya...@mail.gmail.com

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Jay Berkenbilt]

Ian Jackson  wrote:

> Jay Berkenbilt writes ("packages for adoption: icu, tiff, xerces-c, psutils"):
>> 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.
>
> I regularly use psutils and would be happy to take it on.

That's great! Go ahead and retitle the RFA to ITA.

> I guess we should wait until after jessie before formalising this with
> an upload.

Yeah, unlike tiff and icu which have pending rc bugs that can hopefully
be fixed before jessie by my successor, psutils is not likely to have
any issues like that. Feel free to switch RFA to ITA and upload right
after jessie is released. Thanks!

-- 
Jay Berkenbilt 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150212163857.3019399151.qww314...@jberkenbilt-linux.appiancorp.com

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Ian Jackson]

Jay Berkenbilt writes ("packages for adoption: icu, tiff, xerces-c, psutils"):
> 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.

I regularly use psutils and would be happy to take it on.

I guess we should wait until after jessie before formalising this with
an upload.

Ian.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/21724.39472.998719.247...@chiark.greenend.org.uk

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Richard Winters]

Jay,

Thank you for that good sir, I will do just that (I'm sure by the time I
wrap my head around orchestrating a transition of ICU to version 54.1;
someone would have taken over - and perhaps I'd be able to contribute
through them at that time and work my way up to a co/maintainer over time).

Really appreciate your response -> your first paragraph actually motivated
me even more.

Cheers -


*Richard B. Winters*

On Wed, Feb 11, 2015 at 1:26 PM, Jay Berkenbilt  wrote:

>
> My suggestion would be to read through the material at
> https://wiki.debian.org/DebianMaintainer and take it from there. Sounds
> like you're about where I was when I started with Debian in 2003: I was
> experienced Linux/C/C++ developer using tiff, xerces, and icu at work. I
> took over the packages with the help of sponsors and initially as a
> co-maintainer and used my experience there toward becoming a full debian
> developer about 18 months later.
>
> I'm afraid I don't have time or energy to help with the sponsorship, but
> maybe you can find someone who can take over maintaining icu with the
> intention of sponsoring you or who can sponsor you to take over
> maintenance. I got my start with the tiff packages by managing a
> transition that corrected an inadvertent binary compatibility problem
> without an soname bump, and through that, earned enough of a reputation
> to be able to move through the new maintainer process pretty easily. ICU
> presents an opportunity to do something similar. Take a look at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757025. When I created
> that, ICU 53 was out, but I was not able to get the transition done for
> jessie. Now ICU 54 is out, and one of the first jobs of icu's next
> maintainer will be, post jessie, to orchestrate a transition of icu to
> version 54.1 or whatever is current at the time. This would be a good
> way to cut your teeth on slightly more advanced package maintenance
> activities required with library packages.
>
> --
> Jay Berkenbilt 
>

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Jay Berkenbilt]

Richard Winters  wrote:

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

My suggestion would be to read through the material at
https://wiki.debian.org/DebianMaintainer and take it from there. Sounds
like you're about where I was when I started with Debian in 2003: I was
experienced Linux/C/C++ developer using tiff, xerces, and icu at work. I
took over the packages with the help of sponsors and initially as a
co-maintainer and used my experience there toward becoming a full debian
developer about 18 months later.

I'm afraid I don't have time or energy to help with the sponsorship, but
maybe you can find someone who can take over maintaining icu with the
intention of sponsoring you or who can sponsor you to take over
maintenance. I got my start with the tiff packages by managing a
transition that corrected an inadvertent binary compatibility problem
without an soname bump, and through that, earned enough of a reputation
to be able to move through the new maintainer process pretty easily. ICU
presents an opportunity to do something similar. Take a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757025. When I created
that, ICU 53 was out, but I was not able to get the transition done for
jessie. Now ICU 54 is out, and one of the first jobs of icu's next
maintainer will be, post jessie, to orchestrate a transition of icu to
version 54.1 or whatever is current at the time. This would be a good
way to cut your teeth on slightly more advanced package maintenance
activities required with library packages.

-- 
Jay Berkenbilt 


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150211132653.0261594103.qww314...@jberkenbilt-linux.appiancorp.com

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Richard Winters]

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 maintainersome 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 

On Wed, Feb 11, 2015 at 11:01 AM, Jay Berkenbilt  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 
>

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Jay Berkenbilt]

Ondřej Surý  wrote:

> JFTR I sent email to tiff RFA and I am willing to take over it.
>
> Thank you, Jay, for all your hardwork on libtiff4->libtiff5 transition
> (and also for the rest of your packages).
>
> If you don't get any volunteers for the rest, please ping here and me
> again after jessie release (instead of orphaning them).
>
> Cheers,
> Ondrej

This is great. Thanks for the response. Feel free to take over tiff at
any time. There are open security issues that I haven't had time to take
care of yet. If you take care of the security issues, you can grab the
packages at that time. If you use git-buildpackage and want to take over
the repos, you can get https://github.com/jberkenbilt/debian-tiff and
push it to wherever. Obviously don't fork it on github since then I
won't be able to delete my copy.

I could be open to giving up vips and nip2 as well. They are very low
effort, and upstream is super-responsive, so I can probably still handle
them even with almost no time, but if you wanted them, I'd be open to
it.

-- 
Jay Berkenbilt 


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/2015025047.0225557611.qww314...@jberkenbilt-linux.appiancorp.com

Re: packages for adoption: icu, tiff, xerces-c, psutils

[Ondřej Surý]

JFTR I sent email to tiff RFA and I am willing to take over it.

Thank you, Jay, for all your hardwork on libtiff4->libtiff5 transition
(and also for the rest of your packages).

If you don't get any volunteers for the rest, please ping here and me
again after jessie release (instead of orphaning them).

Cheers,
Ondrej

On Wed, Feb 11, 2015, at 17:01, Jay Berkenbilt 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 
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1423672075.1544800.226222857.2c551...@webmail.messagingengine.com

Re: Packages for adoption

[Indra Kusuma]

On Tue, 27 Aug 2002, Chanop Silpa-Anan wrote:

# Hola amigos,
#
#
# Due to my constraints in life, I could not maintain a number of packages
# properly. So here are packages up for adoption :
#
# coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html,
# libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs,
# muttprint, type1inst, freefont, and sharefont.

im interesting on cpuburn pkg

Cheers,

Indra Kusuma
--
 ,''`. Indra{@,.}Kusuma.OR.ID -> [personal - Debian/GNU Linux - IPv6]
: :' : 0x4D829E49 - 187D 8C98 FB76 E1A8 5558 853A 4795 4FC1 4D82 9E49
`. `'
  `-

Re: Packages for adoption

[Aurélien Beaujean]

Le mardi 27 août 2002 à 22:50, Chanop Silpa-Anan écrivait:
> coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html,
> libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs,
> muttprint, type1inst, freefont, and sharefont.

As Rene took muttprint, i took latex2html and i will also upload a new
package soon.

Auré
-- 
BOFH excuse #18: excess surge protection

RE: Packages for adoption

[STOJICEVIC Edi EXPSIA]

> Due to my constraints in life, I could not maintain a number of packages
> properly. So here are packages up for adoption :
> 
> coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html,
> libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs,
> muttprint, type1inst, freefont, and sharefont.

Hi,

Can someone tell me what these packages are about :

coriander, cpuburn, gscanbus, gsumi ? 

Sorry but I don't have internet here :(

Best regards,

-- 
 .''`.  Debian GNU/Linux 3.0 released !
: :'  :   Use it ! ;)
`. `~'  http://www.debianworld.org
  `-

*

Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite. 
Tout message electronique est susceptible d'alteration. 
La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de 
ce message s'il a ete altere, deforme ou falsifie.



This message and any attachments (the "message") are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited. 
E-mails are susceptible to alteration.   
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be 
liable for the message if altered, changed or falsified. 

*

Re: Packages for adoption

[Rene Engelhard]

Hi all,

Chanop Silpa-Anan wrote:
> Due to my constraints in life, I could not maintain a number of packages
> properly. So here are packages up for adoption :
> 
> coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html,
> libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs,
> muttprint, type1inst, freefont, and sharefont.

I took muttprint and will upload a new package soon...

Regards,

Rene

-- 
  .''`.Rene Engelhard  
 : :' :** Debian GNU/Linux Developer ** 
 `. `' http://www.debian.org | http://people.debian.org/~rene/
   `-  [EMAIL PROTECTED]


pgpBLfOHCRuuK.pgp
Description: PGP signature

Re: Packages for adoption

[Federico Di Gregorio]

Il mar, 2002-08-27 alle 14:50, Chanop Silpa-Anan ha scritto:
> Hola amigos,
> 
> 
> Due to my constraints in life, I could not maintain a number of packages
> properly. So here are packages up for adoption :
> 
> coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html,
> libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs,
> muttprint, type1inst, freefont, and sharefont.

i'll take the following one ifno one objects:

hyperlatex
freefont
sharefont

-- 
Federico Di Gregorio
Debian GNU/Linux Developer & Italian Press Contact[EMAIL PROTECTED]
INIT.D Developer   [EMAIL PROTECTED]
  99.% still isn't 100% but sometimes suffice. -- Me


signature.asc
Description: PGP signature

Re: Packages for adoption

[Taketoshi Sano]

Hi.

I am now using and prefer the asclassic, and since knghtbrd (the maintainer)
and joel (he is another applicant for asclassic) agreed to my succession, 
I take it over. Thanks.

In article <[EMAIL PROTECTED]>
 [EMAIL PROTECTED] (Joseph Carter) writes:

> [1  ]
> I have a few packages which are mine that I no longer actually use and it
> would be best to give these to other developers who WOULD use them:
> 
> asclassic  - version 1.1 of AfterStep, up until recently the only wm I
>  could stomach.  The others all sucked, including new versions
>of AS which were painful to configure, poorly documented, and
>too damned slow.  Window Maker has become at least as useful
>to me and in fact I think I have fewer complaints about wmaker
>than asclassic at this point.  

-- 
  Taketoshi Sano: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>