a quick check of the history of CONTRIBUTING.md and DEVELOPING.md shows that they are not often edited compared to the wiki pages. i attribute this to the amount of time it takes to open up a pull request and go through the review process. it's just more convenient to edit the wiki directly, and that's why most of our dev docs have gone there.

👍

furthermore, development processes are not really specific to the SC version, so keeping them embedded in the git repo history isn't necessary.

👍

migrate all project docs to the wiki

what is included in "all project docs"?

other than that all sounds good to me, thanks!!

what is included in "all project docs"?

DEVELOPING.md, CONTRIBUTING.md, and anything worth salvaging from the "development" section of the supercollider website

awesome, let's do ih

sick

alright check it out, i moved CONTRIBUTING.md to become the "Guide for New Contributors," did some major updates to the out-of-date parts, and broke off the pull requests part to its own page. some further revisions are necessary, but at least they're way more convenient to edit now: https://github.com/supercollider/supercollider/wiki

DEVELOPING.md is now the "Developer Reference". it is way too long and i intend to split it into separate pages.

@brianlheim do the names "Guide for New Contributors" and "Developer Reference" sound good to you? it will be hard to change them afterward because github's wiki creates the URL based on the page title, so i just want to finalize those

thanks @snappizz!

Guide for New Contributors sounds good to me. As we discussed on slack I agree it would be a good idea to break up the developer reference page into a couple subpages and then reference them from the main wiki page, which will then become a kind of overview of guides and references.

let's leave this issue open until contributing.md and developing.md have been updated.

#4503