Browse Source

Managing help offers (#2178)

* removed reference to the style-guide
* added a how-to-help; added a document describing the current maintainer status; fixes #2170; closes #1781
* listing the members of the support team
* use search before creating a new issue
* fixes typos
Alexander Wunschik 7 years ago
committed by GitHub
3 changed files with 94 additions and 20 deletions
  1. +12
  2. +67
  3. +15

+ 12
- 20 View File

@ -1,22 +1,14 @@
## Contributing
Contributions to the vis.js library are very welcome! We can't do this alone.
You can contribute in different ways: spread the word, report bugs, come up with
ideas and suggestions, and contribute to the code.
If you have any **general question** on how to use the vis.js library in your
project please check out
[stackoverflow]( for that.
There are a few preferences regarding **code contributions**:
- vis.js follows the node.js code style as described
- When implementing new features, please update the documentation accordingly.
- Make changes in the `develop` branch, not the `master` branch.
- Send pull requests to the `develop` branch, not the `master` branch.
- Only commit changes done in the source files under `lib`, not to the builds
which are located in the folder `dist`.
[Contributions](// to the vis.js library are very welcome! [We can't do this alone](//
### Questions
If you have any *general question* on how to use the vis.js library in your own project please check out [stackoverflow]( for thinks like that. **This is NOT a JavaScript help forum!**
### Bugs, Problems and Feature-Requests
If you really want to open a new issue:
* Please use the [search functionality](// to make sure that there is not already an issue concerning the same topic.
* Please make sure to **mention which module** of vis.js (network, timeline, graph3d, ...) your are referring to.
* If you think you found a bug please **provide a simple example** (e.g. on [jsbin]( that demonstrates the problem.
* If you want to propose a feature-request please **describe what you are looking for in detail**, ideally providing a screenshot, drawing or something similar.
* **Close the issue later**, when the issue is no longer needed.

+ 67
- 0
misc/ View File

@ -0,0 +1,67 @@
# HowTo Help
The company that developed vis.js for the main part, *almende* is [not able to maintain the project at the moment](./ So help from the community is very needed and welcome!
## There are many ways to help:
### Answering questions
There are new [issues with questions](// how to use vis.js opened almost every day. Be part of the community and help answer them!
A better way to ask questions on how to use vis.js is [stackoverflow]( Questions are posed here also and need to be answered by the community. [Please help answering questions]( here also.
### Closing old issues
A new issue is often opened fast and then forgotten. Please help go trough [the old issues](// (especially the [questions](// and ask the creator of the issues if the problem still exists before closing the issue. The support team uses the **issue inactive** label to mark these issues.
### Improve the webpage
The webpage is hosted on the [gh-pages branch](// If you find a typo or anything else that should be improved feel free to create a pull-request to *gh-pages*. Please make changes in your own fork of gh-pages so the support team can view the changes in your hosted fork.
### Create new examples
We have [a collection of examples](// Please help by creating interesting new ones that show a specific problem or layout. Keep the examples easy to understand for beginners and remove unnecessary clutter.
### Provide interesting showcases
If you use vis.js to develop something beautiful feel free to create a pull-request to our show cases page in the gh-pages branch](// [These showcases are displayed on our webpage]( and we are always looking for new examples.
### Confirming and fixing bugs
Every software has bugs. We also have [quite a nice collection]( ;-)
Feel free to fix as many bugs as you want!
You can not only help by fixing bugs, but also by confirming the bug or even creating a minimal code example to prove this bug exists.
### Implementing Feature-Requests
A lot of people have a lot of ideas for improving vis.js. [We label these issues as **enhancement**]( Feel free to implement a new feature by creating a new Pull-Request.
[Some issues are labeled **For everybody!**](// These are a good starting point.
### Reviewing Pull-Requests
We use [GitHub's two-step review](// to make sure pull-requests are clean. You can help by checking out pull-request branches and testing them. You also can comment on lines of code and make sure the pull-request introduces no new bugs or typos.
## Creating Pull Requests
There are some rules for pull-request:
* All pull-request must be to the [develop-branch](// Pull-request against the [master-branch](// must be closed. (Changes to [gh-pages](// are also ok.)
* Only commit changes done in the source files in the folder `lib`, not to the builds
which are located in the folder `dist`.
* Keep your changes small and clear. Only work on one topic at one time and only change lines of code that you have to change to reach your goal.
* Test your changes before creating a pull-request. The easiest way is to open the existing examples and playing with them.
* If you are fixing or implementing an existing issue, please refer to it in the description and in the commit message.
* If you are introducing a new feature, add some documentation and a new example to make it easy to adapt.
* If you introduce breaking changes, like changing the signature of a public function, point that out in your description. Breaking changes result in a new major release.
* Always adapt to the code style of the existing source. Never adapt existing code to your personal taste. :trollface:
**Happy Helping!!**

+ 15
- 0
misc/ View File

@ -0,0 +1,15 @@
# We need help!
## The current status
Vis.js is looking for people who can help maintain and improve the library. We've put a lot of effort in building these visualizations, fixing bugs, and supporting users as much as we can. For some time now, we’ve been lacking the manpower to maintain the library the way we have in recent years. @josdejong has left the company for a new opportunity, and @AlexDM0 has moved internally to a daughter company, with severe impact on his time and availability for Vis.js. At the moment @ludost is the official maintainer from Almende, but does not have much time to help out.
Although Almende is looking to replace the expertise required for Vis.js, we don't expect to be able to do comprehensive project management any time soon. At the same time we’d like to spare Vis.js from becoming abandonware, especially given the relative healthy user base. For the longer term future we would be happy if vis.js could stand on its own feet, community supported.
**If you want to support the project please just start by [helping out](./**
If you have shown some commitment to the project you can ask @ludost to become a member of the community support team. This team has write permissions to the repository and is helping maintaining it. Currently this team consists of:
* @ludost (almende maintainer)
* @mojoaxel
* @yotamberk