pfs_development.pdf
[INFRA-38] Document coding standards and procedures Created: 02/Jul/16 Updated: 31/Jul/16 Resolved: 31/Jul/16 |
|
| Status: | Done |
| Project: | Software Development Infrastructure |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | swinbank | Assignee: | swinbank |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
pfs_development.pdf
|
| Epic Link: | drp-docs |
| Sprint: | 2014-15, 2014-16 |
| Reviewers: | aritter |
| Description |
|
Our coding standards and development procedure are derived from LSST's. In many cases, we can use the relevant LSST documentation directly; in others, some modification may be appropriate. Collect and publish a collection of pointers to the relevant LSST docs, together with such modifications as are required for PFS DRP. |
| Comments |
| Comment by swinbank [ 12/Jul/16 ] |
|
Attached is a set of notes I brain-dumped on how things work on LSST and how they translate to PFS. I do not claim it is comprehensive, but it's a starting point. Can you please check and see if there's anything in there you disagree with and/or if there are important things that ought to be added? |
| Comment by swinbank [ 12/Jul/16 ] |
|
Because of the way PFS-JIRA is configured, it's only possible to have a single user named as a reviewer. Changing that is not impossible, but it's awkward. Therefore, only aritter is named as a reviewer here, but I think it would be useful for rhl to take a look as well. |
| Comment by aritter [ 17/Jul/16 ] |
|
Looks reasonable and captures everything I can think of. |
| Comment by swinbank [ 31/Jul/16 ] |
|
Now displayed at http://pfs-2d-pipeline.readthedocs.io/en/latest/dev.html. |