On 04/11/2018 10:06 AM, Alvaro Herrera wrote:
> Andres Freund wrote:
>> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
>>> The other proposal was that we could have a simple web app to track open
>>> items. After all, we now know what we need from it. A wiki page seems
>>> more laborious. (The commitfest app also sprung from a wiki page.)
>>
>> Growing a number of non-issue issue trackers...
>
> Yes, because the generic ones are confusing, hard to search, easy to
> misuse, easy for things to get lost, easy for dupes to crop up --- easy
> for things go wrong all over the place.
Just like now except at least with an issue tracker it is easy to move
items from one place to another, assign ownership and track what is
actually going on.
>
> The dedicated apps have a very limited purpose and work the way we want,
> avoiding all these problems: in essence, they are but a glorified
No, they work the way you want which in turn creates an ever higher
barrier of entry for new community members.
> We've had wiki pages for open items for 10 years now. It's gotten
> boring and tiresome.
> https://wiki.postgresql.org/wiki/Category:Open_Items
At least with an issue tracker it would be easy to see and know what is
going on there.
jD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*** A fault and talent of mine is to tell it exactly how it is. ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****