CVS Account Request: merlin

php.internals

Pavlo Shelyazhenko

20 years ago
To develop the Summer of Code project - PHP Macro Preprocessor

Pierre Joye

20 years ago
On 5/27/06, Pavlo Shelyazhenko <shelyazhenko@voliacable.com> wrote:
> To develop the Summer of Code project - PHP Macro Preprocessor
Once there is some code to see, we will create your accounts and give you CVS access. Also we should name your project before the first commit. --Pierre

Marcus Börger

20 years ago
Hello Pierre, you don't mind if the Mentors take care of their students do you? Saturday, May 27, 2006, 5:12:00 PM, you wrote:
> On 5/27/06, Pavlo Shelyazhenko <shelyazhenko@voliacable.com> wrote: >> To develop the Summer of Code project - PHP Macro Preprocessor
> Once there is some code to see, we will create your accounts and give > you CVS access. Also we should name your project before the first > commit.
> --Pierre
Best regards, Marcus

Pierre Joye

20 years ago
On 5/27/06, Marcus Boerger <helly@php.net> wrote:
> Hello Pierre, > > you don't mind if the Mentors take care of their students do you?
Let me rephrase. SoC or not, Mr. Boerger or not, it does not matter. The base principle to get a PECL/PEAR/PHP.net account and cvs access is to: - Introduce yourself to the project list (internals or pecl in that case) - Show up some sources code, incl. the license and some roadmaps Thanks for your attention, --Pierre

Antony Dovgal

20 years ago
On 27.05.2006 19:16, Pierre wrote:
> On 5/27/06, Marcus Boerger <helly@php.net> wrote: >> Hello Pierre, >> >> you don't mind if the Mentors take care of their students do you? > > Let me rephrase. SoC or not, Mr. Boerger or not, it does not matter. > > The base principle to get a PECL/PEAR/PHP.net account and cvs access is to: > > - Introduce yourself to the project list (internals or pecl in that case) > - Show up some sources code, incl. the license and some roadmaps
I have to second that. It's not about you, Marcus, or Pavlo, or anybody else. It's about rules. If you have nothing to show atm - there is no reason to apply for an account.
-- Wbr, Antony Dovgal

Wez Furlong

20 years ago
Of course, if a upstanding member of our community can vouch for someone then we have no problem with opening up an account. This is precisely what the mentor is doing here. I've opened up PECL and CVS accounts for Pavlo, but granted no karma yet. Marcus (and other mentors): where CVS access is required, please advise us the portions of the repository for which karma is needed. --Wez. On 5/27/06, Pierre <pierre.php@gmail.com> wrote:

Marcus Börger

20 years ago
Hello Wez, thanks a lot. Special access has to be discussed separately of course as with any body else. best regards marcus Saturday, May 27, 2006, 5:39:59 PM, you wrote:
> Of course, if a upstanding member of our community can vouch for > someone then we have no problem with opening up an account. This is > precisely what the mentor is doing here.
> I've opened up PECL and CVS accounts for Pavlo, but granted no karma yet.
> Marcus (and other mentors): where CVS access is required, please > advise us the portions of the repository for which karma is needed.
> --Wez.
> On 5/27/06, Pierre <pierre.php@gmail.com> wrote: >> On 5/27/06, Marcus Boerger <helly@php.net> wrote: >> > Hello Pierre, >> > you don't mind if the Mentors take care of their students do you? >> Let me rephrase. SoC or not, Mr. Boerger or not, it does not matter. >> The base principle to get a PECL/PEAR/PHP.net account and cvs access is to: >> - Introduce yourself to the project list (internals or pecl in that case) >> - Show up some sources code, incl. the license and some roadmaps
Best regards, Marcus

Pierre Joye

20 years ago
On 5/27/06, Wez Furlong <kingwez@gmail.com> wrote:
> Of course, if a upstanding member of our community can vouch for > someone then we have no problem with opening up an account. This is > precisely what the mentor is doing here. > > I've opened up PECL and CVS accounts for Pavlo, but granted no karma yet.
It is a mistake. We never proceeded like that and I see no reason to do it now. The whole decision process is opaque, sticking to our rules would make it more transparent. --Pierre

Wez Furlong

20 years ago
The whole point of the mentor is to streamline the process of getting new blood into a project; I see no reason to make it more difficult by being too rigid. --Wez. On 5/27/06, Pierre <pierre.php@gmail.com> wrote:

Pierre Joye

20 years ago
On 5/27/06, Wez Furlong <kingwez@gmail.com> wrote:
> The whole point of the mentor is to streamline the process of getting > new blood into a project; I see no reason to make it more difficult by > being too rigid.
It is not being rigid to ask some more transparency. We had reasons to define these simple rules, I don't reasons to forget them for SoC. We are not asking the mood, but some codes and a roadmap. Something to show us what is the project etc. like in any other previous proposals. --Pierre

Wez Furlong

20 years ago
The mentors have already volunteered their time to guide the SoC folks through the process; we should back them up and let them get on with it; there is little point in wasting our collective time in bickering over the fine print. --Wez On 5/27/06, Pierre <pierre.php@gmail.com> wrote:

Pierre Joye

20 years ago
On 5/27/06, Wez Furlong <kingwez@gmail.com> wrote:
> The mentors have already volunteered their time to guide the SoC folks > through the process; we should back them up and let them get on with > it; there is little point in wasting our collective time in bickering > over the fine print.
Excuse me to take care of your job. And excuse me to ask things I should not ask. I will simply open accounts in the future. --Pierre

Marcus Börger

20 years ago
Hello Pierre, everything will be only. At least on code.google.com in a bit if you don't let me continue to do th eadminstration part... Saturday, May 27, 2006, 6:01:11 PM, you wrote:
> On 5/27/06, Wez Furlong <kingwez@gmail.com> wrote: >> The whole point of the mentor is to streamline the process of getting >> new blood into a project; I see no reason to make it more difficult by >> being too rigid.
> It is not being rigid to ask some more transparency. We had reasons to > define these simple rules, I don't reasons to forget them for SoC.
> We are not asking the mood, but some codes and a roadmap. Something to > show us what is the project etc. like in any other previous proposals.
> --Pierre
Best regards, Marcus