Speed-up calender development

[evaarties]

Correct me if I’m wrong, but to me it feels like the development on the calendar and calendar resources management is more or less stalled. There are commits at

• GitHub - nextcloud/calendar_resource_management: Resources back-end for the Nextcloud CalDAV server · GitHub
• https://github.com/nextcloud/calendar

But most concern dependency upgrades.

What can we as a community do to help speed-up the development?

Personally, I really need those mail-less resources with auto acceptance of mettings.

[jtr]

@evaarties

is more or less stalled. There are commits at
[…]
But most concern dependency upgrades.

For what it’s worth, for the Calendar app, the changelog is maintained in the individual version branches not main. The actual changelogs are viewable in the app store and/or the latested published version branch.

Even after excluding dependency bumps and translation updates, looks pretty active, but I doubt anyone would be against further momentum.

Also, keep in mind that many “Calendar matters” aren’t necessarily part of the Calendar app, but associated with the CalDAV backend so those changes would flow through the nextcloud/server repo and changelog(s) instead..

What can we as a community do to help speed-up the development?

Personally, I really need those mail-less resources with auto acceptance of mettings.

• Help triage existing issues to free up developer time - e.g.
  • identify duplicate bug reports and link them
  • identify incomplete bug reports and request follow-up info
  • identify bug reports that are really support requests; redirect those reporters here to the forum to get community support (and then help them out) and/or to appropriate documentation (also see documentation improvements, below, since these types of Issues can also be signs of coverage or clarity gaps in the docs that can be used to identify doc improvement opportunities)
  • identify Calendar app bug reports that are associated with or really more CalDav (backend) oriented and more properly belong in the nextcloud/server repo (which has its own special CalDAV label for these matters)
  • test proposed code changes (unmerged pull requests) and provide feedback on results
• Propose documentation improvements to the User & Admin manuals in the sections that cover Calendar/CalDAV related matters - e.g.
  • Using the Calendar app — Nextcloud latest User Manual latest documentation
  • Calendar / CalDAV — Nextcloud latest Administration Manual latest documentation
• When mentioning specific matters such as “I really need those mail-less resources with auto acceptance of meetings”, include links to their respective Enhancement/Bug tracking Issues so others can see what you’re talking about.
• Upvote Issues you care about (on GitHub)
• If you’re part of an organization that is using Nextcloud: consider getting enterprise support via Nextcloud GmbH to help underwrite development in general or, if your org already has paid support, use appropriate enterprise specific channels to get your bugs/enhancements prioritized so everyone can ultimately benefit.

[evaarties]

• Thanks, that gives a lot of pointers :). Will have a look indeed. About those matters I’m talking about, those are:

• auto-accept Room Auto-Acceptance Not Working After Defining Resource in Nextcloud Calendar · Issue #192 · nextcloud/calendar_resource_management · GitHub

• no mailadress https://github.com/nextcloud/calendar_resource_management/issues/119

  • for this one, a calendar view for the room must be available too, so one can see a all bookings for a room ( https://github.com/nextcloud/calendar_resource_management/issues/194 ) . A workaround if you have a small number of rooms, is to create NextCloud accounts with the same mail address and share the calendar.

PS If you could give me some guidance for this, Issue · GitHub , I might be able to fix it.