You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by te...@apache.org on 2003/07/29 12:40:19 UTC
cvs commit: jakarta-poi/src/documentation/content/xdocs/trans book.xml guidelines.xml index.xml
tetsuya 2003/07/29 03:40:19
Modified: src/documentation/content/xdocs casestudies.xml
src/documentation/content/xdocs/getinvolved book.xml
src/documentation/content/xdocs/trans book.xml
guidelines.xml index.xml
Log:
FIXED miscs (mail.html --> mail2.html etc)
Revision Changes Path
1.6 +14 -14 jakarta-poi/src/documentation/content/xdocs/casestudies.xml
Index: casestudies.xml
===================================================================
RCS file: /home/cvs/jakarta-poi/src/documentation/content/xdocs/casestudies.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- casestudies.xml 24 Jul 2003 16:45:19 -0000 1.5
+++ casestudies.xml 29 Jul 2003 10:40:18 -0000 1.6
@@ -3,7 +3,7 @@
<document>
<header>
- <title>Jakarta POI - Case Studies</title>
+ <title>Jakarta Poi - Case Studies</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person id="CR" name="Cameron Riley" email="crileyNO@SPAMekmail.com"/>
@@ -26,21 +26,21 @@
<title>Submitting a Case Study</title>
<p>
We are actively seeking case studies for this page (after all it
- just started). Andy Oliver (acoliver at apache dot org) has
+ just started). Andrew C. Oliver (acoliver at apache dot org) has
agreed to have a few T-Shirts printed with the POI logo (once its
chosen) for the first
few best submissions. To submit a case study, either
<link href="http://jakarta.apache.org/poi/getinvolved/index.html">
- submit a patch for this page</link> (preferred) or email it to the
- <link href="http://jakarta.apache.org/site/mail.html">mailing list
- </link>.
+ submit a patch for this page</link> or email it to the
+ <link href="http://jakarta.apache.org/site/mail2.html#poi">mailing list
+ </link> (with [PATCH] prefixed subject, please).
</p>
</section>
<section>
<title>Case Studies</title>
<section><title>Sunshine Systems</title>
<p>
- <link href="http://www.sunshinesys.com">Sunshine Systems</link> deveveloped a
+ <link href="http://www.sunshinesys.com/">Sunshine Systems</link> deveveloped a
POI based reporting solution for a price optimization software package which
is used by major retail chains.
</p>
@@ -82,11 +82,11 @@
<title>Bank of Lithuania</title>
<p>
The
- <link href="http://www.lbank.lt">Bank of Lithuania</link>
+ <link href="http://www.lbank.lt/">Bank of Lithuania</link>
reports financial statistical data to Excel format using the
- <link href="http://jakarta.apache.org/poi">Jakarta POI</link>
+ <link href="http://jakarta.apache.org/poi/">Jakarta POI</link>
project's
- <link href="http://jakarta.apache.org/poi/hssf">
+ <link href="http://jakarta.apache.org/poi/hssf/">
HSSF</link> API. The system is based on Oracle JServer and
utilizes a Java stored procedure that outputs to XLS format
using the HSSF API. - Arian Lashkov (alaskov at lbank.lt)
@@ -95,7 +95,7 @@
<section>
<title>Bit Tracker by Tracker Inc., and ThinkVirtual</title>
<p>
- Bit Tracker (http://www.bittracker.com) is the world's first and only web-based drill bit tracking system to manage your company's critical bit information and use that data to its full potential. It manages all bit related data, including their usage, locations, how they were used, and results such as rate of penetration and dull grade after use. This data needs to be available in Excel format for backwards compatibility and other uses in the industry. After using CSV and HTML formats, we needed something better for creating the spreadsheets and POI is the answer. It works great and was easy to implement. Kudos to the POI team.
+ Bit Tracker (http://www.bittracker.com/) is the world's first and only web-based drill bit tracking system to manage your company's critical bit information and use that data to its full potential. It manages all bit related data, including their usage, locations, how they were used, and results such as rate of penetration and dull grade after use. This data needs to be available in Excel format for backwards compatibility and other uses in the industry. After using CSV and HTML formats, we needed something better for creating the spreadsheets and POI is the answer. It works great and was easy to implement. Kudos to the POI team.
</p>
<p>
Travis Reeder (travis at thinkvirtual dot com)
@@ -125,7 +125,7 @@
<section>
<title>ClickFind</title>
<p>
- <link href="http://www.clickfind.com">ClickFind Inc.</link> used the POI
+ <link href="http://www.clickfind.com/">ClickFind Inc.</link> used the POI
projects HSSF API to provide their medical
research clients with an Excel export from their electronic data
collection web service Data Collector 3.0. The POI team's assistance
@@ -140,11 +140,11 @@
<section>
<title>IKAN Software NV</title>
<p>In addition to Change Management and Database Modelling, IKAN Software NV
- (http://www.ikan.be) develops and supports its own ETL
+ (http://www.ikan.be/) develops and supports its own ETL
(Extract/Transform/Load) tools.</p>
<p>IKAN's latest product is this domain is called ETL4ALL
- (http://www.ikan.be/etl4all). ETL4ALL is an open source tool
+ (http://www.ikan.be/etl4all/). ETL4ALL is an open source tool
allowing data transfer from and to virtually any data source. Users can
combine and examine data stored in relational databases, XML databases, PDF
files, EDI, CSV files, etc.
1.4 +1 -1 jakarta-poi/src/documentation/content/xdocs/getinvolved/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/jakarta-poi/src/documentation/content/xdocs/getinvolved/book.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- book.xml 17 Jun 2003 03:20:53 -0000 1.3
+++ book.xml 29 Jul 2003 10:40:18 -0000 1.4
@@ -13,7 +13,7 @@
<menu label="Get Involved">
<menu-item label="Contributing" href="index.html"/>
<menu-item label="Branching" href="branching.html"/>
- <menu-item label="Mail Lists" href="http://jakarta.apache.org/site/mail.html"/>
+ <menu-item label="Mail Lists" href="http://jakarta.apache.org/site/mail2.html#poi"/>
</menu>
</book>
1.5 +1 -1 jakarta-poi/src/documentation/content/xdocs/trans/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/jakarta-poi/src/documentation/content/xdocs/trans/book.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- book.xml 16 Jun 2003 06:00:05 -0000 1.4
+++ book.xml 29 Jul 2003 10:40:19 -0000 1.5
@@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "./dtd/book-cocoon-v10.dtd">
<book software="Poi"
- title="POI Documentation Translations"
+ title="Poi Documentation Translations"
copyright="@year@ Poi Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
1.5 +2 -2 jakarta-poi/src/documentation/content/xdocs/trans/guidelines.xml
Index: guidelines.xml
===================================================================
RCS file: /home/cvs/jakarta-poi/src/documentation/content/xdocs/trans/guidelines.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- guidelines.xml 16 Jun 2003 05:57:18 -0000 1.4
+++ guidelines.xml 29 Jul 2003 10:40:19 -0000 1.5
@@ -3,7 +3,7 @@
<document>
<header>
- <title>Welcome to POI</title>
+ <title>Welcome to POI -- Poi Website Translation Guildeline</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person id="TK" name="Tetsuya Kitahata" email="tetsuya@apache.org"/>
1.5 +4 -4 jakarta-poi/src/documentation/content/xdocs/trans/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-poi/src/documentation/content/xdocs/trans/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 16 Jun 2003 05:58:18 -0000 1.4
+++ index.xml 29 Jul 2003 10:40:19 -0000 1.5
@@ -3,7 +3,7 @@
<document>
<header>
- <title>POI Documentation Translations</title>
+ <title>The Apache Jakarta Poi Documentation Translations</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
</authors>
@@ -32,9 +32,9 @@
<td><link href="de/index.html">link</link></td></tr>
<tr><td>es</td><td>Spanish</td><td>Index page, some auxiliary pages translated</td><td>On</td>
<td><link href="es/index.html">link</link></td></tr>
- <tr><td>jp</td><td>Japanese</td><td>Complete XML translation</td><td>Off</td>
+ <tr><td>jp</td><td>Japanese</td><td>Complete XML translations and built with FORREST</td><td>Off</td>
<td><link href="http://jakarta.terra-intl.com/poi/">link</link></td></tr>
- <tr><td>kr</td><td>Korean</td><td>Conducted by <link href="http://jakarta.apache-korea.org/">Jakarta-Seoul-Project</link></td><td>Off</td>
+ <tr><td>kr</td><td>Korean</td><td>Conducted by <link href="http://jakarta.apache-korea.org/">Jakarta-Seoul-Project</link>.</td><td>Off</td>
<td><link href="http://jakarta.apache-korea.org/poi/">link</link></td></tr>
</table>
</section>
Re: cvs commit:
jakarta-poi/src/documentation/content/xdocs/trans book.xml guidelines.xml
index.xml
Posted by "Andrew C. Oliver" <ac...@apache.org>.
On 7/29/03 9:17 PM, "Tetsuya Kitahata" <te...@apache.org> wrote:
> Glen, Rainer,
>
> To tell the truth, I also agree with this point.
>
> Especially, this line:
>
>> Vetoing the making of this decision was not cool
>
That doesn't matter. I do not consent. YOU DO NOT GET TO CHANGE THE APACHE
VOTING RULES!!!! There is no discussion on this! If you don't like the
voting rules go talk to the board. I've PASTED YOU THE LINK. Show me WHERE
it says "Product changes are by Majority" in fact it says EXACTLY the
opposite. ONE guy's veto makes difference.
>
> Also, from my point of view, Andy's "veto" declaration was
> not cool.
> I declared, "this vote will be passed if the average of the
> votes will be greater than 0.5".. It meant, "This vote
> will not be passed even two(+1) and one(-1) .. at least we need
> three(+1) and less than one(-1)". And, vise versa.
> I thought, "this vote will not be passed, I know.
> But, there were no *conversation* (involve all the committers)
> about this issue before, it seems.
> The *process* will be precious rather than the *result*."
>
YOU DO NOT GET TO MAKE THE VOTING RULES! Tetsuya I'm really upset with both
you and Glen right now. I'm mostly upset with you because of suppositions
like this. When do you suppose the project was named? Why...2+ years ago.
How many committers were there? 2. Me and Marc Johnson. There was a
conversation, we didn't vote because it predated Apache and votes with two
people are just silly. However had there been a vote, it would have been
unanimous because Marc REALLY liked the name.
Now WHERE did you get the idea there was not a conversation? YOU pulled
this idea out of the air. Its insulting, its WRONG and I'm really feeling
attacked here.
> Andy's declaration was a bit against the community process, it seems.
> (I am very sad to say, however ...)
>
No your vote, your deciding YOUR OWN voting rules was totally against the
Apache community process. Remember the process protects the minority as
much as the majority. The issue is "Do we change the spelling to Poi" the
answer was -1 from me (and Rainer, et al). Its a product change so YOU must
get CONSENSUS. NOT MAJORITY.
I didn't make this Rule, APACHE DID. PLEASE read the voting rules before
proposing any more votes. YOU DO NOT get to decide the method of voting.
> There might be one more choice:
> 1. Product name: Jakarta Poi
> 2. Project name: Jakarta POI
>
No there is a third. Leave things the way they are. You're creating a vote
that is actually addressing two issues: "Adopt a naming convention" and
then what it should be. By not allowing us to vote against the first,
you're making a decision for us. This is a *consensus* based process which
means that little pedantic issues like spelling tend to be divisive which is
why I asked nicely several times "PLEASE STOP THIS" and well we're now going
on over a week discussing this.
You'll notice that all of the early decisions reflect a certain pragmatism
which said "We'll never agree on this so 'either is fine'". I bet Rainer
would like a policy which said everything was done POI versus Poi. So he'd
effect a policy and it would be based on his preference. I vote: LIVE and
LET LIVE. Why? Because these long running threads about something SILLY
don't have to happen. We can all get along and work together and be happy
by just avoiding pedantic discussions just like this one.
> -- Tetsuya (tetsuya@apache.org)
>
> P.S. Rather, is it better to be emphasized?
> "Why was there no vote on the fork of 3.0?"
>
Hey guess what Tetsuya:
http://marc.theaimsgroup.com/?l=poi-dev&m=105101098201136&w=2
http://marc.theaimsgroup.com/?l=poi-dev&m=105714993000768&w=2
I proposed it. Glen did it. No one disagreed. Whether we should have
called a vote, perhaps, it might have been considered something up to the
release manager and subject to lazy consensus. Now what we forgot to vote
on was the most recent release. My apologies to Rainer for that. I
basically just forgot because I didn't have much time to do the release and
Glen wasn't able to do it except for a limited amount of time.
Tetsuya, for someone who is relatively new to the project, has contributed
relatively little...do you think you should be stirring up this much
division this early into your committership?
-Andy
> --
>
> On Wed, 30 Jul 2003 09:53:34 +1000
> Glen Stampoultzis <gs...@iinet.net.au> wrote:
>
>>
>> Rainer, I agree.
>>
>> Although I preferred Poi I feel it's much more important to be
>> consistent. A simple vote would have cleared this whole point up and we
>> would no longer be having this conversation. Vetoing the making of this
>> decision was not cool and reflects an unwillingness on Andy's part to let
>> go of his baby.
>>
>> -- Glen
>>
>> At 07:02 AM 30/07/2003, you wrote:
>>>> It is not appropriate to go through the docs and change one to another,
>>>> however we have not indeed voted to change from the convention that both
>>>> are
>>>> acceptable. Spelling it Poi on new Doc's that are created is ATM
>>>> acceptable.
>>>
>>> This is a typical purely technical attitude. What do you think why
>>> Microsoft is so successful? Because of its superior quality products? Look
>>> and there marketing and learn! Do you think they don't care whether they
>>> spell it "Windows", "WINDOWS" or "wInDoWs"?
>>>
>>>
>>>> It REALLY bugs me that this issue is achieving greater importance than our
>>>> next release.
>>>
>>> Believe me, it is at least equally important. That "POI" or "Poi" spelling
>>> makes at least a sloppy impression. Impression counts. Would you rely your
>>> enterprise-critical application on a sloppy product. But wait, no, POI
>>> isn't a product: It does not even have a brand!
>>>
>>>
>>> Best regards
>>> Rainer ("out of town 'till Thursday") Klute
>
>
> ---------------------------------------------------------------------
> 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: cvs commit: jakarta-poi/src/documentation/content/xdocs/trans book.xml guidelines.xml index.xml
Posted by Tetsuya Kitahata <te...@apache.org>.
Glen, Rainer,
To tell the truth, I also agree with this point.
Especially, this line:
> Vetoing the making of this decision was not cool
--
My preference (opinion) is "Poi" rather than "POI".
Because
1. This project used this "POI" as acronym and the market knows
the *fact*.
2. Making all letters capitalized means "acronym". See the other
jakarta subprojects. (BSF,BCEL,ECS,ORO,...)
3. From marketing point of view, I am [+1] to "Poi", to wipe out
the dark image in the past.
--
Also, from my point of view, Andy's "veto" declaration was
not cool.
I declared, "this vote will be passed if the average of the
votes will be greater than 0.5".. It meant, "This vote
will not be passed even two(+1) and one(-1) .. at least we need
three(+1) and less than one(-1)". And, vise versa.
I thought, "this vote will not be passed, I know.
But, there were no *conversation* (involve all the committers)
about this issue before, it seems.
The *process* will be precious rather than the *result*."
Andy's declaration was a bit against the community process, it seems.
(I am very sad to say, however ...)
There might be one more choice:
1. Product name: Jakarta Poi
2. Project name: Jakarta POI
-- Tetsuya (tetsuya@apache.org)
P.S. Rather, is it better to be emphasized?
"Why was there no vote on the fork of 3.0?"
--
On Wed, 30 Jul 2003 09:53:34 +1000
Glen Stampoultzis <gs...@iinet.net.au> wrote:
>
> Rainer, I agree.
>
> Although I preferred Poi I feel it's much more important to be
> consistent. A simple vote would have cleared this whole point up and we
> would no longer be having this conversation. Vetoing the making of this
> decision was not cool and reflects an unwillingness on Andy's part to let
> go of his baby.
>
> -- Glen
>
> At 07:02 AM 30/07/2003, you wrote:
> > >It is not appropriate to go through the docs and change one to another,
> > >however we have not indeed voted to change from the convention that both are
> > >acceptable. Spelling it Poi on new Doc's that are created is ATM
> > >acceptable.
> >
> >This is a typical purely technical attitude. What do you think why
> >Microsoft is so successful? Because of its superior quality products? Look
> >and there marketing and learn! Do you think they don't care whether they
> >spell it "Windows", "WINDOWS" or "wInDoWs"?
> >
> >
> > >It REALLY bugs me that this issue is achieving greater importance than our
> > >next release.
> >
> >Believe me, it is at least equally important. That "POI" or "Poi" spelling
> >makes at least a sloppy impression. Impression counts. Would you rely your
> >enterprise-critical application on a sloppy product. But wait, no, POI
> >isn't a product: It does not even have a brand!
> >
> >
> >Best regards
> >Rainer ("out of town 'till Thursday") Klute
Re: cvs commit:
jakarta-poi/src/documentation/content/xdocs/trans book.xml
guidelines.xml index.xml
Posted by Glen Stampoultzis <gs...@iinet.net.au>.
Rainer, I agree.
Although I preferred Poi I feel it's much more important to be
consistent. A simple vote would have cleared this whole point up and we
would no longer be having this conversation. Vetoing the making of this
decision was not cool and reflects an unwillingness on Andy's part to let
go of his baby.
-- Glen
At 07:02 AM 30/07/2003, you wrote:
> >It is not appropriate to go through the docs and change one to another,
> >however we have not indeed voted to change from the convention that both are
> >acceptable. Spelling it Poi on new Doc's that are created is ATM
> >acceptable.
>
>This is a typical purely technical attitude. What do you think why
>Microsoft is so successful? Because of its superior quality products? Look
>and there marketing and learn! Do you think they don't care whether they
>spell it "Windows", "WINDOWS" or "wInDoWs"?
>
>
> >It REALLY bugs me that this issue is achieving greater importance than our
> >next release.
>
>Believe me, it is at least equally important. That "POI" or "Poi" spelling
>makes at least a sloppy impression. Impression counts. Would you rely your
>enterprise-critical application on a sloppy product. But wait, no, POI
>isn't a product: It does not even have a brand!
>
>
>Best regards
>Rainer ("out of town 'till Thursday") 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
>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: cvs commit: jakarta-poi/src/documentation/content/xdocs/trans
book.xml guidelines.xml index.xml
Posted by "Andrew C. Oliver" <ac...@apache.org>.
It is not appropriate to go through the docs and change one to another,
however we have not indeed voted to change from the convention that both are
acceptable. Spelling it Poi on new Doc's that are created is ATM
acceptable.
It REALLY bugs me that this issue is achieving greater importance than our
next release.
-Andy
On 7/29/03 8:57 AM, "rainer.klute@gmx.de" <ra...@gmx.de> wrote:
>> tetsuya 2003/07/29 03:40:19
>>
>> Modified: src/documentation/content/xdocs casestudies.xml
>> src/documentation/content/xdocs/getinvolved book.xml
>> src/documentation/content/xdocs/trans book.xml
>> guidelines.xml index.xml
>> Log:
>> FIXED miscs (mail.html --> mail2.html etc)
>
> Tetsuya,
>
> please stop changing "POI" to "Poi" and revert the changes you have made
> already! Thanks!
>
> Reasoning: For our public recognition and reputation we should demonstrate
> that we are at least able to spell our own name - and do so consistently. We
> have had our vote, so please stick to it!
>
> Best regards
> Rainer Klute
--
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: cvs commit: jakarta-poi/src/documentation/content/xdocs/trans book.xml guidelines.xml index.xml
Posted by ra...@gmx.de.
> tetsuya 2003/07/29 03:40:19
>
> Modified: src/documentation/content/xdocs casestudies.xml
> src/documentation/content/xdocs/getinvolved book.xml
> src/documentation/content/xdocs/trans book.xml
> guidelines.xml index.xml
> Log:
> FIXED miscs (mail.html --> mail2.html etc)
Tetsuya,
please stop changing "POI" to "Poi" and revert the changes you have made
already! Thanks!
Reasoning: For our public recognition and reputation we should demonstrate
that we are at least able to spell our own name - and do so consistently. We
have had our vote, so please stick to it!
Best regards
Rainer Klute
--
RAINER KLUTE IT-CONSULTING GMBH
Dipl.-Inform.
Rainer Klute klute@rainer-klute.de
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post