Refine chunked transcription strategy
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
# Contributing
|
||||
|
||||
1. Branch Strategy
|
||||
2. Development Workflow
|
||||
3. Commit Messages
|
||||
4. Definition of Done
|
||||
5. Coding Standards
|
||||
6. Documentation Requirements
|
||||
7. Testing
|
||||
8. Creating ADRs
|
||||
|
||||
## Development Workflow
|
||||
|
||||
See ADR 0010 for the overall development workflow.
|
||||
|
||||
---
|
||||
|
||||
## Commit Messages
|
||||
|
||||
Commit messages should be:
|
||||
|
||||
- short
|
||||
- descriptive
|
||||
- written in the imperative mood
|
||||
|
||||
Examples:
|
||||
|
||||
- Add meeting import
|
||||
- Implement transcript persistence
|
||||
- Refactor storage layer
|
||||
- Fix timestamp serialization
|
||||
|
||||
Avoid messages such as:
|
||||
|
||||
- Update
|
||||
- Changes
|
||||
- Fix
|
||||
- Miscellaneous
|
||||
|
||||
Reference in New Issue
Block a user