Re: [gobo-eiffel-develop] Hello

[Berend de B. <be...@po...>]

Eric Bezault <er...@go...> writes:

> What I suggest is that I start writing a first draft of
> the developer guidelines this weekend and then make it
> available to this mailing list as a starting point for
> discussion. As soon as I have a first draft I will also
> announce the existence of this mailing list publicly so
> that others can join the discussion if they are interested.

Good idea.


> In the meantime feel free to post to this mailing list
> if you want to start the discussion.

A few things:

1. I think ECLI is also a good candidate (odbc access).

2. Does anyone know Perforce? (http://www.perforce.com). I like its
   version control system much more than CVS, its available for free
   for Open Source projects.
   However, CVS and SourceForge are already setup and available, but I
   just wanted to know if more people know and like Perforce.

3. For the guideline: note that eposix also has several layers like a
   Standard C, POSIX, Single Unix Specification and an abstract layer
   (common subset of POSIX and  Win32). With single prefixes like PX
   or so I don't get that far in communication the structure. Perhaps
   you can give this some thoughts.

4. It's great to see UCSTRING become part of the lib.

5. The name: I think the Gobo name is quite usefull as it is
   well-known. But what about a somewhat more catchy name like Unified
   Gobo? "The Unified Open Source Eiffel Library" is to formal, but
   Unified Gobo sounds as somewhat more important for this large
   undertaking.
   But I'm also just fine with Gobo.


Groetjes,

Berend. (-: