From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <448EBEC0.5070203@domain.hid> Date: Tue, 13 Jun 2006 15:33:52 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig208EF4661238B61B3D13500D" Sender: jan.kiszka@domain.hid Subject: [Xenomai-core] public roadmap/todo list (was: ns vs. tsc as internal timer base) List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai-core This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig208EF4661238B61B3D13500D Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Philippe Gerum wrote: > Jan Kiszka wrote: >> >> :) We should coordinate better. >> > > The answer is published roadmap + todo list, but this requires some > organisation we have not been able to setup yet. Indeed. I think this is first of all a technical issue: lowering the convenience barrier for entering/updating stuff within the team. Spontaneously, I have two options in mind: - existing bug/feature tracking system on gna.org - non-existent wiki with one or more dedicated pages about this, following some loose convention on the item structure Any other suggestions? Any preferences? How to proceed? Jan --------------enig208EF4661238B61B3D13500D 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.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEjr7AniDOoMHTA+kRArKPAJ9OzHyaGgG659q+2m+1UqwbGhWlJwCdHvBE elgsGXPdNHF4qmsZQ7jfTD4= =xOu1 -----END PGP SIGNATURE----- --------------enig208EF4661238B61B3D13500D--