New release or mark obsolete and redirect people to fullcalendar_view?

+1 I second this. This really needs some kind of alpha release soon.

Seconded - this module looks to still be progressing along faster towards a stable version than the "calendar" module, and I'd love to see a recent alpha with the latest patches applied.

FYI, I'm currently using fullcalendar_view, a 3rd D8 calendar module that actually seems to work right now and has official releases.

It's sad when these sorts of efforts get fragmented like this. I wish everyone could contribute to the same project, both to avoid confusion for site builders when selecting a module in the first place, and to concentrate all the support, code, review and testing contributions in one place.

Would the maintainer(s) of this module consider merging projects? Mark this one "obsolete" and point folks over to fullcalendar_view?

Thanks,
-Derek

Agreed. I mentioned this idea in the other 2 upgrade trackers.

We've fully transitioned to fullcalendar_view now, primarily because of some fundamentally flawed changes to this module. Two completely redundant and overlapping modules. This is bad Drupal practice, folks.

At the very least, I'd propose drafting a pro/con comparison chart of the 3 options - what basic/extended features does each provide, what resources are used (FC & FCV use js, my understanding is regular Calendar does not), any noticeable differences in performance (i.e., between anon and logged in users), etc.

This might also help in highlighting where to consolidate efforts with people looking to donate development time to a project.

Hi All. MIA module maintainer here.

I share your frustrations on the situation with this project. When I took over, I needed FC for a project I was working on. Then the situation changed and I moved on to other things. During the lack of activity on the Drupal module, I did some work, briefly, for Fullcalendar itself so I didn't totally forget about this project. Then not too long ago, I needed to become more active and have been.

A lot has taken place in both Fullcalendar and Drupal projects and we now have a couple of versions to work with. Fullcalendar introduced major breaking changes in version 4 and a new architecture to the library. The main change is the removal of jQuery as a dependency. In addition, many settings and callbacks have been removed, renamed or reworked. See https://fullcalendar.io/docs/upgrading-from-v3

Then there's the new version 5, currently in beta which has introduced additional major breaking changes along with new features. See https://fullcalendar.io/docs/v5/upgrading-from-v4

So our Drupal integration now has to provide support for at least v4 and v5 of Fullcalendar.

Drupal Fullcalendar 8.x-1.x will continue to support Fullcalendar 3.9.0 (with Drupal 9 compatibility)

I have created a new 8.x-2.x branch for Fullcalendar version 4 with some code that provides basic functionality, including displaying events from Google Calendar. Most Fullcalendar settings are configurable in Drupal. Please take a look and let's talk :-)

I intend to support Fullcalendar 5 in a separate 8.x-3.x branch but haven't started yet.

Hi @dakala, nice to hear from you, and thanks for the update.

I believe the question of merging efforts and d.o projects is still valid, regardless of changes to the upstream library. What do you think about that?

Thanks!
-Derek

Hi @dww. Of course merging efforts is the right way to go. The first release of Fullcalendar was way back in September 2010 for Drupal 6 and there's been releases for D7 and D8 at different times. Perhaps the Fullcalendar View maintainers should have reached out and collaborated on this project? A couple of people have helped out over the years since I took over.

@dakala: While we can't do anything about that now, if that's a more active project, might it make more sense for you to spend your efforts there (or even on the original Calendar module) rather than continue to work on this one? Is this something to consider? Otherwise, we'll still have 3 different groups of people working on three different projects, which is significantly dividing momentum.

And yes, it perfectly valid to ask the other folks the same question. Perhaps coordinating a discussion among all of the project maintainers would be a good place to start? See who needs help wherever, and try to coordinate?

I really don't believe that 3 barely-chugging-along projects is serving the community well when there are opportunities for getting one (or even two, if it makes sense) of them into a polished state.

@colan: Well, it always helps to talk. AFAICT, Calendar offers something different from Fullcalendar & Fullcalendar View which is an integration with a 3rd-party JavaScript solution.

Development has restarted on this module and version 3 was released.