This repository has been archived by the owner on May 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Home
Tom Lant edited this page Mar 22, 2017
·
2 revisions
Riot Meta is place to discuss and coordinate Riot Product changes independently of the platform-specific implementations.
Right now it is an experiment. The hypothesis that this experiment is testing is: by decoupling feature discussions from the platform-specific projects, we can maintain a clearer view of feature parity across the platforms.
- A feature is represented as a single issue. It will most likely have corresponding issues (perhaps multiple) within each platform's repo.
- The Riot Meta repo has a project for each platform which is used to track each issue's progress through development. This progress can be seen on the issue page in the 'Project' box.
- Keeping these projects up-to-date is the job of the project manager - for Riot Web this is Tom, for mobile this is Giom.
There are outstanding questions about how this should be used:
- Should items in riot-meta represent:
- Features (expecting to represent potentially multiple changes to multiple platforms, potentially developed by separate people and deployed at separate times)
- Every one of the smallest-possible code changes required to implement said feature
- Something in between
- How much do we need to proscribe linking between riot-meta issues and platform-specific issues?
- Probably not much
- How much value (vs how much overhead) does this add compared to using riot-web as a de-facto cross-platform feature development tracker?
- Should these features have priority tags associated with them?