Re: [avr-libc-dev] [bug #48480] missing definitions in iox128a1u.h, iox64a1u.h

[Chris Pavlina]

Understood. I can't exactly criticize you for not having time when I
have little of my own to offer. Still, I would suggest if you have even
a bit extra, trying to prioritize such that a bit is afforded to the bug
tracker. The avr-libc tracker gets very few bugs, there were only two
for the entire month of July, it doesn't take very long to just assign a
priority and show that the bug has been seen.

I wonder if you'd be willing to accept a bit of help with the bug
tracker. I know we don't know each other and you have no reason to trust
me, but responding to and triaging new bugs on the avr-libc tracker,
especially given the infrequency, is definitely something I could find
time for.

On Thu, Aug 11, 2016 at 07:47:18PM +0200, Joerg Wunsch wrote:
> 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. ;-)