[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Fwd] Bug#621966: hasciicam: FTBFS: hasciicam.c



dear Mentors,

first and foremost: thanks for your answers!

On Mon, 25 Apr 2011, The Fungi wrote:

> On Tue, Apr 26, 2011 at 02:28:10AM +0900, Charles Plessy wrote:
> > I see that one uploader of hasciicam is Debian Developer. He is
> > the first person to contact for upload or to recommend you as
> > Debian Maintainer--that is, to give you upload privilege.
> 
> Specifically, according to who-uploads, 1.0-1 was uploaded to
> unstable by Giunchedi Filippo <filippo@debian.org>, so he'd be the
> right place to start asking for a new upload.

sure! and so I did, also knowing Filippo personally. In fact, despite
the limited amount of time at his hands, he is doing his best to
review my other upstream software package, which is arguably more
urgent than hasciicam: freej, for which i've also fixed open bugs but
had no way to upload them.

ultimately what is very frustrating is just the fact of not being able
to upload anything and to keep receiving bug notices that i have fixed
in upstream months if not years ago, while volunteering to fix them
and being an upstream developer for the software, willing to become DM
for his packages.

i hope i didn't annoy you too much with my mails and if it was so i
apologize for my Mediterranean temper (but well, as your next
gathering is in Bosnia/Erzegovina then you'd better start get used).
one could call it just a rand, but i'm trying to give a point of view
of an upstream developer willing to enter Debian and some hints why
Debian is "not very popular" among software developers.. acknowledging
such situations is the first step to make things better, no?  in
general i think less beaurocracy and more trust for people and the
code they wrote so far would help Debian to get better.

ciao

-- 
jaromil,  dyne.org developer,  http://jaromil.dyne.org
GPG: B2D9 9376 BFB2 60B7 601F 5B62 F6D3 FBD9 C2B6 8E39
Send bitcoins to:  1EJYtvuq39hoWcventcnnvhPXh6i5QDReM


Attachment: signature.asc
Description: Digital signature


Reply to: