search

danvk / dygraphs

Interactive visualizations of time series using JavaScript and the HTML canvas tag
http://dygraphs.com
Other
3.17k stars 605 forks source link

Broaden ownership of dygraphs #727

Open danvk opened 8 years ago

danvk commented 8 years ago

dygraphs is a popular project, but lately it hasn't been getting the amount of work it deserves:

I don't expect to have much time to spend on dygraphs in the near future. @kberg isn't likely to, either. @pshevtsov has expressed interest in getting more involved. If you're a contributor who's interested in becoming a collaborator or owner, now would be a great time!

Recent contributors who might be interested: @timeu @kbaggott @reinert @mjanda @sslepian @cthrax

The next step for dygraphs is to get a 2.0.0 release out which incorporates the many improvements which have been made over the past year. If you're interested in helping out, please either respond on this issue or shoot me an email.

timeu commented 8 years ago

I am also quite busy but I wouldn't mind helping out with the release (althogh I don't know the details of the process) and if there is time in between fixing bugs.

danvk commented 8 years ago

I've added @pshevtsov and @timeu as collaborators. The more the merrier! There's a 2.0.0 milestone with a few easy bug fixes, and of course the giant backlog of 160 open issues. Please still send PRs for anything you'd like to fix.

kbaggott commented 8 years ago

I'm not very experienced in writing tests but more than happy to help with issues and new features as and when I have time?

danvk commented 8 years ago

@kbaggott I've added you, too. Help dealing with issues (especially closing out invalid issues and dupes) would be greatly appreciated.

klausw commented 8 years ago

I can't currently commit to any ongoing development work, though I do want to stay in the loop for areas related to code I've been working on. Unfortunately our internal repository has stopped tracking upstream due to alleged incompatibilities. I'll try to sort out what's going on there, but I may be stuck with backporting fixes on a case-by-case basis, and that's obviously not a good situation for making contributions.

LostInBrittany commented 8 years ago

If you still need people to help, please add me, I use Dygraph in some critical projects for my company and I really want to see it going forward...

danvk commented 8 years ago

@LostInBrittany thanks for the kind offer. The best thing to do is send a PR to fix some issue on the 2.0.0 milestone (perhaps https://github.com/danvk/dygraphs/issues/669?). I'll review it and then we can get you added.

I would like to do a 2.0.0 release candidate soon. The only real remaining TODO is https://github.com/danvk/dygraphs/pull/678.

danvk commented 8 years ago

@LostInBrittany or just a PR for your own issue :) #775

LostInBrittany commented 8 years ago

I'm digging on it... :)

On Thu, Sep 15, 2016 at 3:31 PM, Dan Vanderkam notifications@github.com wrote:

@LostInBrittany https://github.com/LostInBrittany or just a PR for your own issue :) #775 https://github.com/danvk/dygraphs/issues/775

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danvk/dygraphs/issues/727#issuecomment-247328500, or mute the thread https://github.com/notifications/unsubscribe-auth/AAsVzJd2Ko0PQdCL-wgqOiDDfHHeQuVoks5qqUjOgaJpZM4HVvmn .

reinert commented 8 years ago

It's good to know who is working in what. So two people don't waste effort on the same issue.

Em qui, 15 de set de 2016 às 10:37, Horacio Gonzalez < notifications@github.com> escreveu:

I'm digging on it... :)

On Thu, Sep 15, 2016 at 3:31 PM, Dan Vanderkam notifications@github.com wrote:

@LostInBrittany https://github.com/LostInBrittany or just a PR for your own issue :) #775 https://github.com/danvk/dygraphs/issues/775

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danvk/dygraphs/issues/727#issuecomment-247328500, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAsVzJd2Ko0PQdCL-wgqOiDDfHHeQuVoks5qqUjOgaJpZM4HVvmn

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danvk/dygraphs/issues/727#issuecomment-247329972, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOddpcTeYXGcO-X5GzCaREdY5qSMXx4ks5qqUocgaJpZM4HVvmn .

Danilo Reinert

danvk commented 8 years ago

@reinert sure! If anyone is working on an issue, they should leave a comment on it or assign it to themselves.

LostInBrittany commented 8 years ago

I'm trying to find a solution, but I'm rather new to the code of Dygraphs (I've been using it for a year or two, but I have begun to look at its code this week), so I don't considerer myself competent enough to assign the bug to myself, as I'm not sure to be able to find the cause in a raisonnable time span...

On Thu, Sep 15, 2016 at 7:30 PM, Dan Vanderkam notifications@github.com wrote:

@reinert https://github.com/reinert sure! If anyone is working on an issue, they should leave a comment on it or assign it to themselves.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/danvk/dygraphs/issues/727#issuecomment-247395655, or mute the thread https://github.com/notifications/unsubscribe-auth/AAsVzO1Qh0bHudY4q2G2rHmIGXhqMfdKks5qqYC-gaJpZM4HVvmn .

mirabilos commented 1 year ago

I did it.

I fixed bugs, converted this to Babel 7 (because that’s the version currently in Debian unstable), de-npm-ified the build process some (but it still works with npm, and I test this using GitHub Actions because Travis-CI doesn’t hand out new credits), created a Debian package and uploaded it (it’s currently pending ftpmaster review as it’s a NEW package).

I guess I could also push v2.1.1 to NPM to fix things like https://github.com/danvk/dygraphs/issues/1027 which users experience. I have no idea where the CDN takes its data from, though, so if there are any additional steps to take after npm publish (which would require you to add me first though), please enlighten me.

I’m very much not a JavaScript developer, and I especially do not know many of the new things in ES6, but I plan on using this for a project and keeping it alive and working in Debian. I don’t have enough skill to judge all the pull requests that there currently are, but I guess, if you’ll have me, a little palliative maintenance is better than none? It helps that I like to keep compatibility to older browsers alive (I have an experimental Leaflet application that works with Opera 9 except for the local File API which did not exist back then but is only an optional gimmick).

My strengths do lie with systems administration, (Korn) shell programming, Open Source stuff like licence analysis, packaging, etc. so co-maintainers that know a bit more about the web world are probably welcome. (I know my way around Python, even if I don’t personally like it.)

That is, again, if @danvk will have me.

https://github.com/mirabilos/dygraphs and I even put up a “live view” of that under https://dygraph.github.mirsolutions.de/ via GitHub Pages which fixes some of the annoying bugs like navigation not working, too. This is even included (fully workable!) in the Debian package.

danvk commented 1 year ago

Hi @mirabilos -- if you've gotten all those changes working then I'd say you're definitely a JavaScript developer :) I'll follow up with you over email about dygraphs maintenance.