webmap.js project structure

[Cameron Shorter]

I appologise if I'm going over ground already covered at FOSS4G. I've 
got a couple of house keeping questions about webmap.js.

Are we planning to set up webmap.js as a project? Eg: 
webmap.sourceforge.net or webmap.osgeo.org or similar.

Are we planning to set up a mailing list? I suggest that this list 
should become the webmap.js list.

Where is the Subversion repository going to live?

Where is the issue tracker going to live?

What about a wiki? Actually - I think Chris mentioned this already.

Are we going to set up a seperate Project Management Committee or will 
webmap.js be part of OpenLayers?

Are we going to aim toward a common, Javascript API, or set of API 
convensions that all the webmapping projects use?
(This will make it much easier for users to graduate from one project to 
another and their user requirements change and will reduce the vendor 
lock in that users hate.)
I haven't fully thought through the feasibility of this yet.

Has someone drafted a Javascript API and design yet?

What is the relationship between Map and Layers? How do you treat 
special cases like 2 maps on the same webpage (eg a locator map and main 
map)?


-- 
Cameron Shorter
http://cameron.shorter.net