This came up during the past FAD, during FLOCK and in meetings that we need to work together with other open source projects, share resources and learn together. Being involved with newly formed CHAOSS project could be a way forward in this direction. The project aims to:
Establish standard implementation-agnostic metrics for measuring community activity, contributions, and health, which are objective and repeatable.
Produce integrated open source software for analyzing software community development.
More info: https://chaoss.community/
@bee2502 will talk to Emma from Mozilla about this in April
To clarify, is this ticket focusing only on CHAOSS or is it suggesting all five possible ideas? If the latter, it might be easier to file each idea as its own ticket so we can keep relevant discussions together.
@jflory7 I was working on the description! Hope it's clear now.
Metadata Update from @bee2502: - Issue tagged with: blocked, internal operations
@bee2502 I would like to help you with this and get involved. Do we have any update until now?
I talked to Emma Irwin from Mozilla but she said there is no clear pathway for orgs to join CHAOSS yet. She suggested we attend the calls and subscribe to mailing list - but to me that feels like pathway for individual contributor than an org. Maybe someone can communicate with RH team involved with CHAOSS - about how Fedora can join too?
@jonatoni I would love to join forces.
Metadata Update from @bee2502: - Issue untagged with: blocked
I believe @spot is leading the RH involvement in CHAOSS
Metadata Update from @jflory7: - Issue priority set to: no deadline (was: awaiting triage) - Issue set to the milestone: Future releases
Metadata Update from @jflory7: - Issue priority set to: waiting on assignee (was: awaiting triage)
I discussed this with @spot and he suggested that we define specific tasks for what we need from CHAOSS and how we want to get involved. Since we have a lot of ongoing tasks right now as compared to team bandwidth, I suggest we revisit this topic in future.
Metadata Update from @bee2502: - Issue tagged with: difficulty - hard, needs info, new change, type - outreach
+1, let's close it for now and revisit it later.
Metadata Update from @jflory7: - Issue set to the milestone: None (was: Future releases)
Metadata Update from @jonatoni: - Issue close_status updated to: not possible - Issue status updated to: Closed (was: Open)
Clossed it as not possible for now - we can reopen it in the future.
Login to comment on this ticket.