Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

cvs: phpdoc /RFC 2003_meeting_agenda.html

1 view
Skip to first unread message

Gabor Hojtsy

unread,
May 31, 2003, 7:19:46 AM5/31/03
to php...@lists.php.net
goba Sat May 31 07:19:46 2003 EDT

Added files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:
Adding first version of the 2003 phpdoc meeting agenda.
Please don't fix the whitespace and discuss every major
modification

goba-20030531071946.txt

Gabor Hojtsy

unread,
Jun 1, 2003, 11:51:17 AM6/1/03
to php...@lists.php.net
goba Sun Jun 1 11:51:17 2003 EDT

Modified files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:
Add Christian...

Index: phpdoc/RFC/2003_meeting_agenda.html
diff -u phpdoc/RFC/2003_meeting_agenda.html:1.1 phpdoc/RFC/2003_meeting_agenda.html:1.2
--- phpdoc/RFC/2003_meeting_agenda.html:1.1 Sat May 31 07:19:46 2003
+++ phpdoc/RFC/2003_meeting_agenda.html Sun Jun 1 11:51:17 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.1 2003/05/31 11:19:46 goba Exp $</p>
+ <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.2 2003/06/01 15:51:17 goba 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
@@ -108,6 +108,7 @@
<li>Richter, <strong>Georg</strong> [maybe only partial]</li>
<li>Schroder, <strong>Kai</strong></li>
<li>Schumann, <strong>Sascha</strong></li>
+ <li>Stocker, <strong>Christian</strong></li>
<li>Weinert, <strong>Thomas</strong></li>
<li>Zic, <strong>Sandro</strong></li>
</ul>


Gabor Hojtsy

unread,
Jun 2, 2003, 12:24:16 PM6/2/03
to php...@lists.php.net
goba Mon Jun 2 12:24:16 2003 EDT

Modified files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:

Hakan is also coming...

Index: phpdoc/RFC/2003_meeting_agenda.html
diff -u phpdoc/RFC/2003_meeting_agenda.html:1.2 phpdoc/RFC/2003_meeting_agenda.html:1.3
--- phpdoc/RFC/2003_meeting_agenda.html:1.2 Sun Jun 1 11:51:17 2003
+++ phpdoc/RFC/2003_meeting_agenda.html Mon Jun 2 12:24:16 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.2 2003/06/01 15:51:17 goba Exp $</p>
+ <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.3 2003/06/02 16:24:16 goba 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

@@ -103,6 +103,7 @@
<li>Hojtsy, <strong>Gabor</strong> [aka Goba]</li>
<li>Holzgraefe, <strong>Hartmut</strong></li>
<li>Kronsbein, <strong>Mark</strong></li>
+ <li>Kuecuekyilmaz, <strong>Hakan</strong></li>
<li>Lerdorf, <strong>Rasmus</strong></li>
<li>Rethans, <strong>Derick</strong></li>

Philip Olson

unread,
Jun 3, 2003, 4:06:00 AM6/3/03
to php...@lists.php.net
philip Tue Jun 3 04:06:00 2003 EDT

Modified files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:

Added "What do do with PHP3 Documentation"


Index: phpdoc/RFC/2003_meeting_agenda.html
diff -u phpdoc/RFC/2003_meeting_agenda.html:1.3 phpdoc/RFC/2003_meeting_agenda.html:1.4
--- phpdoc/RFC/2003_meeting_agenda.html:1.3 Mon Jun 2 12:24:16 2003
+++ phpdoc/RFC/2003_meeting_agenda.html Tue Jun 3 04:06:00 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.3 2003/06/02 16:24:16 goba Exp $</p>
+ <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.4 2003/06/03 08:06:00 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

@@ -499,6 +499,22 @@

<div class="seealso">
I don't know of any material to put here...
+ </div>
+ </li>
+ <li>
+ <h3>What do do with PHP3 documentation</h3>
+
+ <p>In an effort to preserve history and possible PHP3 users, we need
+ to keep this information available but at the same time it adds
+ clutter to the documentation. One proposal is to list all PHP3
+ information in its own appendix, and add appropriate links/notes
+ to them. Within a manual page, one will see a simple link titled
+ "PHP3 Note" and it'll link to the appropriate location in the "PHP3
+ Appendix". In here it might mention a feature was added in PHP3, etc.
+ Most people seemed to like this idea, no specifics have been discussed.</p>
+
+ <div class="seealso">
+ <a href="http://marc.theaimsgroup.com/?l=phpdoc&m=104328040919058">Proposal summary</a>
</div>
</li>
<li>


