========= Community ========= .. toctree:: :hidden: :glob: org/* governance/* .. container:: row .. container:: col-md-1 text-center .. raw:: html .. container:: col-md-4 If you have questions related to the use of vispy, we have a `chat room `_ on gitter. .. raw:: html
.. container:: col-md-1 text-center .. raw:: html .. container:: col-md-4 If you find a problem related to this website, please submit an issue to the `vispy repository `_. .. raw:: html
.. container:: row .. container:: col-md-1 text-center .. raw:: html .. container:: col-md-4 If you have a bug to report, a feature you’d like to request or a patch you wish to submit, please `submit an issue `_. .. container:: col-md-1 text-center .. raw:: html .. container:: col-md-4 If you want to help with the development of vispy, join us on `GitHub `_ or the `Developer Gitter `_. There is also a `developer's mailing list `_. .. container:: row .. container:: col-md-1 text-center .. raw:: html .. container:: col-md-4 VisPy is both a library and an organization. If you want to know more about the organization and its structure check out our :doc:`Charter <./org/CHARTER>` and see who's on the :doc:`Steering Committee <./org/STEERING-COMMITTEE>`. .. container:: col-md-1 text-center .. raw:: html .. container:: col-md-4 The :doc:`maintainers <./governance/MAINTAINERS>` of VisPy manage the project following a simple set of expectations which you can find in the :doc:`governance <./governance/GOVERNANCE>` document.