This is a followup to https://git.centos.org/centos/board/issue/79
Can a script/tool be generated to record existing and historical SIG membership per SIG in some sort of public git repo? Ideally the output would be some sort of human readable and machine readable output tracking membership, roles, and dates.
The "big picture" goal is to ensure folks who "joined a SIG, got elected chair, returned to a standard member, and moved on to another project" are able to inform current/future employers of their work in our community and we can provide a clear attestation that of their roles within the groups.
In part we don't want historical folks to lose credit for their work when they move on, and in part we want them to be able to show their current employers that the work they are currently doing in CentOS is valued.
This will need to be also GDPR compliant so will need to be tied into any scripts for searching/scrubbing such data.
Pending board approval.
Metadata Update from @zlopez: - Issue priority set to: Waiting on External (was: Needs Review) - Issue tagged with: feature-request, need-more-info
+1 from me
+1 as long as the member agrees (with the possibility to change opinion).
+1
+1 and I like the idea that someone can request to be removed in the future
[backlog refinement] We have three solutions:
Simple - Daily fasjson checked in to git repo that can be reviewed over time. Possibly used as a stop gap if the complex solution is required.
Complex - Integrate fasjson with either Fedora Badges/CentOS Badges (doesn't exist) that gives the ability to show levels of membership and timeframes.
Very complex - Standup new application, which reads fasjson membership and interprets it to a set of web pages, which show information.
Solutions 2 and 3 require significant work from CPE and will require tickets within cpe initiative tracker. And also we need to look for maintainer of the new solution.
All solutions are subject of priority and capacity of the CPE Team.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Waiting on External)
I assume tracking this in noggin itself isn't possible, correct? (otherwise, I guess it would have been proposal #4)
The Board feels that #1 is the best option to get this implemented with revisiting #2 down the road
[backlog refinement] We currently don't have time to work on this, but at least here is more detailed solution for #1:
The simple solution could be done by creating a toddler for syncing the fasjson information with git repository hosted on git.centos.org.
How do we deal with GDPR issues? You will need to regularly scrub the git repository when accounts want to be completely deleted.
During our backlog refinement session for CentOS Infra, we discussed this ticket and unfortunately due to capacity restraints in the CPE team, we would not be able to work on this request. SIGs can however manage and maintain their membership independently on the CentOS Wiki page and this would serve as a way to track and view historical membership.
Closing this ticket.
Thanks! Aoife
Metadata Update from @zlopez: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.