Create CONTRIBUTING.md #16
Conversation
|
Sorry for the slow response, I recently got back from vacation and I had a pile of stuff to go through. I assume this is something commonly added to ROS-Industrial repos, is that correct? |
|
See my comment in ros-industrial/abb_libegm#13 (comment). |
|
Yes, this is long overdue, I will look at it today. |
There was a problem hiding this comment.
In the first section there is a reference to a figure, and later in the document there are several items mentioned that I assume are part of it. @tfoote or @gavanderhoorn, is this figure available somewhere?
Also, numbers 7. - 9. are not currently applicaple to this repository. Maybe remove them for now? And add a note like "Note: Items 7 to 9, in the figure, are currently not applicaple to this repository." just before the last line?
| @@ -0,0 +1,21 @@ | |||
| ROS-Industrial is a community project. We welcome contributions from any source, from those who are extremely active to casual users. The following sections outline the steps on how to contribute to ROS-Industrial. It assumes there is an existing repository to which one would like to contribute (item 1 in the figure above) and one is familiar with the Git "Fork and Branch" workflow, detailed [here](http://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/). | |||
|
|
|||
| 1. Before any development is undertaken, a contributor would communicate a need and/or issue to the ROS-Industrial community. This can be done by submitting an issue on the appropriate GitHub repo, the [issues repo](https://github.com/ros-industrial/ros_industrial_issues), or by posting a message in the [ROS-Industrial category on ROS Discourse](//swri-ros-pkg-dev@googlegroups.com). . Doing so may save you time if similar development is underway and ensure that whatever approach you take is acceptable to the community of reviewers once it is submitted. | |||
There was a problem hiding this comment.
| 1. Before any development is undertaken, a contributor would communicate a need and/or issue to the ROS-Industrial community. This can be done by submitting an issue on the appropriate GitHub repo, the [issues repo](https://github.com/ros-industrial/ros_industrial_issues), or by posting a message in the [ROS-Industrial category on ROS Discourse](//swri-ros-pkg-dev@googlegroups.com). . Doing so may save you time if similar development is underway and ensure that whatever approach you take is acceptable to the community of reviewers once it is submitted. | |
| 1. Before any development is undertaken, a contributor would communicate a need and/or issue to the ROS-Industrial community. This can be done by submitting an issue on the appropriate GitHub repo, the [issues repo](https://github.com/ros-industrial/ros_industrial_issues), or by posting a message in the [ROS-Industrial category on ROS Discourse](https://discourse.ros.org/c/ros-industrial). Doing so may save you time if similar development is underway and ensure that whatever approach you take is acceptable to the community of reviewers once it is submitted. |
I assume that the ROS Discourse link went to the wrong place. Is this the correct link?
|
Same comments as on ros-industrial/abb_libegm#13. |
|
Closing according to ros-industrial/abb_libegm#13 (comment). |
re: ros-industrial/ros_industrial_issues#26