adopted-ember-addons / adopted-ember-addons/program-guidelines

Improve consistency of addons in this org for maintenance

Open
#28 25 comments 9 reactions 1 assignee Claimed by @MelSumner View on GitHub
proposal
Dominant language
JavaScript
Stars
4
Forks
4
PR merge metrics
No merged PRs in 30d

Description

There are a lot of times when I struggle to update or release one of these addons (in the org) because they're all using different configurations.

I'd like to propose that we adopt these standards:

- The primary branch of all repos is `main`
- All packages use `pnpm`
- All packages use `release-plan` (setup instructions here: https://github.com/mansona/create-release-plan-setup)
- ensure each repo has a consistent github ci workflow file
- ensure each repo is using `ember-try`
- use dependabot, use consistent config

For settings:

- update settings so a PR is required
- branches should be deleted after merge
- we'll add a consistent social preview image to each repo

If an addon should be archived:

- file an issue on that repo and let us know in the Discord channel

Did I forget anything?

cc @adopted-ember-addons/admin
```[tasklist]
### Tasks
- [ ] Create template maintanance project
- [ ] Update documentation for this org
- [ ] Add project to each repo in org
```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.