Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Point of contact for onboarding #400

Closed
tobie opened this issue Nov 6, 2019 · 5 comments · Fixed by #422
Closed

Point of contact for onboarding #400

tobie opened this issue Nov 6, 2019 · 5 comments · Fixed by #422
Labels
onboarding tracking onboarding for new/incubating projects

Comments

@tobie
Copy link
Contributor

tobie commented Nov 6, 2019

While there is a clear point of contact during onboarding (the project champion and a single mailing list address), it's not super clear who to contact during incubation to help answer project-specific questions or how to do so.

I've cc'ed @brianwarner on a number of issues here and on various AMP repositories, but that feels brittle; I'm not sure Brian's always the right person, and if he received those GH notifications, and thus whether or not someone is actually working on those.

I also have specific issues that I need the CPC to answer (e.g. ampproject/wg-foundation-onboarding#2), and I'm not sure how to go about that either.

It would be helpful to have a better idea of how to proceed here. Maybe a dedicated incubation GH team we could assign issues to? Maybe an incubation champion?

Maybe a lot of this is already organized and I'm just not aware of it.

@brianwarner
Copy link
Contributor

Assigning (as opposed to cc'ing) is a good way to ensure I see it. It also allows me to reassign if I'm not the right person.

@tobie
Copy link
Contributor Author

tobie commented Nov 6, 2019

Right, but that requires:

  • The applicant to be a member of this org and have triage permission for this repository (or the incubation one) and each repository in the Applicant's own org in which you might be susceptible to be assigned an issue.
  • You to be a member of each org that's in incubation and have triage permission on each repository where you're susceptible to have an issue assigned.
  • Any of your colleagues susceptible to have an issue re-assigned to them be a member of each incubation org and have read permission on each repository in which they're susceptible to have an issue re-assigned to them by you.

That's certainly doable, but it would be good to have it written down so it can be organized all at once.

@tobie tobie changed the title Point of contact during incubation Point of contact for onboarding Nov 6, 2019
@tobie tobie added onboarding tracking onboarding for new/incubating projects cross-project-council-agenda labels Nov 7, 2019
@joesepi
Copy link
Member

joesepi commented Dec 3, 2019

Champion remains point of contact through incubation. Documentation needs to be updated to make that clear.

@mikesamuel
Copy link
Contributor

As discussed, I will send out a doc update PR.

(I don't have perms to assign to myself yet.)

@mikesamuel
Copy link
Contributor

IIUC, I should update PROJECT_PROGRESSION and maybe link reference to "champion" in STAGING_PROCESS to the requirements that they be able to push things before the council.

mikesamuel added a commit to mikesamuel/cross-project-council that referenced this issue Dec 13, 2019
Fixes openjs-foundation#400 per @joesepi's summary of consensus

> Champion remains point of contact through incubation. Documentation
> needs to be updated to make that clear.
joesepi pushed a commit that referenced this issue Jan 9, 2020
* Clarify that champion duties extend through incubation.

Fixes #400 per @joesepi's summary of consensus

> Champion remains point of contact through incubation. Documentation
> needs to be updated to make that clear.

* Update PROJECT_PROGRESSION.md

Co-Authored-By: Antón Molleda <molant@users.noreply.github.com>

* Properly capitalize "GitHub"

Co-Authored-By: Antón Molleda <molant@users.noreply.github.com>

* Update PROJECT_PROGRESSION.md

Co-Authored-By: Tobie Langel <tobie@unlockopen.com>

Co-authored-by: Antón Molleda <molant@users.noreply.github.com>
Co-authored-by: Tobie Langel <tobie@unlockopen.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
onboarding tracking onboarding for new/incubating projects
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants