service_providers.rst 4.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. .. _service_providers:
  2. Service Providers
  3. =================
  4. Service providers are an important part of GeoServer community, thank you for helping GeoServer reach a larger audience. Just as open source is a part of your success, your participation and investment is fundamental to the GeoServer project's sustainability.
  5. The PSC manages:
  6. * :website:`GeoServer Commercial Support <support>` (geoserver.org)
  7. * `Service Providers List <https://www.osgeo.org/service-providers/?p=geoserver>`__ (osgeo.org)
  8. Available from `project page <https://www.osgeo.org/projects/geoserver/>`__ from *view all service providers* link.
  9. In addition:
  10. * Project :wiki:`sponsorship <Sponsor>` is another way to increase visibility, with specific activities available to sponsor throughout the year. Financial support is also recognized on the `osgeo sponsor <https://www.osgeo.org/sponsors/>`__ page.
  11. Service Provider checklist
  12. --------------------------
  13. To recognizing experienced providers and core contributors consistently we have developed the following checklist.
  14. Core contributors: take responsibility for the project, meeting all three core responsibilities:
  15. * ``core`` demonstrating an ongoing responsibility: geoserver-security, releases, supported extension
  16. * ``committer`` active development: geoserver-devel, review of pull-requests, assigned Jira tickets, development activities such bug-stomps and sprint participation
  17. * ``support`` sustained community support: GeoServer User forum, review of Jira issues, gis.stackexchange.com, something!
  18. Experienced providers: work on GeoServer when hired by customers but are not always active, demonstrating experience with a selection of the following checklist labels:
  19. * ``development`` feature development: examples GISP proposal, community module
  20. * ``coding`` work on java code, bug fix, signed code contribution agreement
  21. * ``documentation`` contributions to user guide or similar
  22. * ``translation`` helped out translation of application or user guide
  23. * ``outreach`` public presentations of geoserver at foss4g and regional events, public writing such as blog posts, podcast etc...
  24. * ``training`` link to your geoserver training page
  25. * ``services`` link to your geoserver consulting or services page
  26. * ``product`` link to a geoserver based product
  27. Service provider:
  28. * Ask to be listed
  29. * Provide a text description and icon.
  30. Please write description of services offered in third-person (as this text is part of the GeoServer website describing you)
  31. Adding a Service Provider
  32. -------------------------
  33. To apply to be listed on the service-provider page:
  34. #. Please email the developers list with your request to be listed.
  35. We will need your company logo, and short blurb on how you wish to be described.
  36. #. To save time make a pull-request to `geoserver.github.io <https://github.com/geoserver/geoserver.github.io>`__ directly.
  37. Navigate to `support page <https://github.com/geoserver/geoserver.github.io/blob/main/support/index.html>`__ and use the :guilabel:`Edit` option to edit the page - adding an entry similar to:
  38. .. code-block:: html
  39. <div class="row tbl">
  40. <div class="col-xs-2 cell text-center">
  41. <img src="img/madmaps-logo.png" width="52" height="52"></img>
  42. </div>
  43. <div class="col-xs-10">
  44. <a href="https://www.madmaps.com/">Mad Maps, Inc</a> is located in the Pacific Northwest along the famous I5 Interstate and they know how to map. Mad Maps provides creative mapping solutions powered by the open-source available: GeoServer, PostGIS, QGIS and more!
  45. </div>
  46. </div>
  47. For step-by-step instructions on editing in directly in GitHub see documentation guide :docguide:`quickfix <quickfix.html>` instructions.
  48. #. You may also wish to vist osgeo.org and follow the instructions to `add a service provider page <https://www.osgeo.org/community/getting-started-osgeo/add-service-provider/>`__ for your organization.
  49. Experienced Providers:
  50. #. Please email the developers list with your request to be listed, or attend one of the bi-weekly meetings announced on the developer list.
  51. #. Help us out by including the checklist in your email with some links demonstrating your experience and expertise:
  52. * `Commercial support, requirements to move terrestris to experienced providers <https://www.mail-archive.com/geoserver-devel@lists.sourceforge.net/msg46359.html>`__
  53. Core Contributors:
  54. #. Please email the developers list with your request to be listed, or attend one of the bi-weekly meetings announced on the developer list.
  55. #. By the time you ask your service provider checklist should already demonstrate a sustained participation in the GeoServer community.
  56. #. Remember to `add a service provider page <https://www.osgeo.org/community/getting-started-osgeo/add-service-provider/>`__ on the osgeo website so you can be listed as a core contributor on our project page.