Philip Olson

unread,
Jun 3, 2003, 4:26:59 AM6/3/03
to php...@lists.php.net
philip Tue Jun 3 04:26:59 2003 EDT

Modified files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:

Added some PHP 5 / PECL information.


Index: phpdoc/RFC/2003_meeting_agenda.html
diff -u phpdoc/RFC/2003_meeting_agenda.html:1.4 phpdoc/RFC/2003_meeting_agenda.html:1.5
--- phpdoc/RFC/2003_meeting_agenda.html:1.4 Tue Jun 3 04:06:00 2003
+++ phpdoc/RFC/2003_meeting_agenda.html Tue Jun 3 04:26:58 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.4 2003/06/03 08:06:00 philip Exp $</p>
+ <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.5 2003/06/03 08:26:58 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

@@ -482,23 +482,29 @@
increasingly ready for a copy-paste move of the docs of those extensions
[having all extension related docs at one place]. But it is still not
decided whether all moved extensions' docs should move to PECL docs,
- or leave some at phpdoc.</p>
+ or leave some (like the bundled extensions) at phpdoc.</p>

<p>It is also important to maintain some consistency in moved docs.
Eg. have a listing of removed extensions, make the URL shortcuts
redirect to the PECL manual, move / remove the user notes related
- to those extensions, etc.</p>
+ to those extensions, etc. Also, before anything is officially moved
+ out of phpdoc, it should be available online in the peardoc manual.</p>

<div class="points">
Some important questions:
<ul>
<li>How / when to document PHP 5 features?</li>
<li>What extensions will be moved to PECL and when?</li>
+ <li>Is it true that every extension will be moved into PECL, but most still bundled?</li>
+ <li>Will peardoc/PECL continue to use our old extension.xml format? This makes moving more difficult.</li>
</ul>
</div>

<div class="seealso">
- I don't know of any material to put here...
+ <a href="http://marc.theaimsgroup.com/?l=phpdoc&m=103856748014419">Some ideas</a>,
+ <a href="http://cvs.php.net/co.php/phpdoc/RFC/removed_extensions">phpdoc/RFC/removed_extensions</a>,
+ <a href="http://cvs.php.net/co.php/phpdoc/RFC/moved_extensions">phpdoc/RFC/moved_extensions</a>, and a
+ <a href="http://www.faqts.com/knowledge_base/view.phtml/aid/22154/fid/1150">PHP 5 Faqt</a> that links to PHP 5 related resources.
</div>
</li>
<li>


Philip Olson

unread,
Jun 4, 2003, 1:19:27 PM6/4/03
to php...@lists.php.net
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>


Gabor Hojtsy

unread,
Jun 5, 2003, 1:37:30 PM6/5/03
to php...@lists.php.net
goba Thu Jun 5 13:37:30 2003 EDT

Modified files:
/phpdoc/RFC 2003_meeting_agenda.html
Log:

Reflect current practice ;)

Index: phpdoc/RFC/2003_meeting_agenda.html
diff -u phpdoc/RFC/2003_meeting_agenda.html:1.6 phpdoc/RFC/2003_meeting_agenda.html:1.7
--- phpdoc/RFC/2003_meeting_agenda.html:1.6 Wed Jun 4 13:19:27 2003
+++ phpdoc/RFC/2003_meeting_agenda.html Thu Jun 5 13:37:30 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.6 2003/06/04 17:19:27 philip Exp $</p>
+ <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.7 2003/06/05 17:37:30 goba 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

@@ -602,9 +602,10 @@

<p>Contact <a href="mailto:php...@lists.php.net">the PHP Documentation
Mailing List</a> in case of questions and suggestions for discussions. In
- case of suggestions regarding this page or personal problems, please
+ case of suggestions regarding this page, please
write to Goba (<span class="linklooking"
- title="This is not a real link, you know why :)">goba at php dot net</span>)</p>
+ title="This is not a real link, you know why :)">goba at php dot net</span>)
+ or fix the page yourself in phpdoc/RFC/2003_meeting_agenda.html.</p>

</div>
</body>


0 new messages