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

Package should belong to JuliaIO #62

Closed
o314 opened this issue Jan 8, 2019 · 5 comments
Closed

Package should belong to JuliaIO #62

o314 opened this issue Jan 8, 2019 · 5 comments

Comments

@o314
Copy link

o314 commented Jan 8, 2019

Hello BioJulia,

I'm fighting with entropy in the Julia world those days. It's becoming very,
very hard to know where to grasp a recommended / authoritative package among
Julia ones, even in 2019.

Doesn't this package would be better hosted at
JuliaIO so anyone concerned would
find it easily ?

Thanks

@jgreener64
Copy link

I can't comment on this package individually as I haven't been involved with it, but in my view orgs arise organically around groups of like-minded developers. It kind of makes sense that packages stay close to the orgs involved in writing and maintaining them.

Which org a package is in shouldn't matter provided there are separate systems for searching and recommending packages. I admit that this is lacking at the minute in the general ecosystem though. However a Google search for "YAML julia" or "YAML jl" both return this repository first.

@kescobo
Copy link
Collaborator

kescobo commented Jan 8, 2019

The question is whether we expect people will look directly for a solution to parsing YAML files (so @jgreener64 's google search info is useful), or whether we'd expect people to browse through JuliaIO to see what file types are supported. The former is much closer to the way I'd expect to search, but it's not unreasonable to think there are some in the latter camp.

That said, I also agree that package search is a known and open issue. Until that gets ironed out, it might make sense to move it, but would also require buy-in from JuliaIO, and the willingness of both maintainers and JuliaIO folks to make the move.

@TransGirlCodes
Copy link
Contributor

TransGirlCodes commented Jan 9, 2019

Heya @o314, YAML.jl is in BioJulia I think because the creator was a heavy developer of a lot of BioJulia's early code, and as he scaled down his activity, YAML maintanance, which used to exist on their profile suffered a bit, so I said something to the tune of "Hey as a stopgap, BioJulia can house it until it gets a proper owner". If JuliaIO would be happy to take on YAML.jl then I would be very happy with that.

@TransGirlCodes TransGirlCodes changed the title Package should belongs to JuliaIO Package should belong to JuliaIO Jan 9, 2019
@o314
Copy link
Author

o314 commented Jan 9, 2019

Hello BioJulia people.

Thanks your for constructive replies,
and all the work behind it !

@TransGirlCodes
Copy link
Contributor

I'm going to close this issue unless the topic arises again, by someone raising the possibility of adopting YAML.jl

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