Community: Changing affiliation needs to be documented

[castrojo]

It's unclear what we should do when someone changes affiliation. There's sigs.yaml but it's not just about updating it, people need to run make, etc.

We should probably have document these bits as devstats for the person needs to be updated as well. This feel like an area where we should be consistent across the CNCF.

/cc @idvoretskyi
/sig contributor-experience
/area contributor-guide

[idvoretskyi]

+1, I agree.

We have a few samples of outdated info about the company affiliation.

[cblecker]

Should we also open up an issue against devstats?

[idvoretskyi]

@cblecker Yes, please, just a reference is enough.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[castrojo]

/remove-lifecycle stale

[castrojo]

/help

[k8s-ci-robot]

@castrojo:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[castrojo]

Ok so it's not hard to change the CNCF affiliation, I blogged about it here: https://blog.jorgecastro.org/2018/01/29/updating-your-cncf-developer-affiliation/

We just need to take that and generalize it somewhere.

[guineveresaenger]

@castrojo the above blog entry is a bit unclear on the exact steps you took to change your affiliation.
If you can give a bit more detail, we can make this a good first issue.
It should probably be linked to in https://github.com/kubernetes/community/tree/master/contributors/guide#sign-the-cla
and documented here:
https://github.com/kubernetes/community/blob/master/CLA.md

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[parispittman]

/remove-lifecycle stale

i don't think this has been addressed. if it has, we can close.

[guineveresaenger]

haha I'm going through this literally right now. will try to follow up!