Phillip and I had a chat about this last night and I think we have a
strategy for appealing to the geek in all of us.
-Rasmus
Mehdi Achour wrote:
> As Phillip stated, we already have a set of tools that points us to
> the problems in the documentation.
>
> We also are switching the documentation
Mehdi Achour wrote:
Thank you all for your replies, I'm happy to see that the snowball
effect started!
Just make sure that you take this momentum and directly contact people
who's offers you want to take up so that real world effect can be
derived from all of the offers.
regards,
Lukas
--
As Phillip stated, we already have a set of tools that points us to
the problems in the documentation.
We also are switching the documentation to a clearer format, which we
help us to have more accurate results on this, while making docs
editing simpler for you guys.
I've noted your periodical u
Hello Wez,
Thanks for your action. BTW, we need to stick to one tag :) I proposed
@doc, you implemented [DOC] .. we should pick one syntax and stick to
it.
By the way, Etienne (cc'ed) started to work on the web interface I
described in my first email. You may want to get in touch with him to
hel
Philip Olson wrote:
There are 137 open documentation bugs and many of these require PHP
internals intervention. I don't know the best way to help that happen
aside from maybe going through them all and updating the summaries (and
appending categories to those summaries) but then what? A questi
On Feb 10, 2007, at 8:38 AM, Rasmus Lerdorf wrote:
We, and by we I mean all of us who write code and hope that divine
intervention will take care of the documentation, need to do a better
job helping out divinity. A DOC tag in cvs commit messages seems
like a
small and easy thing for us to a
On Sat, February 10, 2007 5:41 am, Ronald Chmara wrote:
> Scenario one:
> All behavior changes must be documented, this tag is always there,
> and thus not useful.
I beg to differ.
If every change was documented to the degree that it needed
documentation, the tag would be useful still:
USEFUL:
-
Hi,
I also made a mailing list scanner[1] that fills a DB on doc.php.net.
Every entries can then be commented, tagged as TODO etc...
The scanner itself is ready, the interface still need some work.
Maybe a mix of both ?
[1] http://colder.ch/repository/php/php.net/cvslogger.php
Wez Furlong wr
I tweaked loginfo.pl so that if the commit message contains [DOC],
phpdoc@ will be Cc'd.
Hopefully that'll help in some small way.
--Wez.
On 2/10/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
We, and by we I mean all of us who write code and hope that divine
intervention will take care of the d
Rasmus Lerdorf wrote:
Perhaps we can do more though. Maybe you guys could periodically update
internals on problem areas in the docs. Places where you feel things
are vague and really could use the guy who wrote the code to get off his
ass and explain how it works. Or maybe we could get every
We, and by we I mean all of us who write code and hope that divine
intervention will take care of the documentation, need to do a better
job helping out divinity. A DOC tag in cvs commit messages seems like a
small and easy thing for us to add to the process, so if you feel that
will be enough to
On Jan 27, 2007, at 8:26 AM, Mehdi Achour wrote:
Hello internals,
I've been helping with PHP documentation for 4 years now, and I
still can't help the fact that a lt of things are not
documented, that our/my way of handling the PHP documentation
update is not accurate, nor productive, n
Personally, I try to follow commits on
php.cvs, bug reports, Change Log,
user notes on the online manual..
but I still have the feeling of missing
a lot of changes. After a year away from
the project, I have _no_ clue what was
added, when, and whether it was added
to our documentation or not.
13 matches
Mail list logo
