Policies

Need some detail on:
- [ ] Package naming policies. Particularly with regards to divergence from anaconda. #18
- [ ] Requesting to become a maintainer.
- [ ] Removal of distributions from the conda-forge channel (perhaps those which are beyond a certain age and have never been downloaded)
- [ ] Where to submit issues
- [ ] How to resolve a package name dispute (to avoid name squatters)
- [ ] Contribution guidelines (including the license of the recipes)
- [ ] Advice on how to write quality recipes
- [ ] Dependencies on system libraries #23
- [x] When to package software which is already in the default conda channel #22 (Answer: we are aiming to make conda-forge the canonical recipe source, so package away!)
- [ ] Notification of originating packaging proposal back to source repository (so that developers are aware, and can contribute to, the packaging effort)
- [ ] Packaged data limits (some packages ship _huge_ datasets with themselves)
- [ ] Dealing with miscreants who compromise the conda-forge channel's integrity (e.g. by echoing the BINSTAR_TOKEN)
- [ ] How far do we go down the packaging rabbit hole (https://github.com/conda-forge/conda-forge.github.io/issues/81)

I don't think it is healthy to discuss these individual topics in this issue, and we should spin off new issues for those discussions (I'll update this issue with the appropriate links).