ator/ZetaComponentsProposal
>
> Regards,
> Toby
>
> =====
> Proposal: Zeta Components
> =
>
> Zeta Components is a high-quality library of loosely coupled PHP components.
>
> -
> Proposal
> -
>
On Fri, Apr 23, 2010 at 6:28 PM, Tobias Schlitt wrote:
> I actually expected that some mentors would volunteer during the
> discussion here.
Yes, that is normally the case... Question is whether people feel too
over-committed, and we have a short-fall of Mentors.
I would love to, but definitely
> I actually expected that some mentors would volunteer during the
> discussion here. The incubator docs state that "Mentors are chosen by
> the Sponsor". I assumed that the Incubator PMC would be our sponsor. Is
> there a certain process we need to trigger, like asking the Incubator
> PMC for spon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Leo,
On 04/23/2010 12:40 AM, Leo Simons wrote:
> On 4/22/10 10:21 AM, Tobias Schlitt wrote:
>> I updated the proposal to reflect the objections regarding the
>> infrastructure. Our questions regarding the import of our SVN history
>> has been clear
/ZetaComponentsProposal
Regards,
Toby
=
Proposal: Zeta Components
=
Zeta Components is a high-quality library of loosely coupled PHP components.
-
Proposal
-
The Zeta project was originally named *eZ Components* [1]_ and was
developed as an open
://wiki.apache.org/incubator/ZetaComponentsProposal
Regards,
Toby
=
Proposal: Zeta Components
=
Zeta Components is a high-quality library of loosely coupled PHP components.
-
Proposal
-
The Zeta project was originally named *eZ
On 4/22/10 10:21 AM, Tobias Schlitt wrote:
I updated the proposal to reflect the objections regarding the
infrastructure. Our questions regarding the import of our SVN history
has been cleared.
Are there further comments, suggestions, objections?
Very nicely written proposal, well done! Looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/04/10 16:27, Tobias Schlitt wrote:
> I think we should do that on the builds@ list later, since I'm not sure
> how to exactly do CI with our stuff in ASF environment, yet. We have a
> custom test suite, based on PHPUnit, and require some PHP exte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 04/22/2010 02:43 PM, Gav... wrote:
>>
>
> The CI stuff is secondary to get started, since we will also have
> external CI. We can take care of that as soon as we are incubated, I
> think.
>
>> Incubation periods vary, it could be 3 months,
> -Original Message-
> From: Tobias Schlitt [mailto:tob...@schlitt.info]
> Sent: Thursday, 22 April 2010 9:55 PM
> To: general@incubator.apache.org
> Cc: Christian Grobmeier
> Subject: Re: [PROPOSAL] Zeta Components - Further comments?
>
> -BEGIN PGP SIGNED M
Hi,
it sounds good, I have no more objections. On CI, lets see how it works out :-)
Cheers!
Christian
On Thu, Apr 22, 2010 at 1:55 PM, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Christian,
>
> On 04/22/2010 12:30 PM, Christian Grobmeier wrote:
>
>>> I updated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Christian,
On 04/22/2010 12:30 PM, Christian Grobmeier wrote:
>> I updated the proposal to reflect the objections regarding the
>> infrastructure. Our questions regarding the import of our SVN history
>> has been cleared.
>> Are there further comm
Hi,
> I updated the proposal to reflect the objections regarding the
> infrastructure. Our questions regarding the import of our SVN history
> has been cleared.
> Are there further comments, suggestions, objections?
I read it again and like the update. Only:
"Required Resources
The current proj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I updated the proposal to reflect the objections regarding the
infrastructure. Our questions regarding the import of our SVN history
has been cleared.
Are there further comments, suggestions, objections?
Thanks a lot for your feedback,
regar
On Wednesday 21 April 2010 6:38:09 am Tobias Schlitt wrote
> I read on the infra pages, that our website is required to be generated
> static HTML content. This is fine for us, since the desired systems does
> basically do this. But I wounder how really dynamic stuff is handeled
> here? E.g. having
> we talked a bit about the issue tracker stuff and came to the conclusion
> that we'd go with Jira. The point of having issues central in ASF infra
> is quite striking and we agree here, that we don't want issues to be
> tracked on an external server.
Thats good, b/c infra responded and they are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 04/21/2010 12:43 PM, Daniel S. Haischt wrote:
> actually blogs are done using apache roller as you may figure from the
> below URL.
> On Wed, Apr 21, 2010 at 12:40 PM, Bertrand Delacretaz
> wrote:
>> On Wed, Apr 21, 2010 at 12:38 PM, Tobias
actually blogs are done using apache roller as you may figure from the
below URL.
On Wed, Apr 21, 2010 at 12:40 PM, Bertrand Delacretaz
wrote:
> On Wed, Apr 21, 2010 at 12:38 PM, Tobias Schlitt wrote:
>> ...I read on the infra pages, that our website is required to be generated
>> static HTML co
On Wed, Apr 21, 2010 at 12:38 PM, Tobias Schlitt wrote:
> ...I read on the infra pages, that our website is required to be generated
> static HTML content. This is fine for us, since the desired systems does
> basically do this. But I wounder how really dynamic stuff is handeled
> here? E.g. havin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
we talked a bit about the issue tracker stuff and came to the conclusion
that we'd go with Jira. The point of having issues central in ASF infra
is quite striking and we agree here, that we don't want issues to be
tracked on an external server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Justin,
On 04/21/2010 08:26 AM, Justin Erenkrantz wrote:
> On Mon, Apr 19, 2010 at 6:52 AM, Tobias Schlitt wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi all,
>>
>> please find below our proposal for Zeta Components. The propo
On Mon, Apr 19, 2010 at 6:52 AM, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> please find below our proposal for Zeta Components. The proposal is also
> available in the wiki:
>
> http://wiki.apache.org/incubator/ZetaComponentsProposal
Sorry that
apache.org/incubator/ZetaComponentsProposal
Regards,
Toby
=
Proposal: Zeta Components
=
Zeta Components is a high-quality library of loosely coupled PHP components.
-
Proposal
-
The Zeta project was originally named *eZ Components* [1
t; Regards,
> Toby
>
> =====
> Proposal: Zeta Components
> =
>
> Zeta Components is a high-quality library of loosely coupled PHP components.
>
> -
> Proposal
> -
>
> The Zeta project was originally named *
> would it be possible to package a SVN-export as a tarball for example,
> and transfer this?
> Loosing the information stored in the 11.5k changesets / commit messages
> would hurt a project of this size quite a bit.
Ask infra if we can import your full history.
--- Noel
On Tue, Apr 20, 2010 at 9:35 PM, Kore Nordmann wrote:
> The IP clearance form [1] defines that the code is transferred using a
> "canocical tarball". Does that mean, we will loose the full version
> history for the project? Or would it be possible to package a SVN-export
> as a tarball for exampl
http://wiki.apache.org/incubator/ZetaComponentsProposal
>
> Regards,
> Toby
>
> =====
> Proposal: Zeta Components
> =
>
> Zeta Components is a high-quality library of loosely coupled PHP
> components.
>
> -
> P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have one question regarding the code import.
The IP clearance form [1] defines that the code is transferred using a
"canocical tarball". Does that mean, we will loose the full version
history for the project? Or would it be possible to package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/04/10 15:11, Bertrand Delacretaz wrote:
> On Tue, Apr 20, 2010 at 3:03 PM, Christian Grobmeier
> wrote:
>>> I don't think this should be an incubation blocker, although some of us
>>> have really strong feelings against Jira and even stronger ag
On Tue, Apr 20, 2010 at 3:03 PM, Christian Grobmeier
wrote:
>> I don't think this should be an incubation blocker, although some of us
>> have really strong feelings against Jira and even stronger against
>> Bugzilla. Therefore, if we can sort out this stuff before, it's good. :)
>
> I wrote the i
> I don't think this should be an incubation blocker, although some of us
> have really strong feelings against Jira and even stronger against
> Bugzilla. Therefore, if we can sort out this stuff before, it's good. :)
I wrote the infra team an e-mail, lets see what they answer
Christian
>
> Rega
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/2010 02:48 PM, Christian Grobmeier wrote:
>> would it be problematic if issue tracking / CI would be hosted on a
>> dedicated server outside Apache? Kore Nordmann and me would happily
>> sponsor this server.
> I am not a decision maker, but I
> would it be problematic if issue tracking / CI would be hosted on a
> dedicated server outside Apache? Kore Nordmann and me would happily
> sponsor this server.
I am not a decision maker, but I would think that CI is no problem. I
mean, it uses code from Apache SVN and there is no documentation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 04/20/2010 01:34 PM, Christian Grobmeier wrote:
>>> I think the complete project should be hosted on apache servers
>> Is it possible to use Arbit instead of the standard issue trackers
>> provided by Apache?
> Currently only bugzilla and jir
Hi,
On Tue, Apr 20, 2010 at 1:34 PM, Christian Grobmeier
wrote:
> Currently only bugzilla and jira is used in apache world. The use of
> Arbit needs to be discussed with the infra team. I am not sure if this
> will happen so easily
>
> For integration, there are several continuus integration serv
>> I think the complete project should be hosted on apache servers
>
> we would be happy to host our infrastructure on Apache servers.
> Especially for SVN and the mailinglists.
SVN and mailinglists should be no problem, this is standard for most projects.
> Is it possible to use Arbit instead of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Christian,
On 04/20/2010 01:14 PM, Christian Grobmeier wrote:
>> An excellent well thought out, complete proposal, with none of the usual
>> copying
>> of previous proposals with a bit of tweaking.
> Just one note:
>>> Required Resources
>>> The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Bertrand,
On 04/20/2010 01:16 PM, Bertrand Delacretaz wrote:
> On Tue, Apr 20, 2010 at 1:07 PM, Erik Abele wrote:
>> On Apr 19, 2010, at 15:52, Tobias Schlitt wrote:
>>> http://wiki.apache.org/incubator/ZetaComponentsProposal
>> +1!
>>
>>
On Tue, 20 Apr 2010, Bertrand Delacretaz wrote:
> On Tue, Apr 20, 2010 at 1:07 PM, Erik Abele wrote:
> > On Apr 19, 2010, at 15:52, Tobias Schlitt wrote:
> >>...
> >> http://wiki.apache.org/incubator/ZetaComponentsProposal
> >
> > +1!
> >
> > Yeah, I know it's long but any other opinions?
>
+1 (Not binding)
On Tue, Apr 20, 2010 at 1:22 PM, Christian Grobmeier
wrote:
>> Being mostly clueless about PHP I'm curious about how such modules
>> would be released. Does the usual model of a downloadable archive that
>> includes NOTICE/LICENSE files apply, or would Zeta components mostly
>> b
> Being mostly clueless about PHP I'm curious about how such modules
> would be released. Does the usual model of a downloadable archive that
> includes NOTICE/LICENSE files apply, or would Zeta components mostly
> be released through a module distribution server like
> http://pear.php.net/ ?
I th
On Tue, Apr 20, 2010 at 1:14 PM, Christian Grobmeier
wrote:
>>> ...However, for reliability
>>> reasons, there are some services which we would want to have hosted by
>>> the ASF.
>
> I think the complete project should be hosted on apache servers
Agree, I missed that but yes all the required inf
On Tue, Apr 20, 2010 at 1:07 PM, Erik Abele wrote:
> On Apr 19, 2010, at 15:52, Tobias Schlitt wrote:
>>...
>> http://wiki.apache.org/incubator/ZetaComponentsProposal
>
> +1!
>
> Yeah, I know it's long but any other opinions?
Just finished reading it, big +1, cool to see more php stuff at A
> An excellent well thought out, complete proposal, with none of the usual
> copying
> of previous proposals with a bit of tweaking.
Just one note:
>> Required Resources
>> The current project infrastructure is hosted by eZ Systems, but this
>> should change. The project can be fully hosted on i
To: general@incubator.apache.org
> Cc: Derick Rethans; Kore Nordmann; Sebastian Bergmann; Ole Marius
> Smestad; Roland Benedetti
> Subject: [PROPOSAL] Zeta Components
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> please find below our proposal f
On Apr 19, 2010, at 15:52, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> please find below our proposal for Zeta Components. The proposal is also
> available in the wiki:
>
> http://wiki.apache.org/incubator/ZetaComponentsProposal
+1!
Yeah, I kn
PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> please find below our proposal for Zeta Components. The proposal is also
> available in the wiki:
>
> http://wiki.apache.org/incubator/ZetaComponentsProposal
>
> Regards,
> Toby
>
> ===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
please find below our proposal for Zeta Components. The proposal is also
available in the wiki:
http://wiki.apache.org/incubator/ZetaComponentsProposal
Regards,
Toby
=
Proposal: Zeta Components
48 matches
Mail list logo
