On 6/1/07, Bill Eldridge <[email protected]> wrote:
Sounds good, Markus - do you have a list of known bugs that need to be
handled?
Yes, I put together a few things that came into mind:
http://mcentral.de/wiki/index.php/Bugtracker
Is this something that can go up on the Wiki, or are there enough that a
bug tracking
system is required?
Wiki/ML should be fine, people use to avoid the bugzilla on kernel.org
although I'd be fine with it (at least for the em28xx project) but
people prefer to add bugreports to the wiki or send mails.
While timelines won't be enforceable for people doing things in their
spare time, it's
still useful to put up time goals and priority lists on projects, both
new development and
bug fixes, to keep momentum going and gauge progress, including seeing
that something
that should have been fixed isn't getting handled.
Can people accept Markus as a reasonable, informed arbiter of what will
go into the main tree
even if there are disagreements? It also sounds like new programmers
here need more startup
instructions/assistance/advice and ground rules than on many open source
projects.
I would appreciate to get more people involved with that project,
VDR/mythTV/mplayer/ffmpeg etc. projects use the outcoming work.
While the v4l and dvb project is doing really hard at the moment and
improvements are handled in a snail speed (if ever handled) this
should really change.
cheers,
Markus
Regards,
Bill
Markus Rechberger wrote:
>
> Some developers are also sick of contributing since the whole
> community is flawed at the moment. I propose a few ways to go
>
> * stopping that signed off by madness that every driver developer has
> to sign off changes which happened at the core which will definitelly
> never happen because people _do not like each other_.
>
> * change the maintainership and push it over to me, even if it sounds
> selfish at the moment _every_ code which provides additional features
> and where noone expects further improvements within the next few weeks
> (without throwing away alot of work or generating useless extra work
> by telling someone to rewrite the core of his work); everyone still
> can try to write better code - but then he _has to do it completly_
> and get in peace with the projects by supporting them to get further.
>
> The problem I have with this project is that many more things are
> upcoming at the moment (including bug fixing) but there are certain
> developers which first weren't experienced enough, afterwards started
> to think about the issues which were tried to discuss at the beginning
> already and who don't have an overview about the requirements, neither
> do they want to discuss the requirements.
> I can name numerous of bugs of this project which can be solved but
> which just get ignored. Some known bugs dont even get explained to
> people who are interested in fixing them, so this is what I consider
> that it's a major problem.
>
> I'm looking for a serious discussion about it, if anyone wants to know
> about the history I can point out to many logfiles/older emails which
> deeply explain the whole video4linux/dvb issues - the project should
> turn back to a real community.
>
> Markus
>
--
Markus Rechberger
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
