Ashutosh Bapat wrote:
> On Thu, Apr 12, 2018 at 6:27 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > Ashutosh Bapat wrote:
> >
> >> We use commitfest app for tracking the patches submitted. It has done
> >> well. Can we re-purpose the same for tracking open items?
> >
> > I think the rules are too different to cram both in the same place.
>
> What do you mean by same place? Can you please explain this a bit?
"Both in the same place" I meant both the CF items and the open items,
in a single place which is the commitfest app.
The commitfest app is designed with the commitfest workflow in mind.
There are rules about when items can be added, there are states that
correspond to patches being developed and discussed. Open items don't
follow the same rules. What I fear is that if we cram open items in the
commitfest app, we will loosen rules and break the workflow in some way
that will cause us pain when we're back to normal commitfest mode.
The other point is that we want additional annotations for open items.
What commit creates an open item (so we know which committer to blame),
when was it created, when did we last notify the committer, what commit
closed it. We don't have that in commitfest, and I bet there would be
an urge to add those eventually.
I was suggesting a different app because that app would implement
solutions for these somewhat different needs.
Now, maybe what you suggest for open items is to create a separate view
using much of the commitfest app code, say
https://commitfest.postgresql.org/openitems/NNN
I think that would probably work well.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
