Re: sway SIG
On 3/18/19 11:12 AM, Timothée Floure wrote: > Hello, > > I'm interested as well! > >> As a side note, a taiga board was noted in the sway bug discussion; >> as I have recently found out, the Fedora one is invite only – is there >> anyone with access to invite others, if there is interest? > > There is an ongoing effort to make taiga a first-class citizen in Fedora's > workflow but I don't know its current state. Last time I heard [0] about it > was > in late January. > The taiga setup is being run and managed by their developers as a service for fedora. This is letting the infra team concentrate on infra tasks instead of managing yet-another service. It also lets us help fund the development and upkeep of another open source project which is a nice bonus. We have things working, but the intent is to soft-launch the service with the Fedora Council and a few small groups to sort out what we'd like the flow to look like, and for us to validate the examples and documentation. Once we've had a chance to do this, we'll open it up to everyone. I know folks are eager to use the new setup but we want to make sure it's done right. Sorry for the inconvenience and we hope to have you using it soon. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Faster composes by eliminating deltarpms and using zchunked rpms instead
On 11/16/18 3:00 PM, Adam Williamson wrote: > On Fri, 2018-11-16 at 22:07 +, Jonathan Dieter wrote: >> For reference, this is in reply to Paul's email about lifecycle >> objectives, specifically focusing on problem statement #1[1]. >> >> >> Have rpm use zchunk as its compression format, removing the need for >> deltarpms, and thus reducing compose time. > > > > you had me at "reducing compose time" > +1. Reducing compose time is at the top of several of my lists. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora Infrastructure manager change
Hello Fedora developers, I know some of you may not be familiar with me[1] unless you’re also working with CentOS or EPEL, but I’d like to take this opportunity to introduce myself a bit more formally on the list. As of 1 February, I’ll be the reporting manager for the Fedora Infrastructure Administration team, and the Fedora Infrastructure Applications team[2], as well as the CentOS engineering team internal to Red Hat. For the most part, this is a Red Hat internal organizational change that doesn’t really impact anything in the community. Paul Frields set a good example of being transparent with the community, and I want to continue that with this transition. Paul won’t be going too far as part of this transition, as he’s taking a promotion of his own, and I’ll be reporting to him as part of the new structure. This is a fantastic group of people, and I’m excited to be working with them. There will be a bit of transition time as Paul and I work through the team organization and update the wiki to reflect the changes, but you’ll probably be seeing a bit more of me around here. You may now return to your regularly scheduled mailing list. 1. https://fedoraproject.org/wiki/User:Jperrin 2. https://fedoraproject.org/wiki/Fedora_Engineering ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Ending development of Hubs
Earlier in the year, the Fedora Infrastructure team had a hackathon. Among other work during the event, we made adjustments to app development and ownership to keep the team working efficiently. For example, we retired the separate Jenkins instance in Fedora infrastructure since it’s redundant. We also decided, after discussion around the team and with the FPL, to cease active development of Hubs. This was a difficult decision but allows the team to put more effort and resources into supporting our core applications. The code for Hubs will continue to live here and of course it remains 100% free and open source: https://pagure.io/fedora-hubs I realized we did not publicly state the end of the development for Hubs, so I’m correcting that oversight with this announcement. I’m proud of the work the team has done on Hubs over the years while trying to balance multiple priorities. However, with limited time and resources, it’s more important that the Infrastructure team focus on core tasks that support the Fedora community such as development, automation and testing. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CX2JLGNRMZICEZ7D5T6OW4VKDVPLSXKO/
