As Chris Pavlina wrote: > The bug tracker is a way for developers to communicate with users. It's > generally considered rude to give the silent treatment to people who > communicate with you.
Well, the problem of this project (as well as AVRDUDE) is that I'm almost alone as active developer. In avr-libc, there's still Pitchumani (of Atmel India), but most others here can be considered casual contributors at best. Given that, and that I've got a day job, a family, as well as other hobbies (I'm not only a developer, but would also like to use that stuff for my own hobby work), I have a tendency to dedicate some of my sparetime to these projects rather in larger "chunks", often eventually then be followed up by a new release. That's also where I do most of the work on bug and patch trackers. Of course, I absolutely wouldn't mind having more developers being active here, but as long as it's a one-man show (or two-man, in caes of Pitchumani), I somehow have to slice up the time I can spend in these projects. Otherwise, I'd quickly be burned out completely. Thus, on simple (and obvious) bugs, I'm just about to fix them in one of those time slots. I'm trying to be more responsive for things that really need to be discussed though, or if questions arise. Sorry for this, but it's the current state. This is not Linux, it's not FreeBSD (all with a large number of active developers), it's not KiCAD (which I appreciate very much myself, btw.). -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
