-
Type: Task
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
-
Story Points:0
https://docs.voltha.org/master/overview/contributing/jira_tickets.html
- Change VOL-xxxx strings into Jira URL refernces.
Description field:
- Note using the preformatted code block for readability
Incorporate Serkant(s) suggestions:
The contributing page has been updated to note them:
o https://docs.voltha.org/master/overview/contributing.html#submitting-code
o https://docs.voltha.org/master/overview/contributing.html#steps-to-successful-prs
All seems good, and very useful info for new comers. Thanks Joey. A couple of questions and comments: 1. It is a little bit confusing and the links in this text doesn't seem going to correct paths. Search for Jenkins Technical User and click a job entry.In the top grey navigation bar, following “Dashboard”, click the test suite name to view the active job dashboard history verify_voltha-docs_unit-test. 2. Why it's necessary to update the copyright in source files? Do you mean "include the copyright text (link to the onf standard copyright) if you submit a new source code? 3. Don't we expect at least 2 approvals to be able to submit a patch?
- links to
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
34601,4 | [VOL-5166] - docs.votlha.org: misc edits | master | voltha-docs | Status: MERGED | +2 | +1 |