On 2008.03.18. 15:39:15 Robert P. J. Day <[EMAIL PROTECTED]> wrote: >> > so why hasn't that fix been added to the git repo? >> > >> >> First, the git-repo isn't the official source (just to make sure we >> don't confuse people here). > > (just to be clear, when i refer to the "git repo," i'm assuming i > could just as easily be talking about the "svn repo" since i imagine > they're kept in sync, yes?) > > i understand that the version control repos aren't the "official" > source for openwrt. but, from a quality assurance and stress testing > point of view, if you make them open to the public, you should *hope* > that there are people (like me) who are willing to work with them, and > hammer on them, and point out where they fail, and even submit patches > that fix some of those failures.
You've missunderstood that part, I've hilighted that the git repo isn't the official repository, _just to make it clear_ for people who would find your post via google (for example). Currently the official repository is the subversion one, and I have no idea how periodically is the git one synced. My comment wasn't about release/development versions. > to be honest, i'm baffled that the developers *don't* seem all that > enthusiastic about responding to bug reports and patches all that > much, and that there are bug reports that are now months old in the > trac database. to be blunt, that's just plain weird. Not weird, just as I've wrote, we have other things to do. Some of the developers are still in the university, the others are working. Either way they have something "more important" to do - life isn't just candy and joy. We would all be happy and spend 12+ hours a day on OpenWrt, but one can hardly pay with OpenWrt changesets for food and housing. No idea how it works for you, but at most places you have to get up, go to work/school, spend 8 hours (or more) there, go home. Any time you can spend after that is your free time, so this limits the available resources one cna put into a project like OpenWrt.. Oh, and mankind dies after 7 days without sleep, so maybe we should think about that one as well, and we still ignored social life and family duties. >> Second, probably none of the developers use these packages, and >> noone had free time to tst and merge the patches yet. > > no one is *asking* the developers to use those packages. that's what > the *users* are for -- to forge ahead, and live dangerously, and > boldly compile packages that haven't been compiled before, and point > out when things explode. but if the users take the time to do that, > and their reports and/or patches aren't even acted on, they're going > to really start losing interest in helping out. > >> OpenWrt is still a non-commercial project, not a company, so don't >> expect that kind of support.. Real work and life gets priority. > > if that's the attitude of the majority of the developers of openwrt, > then i suggest you folks find a different hobby. because that shows > an astonishing contempt for the users who are willing to invest the > time in using and testing openwrt and trying to make it a better > product. > > if the developers can't even be bothered to look at and apply patches > that are handed to them, they shouldn't be doing this. This is all nice, but please mind again time. Look at the number of developers, and check what they are doing. Some of us are only working on specific ports, and never ever touch "package foo" for example, nor any users on those platforms. Add the "real life factor", and you can admit that it's unrealistic to want us test/review/merge changes freqently. This of course doesn't mean that we do or should ignore patches or bugs - we are simply humans with limited free time. By the way, you didn't quote/reply to the only merit part of my mail, when I've wrote about package maintainers. What do you think about that? Would you volunteer to support/update/fix packages yourself? Imre _______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
