ipsframework-fus-comp — Developers and users of fusion-related IPS components

[David E. B. <ber...@or...>]

In conjunction with our new AToM integrated modeling project, we're
beginning to make a serious push to move all IPS and component activity
away from cswim.org and over to sourceforge.

We've had for some time an SVN repo for the IPS framework (only the
framework, no components).  That's at
https://svn.code.sf.net/p/ipsframework/code/trunk

Within the same SourceForge project ("ipsframework"), I have established
a SEPARATE SVN repository to start collecting the fusion-related
components.  That's at https://svn.code.sf.net/p/ipsframework/fus-comp/trunk

The idea is that the framework and the fus-comp trees will live
"side-by-side" in users' work space.  As there are publishable
components from other communities using IPS, they could have their own
repositories, or even their own SourceForge projects.

Presently, the ipsframeworks project has a single "Developers" group
which has (write) access to both repositories.  If it proves desirable,
we can easily change that at a later date, so that there are distinct
developer groups for the framework and for fusion components and users
can be in just one or both groups.  I figure this is a change we can
make easily enough at a later date.

Similarly, most other tools (i.e. tickets) are now handled at the
project level, but in most cases, we can later separate them, as needed.

I did add a new mailing list for people primarily interested in fusion
components (this is the first message on that list).  Feel free to
remove yourself if you don't want to be here.  The -devel and -users
lists remain for the framework (not much used, so far).  And we can
easily add more lists to segregate the fusion components people into
developers and users, if that seems useful.

I expect the fus-comp repo to be populated incrementally.  David Green
will probably be the first, with some new stuff that already exists at
GA.  I recommend we migrate components from the SWIM repo according to
their current usage.

My plan is that once we've got a few components in place and a build and
documentation system for them to fit into, I'll announce on the old SWIM
mailing list that we're beginning to migrate.

I think we'll want to capture (nearly) everything that was in the SWIM
repo for archaeological purposes, but a reasonable fraction of it may
never make the transition to working components in the new repo.  That
will depend primarily on usage and interest on the part of the component
developers/maintainers.

Discussion welcome.  Also, suggestions for immediate additions to the
list and/or developers group (write access to the repo).
-- 
David E. Bernholdt                | Email: ber...@or...
Oak Ridge National Laboratory     | Phone: +1 865-574-3147
http://www.csm.ornl.gov/~bernhold | Fax:   +1 865-576-5491