Bug Tracker
There was a side thread in the CoC thread about expanding the dev community
and making it easier for new devs to get involved. I would think that a bug
tracker, especially one where bugs can be labeled as "Newbie Friendly"
could go a long way towards that goal.
Additionally, a proper bug tracker would make it easier for future users to
find resolutions to issues.
Are there any technical reasons that the project doesn't use a bug tracker
(beyond pgsql-bugs)?
Jim
On 01/11/2016 11:18 AM, James Keener wrote:
There was a side thread in the CoC thread about expanding the dev
community and making it easier for new devs to get involved. I would
think that a bug tracker, especially one where bugs can be labeled as
"Newbie Friendly" could go a long way towards that goal.Additionally, a proper bug tracker would make it easier for future users
to find resolutions to issues.Are there any technical reasons that the project doesn't use a bug
tracker (beyond pgsql-bugs)?
on -hackers there is on an ongoing thread about this [1] but the long
and short is a: It is a culture issue. Warning, the thread has been
going on for almost 4 months.
JD
1.
/messages/by-id/CAG9n48_CoXd-8+nU6ri=Ht5pUD47JALyfCp=ztmcdoYcUvHLcA@mail.gmail.com
Jim
--
Command Prompt, Inc. - http://the.postgres.company/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
If your social views are from the Silicon Valley or The Bay, please
leave them there.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
"Joshua D. Drake" <jd@commandprompt.com> writes:
On 01/11/2016 11:18 AM, James Keener wrote:
Are there any technical reasons that the project doesn't use a bug
tracker (beyond pgsql-bugs)?
on -hackers there is on an ongoing thread about this [1] but the long
and short is a: It is a culture issue. Warning, the thread has been
going on for almost 4 months.
4 months? More like fifteen years. We actually *had* a bug tracker,
for a short while long ago, and it was an unmitigated failure (search
for "Keystone" in the archives, from mid-1999). The reason the longtime
hackers are suspicious of such proposals is it's not clear how to avoid
that fate the next time around. Anything we do has to adapt itself to
existing community habits, a lot more than vice versa, or it will go
down the tubes as well.
My own postmortem on that attempt is here:
/messages/by-id/9072.966741720@sss.pgh.pa.us
and the surrounding thread is well worth reading as well. Doesn't
really seem like the discussion has moved much since 2000 :-(
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 01/11/2016 12:07 PM, Tom Lane wrote:
"Joshua D. Drake" <jd@commandprompt.com> writes:
On 01/11/2016 11:18 AM, James Keener wrote:
Are there any technical reasons that the project doesn't use a bug
tracker (beyond pgsql-bugs)?on -hackers there is on an ongoing thread about this [1] but the long
and short is a: It is a culture issue. Warning, the thread has been
going on for almost 4 months.4 months? More like fifteen years.
The thread referenced is 4 months but you are absolutely correct :)
Sincerely,
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general