Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future of goftp #57

Open
jtwatson opened this issue Jun 16, 2021 · 5 comments
Open

Future of goftp #57

jtwatson opened this issue Jun 16, 2021 · 5 comments

Comments

@jtwatson
Copy link

Hello @muirdm,

I am wondering if I could help with the maintenance of goftp.

I need to add support for the z/OS FTP server for a project of mine. I also see several implementations in the community for Windows FTP Support. Reviewing PR #56 made it clear that my work would conflict.

I also see a few other PRs that I will need to merge into my work. #52 #53

I am sure your life is busy so I am wondering if I can be of help getting through a few PRs?

@jtwatson
Copy link
Author

@muirmanders any thoughts on this?

@fdefilippo
Copy link

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

@richard-rance
Copy link

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
Copy link
Contributor

muirdm commented Nov 14, 2022

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
Copy link

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

Thanks for the quick update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants