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

Community involvement #4015

Open
Jogai opened this Issue Jun 26, 2018 · 20 comments

Comments

Projects
None yet
8 participants
@Jogai
Copy link

Jogai commented Jun 26, 2018

Its good that the project asks for help from the community, but I think the project would benefit if the maintainers looked at pr's more often. There are some issues labeled "Fixed, waiting for release". It might be better to do more small releases to keep the community interested in contributing.

There are more pr opened than closed, the same with issues. The maintainers are barely commenting on anything. Personally that doesn't inspire me to make more contributions...

@avrahamcool

This comment has been minimized.

Copy link

avrahamcool commented Jul 4, 2018

any response from the maintainers?
there are a lot of fixes already committed (and verified) that are crucial for vis.
when do you plan on releasing a new version?

@Jogai

This comment has been minimized.

Copy link
Author

Jogai commented Jul 4, 2018

@yotamberk created his own fork, but it seems he's mostly focusing on timeline. I like forks better if they get an 'official endorsement' from the main project. Now its not clear what the other maintainers ( @ludost @mojoaxel @Tooa @eymiha @bradh @wimrijnders @macleodbroad-wf ) think about the direction of the project.

@mojoaxel

This comment has been minimized.

Copy link
Member

mojoaxel commented Jul 4, 2018

It looks like @yotamberk is the only one still involved in the project.

I would consider this project unmaintaind for the moment.

The only way to get this project back on his feed would be to find a sponsor (opencollective). The first thing a maintanier should do (in my opinion) would be to devide the library in multible modules (network, timeline..), and to ensure a fast release-process.

@bradh

This comment has been minimized.

Copy link
Contributor

bradh commented Jul 4, 2018

I previously retired from maintainership - I couldn't handle the "entitled" approach I saw from a small number of users.

@katjasmin

This comment has been minimized.

Copy link

katjasmin commented Jul 4, 2018

Well it would be helpful if the opencollective link would be more prominent. So vis users like myself could easily contribute at least some money to the project, because I would happily do so. I just didn't know that the link existed, because it isn't mentioned on either the project home page or the github page.

@mojoaxel

This comment has been minimized.

Copy link
Member

mojoaxel commented Jul 4, 2018

Well it would be helpful if the opencollective link would be more prominent.

I've integrated it in the README (develop branch) but there has not been a single release since that. That's why the readme is not up to date...Somebody really should create a new release!

@avrahamcool

This comment has been minimized.

Copy link

avrahamcool commented Jul 5, 2018

vis is a great and impactfull project.
it has a large (and active) community - it will be a great loss if it will fade like that.
there are no real alternatives for the capabilities of vis.

will sponsoring the project really help? how much money are we talking here?
I think that we can raise the community awareness for that matter - it's a small price to pay for such a great project.

and also - it's time to thanks all the members of the project for their work so far.

@jgorene

This comment has been minimized.

Copy link
Member

jgorene commented Jul 10, 2018

Indeed, it's a awesome library and it would be too bad if this project got lost!
Unfortunately, I don't have enough skills to help effectively...

A single developer (or almost in fact) to maintain this project must be huge over time!
All that remains is "to feed" the opencollective and find a sponsor...
Another solution would be to make a paid version (with low cost by user, hopeful;)... why not ?

@yotamberk

This comment has been minimized.

Copy link
Contributor

yotamberk commented Jul 22, 2018

If anybody is interested in Timeline, you are more than welcome using my branch:
https://github.com/yotamberk/timeline-plus/
I'm maintaining it and upgrading versions weekly.
I feel I had to branch off to my own fork because I couldn't handle the issues for the other modules. There was no easy way for me to maintain this lib without the separation... It seemed that the owners were not going to allow the separation, so I simply took it to my own fork - since I'm the only maintainer anyways...

@micahstubbs

This comment has been minimized.

Copy link

micahstubbs commented Aug 5, 2018

I might make my own fork for Network module if there isn't already another better one.

agree with the other comments about the virtues of smaller, focused repos for the larger vis project. has anyone on this thread seen someone else actively working on the Network module on their own Vis.Js fork?

@micahstubbs

This comment has been minimized.

Copy link

micahstubbs commented Aug 23, 2018

ok, I'm doing it 😄

I've created a new github org visjs-community as a home for community maintained visjs forks and derivative projects. To get things started, I've invited all the people who have sent a PR to almdene/vis in 2018, along with some of the community members from this thread https://github.com/almende/vis/pulls.

These collaborators can review pull requests, curate issues, and create new visjs-community repos. I hope this is the start of something positive and new 🌱

https://github.com/visjs-community

screen shot 2018-08-22 at 5 17 22 pm

@micahstubbs

This comment has been minimized.

Copy link

micahstubbs commented Aug 23, 2018

my vision for this org is a home for all the good ideas and community contributions that are out there in limbo right now. I can imagine splitting the vis monolith into smaller, focused projects, like @yotamberk has already done with https://github.com/yotamberk/timeline-plus

we can also perhaps take inspiration from the transition that the library d3 went through recently from a monolith to many small modules.

https://github.com/d3
https://medium.com/@christopheviau/d3-js-modularity-d5eed78ba06e

@Jogai

This comment has been minimized.

Copy link
Author

Jogai commented Aug 23, 2018

Dividing this into modules was discussed here: #2405

Did you talk to @yotamberk about centralizing in a new org? Because its nice to have a central point, but that only works if everyone is onboard...

@mojoaxel

This comment has been minimized.

Copy link
Member

mojoaxel commented Aug 23, 2018

@micahstubbs Thanks for trying to help. Maybe an new organisation is not a bad idea! I see a few issues here:

First there is already an account visjs That would be perfect for that.
Now that is still very early can we use visjs instead of visjs-community? I could give you all access rights.

Also: We have this OpenCollective account. At the moment it is connected to the almende repository. We should try to move it the the community-account.

Thoughts?

@micahstubbs

This comment has been minimized.

Copy link

micahstubbs commented Aug 23, 2018

@mojoaxel, ah, that's good to know! I didn't find the visjs github account before. If we agree on the broad goals of

  1. reviewing/unblocking all the open PRs
  2. smaller modules (edit looking at this issue #2405 seems like the answer to this is yes 😄 )
  3. many collaborators to make 1) fast & easy

then I imagine we could collaborate over there. It would also be a big win if the good people at almende would be willing to transfer the existing main vis repo with all the issues over to the visjs org.

alternately, it could be useful to have both an official visjs org and a faster-moving, more flexible visjs-community org. this could be especially true if there are two distinct camps in the community today with respect to the stability vs development speed tradeoff.

@micahstubbs

This comment has been minimized.

Copy link

micahstubbs commented Aug 23, 2018

@Jogai yea, had some emails with @yotamberk a few weeks ago. he seemed focused on timesline-plus and open-minded about the direction of the rest of the project.

thanks for linking this modules issue - I had not found this one yet 😄 #2405

@avrahamcool

This comment has been minimized.

Copy link

avrahamcool commented Aug 28, 2018

@micahstubbs, @mojoaxel
the visjs account sounds good - it's still early and we should migrate to this account instead of creating a new community.

@mojoaxel good work on #2405, I think this should be the guiding stone for the migration.

I would also add tasks for updating the typescript types.
I already forked defently-typed to visjs-community, and pushed some minor fixes to the vis types.

I'm very interested in the graph2D/timeline part of vis, and I'm willing to contribute time and effort for the community.
but I currently stuck - I don't even know where to start.
I'm not very familiar with the current code-base so i don't want to do damage.

something that is missing from the new fork is a repo for the dataset/dataview and other common utilities.

also, if we can have some sort of manual guide on how to build and test the project - so we can know that we are not breaking anything while contributing.

@micahstubbs

This comment has been minimized.

Copy link

micahstubbs commented Aug 28, 2018

💯

also, if we can have some sort of manual guide on how to build and test the project - so we can know that we are not breaking anything while contributing.

@avrahamcool

This comment has been minimized.

Copy link

avrahamcool commented Aug 30, 2018

maybe it'll be beneficial to use tools like https://github.com/lerna/lerna for managing a mono repo of vis.

@Jogai

This comment has been minimized.

Copy link
Author

Jogai commented Aug 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment