You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pouchdb.apache.org by Jan Lehnardt <ja...@apache.org> on 2025/12/09 11:36:22 UTC
Periodic Issue Triage Meeting
Hey all,
on Monday we did an impromptu issue-triage meeting in Slack.
The results speak for themselves:
Before:
- issues: 152 open
- pulls: 40 open
After:
- issues: 132 open
- pulls: 37 open
\o/
—
I suggest we make this an institution starting with the new year.
Given the distributed nature of the team, we will have to juggle
time zones a bit. As such I suggest we have two dates with rotating
time slots:
- Every second Monday of the month, 8–9a UTC
- Every fourth Monday of the Month, 3-4p UTC
This won’t cover everyone and I am happy to move things around as
needed.
As for process, we just picked issues and PRs alternating
from the end and the beginning and briefly discussed what needs
doing (close with reason, keep open for later, merge (PRs), or
open PR to close (issue).
I’m happy to send reminders on here and in Slack on the Friday
before so we can make sure at least two folks are around, so
it is more fun.
It’d be nice you any one of you could attend at least one of
these per month, if you can :)
Best
Jan
—
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
24/7 Observation for your CouchDB Instances:
https://opservatory.app
SQL Queries for CouchDB:
https://neighbourhood.ie/products-and-services/structured-query-server
Re: Periodic Issue Triage Meeting
Posted by Jan Lehnardt <ja...@apache.org>.
Progress! :)
• Issues 127 (-7)
• PRs (29 soon) (-1)
Best
Jan
—
> On 26. Feb 2026, at 15:05, Jan Lehnardt <ja...@apache.org> wrote:
>
> The next meeting is on Monday, March 2nd, 15:00–16:00 UTC
>
> —
>
>
>> On 13. Feb 2026, at 17:14, Jan Lehnardt <ja...@apache.org> wrote:
>>
>> The next meeting is this coming Monday, Feb 16th, 8-9a UTC
>>
>> Best
>> Jan
>> —
>>
>>
>>> On 10. Dec 2025, at 07:10, Alex Anderson <al...@apache.org> wrote:
>>>
>>> On 2025/12/09 11:36:22 Jan Lehnardt wrote:
>>>
>>>> I suggest we make this an institution starting with the new year.
>>>> Given the distributed nature of the team, we will have to juggle
>>>> time zones a bit. As such I suggest we have two dates with rotating
>>>> time slots:
>>>>
>>>> - Every second Monday of the month, 8–9a UTC
>>>> - Every fourth Monday of the Month, 3-4p UTC
>>>
>>>
>>> Count me in. These times work well for me.
>>>
>>> For Jan 2026 I think this would be:
>>>
>>> * 2026-01-12 0800Z
>>> * 2026-01-26 1500Z
>>>
>>> Cheers,
>>>
>>> Alex
>>
>
Re: Periodic Issue Triage Meeting
Posted by Jan Lehnardt <ja...@apache.org>.
The next meeting is on Monday, March 2nd, 15:00–16:00 UTC
—
> On 13. Feb 2026, at 17:14, Jan Lehnardt <ja...@apache.org> wrote:
>
> The next meeting is this coming Monday, Feb 16th, 8-9a UTC
>
> Best
> Jan
> —
>
>
>> On 10. Dec 2025, at 07:10, Alex Anderson <al...@apache.org> wrote:
>>
>> On 2025/12/09 11:36:22 Jan Lehnardt wrote:
>>
>>> I suggest we make this an institution starting with the new year.
>>> Given the distributed nature of the team, we will have to juggle
>>> time zones a bit. As such I suggest we have two dates with rotating
>>> time slots:
>>>
>>> - Every second Monday of the month, 8–9a UTC
>>> - Every fourth Monday of the Month, 3-4p UTC
>>
>>
>> Count me in. These times work well for me.
>>
>> For Jan 2026 I think this would be:
>>
>> * 2026-01-12 0800Z
>> * 2026-01-26 1500Z
>>
>> Cheers,
>>
>> Alex
>
Re: Periodic Issue Triage Meeting
Posted by Jan Lehnardt <ja...@apache.org>.
The next meeting is this coming Monday, Feb 16th, 8-9a UTC
Best
Jan
—
> On 10. Dec 2025, at 07:10, Alex Anderson <al...@apache.org> wrote:
>
> On 2025/12/09 11:36:22 Jan Lehnardt wrote:
>
>> I suggest we make this an institution starting with the new year.
>> Given the distributed nature of the team, we will have to juggle
>> time zones a bit. As such I suggest we have two dates with rotating
>> time slots:
>>
>> - Every second Monday of the month, 8–9a UTC
>> - Every fourth Monday of the Month, 3-4p UTC
>
>
> Count me in. These times work well for me.
>
> For Jan 2026 I think this would be:
>
> * 2026-01-12 0800Z
> * 2026-01-26 1500Z
>
> Cheers,
>
> Alex
Re: Periodic Issue Triage Meeting
Posted by Alex Anderson <al...@apache.org>.
On 2025/12/09 11:36:22 Jan Lehnardt wrote:
> I suggest we make this an institution starting with the new year.
> Given the distributed nature of the team, we will have to juggle
> time zones a bit. As such I suggest we have two dates with rotating
> time slots:
>
> - Every second Monday of the month, 8–9a UTC
> - Every fourth Monday of the Month, 3-4p UTC
Count me in. These times work well for me.
For Jan 2026 I think this would be:
* 2026-01-12 0800Z
* 2026-01-26 1500Z
Cheers,
Alex