-
Notifications
You must be signed in to change notification settings - Fork 46
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
idea for the roadmap, see #261 #265
Conversation
We have some ongoing efforts which need to be done as well as some bug fixes and new features we'd love to implement. If you think we should focus on something else: Please just comment, add it or talk to us, whatever you feel like doing! | ||
|
||
|
||
## Ongoing Efforts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a good breakdown to me! It looks a bit like I can't start working on the 'near future' issues just yet -- is that true?
This is also a good place to mention why you want to accomplish some of these tasks -- it helps cast vision around your project!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I see your point. Do you have a recommendation on how to rephrase it to make it clearer? :-) I'll also try to write a bit about the why for the other points tomorrow. 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be as simple as adding a bit of text under that section: "These issues are up next to be worked on! This is a good place to jump in if you want to help with some of our heavier tasks"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, see the next version 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉👏 I love this!
On Thu, Mar 3, 2016 at 6:19 PM Bastian Greshake notifications@github.com
wrote:
In ROADMAP.md
#265 (comment):@@ -0,0 +1,22 @@
+# Our Roadmap
+
+Hey, there. Thanks so much for the interest in openSNP and what we're trying to accomplish over the next weeks and months.
+
+We have some ongoing efforts which need to be done as well as some bug fixes and new features we'd love to implement. If you think we should focus on something else: Please just comment, add it or talk to us, whatever you feel like doing!
+
+
+## Ongoing Effortsok, see the next version [image: 😄]
—
Reply to this email directly or view it on GitHub
https://github.com/openSNP/snpr/pull/265/files#r54965859.
I've added a bit to the pad about "required knowledge" for each of the issues, in case someone interested wants to focus more on JavaScript than Ruby, for example we should also think about a "who we are so far" section so that potential candidates know who to expect and aren't scared off by an anonymous black box of developers |
I added those requirements to the ROADMAP.md, I think that's good to merge for now if there are no objections :-) |
idea for the roadmap, see #261
This is my draft for a roadmap to close #261