Re: Is PulseAudio dead?

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

 



On Mon, 2010-08-02 at 18:50 +0200, Lennart Poettering wrote:
> On Mon, 02.08.10 17:01, Mike Prispan (fr.prop@xxxxxxxxx) wrote:
> 
> > Hi all,
> > 
> > maybe I'm wrong (I guess I am), but is PulseAudio really dead? What lead me
> > to this conclusion? Well look at this:
> > * Fedora has 201 NEW/ASSIGNED bugs right now [1]
> > * there was not fixed a single bug last six months (since 2010-02-23) [2][3]
> > * there are not only "not pulseaudio, but alsa is broken" bugs, for example
> > abrt reported crashes
> > 
> > No development, no bug fixing, hard to say if there are any comments from
> > bug assignee(s) at all. I've checked only a few bug and did not find any,
> > only from bug reporters pinging or asking if more info is required, but I
> > did not check it using bugzilla query (don't know if it's possible at all).
> > 
> > So, again, is PulseAudio dead? Seems to me
> 
> No, it's not. I am just pushing systemd through right now, and did other
> stuff.
> 
> Also, check upstream git to figure out whether a project is dead. The
> last commit there is from 2 weeks ago. Git can tell you something about
> whether development happens. Bugzilla just tells you whether I have
> devoted my life to processing bug reports. And well, I haven't done
> that. Sorry that I don't exclsuively spend my time on making my stats on
> bugzilla look pretty. If I did, then I would not get any real work done
> anymore.
> 
> Most of the abrt stuff can probably be merged as duplicates. I'd welcome
> if somebody wants to go through this and do this.
> 
> BTW, would be cool to direct flamewar-inducing mails like this to me
> directly, first. Unless of course you think flamewars are a good thing,
> not a bad thing.
> 
> Lennart
> 
> -- 
> Lennart Poettering - Red Hat, Inc.

I am a little off this subject personally but would like to express my
thought on that.

Knowing that you won't put the time PA need and that you will focus on
another project for a relatively long period of time, would the ideal
workflow to follow is to try to find someone to replace you or at least
tell the world that you won't put anymore time fixing bugs? That way,
someone could have stepped up and help you. Currently, it took someone
to find out that no bug was fix for a long period of time to know that
you don't check them anymore.

I think that PA is an important part of a default Fedora system and
knowing that nobody currently monitor bugs and fix them seems a little
bit alarming to me.

This is not a criticism, I currently like what you are doing with
systemd. But, I think this should be addressed correctly for the future.


-- 
Jean-Francois Saucier (djf_jeff)
GPG key : 0xA9E6E953

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux