We need your help #1781

josdejong · 2016-04-07T10:14:24Z

Almende is looking for people who can help maintaining and improving vis.js. We've put a lot of effort in building these visualizations, fix bugs, and support users as much as we can. Since some time we're lacking the manpower to maintain the library as we've done latest years. We need your help!

What can you do?

Help out other users having questions
Help fixing small bugs
Help with implementing new features
Become a collaborator and help with releases & maintenance
...

Are you interested in helping some way or another? Please let us know.

AlexDM0 · 2016-04-08T07:57:07Z

Hi Winston, We can use whatever help you want to provide. If you'd like to join just respond to the issues on here. If there are bugs in vis you can do a pull request with the solution until we find a better way to do it. Thanks for helping out!

for-sagacity · 2016-04-08T08:09:39Z

Ok I got it.
I will help you as far as i can.

beingsagir · 2016-04-12T08:14:05Z

This is an awesome library. In future it will serve a lot of professional designs and apps. We need to come forward and carry it together. I will be there.
I also do suggest to (let's) make everything little organised so, each time we come here know what to do.

[-] The website also needs to be little more organised.

AlexDM0 · 2016-04-12T08:15:44Z

Thanks! We're open to suggestions and pull requests to the website as well. What do you have in mind?

yotamberk · 2016-04-14T07:30:44Z

I can pick up some bugs during some weekends.
I deal mostly with the timeline so I'm willing to take any bugs there.

AlexDM0 · 2016-04-14T07:41:09Z

That would be great!

beegeesquare · 2016-04-15T12:17:33Z

I'm happy to help !

josdejong · 2016-04-16T07:34:01Z

Thanks @beegeesquare . Just sniff around for smaller or bigger issues/feature requests that you find interesting to pick up.

kurtcagle · 2016-04-19T17:42:56Z

I'm a regular user (and evangelist) of visjs, I can't promise much, but I'll try to spend some time in the code as well.

SepiG · 2016-04-19T19:58:05Z

Interested, what's next?

AlexDM0 · 2016-04-19T20:12:11Z

That would be great! If not the code then we could use a lot of help with answering issues.

Regards

AlexDM0 · 2016-04-19T20:15:02Z

@SepiG answering issues, both open and new ones. Help out in code where you can or improve the website and/or documentation. Any changes can be done with pull requests to the ghpages or develop branch.

Regards

kurtcagle · 2016-04-19T20:58:28Z

Alex,

I'd definitely be willing to help there. I'm kind of a JS-lite kind of guy,
good enough to understand what's going on and use the tools, but definitely
much better writing about it than deep-diving. If there a particular faq or
similar area that you need to have filled in?

Kurt Cagle
Founder, Semantical LLC
[email protected]
443-837-8725

AlexDM0 · 2016-04-19T21:00:13Z

If you feel that a faq would alleviate the amount of issues that come in then sure. It would be nice if there would be only one place to find answers though: the documentation.

kurtcagle · 2016-04-19T23:55:05Z

That makes sense. How do you generate your documentation?

Kurt Cagle
Founder, Semantical LLC
[email protected]
443-837-8725

On Tue, Apr 19, 2016 at 2:00 PM, Alex [email protected] wrote:

If you feel that a faq would alleviate the amount of issues that come in
then sure. It would be nice if there would be only one place to find
answers though: the documentation.

On 19 Apr 2016, at 22:58, kurtcagle [email protected] wrote:

Alex,

I'd definitely be willing to help there. I'm kind of a JS-lite kind of
guy,
good enough to understand what's going on and use the tools, but
definitely
much better writing about it than deep-diving. If there a particular faq
or
similar area that you need to have filled in?

Kurt Cagle
Founder, Semantical LLC
[email protected]
443-837-8725

On Tue, Apr 19, 2016 at 1:12 PM, Alex [email protected] wrote:

That would be great! If not the code then we could use a lot of help
with
answering issues.

Regards

On 19 Apr 2016, at 19:43, kurtcagle [email protected]
wrote:

I'm a regular user (and evangelist) of visjs, I can't promise much,
but
I'll try to spend some time in the code as well.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#1781 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#1781 (comment)

DanielZhangQingLong · 2016-04-20T03:25:28Z

I have been using your vis.js for quite a long time, I like to help though I am not very good js developper.

AlexDM0 · 2016-04-20T07:56:51Z

@DanielZhangQingLong a lot of the work now is answering issues. Most of them do not require coding, like users with questions or users misunderstanding the dataset or events or options. If you can help out responding to these that would be great! You can always ask for help in the issue if you feel it's going over your head.

@kurtcagle we write it in html in the develop branch. Every release we overwrite the docs on ghpages with those on develop. If you feel like automating it all, be me quest ;). it could improve the inline documentation.

