I propose this objective:
Create our first "CommOps Random Metrics" in CommBlog
For this, We can need to use/update/adapt our current toolbox scripts
I make many "first issues" on the code of geofp and the gsoc-stats port to python3 FedoraCommunityStats repositories.
Some cool topics for the post can be:
I attached some FAS data as an example.
Thanks in advance for help in this hack session.
<img alt="Fedora_Packagers.html" src="/fedora-commops/issue/raw/files/208cf8afea18dee8d0faf58c4ecc017f225694336609c89dc4888478e3bd7a9a-Fedora_Packagers.html" />
<img alt="Fedora_packagers.csv" src="/fedora-commops/issue/raw/files/8e17c5ec858d790f4bc288c2b3aae23998cf4c70c6cfb37eef42661535c7c4c7-Fedora_packagers.csv" />
<img alt="Fedora_Community.html" src="/fedora-commops/issue/raw/files/e7b6c542080383553986a0d20b4f59b346db2a4a14cc0f7c28a644abc80bbeee-Fedora_Community.html" />
<img alt="Fedora_Community.csv" src="/fedora-commops/issue/raw/files/111900ab13ace6e5f75b79871bd4ae905e6db570b66b2db5f25bac5e99d899f1-Fedora_Community.csv" />
etherpad from the session:
Metadata Update from @jflory7:
- Issue assigned to bt0dotninja
- Issue priority set to: next meeting (was: awaiting triage)
- Issue tagged with: team - commops, type - Flock, type - metrics
Tickets #218 and #219 were created at the Metrics hackfest as a result of our discussion. I propose we close this ticket as complete, and move new discussion to those tickets.
What do you think? Is it okay if I close as complete @bt0dotninja @bee2502 @nasirhm?
Metadata Update from @bt0dotninja:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)
to comment on this ticket.