Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Corporate contrib stats: CLA signature logs needed from CNCF #1972

Closed
ryanj opened this issue Nov 2, 2016 · 8 comments
Closed

Corporate contrib stats: CLA signature logs needed from CNCF #1972

ryanj opened this issue Nov 2, 2016 · 8 comments
Labels
kind/velocity-improvement lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@ryanj
Copy link

ryanj commented Nov 2, 2016

In order to quantify the amount of impact that various corporate groups are making, we need an effective way to establish and maintain a map of corporate affiliations per each individual contributor.

The CLA signing process is an excellent forcing function that will help ensure that this mapping is accurate and up-to-date.

CNCF should provide logs with the following information to help make these calculations independently verifiable by different corporate groups:

  1. cla_signature_timestamp
  2. github_id
  3. corporate_affiliation (or "individual contributor" for CLA signatures without any corporate affiliation)

The CLA signature timestamp is needed to keep track of changes in corporate affiliations over time.

@ryanj
Copy link
Author

ryanj commented Nov 2, 2016

FYI @foxish

@foxish
Copy link
Contributor

foxish commented Nov 2, 2016

cc @caniszczyk @emsearcy

@foxish
Copy link
Contributor

foxish commented Nov 2, 2016

cc @kubernetes/contributor-experience

@apelisse
Copy link
Contributor

apelisse commented Nov 2, 2016

Should the data be public though?

@ryanj
Copy link
Author

ryanj commented Nov 18, 2016

@apelisse good question.
I think public disclosures and transparency around corporate involvement will be needed in order to ensure that the community can reliably answer questions of "which corporations are involved?" and "what are they involved in? / what are they doing?".

Details that are not required include: email addresses or real names of individual contributors.

@fejta-bot
Copy link

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 17, 2018
@bgrant0607
Copy link
Contributor

Handled by https://github.com/cncf/gitdm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/velocity-improvement lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants