Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
Please use "reply all" when replying, so others will also get the mail. If you have Karma for this, please commit, the changes seem very much reasonable. From http://www.php.net/cvs-php.php "Submitting patches and participating in the discussion on the 'internals' list before requesting full CVS access is strongly suggested, so the PHP development team can get to know you and what you'll be contributing." I don't have a CVS account, so I was following this advice by simply submitting a patch, and the internals list seemed wrong for a phpdoc patch. Should I just apply for an account? Well that text refers to the internals list, and not phpdoc ;) I am not sure what rules should apply here... I would be happy to commit your modifications to CVS, but I am not near an environment ready for this currently. If you intend to contribute on a regular basis, I would suggest you request a CVS account. Can you explain the karma system more or provide a URL? I haven't found much information about it on php.net. The aforementioned URL says nothing about karma, either. It's not enough to have a CVS account. The Karma system controls what you have write access to (anybody has read access to anything on cvs.php.net even without a CVS account). This is to prevent you from messing with something you are not supposed to modify. So it can happen that you have a CVS account, but still you are unable to commit to phpdoc because you have no Karma for that. Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
Forget the last patch, this one is much more extensive! "Oops". If you have Karma for this, please commit, the changes seem very much reasonable. Thanks, Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
Forget the last patch, this one is much more extensive! Dave -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] [PATCH] phpdoc/howto/working.xml
Attached is a patch fixing a couple of typos and grammatical mistakes. Dave working.xml.patch Description: Binary data -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
On Sunday, August 10, 2003, 10:22:31 PM, Gabor wrote: > Please use "reply all" when replying, so others will also get the mail. *nod* >> Can you explain the karma system more or provide a URL? I haven't found >> much information about it on php.net. The aforementioned URL says >> nothing about karma, either. > It's not enough to have a CVS account. The Karma system controls what > you have write access to (anybody has read access to anything on > cvs.php.net even without a CVS account). This is to prevent you from > messing with something you are not supposed to modify. So it can happen > that you have a CVS account, but still you are unable to commit to > phpdoc because you have no Karma for that. Ah, so it's just write access control to certain modules/directories? Now it all makes sense. When I think of karma, I think of good/bad karma. I suppose getting access to an extra part of the repository might be considered increasing your karma in a way. Thanks for the rundown. > Goba Dave -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
> Forget the last patch, this one is much more extensive! "Oops". Dave working.xml.patch Description: Binary data -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
On Sat, 9 Aug 2003, dave wrote: > > Forget the last patch, this one is much more extensive! > > "Oops". Can you please make your email cliena attach it as plain text? (You might need to rename it to .txt for your client). Derick -- "Interpreting what the GPL actually means is a job best left to those that read the future by examining animal entrails." - Derick Rethans http://derickrethans.nl/ International PHP Magazine http://php-mag.net/ - -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] [PATCH] phpdoc/howto/working.xml
On Saturday, August 9, 2003, 9:55:21 PM, Derick wrote: > Can you please make your email cliena attach it as plain text? (You > might need to rename it to .txt for your client). Sure. Sorry about that. > Derick DaveIndex: working.xml === RCS file: /repository/phpdoc/howto/working.xml,v retrieving revision 1.36 diff -u -r1.36 working.xml --- working.xml 23 Jun 2003 09:47:28 - 1.36 +++ working.xml 9 Aug 2003 11:49:52 - @@ -409,7 +409,7 @@ Function names should be created, and documented, in lowercase format with an underscore separating the name components. Names without underscores are often only kept for backward - compatibilty. Document the function named with underscores + compatibility. Document the function named with underscores separating components, and mention the old one as an alias. @@ -457,13 +457,13 @@ - Brevity is appreciated. Long winded descriptions of each and + Brevity is appreciated. Long-winded descriptions of each and every function are not appropriate for the reference sections. Using the errata comments as guidelines, it's easier to tell when more documentation is needed, as well as the inverse, when too much documentation in one section has increased confusion. - Noone complained about too much documentation - in any section till now, so be brave to add longer explanations, + No one complained about too much documentation + in any section until now, so be brave to add longer explanations, and more than one example per function. :) @@ -655,9 +655,9 @@ There are many active translations out there of the PHP - documentation. Some lanaguages are being maintaned by + documentation. Some languages are being maintained by a group of translators (eg. the German), some are one person - projects (eg. the Japanese). There are quite many things for + projects (eg. the Japanese). There are quite a few things for translators to know, though these are simple. @@ -665,7 +665,7 @@ Starting a New Translation Starting a new language translation comes down to -the following simple steps now. +the following simple steps: @@ -678,7 +678,7 @@ Ask for a CVS account. - Mention, that you would like to start a new translation. + Mention that you would like to start a new translation. @@ -696,7 +696,7 @@ and phpdoc-LANGCODE (using the phpdoc-LANGCODE-dir alias) as described in the CVS chapter - of this howto. + of this HOWTO. @@ -716,7 +716,7 @@ revision tracking for help about how can you ease your work of tracking the English - versions, and your languages versions. + version and your language's version. @@ -752,15 +752,15 @@ If you see that a manual for your language is set up, and you would like to join the group, please ask on the appropriate mailing -list about who is responsible to manage that +list about who is responsible for managing that translation. If you are new to the PHP project, and you have no CVS account, you need to request -one account, before you can join the work. Although +an account before you can join the group. Although there are some translations where just a few people have -CVS accounts, and they are responsible for comitting the +CVS accounts, and they are responsible for committing the other's works, this may not be ideal. @@ -788,7 +788,7 @@ Use a system to coordinate with the translators in your language. Currently we have two systems - used paralelly, the Translators files and the + used in parallel, the Translators files and the Revision comments. See the section about revision tracking to learn more about this subject. @@ -833,8 +833,8 @@ made to your language's files, are correct. You may introduce illegal characters. Please always do a make - test before commiting. Introducing an - error in your languages manual can stop the + test before committing. Introducing an + error in your language's manual can stop the automatic updates online until you correct the error. @@ -850,10 +850,10 @@ &url.buildlog.de;. Substitute "de" with your own language code to see the information about your manual. This file - provides you information about the build times, + provides you with information about the build times, and errors (if there were any). If the manual is - not updated online, it is a good idea, to look - into this file and see what was the er
