search

jazzband / django-recurrence

Utility for working with recurring dates in Django.
https://django-recurrence.readthedocs.org/
BSD 3-Clause "New" or "Revised" License
486 stars 190 forks source link

Abandoned? #287

Open robd003 opened 1 year ago

robd003 commented 1 year ago

Is this project abandoned?

lino commented 9 months ago

This is a jazzband project. As I am using this library actively, I kinda try to maintain it, but as you know how things are, sometimes other things are more important or at least shout louder in your general direction.

thibaudcolas commented 1 month ago

@lino it seems you raised the release failure in #291 / https://github.com/jazzband/help/issues/355. Do you know if there’s been any movement on it since January?

As-is it seems the package is stuck without a way to publish releases to PyPI.

sheepman4267 commented 1 month ago

I'm also actively using this in multiple projects, and would be happy to share the load of maintaining the project.

boosh commented 3 weeks ago

Just dropping this here in case you want to add it to the docs or something. I needed support for times and #163 said it wasn't possible in this lib, so I've created an alternative: django-recurring. I'm still just testing it but check it out. It also supports counts and hourly intervals which I think are other shortcomings of this lib. It also allows creating ical calendar entries with multiple events and exclusion ranges.

I doubt I'll be much more responsive at maintaining it TBH. I needed to scratch my own itch. But if it could become the v2 of this lib perhaps it could be shunted into jazzband ownership once it's more mature.

lino commented 3 weeks ago

Well. The whole issue of ical and recurrence is very, very complex and I would really appreciate if the people who actively want to maintain libraries would concentrate their resources in a single project. But that's just my opinion.

boosh commented 3 weeks ago

Yeah I'd far rather that my lib became the v2 of django-recurrence. It solves a lot of outstanding issues (#116, #150, #155, etc) by supporting datetimes and provides several enhancements. However, it depends what any potential maintainers, etc. want.

Then again, this repo has < 500 stars and ~125k monthly downloads and an apparently broken release pipeline, so it may not be worth the hassle for people to upgrade...

lino commented 3 weeks ago

I'm working on resolving the outstanding issues, so if that's resolved, we can talk about how to proceed.

lino commented 3 weeks ago

Completely apart from the whole deployment issues thing, I would love to start planning for a v2 release, because it will allow us to remove some really janky behaviour of this library, but as breaking changes should not be unannounced, it needs some planning. I would really love to talk to you @boosh about what could be done for a v2.

boosh commented 3 weeks ago

Sure. I've created a discord server: https://discord.com/invite/EWTN65nN9f