Re: A community Windows binding

[Stephen Leake <stephen_leake@acm.org>]

Given the response so far, it is clear there is much more support for
using GWindows as the base of a "community Windows binding" than CLAW.

Also, it seems clear that SourceForge is the platform to use. Using
Gnu Arch is appealing, but it requires that each developer open their
machines to outside access. I'd rather let SourceForge worry about the
security implications of that. The other hosts suggested don't seem as
well supported as SourceForge.

Before I actually create a SourceForge project, I'd like to get at
least one other developer to commit to being a sysadmin on the
project. I don't think being sysadmin will take much time; it mostly
consists of setting up accounts for developers. When we get to doing
releases, there will be more work, but we can deal with that then.

Another minor issue is the name of the project. 

We want to host GWindows code (no need to change the name of that
package).

Also the Gnatcom code? I'm not clear if this is available anywhere
other than AdaPower, or if it needs a CVS project.

And possibly a version of Ada.Collections, until they become widely
available from vendors. We should start using that for any collection
needs in GWindows. Or we could just redistribute a .tar.gz of Matthew
Heaney's current stuff.

And possibly other GUI/Windows related packages in the future; maybe a
separate database binding, or a GUI builder, etc.

So perhaps GWindows is not the best name for the SourceForge project.

Let's have a short discussion on this, then I'll set up the project
next weekend, and we can start using that mailing list for any other
issues.

For my part, I actually think we should use GWindows; it's currently a
recognized name, and is general enough to mean "Anything Open Source
in Ada related to Windows".

-- 
-- Stephe