Add stub template for App Runtime Platform WG #142
Conversation
TODO before merge: * Identify leads for WG * Identify initial goals and scope for WG * List main technical assets for WG
|
I would love to see https://github.com/cloudfoundry-incubator/haproxy-boshrelease promoted to the I believe it is the only "Technical Asset" in the list that is still under incubation. At ~600 commits and numerous production deployments, it seems ready to hatch 🐣. |
|
@Gerg SGTM! The TOC has been discussing merging the entire cloudfoundry-incubator org into the cloudfoundry org, likely after a long-overdue round of repo pruning/archival. |
|
FYI @aminjam @Benjamintf1 @ameowlia @gcapizzi @geofffranks @domdom82 for feedback and suggestions for approvers/leads. |
|
@emalm I agree. I think we have a list of things to do besides clicking the "transfer repository" button. I volunteer for taking ownership since @geofffranks phased out of the project quite some time ago. I might need to have the rights to create a repo under the cloudfoundry org, though. |
|
@ameowlia I added some initial goals and scope to this WG's draft charter and proposed you as a lead in the group. Could you please provide feedback on them and work with the TOC to establish a good initial charter for this WG? Thanks! |
Co-authored-by: Amelia Downs <adowns@vmware.com>
|
I'm not sure how many approvers we are expecting in each area. I'm happy to take a "more is more" approach and start with high trust. Suggested Approvers (if not Tech Leads 👀 ) (just from the top of my head, happy to add more): |
* Add WG areas and candidate approvers * Consolidate technical assets under areas * Revise goals and non-goals Co-authored-by: Amelia Downs <adowns@vmware.com>
|
I'd also like to nominate Ivan Hristov ( @IvanHristov98 ) from SAP as an approver for the Diego repos. He has accepted this nomination. |
|
@ameowlia I've updated the PR draft with those additional approver candidates. Please let me know whether you think the charter draft is ready for the TOC to review officially or whether there should be any more changes before that! |
Reserve Eirini assets for a soon-to-be-proposed working group dedicated to CF on K8s.
emalm
force-pushed
the
wg-app-runtime-platform
branch
from
748e635
to
b3624d2
Compare
|
@loewenstein Good point, I was waffling on whether to include K8s infrastructure in the goals as a longer-term view, but I think it's better to remove it for now. Then there's no update needed if the new CF on K8s WG ends up being long-lived, and if we do end up merging areas from it into the other App Runtime WGs then that should prompt a change to goals and scope anyway. |
|
For the record, I approve this PR as worded, but I'm the requester so I can't be a reviewer myself. |
This PR proposes a charter document for the App Runtime Platform working group.