Notice: As of 30 June 2022, DTC has ceased all activities supporting the HWRF Developer community. The HWRF developers committee has transitioned to the UFS Hurricane Application and no longer addresses development for the HWRF system.
DTC Roles and Responsibilities
- Set up and maintain the HWRF repository
- Run the DTC Consistency Checks on the trunk of the community repositories on an as-needed basis. A review of the community repository developments will be done at least monthly (can be done more frequently at times of intense development) and updates from the community repository trunk will be done as needed.
- After consistency checks have passed, update branches/HWRF with the developments in the trunk of the community repositories.
- When developments are complete, update the trunk of the community repositories to contain the developments from branches/HWRF.
- Provide support to developers in using SVN code management.
EMC Roles and Responsibilities
- Maintain a read-only mirror of hwrf repository at EMC subversion server (to be used for annual HWRF implementations)
- EMC development of new HWRF capabilities will follow internal EMC guidelines and may be added to the HWRF repository at any time.
Developers Roles and Responsibilities
- Become familiar with the basics of SVN code management.
- Contact the HWRF Developers Committee to describe their planned development and discuss the timeline and requirements for the project.
- Use a development branch of the hwrf repository for all code development.
- Follow best practices in code development and any specific rules for the component they are developing for.
- Do not break or change the answer of existing configurations, either operational or generic (may be important to community users) without previous discussion and agreement by the HWRF developers committee.
- Update the development branch as often as possible, as appropriate.
- When the development is complete, resolve any conflicts with branches/HWRF.
- Propose the developmental work to the HWRF Developers Committee.
- After approval from the HWRF Developers Committee, commit developments to branches/HWRF.
Developers Committee Responsibilities
- An HWRF developers’ committee, consisting of two members from EMC and two members from DTC, will be established to decide what developments from the development branches should be added to branches/HWRF.
- The committee will meet twice a month to review any proposals for commits to branches/HWRF.
- Developers who are ready to commit their developments to branches/HWRF should inform the committee of their intent at least 24 h before the meeting, and send a description of their changes, along with code diffs and a summary of the results of their tests. During the meeting, the committee will approve or reject the commits.
- All members have veto power.
