-
-
Notifications
You must be signed in to change notification settings - Fork 706
Home
Daniel Krol edited this page Aug 15, 2024
·
74 revisions
Welcome to the Sandstorm wiki!
The Sandstorm community has been working on a revival, and our coordination is taking place in a few different places.
- Our new domain, sandstorm.org - We are migrating things off of sandstorm.io.
-
Our blog is a good place to get up to date with major events.
- Also see Kenton's announcement about handing off the project to the community.
- Our Mastodon is a good place to stay up to date with minor events.
- Mailing lists and Matrix for support, app development news, etc. Note that we now have separate User group and Developer group mailing lists.
- Sandstorm Community Meetings - We virtually meet every week, and we take notes on our meetings. Join our mailing list or Matrix to find out how to attend.
-
Milestones - a high level overview of our upcoming high level goals, each of which can contain multiple Github Issues.
- As of May 2024, our roadmap is not well reflected in this list of Milestones. For now, connect with our community.
Various resources for users and developers
- docs.sandstorm.io contains documentation on how to use, develop apps for, or administer Sandstorm.
- To edit the docs, submit pull requests to the
docs
folder in the main Sandstorm repo. Preview docs changes by running mkdocs on your computer. Read the docs on the docs for more info.
- Again, our docs are a great place to start for basic app development. We recommended Vagrant-based development, but raw packaging is available if your needs differ.
- You may want to look at the Qubes and Hybrid guide for some special tips:
- If you have QubesOS, you will need to do raw packaging, as Vagrant isn't an option.
- If you want to do raw packaging anyway, and you want vagrant users to be able to build your app.
- You may want to look at the Qubes and Hybrid guide for some special tips:
- App Scrap Yard - apps that have been abandoned, but which may be useful for future app developers. Maybe they want to pick up where someone left off. Maybe they got a certain database to run that could be useful for a totally different project. Etc.
- Pull Request - Code Review Procedure explains our approach to code ownership & review.
- Giving credit to other open source projects explains our approach to OSS license compliance for Sandstorm core.
- English language style guide explains how we capitalize, etc., with the text that a Sandstorm user sees.
- Using the Vagrantfile explains how to use Sandstorm in a virtual machine.
- Speaker Kit - Lightning Talk - Give a lightning talk near you, and help others learn about Sandstorm!
- Testing a Sandstorm app or Sandstorm itself: Advice on how to test an app and give advice to make it even better.
- Code of Conduct, currently just for the Sandstorm SF Bay Meetup group.
- Sandstorm Talks that people have already given.
- Meetup event checklist for making sure a Meetup event page has everything it needs.
- Places to give a talk, a list of conferences and events where you can become more famous by talking about Sandstorm.
- How to approve/review apps for the app market - notes on what to look at when doing an app review.
- Security non-issues: A partial list of security issues that have not affected Sandstorm. (NOTE that this is not a statement that Sandstorm is infallible! Read more within the page.)
- Spring 2015 Sandstorm Usability Research: The goal of the Spring 2015 Sandstorm Usability Research effort is to take apps in the Sandstorm app list and make sure they truly serve people's needs.
- Contributing to external projects: A quick guide for what to do, copyright-wise, for Sandstorm people to contribute to external open source projects.
- Responding to common questions: A quick guide for e.g. people who look at Sandstorm's Twitter account
- Manual testing for Sandstorm apps: A list of things to try when testing specific Sandstorm apps
- Sandstorm public services monitoring: Information for the Sandstorm team about our public services and how they are monitored.