Hi all,

Well despite Rob Kenricks's probably highly accurate description of how 
development for RISC OS is ("hateful"!), I am interested, and have expressed 
that interest on the developers' mailing list. And I'm not the only one.

I've had quick responses to the (so far few) questions I've asked, and I 
believe that the existing NetSurf developers will continue to bend over 
backwards to help anyone with the time and inclination to maintain the RISC OS 
front end. They just haven't got the time or the inclination to do it 
themselves. I'm sure everyone here can understand that.

Right now my time is very limited, just like most other people's. However, I am 
looking over the sources in the little free time I do have, and I'm starting to 
get a feel for things. I fully expect to be able to make a positive 
contribution to the project in time, but I can't just pick up such a large 
software project and start committing code without a pretty serious investment 
of time. So patience is required before I, or anyone else I should think, can 
get up to speed with the project and fill in the gaps. I would therefore 
understand if the core developers wanted to drop RISC OS support and merge 
their improvements for now to prevent this stall in development affecting the 
other platforms for any longer than it has already.

That doesn't mean I or somebody else can't be working on getting the RISC OS 
front end back into shape at a later date, does it? It would just mean RISC OS 
autobuilds had to stop for a period, I think.

Correct me if I'm wrong!

WPB



      

Reply via email to