conda-forge.github.io
conda-forge.github.io copied to clipboard
conda-forge
Document where to raise issues
It's not totally obvious that policy issues should be raised on the webpage repo, or that package requests should show up on staged-recipes, or what the feedstocks repo issue tracker is used for. We should document this somehow so new people understand where to get help and feedback on ideas they have.
Also would be good to link external issue trackers that are relevant to. For example, conda and conda-build as well as things like Anaconda Platform's support issue tracker.
Hi @PrernaSingh587 it is still not incorporated, feel free to open a PR if you are interested :smile:, I will not assign this to anyone as it is now, but feel free to link your related PR's with this.
@viniciusdc Sure I will work on it!
btw, have a good look inside the main parts of the docs, because (maybe) some parts of this issue are already done, but scattered inside the docs
@jakirkham policy issues should be raised on the webpage repo,
or that package requests should show up on staged-recipes,
or what the feedstocks repo issue tracker is used for.
In this issue, @viniciusdc mentioned that some part of it is already done. I gather , by digging the docs, I saw that the 2nd ( https://conda-forge.org/docs/maintainer/infrastructure.html#repositories) and 3rd(https://conda-forge.org/docs/orga/getting-in-touch.html?highlight=issue%20tracker) part is already done. I can't seem to find anything related to the first part i.e the policy issues.
Could you give me pointers about this so that I can atleast begin creating a draft for the documentation?
@kathatherine @jakirkham, I am thinking of adding the remaining things (issue tracker for conda, conda-build and Anaconda Platform's support issue tracker in the "Getting in touch" section. Also, I think this could also be a good idea to have a section entirely for this, something like Raise your issues/concerns in "Getting in touch". Please share what do you think about this, if this sounds good, I will open a PR for this.
@ssurbhi560, did you end up reopening this PR anywhere else? This would be good to finish up.
Sorry for the slow reply.
Yeah maybe this is already covered with "Getting in Touch". Though Idk if this should live in "Organisation Documentation" or "User Documentation". Maybe the latter is friendlier for newer contributors? What do you think?
Policy issues probably make sense on the webpage repo. That's where we have had these historically. Though maybe we can spell that out better.
I agree that Getting in Touch would probably work better in the User Documentation. Do y'all do redirects to make sure no outside links are broken when whole sections are moved?
@kathatherine, I haven't reopened it yet. And now that we are planning to move the "Getting in Touch" section to "User documentation" I would need to understand how redirects work. I will look into this and will open a PR soon.
Policy issues probably make sense on the webpage repo. That's where we have had these historically. Though maybe we can spell that out better.
Hi @jakirkham! :) Just to clarify, by webpage repo, do you mean on the website, here?