Experimental Physics and
Industrial Control System
| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Channel Access Protocol Specification |
| From: | Klemen Zagar <[email protected]> |
| To: | [email protected] |
| Date: | Thu, 04 Nov 2004 14:50:54 +0100 |
Lawrence Hoff wrote:
It seems to me that any of us who are capable of, and interested in assisting in this effort must organize ourselves in a way that allows such questions to be raised, understanding to be achieved, and clarifications to be made to the document. In some cases, such clarifications might even result in necessary changes to *existing* implementations (e.g. to address situations not previously anticipated, such as out-of-order packets).
Is COSYLab interested in setting up a Wiki or other collaborative environment so folks can pitch in and help out?
We have prepared a mailing list to which you can send any issues you might discover regarding the document. To subscribe, unsubscribe or view the list's archive, visit:
http://lists.cosylab.com/wws/info/lists-ca-spec
Everybody is invited to subscribe and contribute to this mailing list!
(For convenience, the 'mail' icons in the specification now point at this mailing list.)
About the document improvement process:
1. The process is open: anyone can contribute his ideas, views, comments, ... (the technical means to do so is the above mailing list)
2. The document is free: if anyone wishes to modify the document by volunteering to take responsibility for its maintenance in the future, Cosylab can give the sources for the document and instructions on how to produce the fancy HTML.
3. Cosylab will resolve any 'major or critical' issues reported before the 12th of August 2005. This is when the warranty period on the contract with Steve Hunt (who funded this version of the specification) will expire. 'Major or critical' issues are the reports where information in the document is incorrect.
4. Non-critical issues, such as
- change of document's structure - expansion of document's scope (e.g., to behavior or version differences)
will be processed when someone is interested enough to fund future work on the specification document (or takes over the document maintenance according to section 2).
5. The document status is 'draft' when it is still under preparation, and 'released' when it has been reviewed and approved by Jeff Hill (performed in June for this version of the document) and Cosylab's quality assurance. The validation is performed against the document's scope. We prefer to do reviews when there are bunches of changes, and not every change individually.
Best regards, Klemen.
--
_____________________ _ _ _ _ ____________________
|_| |_| |_| |_| |_|
Klemen Zagar Cosylab
Quality Manager http://www.cosylab.com
Email: [email protected] Teslova ulica 30
Phone: +386 (41) 341-846 SI-1000 Ljubljana
Slovenia
__ _ _ _ _ __________________ _ _ _ _ __
|_| |_| |_| |_| |_| |_| |_| |_| |_| |_|- Navigate by Date:
- Prev: Problem restoring some PVs with burtwb Burkhard Kolb
- Next: asyn3-3 external access Geoff Savage
- Index: 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
- Navigate by Thread:
- Prev: RE: Channel Access Protocol Specification Dalesio, Leo
- Next: asynDriver, devEpics user parameter access Geoff Savage
- Index: 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·