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

Should the ecosystem move to an organization? #178

Open
asinghvi17 opened this issue Aug 29, 2024 · 2 comments
Open

Should the ecosystem move to an organization? #178

asinghvi17 opened this issue Aug 29, 2024 · 2 comments

Comments

@asinghvi17
Copy link

Hey, it may make sense to move the FilePaths ecosystem to an org (maybe JuliaIO, or spin up a new JuliaFileAccess org or something) for maintainability and to reduce bus factor.

Just a thought, it's not particularly urgent. Happy to facilitate if needed.

@rofinn
Copy link
Owner

rofinn commented Aug 30, 2024

Possibly. I feel like JuliaIO could make sense, though I don't believe I'm in that org currently. I haven't personally found adding packages to orgs really helps address the maintenance issue, it's still a tragedy of the commons problem. For example, BSON.jl also has a bunch of unaddressed issues and hasn't had an update since Jan. That being said, it can be a convenient way of lowering the bus factor, rather than adding individual folks to specific repos.

@asinghvi17
Copy link
Author

Yeah, it is quite a problem - I guess the downside of having widely used packages is that there are a lot more bugs for comparatively fewer developers per user...

In case you'd like to move the repos to JuliaIO, let me know and I can get the ball rolling over there!

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

2 participants