The benefits is that people, whether an organizer or curious visitors, can reach or discover the information they need without having to ask for it.

At Creatorsgarten, we encourage learning in public. Most of our code is public on GitHub, and we put information on our public wiki as much as possible. For some events, the income and expense are tracked in a public document. We also publish feedback we receive from event participants on the wiki.

For further reading about the public by default principle, see:

• https://about.gitlab.com/handbook/values/#transparency
• https://www.getonbrd.com/blog/public-by-default-how-we-manage-information-visibility-at-get-on-board

Financial transparency

For some events, we track the income and expense in a public document. This is to show how the money is spent, and to make it easier for participants to see the financial status of the event. Examples include:

• The Stupid Hackathon Thailand #3: Tracked in Notion
• The Stupid Hackathon Thailand #2: Tracked in Google Sheets

Non-public information

Some information is not suitable for public sharing:

• Personal information about event participants
• For a competitive event, the challenge details (albeit only temporarily)