Anyone else: it would be a great help if someone could go over all examples and add a clone in jsbin link to them. This would make is much much easier to help new people as you can take a jsbin staring point from any example. It would also make it easier for users with questions to show their issues.

rcbyrne · 2016-04-22T08:45:55Z

I use Vis.js as a key part of an internal application I develop. I have also been wanting to get into some open source development outside of work, so would be happy to help pick up some work on the odd weekend.

andreasmacht · 2016-04-30T13:50:15Z

Hi Almende team,

First time I saw visjs library, I was very impressed about the visual features that you implemented. I am still a light-weight JS guy, but I want to get more proficient in JS and start a new career in there. I am definitely strong in documentation, issues' handling and management, answering questions as far my knowledge takes me. And the more I deep dive into JS, I would also like to support in fixing bugs in the future.

Currently, I am doing a capstone project with MeteorJS where I also use visjs (I've recognised in the past that visjs doesn't always respond well with MeteorJS). Due date is 23rd May. Hence, till then you won't find me being crazily active here, but I keep watching the progress and I am willing to support.

Best!

murarisumit · 2016-05-02T05:49:33Z

Hi @josdejong , I'm more into devops, so if anything in that domain is required, I'll be happy to help :)

acefxlabs · 2016-05-03T14:01:34Z

Just saw vis and actually we are intending on extending it in the office so we can also be part of this, will do all i can to contribute

data-hack-scripts · 2016-05-11T23:07:59Z

Hello
I would like to help, I like VIS!
:)

frankc60 · 2016-05-18T18:23:55Z

Hi, I am more than happy to be available to help out and contribute.

AlexDM0 · 2016-05-18T19:58:09Z

Thats great! We're looking for people helping out on issues and putting in / reviewing pull requests.

Cheers

On 18 May 2016, at 20:24, Frank [email protected] wrote:

Hi, I am more than happy to be available to help out and contribute.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

igbopie · 2016-05-20T19:05:44Z

Hi!

I am interested!

carthworks · 2016-05-24T07:27:43Z

please add me too

AlexDM0 · 2016-05-24T07:54:25Z

Thanks!

On 24 May 2016, at 09:27, Karthikeyan Thiagarajan [email protected] wrote:

please add me too

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

igalapedia · 2016-05-29T15:33:51Z

I will be ready to contribute with the best of my knowledge in which ever way it comes before me. I am in the practice of applying VIS.js to my web based design application for solving engineering problems.

Please add me to the team of contributors and don't forget to send alert when there is issue to attend to.

mojoaxel · 2016-08-17T09:41:24Z

@jankdiss No questions in this issue, please. The best place to ask this kind of questions is stackoverflow.

garthtee · 2016-08-21T17:25:52Z

I'd love to help 👍 @josdejong

yotamberk · 2016-08-27T20:18:55Z

How can I submit an application to the support team?

mojoaxel · 2016-08-27T20:39:16Z

@yotamberk Just start helping here.
After you started getting "into the flow" of the project you can contact @ludost with a request for access.

yotamberk · 2016-08-27T20:57:13Z

No problem. I've added recently the rtl to the timeline, and now working on horizontal hiding of items when not visible + horizontal scroll. I'll submit the two in two separate pull request hopefully in the next two weeks after I've fully tested them. I'll be happy to go over other pull requests and test them out.

ceomuse · 2016-09-10T00:24:14Z

Hello, I'm afraid I don't have the skills to assist but perhaps I can help in so other ways. I can provide a paid staff we've contracted for the next few years. The other is that dirty word, money to pay for some additional help. I like what you're doing and see some features we may be able to utilize in one of our projects down the road.

May we help and if so, who is the best contact?

josdejong · 2016-09-12T07:16:08Z

Thanks for your offer @ceomuse. I think it's best to send an email to Andries Stam ([email protected]) for financial/business related ideas, and to contact Ludo (@ludost) for technical ideas.

balguri23 · 2016-09-13T09:54:39Z

