Contributing
dengemann opened this issue · 3 comments
@mwaskom I just discovered this. I was thinking for quite some time about doing something similar to prevent myself from copying my utils manually from project to project...
How would you feel about contributions mostly related to visualization, stats and dealing with reaction time data and a few MEG specific utils.
Oh crap, sorry, I lost track of this over Thanksgiving.
In general I would not be super enthusiastic about dumping a lot of random stuff into moss. That partly reflects the fact that people are using seaborn now (which wasn't actually my original intention, or at least not my expectation), and seaborn depends on moss. That might not have been the case if I thought anyone other than me was going to care about the tools. So, part of me wants to keep moss as lightweight as possible to make installing/using seaborn less of a hassle.
Relatedly, I don't really have the bandwidth to be maintaining a huge bucket of general interest scientific code. Seaborn is already taking up more of my time than it probably should. And I'm too anal to be releasing code that I don't feel like I understand and am on top of the organization of. So I'm currently considering moss to kind of an internal part of seaborn that happens to be in another package. As you have probably noticed, it doesn't even really have documentation! Very troubling. Best to think of it as _moss, really. :)
If I were to accept a lot of new stuff in moss, I'd want to have a pretty clear idea of what the scope of the project should be. At the moment I don't feel like that's the case -- I have a rough idea of where in my set of projects I should write new things, but I think stuff will probably still be moving around somewhat. So, for the time being, I don't think I'm going to accept big contributions to this project (bug fixes of course always appreciated!). But that may change going forward.
Sorry again about the delay in getting back to you.