Maintainer preferences about staged-recipes HOT 21 OPEN

If you see it on http://www.coglib.com/~icordasc/projects.html you can add me to it.

from staged-recipes.

@ericdill can add me as maintainer to packages at his discretion. Anyone from the jupyter team can add me as maintainer of jupyter packages at their discretion.

from staged-recipes.

I care about skll, gridmap, drmaa-python, chardet, streamparse, pystorm, IO::Storm and any dependencies they have that nothing else has.

from staged-recipes.

@ericdill can add me as a maintainer for anything at his discretion.

For other things, mpl + mpl deps and anything i use in my day job at bnl.

from staged-recipes.

I am OK with being listed as a maintainer on any recipes @ericdill add to conda forge.

from staged-recipes.

@wyseguy7 can add me as a maintainer for any packages at his discretion

from staged-recipes.

@jarifibrahim can add me as a maintainer for any packages at his discretion

from staged-recipes.

@ericdill can add me as a maintainer for any package at his discretion.

from staged-recipes.

@pelson and @ocefpaf after doing a few of these, I thought we should have some concrete guidelines to make it clear what should be done in the migration. Above I have written some of my thoughts. I am totally happy to amend based on suggestions you or others have. My hope is to reduce the workload in the transfer process in terms of review time and implementation time. Maybe adding a contributing.md to the repo would help in this effort. Any feedback anyone has would be appreciated.

from staged-recipes.

Awesome stuff @jakirkham! I guess we should start writing that down in the webpage.

from staged-recipes.

Very nicely put. I've been meaning to put together a place for these kinds of guidelines, but this issue serves us well for the time being. 👍

from staged-recipes.

Thanks guys. Glad to know I am not totally off base.

Yeah, I can see this information being incorporated in various ways. The webpage, the wiki, a CONTRIBUTING.md document here and/or one in each feedstock, linter improvements to smoke out more mistakes via warnings or errors, etc. Welcome any feedback on these and other possible ways of incorporating this information.

from staged-recipes.

I really like linters + git pre-push hooks. I think many people can't be bothered to read things, and we also shouldn't depend on linting being done on only the CI side (because that encourages the bad behavior of "I'll just push and see what the CI does").

from staged-recipes.

This is getting add to the docs ( conda-forge/conda-forge.github.io#95 ) so that we can get it somewhere with more visibility. Suggestions, edits, tweaks, and even PRs against that PR are welcome.

from staged-recipes.

Some contributors to these repos were quite prolific, but may not be as actively engaged. If they specify they only want to be contacted for certain recipes or none at all, please respect their wishes also add here what recipes (if any) they would like to be notified for. If they are no longer interested in any conda recipes, make that note here as well. Before contacting anyone please consult the list below to see if that contributor has restrictions.

@asmeurer only cares about sympy or sympy dependencies.

from staged-recipes.

Thanks @dan-blanchard.

from staged-recipes.

As part of the transfer process, we keep track of people's recipe interests here. So, am adding this below so we can track it and hopefully avoid making more noise than strictly necessary.

Yes. In general I am fine being listed as a maintainer under any project that Kris Overholt lists me as such or for any project listed as being under the dask github organization.

-- comment by @mrocklin.

from staged-recipes.

As the bulk of this content was moved in this PR ( conda-forge/conda-forge.github.io#95 ) and now lives in this doc. I have restructured the message in the comment above and the title accordingly. As we still find ourselves needing to list general maintainer preferences, I have kept this open and restructured it for that purpose alone.

I hope this change is not disruptive and would appreciate feedback and thoughts on it.

from staged-recipes.

How do you feel about legacy packages (e.g. pep8 or pep257), @sigmavirus24? Mainly we keep these around for packages that have not updated to the new name.

from staged-recipes.

@ericdill can add me as a maintainer for any packages at his discretion.

from staged-recipes.

@sannykr can add me as a maintainer to packages at his discretion.

from staged-recipes.