Collaboration Activities - Revision history

AndrewJohnson: Remove a few cob-webs...

2016-03-29T21:40:09Z

Remove a few cob-webs...

← Older revision		Revision as of 21:40, 29 March 2016
Line 1:		Line 1:
	== Current Activities within the EPICS Collaboration ==		== Current Activities within the EPICS Collaboration ==

	EPICS is a world-wide collaboration and relies upon its users to contribute to ongoing development and support of the software tools. To coordinate such activity, the diverse efforts are grouped into four categories with each category being coordinated by <volunteer> "category leads". The categories are described below with contact information for the category lead(s). A URL is ~~also provided~~ for more detailed information about the current activities in each category. Please feel free to contact the category lead(s) if you have any ideas or would be willing to contribute resources (either $$ or man-power) to specific activities.		EPICS is a world-wide collaboration and relies upon its users to contribute to ongoing development and support of the software tools. Since there is no central funding for EPICS development, there is also no format central organization for planning its future development, although many sites and users make contributions towards its continued relevence and usefulness. Coordination is generally organized or at least initiated through the [http://www.aps.anl.gov/epics/tech-talk/ tech-talk mailing list].

	~~=== [[Evolution of~~ EPICS ~~Core]] ===~~

	~~This category includes the efforts to define, plan, and implement near term (0-3 years) modifications and enhancements to the core EPICS software components (i.e. iocCore, Channel Access, SNL, etc).~~

	~~Category Lead: Bob Dalesio <[mailto:dalesio@slac.stanford.edu dalesio@slac.stanford.edu]>~~

	~~=== [[Fundamental Tools and Popular Extensions]] ===~~

	~~This category includes the efforts to define, enhance, and/or implement a set of tools that are imperative (or widely used) for any control system (display manager~~, ~~alarm handler, strip tool, archiver, etc). It~~ is ~~hoped that such tools will evolve to have a common look-and-feel, similar configuration mechanisms, and be tightly integrated.~~

	~~Category Lead: Matthias Clausen <[mailto:Matthias.Clausen@desy.de Matthias.Clausen@desy.de]>~~

	~~=== [[Collaboration Support]] ===~~

	~~This category includes the efforts to plan and coordinate the~~ organization ~~of documentation, training, work done by others (i.e. device support)~~, and ~~other tools to provide EPICS~~ users ~~with the information they need to fully leverage the vast~~ contributions ~~from~~ the ~~EPICS community.~~

	~~Category Leads: John Maclean <~~[~~mailto~~:~~jfm@aps~~.~~anl.gov jfm@~~aps.anl.gov]~~>, Ned Arnold <[mailto:nda@aps.anl.gov nda@aps~~.~~anl.gov]>~~

AndrewJohnson at 14:38, 22 June 2006

2006-06-22T14:38:50Z

← Older revision		Revision as of 14:38, 22 June 2006
Line 20:		Line 20:

	Category Leads: John Maclean <[mailto:jfm@aps.anl.gov jfm@aps.anl.gov]>, Ned Arnold <[mailto:nda@aps.anl.gov nda@aps.anl.gov]>		Category Leads: John Maclean <[mailto:jfm@aps.anl.gov jfm@aps.anl.gov]>, Ned Arnold <[mailto:nda@aps.anl.gov nda@aps.anl.gov]>

	~~=== [http://epics-research.org/ R&D for Future EPICS Capabilities] ===~~

	This category includes the efforts to investigate emerging technologies and evaluate how they may apply to future real-time control systems. Results from these activities will guide longer term EPICS capabilities and development.

	~~Category Lead: Steve Hunt <[mailto:hunt@psi.ch hunt@psi.ch]>~~

164.54.8.164: Link to epics-research.org

2005-02-03T16:36:08Z

Link to epics-research.org

New page

== Current Activities within the EPICS Collaboration ==

EPICS is a world-wide collaboration and relies upon its users to contribute to ongoing development and support of the software tools. To coordinate such activity, the diverse efforts are grouped into four categories with each category being coordinated by <volunteer> "category leads". The categories are described below with contact information for the category lead(s). A URL is also provided for more detailed information about the current activities in each category. Please feel free to contact the category lead(s) if you have any ideas or would be willing to contribute resources (either $$ or man-power) to specific activities.

=== [[Evolution of EPICS Core]] ===

This category includes the efforts to define, plan, and implement near term (0-3 years) modifications and enhancements to the core EPICS software components (i.e. iocCore, Channel Access, SNL, etc).

Category Lead: Bob Dalesio <[mailto:dalesio@slac.stanford.edu dalesio@slac.stanford.edu]>

=== [[Fundamental Tools and Popular Extensions]] ===

This category includes the efforts to define, enhance, and/or implement a set of tools that are imperative (or widely used) for any control system (display manager, alarm handler, strip tool, archiver, etc). It is hoped that such tools will evolve to have a common look-and-feel, similar configuration mechanisms, and be tightly integrated.

Category Lead: Matthias Clausen <[mailto:Matthias.Clausen@desy.de Matthias.Clausen@desy.de]>

=== [[Collaboration Support]] ===

This category includes the efforts to plan and coordinate the organization of documentation, training, work done by others (i.e. device support), and other tools to provide EPICS users with the information they need to fully leverage the vast contributions from the EPICS community.

Category Leads: John Maclean <[mailto:jfm@aps.anl.gov jfm@aps.anl.gov]>, Ned Arnold <[mailto:nda@aps.anl.gov nda@aps.anl.gov]>

=== [http://epics-research.org/ R&D for Future EPICS Capabilities] ===

This category includes the efforts to investigate emerging technologies and evaluate how they may apply to future real-time control systems. Results from these activities will guide longer term EPICS capabilities and development.

Category Lead: Steve Hunt <[mailto:hunt@psi.ch hunt@psi.ch]>