Skip to content
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.

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

Agree on an one or more extensions with common interest to develop concurrently with framework #22

Closed
birkland opened this issue May 13, 2016 · 2 comments

Comments

@birkland
Copy link
Contributor

Create corresponding github issues.

@scossu
Copy link

scossu commented May 18, 2016

I would go with option 3: establish a time frame for another round of votes (likes), pick 1-3 top use cases depending on implementation efforts required, and update the descriptions of these use cases to reflect the latest architecture design (some of the workflows rely on assumptions that are no longer valid).

@birkland
Copy link
Contributor Author

this was actually done in the form of Amherst's repository extension services. Additional extensions of common interest should be addressed in separate tickets, where applicable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants