Hello, the Cyrus IMAP Development Process is described on two different places in two different ways:
At https://www.cyrusimap.org/overview/cyrus_bylaws.html#iv-development-process is stated that “The submitter of the code is responsible for ensuring that the code gets reviewed by the core developers.” Submitters of changes have absolutely no means to ensure that code gets reviewed, so they cannot be responsible for this. The procedure at https://www.cyrusimap.org/imap/developer/process.html suggests these steps: Create a pull request, wait for review (a quick note to the mailing list can speed this along). In October 2024 I published https://github.com/cyrusimap/cyrus-imapd/pull/5075 , which enhances the CalDAV Admin HTML page ( http://server/dav/calendars/user/localpart@domain/ ) by adding one more property (toggle to enable the server-side scheduling for a calendar). This feature can be currently anyway applied by issuing undocumented PROPPATCH requests. On 4 December I asked at devel@cyrus.topicbox.com if that change can be integrated. So far nothing happened, which suggests that the suggested process: “Create a pull request, then wait for review (a quick note to the mailing list can speed this along)” is not working. A clearer criteria whether the procedures described at https://www.cyrusimap.org/imap/developer/process.html do function, would be to announce also how long one has to wait. Two years, more than three years? Greetings Дилян ------------------------------------------ Cyrus: Devel Permalink: https://cyrus.topicbox.com/groups/devel/T4b8a7a5d201419b6-Mda79a3bc2b7d12a4fd77d885 Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
