On 22 Oct, dsilvers wrote: > > Is there a definition somewhere of what's involved? > > As this is open-source/free-software work there's rarely anything written > down. > > My understanding of a port maintainer (for us at least) would be someone > who can commit to being around on-channel at least a bit; is competent in > the use of, and development of, applications on their target system, can > respond in a timely fashion to tickets, ideally within a few days even if > only to say thanks, I need to think about this; and will jump on front-end > failures evident in the CI system within a day or two at most. > > Ideally they'd also be interested in learning about and assisting with the > core of the NetSurf codebase, and also our libraries; since all ports rely > on those to a greater or lesser extent.
That's a very useful outline, thanks (sorry about the slow reply, I messed up the mail filter and it binned all your replies). > > I went ahead and wrote patches for > > > > http://bugs.netsurf-browser.org/mantis/view.php?id=2266 > > http://bugs.netsurf-browser.org/mantis/view.php?id=2170 > > http://bugs.netsurf-browser.org/mantis/view.php?id=2336 > > http://bugs.netsurf-browser.org/mantis/view.php?id=2289 > > Thank you. Hopefully Dave Higton may get to these, he has been invaluable > recently :-) It sounds like Dave H might be about to put his hand up as a RISC OS maintainer then! I can keep an eye on the tickets too, I've put the build environment on my laptop so along with RPCEmu can pick over things when stuck on a train. However, I'm not sure developing the core code/being on IRC is something I can juggle as well, so some kind of job share might work better, Sprow.
