Broaden ownership of dygraphs

[danvk]

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

• no blog posts in >1 year
• no major releases in >1 year (See Is Release 2.0 in near future, can we have some tentative dates ? #705)
• 150+ open issues
• many open PRs, including some long-standing ones

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]

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]

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]

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]

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

[klausw]

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]

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]

@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 #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 #678.

[danvk]

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

[LostInBrittany]

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 #775

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

[reinert]

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 #775

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#727 (comment),
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
#727 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABOddpcTeYXGcO-X5GzCaREdY5qSMXx4ks5qqUocgaJpZM4HVvmn
.

Danilo Reinert

[danvk]

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

[LostInBrittany]

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
#727 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAsVzO1Qh0bHudY4q2G2rHmIGXhqMfdKks5qqYC-gaJpZM4HVvmn
.