Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [epf-dev] VOTE: OpenUp => New name for BUP++

I think I have already voted on this but just for the record – yes I am favour of OpenUP.

 

Steve

 


From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Per Kroll
Sent: Tuesday, April 18, 2006 7:52 AM
To: Eclipse Process Framework Project Developers List
Cc: Eclipse Process Framework Project Developers List; epf-dev-bounces@xxxxxxxxxxx
Subject: RE: [epf-dev] VOTE: OpenUp => New name for BUP++

 


OK, so I vote OpenUP.
I need a couple of more votes to close this issue for good... :)

Cheers

Per Kroll
STSM, Manager Methods: RUP / RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
408-342-3815


Naveena Bereny/Cupertino/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx

04/18/2006 06:32 AM

Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

To

Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

cc

Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>, epf-dev-bounces@xxxxxxxxxxx

Subject

RE: [epf-dev] VOTE: OpenUp => New name for BUP++

 

 

 





Per,


I'm behind OpenUP for the following reasons:

1. The upper case lettering allows us to reference its origins which are from the UP.

2. The OpenUP is cosmetically better than OpenUp, and from a branding perspective, I think the former would look better in a logo than the latter.


Cheers

Naveena


Per Kroll/Cupertino/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx

04/14/2006 11:11 AM

Please respond to
Eclipse Process Framework Project Developers List

To

Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

cc

"'Eclipse Process Framework Project Developers List'" <epf-dev@xxxxxxxxxxx>, epf-dev-bounces@xxxxxxxxxxx

Subject

RE: [epf-dev] VOTE: OpenUp => New name for BUP++

 

 

 






Hi,


several people have approched me about whether to use OpenUP or OpenUp, and I realize that all the discussions on this issue before and after me sending the voting e-mail was done outside this public forum. So, I wanted to give people a chance to chip in.

The reason for lowercase is to denote that we talk about a "small process".

The reason for uppercase is to keep the connection to Unified Process, which still carries a lot of weight. Some people also think OpenUP looks better.


Opinions?


<There are no legal ramifications, they do not care about lower/uppercase.>


Cheers


Per Kroll
STSM, Manager Methods: RUP / RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
408-342-3815

"steve" <steve@xxxxxxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx

04/12/2006 02:03 PM

Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

 

To

"'Eclipse Process Framework Project Developers List'" <epf-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [epf-dev] VOTE: OpenUp => New name for BUP++



 

 






Hmmm, wouldn't that be "OpenUp or I'll UP your house down" :-)

Steve

-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Scott W. Ambler
Sent: Wednesday, April 12, 2006 1:51 PM
To: Eclipse Process Framework Project Developers List
Subject: RE: [epf-dev] VOTE: OpenUp => New name for BUP++

One observation.  A name like OpenUp leaves you vulnerable to big bad
wolf jokes.  e.g. "OpenUp or I'll develop your house down."

On a side note about the dangers of not thinking through the joke
potential of a name, a Canadian friend of mine just named his newborn
son "Robert Mackenzie".  Bob Mackenzie is a famous Canadian TV character.

- Scott

At 04:35 PM 4/12/2006, you wrote:

>I cast a Yes vote.
>
>Charlie Yan
>EPF Tooling Dev Lead
>Phone: 408-342-4681

====================================================
Scott W. Ambler  :-)
Senior Consultant, Ambysoft Inc.
www.ambysoft.com/scottAmbler.html

Refactoring Databases: Evolutionary Database Design
(www.ambysoft.com/books/refactoringDatabases.html) is now available!

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev



_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev


Back to the top