[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[epf-dev] RE: VOTE: OpenUp => New name for BUP++ (Sigurd Hopen)
|
I vote YES for OpenUp.
/Sigurd Hopen
2-Pro Mentor, Norway
+47 90689131
shopen@xxxxxxxxxxxxxx
www.2promentor.com
-----
From: "Asier Azaceta" <Asier.Azaceta@xxxxxx>
Subject: RE: [epf-dev] VOTE: OpenUp => New name for BUP++
To: "Eclipse Process Framework Project Developers List"
<epf-dev@xxxxxxxxxxx>
Message-ID: <2222905F268D384BBAF80AF4CF9C17D6024C68DF@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
I vote YES to the name change to OpenUp
Regards,
Asier Azaceta
mailto:asier.azaceta@xxxxxx <mailto:asier.azaceta@xxxxxx>
_____
From: Per Kroll [mailto:pkroll@xxxxxxxxxx]
Sent: Wednesday, April 12, 2006 9:39 PM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] VOTE: OpenUp => New name for BUP++
Hi,
we have now (finally) got legal clearance on using the name
OpenUp.
We had informal voting a few months ago, and the results was
anonnimously for OpenUp.
To get a formal voting record, I request that the committers
respond to this e-mail with a Yes, No, or Obstain vote regarding doing a
name change.
Majority vote rules.
Voters are committers per the list at
http://www.eclipse.org/epf/team/team.php
21 people listed under "Current Committers", "Voted to be
committers" + DJ <We need to update the committer list to state that
these 21 people are committers> can vote, all votes are equal.
Proposal to vote for:
- OpenUp denotes the process framework built on top of BUP,
including BUP.
- OpenUp/BUP denotes what is today called Basic Unified Process
(see http://www.eclipse.org/epf/bup_component/bup_vision.php)
- OpenUp/MDA denotes a potential future process in this
framework guiding you in how to develop software using an MDA approach
- OpenUp/<X> denotes a potential future process in this
framework guiding you in how to develop software using an <X> approach
"Open" in OpenUp signifies it's openess, as a result of being an
open source process.
"Up" signifies that it is the open source version of Unified
Process
Lowercase "p" signifies that OpenUp promotes process with a
lowercase 'p', rather than BIG P processes with a lot of overhead.
I cast a YES vote through this e-mail.
Thanks
Per Kroll
STSM, Manager Methods: RUP / RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
408-342-3815
********************************** DISCLAIMER
*******************************
This message may contain confidential, proprietary or legally privileged
information.
If you are not the intended recipient of this message, please notify it to
the sender and delete without resending or backing it, as it is legally
prohibited.
********************************** AVISO LEGAL
******************************
Este mensaje puede contener informacion confidencial, en propiedad o
legalmente protegida.
Si usted no es el destinatario, le rogamos lo comunique al remitente y
proceda a borrarlo, sin reenviarlo ni conservarlo, ya que su uso no
autorizado esta prohibido legalmente.
****************************************************************************
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/epf-dev/attachments/20060418/346df627/attachmen
t.html
------------------------------
Message: 3
Date: Tue, 18 Apr 2006 11:21:20 +0200
From: "Asier Azaceta" <Asier.Azaceta@xxxxxx>
Subject: RE: [epf-dev] VOTE: OpenUp => New name for BUP++
To: "Eclipse Process Framework Project Developers List"
<epf-dev@xxxxxxxxxxx>
Message-ID: <2222905F268D384BBAF80AF4CF9C17D6024C6922@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi Per,
I like OpenUP.
Regards,
Asier Azaceta
mailto:asier.azaceta@xxxxxx <mailto:asier.azaceta@xxxxxx>
_____
From: Per Kroll [mailto:pkroll@xxxxxxxxxx]
Sent: Friday, April 14, 2006 8:11 PM
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++
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
********************************** DISCLAIMER
*******************************
This message may contain confidential, proprietary or legally privileged
information.
If you are not the intended recipient of this message, please notify it to
the sender and delete without resending or backing it, as it is legally
prohibited.
********************************** AVISO LEGAL
******************************
Este mensaje puede contener informacion confidencial, en propiedad o
legalmente protegida.
Si usted no es el destinatario, le rogamos lo comunique al remitente y
proceda a borrarlo, sin reenviarlo ni conservarlo, ya que su uso no
autorizado esta prohibido legalmente.
****************************************************************************
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/epf-dev/attachments/20060418/d16ec7b0/attachmen
t.html
------------------------------
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
End of epf-dev Digest, Vol 4, Issue 66
**************************************