You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by "Andrew C. Oliver" <ac...@apache.org> on 2003/07/30 06:34:14 UTC
[VOTE] Effect a naming policy g/POI/s//Poi/g
Let me put this the right way. This vote will be conducted by the Apache
voting rules as documented here:
http://jakarta.apache.org/site/decisions.html
http://httpd.apache.org/dev/guidelines.html
Note specifically:
The act of voting carries certain obligations. Voting members are not only
stating their opinion, they are also agreeing to help do the work.
An action requiring consensus approval must receive at least 3 binding +1
votes and no binding vetos . An action requiring majority approval must
receive at least 3 binding +1 votes and more +1 votes than -1 votes. All
other action items are considered to have lazy approval until somebody
votes -1 , after which point they are decided by either consensus or
majority vote, depending on the type of action item.
Product Changes
Changes to the products of the Project, including code and documentation,
will appear as action items in the status file. All product changes to the
currently active repository are subject to lazy consensus.
However, I'm opting to call a vote.
===========================================================================
Presently the policy is:
So if you like acronyms, then POI is an acronym. If you hate them, then we
just used the name of the food for our
project. If you wish to signify your love or hate for
acronyms, use POI or Poi to refer to the project respectively.
I propose to CHANGE this policy to:
Only Poi is the acceptable spelling, POI is not an acronym. You must use
Poi to refer to the project in all documentation. To preserve consistency
with earlier releases all source code will use POI in class names and poi in
package names.
Please remember that a +1 indicates that you will help rename everything!!!
[ ] +1 - I wish to enact this product change and will help
[ ] +0 - I wish it to happen but will not help
[ ] -0 - I don't wish it to happen but will not veto
[ ] -1 - I veto the proposal.
This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
mentioned above, to carry it must receive 3 BINDING +1 votes (active
committers) and NO binding vetoes (-1).
I expect that once this vote is complete that the matter should be closed.
-Andy
---
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Danny Mui <da...@muibros.com>.
>[ ] +1 - I wish to enact this product change and will help
>[ ] +0 - I wish it to happen but will not help
>[X] -0 - I don't wish it to happen but will not veto
>[ ] -1 - I veto the proposal.
>
>This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
>mentioned above, to carry it must receive 3 BINDING +1 votes (active
>committers) and NO binding vetoes (-1).
>
>I expect that once this vote is complete that the matter should be closed.
>
>
>-Andy
>
>
>
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Rainer Klute <ra...@epost.de>.
On Wed, 30 Jul 2003 00:34:14 -0400 "Andrew C. Oliver" <ac...@apache.org> wrote:
> Only Poi is the acceptable spelling, POI is not an acronym. You must use
> Poi to refer to the project in all documentation. To preserve consistency
> with earlier releases all source code will use POI in class names and poi in
> package names.
>
> Please remember that a +1 indicates that you will help rename everything!!!
>
> [ ] +1 - I wish to enact this product change and will help
> [ ] +0 - I wish it to happen but will not help
> [ ] -0 - I don't wish it to happen but will not veto
> [X] -1 - I veto the proposal, because the project's name should be something
can be remembered easily by users or potential users. People are used
to acronyms, and POI is has a viable meaning. The word "poi" is something
strange. You will have to explain it to people, and only when and if
they understand what poi is they might find some connection to what
our project deals with. I'd like to see some marketing considerations
exchanged before we ever do such a vote again.
> This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
> mentioned above, to carry it must receive 3 BINDING +1 votes (active
> committers) and NO binding vetoes (-1).
I object to such a short time frame. One should have a week or so to
send in one's vote. For example, I just returned from a 2-days-trip
without mail access. You should also take into account that others
might have to do other work with a higher priority. Unless, of course, the
Board's rules say something different.
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH
Dipl.-Inform.
Rainer Klute E-Mail: klute@rainer-klute.de
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Tetsuya Kitahata <te...@apache.org>.
Just I responded to Andrew's this line:
> Please remember that a +1 indicates that you will
> help rename everything!!!
No need for takin' it too seriously. There will be various
ways to accomplish the renaming.
Just enumerated the task list. (to help rename everything)
-- Tetsuya (tetsuya@apache.org)
On Wed, 30 Jul 2003 20:34:34 +1000
(Subject: Re: [VOTE] Effect a naming policy g/POI/s//Poi/g)
Glen Stampoultzis <gs...@iinet.net.au> wrote:
>
> I don't understand what you are talking about.
>
> At 03:52 PM 30/07/2003, you wrote:
>
> >Forgot to mention:
> >(This vote result will be given as an official notice
> >to Jakarta PMC)
> >
> >There will be some step to change all the material in jakarta.apache.org
> >
> >1. change on jakarta-site2 module : this could be done by myself
> >(Tetsuya)
> >2. change on the List-Id:, Reply-To: Header of -dev, -user lists
> >(Infrastructure)
> >3. change on Apachewiki (Tetsuya)
> >4. Other materials: Please tell me if you notice.
> >
> >All the .java file had been sucessfully compiled. No problem
> >with website, too.
> >
> >Please take these above and below into consideration and let's vote!
> >
> >-- Tetsuya (tetsuya@apache.org)
> >
> >P.S. creation of jakarta-poi-3 module might be one of the best choices.
> >There could be *no* CVS change, whether case sensitive or not
> >
> >--
> >
> >On Wed, 30 Jul 2003 14:16:24 +0900
> >(Subject: Re: [VOTE] Effect a naming policy g/POI/s//Poi/g)
> >Tetsuya Kitahata <te...@apache.org> wrote:
> >
> > >
> > > I am not sure that renaming all the .java files might
> > > a good idea, however, I completed this ( 5 minites :-)
> > >
> > > There was no *build error*.
> > >
> > > Please vote with this fact taken into consideration >> all
> > >
> > > -- Tetsuya (tetsuya@apache.org)
> > >
> > > --
> > >
> > > On Wed, 30 Jul 2003 00:34:14 -0400
> > > (Subject: [VOTE] Effect a naming policy g/POI/s//Poi/g)
> > > "Andrew C. Oliver" <ac...@apache.org> wrote:
> > >
> > > > Let me put this the right way. This vote will be conducted by the Apache
> > > > voting rules as documented here:
> > > >
> > > > http://jakarta.apache.org/site/decisions.html
> > > > http://httpd.apache.org/dev/guidelines.html
> > > >
> > > >
> > > > Note specifically:
> > > >
> > > > The act of voting carries certain obligations. Voting members
> > are not only
> > > > stating their opinion, they are also agreeing to help do the work.
> > > >
> > > > An action requiring consensus approval must receive at least 3 binding +1
> > > > votes and no binding vetos . An action requiring majority approval must
> > > > receive at least 3 binding +1 votes and more +1 votes than -1
> > votes. All
> > > > other action items are considered to have lazy approval until somebody
> > > > votes -1 , after which point they are decided by either consensus or
> > > > majority vote, depending on the type of action item.
> > > >
> > > > Product Changes
> > > >
> > > > Changes to the products of the Project, including code
> > and documentation,
> > > > will appear as action items in the status file. All product changes
> > to the
> > > > currently active repository are subject to lazy consensus.
> > > >
> > > > However, I'm opting to call a vote.
> > > >
> > > >
> > ===========================================================================
> > > >
> > > > Presently the policy is:
> > > >
> > > > So if you like acronyms, then POI is an acronym. If you hate them,
> > then we
> > > > just used the name of the food for our
> > > > project. If you wish to signify your love or hate for
> > > > acronyms, use POI or Poi to refer to the project respectively.
> > > >
> > > > I propose to CHANGE this policy to:
> > > >
> > > > Only Poi is the acceptable spelling, POI is not an acronym. You must use
> > > > Poi to refer to the project in all documentation. To preserve
> > consistency
> > > > with earlier releases all source code will use POI in class names and
> > poi in
> > > > package names.
> > > >
> > > > Please remember that a +1 indicates that you will help rename
> > everything!!!
> > > >
> > > > [X] +1 - I wish to enact this product change and will help
> > > > [ ] +0 - I wish it to happen but will not help
> > > > [ ] -0 - I don't wish it to happen but will not veto
> > > > [ ] -1 - I veto the proposal.
> > > >
> > > > This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
> > > > mentioned above, to carry it must receive 3 BINDING +1 votes (active
> > > > committers) and NO binding vetoes (-1).
> > > >
> > > > I expect that once this vote is complete that the matter should be
> > closed.
> > > >
> > > >
> > > > -Andy
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
>
> Glen Stampoultzis
> gstamp@iinet.net.au
> http://members.iinet.net.au/~gstamp/glen/
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Glen Stampoultzis <gs...@iinet.net.au>.
I don't understand what you are talking about.
At 03:52 PM 30/07/2003, you wrote:
>Forgot to mention:
>(This vote result will be given as an official notice
>to Jakarta PMC)
>
>There will be some step to change all the material in jakarta.apache.org
>
>1. change on jakarta-site2 module : this could be done by myself
>(Tetsuya)
>2. change on the List-Id:, Reply-To: Header of -dev, -user lists
>(Infrastructure)
>3. change on Apachewiki (Tetsuya)
>4. Other materials: Please tell me if you notice.
>
>All the .java file had been sucessfully compiled. No problem
>with website, too.
>
>Please take these above and below into consideration and let's vote!
>
>-- Tetsuya (tetsuya@apache.org)
>
>P.S. creation of jakarta-poi-3 module might be one of the best choices.
>There could be *no* CVS change, whether case sensitive or not
>
>--
>
>On Wed, 30 Jul 2003 14:16:24 +0900
>(Subject: Re: [VOTE] Effect a naming policy g/POI/s//Poi/g)
>Tetsuya Kitahata <te...@apache.org> wrote:
>
> >
> > I am not sure that renaming all the .java files might
> > a good idea, however, I completed this ( 5 minites :-)
> >
> > There was no *build error*.
> >
> > Please vote with this fact taken into consideration >> all
> >
> > -- Tetsuya (tetsuya@apache.org)
> >
> > --
> >
> > On Wed, 30 Jul 2003 00:34:14 -0400
> > (Subject: [VOTE] Effect a naming policy g/POI/s//Poi/g)
> > "Andrew C. Oliver" <ac...@apache.org> wrote:
> >
> > > Let me put this the right way. This vote will be conducted by the Apache
> > > voting rules as documented here:
> > >
> > > http://jakarta.apache.org/site/decisions.html
> > > http://httpd.apache.org/dev/guidelines.html
> > >
> > >
> > > Note specifically:
> > >
> > > The act of voting carries certain obligations. Voting members
> are not only
> > > stating their opinion, they are also agreeing to help do the work.
> > >
> > > An action requiring consensus approval must receive at least 3 binding +1
> > > votes and no binding vetos . An action requiring majority approval must
> > > receive at least 3 binding +1 votes and more +1 votes than -1
> votes. All
> > > other action items are considered to have lazy approval until somebody
> > > votes -1 , after which point they are decided by either consensus or
> > > majority vote, depending on the type of action item.
> > >
> > > Product Changes
> > >
> > > Changes to the products of the Project, including code
> and documentation,
> > > will appear as action items in the status file. All product changes
> to the
> > > currently active repository are subject to lazy consensus.
> > >
> > > However, I'm opting to call a vote.
> > >
> > >
> ===========================================================================
> > >
> > > Presently the policy is:
> > >
> > > So if you like acronyms, then POI is an acronym. If you hate them,
> then we
> > > just used the name of the food for our
> > > project. If you wish to signify your love or hate for
> > > acronyms, use POI or Poi to refer to the project respectively.
> > >
> > > I propose to CHANGE this policy to:
> > >
> > > Only Poi is the acceptable spelling, POI is not an acronym. You must use
> > > Poi to refer to the project in all documentation. To preserve
> consistency
> > > with earlier releases all source code will use POI in class names and
> poi in
> > > package names.
> > >
> > > Please remember that a +1 indicates that you will help rename
> everything!!!
> > >
> > > [X] +1 - I wish to enact this product change and will help
> > > [ ] +0 - I wish it to happen but will not help
> > > [ ] -0 - I don't wish it to happen but will not veto
> > > [ ] -1 - I veto the proposal.
> > >
> > > This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
> > > mentioned above, to carry it must receive 3 BINDING +1 votes (active
> > > committers) and NO binding vetoes (-1).
> > >
> > > I expect that once this vote is complete that the matter should be
> closed.
> > >
> > >
> > > -Andy
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: poi-dev-help@jakarta.apache.org
Glen Stampoultzis
gstamp@iinet.net.au
http://members.iinet.net.au/~gstamp/glen/
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Tetsuya Kitahata <te...@apache.org>.
On Wed, 30 Jul 2003 02:05:19 -0400
"Andrew C. Oliver" <ac...@apache.org> wrote:
> On 7/30/03 1:52 AM, "Tetsuya Kitahata" <te...@apache.org> wrote:
> > P.S. creation of jakarta-poi-3 module might be one of the best choices.
> > There could be *no* CVS change, whether case sensitive or not
> There is not/was never a jakarta-poi-3 module. There is a CVS BRANCH in the
> jakarta-poi module for REL_2_BRANCH and the HEAD.
Yes there *is* not, however, it does not influence to the future of poi.
In the future we can create jakarta-poi-3 module, I said.
(Like jakarta-jetspeed-2 which was just created yesterday!)
Next, if we think about the creation of the *new* TLP,
it will be *new* fileformats-poi module. You (all) do not have to
think about the current CVS (case sensitive, not, etc. because
it will be *new* module)
-- Tetsuya (tetsuya@apache.org)
P.S. What I wrote is that we did not have to think about the
technical matter too seriously when thinking of this voting issue.
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by "Andrew C. Oliver" <ac...@apache.org>.
On 7/30/03 1:52 AM, "Tetsuya Kitahata" <te...@apache.org> wrote:
>
> P.S. creation of jakarta-poi-3 module might be one of the best choices.
> There could be *no* CVS change, whether case sensitive or not
>
There is not/was never a jakarta-poi-3 module. There is a CVS BRANCH in the
jakarta-poi module for REL_2_BRANCH and the HEAD.
-Andy
> --
>
> On Wed, 30 Jul 2003 14:16:24 +0900
> (Subject: Re: [VOTE] Effect a naming policy g/POI/s//Poi/g)
> Tetsuya Kitahata <te...@apache.org> wrote:
>
>>
>> I am not sure that renaming all the .java files might
>> a good idea, however, I completed this ( 5 minites :-)
>>
>> There was no *build error*.
>>
>> Please vote with this fact taken into consideration >> all
>>
>> -- Tetsuya (tetsuya@apache.org)
>>
>> --
>>
>> On Wed, 30 Jul 2003 00:34:14 -0400
>> (Subject: [VOTE] Effect a naming policy g/POI/s//Poi/g)
>> "Andrew C. Oliver" <ac...@apache.org> wrote:
>>
>>> Let me put this the right way. This vote will be conducted by the Apache
>>> voting rules as documented here:
>>>
>>> http://jakarta.apache.org/site/decisions.html
>>> http://httpd.apache.org/dev/guidelines.html
>>>
>>>
>>> Note specifically:
>>>
>>> The act of voting carries certain obligations. Voting members are not only
>>> stating their opinion, they are also agreeing to help do the work.
>>>
>>> An action requiring consensus approval must receive at least 3 binding +1
>>> votes and no binding vetos . An action requiring majority approval must
>>> receive at least 3 binding +1 votes and more +1 votes than -1 votes. All
>>> other action items are considered to have lazy approval until somebody
>>> votes -1 , after which point they are decided by either consensus or
>>> majority vote, depending on the type of action item.
>>>
>>> Product Changes
>>>
>>> Changes to the products of the Project, including code and documentation,
>>> will appear as action items in the status file. All product changes to the
>>> currently active repository are subject to lazy consensus.
>>>
>>> However, I'm opting to call a vote.
>>>
>>> ===========================================================================
>>>
>>> Presently the policy is:
>>>
>>> So if you like acronyms, then POI is an acronym. If you hate them, then we
>>> just used the name of the food for our
>>> project. If you wish to signify your love or hate for
>>> acronyms, use POI or Poi to refer to the project respectively.
>>>
>>> I propose to CHANGE this policy to:
>>>
>>> Only Poi is the acceptable spelling, POI is not an acronym. You must use
>>> Poi to refer to the project in all documentation. To preserve consistency
>>> with earlier releases all source code will use POI in class names and poi in
>>> package names.
>>>
>>> Please remember that a +1 indicates that you will help rename everything!!!
>>>
>>> [X] +1 - I wish to enact this product change and will help
>>> [ ] +0 - I wish it to happen but will not help
>>> [ ] -0 - I don't wish it to happen but will not veto
>>> [ ] -1 - I veto the proposal.
>>>
>>> This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
>>> mentioned above, to carry it must receive 3 BINDING +1 votes (active
>>> committers) and NO binding vetoes (-1).
>>>
>>> I expect that once this vote is complete that the matter should be closed.
>>>
>>>
>>> -Andy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Tetsuya Kitahata <te...@apache.org>.
Forgot to mention:
(This vote result will be given as an official notice
to Jakarta PMC)
There will be some step to change all the material in jakarta.apache.org
1. change on jakarta-site2 module : this could be done by myself
(Tetsuya)
2. change on the List-Id:, Reply-To: Header of -dev, -user lists
(Infrastructure)
3. change on Apachewiki (Tetsuya)
4. Other materials: Please tell me if you notice.
All the .java file had been sucessfully compiled. No problem
with website, too.
Please take these above and below into consideration and let's vote!
-- Tetsuya (tetsuya@apache.org)
P.S. creation of jakarta-poi-3 module might be one of the best choices.
There could be *no* CVS change, whether case sensitive or not
--
On Wed, 30 Jul 2003 14:16:24 +0900
(Subject: Re: [VOTE] Effect a naming policy g/POI/s//Poi/g)
Tetsuya Kitahata <te...@apache.org> wrote:
>
> I am not sure that renaming all the .java files might
> a good idea, however, I completed this ( 5 minites :-)
>
> There was no *build error*.
>
> Please vote with this fact taken into consideration >> all
>
> -- Tetsuya (tetsuya@apache.org)
>
> --
>
> On Wed, 30 Jul 2003 00:34:14 -0400
> (Subject: [VOTE] Effect a naming policy g/POI/s//Poi/g)
> "Andrew C. Oliver" <ac...@apache.org> wrote:
>
> > Let me put this the right way. This vote will be conducted by the Apache
> > voting rules as documented here:
> >
> > http://jakarta.apache.org/site/decisions.html
> > http://httpd.apache.org/dev/guidelines.html
> >
> >
> > Note specifically:
> >
> > The act of voting carries certain obligations. Voting members are not only
> > stating their opinion, they are also agreeing to help do the work.
> >
> > An action requiring consensus approval must receive at least 3 binding +1
> > votes and no binding vetos . An action requiring majority approval must
> > receive at least 3 binding +1 votes and more +1 votes than -1 votes. All
> > other action items are considered to have lazy approval until somebody
> > votes -1 , after which point they are decided by either consensus or
> > majority vote, depending on the type of action item.
> >
> > Product Changes
> >
> > Changes to the products of the Project, including code and documentation,
> > will appear as action items in the status file. All product changes to the
> > currently active repository are subject to lazy consensus.
> >
> > However, I'm opting to call a vote.
> >
> > ===========================================================================
> >
> > Presently the policy is:
> >
> > So if you like acronyms, then POI is an acronym. If you hate them, then we
> > just used the name of the food for our
> > project. If you wish to signify your love or hate for
> > acronyms, use POI or Poi to refer to the project respectively.
> >
> > I propose to CHANGE this policy to:
> >
> > Only Poi is the acceptable spelling, POI is not an acronym. You must use
> > Poi to refer to the project in all documentation. To preserve consistency
> > with earlier releases all source code will use POI in class names and poi in
> > package names.
> >
> > Please remember that a +1 indicates that you will help rename everything!!!
> >
> > [X] +1 - I wish to enact this product change and will help
> > [ ] +0 - I wish it to happen but will not help
> > [ ] -0 - I don't wish it to happen but will not veto
> > [ ] -1 - I veto the proposal.
> >
> > This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
> > mentioned above, to carry it must receive 3 BINDING +1 votes (active
> > committers) and NO binding vetoes (-1).
> >
> > I expect that once this vote is complete that the matter should be closed.
> >
> >
> > -Andy
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by "Andrew C. Oliver" <ac...@apache.org>.
On 7/30/03 1:16 AM, "Tetsuya Kitahata" <te...@apache.org> wrote:
>
> I am not sure that renaming all the .java files might
> a good idea, however, I completed this ( 5 minites :-)
>
> There was no *build error*.
>
> Please vote with this fact taken into consideration >> all
>
The vote specifically excludes this. The existing naming convention is
preserved. It would just be way too disruptive to do otherwise (have to
deal with the CVS history, non-case-sensitive operating systems interacting
with CVS, etc...big big pain...getting it to compile is nothing). If you
wish to vote to do that (which would be another product change) we can do
so..you of course know what my vote would be.
-Andy
> -- Tetsuya (tetsuya@apache.org)
>
> --
>
> On Wed, 30 Jul 2003 00:34:14 -0400
> (Subject: [VOTE] Effect a naming policy g/POI/s//Poi/g)
> "Andrew C. Oliver" <ac...@apache.org> wrote:
>
>> Let me put this the right way. This vote will be conducted by the Apache
>> voting rules as documented here:
>>
>> http://jakarta.apache.org/site/decisions.html
>> http://httpd.apache.org/dev/guidelines.html
>>
>>
>> Note specifically:
>>
>> The act of voting carries certain obligations. Voting members are not only
>> stating their opinion, they are also agreeing to help do the work.
>>
>> An action requiring consensus approval must receive at least 3 binding +1
>> votes and no binding vetos . An action requiring majority approval must
>> receive at least 3 binding +1 votes and more +1 votes than -1 votes. All
>> other action items are considered to have lazy approval until somebody
>> votes -1 , after which point they are decided by either consensus or
>> majority vote, depending on the type of action item.
>>
>> Product Changes
>>
>> Changes to the products of the Project, including code and documentation,
>> will appear as action items in the status file. All product changes to the
>> currently active repository are subject to lazy consensus.
>>
>> However, I'm opting to call a vote.
>>
>> ===========================================================================
>>
>> Presently the policy is:
>>
>> So if you like acronyms, then POI is an acronym. If you hate them, then we
>> just used the name of the food for our
>> project. If you wish to signify your love or hate for
>> acronyms, use POI or Poi to refer to the project respectively.
>>
>> I propose to CHANGE this policy to:
>>
>> Only Poi is the acceptable spelling, POI is not an acronym. You must use
>> Poi to refer to the project in all documentation. To preserve consistency
>> with earlier releases all source code will use POI in class names and poi in
>> package names.
>>
>> Please remember that a +1 indicates that you will help rename everything!!!
>>
>> [X] +1 - I wish to enact this product change and will help
>> [ ] +0 - I wish it to happen but will not help
>> [ ] -0 - I don't wish it to happen but will not veto
>> [ ] -1 - I veto the proposal.
>>
>> This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
>> mentioned above, to carry it must receive 3 BINDING +1 votes (active
>> committers) and NO binding vetoes (-1).
>>
>> I expect that once this vote is complete that the matter should be closed.
>>
>>
>> -Andy
>>
>>
>> ---
>> Andrew C. Oliver
>> http://www.superlinksoftware.com/poi.jsp
>> Custom enhancements and Commercial Implementation for Jakarta POI
>>
>> http://jakarta.apache.org/poi
>> For Java and Excel, Got POI?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
> -----------------------------------------------------
> Tetsuya Kitahata -- Terra-International, Inc.
> E-mail: tetsuya@apache.org
> http://www.terra-intl.com/
> (Apache Jakarta Translation, Japanese)
> http://jakarta.terra-intl.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
Re: [VOTE] Effect a naming policy g/POI/s//Poi/g
Posted by Tetsuya Kitahata <te...@apache.org>.
I am not sure that renaming all the .java files might
a good idea, however, I completed this ( 5 minites :-)
There was no *build error*.
Please vote with this fact taken into consideration >> all
-- Tetsuya (tetsuya@apache.org)
--
On Wed, 30 Jul 2003 00:34:14 -0400
(Subject: [VOTE] Effect a naming policy g/POI/s//Poi/g)
"Andrew C. Oliver" <ac...@apache.org> wrote:
> Let me put this the right way. This vote will be conducted by the Apache
> voting rules as documented here:
>
> http://jakarta.apache.org/site/decisions.html
> http://httpd.apache.org/dev/guidelines.html
>
>
> Note specifically:
>
> The act of voting carries certain obligations. Voting members are not only
> stating their opinion, they are also agreeing to help do the work.
>
> An action requiring consensus approval must receive at least 3 binding +1
> votes and no binding vetos . An action requiring majority approval must
> receive at least 3 binding +1 votes and more +1 votes than -1 votes. All
> other action items are considered to have lazy approval until somebody
> votes -1 , after which point they are decided by either consensus or
> majority vote, depending on the type of action item.
>
> Product Changes
>
> Changes to the products of the Project, including code and documentation,
> will appear as action items in the status file. All product changes to the
> currently active repository are subject to lazy consensus.
>
> However, I'm opting to call a vote.
>
> ===========================================================================
>
> Presently the policy is:
>
> So if you like acronyms, then POI is an acronym. If you hate them, then we
> just used the name of the food for our
> project. If you wish to signify your love or hate for
> acronyms, use POI or Poi to refer to the project respectively.
>
> I propose to CHANGE this policy to:
>
> Only Poi is the acceptable spelling, POI is not an acronym. You must use
> Poi to refer to the project in all documentation. To preserve consistency
> with earlier releases all source code will use POI in class names and poi in
> package names.
>
> Please remember that a +1 indicates that you will help rename everything!!!
>
> [X] +1 - I wish to enact this product change and will help
> [ ] +0 - I wish it to happen but will not help
> [ ] -0 - I don't wish it to happen but will not veto
> [ ] -1 - I veto the proposal.
>
> This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
> mentioned above, to carry it must receive 3 BINDING +1 votes (active
> committers) and NO binding vetoes (-1).
>
> I expect that once this vote is complete that the matter should be closed.
>
>
> -Andy
>
>
> ---
> Andrew C. Oliver
> http://www.superlinksoftware.com/poi.jsp
> Custom enhancements and Commercial Implementation for Jakarta POI
>
> http://jakarta.apache.org/poi
> For Java and Excel, Got POI?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
-----------------------------------------------------
Tetsuya Kitahata -- Terra-International, Inc.
E-mail: tetsuya@apache.org
http://www.terra-intl.com/
(Apache Jakarta Translation, Japanese)
http://jakarta.terra-intl.com/
[RESULTS] Effect a naming policy g/POI/s//Poi/g
Posted by "Andrew C. Oliver" <ac...@apache.org>.
The motion failed to pass.
+1 = 1 vote
-0 = 1 vote
To pass it required 3 +1 votes and not -1s.
Lets move on now please. Regardless of personal preference lets put the
community first. We don't have consensus on this, can never achieve
consensus on this. That¹s why the policy was set to either in the first
place.
Tetsuya's issue seems to be primarily based on an issue with his editor not
knowing which is correct POI or Poi. I have offered off-list to write his
editor.
Let us always remember what the project is about: writing great code and
working with great guys. The details REALLY TRULY don't matter. It is
important that we stick together and work together. It is important that we
work towards things we CAN agree on and come up with inclusive ways to deal
with things that we can't.
We have a precedent of working in this way and if that¹s me not letting go
of my baby then DAMN STRAIGHT. And neither should you.
There are some people on this project with pretty strong opinions and hard
heads and that is why we must always find the middle road. The one with
either two winners or no losers.
Lets get 2.0 out the door! I want to have some fun again! Lets make 3.0
into a hummer instead of a Hummer* ;-)
-Andy
* - a consumer version of a US mechanized infantry vehicle which has become
popular. Its most notable for being HUGE, taking a lot of gas and looking
like a big box. Very popular now a days... (logic however has fallen from
favor)
On 7/30/03 12:34 AM, "Andrew C. Oliver" <ac...@apache.org> wrote:
> Let me put this the right way. This vote will be conducted by the Apache
> voting rules as documented here:
>
> http://jakarta.apache.org/site/decisions.html
> http://httpd.apache.org/dev/guidelines.html
>
>
> Note specifically:
>
> The act of voting carries certain obligations. Voting members are not only
> stating their opinion, they are also agreeing to help do the work.
>
> An action requiring consensus approval must receive at least 3 binding +1
> votes and no binding vetos . An action requiring majority approval must
> receive at least 3 binding +1 votes and more +1 votes than -1 votes. All
> other action items are considered to have lazy approval until somebody
> votes -1 , after which point they are decided by either consensus or
> majority vote, depending on the type of action item.
>
> Product Changes
>
> Changes to the products of the Project, including code and documentation,
> will appear as action items in the status file. All product changes to the
> currently active repository are subject to lazy consensus.
>
> However, I'm opting to call a vote.
>
> ===========================================================================
>
> Presently the policy is:
>
> So if you like acronyms, then POI is an acronym. If you hate them, then we
> just used the name of the food for our
> project. If you wish to signify your love or hate for
> acronyms, use POI or Poi to refer to the project respectively.
>
> I propose to CHANGE this policy to:
>
> Only Poi is the acceptable spelling, POI is not an acronym. You must use
> Poi to refer to the project in all documentation. To preserve consistency
> with earlier releases all source code will use POI in class names and poi in
> package names.
>
> Please remember that a +1 indicates that you will help rename everything!!!
>
> [ ] +1 - I wish to enact this product change and will help
> [ ] +0 - I wish it to happen but will not help
> [ ] -0 - I don't wish it to happen but will not veto
> [ ] -1 - I veto the proposal.
>
> This vote will end at Thursday Friday August 1 at 00:30:00 EST. As
> mentioned above, to carry it must receive 3 BINDING +1 votes (active
> committers) and NO binding vetoes (-1).
>
> I expect that once this vote is complete that the matter should be closed.
>
>
> -Andy
>
>
> ---
> Andrew C. Oliver
> http://www.superlinksoftware.com/poi.jsp
> Custom enhancements and Commercial Implementation for Jakarta POI
>
> http://jakarta.apache.org/poi
> For Java and Excel, Got POI?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/