How does everyone (PSC, comitters, contributors) feel about updating the
developers guide procedures to better reflect how we get things done in
2016:
Changing contributions to be expressed in terms of pull requests (not
patches):
- https://github.com/geoserver/geoserver/pull/1554 updated pull request
review guidelines
- The information on community modules is spread out over several pages
making it hard to follow
- I would like to try gathering this into a single page to make it easier
to follow
The balance of activity in our project has shifted from module maintainers
to the project steering committee:
- Andrea has provided an excellent summary of responsibilities on the wiki
<https://github.com/geoserver/geoserver/wiki/Some-ideas-about-minimum-community-software-responsibility-and-participation>
-
I would like to use this to update the developers guide
- I am hesitant to adjust the responsibilities as I believe they provide a
fair representation of the amount of work required to keep GeoServer
operational.
- Other than recruiting additional volunteers I am not quite sure how to
address this
--
Jody Garnett
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
