You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Felix Meschberger <fm...@gmail.com> on 2007/11/02 09:38:13 UTC
[VOTE] Sling API
Hi all,
Finally after much fiddling around on the Sling API and its "reference
implementation" microsling, I would like to start the vote on the Sling
API. This vote is not to cast the Sling API in stone for the next 2000
years but to ack that it is in a good enough shape as to warrant
refactoring of Sling to the new Sling API and drop the Component API.
[ ] +1 Sling API is good enough to refactor Sling
[ ] 0
[ ] -1 Sling API is not good enough, keep the old Component API
Everyone is invited to vote. The vote passes with at least three binding
+1 votes and no -1 votes (vetoes). The vote is open until Thuesday, 8
AM, CET.
Thanks and Regards
Felix
Re: [VOTE] Sling API
Posted by Carsten Ziegeler <cz...@apache.org>.
+1
Carsten
Felix Meschberger wrote:
> Hi all,
>
> Finally after much fiddling around on the Sling API and its "reference
> implementation" microsling, I would like to start the vote on the Sling
> API. This vote is not to cast the Sling API in stone for the next 2000
> years but to ack that it is in a good enough shape as to warrant
> refactoring of Sling to the new Sling API and drop the Component API.
>
> [ ] +1 Sling API is good enough to refactor Sling
> [ ] 0
> [ ] -1 Sling API is not good enough, keep the old Component API
>
> Everyone is invited to vote. The vote passes with at least three binding
> +1 votes and no -1 votes (vetoes). The vote is open until Thuesday, 8
> AM, CET.
>
> Thanks and Regards
> Felix
>
>
--
Carsten Ziegeler
cziegeler@apache.org
Re: [VOTE] Sling API
Posted by Juan José Vázquez Delgado <ju...@gmail.com>.
+1
BR,
Juanjo
On 11/2/07, Felix Meschberger <fm...@gmail.com> wrote:
>
> Hi all,
>
> Finally after much fiddling around on the Sling API and its "reference
> implementation" microsling, I would like to start the vote on the Sling
> API. This vote is not to cast the Sling API in stone for the next 2000
> years but to ack that it is in a good enough shape as to warrant
> refactoring of Sling to the new Sling API and drop the Component API.
>
> [ ] +1 Sling API is good enough to refactor Sling
> [ ] 0
> [ ] -1 Sling API is not good enough, keep the old Component API
>
> Everyone is invited to vote. The vote passes with at least three binding
> +1 votes and no -1 votes (vetoes). The vote is open until Thuesday, 8
> AM, CET.
>
> Thanks and Regards
> Felix
>
>
Re: [VOTE] Sling API
Posted by Felix Meschberger <fm...@gmail.com>.
+1
Regards
Felix
Am Freitag, den 02.11.2007, 09:38 +0100 schrieb Felix Meschberger:
> Hi all,
>
> Finally after much fiddling around on the Sling API and its "reference
> implementation" microsling, I would like to start the vote on the Sling
> API. This vote is not to cast the Sling API in stone for the next 2000
> years but to ack that it is in a good enough shape as to warrant
> refactoring of Sling to the new Sling API and drop the Component API.
>
> [ ] +1 Sling API is good enough to refactor Sling
> [ ] 0
> [ ] -1 Sling API is not good enough, keep the old Component API
>
> Everyone is invited to vote. The vote passes with at least three binding
> +1 votes and no -1 votes (vetoes). The vote is open until Thuesday, 8
> AM, CET.
>
> Thanks and Regards
> Felix
Re: [VOTE] Sling API
Posted by Christophe Lombart <ch...@gmail.com>.
+1. I really like it even if I'm not really imply in the project.
Christophe
On 11/2/07, Felix Meschberger <fm...@gmail.com> wrote:
>
> Hi all,
>
> Finally after much fiddling around on the Sling API and its "reference
> implementation" microsling, I would like to start the vote on the Sling
> API. This vote is not to cast the Sling API in stone for the next 2000
> years but to ack that it is in a good enough shape as to warrant
> refactoring of Sling to the new Sling API and drop the Component API.
>
> [ ] +1 Sling API is good enough to refactor Sling
> [ ] 0
> [ ] -1 Sling API is not good enough, keep the old Component API
>
> Everyone is invited to vote. The vote passes with at least three binding
> +1 votes and no -1 votes (vetoes). The vote is open until Thuesday, 8
> AM, CET.
>
> Thanks and Regards
> Felix
>
>
Re: [VOTE] Sling API
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 11/2/07, Felix Meschberger <fm...@gmail.com> wrote:
> [X ] +1 Sling API is good enough to refactor Sling
Just in case, here's the URL to the API:
http://svn.apache.org/repos/asf/incubator/sling/trunk/sling-api/
-Bertrand
[RESULT] [VOTE] Sling API
Posted by Felix Meschberger <fm...@gmail.com>.
Hi all,
The vote for the new Sling API to replace the former Component API is
now closed with the following result (* marks binding votes):
*Felix Meschberger +1
*Betrand Delacretaz +1
*Juanjo Velazquez +1
*Carsten Ziegeler +1
*Christophe Lombart +1
Torgeir Veimo +1
This vote passes with 6 (5 of which binding) +1 votes and no veto. Thank
you all for voting.
I will now create a branch of the current Sling state as
Sling_Component_API start reorganizing the trunk according to Module
Reorganization Proposal [1]. Next I will start porting the code to the
new Sling API.
Regards
Felix
[1] http://cwiki.apache.org/confluence/x/6REB
Am Freitag, den 02.11.2007, 09:38 +0100 schrieb Felix Meschberger:
> Hi all,
>
> Finally after much fiddling around on the Sling API and its "reference
> implementation" microsling, I would like to start the vote on the Sling
> API. This vote is not to cast the Sling API in stone for the next 2000
> years but to ack that it is in a good enough shape as to warrant
> refactoring of Sling to the new Sling API and drop the Component API.
>
> [ ] +1 Sling API is good enough to refactor Sling
> [ ] 0
> [ ] -1 Sling API is not good enough, keep the old Component API
>
> Everyone is invited to vote. The vote passes with at least three binding
> +1 votes and no -1 votes (vetoes). The vote is open until Thuesday, 8
> AM, CET.
>
> Thanks and Regards
> Felix