I agree - too narrow since it names a spec. I wasn't thinking claiming
spec ownership, just giving people a clue.
So how narrow do you think? We have :
httpd
db
directory
logging
perl
portals
TCL
WS
XML
XMLGraphics
as project names that "cover" an area. Maybe HTTPD isn't one (Apache
BPELd?)
How about adding BPEL as a suffix?
Apache OpenBPEL is out - (OpenBPEL already exists...)
Apache Fielding? :)
geir
Roy T. Fielding wrote:
On Feb 16, 2006, at 10:08 AM, Geir Magnusson Jr wrote:
Could I presume to suggest something as obvious as "Apache BPEL" or
similar? makes it easier for people to grok what we're doing. I know
it's not terribly imaginative, but might make it easy for people to
recognize it as a BPEL project. (Like "ActiveBPEL")
-1 -- there should not be any more project names at Apache that claim
ownership of a functionality space.
....Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
