> Back with an okay from nexen :)
>
> I had a discussion with my company, and giving the fact that it's an
> "open source" project, there are okay to provide us with our needs.
>
Wonderfull news!... You boss is great.
Now lets wait for a systems response.
Back with an okay from nexen :)
I had a discussion with my company, and giving the fact that it's an
"open source" project, there are okay to provide us with our needs.
The server is a mono-CPU [EMAIL PROTECTED], 512MB RAM, RAID controler. It will
be hosted in a French DataCenter (redbus), at P
David:
we'd be interested in what you have to offer - please contact me
directly and we will figure something out. :)
thanks,
- james
On 1 Feb 2004, at 12:09, Mehdi Achour wrote:
Derick Rethans wrote:
On Sat, 31 Jan 2004, Mehdi Achour wrote:
a big big big +1 here :) It will be great to allow some ssh access
for
some active persons of the doc team. Having the doc.php.net on
another
(isolated) machine will also make happy system
On 31 Jan 2004, at 22:20, David Costa wrote:
On Jan 31, 2004, at 11:15 PM, Mehdi Achour wrote:
Gabor Hojtsy wrote:
- revcheck output hosting
- build logs, error reports
Those will end up on the doc build machine, which is now
sc1.php.net
(and yes, they still need to be enabled)
So then it w
I agree...many bugs are initially entered as php-bugs, but a big part of
them are most likely "mal-comprehension" issues or bad documented behaviour,
so this transition should be easy at any time.
"Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> >> - have an independent
Great idea!
As it was mentioned above, it will help very much to newbies and to
translation teams. However, every translation is a completely "new"
documentation, so the TODO list would be very useful. Like that each new
"docer" will know where the team is and he can start almost immediately to
wo
Hi all,
On Feb 1, 2004, at 4:48 PM, Gabor Hojtsy wrote:
As much as I'd like to see this project expedited, as well, I agree
with Derick, here. It would be nice to have an independent server,
but we can't risk the possibility of its admins becoming "rogue",
and dirtying the php.net domain.
umh
On Feb 1, 2004, at 4:48 PM, Gabor Hojtsy wrote:
As much as I'd like to see this project expedited, as well, I agree
with Derick, here. It would be nice to have an independent server,
but we can't risk the possibility of its admins becoming "rogue",
and dirtying the php.net domain.
umh but if the
I don't. You want this to be an official PHP thing, then it should be
hosted on an official machine. We can't have each subproject being run
by somebody else (if only for security reasons).
As much as I'd like to see this project expedited, as well, I agree
with Derick, here. It would be nice to h
On Feb 1, 2004, at 6:33 AM, Sean Coates wrote:
I don't. You want this to be an official PHP thing, then it should be
hosted on an official machine. We can't have each subproject being run
by somebody else (if only for security reasons).
As much as I'd like to see this project expedited, as well, I
On Feb 1, 2004, at 2:59 PM, Gabor Hojtsy wrote:
I don't. You want this to be an official PHP thing, then it should be
hosted on an official machine. We can't have each subproject being run
by somebody else (if only for security reasons).
That server would only need to cvs checkout data anonymously
Ah, all right... Understandable. Then the question is still up to
systems@ whether there is some willingness to set up a machine/vhost, or
we will better do with opening a vhost on some new donated machine
offered by a docteam member?
The added benefit of the latter option would be that we will not
Derick Rethans wrote:
On Sat, 31 Jan 2004, Mehdi Achour wrote:
a big big big +1 here :) It will be great to allow some ssh access for
some active persons of the doc team. Having the doc.php.net on another
(isolated) machine will also make happy systems@ IMHO :)
Why do you need ssh access?
Becau
I don't. You want this to be an official PHP thing, then it should be
hosted on an official machine. We can't have each subproject being run
by somebody else (if only for security reasons).
As much as I'd like to see this project expedited, as well, I agree with
Derick, here. It would be nice to h
On Sat, 31 Jan 2004, Mehdi Achour wrote:
> a big big big +1 here :) It will be great to allow some ssh access for
> some active persons of the doc team. Having the doc.php.net on another
> (isolated) machine will also make happy systems@ IMHO :)
Why do you need ssh access?
Derick
On Sat, 31 Jan 2004, Gabor Hojtsy wrote:
> Ah, all right... Understandable. Then the question is still up to
> systems@ whether there is some willingness to set up a machine/vhost, or
> we will better do with opening a vhost on some new donated machine
> offered by a docteam member?
>
> The added
Gabor Hojtsy wrote:
Hi All!
I was thinking about opening a site dedicated to the phpdoc team.
This site would have the following goals:
- centralize the efforts of the various contributors.
- provide reference documents:
* list of the undocumented functions
* large TODO
* list of the functi
Gabor Hojtsy wrote:
Hi All!
I was thinking about opening a site dedicated to the phpdoc team.
This site would have the following goals:
- centralize the efforts of the various contributors.
- provide reference documents:
* list of the undocumented functions
* large TODO
* list of the functi
On Jan 31, 2004, at 11:15 PM, Mehdi Achour wrote:
Gabor Hojtsy wrote:
- revcheck output hosting
- build logs, error reports
Those will end up on the doc build machine, which is now
sc1.php.net
(and yes, they still need to be enabled)
So then it will be ideal to set up this docteam website on
Gabor Hojtsy wrote:
- have an independent bug system ?
BTW I would not support an independent bug system yet... Maybe on the
long term... There are valid reasons for this, but we are not ready yet
for such a system IMHO. The other points mentioned by Mehdi are fine :))
mmm.. Ok, ok, I won't to
Gabor Hojtsy wrote:
- revcheck output hosting
- build logs, error reports
Those will end up on the doc build machine, which is now sc1.php.net
(and yes, they still need to be enabled)
So then it will be ideal to set up this docteam website on the same
machine, since a lot of the needed checkou
- revcheck output hosting
- build logs, error reports
Those will end up on the doc build machine, which is now sc1.php.net
(and yes, they still need to be enabled)
So then it will be ideal to set up this docteam website on the same
machine, since a lot of the needed checkouts are already present th
On Sat, 31 Jan 2004, Gabor Hojtsy wrote:
> >> - revcheck output hosting
> >> - build logs, error reports
> >
> > Those will end up on the doc build machine, which is now sc1.php.net
> > (and yes, they still need to be enabled)
>
> So then it will be ideal to set up this docteam website on the sa
- revcheck output hosting
- build logs, error reports
Those will end up on the doc build machine, which is now sc1.php.net
(and yes, they still need to be enabled)
So then it will be ideal to set up this docteam website on the same
machine, since a lot of the needed checkouts are already present
On Sat, 31 Jan 2004, Gabor Hojtsy wrote:
> - revcheck output hosting
> - build logs, error reports
Those will end up on the doc build machine, which is now sc1.php.net
(and yes, they still need to be enabled)
Derick
- have an independent bug system ?
BTW I would not support an independent bug system yet... Maybe on the
long term... There are valid reasons for this, but we are not ready yet
for such a system IMHO. The other points mentioned by Mehdi are fine :))
Goba
Hi All!
I was thinking about opening a site dedicated to the phpdoc team.
This site would have the following goals:
- centralize the efforts of the various contributors.
- provide reference documents:
* list of the undocumented functions
* large TODO
* list of the functions with bad protos,
28 matches
Mail list logo
