Sun 15 Feb 2009 10:54:18 AM UTC, comment #4:
As Bill told, this projects is just a proposal which, if success, will evolve "in directions we haven't thought of yet."
Savannah has a FS developer database. If it is possible, join is always the way to follow.
Options:
1) We could drop the gnuherds database in favor of the savannah one, which
could be extended to fit the GNU Herds needs.
gnuherds.org could be the frontend to the right dababase backend. Even,
several data bases could be merged via a middleware, e.g., savannah and
gnuherds.
2) The gnuherds.org web site frontend could be dropped in favor of, e.g., the
needed extra features in the Savannah web site frontend.
3) On the other hand, we could keep the gnuherds.org frontend to offer a clean
interface to the user and the identity of the Association.
4) We can keep the current design, with our frontend (web app) and our backend
(data base) but integrating the systems so as to the FS contributors can be a
GNU Herds members automatically, if she/she are debian developers, or are
registered at Savannah, or ... so no disturbing with extra form field to the
normal savannah user.
IMHO the right option is the (4).
|