Hi all,
I’m starting this conversation to see if/how we can amend the procedures for graduating a community module a bit.
For reference, the current procedure is here:
https://docs.geoserver.org/latest/en/developer/policies/community-modules.html#id2
In particular, I’m thinking about requirement “1”, the module has at least 3 users.
The reason for the check is a good one, we don’t want to clutter the main code base with modules that are specific to one single user site. At the same time, this creates a “chicken and egg” problem, because many sites won’t consider using a module until it’s supported.
So, I’d like to keep the intent of requirement 1, but propose a change in its implementation. 3 usage sites can be one of the options, but can we also consider a PSC opinion on the matter as a valid alternative? And a PSC member can provide feedback on the module generality while the graduation is being voted.
I know that Jody wants to also talk about point 3 (module being stable, as a prerequisite, the standards that the module is based on being stable too), but can we please have a separate thread for that?
Best regards
Andrea
···
==
GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail