How To Help

Welcome! The STAC community prides itself on being welcoming and collaborative, and we are excited you clicked on this page to learn how you might help!

We list a number of general ideas below, and you're welcome to find one and just start working away. But if you aren't sure where to start we encourage you to jump on our gitter chat and introduce yourself and what you might be interested in. We can help match with a good project given your skills and time availability. We are working on more resources to make it easier to figure out where to plugin for data or software help, but for now saying hi on the gitter is your best best.

We also do video calls where we discuss various issues and move the spec forward. We alternate between hour long calls where we aim to talk through the issues in front of us, and 3 hour long 'working sessions' where people find some dedicated time to work on STAC, with others on the video call at the same time for any questions or collaboration. And then the other main locus of community activity is the stac-spec repo. We also have a google group, called stac-spec, where there are occasional messages.

Help with Data

Perhaps the biggest way to help push forward STAC is by helping to translate more data into STAC compliant catalogs. There are a number of existing open data sets that we would like to make accessible as STAC, which need a volunteer who is tech savvy to use STAC tools or develop new ones.

If you are a data provider and are contemplating exposing data with STAC we'd love to talk to you. There are likely community members who can help if your data is going to be open. And we are happy to give advice on STAC best practices for proprietary. You can use STAC to help expose downsampled assets to attract customers, or as a format for your paying users or on your intranets.

One of the biggest goals right now is to bring in more diverse types of data. So those who have data that is different and are up for pioneering a new extension are highly appreciated. We want to ensure that the core spec is able to handle a wide variety of extensions representing lots of different data types before we settle in at 1.0, so we can ensure stability of the core.

Help with Software Development

While there are already a handful of STAC implementations, our goal is to have tools in every language, and integrations in every major geospatial-aware software project. So if you are a software developer who would like to help just get in touch and we can find a project for you. It could be helping with an existing one or starting something new - it's up to you. We have opportunities with servers, javascript clients, command line tools, client libraries, testing tools and more. And we are happy for those who have existing projects that they want to bring into the STAC ecosystem.

Help with Web Design

There copious opportunities for web designers, as we have none in our community as of yet. Even if you are just starting out with web design, we welcome your contribution and can give you meaningful projects. There is helping with this website, but also cool projects customizing different STAC HTML implementations in STAC Browser, so they don't all look the same. Creativity is welcome!

Help with Outreach

As a community we know one of the most important things is to spread the word about our work. This could be presenting at conferences or meet-ups, writing blog posts or whitepapers, or helping refine the website. We welcome anything from minor fixes on the site to creating full tutorials or new forms of outreach. We are a very open community, and are happy to help you develop skills and experience that help you.

Help with the Specification

The biggest way to help with the specification is to create compliant catalogs or software and give us feedback from that experience. That experience should ground you in what is possible, and then help us build the spec with pull requests from there. But we also welcome those who like to make things easier to read - organizing and editing the spec.