Future of goftp about goftp

[jtwatson]

@muirmanders any thoughts on this?

[fdefilippo]

@jtwatson hello, have you implemented something? I would need the MVS part too.

[richard-rance]

It looks like @muirmanders only made 2 contributions on github in 2020 and nothing since according to their profile. This library seems pretty well designed and tested so I would hate to see it go abandoned.

Would someone be interested in consolidating all the forks into a new home that is community maintained?

[muirdm]

My vague plan has been to do a proper v2 module release with these changes:

1. Remove implicit connection pooling, possibly leaving it as separate, optional functionality (thoughts?)
2. Merge PRs that I have reasonable confidence in (e.g. have tests), and are in-scope for this project
3. Triage remaining issues and fix stuff as necessary (allowing breaking changes)
4. Implement support for the Go filesystem interface
5. Consider switching "Dial" interface to use func callback config setters rather than a user visible config struct
6. Rework logger to take a *log.Logger, or perhaps better wait for the slog stuff.

[richard-rance]

🤦‍♂️ I should have looked closer. You have a new github username now.

Thanks for the quick update.