CONTRIBUTING.md creation request
The project is missing a CONTRIBUTING.md file. The project is also missing any open "good first issue" tickets, which makes it harder for newcomers to contribute.
It might be a good idea to create a "good first issue" issue, with a request to create a CONTRIBUTING.md file. It would be nice to provide a template for this file, based on other projects of OpenShift.
It would be also nice to mention all the different ways people can contribute to the project, in this CONTRIBUTING.md file:
- sharing insights of the project on Twitter
- maintaining project
- fixing tickets of all kinds
- checking existing issues and commenting on them, wherever it's needed
- ...
I agree! I'd like to contribute and was just looking for a Code of Conduct and Contributing file.
I'd like to work on this, if that's ok. Looks like there's similar docs on other projects of OpenShift.
Of course, it's OK. Even if CONTRIBUTING.md is empty, it's still better than nothing :)
Thank you for your contribution.
Well, I'll see if I can do more than that! Now, let me see. I need to find a contribute doc on how to contribute a contribute doc....
can I do this one though I am new to openshift
The project is missing a CONTRIBUTING.md file. The project is also missing any open "good first issue" tickets, which makes it harder for newcomers to contribute.
It might be a good idea to create a "good first issue" issue, with a request to create a CONTRIBUTING.md file. It would be nice to provide a template for this file, based on other projects of OpenShift.
It would be also nice to mention all the different ways people can contribute to the project, in this CONTRIBUTING.md file:
- sharing insights of the project on Twitter
- maintaining project
- fixing tickets of all kinds
- checking existing issues and commenting on them, wherever it's needed
- ...
Is there any way that I can contribute to this open source, as a rookie I have no idea how I can be of any help . being a student and knowing java I really want to learn many things, looking at guys like you out there always encourages me to know more .
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.