(please don't take any of my paragraph replies as a whole)
Gabor Hojtsy wrote: <snip>
It is somewhat positive to see so many people doing things, but it is quite satiric to see that there is no common way, and everyone comes up with his own solutions.
I can't speak for the others, but I think I've clearly labeled my contributions "unofficial", and do not think of them as anything more. There are a few of us (including Dave, and Philip, as you address, below) that use some/all of these tools regularly, and we regularly help each other out through #phpdoc on freenode.
Dave, the docweb project is supposed to contain scripts used to support phpdoc workers via the web. Or if you have scripts to commit to phpdoc, then you can also commit there. Have I overlooked your tools commited to one of these modules, or there is some strong reason to start a new project? Note that if you are not going to commit your code, people will start to write the tools again and again, as it used to be...
Really, it's up to Dave to modify these tools for use in docweb. If he feels like it, he will, if not, he won't. The only reason they're on my server (at which phpdoc.info points) is because erigol.com was unfortunately offline for a few days/weeks and I offered to host Dave's tools. They're good tools, and we have no official place for them. What good would they do in CVS, currently?
Philip/Sean, are you dissatisfied with the adoptoin of pepr to the php doc projects (as being worked on by Vincent), or you have the intention to post your RFCs on this new system later, and you are just impatient? Having RFCs, have you looked into the adopted pepr?
Again, I can't speak for Philip, but yes, I am impatient. My Nomenclature RFC is nothing more than a work in progress. The wiki serves it well, and when I feel it is ready, I will either post it to PEPr (if that's ready by then), or post it to the list. Again, this is all unofficial.
As for Philip's DocSkel RFC, I took the liberty of adopting the skeleton he was hosting in a .zip file on boogle.com and posting it on the wiki, because I wanted to make a few changes, and it's extremely difficult to patch a .zip.
The wiki lends well to this situation, and when asking around, the general concensus (from Derick, especially, IIRC) is that systems@ is not interested in hosting/managing a wiki. So I am.
PEPr does not exist for doc purposes, yet. In the interim, peoples' ideas should not stop flowing. Docweb is new. There's no way to USE PEPr, yet, officially. Do you propose we set up individual PEPrs and use them? of course not. That is no different than the collection of links, above.
I am really sad that the efforts tend to get disorganized by intention. Maybe when I have some idea to discuss, I will set up a new cms somewhere (probably Drupal to be inconsistent and because I love this CMS :), and post my ideas via that interface, so if someone finds it sometime, (s)he can reply to it. Would it be better? I don't think so.
Your sarcasm is appreciated, but I was (and am still) not officially soliciting replies to my Nomenclature RFC. If I was, it would've been posted to the list. If someone stumbles upon it, and has some input, great, but I'm not looking for much, right now, other than asking the guys on #phpdoc what they think.
I'm also not hurt that nobody has searched me out and found my RFC and made modifications to it, or patted me on the back. I was even surprised to see the wiki posted to [PHP-DOC] this morning.
About the official docweb server.<snip>no reply, just get it done! (-; </snip>
While we are playing games above this issue, more and more patch sites, wikis, rfc systems, tools pop up in different locations of the web, and getting the info needed for decision making and pushing the project forward does not get easier but rather harder and harder, as finding the stuff you read yesterday get impossible.
Again, none of it is official. We (or at least I) don't expect it to be. The patch sites popped up out of necessity (how long were Nuno's patches available and lost in the archives before I spoke up about them? -- THERE WAS a central repository for livedocs patches: CVS, but access to it was restricted, hence the patch sites).
The fact remains: doc-web does not yet exist. Once we get something official (like maybe a domain name with attached server, and a functioning checkout of the module?), people like myself might be inclined to commit some code. In the mean-time, I'd rather USE (and allow others to use) the tools I've written instead of watching them rot in a CVS repository that may or may not see the light of day, depending on who has bigger toes.
As I see it, there are two central points of gathering for the php-doc team: the mailing list(s) and CVS. If you "read stuff yesterday" and it wasn't in one of those two places, it shouldn't be considered official, and should not impede your work.
Note: I've also written a factoid bot that sits on #phpdoc that wasn't linked above, it's tied into [PHP-DOC] and alerts us to commits, as well. I hope I won't be shamed for that, too.
S
