Brew 1password

| Posted on by



  1. Brew 1password 6
  2. Brew 1password
  3. Brew 1password App
  4. Brew 1password Review
Brew 1password

# Brewfile snippet # install Python and SQLite brew 'python' brew 'sqlite' # install 1Password, Pages, and Drafts from the Mac App Store mas 'com.agilebits.

  1. Install command: brew install -cask 1password-cli.
  2. MY ACCOUNT - BREWOF BREWING INGREDIENT SUPPLY.
  3. 1pass is designed to make using your 1Password usernames and passwords quick and easy. It is intended for use within an interactive shell as well as from scripts. Once installed and configured as described below, you can obtain an account password in a shell simply by typing: $ 1pass Github.
  4. The first time you use the 1Password command-line tool, you’ll need to enter your sign-in address and email address: op signin example.1password.com wendyappleseed@example.com Then enter your Secret Key and Master Password.

This is a guide used by existing maintainers to invite new maintainers. You might find it interesting but there’s nothing here users should have to know.

There’s someone who has been making consistently high-quality contributions to Homebrew and shown themselves able to make slightly more advanced contributions than just e.g. formula updates? Let’s invite them to be a maintainer!

Brew 1password 6

First, send them the invitation email:

If they accept, follow a few steps to get them set up:

  • Invite them to the @Homebrew/maintainers team (or any relevant subteams) to give them write access to relevant repositories (but don’t make them owners). They will need to enable GitHub’s Two Factor Authentication.
  • Invite them to the homebrew-maintainers private maintainers mailing list.
  • Invite them to the machomebrew private maintainers Slack (and ensure they’ve read the communication guidelines) and ask them to use their real name there (rather than a pseudonym they may use on e.g. GitHub).
  • Ask them to disable SMS as a 2FA device or fallback on their GitHub account in favour of using one of the other authentication methods.
  • Ask them to (regularly) review remove any unneeded GitHub personal access tokens.
  • Start the process to add them as Homebrew members, for formal voting rights and the ability to hold office for Homebrew.

If they are interested in doing system administration work:

  • Invite them to the homebrew-ops private operations mailing list.
  • Invite them to the homebrew private 1Password.
  • Optionally: make them owners on the Homebrew GitHub organisation if they need to access organisation-wide settings (like GitHub Actions organisation shared runners).

If they are elected to the Homebrew’s Project Leadership Committee:

Brew 1password

  • Email their name, email and employer to the Software Freedom Conservancy at homebrew@sfconservancy.org
  • Make them owners on the Homebrew GitHub organisation
  • Invite them to the @Homebrew/plc team
  • Invite them to Google Analytics.
  • Invite them to the homebrew private 1Password.
  • Make them owners on the machomebrew private maintainers Slack).

If there are problems, ask them to step down as a maintainer and revoke their access to all of the above.

In interests of loosely verifying maintainer identity and building camaraderie, if you find yourself in the same town (e.g living, visiting or at a conference) as another Homebrew maintainer you should make the effort to meet up. If you do so, you can expense your meal (within SFC reimbursable expense policies. This is a more relaxed version of similar policies used by other projects, e.g. the Debian system to meet in person to sign keys with legal ID verification.

Now sit back, relax and let the new maintainers handle more of our contributions.

Members

Brew 1password App

People who are either not eligible or willing to be Homebrew maintainers but have shown continued involvement in the Homebrew community may be admitted by a majority vote of the Project Leadership Committee to join the Homebrew GitHub organisation as members.

When admitted as members:

Brew 1password Review

  • Invite them to the @Homebrew/members team, to give them access to the private governance repository.
  • Invite them as a single-channel guest to the #members channel on the machomebrew private maintainers Slack (and ensure they’ve read the communication guidelines) and ask them to use their real name there (rather than a pseudonym they may use on e.g. GitHub).
  • Add them to the membership list in the homebrew-governance repository.