We’re glad you’re interested in joining Pavilion!
If you’re not sure what Pavilion is yet, check out this topic first: What is Pavilion?.
Before you join, there’s a few things you should know, and a few questions you may have. This topic is intended to tell you the basics and answer some of your initial questions. You can respond here if you’d like to know more. You’ll also find more detailed resources linked throughout this post.
Why join Pavilion?
There are three main reasons for being involved in Pavilion.
Open Source and Community. All of our members support and value the open source and community-building work we do. Some members are involved for only this reason. They have income from other sources and work on our open source projects in their spare time. To learn more about our open source and community work, check out:
Earning Money. Some members are looking to earn money working on our paid projects. We have worked hard to make Pavilion a viable business in its own right and it is the primary source of income for a number of our members. If you want to know more about our paid work, check out:
Learning and Development. Some members are involved because they want to improve their software development or product management skills. Working on code or materials used in and by real communities is a great way to learn. To learn more about learning opportunites, check out:
How to join Pavilion
You need three things to join Pavilion:
Specialisation. There are two specialisations in Pavilion: Software Development and Product Management. You must choose one specialisation when joining, however you can pursue both once you’ve completed your first project.
Project. You have to be assigned to an Open Source Project to join. Open Source Projects are listed in #open-source:projects, and tagged as either #dev-needed or #pm-needed. Projects are typically months-long endeavours like becoming the maintainer of an open source plugin, or launching a new open source Pavilion service. You can only be assigned to un-assigned projects.
Sponsor. Each new member must have a sponsor with an “Senior” badge in the specialisation they wish to join on. Your sponsor is your collaborator or mentor on your first project. You can find lists of members with Senior badges in Software Development and Product Management on this site.
To start the process you simply have to @mention a Senior member in the relevant specialisation on an unassigned project you wish to work on.
There’s a more detailed description of how membership works, including how to join, here:
Things you should know
We work remotely
One of the biggest things to be aware of is that almost everything we do is done remotely. We work with clients remotely, we work with the users of our open source work remotely and we talk with each other remotely. Most of our communication is through our Discourse, i.e. this website. There’s a detailed topic on the different mediums we use to communicate here: How we communicate.
The tyranny of distance can raise some issues that you may not be used to. You often have to wait for people in a different timezone to wake up before they respond to a topic or message. You may need to attend meetings at odd hours. Meaning can sometimes be lost in text-based communication. It can be harder to create a “human” connection in text-based or even video-based communication.
There are also benefits to working remotely. Sometimes timezones can work in your favour by giving you extra breathing space to get a piece of work done. Longform communication can be useful to focus and structure your thoughts. Being awake when the users of a site you’re working on are asleep can making scheduling updates easier.
We also have developed ways of working and collaborating to make the distance feel smaller. We have at least one virtual member meetup each month, where you get the chance to just hang out with the other members without having to talk about work. We’re looking to run in-person meetups as well.