search

carbon-language / carbon-lang

Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
http://docs.carbon-lang.dev/
Other
32.33k stars 1.48k forks source link

Define and document success at gaining "broad industry interest and participation". #1361

Open chandlerc opened 2 years ago

chandlerc commented 2 years ago

In #1315 (the original go-public proposal), @camio correctly suggested that we need to document the metrics that will track our broad engagament.

To expand on that a bit, I think we need to define and document:

Filing this issue to track resolving this.

@camio also suggested some starting points here:

I think it is important to document which metrics are intended to be used to measure "broad industry interest and participation" because that is the stated intent of this proposal. It obviously cannot be perfect, but I think we should be analytical rather than go based on feelings.

Something we can use as a baseline is C++ standardization. PL22.16 currently has 52 different entities in participation. WG21 has maybe a half dozen countries represented. Given that I would say "broad industry interest" would be:

  • 25 different entities who have signed up to participate
  • A weekly meeting with 15 entities represented on a regular basis

This measures just interest. Participation involves proposal development, proposal feedback, and development work. WG21 can help here too. In May, there were 34 papers published and 13 of them were new.

  • 5 entities publishing new papers in a given month

Development work is harder. Maybe you have better visibility into this than I do. How many different entities should be creating pull requests to the codebase every month?

_Originally posted by @camio in https://github.com/carbon-language/carbon-lang/pull/1315#discussion_r898071692_

github-actions[bot] commented 2 years ago

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive label. The long term label can also be added for issues which are expected to take time. This issue is labeled inactive because the last activity was over 90 days ago.