mirrors/brew
0
0 Fork 0
mirror of https://github.com/Homebrew/brew.git synced 2026-10-28 09:34:42 +08:00
Code Activity

docs: restyle governance and maintainer process pages

Browse Source 
Signed-off-by: Patrick Linnane <patrick@linnane.io>
This commit is contained in:
Patrick Linnane committed 2026-07-18 23:34:31 -07:00
1 parent 67390e0b61
commit df3eb44e1e
6 files changed
+97 -94
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/Homebrew-Governance-Archives.md
+1 -1
View File
@@ -1,5 +1,5 @@
---
last_review_date: "1970-01-01"
last_review_date: "2026-07-18"
---
# Homebrew Governance Archives
docs/Homebrew-Governance.md
+9 -9
View File
@@ -103,7 +103,7 @@ No single person holds special authority beyond the Project Leader role.
- Serves as the primary point for formal communications and external coordination, and may delegate public representation to other Lead Maintainers as needed.
- Coordinates day-to-day operations, executes addition and removal of Maintainers under the eligibility criteria and inactivity policies defined in this document, and ensures project-level decisions are followed through.
- Organizes Lead Maintainer discussions.
- Organises Lead Maintainer discussions.
- Executes and ensures decision-making processes as required by this governance document.
- Facilitates AGM planning and/or appoints designees to do so.
@@ -127,11 +127,11 @@ No single person holds special authority beyond the Project Leader role.
---
## 3. Decision-Making
## 3. Decision-making
Formal governance decisions are made by vote of all Maintainers.
Major financial decisions (i.e. changes to existing documented financial processes or new one-time expenditures) are made by vote of the Lead Maintainers.
Minor financial approvals (i.e. approving expected OpenCollective expenses) can be made by any Lead Maintainer.
Minor financial approvals (i.e. approving expected Open Collective expenses) can be made by any Lead Maintainer.
- Informal decisions may proceed by discussion unless a vote is requested by any Lead Maintainer.
- Formal votes require a simple majority.
@@ -144,29 +144,29 @@ Minor financial approvals (i.e. approving expected OpenCollective expenses) can
- When voting is conducted using pull request review:
- Voting will begin when the pull request is opened.
- Voting is conducted as follows:
- To vote in favor: Submit a ✅ review approval, or if lacking write permissions, a comment review with a ✅ emoji in the comment.
- To vote in favour: Submit a ✅ review approval, or if lacking write permissions, a comment review with a ✅ emoji in the comment.
- To vote against: Submit a ❌ "request changes" review, or if lacking write permissions, a comment review with a ❌ emoji in the comment.
- To abstain: Submit a comment review containing the word "abstain".
---
## 4. Security & Emergency Actions
## 4. Security & emergency actions
- The Security Team is comprised of any number of Maintainers appointed by the Project Leader, serving until resignation or removal from the team by the Project Leader.
- The Project Leader and 2 other Lead Maintainers are granted the necessary technical permissions (e.g. Owner or Admin roles) on all primary Homebrew repositories and infrastructure to immediately revoke access in emergencies.
When possible, these 2 Lead Maintainers should be members of the Security Team.
If there are not enough eligible Lead Maintainers on the Security Team, the Project Leader will appoint other Lead Maintainers to fulfill this role, with the appointments subject to confirmation by a simple majority vote of all Lead Maintainers.
If there are not enough eligible Lead Maintainers on the Security Team, the Project Leader will appoint other Lead Maintainers to fulfil this role, with the appointments subject to confirmation by a simple majority vote of all Lead Maintainers.
- In emergencies (e.g. malicious commits, compromised credentials, abuse of access), any Lead Maintainer may immediately revoke access and must notify all other Lead Maintainers.
- A formal review must occur within 7 days and be published to all Maintainers within 21 days.
- Restoration or permanent removal is determined by a simple majority vote of Lead Maintainers.
---
## 5. Transparency & Updates
## 5. Transparency & updates
- This document will be reviewed annually.
### Amendment Process
### Amendment process
- **Who can propose changes:** Any Maintainer or Lead Maintainer may propose amendments to this document.
- **How to propose:** Proposed changes must be submitted as a pull request with a clear rationale and summary.
@@ -176,7 +176,7 @@ Minor financial approvals (i.e. approving expected OpenCollective expenses) can
---
## 6. Code of Conduct
## 6. Code of conduct
All contributors, Maintainers and Lead Maintainers must follow the Homebrew [Code of Conduct](https://github.com/Homebrew/.github/blob/HEAD/CODE_OF_CONDUCT.md).
docs/Homebrew-Leadership-Responsibilities.md
+3 -3
View File
@@ -4,7 +4,7 @@ last_review_date: "2025-11-26"
# Homebrew Leadership Responsibilities
## Project Leader Sole Responsibilities
## Project Leader sole responsibilities
- manage all day-to-day technical decisions
- resolve disputes related to the operation of Homebrew between maintainers, other contributors, and users
@@ -12,11 +12,11 @@ last_review_date: "2025-11-26"
- each quarter: checking for activity of maintainers and asking them to step down if they have not been active enough in the past quarters
- organising the AGM (with delegation of tasks to other maintainers)
## Lead Maintainers Sole Responsibilities
## Lead Maintainers' sole responsibilities
- decide on technical disputes between Homebrew maintainers and the Project Leader
## Project Leader and Lead Maintainers Shared Responsibilities
## Project Leader and Lead Maintainers' shared responsibilities
- blocking abusive GitHub users
- approving Open Collective expenses that are expected or have already been agreed upon by the Lead Maintainers (e.g. Homebrew cloud usage on a personal credit card) (only one approval needed)
docs/How-To-Organise-the-AGM.md
+38 -40
View File
@@ -1,7 +1,8 @@
---
last_review_date: "2025-11-26"
last_review_date: "2026-07-18"
---
# How To Organise the AGM
# How to Organise the AGM
The Annual General Meeting (AGM) is our combination of a business meeting, yearly work planning session, and opportunity to meet others in our international team in person.
@@ -11,7 +12,7 @@ If a situation occurs that prevents that, it is acceptable to execute it virtual
<!-- TOC start -->
* [Roles](#roles)
* [Logistics Timeline](#logistics-timeline)
* [Logistics timeline](#logistics-timeline)
* [Two months prior](#two-months-prior)
* [Four weeks prior](#four-weeks-prior)
* [Three weeks prior](#three-weeks-prior)
@@ -21,9 +22,9 @@ If a situation occurs that prevents that, it is acceptable to execute it virtual
* [Day before](#day-before)
* [Day-of](#day-of)
* [Pre-planning](#pre-planning)
* [Finding a Meeting Venue](#finding-a-meeting-venue)
* [Who Qualifies For AGM Travel Assistance](#who-qualifies-for-agm-travel-assistance)
* [Dietary Requirements](#dietary-requirements)
* [Finding a meeting venue](#finding-a-meeting-venue)
* [Who qualifies for AGM travel assistance](#who-qualifies-for-agm-travel-assistance)
* [Dietary requirements](#dietary-requirements)
<!-- TOC end -->
@@ -31,38 +32,33 @@ If a situation occurs that prevents that, it is acceptable to execute it virtual
Expected participants:
|Who|Role|
|---|---|
|Project Leader (PL)|Should be physically present if possible, dialed-in if not. Regardless, needed to provide content for meeting.|
|Lead Maintainers (LM)|Should be physically present if possible, dialed-in if not. Regardless, needed to provide content for meeting.|
|Maintainers|Should dial-in or participate in person if possible.|
| Who | Role |
| --------------------- | ---------------------------------------------------------------------------------------------- |
| Project Leader (PL) | Should be physically present if possible and dialled in otherwise, providing meeting content. |
| Lead Maintainers (LM) | Should be physically present if possible and dialled in otherwise, providing meeting content. |
| Maintainers | Should dial in or participate in person if possible. |
Delegated maintainer roles of responsibility for planning and execution:
|Who|Role|
|---|---|
|Logistics Coordinator (LC)|Coordinates with meeting venue, restaurants, vendors, maintainers|
|Agenda Coordinator (AC)|Coordinates agenda and content to be presented|
|Technology Coordinator (TC)|Coordinates video conference audiovisual setup|
| Who | Role |
| --------------------------- | ------------------------------------------------------------------------ |
| Logistics Coordinator (LC) | Coordinates with the meeting venue, restaurants, vendors and maintainers. |
| Agenda Coordinator (AC) | Coordinates the agenda and content to be presented. |
| Technology Coordinator (TC) | Coordinates the video-conference audiovisual setup. |
A person may have more than one role but one person should not have all roles.
## Logistics Timeline
## Logistics timeline
Past practice and future intent is for AGM to coincide with [FOSDEM](https://fosdem.org "Free and Open Source Developers European Meeting"), which is held in Brussels, Belgium annually typically on the Saturday and Sunday of the fifth ISO-8601 week of the calendar year, calculable with:
Past practice is for the AGM to coincide with [FOSDEM](https://fosdem.org "Free and Open Source Developers European Meeting") in Brussels, Belgium.
The AGM is normally held on the Friday before FOSDEM or the following Monday.
ruby -rdate -e "s=ARGV[0].to_i;s.upto(s+4).map{|y|Date.commercial(y,5,6)}.each{|y|puts [y,y+1].join(' - ')}" 2026
AGM should be held on the Friday before or the Monday following FOSDEM.
:information_source: _Regenerate the dates for the WHEN lines in the next several headers
using this quick command:_
ruby -rdate -e "YEAR=ARGV[0].to_i;puts ([[49,YEAR-1]]+(1.upto(4).map{|wk|[wk, YEAR]})).map{|wk,yr|Date.commercial(yr,wk).to_s}" 2026
Confirm the published FOSDEM dates before opening travel approval or making reservations.
Use the relative timeline below and record year-specific dates in the private planning issue or project rather than embedding them in this reusable guide.
### Two months prior
**When:** Week 49 of YEAR-1 :date: `2025-12-01`
**When:** Approximately two months before the AGM.
* [ ] LC: Seek informal count of maintainers intending to attend in person.
* [ ] PL: Review maintainer activity per [Homebrew Governance](Homebrew-Governance.md).
@@ -70,26 +66,28 @@ using this quick command:_
* This is primarily to enable maintainers to begin planning travel by
asking for time off, requesting employer reimbursement,
arranging childcare or pet sitters,
[applying for a visa](https://5195.f2w.bosa.be/en/themes/entry/border-control/visa/visa-type-c)
which may [take 2–7 weeks](https://dofi.ibz.be/en/themes/third-country-nationals/short-stay/processing-time-visa-application),
[applying for a visa](https://5195.f2w.bosa.be/en/themes/entry/border-control/visa/visa-type-c),
which may [take two to seven weeks](https://dofi.ibz.be/en/themes/third-country-nationals/short-stay/processing-time-visa-application),
etc.
* [ ] PL: Remind those traveling from countries exempt from EU visa requirements (e.g. US, UK, AU, CA) to file for [ETIAS travel authorization](https://travel-europe.europa.eu/etias_en) (generally processed in minutes but could take up to 30 days), advisable to get processed _before_ buying airfare.
* [ ] PL: Check the [official EU travel requirements](https://travel-europe.europa.eu/etias_en) for each traveller's nationality and travel dates.
Do not direct travellers to apply unless the official page says the service is operating.
Once it is operating, allow for the published maximum processing time before non-refundable travel is purchased.
### Four weeks prior
**When:** Week 1 of YEAR :date: `2025-12-29`
**When:** Approximately four weeks before the AGM.
* [ ] PL: Solicit changes to [Homebrew Governance](Homebrew-Governance.md) in the form of PRs to the `private` repository.
### Three weeks prior
**When:** Week 2 of YEAR :date: `2026-01-05`
**When:** Approximately three weeks before the AGM.
* [ ] PL: Close travel assistance pre-approval process.
### Two weeks prior
**When:** Week 3 of YEAR :date: `2025-01-06`
**When:** Approximately two weeks before the AGM.
* [ ] AC: Create agenda, solicit agenda items from PL and LM.
* [ ] LC: Seek committed maintainer attendance and dietary requirements for each.
@@ -97,13 +95,13 @@ using this quick command:_
### 10 days prior
**When:** Week 3 of YEAR :date: `2026-01-12`
**When:** 10 days before the AGM.
* [ ] PL: Resolve all open Governance PRs, roll-up changes, and open PR with changes to `docs/Homebrew-Governance.md` on `homebrew/brew`.
### One week prior
**When:** Week 4 of YEAR :date: `2026-01-19`
**When:** One week before the AGM.
* [ ] PL: Open voting for PL and Governance changes.
* [ ] AC: Solicit agenda items from maintainers.
@@ -117,18 +115,18 @@ using this quick command:_
### Day-of
* [ ] LC: Confirm reservation count for dinner with venue
* [ ] TC: Connect to video conference, ensure audiovisual equipment is ready and appropriately placed and leveled periodically
* [ ] AC: Keep the meeting paced to the agenda, keep time for timeboxed discussions, cut people off if they're talking too long, ensure remote attendees can get a word in
* [ ] TC: Connect to the video conference and ensure that audiovisual equipment is ready, appropriately placed and periodically levelled.
* [ ] AC: Keep the meeting to the agenda and time-boxed discussion limits while ensuring remote attendees can participate.
## Pre-planning
### Finding a Meeting Venue
### Finding a meeting venue
In the past, Homebrew hosted the AGM at the
[THON Hotel Brussels City Centre](https://www.thonhotels.com/conference/belgium/brussels/thon-hotel-brussels-city-centre/?Persons=20)
and arranged for a room block checking in the day before FOSDEM and AGM weekend, generally on Friday, and checking out the day after, generally Tuesday when the AGM is Monday.
### Who Qualifies For AGM Travel Assistance
### Who qualifies for AGM travel assistance
Travel assistance is available for AGM participants who are expected to attend the AGM in-person.
Those who have employers able to cover all or a part of the costs of attending FOSDEM should exhaust that
@@ -139,6 +137,6 @@ PL, LM and maintainers can expect to have all reasonable, in-policy expenses cov
See also the [Expense and Reimbursement Travel Policy](Expense-and-Reimbursement-Policy.md#travel-policy) for process and details on what is covered.
It is important that all attendees expecting reimbursement stay in-policy.
### Dietary Requirements
### Dietary requirements
Track dietary requirements centrally for in-person participants.
docs/Maintainer-Stipends-and-Grants.md
+42 -39
View File
@@ -1,28 +1,30 @@
---
last_review_date: "2026-07-18"
---
# Maintainer Stipends and Grants
## Maintainer Stipends
The Lead Maintainers own and approve this policy.
## Maintainer stipends
### Eligibility
The PL will notify quarterly the maintainers who have insufficient maintainer contributions for the prior quarter's stipend.
Each quarter, the Project Leader will notify maintainers whose contributions in the preceding quarter were insufficient for the stipend.
The PL reviews those who are receiving the stipend for activity in mid-late December/March/June/September.
The PL reviews those for AGM attendance expenses eligibility in mid-late December.
The Project Leader reviews stipend eligibility in the second half of March, June, September and December.
The Project Leader reviews eligibility for Annual General Meeting travel assistance in the second half of December.
Maintainers will not receive the stipend for months where they are doing paid project work.
### Amount and Frequency
### Amount and frequency
The stipend is $300/month.
We pay maintainers via invoice from the [OpenCollective](https://opencollective.com/homebrew).
Maintainers are paid through invoices submitted to [Homebrew on Open Collective](https://opencollective.com/homebrew).
### Invoicing and Getting Paid
### Invoicing and getting paid
To reduce administrative overhead, maintainers should
[set their invoices to recur once per quarter](https://docs.opencollective.com/help/expenses-and-getting-paid/submitting-expenses#regular-recurring-expenses)
tagging the request with `maintainer-stipend` and
submit them to the [OpenCollective](https://opencollective.com/homebrew)
in the amount of $`\$300 \times 3 = \$900`$ USD.
To reduce administrative overhead, maintainers should [set their invoices to recur once per quarter](https://docs.opencollective.com/help/expenses-and-getting-paid/submitting-expenses#regular-recurring-expenses), tag the request with `maintainer-stipend` and submit it to [Homebrew on Open Collective](https://opencollective.com/homebrew) for US$900, covering three months at US$300 per month.
Invoices must be filed during January, April, July and October for the preceding quarter.
If previous invoices were submitted on a different schedule, please adjust the amounts and the new schedule accordingly.
@@ -30,7 +32,7 @@ If previous invoices were submitted on a different schedule, please adjust the a
Invoices must contain:
* The date the invoice was created
* A due date no less than 30 days after the creation date (NET30)
* A due date at least 30 days after the creation date (NET30)
* Your legal banking name
* Your mailing address
* A line item for each quarter you are owed, noted as
@@ -40,27 +42,25 @@ Invoices must contain:
and the amount of the stipend.
If the invoice template you are using has a quantity field, simply use 1.
OpenCollective handles payment transfer, so ensure that you have enrolled
in its payment system prior to submitting your invoice or payment will be delayed.
Open Collective handles the payment transfer.
Enrol in its payment system before submitting an invoice; otherwise, payment will be delayed.
(Update this list if OpenCollective changes its invoicing requirements.)
### Things to know
### Things to Know
Maintainers who sponsor Homebrew for any amount should consider canceling that sponsorship.
Maintainers who sponsor Homebrew for any amount should consider cancelling that sponsorship.
We appreciate the historical support, but being an active maintainer is more valuable to the project.
Moreover, contributing while receiving payment may complicate your taxes in some countries!
### Stipend Program History
### Stipend program history
In November 2022, the Project Leadership Committee voted to pay maintainers a minimal monthly stipend via GitHub Sponsors.
This was in an effort to utilize our accrued funds alongside paying for larger, individual development projects, such as the API installation improvements and CI runners.
The programme used accrued funds alongside larger individual development projects, such as API installation improvements and CI runners.
In August 2023, the Project Leadership Committee voted to change the way we pay maintainers from GitHub Sponsors to quarterly invoices submitted through OpenCollective.
In August 2023, the Project Leadership Committee voted to change the way we pay maintainers from GitHub Sponsors to quarterly invoices submitted through Open Collective.
In December 2025, the Project Leadership Committee was replaced with the Lead Maintainers.
## Maintainer Grants
## Maintainer grants
Homebrew offers several grants to maintainers who are working to improve Homebrew. The Lead Maintainers authorise support for these categories of activities:
@@ -69,10 +69,11 @@ Homebrew offers several grants to maintainers who are working to improve Homebre
1. Travel to conferences
1. Travel to the Homebrew Annual General Meeting
In accordance with the [Expense and Reimbursement Policy](Expense-and-Reimbursement-Policy.md), Lead Maintainers pre-approval is required.
You can also contact a Lead Maintainer via Slack for presubmission enquiries.
The [Expense and Reimbursement Policy](Expense-and-Reimbursement-Policy.md) requires pre-approval from the Lead Maintainers.
You can contact a Lead Maintainer through the private maintainer communication channel before submitting a request.
The Lead Maintainers may also support *ad hoc* awards; if you believe that your proposed expense would advance Homebrew's project goals these should be sent to [OpenCollective](https://opencollective.com/homebrew) to be approved by Lead Maintainers.
The Lead Maintainers may also support *ad hoc* awards.
Submit a proposal that explains how the expense advances Homebrew's goals before creating the [Open Collective](https://opencollective.com/homebrew) reimbursement request.
See [Expense and Reimbursement Policy's *Getting Reimbursed* section](Expense-and-Reimbursement-Policy.md#getting-reimbursed) for instructions how to submit expenses approved for the following sections.
Remember to tag the reimbursement request with `maintainer-grant`.
@@ -83,20 +84,20 @@ Maintainer hackathons can be organised to rapidly develop new features or otherw
* Well-defined goals that the hackathon will aim to achieve
* List of (tentatively) attending maintainers and their departure cities
* Proposed schedule with dates, location, and itemized budget
* Proposed schedule with dates, location and itemised budget
You can also contact a Lead Maintainer member via Slack for presubmission enquiries.
You can contact a Lead Maintainer through the private maintainer communication channel before submitting a request.
Organisers should, if possible, seek local sponsorships to offset costs of e.g. venue or equipment hire. Organisers should also budget for group meals for lunches and dinners to build maintainer camaraderie.
The Lead Maintainers will reimburse travel expenses for reasonably local maintainers. For example, reimbursement for hackathon travel between Australia and Europe is unlikely, but reimbursement for travel within Europe is acceptable.
See the [Expense and Reimbursement Policy's Meals and Entertainment section](Expense-and-Reimbursement-Policy.md#meals-and-entertainment) on what meals may be covered.
All attendees will be expected to follow Homebrew's [Code of Conduct](https://github.com/Homebrew/.github/blob/master/CODE_OF_CONDUCT.md#code-of-conduct).
All attendees must follow Homebrew's [Code of Conduct](https://github.com/Homebrew/.github/blob/HEAD/CODE_OF_CONDUCT.md#code-of-conduct).
After the hackathon finishes, the organiser must provide to the Lead Maintainers a brief report on who attended and what was accomplished, with links to pull requests or other verifiable achievements.
## Homebrew Hardware
## Homebrew hardware
The Lead Maintainers will reimburse reasonable purchases of hardware necessary to maintain Homebrew. To apply, a maintainer should submit to the Lead Maintainers for pre-approval:
@@ -109,30 +110,32 @@ Eligibility for hardware grant is also subject to the following:
1. The maintainer must have been eligible for the maintainer stipend the last 4 quarters and been a maintainer at least a year.
1. A maintainer can only apply for hardware once every 4 years.
Note that Homebrew should not be buying anyone a top-of-the-range MacBook.
As-of April 2024, for example, you can buy 14" and 16" MacBook Pros with 18GB-128GB memory, 512GB-8TB storage and M3 Pro or Max CPUs.
The best balance between cost and performance would be, at most, the 16" MacBook Pro with 36GB memory, 512GB storage and M3 Pro CPU.
Regardless, the cost to Homebrew must be less than $4000 USD, maintainers are allowed to pay the difference if they insist on higher specs.
Homebrew does not fund top-of-the-range hardware when a lower-cost configuration meets the documented maintenance need.
The request must compare current models and explain the selected balance of cost, performance and expected useful life.
Homebrew's contribution must be less than US$4,000.
A maintainer may pay the difference for a more expensive configuration after the Homebrew-funded configuration has been approved.
You can also contact a Lead Maintainer via Slack for presubmission enquiries.
You can contact a Lead Maintainer through the private maintainer communication channel before submitting a request.
## Conference travel
The Lead Maintainers may reimburse maintainers who attend conferences that advance the goals of Homebrew. For budgetary reasons, maintainers who have support via e.g. their employer or the conference, are asked to use those funds prior to requesting reimbursement from Homebrew. The Lead Maintainers encourage maintainers to give presentations related to Homebrew; if you choose to do so, please acknowledge Homebrew's support and share your poster/slides/recorded talk, where possible.
The Lead Maintainers may reimburse maintainers who attend conferences that advance Homebrew's goals.
Maintainers who can obtain support from an employer, conference or another source should use that support before requesting Homebrew funds.
Maintainers giving a Homebrew-related presentation should acknowledge Homebrew's support and share the poster, slides or recording where possible.
To apply for reimbursement of conference expenses, a maintainer must submit to the Lead Maintainers:
* The name, location, and dates of the conference
* The workshops, panels, or other events where maintainer attendance can benefit Homebrew
* The title of the Homebrew-related presentation (if applicable)
* An itemized estimate of conference expenses
* An itemised estimate of conference expenses
As justification for attendance, the Lead Maintainers may ask the maintainer for a brief report on the conference, and how attending the conference has helped or could help improve Homebrew.
All travellers will be expected to follow Homebrew's [Code of Conduct](https://github.com/Homebrew/.github/blob/master/CODE_OF_CONDUCT.md#code-of-conduct), in addition to any policies that the conference itself may have.
All travellers must follow Homebrew's [Code of Conduct](https://github.com/Homebrew/.github/blob/HEAD/CODE_OF_CONDUCT.md#code-of-conduct) and the conference's policies.
## Annual General Meeting
The Lead Maintainers will typically reimburse the expenses of active maintainers to attend the Homebrew Annual General Meeting. The Lead Maintainers will solicit applications via Slack yearly, around October. Maintainers who have not yet attended an annual meeting are especially encouraged to apply.
The Lead Maintainers will typically reimburse the expenses of active maintainers to attend the Homebrew Annual General Meeting. The Lead Maintainers will solicit applications through the private maintainer communication channel yearly, around October. Maintainers who have not yet attended an annual meeting are especially encouraged to apply.
See [Expense and Reimbursement Policy's *Getting Reimbursed* section](Expense-and-Reimbursement-Policy.md#getting-reimbursed) for instructions how to seek approval for travel and submit approved expenses.
docs/index.md
+4 -2
View File
@@ -47,8 +47,6 @@ Documentation is grouped below by audience: users, contributors, maintainers and
- [Updating Software in Homebrew](Updating-Software-in-Homebrew.md)
- [Adding Software to Homebrew](Adding-Software-to-Homebrew.md)
- [Kickstarter Supporters](Kickstarter-Supporters.md)
## Contributors
- [How to Open a Pull Request (and get it merged)](How-To-Open-a-Homebrew-Pull-Request.md)
@@ -100,3 +98,7 @@ Documentation is grouped below by audience: users, contributors, maintainers and
- [Homebrew's Expense and Reimbursement Policy](Expense-and-Reimbursement-Policy.md)
- [How To Organise the Homebrew AGM](How-To-Organise-the-AGM.md)
- [Homebrew's Maintainer Stipends and Grants](Maintainer-Stipends-and-Grants.md)
## Project history
- [Kickstarter Supporters](Kickstarter-Supporters.md)