On Wed, 30 Aug 2000, Andreas Beck wrote:
> 2. Our Homepage needs a serious refreshment. I feel that myself. While it is
> pretty clean and simple, especially for those who know the project, it lacks
> some spice for the others. We need some eye-candy there, and we should
> change it on a regular basis to keep people hitting the site.
Agreed.
> A few suggestions for that:
> a. We feature a "cool GGI Screenshot of the week". I'd volunteer to take the
> pics all you out there would send me and judge them and integrate them with
> the website. Webbased voting would also do, but someone would have to set
> that up.
> b. I have kind of a webcam here which is GGI enabled, at least if I rewrite
> a few small tools I lost in my HD crash. Should be no biggie.
> However that wouldn't be a really interesting thing to look at - if it
> really gets interesting, I'll surely have turned it off in time :-) ...
> Moreover, as I'm not on a permanent connections, updates would be at most
> something like twice a day or something.
A good idea.
> And we'll probably have to restructure it a little to the current mainstream
> "sourceforge"-structure like "info - screenshots - download - contact".
>
> More ideas very welcome.
How about "Related links" to GGI-projects?
> 3. We have a problem with our distribution model.
> We tell most people to get a recent devel snapshot, but its size scares
> them. We have nicely split rpms and debs, but they are out of date.
>
> O.K. - I think we should do the following:
>
> Apart from the full snap, generate at least 2 more tgzs with libgii and
> libggi separated out. Even better would be libgii, libggi, svgalib_wrap
> and kgi. The rest ist pretty much optional. Maybe libwmh for some people.
>
> This should cost nothing but a few small changes to the docs, the webserver
> scripts and some space on the ftp-server.
Yes, that sounds much better.
> 4. We need a release.
>
> I need to talk to Marcus about that, to recheck, that there isn't much that
> really needs to be fixed.
No! You and Marcus _NEVER_ will find _every_ bug! Only a _community_ can do
that. Make _public pre-releases_ available - EARLY AND OFTEN - and wait for
feedback from the user-community!
This is much more efficient. You will see.
> When we agreed on that, making a release would be
> nothing but keeping our hands off the code until the next snapshot
> generation, if we adopt the model from 3.
OK. Please don't forget to post a actual job list permamently for the final
release. Each point should be small enough, so that it can ideomatically be
done within a few days...
> 5. Someone suggested a "small release", with only the most important
> targets.
>
> I don't think this would be good. The beauty of LibGGI shows in the big
> choice of possible targets. I think targets are detected reliably enough to
> cause no problem in the build process. If any do, we should just disable
> them in configure.
Agreed, too.
> 7. Someone suggested a big IRC meeting.
>
> This would indeed probably rise the spirits some. I do remember the times,
> when I summarized such meetings with that famous fantasy-touch stories ...
> was quite some fun, and I think we should start having so much fun again ...
> ;-).
Yes! But please don't forget to post the log to the ML... ;-) see my earlier
mail.
> 8. Someone asked about EvStack.
>
> To my knowledge, the linux-input project tries to establish something like
> it. It really was a great project, but it dives deeply into kernel internals.
> I don't have the nerve to do that again, as I have pretty much rid myself
> from Linux kernel development in favour of more portable stuff. While the
> evstack principle and its modules are fairly portable (EMan surely knows
> what I am talking about - right ?), the kernel interfacing isn't.
> If someone wants to pick that up again, I'll surely assist in any way.
According to EvStack I can't say anything. It died, _before_ I started to use
GGI... :-(
> O.K. - how does that sound ? Comments and volunteers welcome.
It sound's good. And... how about to realize that now? :-)
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
