Sounds good, Markus - do you have a list of known bugs that need to be handled? Is this something that can go up on the Wiki, or are there enough that a bug tracking system is required? 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. 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 > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
