| From: | James Keener <jim(at)jimkeener(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com> |
| Cc: | John R Pierce <pierce(at)hogranch(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Code of Conduct: Is it time? |
| Date: | 2016-01-06 16:42:30 |
| Message-ID: | 568D43F6.8060609@jimkeener.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> No, CoC by itself doesn't grow the community. That doesn't mean we
> shouldn't have one.
I'd agree with that. Thinking back over my previous points, it does make
sense to have one, if only to deal with people who represent the
community in some way, i.e. have some kind of commit or marketing access.
> Another weakness we have is the mentality that the only way to
> contribute to the community is as a developer.
Perhaps this is a separate issue from having a CoC.
Things like not having a bug tracker [1] prevent people from finding
issues to even be involved with, including the website, marketing, code,
tests, &c. That was 10 years ago and it's still the first result for
"Postgres bug tracker" on Google.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Anton | 2016-01-06 16:46:35 | Re: Code of Conduct: Is it time? |
| Previous Message | FarjadFarid(ChkNet) | 2016-01-06 16:25:08 | Re: Charging for PostgreSQL |