Fedora Badges - Long Term Maintenance Discussion
Hey folks, Fedora Badges[0] is one of the most loved projects in our community but it’s in a bad state right now. There are multiple problems with it ranging from outdated compatibility with our authentication system and messaging bus, to it using a not-so-friendly framework for community members (Pyramid). All of these combined make it a tricky application to approach and fix. The Community Platform Engineering team have been discussing in recent weeks what would be the best solution to fix badges, whether a rewrite of the application would be best or whether a refactoring is the way to go. The problem though is that unfortunately Fedora Badges doesn’t fit exactly into the CPE team mission[1], but we do understand its importance in the Fedora community. We felt that the best course of action to make Badges better for everyone is to try to make space for a project ‘team’ of sorts that is made up of folks from the CPE team and Fedora community volunteers who would work on developing a solution for the Badges service together, from ideation to delivery. But first we need to assemble the Avengers Team and some terms and a proposal of who will take on what work needs to be agreed on. While the Badges application is not within the CPE teams remit to maintain, the CPE team would like to offer to: - Collaborate with the community maintainers to investigate the best course of action to make the Badges service more stable and maintainable - Pair with the community maintainers to assist them in rewriting the application - Assist them while integrating the newer service/version with the rest of the Fedora projects apps. - Provide power and ping to the service - Help with writing good documentation for troubleshooting and a standard operating procedure for the service to make sure its easier for people to understand how it works and contribute to in the future On the community maintainer(s) side, we would like them to: - Contribute to the writing of the new app - Keeping up to date with Fedora’s application integration - Updating/resolving CVEs and dependencies change - Responding to issues/PRs opened by community members. So before our team can move ahead, we would like to reach out to the Fedora community to ask for a maintainer(s) for the Badges application who will be able to work (part time is fine) with the CPE team in developing a better Badges for all! If you are interested in working with us to improve the Badges application and become its maintainer, please respond to this Discussion thread[2] (this discussion remains open until mid September). [0] https://badges.fedoraproject.org/ [1] https://docs.fedoraproject.org/en-US/cpe/#_our_responsibilities [2] https://discussion.fedoraproject.org/t/fedora-badges-long-term-maintenance-discussion/41109 Cheers, Ant -- Ant Carroll Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City X91 NY33 ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
CPE Feedback Survey Q3-Q4 2021
Hey folks, We have been doing the Community Platform Engineering feedback survey for a while now, and we still use the feedback collected to adjust our communications and processes. We would like to hear your thoughts again through a short survey we've put together to learn how your experiences have been with us since July 2021. If you could take the time (5mins max) to complete it, it would be hugely valuable as we work on this continuous improvement - https://fedoraproject.limequery.com/6 The survey will remain open until Feb 07th (23:59 UTC). Know more about the team at: https://docs.fedoraproject.org/en-US/cpe/ Cheers, Ant -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Upcoming changes on datanomer/datagrepper
Hey folks, One of the initiatives the CPE team has taken over this quarter is updating and improving the performances of datagrepper/datanomer. That work is based upon the investigation done earlier in the year whose results can be found at: https://fedora-arc.readthedocs.io/en/latest/datanommer_datagrepper/index.html One important item to note is that we will introduce a default value for the `delta` argument. Currently, if you do not specify one, datagrepper will not limit its queries by time, which is very resource intensive and often so much so that you do not get any results back. By setting a default `delta` argument we can ensure that just browsing the UI does not throw random time-out errors and increase the performance of some of the queries. However, this is a **non-backward compatible change**! If you have scripts relying on the fact that the messages returned can be of any date, they will break once the default delta is in place. You should thus adjust them to specify a delta (which will override the default one). The default delta will likely be set to "one day" but that's not fixed yet. Once it has been fully confirmed we'll update again, so please treat this as an FYI, but also start looking at your scripts. Specifying the `delta` today won't break the current behavior and will ensure they keep working once the change has landed. Secondly, the grouped feature [2] will be dropped as it's not supported in the new library. If you're using it, please reach out to us so we can figure out mitigation plans. Enjoy Nest if you're attending and have a nice weekend! Cheers, Ant [1] https://fedora-arc.readthedocs.io/en/latest/datanommer_datagrepper/index.html [2] See the section "Formatting arguments" at: https://apps.fedoraproject.org/datagrepper/reference -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Upcoming changes on datanomer/datagrepper
Hey folks, One of the initiatives the CPE team has taken over this quarter is updating and improving the performances of datagrepper/datanomer. That work is based upon the investigation done earlier in the year whose results can be found at: https://fedora-arc.readthedocs.io/en/latest/datanommer_datagrepper/index.html One important item to note is that we will introduce a default value for the `delta` argument. Currently, if you do not specify one, datagrepper will not limit its queries by time, which is very resource intensive and often so much so that you do not get any results back. By setting a default `delta` argument we can ensure that just browsing the UI does not throw random time-out errors and increase the performance of some of the queries. However, this is a **non-backward compatible change**! If you have scripts relying on the fact that the messages returned can be of any date, they will break once the default delta is in place. You should thus adjust them to specify a delta (which will override the default one). The default delta will likely be set to "one day" but that's not fixed yet. Once it has been fully confirmed we'll update again, so please treat this as an FYI, but also start looking at your scripts. Specifying the `delta` today won't break the current behavior and will ensure they keep working once the change has landed. Secondly, the grouped feature [2] will be dropped as it's not supported in the new library. If you're using it, please reach out to us so we can figure out mitigation plans. Enjoy Nest if you're attending and have a nice weekend! Cheers, Ant [1] https://fedora-arc.readthedocs.io/en/latest/datanommer_datagrepper/index.html [2] See the section "Formatting arguments" at: https://apps.fedoraproject.org/datagrepper/reference -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
CPE Feedback Survey
Hey folks, Over the last several months we’ve been trying to continue our improvements with how we interact and share information with you all based on the feedback of the last surveys. From the blog posts, to mails and how we work on the tickets you send us. Here is a link to our very short survey where you can give us that feedback: https://fedoraproject.limequery.com/5 If you could take the time (5mins max) to complete it for us it would be massively appreciated as always. We're also moving the cadence of this to once every 6 months. The shorter survey times at the start were great to give us that initial burst of improvements to work on, and the increases in happiness we've seen from you reflect the work the team has done. Hope to see some of you at Nest, Ant -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
New Fedora Account System Production Deployment - What this means for you
Background For the last 12 + months, the Community Platform Engineering team have been developing a new service to replace the current FAS2 application for the Fedora Account System. The FAS2 application was written over 10 years ago with python2 and TurboGears1 framework. Due to its dependencies, it is tied to a RHEL6 deployment and could not be moved to a newer OS without rewriting. Finally FAS2 has a very small deployment base and we had to maintain it all. The new account system is based on the widely used IPA product. We have created a community portal frontend for managing account details (noggin). This means we only need to maintain the frontend and can leave the high security parts to IPA. Additionally, noggin may be used by many more community products. Key Dates - Subject to Change* Tuesday 23rd March: Data sync to IPA Wednesday 24th & Thursday 25th March: System-Wide Outage for machine config to Noggin 25th March: Final Run-Through of Production Rollout 26th March: Production Rollout Complete 29th March March onwards: Support for post deployment issues We do not anticipate these dates to change, however our team will meet for a final review of work on Tuesday 23rd March and once satisfied all rollback paths are in place and risks have been mitigated, we intend to deploy to production against the dates listed above. Please keep an eye on this mail for any potential last minute updates What This Means for You Everyone If you have an otp token enrolled it will be needed everywhere. This will include logging in through ipsilon or getting a kerberos ticket(kinit) which was not previously the case. Outages and interruptions to services during migration dates System Administrators All system administrators will need to enroll a new otp token with noggin Sudo command will ask for First factor and Second factor separately which is a slight change from the previous password+otp prompt Packagers & Package Maintainers Any packager that has otp enabled will have to follow new process in docs for kinit/pkinit ‘Drive-By’ Contributors If you are a ‘drive-by’ or more casual contributor to the Fedora project, you may have to reset your password. We anticipate the number of people who will need to do this is low, depending on when you last logged in. Please re-sign into your Fedora account post migration date. Post Deployment Support If you experience issues with your workflow as a result of FAS changing please log an issue on the fedora infra tracker https://pagure.io/fedora-infrastructure/issues. FAS will be left in a read-only state to support any applications that you might not be in a position to migrate immediately. However, we don’t recommend using it as the data it contains will quickly become out of date. Maintainer-test instances will be left in a “frozen” state which means any user changes such as new users or new ssh keys will not be reflected on these machines. Further Information Outage ticket link: https://pagure.io/fedora-infrastructure/issue/9747 Community blog post: https://communityblog.fedoraproject.org/introducing-the-new-fedora-accounts/ Noggin Documentation: https://noggin-aaa.readthedocs.io/en/latest/userguide.html#user-accounts -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs redhatjobs @redhatjobs ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
New Fedora Account System Production Deployment - What this means for you
Background For the last 12 + months, the Community Platform Engineering team have been developing a new service to replace the current FAS2 application for the Fedora Account System. The FAS2 application was written over 10 years ago with python2 and TurboGears1 framework. Due to its dependencies, it is tied to a RHEL6 deployment and could not be moved to a newer OS without rewriting. Finally FAS2 has a very small deployment base and we had to maintain it all. The new account system is based on the widely used IPA product. We have created a community portal frontend for managing account details (noggin). This means we only need to maintain the frontend and can leave the high security parts to IPA. Additionally, noggin may be used by many more community products. Key Dates - Subject to Change* Tuesday 23rd March: Data sync to IPA Wednesday 24th & Thursday 25th March: System-Wide Outage for machine config to Noggin 25th March: Final Run-Through of Production Rollout 26th March: Production Rollout Complete 29th March March onwards: Support for post deployment issues We do not anticipate these dates to change, however our team will meet for a final review of work on Tuesday 23rd March and once satisfied all rollback paths are in place and risks have been mitigated, we intend to deploy to production against the dates listed above. Please keep an eye on this mail for any potential last minute updates What This Means for You Everyone If you have an otp token enrolled it will be needed everywhere. This will include logging in through ipsilon or getting a kerberos ticket(kinit) which was not previously the case. Outages and interruptions to services during migration dates System Administrators All system administrators will need to enroll a new otp token with noggin Sudo command will ask for First factor and Second factor separately which is a slight change from the previous password+otp prompt Packagers & Package Maintainers Any packager that has otp enabled will have to follow new process in docs for kinit/pkinit ‘Drive-By’ Contributors If you are a ‘drive-by’ or more casual contributor to the Fedora project, you may have to reset your password. We anticipate the number of people who will need to do this is low, depending on when you last logged in. Please re-sign into your Fedora account post migration date. Post Deployment Support If you experience issues with your workflow as a result of FAS changing please log an issue on the fedora infra tracker https://pagure.io/fedora-infrastructure/issues. FAS will be left in a read-only state to support any applications that you might not be in a position to migrate immediately. However, we don’t recommend using it as the data it contains will quickly become out of date. Maintainer-test instances will be left in a “frozen” state which means any user changes such as new users or new ssh keys will not be reflected on these machines. Further Information Outage ticket link: https://pagure.io/fedora-infrastructure/issue/9747 Community blog post: https://communityblog.fedoraproject.org/introducing-the-new-fedora-accounts/ Noggin Documentation: https://noggin-aaa.readthedocs.io/en/latest/userguide.html#user-accounts -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs redhatjobs @redhatjobs ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
CPE Feedback Survey
Hey folks, Apologies for the delay in getting this out to you after the start of the year. Hopefully you've noticed the changes to communication since the results of the last survey we did in August. However, we know this is ever changing, people join or become inactive and so want to ensure we continue with making improvements that benefit us all. I'm here asking for your help with this again [image: ] Here is a link to a very short survey we've put together to learn how your experiences have been with the CPE team since October 2020. If you could take the time (5mins max) to complete it for us it would be hugely valuable as we work on this continuous improvement - https://fedoraproject.limequery.com/4?lang=en The survey will remain open until Feb 17th (23:59 UTC). Cheers, Ant -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
CPE Quarterly Feedback Survey Results
Hey folks, I want to thank everyone that took the time to complete the survey for us. Even more so for those of you that left comments to help give us extra info and context, this is invaluable. The flip side is, it takes a little time to work through and that's what we're doing right now. A few pieces we can acknowledge off the bat though: - Mediums of communication were overwhelmingly positive for weekly email lists and blog posts. 76% for the emails and 46% for blog posts respectively We're discussing how to improve these even further at the moment as well as tweak the PO office hours and wind down the Taiga boards as these were significantly less popular. 14% for the PO office hours and 1% for the Taiga boards. - Transparency of decisions and communications. You want more of the former and streamlining on the latter. We hear you and will aim to deliver this alongside the first point above. - Overall (82%+ reponses) you feel we did a good job since April of this year. We appreciate the level of confidence you've shown in us and our desire is to continuously improve this with your feedback. Cheers, Ant -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: CPE Feedback Survey
Hey all, First of all, thanks to everyone that has taken the time to complete the survey for us already. It will remain open until the end of August, so if you haven't had the chance to fill it in yet, we'd really appreciate you taking the few minutes to do so before it closes. Thanks again, Ant On Thu, Aug 6, 2020 at 6:23 PM Ant Carroll wrote: > Hey folks, > > CPE <https://docs.fedoraproject.org/en-US/cpe/>need your help :) > > Over the last several months we've been trying to improve how we interact > and share information with you all. From the blog posts, to mails and how > we work on the tickets you send us. > > Here is a link to a very short survey we've put together to learn how we > can give you the best experience possible going forward by understanding > the experiences you've had recently. > If you could take the time (5mins max) to complete it for us it would be > hugely valuable as we work on this continuous improvement - > https://fedoraproject.limequery.com/696793?lang=en > <https://meet.google.com/linkredirect?authuser=0=https%3A%2F%2Ffedoraproject.limequery.com%2F696793%3Flang%3Den> > > > Cheers, > > Ant > -- > > Ant Carroll > > Associate Manager, CPE Team > > Red Hat Waterford <http://www.redhat.com> > > Communications House > > Cork Road, Waterford City > > ancar...@redhat.com > M: +353876213163 IM: ancarrol > @redhatjobs <https://twitter.com/redhatjobs> redhatjobs > <https://www.facebook.com/redhatjobs> @redhatjobs > <https://instagram.com/redhatjobs> > <https://www.redhat.com/> > -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
CPE Feedback Survey
CPE <https://docs.fedoraproject.org/en-US/cpe/>need your help :) Over the last several months we've been trying to improve how we interact and share information with you all. From the blog posts, to mails and how we work on the tickets you send us. Here is a link to a very short survey we've put together to learn how we can give you the best experience possible going forward by understanding the experiences you've had recently. If you could take the time (5mins max) to complete it for us it would be hugely valuable as we work on this continuous improvement - https://fedoraproject.limequery.com/696793?lang=en <https://meet.google.com/linkredirect?authuser=0=https%3A%2F%2Ffedoraproject.limequery.com%2F696793%3Flang%3Den> Cheers, Ant -- Ant Carroll Associate Manager, Software Engineering Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancar...@redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
