Sorry, I understand the sigh. I would support this.
Ciao,
Rex
At 4:50 PM -0500 2/18/04, Christopher B Ferris wrote:
>Sigh,
>
>I only meant that both eclipse and netbeans offer useful front-ends. Of
>course, they are both
>Open Source projects and as such non-proprietary, but all that aside...
>the point is that there
>are a gazillion CVS clients available. You don't like one, you have a sea
>of others from which
>to choose. You can use any platform you like as well.
>
>As the old French adage goes "chacun en son gout!".
>
>Cheers,
>
>Christopher Ferris
>STSM, Emerging e-business Industry Architecture
>email:
>blog: http://webpages.charter.net/chrisfer/blog.html
>phone: +1 508 377 9295
>
>Rex Brooks <> wrote on 02/18/2004 05:30:16 PM:
>
>> I'm in the process of reading and reviewing this thread, having read
>> the document Karl sent out yesterday, and I plan to summarize my own
>> thoughts at the current end, when I get there, but in the meantime,
>> when I come across a note like this one, I want to say that while
>> NetBeans works for me, I don't think it would fly for OASIS to be
>> tied to any proprietary solution.
>>
>> Ciao,
>> Rex
>>
>> At 9:54 AM -0500 2/18/04, Christopher B Ferris wrote:
>> >David,
>> >
>> >Have you seen WebCVS? CVS is NOT only accessible via the command-line.
>Not
>> >only that
>> >but there are a vast array of GUI clients available for CVS as well,
>> >including Eclipse and likely
>> >NetBeans.
>> >
>> >Cheers,
>> >
>> >Christopher Ferris
>> >STSM, Emerging e-business Industry Architecture
>> >email:
>> >blog: http://webpages.charter.net/chrisfer/blog.html
>> >phone: +1 508 377 9295
>> >
>> >"David RR Webber" <> wrote on 02/17/2004 11:13:50 PM:
>> >
>> >> Karl,
>> >>
>> >> Some of these seem like good ideas - but overall I sense this will
>> >> be cumbersome to use and hard to implement. CVS style
>> >> generally is more programmer friendly than user friendly.
>> >>
>> >> I'm really after something that's simpler and more predictable
>> >> than currently. I really do not want the system inventing
>> >> OASIS filenames for me - generally I have good reasons
>> >> for using certain file names - and then also - when it is
>> >> a spec' - I want to create that name myself before hand
>> >> and keep it - since I do not want to have to edit references
>> >> to whatever the system called it - assuming I can find that
>> >> out.
>> >>
>> >> The biggest thing by far is the persistent URLs - but I
>> >> liked Matt MacKenzies suggestion on this a few weeks
>> >> back. If persistent URLs means something like:
>> >>
>> >>
>> >> http://persistentURL.oasis-open.
>> >>
>>
>>org/committees/bcm/documents/kaviCVS/WE4X78/archive/ERYT67A/temporary/store/oasis.bcm.
>> >> word/draft/february/2004/WT5677/more/draft.120304.bcm.doc
>> >>
>> >> That's not what I have in mind! Shorter is MUCH better.
>> >>
>> >> The idea of being able to see Access counts is excellent,
>> >> that would be helpful.
>> >>
>> >> If the system could automatically track when one document
>> >> is replacing another and keep a history tree - that would be
>> >> a plus. But this should be simply driven with a drop-down
>> >> list of recently uploaded documents. We definately
>> >> do not want to be writing CVS style command line
>> >> storage instructions!
>> >>
>> >> Thanks, DW.
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Karl F. Best" <>
>> >> To: "Chairs OASIS" <>; "Jeff Lomas"
>> >> <>
>> >> Sent: Tuesday, February 17, 2004 2:48 PM
>> >> Subject: [chairs] need your comments on DocMgmt system requirements
>> >>
>> >>
>> >> > TC Chairs, Secretaries:
>> >> >
>> >> > Early last month I sent out a request for your input on priorities
>for
>> >> > new functionality that OASIS needs to provide to the TCs. It's
>obvious
>> >> > that our first priority needs to be a document management system.
>> >OASIS
>> >> > management and technical staff have agreed to this.
>> >> >
>> >> > I've put together a draft functional requirements document for
>this
>> >doc
>> >> > mgmt system and would like to get your feedback. It is very
>important
>> >> > that we have the requirements correct and complete before we start
>> >> > development of the project -- many of you are developers so I'm
>sure
>> >> > that you understand the importance of this.
>> >> >
>> >> > Please send your comments in the next week or so if at all
>possible.
>> >> > Jeff Lomas, our Technology Services manager, and I will be
>finalizing
>> >> > these requirements and starting system design and development by
>the
>> >end
>> >> > of this month.
>> >> >
>> >> >
>> >> > -Karl
>> >> >
>> >> > =================================================================
>> >> > Karl F. Best
>> >> > Vice President, OASIS
>> >> > office +1 978.667.5115 x206 mobile +1 978.761.1648
>> >> > http://www.oasis-open.org
>> > > >
>> >>
>>
>>
>> --
>> Rex Brooks
>> GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
>> W3Address: http://www.starbourne.com
>> Email:
>> Tel: 510-849-2309
>> Fax: By Request
--
Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email:
Tel: 510-849-2309
Fax: By Request
