Move to fsprojects?

[dsyme]

Hi @stephan-tolksdorf ,

Some people (e.g. @cartermp) have asked if it would be possible to have this in fsprojects to allow ongoing development by a broader community. It's a key piece used by many, and for which many are very grateful.

Please let me know what you think? The fsprojects policies are here. We much prefer if projects are moved in by the creators, though if you like we could fork it in and find people to own/maintain/develop.

Thanks!!!
Don

[stephan-tolksdorf]

Hi Don!

I intend to resume actively maintaining FParsec shortly. I suppose updated project files and NuGet packages are currently the biggest need. Where do you see the biggest opportunities for improvements? (Of course, I continue to welcome external contributions to FParsec.)

You mention people requesting a transfer to fsprojects. Was there a public discussion I could read up on?

[cartermp]

Most discussion was in the FSSF community slack, unsure if a public link is available.

I think there's an outstanding issue about the net45 target (which could just get removed and the next foparsec could just target net standard), and updated packaging

[dsyme]

Cool makes sense!

Possibly also using the new resumable code features for performance and debuggability would make sense. See https://github.com/TheAngryByrd/IcedTasks for related examples.

@stephan-tolksdorf I'd recommend bringing on board a second maintainer if you can. And if you do want to move to fsprojects, you retain project control per the policies - we're really primarily there to help as backup maintainers and help attract new contributors :)

[maciej-izak]

IMO move to fsprojects would be brilliant idea. To be honest fparsec is flagship F# library, @stephan-tolksdorf thanks to your project I am F# programmer...

[jmhimara]

I second this as well @stephan-tolksdorf . This is a very valuable library for the F# ecosystem, and it would be nice to know that it's maintained/updated.

[dsyme]

@stephan-tolksdorf Any thoughts on this? There's some talk of creating a temporary fork, is that something you'd encourage or discourage? Thanks

[stephan-tolksdorf]

I've just updated the project files for .NET 6 and fixed the compiler warnings about inconsistent parameter names. I will publish a new NuGet package without .NET 4.5 support.

I'd prefer Pull Requests to forking the project on fsprojects, and I'd be happy to give contributors maintainer rights.

[dsyme]

Thanks, that's great!

Any volunteers to be co-maintainers with Stephen?

[travis-leith]

a fairly cheap quick win might be applicative syntax support in the CE: #60

[no1melman]

I would be happy to be a co-maintainer, I've been using this for project for several things - I would need some bringing up to speed on the project as whole