mirror of https://github.com/knative/docs.git
33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
# Elafros Project Checklist
|
|
|
|
The purpose of this checklist is to outline must-have items required to open the Elafros GitHub repositories to the public.
|
|
|
|
## Blockers to making project public
|
|
|
|
The tasks we would like to complete prior to making repository public, are:
|
|
|
|
- [x] Migrate code to github.com/elafros organization
|
|
- [x] Migrate project roles document to the CONTRIBUTING.md
|
|
- [ ] Review project roles & governance changes
|
|
- [x] Elafros design/API documents posted to repo and reviewed
|
|
- [x] Implement Service CRD in the compute/serving repo
|
|
- [ ] Seed initial project roadmap docs (e.g. API, Build, Autoscaling, Eventing)
|
|
- [ ] Validated no-build deployment ([Elafros Easy](https://github.com/elafros/install)) for GKE and non-GKE k8s cluster
|
|
- [ ] Validate all sample apps against elafros/install deployed cluster
|
|
- [ ] Operator/Developer upgrade user guide (fully manual ok for now)
|
|
|
|
|
|
|
|
## After project is public
|
|
|
|
Additional items, that while still important can be completed after opening the repository, are:
|
|
|
|
- [ ] Configure @elafros Twitter account profile
|
|
- [ ] Set up long-term billing for Slack, Github, etc.
|
|
- [ ] Configure social Stack Overflow label(s)
|
|
- [ ] Clean up GitHub landing page (pin repos, update description & links, seed community)
|
|
- [ ] Team Drive and mailing lists created
|
|
- [ ] Finalize logo design and apply it in Slack/GitHub
|
|
- [ ] Migrate to public prow
|
|
- [ ] Potentially rename elafros/elafros to elafros/serving or elafros/compute
|