Open wtbarnes opened 7 years ago
Having fiasco be a SunPy affiliated package would be great! Ideally it would be able to be used by both Astropy and SunPy users.
fiasco now uses the SunPy package template. At some point in the future, it makes sense to move the repo out from under my personal account and move it under the SunPy organization umbrella. There have been several legitimate concerns raised about this:
The main reason for moving it out from under my personal account and into the SunPy org. (at some point would be mostly for the purposes of attracting users and more importantly contributors. People are more likely to start contributing to a package if it is managed by an org rather than a user and the SunPy org already has a preexisting pool of contributors to pull from. Additionally, fiasco could be eligible for inclusion in Google Summer of Code or ESA Summer of Code under OpenAstronomy.
Thoughts on this @dpshelio, @cadair, @namurphy
To participate in any of the summer of codes under OpenAstronomy is just enough that you provide us with a set of ideas and mentors. I don't really worry whether it's or not under sunpy. For attracting people, maybe more than having it under sunpy organisation will help to have it advertised in the sunpy webpage as friendly packages - if not as affiliated. In the same way that astropy has "Other astronomy related packages". @Cadair, how do you see that?
Ideally, fiasco should be a SunPy affiliated package. The steps required are detailed in this SEP. As such, fiasco should use one of the relevant package templates:
This would also mean transferring ownership of the repo to the sunpy org.