[Geoserver-devel] update developers guide to match current practice

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 - 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

On Mon, Apr 18, 2016 at 9:07 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

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

+1

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&gt; -
I would like to use this to update the developers guide

I'd also update the contributor.md, so that we can point people making
significant pull requests to it.

- 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.

I don't understand what you mean here... are you hesitant to adjust the
current doc, to adjust the wiki page, or ... something else?

- Other than recruiting additional volunteers I am not quite sure how to
address this

I'd say that people directly benefiting from working in GeoServer
(companies, consultants) should be simply pushed to also perform chores that
keep the projection operational and thus have more to work on in the
future, otherwise the project risks dying. Thus the above guide.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

On Mon, Apr 18, 2016 at 9:07 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

- 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.

I don't understand what you mean here... are you hesitant to adjust the
current doc, to adjust the wiki page, or ... something else?

I am hesitant to lower our standards, but I recognize they are not being
maintained at present. I think the responsibilities are an accurate
reflection of what it takes to keep the GeoServer project going.

- Other than recruiting additional volunteers I am not quite sure how to

address this

I'd say that people directly benefiting from working in GeoServer
(companies, consultants) should be simply pushed to also perform chores
that keep the projection operational and thus have more to work on in the
future, otherwise the project risks dying. Thus the above guide.

This would indeed be recruiting more volunteers. Starting with companies
and consultants that benefit from GeoServer is a great place to start.
--
Jody