We've been developing the new administration interface for GeoServer 2.0 in a community module thus far, but obviously we want to move it to the main section before the final release. We need to firm up the process for modules graduating from community before this can happen; in the channel aaime and I developed the following list of tasks:
* GSIP for the Wicket UI
* Finalize the Community Module graduation policy
* (If the graduation policy passes as-is: Get test coverage and documentation for the new UI up to the standard)
* Actually do the move and update all the release machinery to use the new web modules.
Just wanted to open up this discussion to the community, what does everyone think?
We've been developing the new administration interface for GeoServer 2.0 in a community module thus far, but obviously we want to move it to the main section before the final release. We need to firm up the process for modules graduating from community before this can happen; in the channel aaime and I developed the following list of tasks:
* GSIP for the Wicket UI
* Finalize the Community Module graduation policy
* (If the graduation policy passes as-is: Get test coverage and documentation for the new UI up to the standard)
* Actually do the move and update all the release machinery to use the new web modules.
Just wanted to open up this discussion to the community, what does everyone think?
I think it's a very good exercise of "eat your own dogfood" practice,
and we must go thru it all right
Cheers
Andrea
We've been developing the new administration interface for GeoServer 2.0 in a community module thus far, but obviously we want to move it to the main section before the final release. We need to firm up the process for modules graduating from community before this can happen; in the channel aaime and I developed the following list of tasks:
* GSIP for the Wicket UI
I started one back before the sprint... its out of date now though.
* Finalize the Community Module graduation policy
There is also a GSIP in the works to formalize this process as well. It is up there on my TODO list, i am hoping to get to it soon. I think all the feedback has been gathered, it just needs to be written up and documented.
* (If the graduation policy passes as-is: Get test coverage and documentation for the new UI up to the standard)
Have we figured out how to write unit tests for the UI yet? I don't see any in the web modules.
* Actually do the move and update all the release machinery to use the new web modules.
Just wanted to open up this discussion to the community, what does everyone think?
-David Winslow
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
We've been developing the new administration interface for GeoServer 2.0 in a community module thus far, but obviously we want to move it to the main section before the final release. We need to firm up the process for modules graduating from community before this can happen; in the channel aaime and I developed the following list of tasks:
* GSIP for the Wicket UI
I started one back before the sprint... its out of date now though.
* Finalize the Community Module graduation policy
There is also a GSIP in the works to formalize this process as well. It is up there on my TODO list, i am hoping to get to it soon. I think all the feedback has been gathered, it just needs to be written up and documented.
* (If the graduation policy passes as-is: Get test coverage and documentation for the new UI up to the standard)
Have we figured out how to write unit tests for the UI yet? I don't see any in the web modules.
No, no tests have been written yet. However Wicket does provide some testing facilities so I doubt this will be too tough to set up.
* Actually do the move and update all the release machinery to use the new web modules.
Just wanted to open up this discussion to the community, what does everyone think?
-David Winslow
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
We've been developing the new administration interface for GeoServer 2.0 in a community module thus far, but obviously we want to move it to the main section before the final release. We need to firm up the process for modules graduating from community before this can happen; in the channel aaime and I developed the following list of tasks:
* GSIP for the Wicket UI
* Finalize the Community Module graduation policy
* (If the graduation policy passes as-is: Get test coverage and documentation for the new UI up to the standard)
* Actually do the move and update all the release machinery to use the new web modules.
Just wanted to open up this discussion to the community, what does everyone think?
I agree with the "eat your own dogfood idea" - thanks for making this a very professional transition. I think the discussion on how to handle community module graduation has wrapped up and we need to crunch a couple of the GSIPs together into one good one.
