Skip to content
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

Project status - we're alive! #177

Closed
emauricio opened this issue Jul 5, 2017 · 8 comments
Closed

Project status - we're alive! #177

emauricio opened this issue Jul 5, 2017 · 8 comments

Comments

@emauricio
Copy link

Hi there,
Just simple question, is the project still alive? :)
seems like a long time since last update.

@carlholloway
Copy link
Contributor

Hi @emauricio

Yes! moment-range is very much alive. After many years of awesome work, @gf3 unfortunately no longer has time to maintain the project. We (here at Rotaready) are super excited and humbled to be taking on responsibility as of yesterday.

Over the coming days we'll start reviewing the issues and pull requests. We'll fix any bugs as a priority and then look at enhancements to ensure moment-range remains the best moment plugin for date range manipulation. We've had a long chat with @gf3 to ensure we follow his long term vision for the library going forwards.

If anyone has any feedback, please feel free to use this thread to put your thoughts across to us.

Cheers!

@carlholloway carlholloway changed the title [question] Project status Project status - we're alive! Jul 6, 2017
@emauricio
Copy link
Author

as suggestion or idea.... will be nice if the project come by default with the ".d.ts" for typescript projects, i think it should be easy to create or maintain since this project already is using flow.

@AndreSteenveld
Copy link
Contributor

AndreSteenveld commented Jul 19, 2017

@carlholloway Selfishly I'm here to ask if some of the PR's can be merged and what the plans are for the near future to keep the project running (merging/declining the PRs, dealing with the issues, etc). Is there anywhere that I (as a mere mortal ;) can get some information about the long term vision?

@carlholloway
Copy link
Contributor

carlholloway commented Jul 20, 2017

@AndreSteenveld Hey! We're on it :) There are many issues and PRs so at the moment it's a case of prioritisation and getting up to speed with it all.

My aim is to get all the small fixes and quick wins rolled into a minor release over the next week or so. The bigger improvements will follow (our plan is to follow @gf3's lead and use "next version" branches to track longer running feature development so you can all test out new ideas and give feedback etc.)

PS thank you for your PRs!

@AndreSteenveld
Copy link
Contributor

@carlholloway If there is anything I can do I'd like to contribute 4~6 hours in the next few weeks.

@sandstrom
Copy link

sandstrom commented Aug 1, 2017

Awesome to see this rejuvenated!

Personally I'd be thrilled to see nice formatting of time ranges: #131

@Rosensweig
Copy link

Hi everyone! Glad to see this is being updated again.

I'm currently using moment-range to manipulate time for a scheduling app I'm creating. In the process, I've written functions to add and subtract arrays of time ranges (like a whole list of GCal events from their API). It wouldn't take much adaptation to make them a part of the whole package, rather than my own separate functions. I think it would be useful functionality for others, so I'd like to contribute that.

I'd also like to modify the add() function to allow adjacent as an option (just like the overlaps() function does). I had to create my own add function (for just two ranges) in the process of creating functionality to add arrays of ranges, because yours didn't include this. I think it should be at least an option to add, say 2-4 PM and 4-5 PM, and get back 2-5 PM rather than null. (Maybe even the default behavior if I were coding from scratch, but since people are already using it with existing behavior, making it an option is less likely to break existing code.)

Since you have a backlog of pull requests right now, would it make sense to wait a little bit before doing that, until you've handled some of the more pressing ones? It might avoid unnecessary merge conflicts, if I went in after those had been done.

@gf3 gf3 self-assigned this Mar 5, 2018
@gf3
Copy link
Contributor

gf3 commented Apr 16, 2018

moment-range has been on a steady release schedule for quite some time now. check out the newly released 4.0.0! closing this issue for now. thanks everyone

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

No branches or pull requests

6 participants