On Wed, 31 Jan 2001, Jon M. Taylor wrote:
> On Wed, 31 Jan 2001, Lee Brown wrote:
>
> > On Tue, 30 Jan 2001, Andreas Beck wrote:
> > > Someone please step ahead and take the lead.
> >
> > Dear GGI people,
> >
> > I'll take the job for six months. If you don't feel that we are
> > moving quickly enough or in the right direction, I would willingly resign.
> >
> > It would be a pleasure to work with so many
> > knowledgable people. Whatever tasks need to be done, I'll gladly do. I have
> > time.
>
> Probably the best thing you could do at this point is to get
> administration rights to the GGI SourceForge project and move our CVS, FTP
> and Eric's new web pages over. We need a properly functioning project
> management infrastructure, badly.
I am registered at SF, too. My name is "cegger". Add me as a member,
and I can help there.
> > Most of all, I would listen to the people on the list and help go in the
> > direction they want to go. It's their project after all.
>
> Please do, especially when it comes to CVS. As I mentioned in
> another post, we'll probably want to reorganize the tree a bit.
>
> > I realize I am not the best coder here, but there is my offer anyway.
>
> We don't need super whiz coders right now nearly as much as we
> need someone to come in and sweep out the corners, knock out the dents and
> smooth out the rough edges. See below.
I agree.
> > It
> > is made with the best of intentions.
>
> The offer is appreciated. We need the admin work a lot more than
> we need more GGI code right now. If you still want to code, code where
> it'll make the most difference: Be a dilletante and work a little bit on
> a lot of different bits of existing code, instead of plunging into a
> larger project like writing your own extension. Unfortunately, this type
> of "fingers in a lot of pies" approach takes quite a bit of time, but if
> you have the time like you said, you could do us a world of good.
>
> Christoph Egger does a lot of this type of work - lots of little
> patches to clean up small bugs and tighten things down in general.
TNX for your credits.
> Go over the GGI code with a magnifying glass and looking for bugs,
> out of date docs, design thinkos, etc. Stress-test GGI by trying
> as many different types of targets, in as many different
> combinations, as you can think of. "Sweat the Small Stuff" would
> be your motto |->. Anyway, think it over.
I agree here, too.
It should be mentioned here, that we have to fix up GGI's extension
system. Just think of a code like this:
-------------------------------------------------------
...
xmiInit();
...
xmiExit();
...
xmiInit();
...
xmiExit();
...
-------------------------------------------------------
The second xmiInit() creates a core-dump as people reported. And this
bug isn't only in libxmi.
Marcus said, we have to make a redesign to fix this in the right way.
I can't do that, because I don't have any ideas of _how_ doing
this _right_. As I am not Marcus, I can't therefore know, what
Marcus' intension is of _how_ doing this.
I offered my help in PM to him last year, but I haven't got no
response yet.
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
P.S.: If I am not clear enough, then let me know.
