[Incubator] Review Of MapBuilder incubation artifacts

[Cameron Shorter]

Jody, sorry for delay. Issues addressed below.
I'll send a seperate email about the Graduation Template.

Jody Garnett wrote:
 > Jody Garnett wrote:
 >
 >> Hi Frank, good call on email discussion ...
 >>
 >> I am going to review the docs that we generated as part of the
 >> incubation process and make sure they offer good visibility for where
 >> MapBuilder is now. I would not mind a separate account of what changes
 >> MapBuilder needed to make as part of it's incubation - as an example
 >> for projects that come later.
 >>
 >> I will vote after the review...
 >
 > http://wiki.osgeo.org/index.php/Community_Mapbuilder_Incubation_Progress
 >
 > Page is good, notes follow:
 > - page should be done up as a formal document/report for the official
 > OSGeo site, at the end of incubation this is the only record we have.

Raised a JIRA issue to track this.
http://jira.codehaus.org/browse/MAP-145

 > - for the first section where OSGeo infrastructure was not used, the
 > actual alternative should be present as a link (so that when we hand
 > this document over to webcomm they will be able to quickly set up a
 > summary page)

Done.

 > - Project Steering Committee - in addition to members list I would like
 > to see evidence of a procedure (so we can confirm it is infact open to
 > members of different organizations etc...) Google found:
 > http://docs.codehaus.org/display/MAP/Credits (which does not provide a
 > procedure). Note the sponsorship section on that page is very good, we
 > should consider asking for a list of sponsors from each project - as
 > OSGeo visibility is a reason for sponsors to invest time and effort into
 > both MapBuilder (and specifically into getting MapBuilder through
 > incubation)

Done.

I think you are looking for the PSC section of 
http://communitymapbuilder.org/display/MAP/Contributers+Guide which 
describes responsibilities of PSC members and how to select new PSC 
members. Possibly also 
http://communitymapbuilder.org/display/MAP/Decision+Making . I've added 
these links to the Incubation Progress page.

 > - project documents, what are we looking for here indeed. I am 
looking for
 > a) link to OSGeo
 > b) correct use of OSGeo logo
 > c) OSGeo contact information on official docs such as pdf installation
 > instructions etc
 > d) correct use of fonts and branding on official documents
 > e) since the viscomm / webcomm have not facilitated this I would like to
 > see mapbuilder have a plan for documentation / website upgrade
 > - brand the project web site, same comments simply viewing the project
 > website as an official document to be treated like any other

As you mention, the OSGeo branding is not available yet, so I've raised 
issue http://jira.codehaus.org/browse/MAP-146 to track this.

 > ****warning markoid semi-requirements****

The following documentation requirements are not part of the current 
Graduation Template and if we want Mapbuilder to address these issues, 
then the Graduation Template is on the critical path for Mapbuilder 
graduating.

Volunteers?


 > We also need a couple of markoid documents from MapBuilder, handout is
 > already available for example, it would be also be wise to have a
 > feature matrix. While the web and vis committees have not figured out
 > what the exact requirement is I can not hold MapBuilder responsible for
 > its lack.
 > Cameron can I request the following documents:
 > a) Feature Matrix - with special attention paid to what SDI component
 > mapbuilder is (ie a web client), what standards it uses to play with
 > others (WMS and WFS, and Tile?), and specifically what FOSS others it
 > plays with nicely (ie what do you test against as part of your release
 > procedure?)

I've created this: http://docs.codehaus.org/display/MAP/Feature+Matrix
as a starting point.

 > b) Developer and User Guides - links will suffice, want to ensure that
 > both the development process is open, and that users are catered to

Developer and User guides are liked from the home page:
http://docs.codehaus.org/display/MAP/User+Guide
http://docs.codehaus.org/display/MAP/Tutorials
http://docs.codehaus.org/display/MAP/Developers+Guide

 > c) Handout - understand this is already done, simply listed as a
 > checkpoint for following project

Done.

 > d) license, was not listed here

License is covered when you start the incubation process which is 
probably why it is not covered here. Also covered by the code providence 
review, 
http://wiki.osgeo.org/index.php/Community_Mapbuilder_Provenance_Review#History

 > e) Release Process (should be a section of the developers guide) and
 > Roadmap, want to ensure that release process is open and scheduled so
 > that others wanting to use MapBuilder can plan

Done.
Release Process is documented at: 
http://docs.codehaus.org/display/MAP/Release+Process and the Developers 
guide links to the release process.

 > - Code Copyright review, link is present
 > - Issues Raised, yes they have been addressed - would it be a benifit to
 > offer a summary here? The link does provide the license but does not
 > provide a list of the issues addressed.

I've added a short summary of issues. I didn't keep records of the 
issues and don't see a need to go back and recreate the list now.

 >
 > Other things to check:
 > - contact information on wiki for interaction with other OSGeo
 > committees, understand that Cameron is already listed

I've added my contact details to the top.

 >
 > Why this feedback and why now?
 >
 > My thinking is this, when the process grows we will need to ensure the
 > incubation committee provides information to the next people in the
 > chain. We need to make sure that a graduating project actually is ready
 > for graduation with all the materials available needed by other OSGeo
 > committees.  I understand that some of this is hard due to visual
 > standards not being defined yet, setting up an adoption plan or a
 > responsible memeber of the MapBuilder commity will need to prove
 > sufficient.
 >
 > I will wait for Cameron's feedback before voting - perhaps he could
 > forward this message to his developer email list.
 > Jody
 >
 > ---------------------------------------------------------------------
 > To unsubscribe, e-mail: incubator-unsubscribe at incubator.osgeo.org
 > For additional commands, e-mail: incubator-help at incubator.osgeo.org
 >
 >


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