Add OpenJS Foundation accounts to our services used
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, github
- Domain
- devops, infrastructure
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.
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:
- GitHub - Account: @/thelinuxfoundation; Privileges: Org Owner; Invitation: Awaiting acceptance
Services tied to GitHub auth:- Appveyor (Implied) (https://www.appveyor.com) - Permission mapping: https://www.appveyor.com/docs/team-setup/#github-integration
- Travis CI (Implied) (https://www.travis.com) - Permission mapping: https://docs.travis-ci.com/user/travis-ci-for-private/#who-has-access-to-the-builds
- Coveralls (Implied)
Service that may be upcoming:
- Azure (From Azure Open Source Credits program)
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from loopbackio/loopback-governance
-
publish release
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Update EOL date Open
loopbackio/loopback-governance#45 · 1 assignee ·
-
openjsf
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
openjsf
Difficulty 5/5 Over a week Newbie friendliness 25/100
loopbackio/loopback-governance#35 · 2 comments ·
All issues in loopbackio/loopback-governance
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
bug ci-failure high priority
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vllm-project/vllm-omni#7972 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
amponce/archive-movie-browser#166 ·