On Thu, Jan 7, 2016 at 6:30 PM, Jeff Janes <jeff.ja...@gmail.com> wrote:
> I don't completely agree with that.  I have often wanted to know when
> a specific item was added to the TODO page, and/or its individual edit
> history.

Sure, there might be other things it would be better at. But my point
is that it would have the same problem as the wiki in that it would
accumulate vague ideas that someone thought was a good idea once but
didn't have a good idea how to implement or a compelling argument that
convinced others to work on it.

The wiki is the lowest overhead and highest visibility way of
maintaining communal information. Bug trackers exist to impose extra
structure to match an intended workflow. That's fine for bugs or a
closely managed project but it's the last thing you want if you're
trying to get more people to contribute. The whole selling points of
wikis is that they draw in contributors because anyone can edit

This really sounds like you're looking for leverage to fix one problem
by finding other problems that you hope to solve with the same hammer.
That's a recipe for a tool that solves neither problem well and gets
ignored by the both sets of users.


Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to