-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Move Working with the Code from CONTRIBUTING.adoc to the wiki #26332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
If I may add my two cents here: I - as a contributor - always like having the contribution guides and everything that comes along with it inside the actual repository. Having that stuff in the Wiki always feels a bit decoupled and I personally barely look for instructions in the Wiki of a project. That might be wrong, but I wanted to give you the impression of someone that contributes from an outside perspective. Moreover the Wiki has no versioning context by default, if I'm not mistaken. The switch from Maven to Gradle for example in the past was directly reflected in the specific markdown files inside the repo, which I personally see as a big benefit. I don't think we have that case at the moment, but it's something that came to my mind. I might be biased and since I'm no first-time-contributor anymore my view on this might be distorted, but I'd appreciate a link to the new Wiki section in Cheers, |
Thanks for the feedback Christoph. As a frequent contributor this input is definitely valued. We started with a desire to put some of the more specific items like the existing
We discussed the fact that some of this info might vary by release branch, but that seemed manageable in the wiki format since build changes typically apply to a range of release branches. We'll keep an eye on that going forward.
We planned to link in both directions - from |
Thanks for following up on my comments, @scottfrederick |
We'd like to move the
Working with the Code
section fromCONTRIBUTING.adoc
to a new page on the wiki to make it easier to maintain.The text was updated successfully, but these errors were encountered: