Opened 12 years ago
Closed 12 years ago
#176 closed enhancement (fixed)
rfc 5
| Reported by: | sheppard | Owned by: | EliL |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Docs | Version: | |
| Keywords: | rfc | Cc: |
Description (last modified by )
Attached is a patch for a proposed RFC 5 (plus some spelling corrections to the RFC TOC). I have built this against sphinx and it seems to be working. If everything looks good, can someone commit this? I can then send out a note to the mailing list (or does a PSC member need to do it?).
Attachments (2)
Change History (5)
by , 12 years ago
| Attachment: | rfc-4.patch added |
|---|
comment:1 by , 12 years ago
| Description: | modified (diff) |
|---|---|
| Status: | new → assigned |
| Summary: | rfc 4 → rfc 5 |
RFC-4 has already been discussed on the psc list, http://lists.osgeo.org/pipermail/geomoose-psc/2012-November/000058.html so I renamed this RFC-5. I will make appropriate changes in the patch too.
Also note that RFC-3 has a status of development so it has not yet been adopted and is not in effect and could change.
I'll get this committed by early tomorrow. There is no requirement about who starts discussion on the list, calling for a vote is likely to be done by a PSC member and only after two days after notice of the RFC on the website.
comment:2 by , 12 years ago
| Status: | assigned → testing |
|---|
r975 should show up on the trunk website shortly.
RFC 4 and TOC spellcheck