You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently many repositories for Eclipse-Platform, Equinox, JDT and PDE have have CONTRIBUTING or a CONTRIBUTING.md file or both that most of the time just contains a link to the contribution information maintained in the corresponding organization's .github repository.
With that the content of the CONTRIBUTING seems to be duplicated and actually not necessary.
Therefore I propose to delete the CONTRIBUTING if the scenario is as described above.
If I read the Eclipse Foundation Project Handbook correct, having a CONTRIBUTING is not mandatory per project and contributing information can also be contained in the README:
@waynebeaton is that correct or are we not allowed to perform the proposed task?
The contribution information generated by GitHub for a repository inherits the CONTRIBUTING file/information from the organization if no such file exists in the repository. For the jdt.debug repository this proposal was already applied and it worked as expected there:
I understand suggesting an enhancement doesn't mandate anyone to implement it. Other contributors may consider this suggestion, or not, at their own convenience. The most efficient way to get it fixed is that I implement it myself and contribute it back as a good quality patch to the project.
The text was updated successfully, but these errors were encountered:
Let's make sure issue is not already fixed in latest builds first.
Suggestion
Currently many repositories for Eclipse-Platform, Equinox, JDT and PDE have have
CONTRIBUTING
or aCONTRIBUTING.md
file or both that most of the time just contains a link to the contribution information maintained in the corresponding organization's.github
repository.For example in the eclipse.platform repository
That link is then also often repeated in a Contributing section in the README.md of the repository.
See for example
With that the content of the
CONTRIBUTING
seems to be duplicated and actually not necessary.Therefore I propose to delete the CONTRIBUTING if the scenario is as described above.
If I read the
Eclipse Foundation Project Handbook
correct, having aCONTRIBUTING
is not mandatory per project and contributing information can also be contained in the README:@waynebeaton is that correct or are we not allowed to perform the proposed task?
The contribution information generated by GitHub for a repository inherits the
CONTRIBUTING
file/information from the organization if no such file exists in the repository. For thejdt.debug
repository this proposal was already applied and it worked as expected there:See https://github.com/eclipse-jdt/eclipse.jdt.debug/contribute
On the other hand https://github.com/eclipse-jdt/eclipse.jdt.debug/contribute currently needs one more click to reach the final destination.
Community
The text was updated successfully, but these errors were encountered: