Put RFCs into documentation
| From: | Laurent Laville | Date: | Fri, 01 May 2009 09:29:07 +0000 |
| Subject: | Put RFCs into documentation | ||
| Groups: | php.pear.webmaster | ||
| Request: | Send a blank email to pear-webmaster+get-6535@lists.php.net to get a copy of this message | ||
Hi PEAR web team,
While I hope to have at least one day the RFC included into PEAR doc, I wanted to open a report.
And today, while I read the "Reminder about open bugs in Documentation" in PEAR doc mailing list, I found an interesting entry
[1] Request #11198 Put RFCs into documentation
Second, and that is the other goal of my post today. Fix a bug that could help access to the list [2] provided by Christian (anchor uses)
I've noticed that attribute "id" lack value
<h3><a id="">A</a></h3>
<h3><a id="">C</a></h3>
<h3><a id="">D</a></h3>
etc...
We can have for example
http://pear.php.net/pepr/index.php?filter=finished#R
to go to
<h3><a id="R">R</a></h3>
While I was about to post a new bug report, I've noticed that there is an old one [3]
Bug #11200 Add html anchors for letters in proposal list
That was closed/fixed on [2007-06-09]. BUT we need to re-open it : it's no more fixed with current version of pearweb
And last but not least:
I vote +1 to have RFC into PEAR doc before it's request second anniversary !
It will avoid lot of people to search for info that were voted/Accepted long time ago, and not applied because they forgotten to search for additional doc.
Please
[1] http://pear.php.net/bugs/bug.php?id=11198
[2] http://pear.php.net/pepr/index.php?filter=finished
[3] https://pear.php.net/bugs/bug.php?id=11200