You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>In support of an inclusive and welcoming community, the pygeoapi code of conduct can always be found at <ahref="https://github.com/geopython/pygeoapi/blob/master/CODE_OF_CONDUCT.md">https://github.com/geopython/pygeoapi/blob/master/CODE_OF_CONDUCT.md</a>.</p>
46
+
<p>There are numerous ways to interact with the pygeoapi community.</p>
47
+
<h2id="mailing-list">Mailing List</h2>
48
+
<p>The pygeoapi mailing list enables users and developers to exchange ideas, discuss improvements / issues, and ask questions. To subscribe, visit <ahref="https://lists.osgeo.org/mailman/listinfo/pygeoapi">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a>.</p>
49
+
<p>Mailing list archives are available at <ahref="https://lists.osgeo.org/pipermail/pygeoapi">https://lists.osgeo.org/pipermail/pygeoapi</a>.</p>
<p>pygeoapi also provides <ahref="https://github.com/geopython/pygeoapi/discussions">GitHub Discussions</a> as a collaborative community space for general questions, ideas, and more.</p>
52
+
<h2id="chat">Chat</h2>
53
+
<p>pygeoapi provides open communication in real-time, and provides chat via Gitter, Slack, or IRC (note: connecting via either Gitter or Slack or IRC plugs you in to the same chat).</p>
54
+
<p>PSC discussions, meetings and user discussion can typically be found in pygeoapi's chat.</p>
55
+
<h3id="gitter">Gitter</h3>
56
+
<p>Gitter provides a web-based instant messaging and chatroom. The pygeoapi <ahref="https://app.gitter.im/#/room/#geopython_pygeoapi:gitter.im">Gitter chatroom</a> is public and open to anyone.</p>
57
+
<h3id="slack">Slack</h3>
58
+
<p>The OSGeo Slack is provided at <ahref="https://osgeo.slack.com/pygeoapi">https://osgeo.slack.com/pygeoapi</a>.</p>
59
+
<h3id="irc">IRC</h3>
60
+
<p>The pygeoapi IRC can be found at <ahref="irc://irc.freenode.net#pygeoapi">irc://irc.freenode.net#pygeoapi</a>.</p>
61
+
<p>For those wishing only to follow repository changes/updates, the pygeoapi-activity IRC can be found at <ahref="irc://irc.freenode.net#pygeoapi-activity">irc://irc.freenode.net#pygeoapi-activity</a>.</p>
62
+
<h2id="twitter">Twitter</h2>
63
+
<p>The official pygeoapi Twitter handle is at <ahref="https://twitter.com/pygeoapi">https://twitter.com/pygeoapi</a>.</p>
64
+
<h2id="mastodon">Mastodon</h2>
65
+
<p>The official pygeoapi Mastodon handle is at <ahref="https://noc.social/@pygeoapi">https://noc.social/@pygeoapi</a>.</p>
66
+
<h2id="stack-overflow">Stack Overflow</h2>
67
+
<p>pygeoapi discussions on Stack Overflow can be found with the <ahref="https://stackoverflow.com/questions/tagged/pygeoapi">pygeoapi</a> tag.</p>
68
+
<h2id="service-providers">Service Providers</h2>
69
+
<p>pygeoapi service providers (core development, support, training) can be found on the <ahref="service-providers/">Service Providers page</a>.</p>
70
+
<p>Service providers are also listed on the <ahref="https://www.osgeo.org/service-providers">OSGeo Service Provider Directory</a>.</p>
71
+
<h2id="swag">Swag</h2>
72
+
<p>pygeoapi swag (t-shirts, hoodies, stickers, etc.) are available and can be purchased via the <ahref="https://www.redbubble.com/shop/ap/146590645">OSGeo Redbubble shop</a>.</p>
<p>The pygeoapi <ahref="https://github.com/geopython/pygeoapi/wiki">wiki</a> provides an area for supporting information that frequently changes and / or is outside the scope of the formal documentation.</p>
75
+
<p>The pygeoapi <ahref="https://github.com/geopython/pygeoapi/issues">issue tracker</a> is the place to report bugs or request enhancements. To submit a <ahref="https://github.com/geopython/pygeoapi/issues/">bug</a> be sure to specify the version you are using, the appropriate component, a description of how to reproduce the bug, as well as what version of Python and platform.</p>
76
+
<p>GitHub provides the ability for users to issue <ahref="https://help.github.com/articles/creating-a-pull-request">pull requests</a>, and is the preferred way to have your contributions added to pygeoapi, although patches and other mechanisms are welcome as well.</p>
77
+
<p>All pygeoapi <ahref="https://github.com/geopython/pygeoapi">source code</a> is managed on GitHub, which includes the latest (<code>master</code>) and other supported branches.</p>
78
+
<h2id="security-issues">Security issues</h2>
79
+
<p>If you encounter a security vulnerability in pygeoapi please report as per our <ahref="https://github.com/geopython/pygeoapi/blob/master/SECURITY.md">Security Policy</a></p>
80
+
<h2id="getting-involved">Getting Involved</h2>
81
+
<p>Users, developers and others are more than welcome! There are plenty of ways to get involved:</p>
82
+
<ul>
83
+
<li>Documentation</li>
84
+
<li>Fixing bugs</li>
85
+
<li>Testing</li>
86
+
<li>Core development (bug fixing, feature implementation, etc.)</li>
87
+
</ul>
88
+
<p>See <ahref="https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md">https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md</a> for more information on contributing.</p>
89
+
</div>
90
+
</div>
91
+
</div>
92
+
</main>
93
+
<footerstyle="text-align: center;">
94
+
<arel="license" title="This work is licensed under a Creative Commons Attribution 4.0 International License" href="https://creativecommons.org/licenses/by/4.0/"><imgalt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/80x15.png" /></a>
<arel="license" title="This work is licensed under a Creative Commons Attribution 4.0 International License" href="https://creativecommons.org/licenses/by/4.0/"><imgalt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/80x15.png" /></a>
0 commit comments