Managing help offers #2178
Managing help offers #2178
Conversation
|
@ludost Can you please have a look at this pull-request. This is clearly in the realm of the maintainer and I want to make sure we are on the same page here! |
| Thanks! | ||
| ### Bugs, Problems and Feature-Requests | ||
| If you really want to open a new issue: | ||
| * Please make sure to **mention witch module** of vis.js (network, timeline, graph3d, ...) your are referring to. |
There was a problem hiding this comment.
small misspelling "witch" -> "which"
|
|
||
| Thanks! | ||
| ### Bugs, Problems and Feature-Requests | ||
| If you really want to open a new issue: |
There was a problem hiding this comment.
First step should probably be something like: "Please check if the question was asked in the open/closed issues"
|
|
||
| ### Provide interesting showcases | ||
|
|
||
| If you use vis.js to develop something beautiful feel fee to create a pull-request to our show cases page in the gh-pages branch](//github.com/almende/vis/tree/gh-pages/showcase). [These showcases are displayed on our webpage](http://visjs.org/showcase/index.html) and we are always looking for new examples. |
|
General approach is excellent. I do wonder if you are already willing to be mentioned in the 'current status' as part of the support team? Something like: a number of people from the user community have been picking up the first work, forming a support team. Currently this team consists of @mojoaxel and @yotamberk . What do you think about this? Besides the issue tracker and the 'enhancement' label, we might want to create some form of roadmap file as well? This file would be tracking longterm goals in the development. Would something like that be helpful? On a fully separate note: it has been a long standing irritation that the /dist folder is actually under version control, leading to local changes that should not be committed until a release is done. I like to know if there are examples out there of how to handle this cleaner? This question influences the development flow, that's why I mentioned it now. But again, great work! I'm glad you are helping eve.js forward! |
Thanks! I just thought we need to get rid of #1781
Why not!
I don't think that is easy. In a community driven project contributors are normally not willing to stick to a roadmap, but contribute what they want, when the want. As far as I'm concerned a roadmap makes only sense almende internal, if you find time to get somebody implementing again.
I'm so with you!! I was already looking into it and could not find an easy solution, yet. I created #2181 for that. |
This is trying to fix #2170 and to close #1781
I created a document describing the current maintainer situation (misc/we_need_help.md).
I also added a "HowTo Help" document (misc/how_to_help.md) that describes in detail how to start getting involved in the project.
Also I adapted the CONTRIBUTIONS document and made it clear that general questions should be asked on stackoverflow.
This docs should be a first start and I hope you all keep them up to date and helpfull!