Changes in CPS mailing-lists hosting

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0474869546==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigE77A8D1153077813D4B23B09"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE77A8D1153077813D4B23B09
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear all,

the four mailing lists related to CPS have just moved to the
lists.cps-cms.org
domain, including all membership options and archives. Everything should
therefore
be about the same for you, apart from the addresses.

=46rom now on, the addresses at lists.nuxeo.com are obsolete. We can't
guarantee that
you'll be read if you post on them.

Many thanks to our friends at Nuxeo for their help on this operation,
that will
allow us to manage them directly according to our needs.

To make a bit more sense of this cross-posting, let me take the
opportunity to
try and clarify the purposes of the different lists a bit (advices welcom=
e).

 - cps-devel is focused on the development of CPS itself. Discussions
should be about
   design decisions and changes in the standard distributions
(CPS-3-base to CPS-3-full). We
   also often make announcements of releases that are not considered as
ready for a wider
   public there.
 =20
 - cps-users and cps-users-fr are for... users ! In practice, that
should mean mostly questions
   about configuration and administration, but also from people writing
integration products.
   There haven't been much end user questions in the past on it,
probably because most end
   users are in a customized installation with in-house support, but
they would be welcomed
   as long as they don't depend too much on specific issues.

 - cps-translators is obviously about translating the software. There
hasn't been much traffic
   on it since the switch of Nuxeo to Java technologies. Maybe we'll end
up shutting it down and
   redirect everybody to cps-users.

 - code is a technical list to follow day to day development. Mercurial
changesets arriving at the
   authoritative repositories on hg.cps-cms.org, as well as trac
notifications end up there.

Since CPS is written both as a framework and standard integration
components for it, it's normal that
there's a bit of overlapping between cps-users and cps-devel. Indeed, a
discussion about a change in
CPSCourrier workflows should not much differ in contents with one on how
to leverage workflow
stacks for a custom project.
Don't hesitate to wave if you think we should redefine the distinction
between cps-users
and cps-devel. We are open to all suggestions.

Regards,

--=20
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet



--------------enigE77A8D1153077813D4B23B09
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPL7NWAAoJEOAffZJiF+Z44rQIAKtN+/zoQjMNHA9WYSXI0Kij
YMqOMxGvD5m5LUwEP5v+7Xdam2HvWYfMDwApU/cnJcVVJoBda4LkPmQfAv3llF3I
10+h/bzDUWiAm9i7+HfQNHd+ZIaeYIv5H0w3/iG6mOwhz9kOoPzQGNjA80fjhCKA
AO72qpXp/VgHfge8UtRcZ4RO8P8ko5o7ReKCtJ3g4DeOPGTM4r7q3Bo4f0HAz3jy
5ykd+sviTuB7beDWXYD7cob1JhCIT+TmDLZqojjAxnhHdCuvZ+MVgXHUmySE9w+j
rPHPwRv6fubxLKOUbjtuAZ6IUGqHuRZFZZZrzT7Xask95uugiavDLdLSj/xdIU4=
=cGBs
-----END PGP SIGNATURE-----

--------------enigE77A8D1153077813D4B23B09--


--===============0474869546==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

--===============0474869546==--