Current Status of OSLib

[Steve Fryatt]

On 16 Jan, Tony van der Hoff via oslib-user wrote in message
    <b7b5846c-899c-1347-ffbd-ea0b3d8837e0 at vanderhoff.org>:

Hi Tony,

Thanks for the update on the current status!

> Well, I haven't seen any patches here for a very long time.
> 
> Justin F. has contributed one bug report in Decmber 2020, which is still
> outstanding, and 3 bug reports in 2019, which I'm certain have been fixed
> by John Tytgat.

I didn't think Justin's last couple of reports from late 2019 had made it
into fixes, but I could easily be wrong. Checking back, the word "patch" was
incorrect -- I thought they were, but it seems my memory was playing tricks.

> Risc OS itself is not being actively developed, so OSLib is hardly an
> active project; in fact I'd call it dormant.

There's still work being done to RISC OS 5, which could result in additions
to the APIs. I agree progress is relatively glacial in the grand scheme of
things, though. :-)

> Me, I'm still around, and am nominally still lead maintainer, but have
> reached an age where I must admit to a certain lack of enthusiasm to fix
> OSLib bugs. I don't know who else is still around, nor do I know who is
> still using OSLib. Anyone reading this is welcome to announce themselves.

For what it's worth, I still actively use OSLib in all of my C-based
projects, and I also used it when writing a tutorial on coding for the Wimp
in C because it is clearer to work with in examples than the alternatives.

I'm certainly aware of other active projects which depend on it, too.

> Certainly an influx of volunteers to continue the maintenance would be
> welcome, and if you're stepping forwars, I'd be pleased to give you
> SourseForge commit rights.

I would be happy to step forward, if it would be of any help -- I'll drop
you an email off-list with my SourceForge details.

-- 
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/