User: knarf Date: 2011/04/04 09:35 AM
Modified: / ET.tex
Log: more on design and strategy
File Changes:
Directory: / ============
File [modified]: ET.tex Delta lines: +8 -5 =================================================================== --- ET.tex 2011-04-04 14:29:53 UTC (rev 45) +++ ET.tex 2011-04-04 14:35:53 UTC (rev 46) @@ -252,7 +252,7 @@ other areas of science and hereby providing an immediate application of their research.
-\section{Design and Strategy\pages{1 Frank}} +\section{Design and Strategy\pages{0.5 Frank}}
The mechanisms for the development and support of the Einstein Toolkit are designed to be open, transparent and community driven. All the source code, @@ -266,9 +266,11 @@ discussion about the toolkit takes place on an open mail list ({\tt users@einsteintoolkit.org}). The regular weekly meetings for the Einstein Toolkit are open and the community is invited to -participate, and minutes are recorded on the wiki\todo{check}. The Einstein Toolkit +participate, and minutes are recorded and publicly available. The Einstein Toolkit blog requires users to first request a login, but then can be freely posted to. Any user can post comments to entries already on the blog. +The community heavily uses an issue tracking system +({\tt trac.einsteintoolkit.org}), with submissions open to everyone.
Despite the open design, some actions have to be restricted to a small group of maintainers. This is true for e.g. administrative tasks like the @@ -276,9 +278,10 @@ of spam. However, one of the most important tasks of an Einstein Toolkit Maintainer is also to review and apply patches sent by users, to ensure a high software quality level. Every substancial change or addition to -the toolkit has, by not enforced consensus, to be reviewed by another -Einstein Toolkit Maintainer, and is generally open for discussion on the -users mailing list. +the toolkit has to be reviewed by another Einstein Toolkit Maintainer, +and is generally open for discussion on the users mailing list. Despite this +not being enforced by technically it seems to work pretty well while at the +same time promoting development.
\section{Core Technologies\pages{0.5 Frank}}