Set up repo for managing our cross platform plans #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Opening for discussion. I was thinking of ways to help align our cross-product plans, and having a singular repository that all our products use to track shared goals seemed like a sensible solution. The proposed README.md goes into more detail.
Might be cool to even administer the repo with a DAO using radicle orgs or something at some point.
This PR would not just be some new specifications, it represents using this repo to try to reflect the current state of our product, and use pull requests against it as proposals for cross-product changes.
This solves the problem where we open an issue on both mobile and extension every time there is even a small improvement that should be made in both. Those teams could still track their individual progress, but this can give us a shared issue board for considering cross-platform improvements.