.. _community:

================================================================================
Community
================================================================================

GDAL's community interacts through `Mailing List`_, `GitHub`_, and
`Chat`_.  Please feel welcome to ask questions and participate in all of the
venues.  The `Mailing List`_ communication channel is for general questions,
development discussion, and feedback. The `GitHub`_ communication channel is
for development activities, bug reports, and testing. The `Chat`_
room is for real-time chat activities such as meetings and interactive
debugging sessions.

Code of Conduct
---------------

.. only:: html

    GDAL uses a :ref:`code_of_conduct` which governs how we behave in any GDAL
    forum or event and whenever we will be judged by our actions. We expect it to
    be honored by everyone who participates in the GDAL community formally or
    informally, or claims any affiliation with the project.

.. toctree::
   :hidden:

   code_of_conduct


Mailing List
------------

Developers and users of GDAL participate on the GDAL mailing list. It is OK to
ask questions about how to use GDAL, how to integrate GDAL into your own software,
and report issues that you might have.

http://lists.osgeo.org/mailman/listinfo/gdal-dev


GitHub
------

Visit http://github.com/OSGeo/GDAL to file issues you might be having with the
software. GitHub is also where you can obtain a current development version of the
software in the `git`_ revision control system. The GDAL project is eager to
take contributions in all forms, and we welcome those who are willing to roll
up their sleeves and start filing tickets, pushing code, generating builds, and
answering questions.



Chat
----

You can find some GDAL developers in the IRC channel #gdal on `Freenode`_
which is bridged to a `#gdal:osgeo.org`_ Matrix room.
This mechanism is usually reserved for active meetings and other outreach
with the community.
The `Mailing List`_ and `GitHub`_ avenues are going to be more productive
communication channels in most situations.

.. note:: the Freenode channel only accepts messages from registered
          users, so make sure to complete that step. Instructions can be
          found on https://wiki.osgeo.org/wiki/Matrix for doing it from
          the Matrix side and https://freenode.net/kb/answer/registration
          for doing it from the IRC side (if you don't use Matrix)


.. _`git`: https://en.wikipedia.org/wiki/Git_(software)
.. _`Freenode`: http://freenode.net
.. _`#gdal:osgeo.org`: http://matrix.to/#/#gdal:osgeo.org


Social media
------------

You can follow GDAL official news on Twitter: https://twitter.com/GdalOrg


Conference
----------

.. image::   ../../images/foss4g2021.png
   :alt:     FOSS4G 2021
   :target:  https://2021.foss4g.org/

`FOSS4G 2021 <https://2021.foss4g.org/>`_ is the leading annual conference for free and open source geospatial software. It will include presentations related to GDAL/OGR, and some of the GDAL/OGR development community will be attending. It is the event for those interested in GDAL/OGR, other FOSS geospatial technologies and the community around them. The conference will be held ONLINE from September 27th to October 2nd 2021.

Governance and Community Participation
--------------------------------------

OSGeo Project Membership
++++++++++++++++++++++++

Originally, GDAL has been lead by Frank Warmerdam, the original author of much
of GDAL/OGR, though with contributions and input from a variety of people.
As of February 2006 GDAL/OGR became a founding project of the
`Open Source Geospatial Foundation (OSGeo) <https://www.osgeo.org/>`_
and began a transition to a more community oriented governance
model - in keeping with OSGeo expectations.

Membership as an OSGeo project provides assurances that a variety of best practices
are being employed by the GDAL/OGR project, and that users and contributors can be
assured of responsible project operation and continuity of the project. In particular:

- A consensus oriented Project Management Committee will be in charge of the project.
- Project source code and contributions will be vetted to ensure code is properly
  made available, protecting contributors and users of GDAL/OGR.
- Part of the systems infrastructure used by the project is provided by the foundation,
  with responsible backup and redundancy to minimize disruptions.

.. _psc:

Project Steering Committee
++++++++++++++++++++++++++

As of April 2006 (following the GDAL/OGR 1.3.2 release) the project has been
placed in the hands of a Project Steering Committee. This project steering
committee operates under the rules of :ref:`rfc-1`, and is overall responsible for
decisions related to the GDAL/OGR project. The current members are (@github username):

- Frank Warmerdam      (@warmerdam)
- Daniel Morissette    (@dmorissette)
- Howard Butler        (@hobu)
- Tamas Szekeres       (@szekerest)
- Even Rouault (chair) (@rouault)
- Jukka Rahkonen       (@jratike80)
- Kurt Schwehr         (@schwehr)
- Norman Barker        (@normanb)
- Sean Gillies         (@sgillies)
- Mateusz Łoskot       (@mloskot)

Past members:

- Andrey Kiselev       (@strezen) (retired in 2019)

Note that discussion of proposals to the PSC take place on gdal-dev, and input
from all subscribers is welcome. A :ref:`list of past RFC <rfclist>` is available for review.


GDAL Service Providers
----------------------

.. only:: html

    GDAL is developed and supported by a rich ecosystem of businesses and
    individuals around the world. You can consult a list of :ref:`service_providers`
    who can assist you in getting the best out of your GDAL investment.

.. toctree::
   :hidden:

   service_providers
