2 - The unofficial website:
---------------------------
Yannick (mostly), Guillaume (admin) and I have been developping
a first draft since last week. The url is :
http://doc.keliglia.com/
This website is still messy (a lot of french comments, redundancy,
etc) and I was planing to clean it out before making it public.
(Vincent, I'll kick you from #phpdoc as soon as I get back online :p)
This address is going to be doc[s].php.net. What do you think: should we ask systems@ to set these domains up to point to the current server and then reconfigure if the new server is up? Having the server under the php.net umbrella would help in idetifying logged in PHP.net users (and would shed some more official light on the project :).
Go for it, can you please ask them to do so ? Keliglia IP is always the same :
81.57.253.132
I would not bother systems with this, unless we need to wait for Guillaume for a long time (weeks). Otherwise there is not much point in setting the name up now.
So far only I have been objecting against the php.netish look for this joint effort, since I am a bit sick with it, and I do think that it should not be that different for the different doc projects. And what is most important, it will not work if I pick hu.docs.php.net, which is not supposed to be tied to any of the projects.
So what do you want for the new website ? I'm ok with changing the design.
See my simple proposal. I'll do that :)
Since I have a copy of the code, I have seen you are using mysql too. I would suggest you stick to sqlite instead, since livedocs will run on that anyway, and it will be easier for future contributors to help, if only a single database type should be dealt with.
Yup, we used MySQL because we needed to set up the RFC stuff quickly, but I'll
change it to use Sqlite as soon as we have a final decision for this.
IMHO since livedocs uses sqlite anyway, it wold be better to stick to it. It is quite close to MySQL on the PHP API front.
Seems to be fixed, but this wasn't reported to keliglia's mailing list
because of some of my tests on commitinfo.pl. Do you think we should redirect the commits email to this mailing list ?
There is no point in sending emails here about changes on some code which is not visible to people. We should clean it up as soon as possible, and then commit it to cvs.php.net/docweb, and you should set doc.keliglia.com to update code from this cvs module.
Also, I'm an optimistic guy, I believe that if someone reads a translation
of the manual, and sees a warning claiming that this translation is outdated.
This someone can help us updating the translation if we provide a simple way
to do it. (see the phpdoc/RFC for the findings about a visual editing utility)
That is a bit too optimistic with current conditions, but Christian is working on something towards making this possible (his main problem is our entity usage).
What is the project web page ? Maybe Nuno and him can join efforts ?
There is no project web page. Christian is planning on basing this on Bitflux editor, yes. But he is just going to holiday:
http://blog.bitflux.ch/p1709.html I say you not concentrate on visual editing yet, but other stuff to do for the central website instead.
I don't know how this is done in separate projects (PEAR, GTK?)
Me neither to be honnest. Guys ?
See letters from Arnaud.
Goba