Re: The new Change discussion process is painful
Hello team, I don't want to enter a terrain where I don't belong, but I want to express my opinion. Since I understand that you don't want to and don't like the discourse interface, please take into account community participation in discussions. And my example is going to be the controversial "Privacy-preserving Telemetry for Fedora Workstation", on ML, we have 99 comments, but in discourse we are over 500. Maybe it's bad on my part to assume that you want to actual listen to community feedback and not only to devs and packager feedback. The process is experimental and needs to be adjusted, yes; e.g: I propose to don't split discussion in different topics. I hope you don't drop the discourse, and if you do I will try to keep the pace a put the proposals into discourse to make them more visible to the community (adding that the discussion is happening in the ML). Best regards, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: F39 Change Proposal: Color Bash Prompt (System Wide)
What I did with the i3 Spin was to ask to the Design team for something that fits Fedora's color palette. I think for this you could do the same. Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: New Fedora Developer Portal release
Hi again, You should consider updating the favicon for the new logo. Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: New Fedora Developer Portal release
Hi, If the site is not available, please wait a bit. The automation kicks in > periodically (I do not remember how often though), if it is not available > by tomorrow, then I'll take a look by monday :). > It's live now! Great work! -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: New Fedora Developer Portal release
Hi, New: Julia installation page: >* > > https://developer.fedoraproject.org/tech/languages/julia/julia-installation.html > It looks like the Julia site[1] is down or not existent. Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: Do I have a @fedoraproject.org e-mail address ?
El vie., 21 de enero de 2022 11:18, Alain Vigne escribió: > Thank you, I did read this wiki page a long time ago, but was not able to > retrieve it :( > > I remembered that it should work this way, so I sent a test email to my > fedora... address, and I was expecting to get it in my gmail mailbox... > But it doesn't seem to work for me ? > Maybe an infinite loop ? > >- gmail sends to fedoraproject which forwards to gmail ? > > My test e-mail doesn't land in my gmail spam either... > > Could someone send me something at avigne AT fedoraproject org please ? > Is there something wrong with me ? > TIA > Alain > > On Fri, Jan 21, 2022 at 2:52 PM Ankur Sinha > wrote: > >> On Fri, Jan 21, 2022 14:29:07 +0100, Alain Vigne wrote: >> > Hi >> > I am a Fedora packager [1] and I thought writing to >> > my_...@fedoraproject.org >> > would redirect to my registered e-mail address... It seems not !? >> > If yes, how to enter needed information to Thunderbird client, for ex. ? >> > >> > I couldn't find documentation about this question. Thank you for your >> > explanations. >> >> It is an e-mail alias, there's no mailbox attached to it. It simply >> redirects to whatever e-mail you've specified in FAS. >> >> More information here: >> >> https://fedoraproject.org/wiki/EmailAliases >> >> -- >> Thanks, >> Regards, >> Ankur Sinha "FranciscoD" (He / Him / His) | >> https://fedoraproject.org/wiki/User:Ankursinha >> Time zone: Europe/London >> ___ >> 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 >> > > > -- > Alain V. > ___ > 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 > > > It's a little harder to make it work with Gmail, but not impossible. Take a look at https://communityblog.fedoraproject.org/using-fedora-email-alias-gmail/ There is comment I did about how to complete a step. It's related to 2FA. Hope it helps. Br, ___ 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
How do we announce new packages?
Hello people. First of all, I'm not a developer or a packager, I just try to help with the little things I know to do. One thing I try to do is to check news, forums, ML and places where people talk about Fedora. A thing I noted is that a lot of people in magazines and news sites like phoronix, hacker news and other sites follow this list to get news about the project and it started to worry me that a big part of the traffic follow orphaned and retired packages, but nothing is never revealed/published when a new package enter the repositories or nothing similar, maybe a review swap but it's not enough. Trying to market the number of packages, the amount of free and open source software that we offer, how this could be measured and published? Is that something that require to much work? Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: [CoreOS] Fedora CoreOS Community Video Meeting 2021-11-02
Would you like to have this meeting uploaded to Fedora Project's YouTube channel? Br, Eduard Lucena El mié., 3 de noviembre de 2021 18:34, Dusty Mabe escribió: > > > On 11/2/21 10:19 PM, Dusty Mabe wrote: > > Hi All, > > > > Tomorrow we will be holding a video meeting for the Fedora CoreOS > community. > > > > Colin Walters will be presenting on a new proposal for "CoreOS Layering". > > https://github.com/coreos/enhancements/pull/7 > > > > We'll also be discussing any meeting tickets and possibly revisit our > list of high level > > issues. > > > > Time: 16:30 UTC (same as normal) on Wednesday October 6th > > Location: https://meet.google.com/igd-ekxw-nzi (will be recorded) > > Agenda/Notes: https://hackmd.io/5bdC2OLjQYmB5ErZ4AzpdA > > Thanks to everyone who attended! Here is a link to the meeting recording: > > > https://dustymabe.fedorapeople.org/meetings/2021-11-03_FCOS-Community-Meeting.mp4 > ___ > 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 > ___ 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
Re: Fedora Java: The Death of Two SIGs
Hello, I'm not a Fedora Maintainer, or packager, or developer. I was involved more in marketing and more "people person"[1] stuff. I hope this can close this thread. This email has a specific goal, but it doesn't have a great title: For starters, SIG can't die, because they aren't alive. Also the goal was to announce that there aren't active members of @java-maint-sig, which is ok, sometimes stuff like that happens in a community driven project. The problem is all the unnecessary words, and unnecessary responses in it. On one side: Ok, no one is working towards the objective of the @java-maint-sig, maybe someone later will pick it up, or simply it will remain inactive, that's it. Some people are happy working more freely without a heavy well organized structure, and it looks like the Java SIG works this way. On the other side: No need to be happy about something you don't like. It's not working anymore. Some people need more formal structure and it looks like the@java-maint-sig was working this way. No need to interchange any word, no need to trash, minimize or insult the work of any of the SIGs. I don't like Java, neither the language, the way it works with the JVM and JDK and JRE, neither the company it came from; but it's been around for 25 years and it probably will continue for a long time; and people will come and go to maintain what they need to work with it. Just please acknowledge that the @java-maint-sig has no active members, and continue with your lifes. Hope everyone is ok. Best regards [1] https://fedoraproject.org/wiki/Join#PeoplePerson -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: Orphaning pasystray, clipit, python-i3ipc, rnv
I'm not a proven packager, but I'm interested in clipit. Is possible for me to take it? El vie, 19 mar 2021 a las 5:19, Dominik 'Rathann' Mierzejewski (< domi...@greysector.net>) escribió: > On Thursday, 18 March 2021 at 20:44, Michael Šimáček wrote: > > Hi, > > > > Due to lack of time and motivation I've just orphaned the following > > packages which are now free to take: > > pasystray > > I would've taken pasystray as I use it, but it seems Yaakov beat me > to it. > > Yaakov, would you consider updating it to 0.7.1 in F33+, too? > > Regards, > Dominik > -- > Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org > There should be a science of discontent. People need hard times and > oppression to develop psychic muscles. > -- from "Collected Sayings of Muad'Dib" by the Princess Irulan > ___ > 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 > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Re: [i3] i3 Spin staging site now available
Hello Justin and team, Hi all, > > Ben Cotton built a preview of the i3 Spin website that will be used for > Fedora 34. We need to include descriptions of the apps we will ship; > currently, what is shown is for the LXQt desktop. > > https://spins.stg.fedoraproject.org/i3/ > It looks awesome. > Alternatively, we can also opt to not have any applications shown, but I > think it would be cool to show what we're shipping here. > I think we can start with the list that is in our docs [2]. > We will need some hands to help us out with drafting the text to go on > the site. More details in the fedora-websites ticket: > > https://pagure.io/fedora-websites/issue/1056 We agreed with the text on our ticketing instance [1] [1] https://pagure.io/i3-sig/Fedora-i3-Spin/issue/31 [2] https://docs.fedoraproject.org/en-US/i3/package-groups/#minimal -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: CentOS Project shifts focus to CentOS Stream Re: End of CentOS Linux: What about Fedora?
Quite literally here: "CentOS Linux 8, as a rebuild of RHEL 8, will end at the end of 2021" Br, El sáb, 12 dic 2020 a las 12:03, Sérgio Basto () escribió: > On Wed, 2020-12-09 at 00:26 -0300, Sergio Belkin wrote: > > Hi, > How does this (https://blog.centos.org/2020/12/future-is-centos-stream/) > affect Fedora? > > > where you read that is the end of centos ? > > > ___ > > 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 > > > -- > > Sérgio M. B. > > ___ > 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 > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: The future of Fedora Server (was Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change))
I'm not part of the server WG, but a super interested user. Count me in to help if needed. Br, El vie, 4 dic 2020 a las 14:00, Neal Gompa () escribió: > On Fri, Dec 4, 2020 at 11:49 AM Matthew Miller > wrote: > > > > On Fri, Dec 04, 2020 at 10:03:24AM +0100, Fabio Valentini wrote: > > > I agree, sign me up! I've been using Fedora Server for years for my > > > own projects and it's been 99.9% flawless, so I would be sad if it > > > went away. > > > > No one is talking about making it go away, just de-editioning it. I'd > > definitely prefer it to remain an edition, but we need it to be more > active > > for that to work. > > > > Having an active team is one thing, but making changes just because is > quite another. I don't feel it's worth demoting Fedora Server (just > like I didn't like what happened to Fedora Cloud way back when with > Atomic). But if you need me to be there to keep the WG going so it > doesn't get demoted, I'm happy to help shepherd it. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > 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 > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: video meeting to discuss Matrix/Element and IRC
Can we all stop talking about Discord? The Council is trying to update their communications platforms and the options were clearly stated: - Discourse (not Discord, please notice the difference in their names) replacing ML - Matrix replacing IRC. In both cases the Council is looking to keep all platforms bridged or somehow communicating with the new ones. In the particular case of this thread, Matrix has several advantages and IRC will still be keep it bridged, so from my POV we are gaining advantages and not losing anything. Br, Eduard Lucena ___ 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: Increasing the packaging team: regular workshops/vFADs/classroom sessions on packaging
Hello, As part of the marketing team, I think we could put a community campaign, with a video series (series means at least 3) posted properly on YouTube and promoted by Twitter, CommBlog and ML: "Package with us!" Wdyt! Br, El jue., 21 may. 2020 a las 6:12, Ankur Sinha () escribió: > On Thu, May 21, 2020 09:16:40 -, Artur Iwicki wrote: > > I've written blog posts about packaging and gave a talk about it on a > > local Linux group, so I'd be glad to participate in workshops or some > > other initiative. > > > > One idea that comes to my mind right now is - how about making a video > > tutorial? While I personally dislike those and prefer text, I know > > many people like videos for learning, so it might be a worthwhile > > investment. > > That would be great. Any material that walks people through packaging is > useful. > > If at all possible, I'd like to have classroom sessions---there's > something about a live session that encourages people to get involved. > Reading docs and watching videos to self learn lacks the "getting to > know the community" aspect. > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | > https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London > ___ > 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 > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: i3wm for EPEL8
Adding the i3 SIG to the loop, maybe is something achievable by us. Br, El mar., 19 may. 2020 a las 14:11, Paul Howarth () escribió: > On Tue, 19 May 2020 10:47:57 -0400 > Eric Mesa wrote: > > I noticed that the i3 window manager wasn't available in EPEL8. Before > > trying to go through the process of becoming a package maintainer I > > decided to try and run it via copr to see how much modification was > > needed. For EPEL8 (as opposed to 7) I was able to take the current > > spec file and, after creating an EPEL8 copr repo for xcb-util-xrm ( > > https://copr.fedorainfracloud.org/coprs/djotaku/xcb-util-xrm/), it > > would build. But it wouldn't install for it needed some perl > > packages. So I set about building those. You can see how far I got in > > ( https://copr.fedorainfracloud.org/coprs/djotaku/i3wm/packages/), > > but each one had one or more dependencies. So I was rapidly along a > > path towards having to recreate nearly all of Perl for EPEL8. (Only a > > slight exaggeration). Unfortunately, for those, I couldn't just bum > > the spec file because they each had a patch that needed to be > > applied. So I had to download the repo from pagure, use spectool and > > mock to create the srpm and then load that into copr. Quite tedious. > > Interesting what you say about the perl modules because > perl-common-sense, perl-JSON-XS and perl-Types-Serialiser are available > in the EL-8 Code Ready Builder / PowerTools repo, which is a dependency > of EPEL-8: > https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F > > Is that repo not enabled in your EPEL-8 configuration? > > Paul. > ___ > 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 > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: i3 new SIG
Hi Robbie > Depends - do you want us XMonad aficionados to show up? :) > Everyone is invited to join. > (I'm only half joking here, I think. There are some common shared > components I think - the suckless stuff, for instance - but also there > should be a limit to how big a tent you want to have here.) > I still use too many X apps, Wayland still doesn't cover a lot of stuff. > Thanks, > --Robbie > Thinking it more deeply, we can produce a lot of stuff and if Sway is so compatible with i3 as is stated, they should take benefit when all X-needs are covered and make the jump smoothly. Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: i3 new SIG
Hi Dan, Hi Eduard! > > As the current maintainer of i3, I kinda have to join ;-) > Thanks! Welcome! As others have already mentioned in the thread: we should look into > joining forces with the sway SIG (which I am also a member of). It's not a bad idea, but TBH, I still want to stay away from Wayland. While a lot of the packages of interest are not really shared, the general > similarity would allow us to save a lot of time when it comes to QA and > the creation of a spin. Maybe we should merge into the tilling window > manager SIG? (with a better name of course). > Well, we can join effort for packaging but produce different Spins, why not? wdyt? > Cheers, > > Dan > Br, -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: i3 new SIG
Hi, What about sway? :) > Sway have a SIG [1]. You can probably go there and join! :D [1] https://fedoraproject.org/wiki/SIGs/Sway -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
i3 new SIG
Hello guys, My name is Eduard Lucena, some of you maybe know me, tons of you don't. I'm part of the marketing team and host of the Fedora Podcast. I'm starting a SIG about i3 tiling window manager [1], with the final objective of create a remix that can finish up in an official spin. I have a ML you can join [2] and I'm hanging around on #fedora-i3 on IRC. I have a few ideas and I really would love to hear yours. Br, [1] https://fedoraproject.org/wiki/SIGs/i3 [2] i...@lists.fedoraproject.org P.D. I want to create a FAS group, but it looks like it requires more than just having a FAS account. I'll sort out that as soon as possible. -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Fedora AMA on Telegram
Hello, guys, we (admins of Official Fedora Telegram channel[1], at the behest of a member of the group) are hosting an AMA (date not set yet) on a freshly minted telegram group @Fedoraama [2]. We hope to invite as many Fedora contributors and people as possible, and have a lively 3/4 hours discussion. Would anyone be interested to help us out? Would anyone like to participate? We welcome both Q and A segments. We will bridge the group in question with IRC too! We have conservatively decided to have the meeting on the 6th of May 2020, 1400 to 1530 hours, US/Eastern time. Please do drop by! [1] https://t.me/fedora [2] https://t.me/fedoraama -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: Non installable package on F31: python3-i3ipc
Thanks for the answer. I make a comment in the bug. El mar., 25 feb. 2020 a las 16:42, Scott Talbert () escribió: > On Tue, 25 Feb 2020, Eduard Lucena wrote: > > > Hello team, > > > > I'm writing this here, because I don't know of any other place, so if > there > > is another place to report it, I'll listen to go there. > > > > I'm trying to install the package: python3-i3ipc > > > > $ sudo dnf info python3-i3ipc > > Last metadata expiration check: 0:02:42 ago on Tue 25 Feb 2020 02:18:22 > PM > > -03. > > Available Packages > > Name : python3-i3ipc > > Version : 1.5.1 > > Release : 4.fc31 > > Architecture : noarch > > Size : 29 k > > Source : python-i3ipc-1.5.1-4.fc31.src.rpm > > Repository : fedora > > Summary : An improved Python library to control i3wm > > URL : https://github.com/acrisci/i3ipc-python > > License : BSD > > Description : > > : i3's interprocess communication (or ipc) is the interface > > i3wm uses to receive > > : commands from client applications such as i3-msg. It also > > features > > : a publish/subscribe mechanism for notifying interested > > parties of window > > : manager events. > > : > > : i3ipc-python is a Python library for controlling the > window > > manager. This > > : project is intended to be useful for general scripting, > and > > for applications > > : that interact with the window manager like status line > > generators, notification > > : daemons, and pagers. > > > > > > But I get the following error: > > > > $ sudo dnf install python3-i3ipc > > Last metadata expiration check: 0:03:09 ago on Tue 25 Feb 2020 02:18:22 > PM > > -03. > > Error: > > Problem: conflicting requests > > - nothing provides python3.7dist(enum-compat) needed by > > python3-i3ipc-1.5.1-4.fc31.noarch > > (try to add '--skip-broken' to skip uninstallable packages) > > > > I'm reporting it, because the package is coming from the Fedora repo, not > > from a 3rd party repos, so I assume that we should provide it and should > be > > installable. > > > > > > If this is the wrong place, please guide me to the right place. Thanks a > lot > > for your efforts and time to keep fedora great. > > Usually the best place to report a bug about a specific package is > bugzilla. It appears this bug has already been reported. However, it has > been open for a few months without any response: > https://bugzilla.redhat.com/show_bug.cgi?id=1770839 > > Scott -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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
Non installable package on F31: python3-i3ipc
Hello team, I'm writing this here, because I don't know of any other place, so if there is another place to report it, I'll listen to go there. I'm trying to install the package: python3-i3ipc $ sudo dnf info python3-i3ipc Last metadata expiration check: 0:02:42 ago on Tue 25 Feb 2020 02:18:22 PM -03. Available Packages Name : python3-i3ipc Version : 1.5.1 Release : 4.fc31 Architecture : noarch Size : 29 k Source : python-i3ipc-1.5.1-4.fc31.src.rpm Repository : fedora Summary : An improved Python library to control i3wm URL : https://github.com/acrisci/i3ipc-python License : BSD Description : : i3's interprocess communication (or ipc) is the interface i3wm uses to receive : commands from client applications such as i3-msg. It also features : a publish/subscribe mechanism for notifying interested parties of window : manager events. : : i3ipc-python is a Python library for controlling the window manager. This : project is intended to be useful for general scripting, and for applications : that interact with the window manager like status line generators, notification : daemons, and pagers. But I get the following error: $ sudo dnf install python3-i3ipc Last metadata expiration check: 0:03:09 ago on Tue 25 Feb 2020 02:18:22 PM -03. Error: Problem: conflicting requests - nothing provides python3.7dist(enum-compat) needed by python3-i3ipc-1.5.1-4.fc31.noarch (try to add '--skip-broken' to skip uninstallable packages) I'm reporting it, because the package is coming from the Fedora repo, not from a 3rd party repos, so I assume that we should provide it and should be installable. If this is the wrong place, please guide me to the right place. Thanks a lot for your efforts and time to keep fedora great. Best Regards, Eduard "X3MBoy" Lucena -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ 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: Fedora Lifecycles: imagine longer-term possibilities
Well, I have read tons of things, and only one thing bump in my head: "Ubuntu LTS" I mean, it's a great idea, and a lot of people have asked about it in forums, reddit, twitter, fedoraforums and the list goes on. I thing that if someone can make it happens is the awesome Fedora Developers team, but actually my concern is in how to avoid the comparison, or being called copycats, or put in doubt both originality and innovation. I know is probably too early, but give it a thought from the point of view of the marketing: How we can advertise a product that others have? Br, El jue., 15 nov. 2018 a las 21:46, Jason Tibbitts () escribió: > >>>>> "MM" == Matthew Miller writes: > > MM> Let's talk about something new and exciting. > > I assume that you mean "very much not new and about as exciting as the > fifteenth viewing of an episode of the Joy of Painting". > > I know it's been a while. Maybe it's been long enough that a > significant number of the developers here don't remember it. I am > pretty sure you were around, though, so I do hope you have some > recollection of it. Put simply, Fedora has had this discussion before. > A number of times. Going back to FC1 and what the release cycle would > look like. At one point it was basically an endless thread that lasted > the better part of a year. > > For the life of me I simply can't remember the various proposals called > their releases, though. > > One example of what I'm talking about is > > https://kanarip.fedorapeople.org/Fedora%20Extended%20Lifecycle%20Support%20-%20The%20why,%20the%20what,%20the%20how%20and%20the%20who.pdf > but that came after I stopped paying attention to this kind of thing. > > In the end the discussions I recall seemed to come down to a few basic > things. > > 1) A lot of people would love to consume such a release. > > 2) Not nearly as many actual maintainers would want to do so. > > 3) At minimum, we need a kernel. Which means we need a kernel team. I >doubt the current kernel team would be any more enthusiastic about >either backporting everything, maintaining packages of the extended >lifetime kernel packages (assuming those even line up with the >release schedule) or pushing the current kernel back to the >equivalent of... Fedora 25 or so. > > 4) Someone has to do release engineering. Even in the earlier days this >was seen as something that wasn't going to happen. > > My recollection is that meaningful discussion usually stopped at the > kernel issue. At one point we had some basic agreement that people who > cared were welcome to push to old branches of things to keep them going, > but that was back when we had per-branch ACLs. But that never happened, > and as there was no effort to actually compose updates for those > releases, it doesn't matter much anyway. > > And now we're bigger, and there are more big systems that would need > maintenance. Oh, and we have a security team now; they'd have to deal > with issues in those old releases. And more big package sets like > Python and Node and Go and whatever, some of which amount to a larger > number of packages than made up the entirety of one of the old Fedora > releases. Hello, Python SIG? Good luck finally getting rid of > python2. You get two more years of support backporting security fixes > and you don't even get paid for it. > > And to add in an additional argument that we didn't have a decade ago: > We're actually trying to evolve our packaging now. EPEL with it's "old > RPM never changes" restriction is bad enough but fortunately limited in > scope. Having years of Fedora releases that can never evolve but which > still hold back progress in Rawhide is just too much. > > Really, this is what our downstream distributions RHEL and CentOS are > for. That was the answer then and I don't see why it doesn't still > apply. > > MM> How would we balance this with getting people new stuff fast as > MM> well? > > Wait, what? Certainly you're not suggesting trying to do an extended > lifecycle that also gets all the new stuff. That's seems like a > contradiction in terms. > > - J< > ___ > 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 > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___
Re: Fedora Packaging Guidelines on docs.fedoraproject.org
Hi, The question is not about code higlighting but rendering, so when you look > at an > .adoc file it looks like what it would look once transformed into html. > Just like, when you are looking at a readme.md, you don't see the markdown > syntax (unless you specifically ask for it). > For this you can create a local test (I think how to do this is explained in the docs' pagure) or use an editor that create a preview like atom with the asciidoc plugin or asciidocfx. More options can be found on the asciidoc site [1]. Hope this is helpful, Eduard Lucena [1] https://asciidoctor.org/docs/editing-asciidoc-with-live-preview/ > ___ 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: Add release announcement post to Go/No-Go criteria
In fact, and I'm going to take the fault on this, mattdm beta release announcement in the RedHat portal[1] is so awesome, that makes look the one on the Fedora Magazine like a robotic template. Because change set doesn't provide context on why X or Y feature is good or awesome. [1] https://www.redhat.com/en/blog/fedora-29-beta-now-available El mar., 25 de sep. de 2018 18:33, Eduard Lucena escribió: > Basically, the issue on the announcement is that is tight to the Talking > Points, and almost any team is helping us with that. The Marketing task is > to collect the Talking Points, not to create them, because we aren't the > people that work on the new features and the stuff that make the release > awesome, having no talking points create the delay we had today with the > Beta Announcement, because we basically have based the announcement on the > change set, that doesn't necessarily provide good context for general users > on how that is good for the distro. It will be sad to delay the release one > week only for the announcement, I know, but we at least need a way to > engage teams to work on the Talking Points. > > Br, > > El mar., 25 de sep. de 2018 18:25, Kevin Fenzi escribió: > >> On 09/25/2018 01:35 PM, Ben Cotton wrote: >> > With today's Beta release, the release announcement post for Fedora >> > Magazine was not ready. As a result, the announcement went out a >> > little late and then only due to a drop-everything effort (thanks, >> > stickster!). We have a proposal to add a fourth criterion for the >> > Go/No-Go decision, beginning with F29 Final: >> > >> > 4. The release announcement post for Fedora Magazine is substantially >> complete >> > >> > As a reminder, these are the existing criteria: >> > >> > 1. No remaining blocker bugs >> > 2. Release candidate compose is available >> > 3. Test matrices for [milestone = Alpha, Beta, Final] are fully >> completed >> >> I'm prefer to add a new milestone of 'day before release' and put it >> there. I think after the 'go' some folks who would be helpful in making >> the announcement have more time to devote to it. Also, it would seem sad >> to me to be 'go' except for an announcement, and slip a week. >> >> kevin >> >> >> >> ___ >> 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 >> > ___ 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: Add release announcement post to Go/No-Go criteria
Basically, the issue on the announcement is that is tight to the Talking Points, and almost any team is helping us with that. The Marketing task is to collect the Talking Points, not to create them, because we aren't the people that work on the new features and the stuff that make the release awesome, having no talking points create the delay we had today with the Beta Announcement, because we basically have based the announcement on the change set, that doesn't necessarily provide good context for general users on how that is good for the distro. It will be sad to delay the release one week only for the announcement, I know, but we at least need a way to engage teams to work on the Talking Points. Br, El mar., 25 de sep. de 2018 18:25, Kevin Fenzi escribió: > On 09/25/2018 01:35 PM, Ben Cotton wrote: > > With today's Beta release, the release announcement post for Fedora > > Magazine was not ready. As a result, the announcement went out a > > little late and then only due to a drop-everything effort (thanks, > > stickster!). We have a proposal to add a fourth criterion for the > > Go/No-Go decision, beginning with F29 Final: > > > > 4. The release announcement post for Fedora Magazine is substantially > complete > > > > As a reminder, these are the existing criteria: > > > > 1. No remaining blocker bugs > > 2. Release candidate compose is available > > 3. Test matrices for [milestone = Alpha, Beta, Final] are fully completed > > I'm prefer to add a new milestone of 'day before release' and put it > there. I think after the 'go' some folks who would be helpful in making > the announcement have more time to devote to it. Also, it would seem sad > to me to be 'go' except for an announcement, and slip a week. > > kevin > > > > ___ > 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 > ___ 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: I intent to orphan barman
Ok, thanks for the tip. Br, El lun., 20 de ago. de 2018 16:20, Miro Hrončok escribió: > On 20.8.2018 21:09, Eduard Lucena wrote: > > Hi, > > > > Can this package be a good one to start at packaging? > > > > If it is, I will be happy to take it. > > I'd recommend to start with couple of your own packages before such offers. > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ 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/W3UKJROLKO2QR2ZY47MW3PYWBPTKUSGB/
Re: I intent to orphan barman
Hi, Can this package be a good one to start at packaging? If it is, I will be happy to take it. Br, El lun., 20 de ago. de 2018 15:06, Miro Hrončok escribió: > I recently got https://src.fedoraproject.org/rpms/barman > > I will orphan it in a week if nobody wants it. > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > 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/HG7QVZBEOOFKVMLRBXO5CS57FFPVJZUQ/ > ___ 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/3YTI2F6LYY7YBCGI6DFOXO24JTTVPYBN/
Re: Starting a Container SIG
Hi, I'm not familiar with the container technology, but I will love to learn it. I would like to help with this SIG. Br, El mié., 25 de jul. de 2018 1:57 PM, Clement Verna escribió: > Greeting all, > > The container effort in Fedora has until now been looked after by the > Atomic WG, since this Working Group is now going to focus mostly on > Fedora CoreOS, I propose to create a new container SIG to regroup > people interested in the maintenance of application containers in > Fedora. > > This SIG would look after the container guidelines [0], the container > review process [1] and also the release process and tooling. > > Please Reply if you're interested with helping out making the > Container story great in Fedora. If there is a good response, I will > create a Container SIG wiki page, and I guess we can ask for > container-devel mailing list for SIG discussions. > > Regards, > Clément > > [0] - https://fedoraproject.org/wiki/Container:Guidelines > [1] - https://fedoraproject.org/wiki/Container:Review_Process > ___ > 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/55QK4AYKBFGLFXCGAVJSXLEVEMC5NJQ2/ > ___ 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/SDTFDXWQUK4TALQEIGY2FKKOXG32B3NN/
Re: Anyone interested in Testing the wireframes of the Fedora Community App?
Count me in! -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Libravatar shutting down on 2018-09-01
I was reseraching a little bit and I found that this project is made in python with Django. Is it possible that we can take this project and do an implementation of our own? The current implementation [1] is: - Debian - Postgres - Django - Python stack And the stats (infrastructure requirements) [2] are: - Storage: - Application server: - 1 GB General Purpose v1 Rackspace cloud server - Number of user accounts: 6655 - Number of unique avatars: 6919 (355 MB) - Static image server: - 1 GB General Purpose v1 Rackspace cloud server - Size of avatars on disk: 1.8 GB - Traffic: - Application server: - Bandwidth: 328.31 MB - Hits: 43,823 - Static image server: - Bandwidth: 18.99 GB - Total hits: 11,191,373 - Redirects (to Gravatar): 9,605,127 There is a long blog post [3] about why it's shutting down, but the link that I found useful for possibly take this project is the development environment [4]. It's just a question, maybe is too big to take it for the whole world, but it looks like a great project for the Python SIG. Br, [1] https://blog.libravatar.org/posts/Libravatar.org_is_shutting_down_on_2018-09-01 [2] https://wiki.libravatar.org/shutdown-coordination [3] https://feeding.cloud.geek.nz/posts/looking-back-on-starting-libravatar [4] https://wiki.libravatar.org/development_environment -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
