New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Clubhouse #] Feature Name Tech Design RFC #2

Open

tienyuan opened this issue Dec 9, 2019 · 2 comments

Assignees

Owner

tienyuan commented Dec 9, 2019 •

edited

Loading

Proposed Solution

Outline in enough detail for a team member to understand how you'll implement.

Please consider adding:

context, concerns that need product/design/dev clarification
examples for specific use cases, edge cases
FE: logic, states, scenes, VIP, workers, ui, libraries, tools
BE: logic, states, services, database changes, migrations, libraries, tools
performance choices
maintenance choices
flowcharts, pictures, links 🙂
what is in scope

Alternatives/Considerations

What other options have been considered? There are tradeoffs to choosing any path. Attempt to identify them here.

Please consider:

implementation cost, both in term of code size, complexity and time
the impact on maintenance, code readability
integration of this feature with other existing and planned features
cost of migrating existing codebase (is it a breaking change?)
what is not in scope

tienyuan self-assigned this

tienyuan changed the title ~~[Clubhouse #] Clubhouse Title~~ [Clubhouse #] Feature Tech Design

tienyuan changed the title ~~[Clubhouse #] Feature Tech Design~~ [Clubhouse #] Feature Name Tech Design RFC

Owner Author

tienyuan commented Dec 10, 2019

beans

Owner Author

tienyuan commented Dec 10, 2019

beans

omg what about bananas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment