Getting Involved​

If you are interested in helping out with the Lando project, then you've come to theright place! We are looking for people to help out in any of the capacities as follows:

If any of the above sound up your alley, then please proceed togetting started. If not than we ask you at least go over toGitHub and give us a star ⭐.

Getting Started​

To get started you need to doat least one of the below but weHIGHLY RECOMMEND you just do them all:

1. Join the contributors mailing list
2. Join the #contributors channel on Slack
3. Complete our contributor Google Form
4. Create, flag and/or assign some issues you are interested in
5. Come to your first contributor meeting

Comms​

These are the channels we usually use for communication.

GitHub​

GitHub serves as the mechanism for all Lando code, issue reporting/tracking and project management.

While theLando Organization serves as the starting point for all Lando projects, most collaboration is going to occur in the coreLando Project and itsissue queue.

Slack​

Slack serves as the mechanism for Lando support and contributor coordination. You can join the Lando slack org viaLaunchPass. By default, you will be added to the#community channel which is our free and open community support channe but you should also join#contributors.

There are also some other channels you can join at your discretion:

• #administrators - For those who help administer and coordinate Lando
• #bloggers - For those contributing case studies, training materials and other content to the blog
• #evangelists - For those looking to evangelize Lando at meetups, events, camps, etc
• #guiders - For those writing helpful Lando guides and tutorials
• #upsellers - For those helping to help sell Lando sponsorships, support and services
• #social - For suggesting social content for Lando
• #kalabox - For legacy Kalabox community support

Join some channels and say hi!

X/Twitter​

X/Twitter is our primary outreach and social channel. If you are fearless, thenfollow us and get involved in the conversation!

Choosing an Issue​

If you don't already have a GitHub issue or two in mind you can go through them in a few different ways:

• By maintainer projects
• By individual repo
• By all issues in the org

If you don't see one you can alsocreate your own. However once you have an issue or two in mind you will want to do possibly both of the below:

• Label the issue withflag - This will add it into the relevant contributor project board so a maintainer knows to discuss it in their next meeting.
• Assign the issue to yourself - If it's an issue you want to take on thenassign it to yourself.

If you cannot label or assign an issue then we probably need to invite you to collaborate. To do that jump in the#contributors channel in Slack, post your issue and indicate you want to self-assign it and a maintainer will send you an invite.

Note that permissions are given on a per-repo basis so you'll need to do this once for every repo you want to work on.

Meetings​

We are currently meeting for three dedicated purposes:Plugins,DevOps andGovernance & Maintainership, here are the next meetings:

• DevOps - Tuesday, March 25, 2025 @ 4:00:00 PM UTC
• Plugins - Tuesday, March 18, 2025 @ 4:00:00 PM UTC
• Governance & Maintainership - TBD

Make sure youjoin the mailing list and/or#contributors channel in our Slack to get invited/access to the meetings.

Archives​

• March 27, 2024 - Kickoff Meeting

We also putall the raw dataover here in Google Drive if you want to sift through things.