loopbackio / loopbackio/loopback-governance

Add OpenJS Foundation accounts to our services used

Open
#21 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

openjsf
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

From the OpenJS Foundation (OpenJSF) Infrastructure Menu:

For all project services, please add an OpenJS Foundation account at an owner or highest-level of permission access. This helps ensure continuity by reducing the bus factor on the project, and ensures you are never locked out. It is also required in order for the OpenJS Foundation to pay service fees on behalf of your project. Access to the OpenJS Foundation administrator/owner account will never be shared with others, and will only be granted to operations, IT, and finance staff at the Linux Foundation.

If you don’t know the name of the OpenJS Foundation account for a service, please contact operations@openjsf.org.

and

The OpenJS Foundation admin account must be added as administrator for each repository.

Currently know list of services used:

Service that may be upcoming:

  • Azure (From Azure Open Source Credits program)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the checklist in issue #21 and review the linked OpenJS Foundation Infrastructure Menu. Verify the required OpenJS Foundation account access for GitHub, Appveyor, and any upcoming Azure service, coordinating with operations@openjsf.org where the account name or permissions are unknown. Done means each applicable service has the required administrator or highest-level access and the checklist reflects the current status.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, github
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.