| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Policies -> Website patch |
| Date: | 2019-02-07 20:46:44 |
| Message-ID: | DECDB508-D58C-4C65-8872-D50E353DEB66@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> On 6 Feb 2019, at 17:53, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> OK to go on the patch?
A few comments:
+ <li>Accurate contact information
Lacks an ending </li> tag
+<ul>
+ <li>Each listing must include:
+ <ul>
+ <li>Specific locations and dates for that specific training</li>
Can’t the “Each listing must include” heading be included in the previous
paragraph to avoid the nested list?
+ href="http://blog.2ndquadrant.com/planetary_alignment/“>Planetary
This URL will redirect to https, so we might as well link to that directly.
+ href="http://www.postgresql.org/community/contributors/“>PostgreSQL
Use https URL
+<h1>Professional Services and Hosting Approval Policy <i
+ class="fas fa-gavel"></i></h1>
Please avoid linebreaking the tag, it makes for poor readability.
+ <li>Use of Postgresql.org, its mailing lists, or associated forums and
Lowercase ‘postgresql.org’ for consistency?
+The PostgreSQL Community Association of Canada has designated the PostgreSQL Core Team to be its authoritative agent in most matters regarding
Should be in <p> .. </p>
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2019-02-08 11:35:25 | Re: Policies -> Website patch |
| Previous Message | Stephen Frost | 2019-02-07 11:45:07 | Re: mailing list redirect for bug numbers? |