About the Foundation for Public Code

How to staff at the Foundation for Public Code

This guide

Explains:The basics for being a staff member of the Foundation for Public Code

Contents

  1. Useful training
  2. Useful context

Contribute on GitHub

Our staff are expected to follow and uphold both the Community code of conduct and the Staff code of conduct. Make sure you are familiar with both.

In your work you will need to introduce and explain the Foundation for Public Code. You’ll answer questions about why we exist and what we do. The pitching guidance provides a good starting point to learn how to briefly explain our work to others. We also provide a guide which describes our communications activities and how we communicate with each other.

Here are some important things to figure out in the first couple of days:

  • Using space guide - how we use the spaces in the office
  • Email - you should have an account, make sure you can send and receive, you can also use a standard email signature to clearly convey who is communicating and build trust
  • Staff chat - say hello, we’re a welcoming bunch
  • Calendar - add your holidays to the team calendar
  • Manual of me - fill out your own and read the existing ones
  • Odoo - We use Odoo for project management and customer relations management
  • Github - push a branch, make a pull request (maybe to improve this page!). If you are new to this, review GitHub for newcomers. Then start with a ‘good first issue’. You can request an invitation to have your Github account added to the Foundation for Public Code organizational account.
  • Attend morning standup ritual that is in the team calendar
  • Attend sprint retrospective & planning - review the kanbans beforehand
  • Tentoo NMBRS ESS (employee self service) mobile app - to request leave, file expenses and see your payslips
  • If you already have a GitLab account you can join the Foundation for Public Code group although we don’t do any work on GitLab.
  • Start contributing!

We also have a full list of tools we use.

It’s important to understand that we strive to be an open organization. This means that we strive to use open licenses on everything we do.

The default license we use is CC0 - Public Domain.

There are some exceptions to this. If we need certainty that content will not be altered after publishing, we use CC-BY-ND. For brand assets and trademarks we do not use a free license. If external platforms don’t provide CC 0, we use one that is as free and permissive as possible.

Any of your new coworkers will be glad to help! <3

Useful training

We have collected a wide array of training that can help you in your work.

Useful context