Interested to pick some bugs, what next?

ram-c · 2016-09-25T10:06:31Z

Sure :) I'll be happy to help! I'll start with bug regression/testing

bardcrack · 2016-09-27T04:58:46Z

My English no is very good, but i want Help for this project.

wimrijnders · 2016-10-09T20:47:34Z

Hi Almende,

This is to inform you that I have forked vis.js and am currently refactoring the Graph3D part.
My ultimate goal is is make multiple graphs per view possible ('groups' I believe they are called elsewhere), but this is the first step.

I'm rearranging the code so that the parts per graph style are grouped together in 'style handlers', in the process getting rid of all the tests on selected style such as:

if (this.style === Graph3d.STYLE.GRID ||
    this.style === Graph3d.STYLE.SURFACE) {
    this._redrawDataGrid();
  }
  else if (this.style === Graph3d.STYLE.LINE) {
    this._redrawDataLine();
  }
  else if (this.style === Graph3d.STYLE.BAR ||
    this.style === Graph3d.STYLE.BARCOLOR ||
    this.style === Graph3d.STYLE.BARSIZE) {
    this._redrawDataBar();
  }
  else {
    // style is DOT, DOTLINE, DOTCOLOR, DOTSIZE
    this._redrawDataDot();
  }

I hope this can be appreciated.

En groetjes uit Groningen!

Wim.

wimrijnders · 2016-10-10T09:30:03Z

Question, wrt. my previous post here:

I'm making the changes in the master branch - I understand that these should later be pulled into the develop branch.
But shouldn't I have done the changes in the develop branch to begin with?

Just wondering.

Stexxen · 2016-10-10T09:56:23Z

@wimrijnders Hi is there any reason you are specifically forking vis.js and not adding your changes as a pull request?

wimrijnders · 2016-10-10T09:59:05Z

OK, my ignorance is showing here....

I thought that was how a pull request worked, i.e. you fork, make changes
and return the changes from the fork in a pull request.

If this is not the way to do it, please advise me what the correct
procedure is.

Met vriendelijke groet,

Wim Rijnders
http://axizo.nl

On Mon, Oct 10, 2016 at 11:56 AM, Steven [email protected] wrote:

@wimrijnders https://github.com/wimrijnders Hi is there any reason you
are specifically forking vis.js and not adding your changes as a pull
request?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1781 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAu8DfEWLsNduyOnKchNFmrYExL1Jx2Sks5qygvOgaJpZM4IB6xz
.

Stexxen · 2016-10-10T10:09:01Z

Sorry that was my assumption, that you meant fork as in a permanent one.
Please ignore me :-S

In regards to your changes, any pulls must be done on the develop branch, not the master.
Cheers,
S.

wimrijnders · 2016-10-10T10:16:55Z

Ah, ok. No, I wasn't planning on maintaining a fork myself! I have every
intention of folding the changes back to the main project. I have enough
kids to take care of :-).

Pulls to the develop branch: understood. But chould I also be doing the
changes in the develop branch? I used the master as base right now.

Met vriendelijke groet,

Wim Rijnders
http://axizo.nl

On Mon, Oct 10, 2016 at 12:09 PM, Steven [email protected] wrote:

Sorry that was my assumption, that you meant fork as in a permanent one.
Please ignore me :-S

In regards to your changes, any pulls must be done on the develop branch,
not the master.
Cheers,
S.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1781 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAu8Da-Tmsx0padPK5Gog5KmXwXwUNsaks5qyg7EgaJpZM4IB6xz
.

Stexxen · 2016-10-10T10:18:30Z

yes please make changes to develop branch, as that has quite a few pulls already done on it. So is significantly ahead.

wimrijnders · 2016-10-10T10:21:36Z

OK thanks, will do. I'll merge my changes into develop and continue from
there.

Met vriendelijke groet,

Wim Rijnders
http://axizo.nl

On Mon, Oct 10, 2016 at 12:18 PM, Steven [email protected] wrote:

yes please make changes to develop branch, as that has quite a few pulls
already done on it. So is significantly ahead.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1781 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAu8DbNxAmkCyVyyCt1cFQET6yDN20x3ks5qyhD-gaJpZM4IB6xz
.

rohanmallelwar · 2016-10-18T10:51:02Z

Yes, I'm interested both in learning and contributing. Let me know the process to enrol myself for this.

