See:
What is the minimal outcome you would like to see from this initiative to be satisfied?
dailyips.db
What are your nice or really nice to have wishes?
countme-week####.db
totals.db
Fedora, EPEL, CentOS Stream
Do this initiative have any dependencies?
Skills needed?
Person who must or should be involved?
Other work that should be completed prior to this initiative?
Is this initiative under a time-constraint? Should it start or end before a certain date?
Note: I've made some edits to the original post for clarity.
Issue tagged with: Accepted
@smooge is adding himself to be reminded when this gets dealt with.
This initiative has now been scheduled for an investigation spike and is estimated to begin on April 20th 2022. The investigation team will look at possible technical solutions to deliver this project to the success criteria specified in the ticket and recommend a particular course of action. Once a technical solution has been proposed, the ticket will be marked as Ready and picked up as the next project to be actioned.
Cool. It's probably useful for me to have a high-bandwidth meeting with the investigation team, because I have thoughts. :)
Update: as I understand it, the team has addressed definition of success item 1 (the disk space issue) but not by refactoring as outlined https://pagure.io/mirrors-countme/issue/56. (As noted, that's okay — I really only care about the result. But I do think what I suggest has some ongoing benefits.)
1
The rest:
is still pending. Correct?
That is correct. We plan to action this work once communishift wraps up, pending no other higher priority work request being submitted.
On Fri, Aug 5, 2022 at 2:38 PM Matthew Miller pagure@pagure.io wrote:
mattdm added a new comment to an issue you are following: ` Update: as I understand it, the team has addressed definition of success item1` (the disk space issue) but not by refactoring as outlined https://pagure.io/mirrors-countme/issue/56. (As noted, that's okay =E2=80= =94 I really only care about the result. But I do think what I suggest has some ongoing benefits.) The rest: Not dependent on Smooge, because the current setup is not fair to hi= m. Data for IP/day (without actual IPs, mind you!) alongside countme data in "long" form IP/day scripts don't need annual and per-release (or even more frequent!) maintenance is still pending. Correct? `` To reply, visit the link below or just reply to this email https://pagure.io/cpe/initiatives-proposal/issue/17
mattdm added a new comment to an issue you are following: ` Update: as I understand it, the team has addressed definition of success item1` (the disk space issue) but not by refactoring as outlined https://pagure.io/mirrors-countme/issue/56. (As noted, that's okay =E2=80= =94 I really only care about the result. But I do think what I suggest has some ongoing benefits.)
` Update: as I understand it, the team has addressed definition of success item
``
To reply, visit the link below or just reply to this email https://pagure.io/cpe/initiatives-proposal/issue/17
--=20
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA https://www.redhat.com
Communications House
Cork Road
Waterford https://www.redhat.com
BTW: relevant background reading https://tidyr.tidyverse.org/articles/tidy-data.html
An ARC (advance recon crew - small team who pre-scopes work for a request before a dev team takes it on) investigation has been done for this request https://fedora-arc.readthedocs.io/en/latest/mirrors-countme/index.html
Its ready to be scheduled and currently 'next' for CPE team to take on. Current estimated start date is Monday April 3rd 2023.
This project is now in flight and tracked here https://github.com/orgs/fedora-infra/projects/16/views/1
Est completion date is end of June 2023.
Metadata Update from @amoloney: - Issue tagged with: In Progress, On Track
Metadata Update from @amoloney: - Issue set to the milestone: Fedora Infra Enhancements
Log in to comment on this ticket.