---
title: "Free office hours for open-source maintainers"
url: https://meet.barq.dev/for/open-source-maintainers
updated: 2026-11-17
author: "Hammad Ali"
---

# Free office hours for open-source maintainers

> **Short answer:** Open-source maintainers can offer contributor office hours and sponsor calls through a Google Calendar booking page. Barq Meet lets you separate those conversations and limit daily bookings; a 20-minute call with ten minutes afterwards occupies half an hour. Keep bug reports in the repository, and use another system for rotating maintainer coverage.


## Which maintainer conversations deserve office hours?

Offer office hours for a contributor who's stuck on an agreed change, a release decision that needs discussion, or a sponsor's project questions. Keep reproducible bug reports and routine support in issues so the answer remains available to people who weren't on the call.


A link isn't a support contract. Describe the call's purpose before the calendar, including what the contributor should read and where any resulting decision will be recorded.


We let you create distinct events, so a sponsor conversation can have a longer duration than a contributor introduction. Give each one its own description instead of treating every request as thirty minutes of unspecified help.


The [booking features overview](https://meet.barq.dev/features) covers those event controls. For a maintainer's booking page, a practical description might say: bring the issue number and the decision you need help making; write any agreed next step back in the issue afterwards.


## How can I keep contributor calls inside one afternoon?

Start with a single weekly block, a notes buffer and a daily limit on the contributor event. These are proposed settings for office hours for open-source maintainers, not a claim about how much support any project should provide. For a conversation spanning [dated Chicago and India hours](https://meet.barq.dev/meeting-planner/chicago-and-india), check the shared workday before repeating a familiar start in another season.


| Call purpose | Appointment | Buffer before / after | Minimum notice | Preparation question | Link to share |
| --- | --- | --- | --- | --- | --- |
| Contributor unblock | 20 minutes | 0 / 10 minutes | 24 hours | Which issue or pull request? | Public event |
| Sponsor update | 30 minutes | 0 / 15 minutes | 48 hours | Which project topic? | Secret event URL |
| Release decision | 45 minutes | 5 / 10 minutes | 24 hours | Which decision needs a call? | One-off invitation |

Suppose you offer contributor calls on Wednesday between 14:00 and 16:00, with thirty-minute start steps and no calendar conflicts. Starts at 14:00, 14:30, 15:00 and 15:30 allow four twenty-minute calls plus their ten-minute gaps.


Four is the maximum here. Set "Maximum bookings per day" to three on that event if you want fewer commitments; don't rely on an empty calendar to protect coding time.


That setting belongs to the event. If you also offer sponsor calls, inspect their hours and bookings before describing three as a cap across your whole diary.


## How should sponsor calls differ from public contributor calls?

Give sponsors a dedicated event with its own preparation question and distribute its URL in the sponsor conversation. A secret event stays off the public profile, but someone can forward its link; use "Requires approval" when you need to make the final invitation decision.


Keep expectations in writing. A call description can explain which project the discussion concerns without promising delivery dates, priority support or influence over technical decisions. The [developer-relations setup](https://meet.barq.dev/for/developer-relations) keeps individual technical discussions separate from group capacity and issue tracking.


We put "Secret event" and "Requires approval" under "Booking page" in the event editor. Hiding the listing and reviewing a request are different controls, and neither establishes a person's sponsorship status for you.


You still need to decide who should attend. If two maintainers are required, coordinate their availability before offering the call, because this individual booking setup won't search for a time when both are free.


## How do I publish office hours for contributors in other time zones?

Set the schedule's time zone to the one you work in, then let contributors inspect the booking page in their own zone. Offer another block only when you can attend it; a global project doesn't require a calendar that's permanently open.


Test a distant date too. A contributor may be traveling or have a browser using a different zone, so mention that the displayed zone should be checked before confirmation.


1. Connect Google Calendar and select the calendars containing work and personal commitments.
2. Create the contributor event and select its schedule under "When people can book".
3. Open "Advanced" to enter the buffers, "Minimum notice" and "Start-time steps".
4. Add the issue-number question and make a test booking before publishing the link.


We re-check the selected calendars at confirmation, so an appointment created after someone opened the page can remove that slot. That final check still matters when a contributor has spent several minutes reading the preparation instructions before confirming the appointment.


## Where should the office-hours link live after setup?

Place the office-hours URL beside your contribution guidance, with the purpose and expected preparation stated alongside it. Keep support channels visible too, so a contributor who can't attend the offered hours still has a written route to ask for help. For non-urgent help, the [support appointment recipe](https://meet.barq.dev/for/it-support) separates a scheduled conversation from the remote-access process itself. For employee office hours, use the [HR booking recipe](https://meet.barq.dev/for/hr-teams) to ask for a neutral topic instead of a complaint's full details.


Begin with one placement. The [guide to sharing a booking link](https://meet.barq.dev/guides/where-to-share-your-booking-link) explains how to put a link where readers already expect the invitation. The [office-hours announcement examples](https://meet.barq.dev/templates/office-hours-announcement-email) explain which contributor questions belong in a booked discussion and which should remain asynchronous.


There's no paid tier for these controls, although generous fair-use limits apply to stop abuse. Review [what the account includes](https://meet.barq.dev/pricing), then [set up your maintainer office hours](https://meet.barq.dev/app/sign-in) when an individual Google-connected diary is what you need.

## Frequently asked questions

### Should contributors book a call before opening an issue?

Usually, no. Ask contributors to describe the problem in the repository first, then invite a call when a written discussion needs one. A booking page can organize that conversation without becoming a private replacement for the project's issue history. Keep routine questions asynchronous and offer a call when the issue needs a live discussion with the maintainer responsible for it.

### Can I reserve sponsor calls for people I invite?

Yes, you can distribute a secret event's direct URL to sponsors instead of listing it publicly. The URL remains forwardable, so review the request yourself if sponsorship status matters; hiding an event doesn't verify who receives its link. Mark the sponsor offer as secret and share its address selectively, with request approval if forwarded invitations need your review.

### Will a booking create a video room?

Choose Google Meet as the event's location when you want an automatically created meeting link. Use a phone or another custom location when the conversation belongs elsewhere, and check that instruction in the confirmation before sharing office hours publicly. Inspect the location in a sample confirmation, and distinguish an automatically created Meet address from a room URL you supplied yourself.

## Related pages

- [Scheduling features](https://meet.barq.dev/features)
- [Free scheduling, with every feature included](https://meet.barq.dev/pricing)
- [Where to share your booking link: 25 places that work](https://meet.barq.dev/guides/where-to-share-your-booking-link)
- [Office hours announcement email templates](https://meet.barq.dev/templates/office-hours-announcement-email)
- [Free scheduling for IT support appointments](https://meet.barq.dev/for/it-support)
- [Free scheduling for HR 1:1s and benefits office hours](https://meet.barq.dev/for/hr-teams)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
