| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, tomas(dot)vondra(at)2ndquadrant(dot)com, James Keener <jim(at)jimkeener(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, dpage(at)postgresql(dot)org |
| Subject: | Re: Code of Conduct |
| Date: | 2018-09-18 18:35:54 |
| Message-ID: | 19456.1537295754@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> I would ask that you, and anyone else who has a suggestion for how to
> improve or revise the CoC, submit your ideas to the committee by
> email'ing coc(at)postgresql(dot)org(dot)
> As was discussed previously, the current CoC isn't written in stone and
> it will be changed and amended as needed.
The change process is spelled out explicitly in the CoC document.
I believe though that the current plan is to wait awhile (circa 1 year)
and get some experience with the current version before considering
changes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | VENKTESH GUTTEDAR | 2018-09-18 18:37:37 | [GENERAL] optimising the pl/pgsql function |
| Previous Message | Stephen Frost | 2018-09-18 17:14:30 | Re: Code of Conduct |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2018-09-18 18:40:16 | Re: Code of Conduct |
| Previous Message | David Steele | 2018-09-18 17:52:03 | Re: Online verification of checksums |