mojoaxel · 2016-10-18T14:30:20Z

@dragonzone Can you please contact me. I would like to make you a team member if you are interested.

abcbaby · 2016-10-19T00:48:34Z

@mojoaxel , Thanks for the invite, however, I don't think I will have that much time dedicated to the project. Further, I only have experience w/ the vis.js Network & DataSet portion only. Once in awhile in my spare time, I will try to pitch out w/ the project since @AlexDM0 had helped me alot awhile back so I want to give back and don't want the project to be abandonware.

* 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

mojoaxel · 2016-10-19T08:37:38Z

##################################################################################

Please read the new "We need help" page! If you want the help out start Here.

##################################################################################
This issue is closed now.

josdejong added the help wanted label Apr 7, 2016

josdejong mentioned this issue Apr 18, 2016

Hierarchical Graph is so stretched that it looks like a line #1804

Closed

controversial mentioned this issue Aug 27, 2016

Network: Static node size for shapes with labels inside #1838

Closed

mojoaxel mentioned this issue Sep 1, 2016

Timeline: Chrome (Mac/Debian): Stuttering touch/drag of timeline produced by mousewheel usage in another viewsc #2023

Closed

josdejong mentioned this issue Oct 4, 2016

Plot Graph2D and Timeline in the same container #1757

Open

mojoaxel mentioned this issue Oct 18, 2016

Managing help #2170

Closed

mojoaxel mentioned this issue Oct 18, 2016

Managing help offers #2178

Merged

almende locked and limited conversation to collaborators Oct 19, 2016

mojoaxel closed this as completed Feb 16, 2017

We need your help #1781

We need your help #1781

Comments

josdejong commented Apr 7, 2016

AlexDM0 commented Apr 8, 2016 via email

for-sagacity commented Apr 8, 2016

beingsagir commented Apr 12, 2016

AlexDM0 commented Apr 12, 2016

yotamberk commented Apr 14, 2016

AlexDM0 commented Apr 14, 2016 • edited Loading

beegeesquare commented Apr 15, 2016

josdejong commented Apr 16, 2016

kurtcagle commented Apr 19, 2016

SepiG commented Apr 19, 2016

AlexDM0 commented Apr 19, 2016 • edited Loading

AlexDM0 commented Apr 19, 2016

kurtcagle commented Apr 19, 2016 • edited by AlexDM0 Loading

AlexDM0 commented Apr 19, 2016 • edited Loading

kurtcagle commented Apr 19, 2016

DanielZhangQingLong commented Apr 20, 2016

AlexDM0 commented Apr 20, 2016

rcbyrne commented Apr 22, 2016

andreasmacht commented Apr 30, 2016

murarisumit commented May 2, 2016

acefxlabs commented May 3, 2016

data-hack-scripts commented May 11, 2016

frankc60 commented May 18, 2016

AlexDM0 commented May 18, 2016

igbopie commented May 20, 2016

carthworks commented May 24, 2016

AlexDM0 commented May 24, 2016

igalapedia commented May 29, 2016

mojoaxel commented Aug 17, 2016

garthtee commented Aug 21, 2016

yotamberk commented Aug 27, 2016

mojoaxel commented Aug 27, 2016

yotamberk commented Aug 27, 2016

ceomuse commented Sep 10, 2016

josdejong commented Sep 12, 2016

balguri23 commented Sep 13, 2016

ram-c commented Sep 25, 2016

bardcrack commented Sep 27, 2016

wimrijnders commented Oct 9, 2016 • edited Loading

wimrijnders commented Oct 10, 2016

Stexxen commented Oct 10, 2016

wimrijnders commented Oct 10, 2016

Stexxen commented Oct 10, 2016

wimrijnders commented Oct 10, 2016

Stexxen commented Oct 10, 2016

wimrijnders commented Oct 10, 2016

rohanmallelwar commented Oct 18, 2016

mojoaxel commented Oct 18, 2016

abcbaby commented Oct 19, 2016

mojoaxel commented Oct 19, 2016

AlexDM0 commented Apr 14, 2016 •

edited

Loading

AlexDM0 commented Apr 19, 2016 •

edited

Loading

kurtcagle commented Apr 19, 2016 •

edited by AlexDM0

Loading

AlexDM0 commented Apr 19, 2016 •

edited

Loading

wimrijnders commented Oct 9, 2016 •

edited

Loading