2019-04-19 Meeting notes

Date

Apr 19, 2019 10:00 AM PDT

Meeting number (access code): 904 013 480

Join by phone

+1-510-210-8882 USA Toll

Topic: How do projects contribute to core
- Key Decision:
Topic: Use of wiki vs. read-the-docs or GH Pages
- Key Decision: Use wiki or markdown tool or both?
- Key Decision: Which wiki (confluence/github) or markdown tool (RTD/GHP)?
Topic: CI/CD for core
- Key Decision: Resources for CI/CD? Public vs. private (behind JPL)?
- Key Decision: Cost: free or paid? If paid, who’ll pay? Projects/missions? Who needs to be at the table to answer that?
Determined by results of Slack poll https://jpl.slack.com/archives/CHD604FT4/p1554918636009200

Time	Item	Discussion Lead	Notes

Time	Item	Discussion Lead	Notes
:05	Intro	@Frank Greguska	Why Dev Meetup? Meeting Format
:10 - :25	How Projects Contribute to Core	@Sujen Shah	Check Jira if desired functionality already exists or else create a new feature request. Labelling issues Develop and test the new functionality on their cluster and then submit a PR. Voting on change / accepting pull request. How to handle releases in that case? Point release vs merge to master and take new release? Core devs have access to create branches on the core repo and external devs need to fork ? How to install the branch on a running cluster as mozart/ops is not git managed?
:25 - :40	Use of Wiki vs. Docs	@Frank Greguska	Types of documentation: https://www.altexsoft.com/blog/business/technical-documentation-in-software-development-types-best-practices-and-tools/ Versioning wiki’s is hard: https://www.atlassian.com/blog/archives/technical_writing_wiki_documentation_release_management Current wiki’s: https://wiki.jpl.nasa.gov/display/hysds/HySDS+Community https://hysds-core.atlassian.net/wiki/spaces/HYS/pages/17989633/HySDS+Community+Wiki https://github.com/hysds/hysds-framework/wiki
:40 - :55	CI/CD for Core	@Gerald Manipon	Already using CircleCI for weekly builds of HySDS core docker images: https://circleci.com/gh/hysds/hysds-dockerfiles weekly builds pushed up to dockerhub: https://hub.docker.com/u/hysds
:55 - :00	Wrapup	@Frank Greguska	Set time for next meetup

New architecture is being designed in which core will be containerized vs existing on bare metal VM as it is now.

Agreement to use Wiki as well as Read the Docs.
Use Atlassian Wiki
Documentation on Wiki is mainly for documentation that is not version dependent. General concepts, Process Documentation, requirements, etc…
Documentation on Read the Docs will be version-dependent. What do specific parameters mean? Default values? Feature specific information.
Everyone should be comfortable adding/editing the wiki. There is a lot of information on the JPL wiki that needs to be moved over. If you can just move one page it helps.

First step: for each repo run: `python setup.py install` + `python setup.py test`
TODO: look into CircleCI free plan for open source projects
https://circleci.com/open-source/
mission manager: “Not concerned about cost of infrastructure for CI/CD”

look into CircleCI free plan for open source projects

add circleci build jobs for each repo

Figure out how to aggregate sub project documentation into the core single documentation @Frank Greguska

Send out a Poll for next time - bi-weekly meetups @Frank Greguska

Need a deeper discussion about how changes get back based on the new design @Gerald Manipon presented.
Use Atlassian Public Wiki

Setup pubic CircleCi for core repos
Use read the docs for the code documentation and Wiki for the User and Project documentation
No more Friday meetings