philip Wed Jun 4 13:19:27 2003 EDT
Modified files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:
more random additions.
Index: phpdoc/RFC/2003_meeting_agenda.html
diff -u phpdoc/RFC/2003_meeting_agenda.html:1.5 phpdoc/RFC/2003_meeting_agenda.html:1.6
--- phpdoc/RFC/2003_meeting_agenda.html:1.5 Tue Jun 3 04:26:58 2003
+++ phpdoc/RFC/2003_meeting_agenda.html Wed Jun 4 13:19:27 2003
@@ -68,7 +68,7 @@
<div class="content">
<h1>PHP Documentation Meeting 2003 - Agenda</h1>
- <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.5 2003/06/03 08:26:58
philip Exp $</p>
+ <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.6 2003/06/04 17:19:27
philip Exp $</p>
<p>Members of the PHP Documentation Team <a title="meeting protocol"
href="http://www.php-ev.de/documents/phpdoc/protocol.html";>met in 2002
@@ -159,6 +159,9 @@
<li>Human based inclusion or machine based?</li>
<li>Who should decide on license questions?</li>
<li>What to do with the inactive contributors?</li>
+ <li>What names/titles exist for those that contribute?
+ Helper, Author, Editor, Technical Editor, etc.
+ And how are they defined?</li>
</ul>
</div>
@@ -197,6 +200,10 @@
<li>What impact would a WYSIWYG editing method has on
our diffing+mailing system, as WYSIWYG editors are known
to 'rewrite' files, and produce useless diffs</li>
+ <li>Where will the required diff -u and make test commands
+ be executed? People really need to check these before
+ any commit is done and we don't have the resources to
+ execute these for everyone (or do we?)</li>
</ul>
</div>
@@ -224,11 +231,19 @@
request it, and in what form [eg. without email addresses to prevent
further mass email harvesting].</p>
+ <p>Long ago there was discussed (and even commited code) about a
system
+ that allows people (anyone, with or without CVS accounts) to
"maintain"
+ a manual pages notes. For example, Joe would manage the strlen()
+ notes. Not to say only Joe could edit them but Joe would at least
focus
+ on this page and/or other pages.</p>
+
<div class="seealso">
See also: <a href="http://gtk.php.net/manual/en/";>the PHP-GTK
manual</a> for some ideas on how the rating works there, and
the <a
href="http://www.php-ev.de/documents/phpdoc/protocol.html";>2002
meeting protocol</a> on the user note related findings there.
+ Also, the <a
href="http://marc.theaimsgroup.com/?l=phpdoc&m=99618446902193";>notes
+ maintainer proposal</a>.
</div>
</li>
<li>
@@ -530,7 +545,8 @@
presentation of the online and offline manuals. Manual search
solutions, PHP source code highlighting, better table of
contents, indexes and other stuff would greatly add to the user
- experience.</p>
+ experience. Also, one should be able to search both peardoc
+ and phpdoc manuals through one interface (ex. php.net/sqlite)</p>
<p>The extended CHM is the best version for onscreen browsing
on Windows. We should build on it's experience and add new
@@ -570,6 +586,8 @@
<ul>
<li>Do we need translation support for the Internals
Manual?</li>
<li>Should it sit in the phpdoc CVS module?</li>
+ <li>PECL internals are also affected, so this Internals
Manual
+ should cover both?</li>
<li>How to integrate it with the build system?</li>
</ul>
</div>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
