RE: [gnome-db] Name proposal/contest for gnome-db/gASQL
- From: "Fernando Martins" <fmartins hetnet nl>
- To: "GDA" <gnome-db-list gnome org>
- Subject: RE: [gnome-db] Name proposal/contest for gnome-db/gASQL
- Date: Wed, 19 Jun 2002 01:25:01 +0200
> -----Original Message-----
> From: gnome-db-list-admin gnome org
> [mailto:gnome-db-list-admin gnome org]On Behalf Of Rodrigo Moya
> Sent: terça-feira, 18 de Junho de 2002 16:37
> To: Malerba_Vivien stna dgac fr
> Cc: fmartins hetnet nl; GDA
> Subject: RE: [gnome-db] Name proposal/contest for gnome-db/gASQL
>
>
> >
> > > > I agree that we need a kind of features and TODO lists at least for
> > > > Egnima. I can propose something if you want.
> > > >
> > > I've been using bugzilla for that, and I think that's what we
> should be
> > > using, since it helps a lot when keeping track of who is
> working on what
> > > and what else is missing. So far, the list of open bugs for
> > > libgda/libgnomedb/gnome-db/gASQL is at:
> > >
> > >
> http://bugzilla.gnome.org/buglist.cgi?product=gASQL&product=gnome-
> db&product=libgda&product=libgnomedb&bug_status=UNCONFIRMED&bug_st
> atus=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype
> 1=substring&emailassigned_to1=1&email2=&emailtype2=substring&email
> reporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&sh
ort_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_
file_> loc=&bug_file_loc_type=substring&status_whiteboard=&status_whitebo
> ard_type=substring&keywords=&keywords_type=anywords&op_sys_details
> =&op_sys_details_type=substring&version_details=&version_details_t
> ype=substring&cmdtype=doit&order=Reuse+same+sort+as+last+time&form
> _name=query
> > >
> > > so, if nobody has nothing against it, just let's use bugzilla. As soon
> > > as we finish the port, I'll create a product for egnima. Or, even
> > > better, I could create it now. For that, I'd just need to
> know in which
> > > components (parts) are we splitting out egnima. So, vivien,
> please tell
> > > me which components you want, and I'll create them, so that you can
> > > enter TODO tasks into bugzilla and have people take them when
> they want
> > > to work on something.
> >
> > Yes, that's better using bugzilla.
> >
> > About Egnima's components, I don't have a precise idea except to have
> > components for the documentation, packages, translations and general
> > code. I have no idea if we should split further the code into other sub
> > components.
> >
> well, it should be separated into features, more or less, so, for
> instance, we could have:
>
> queries
> forms
> documentation
> packages
> translations
> SQL editor
> ...
>
> although I don't know if it's worthy having too many components. Any
> comments anyone?
>
As I said before in a private email, I think those features should be
visible in the web site. So I definitely think this a good idea from the
project documentation. From the code viewpoint, it can always benefit from
modularity and in fact good code should reflect real world perception (can't
remember who was the big name who said it). But I think development itself
will lead to it. Is it important to have code already organised like this in
CVS (rather than later on as an after-thought)?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]