A style guide for my open source projects.
- links to language specific style guide
- merge go style guide from go-learning and dyweb/gommon
- try to use one word as project name
TBD
- use
UpperCasefor project name?
TODO: this part has changed a lot w/ the new milestone and components based approach, e.g. no longer use issue
- create a issue with title
[design][component-name] XXX- put it into the component's project
- create file under
doc/design, updatedoc/design/README.md. - update
doc/roadmap.mdto add todo items and re order existing timeline.
- find it from roadmap
- create a issue with title
[impl][component-name] XXX- put it into the component's project
- assign a milestone (release number)
- create a new branch
component-name/feature-name/statuse.g.gobench/parse/init - keep track of progress in
doc/log - update
doc/roadmap.md
- move unfinished work in this release to next release in
doc/roadmap
Examples: benchhub
docCHANGELOG.mdROADMAP.mddesignREADME.mdlink to all design doc that cross multiple componentsschema.mde.g. database schema
componentscomp-1README.mdlink to log and milestones, and high level design?feature-a.mdbig feature on that component that worth a dedicated note
README.mdtree to all components
milestonesv0.0.1-small-feature-a-of-medium-feature-1README.mdbreak up features, components and implementation ordercomp-1.mdcomponent notes specific to this milestone
v0.1.0-medium-feature-1v1.0.0-a-major-release-that-i-will-never-reachREADME.mdtree to all milestones
log2020-02-03.mddiary with nothing special2020-02-04-design-schema.mdspecial events should show up in file name
hackDockerfile
MakefileREADME.md
TODO: this part has changed a lot w/ the new milestone and components based approach
For upcoming, order by release number ASC, so recent development is on the top. For finished, order by release number DESC. It may not be same as release note so keep it in Roadmap.
## Upcoming
### v0.0.3
- improve compression
### v0.0.4
- add new index schema
## Finished
## v0.0.2
- fix bugs
## v0.0.1
- introduced a new bug
Order by release number DESC, so recent release is on the op
## v0.0.2
- fix bugs
## v0.0.1
- introduced a new bug