devel November 2019

devel@lists.centos.org

44 participants
33 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

Unshipped -devel packages in CentOS Linux
by Brian Stinson 28 Feb '20

28 Feb '20

Hi Folks, We're gearing up to build the next minor release of CentOS Linux 8 so I thought now would be a good time to revisit the conversation we've been having about what to do with unshipped -devel packages. Just a reminder on a few guiding principles: - The BaseOS, AppStream, and PowerTools repos in CentOS Linux are designed and composed to match Upstream as closely as possible, both in content and behavior - Unshipped devel packages have no defined maintenance lifecycle in Upstream, and especially not in CentOS - We know that some of these devel packages are essential to build applications that the CentOS (and probably EPEL) communities care about. The problems we need to solve if we decide to ship these packages somewhere in a CentOS artifact: - Communicate that these packages are provided as-is and are not meant for runtime dependencies - Provide the packages in a form that is consumable for individuals and the EPEL community I'd like to propose that we create a separate repository, disabled by default that is composed of the -devel packages that we care about, bundled in a module. The name of this repository and the module is up for discussion, but I would like the naming to help with the communication that these are not for general consumption. I'd also like to discuss how we populate this repo/module. It would be easiest to just dump every unshipped package in and move on, but that doesn't help us track which of these packages are truly important outside of building the distro. Shipping *everything* also represents a larger content set to manage if lifecycle issues come up in the future. An alternative would be to store this definition in git (we'll need to do that anyways), and allow folks to make pull requests to include new content, shipping this as a separate repo would let us spin updates on demand. Looking forward to the discussion! -- Brian Stinson CentOS Infra Team

14 29

CentOS 8 Artwork needed
by Rich Bowen 31 Jan '20

31 Jan '20

To all the artists and designers here, we need your help. With RHEL 8 beta released, we need to start producing artwork for CentOS 8. It's time for the CentOS Artwork SIG, and anyone else that's interested in contributing to this effort, to start working on everything that will be needed for the new release. What we know we need is anaconda artwork, and new desktop backgrounds to replace the current '7' themed stuff. As we dig, we may find more things that need to be updated to the new 8 theme. Additionally, we will need to update some of the assets listed here: https://wiki.centos.org/ArtWork/Identity ... and produce new assets for 8 to be listed here: https://wiki.centos.org/ArtWork/Brand/Logo And, finally, we need someone to step up to lead this effort. While we don't yet know for certain when RHEL 8 will officially release, it's safe to assume that it's soon, and we need your help. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

10 30

C8 updates / CentOS-announce
by Leon Fauster 07 Jan '20

07 Jan '20

Do package updates for C8 get announced via centos-announce list? If not whats the new communication "channel"? I see updates but no corresponding announcement ... -- Leon

7 15

Re: [CentOS-devel] Minutes for CentOS Board of Directors 2019-11-13 Meeting
by Patrick Laimbock 03 Jan '20

03 Jan '20

Hi Karsten, Thank you for the update. > Topics covered in the meeting and via email are discussed below, and > remain open on the Board’s rolling agenda for future conversation and > actions: > > 1. Board membership: > 1. The Board has been considering for some time adjusting the > membership of the Board, in particular by adding new Directors. > Discussions with potential new Directors will begin. That's great news. Will the process be similar to how it's done in the Fedora Project [1]? So with a public list of nominees, published interview with each nominee and public voting results? Is there a way for the Community to (self-)nominate? For better Community coverage perhaps CentOS Board related postings could also be sent to the centos-announce and centos mailinglists? Thanks, Patrick [1] https://docs.fedoraproject.org/en-US/program_management/elections/

6 7

Re: [CentOS-devel] missing src.rpm for updated centos 8 kernels?
by Patrick Laimbock 19 Dec '19

19 Dec '19

Hi, -----Original message----- > Hi all, > > Latest (at this time) kernel for Centos 8 is kernel-4.18.0-80.11.2.el8_0. > I am unable to find the .src.rpm for this kernel anywhere in Centos repositories. > > I looked in: > http://vault.centos.org/centos/8/BaseOS/Source/SPackages/ > http://mirror.nsc.liu.se/centos-store/centos/8/BaseOS/Source/SPackages/ > > Source package link on centos.pgks.org is also dead: > https://centos.pkgs.org/8/centos-baseos-x86_64/kernel-4.18.0-80.11.2.el8_0.… > > Where can I find the src.rpm for this kernel? Source packages are available on http://vault.centos.org Best, Patrick

4 10

Reasoning behind RHEL8 packages without corresponding -devel?
by Anthony Alba 12 Dec '19

12 Dec '19

(Of course, we should be asking RH... but nevertheless) EPEL 8 has several issues regarding packages without corresponding -devel. E.g., libXvMC, libbluray. I see that this causes grief for EPEL 8 and collateral damage to RPMFusion. Did RH disclose the reason for this? Was there any discussion on where CentOS will put them, like in Extras perhaps? (I was rolling out some testing VMs in RHEL8 and OL8, and noticed the new but "unsupported" CodeReady repos with -devel packages; yet not all -devels are them.) Cheers Anthony

16 43

CentOS 8 docker images
by Lance Albertson 06 Dec '19

06 Dec '19

When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen? Thanks! [1] https://github.com/CentOS/sig-cloud-instance-images/issues/151 -- Lance Albertson Director Oregon State University | Open Source Lab

10 11

CPE Weekly: 2019-11-29
by Aoife Moloney 29 Nov '19

29 Nov '19

Hi everyone, Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: CentOS: The team have been testing projects migration from repospanner to locally hosted git repositores on git.dev.centos.org and come back with a migration script/plan to unblock RCM CentOS Stream Scoping meetings are still ongoing Fedora: Rawhide Gating: Bodhi was 5.1 released and is deployed in staging Robosignatory is broken in staging preventing testing much there Application Retirements Elections Elections being moved to Communishift really soon! Stay tuned! Fedocal Still no progress on kanban board last four weeks https://teams.fedoraproject.org/project/fedora-calendar/kanban Jlanda is still hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274 Still working on running local instance Nuancier Benson Muite is now working on OIDC authentication A PR will be created on Github to test if we can see the progress New PR from sebwoj - Porting to Fedora messaging is under review Pastebin Still on track for December 1 modernpaste shutdown GDPR and privacy centric conversations with respect to application handovers have resulted in…..more conversations needed - shock :) Misc Bugzilla sync script has been resolved Email inviting to review its change has been sent New changes to src.fedoraproject.org deployed: Ability to set the anitya monitoring status directly in the UI Ability to adopt orphan (and not retired) packages directly in the UI New changes to Pagure on the horizon: New API endpoint to enable/disable git hooks Ability to set dist-git in the default assignee overrides for bugzilla EPEL 8 modularity Updates can now be created in bodhi staging! We are currently testing pushes/composes We are also testing epel8-playground-modules composes Aarch64 is now racked and networked Koji New koji owner script was debugged Koji client was updated Koji was also patched for the --title option fix Configured migrations from Ansible/Jinja template https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/1 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/3 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/11 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/14 https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/16 Various Resolved Issues https://pagure.io/mdapi/pull-request/91 https://github.com/fedora-infra/bodhi/pull/3782 Comments? Suggestions? Feedback? Let Us Know! Have a great weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Minutes for CentOS Board of Directors 2019-11-13 Meeting
by Karsten Wade 27 Nov '19

27 Nov '19

From https://blog.centos.org/2019/11/minutes-for-centos-board-of-directors-2019-…: Public minutes On 2019-11-13 theCentOS Board of Directors <https://centos.org/about/governance/>held their first meeting following the release of CentOS Linux 8 and announcement of CentOS Stream. As covered in this meeting, the CentOS Board are taking on an initiative to increase transparency of the working of the Board. This set of minutes for the community and wider public is the first instance of new, more transparent processes in action. Topics covered in the meeting and via email are discussed below, and remain open on the Board’s rolling agenda for future conversation and actions: 1. Board membership: 1. The Board has been considering for some time adjusting the membership of the Board, in particular by adding new Directors. Discussions with potential new Directors will begin. 2. All Directors discussed the need for future leadership of the CentOS Project to continue being able to straddle the project’s traditional footing on one side, and help drive a vision for the future on the other side. 2. Transparency initiatives: 1. All agree that the biggest need for transparency in the Project is at the Board level. 1. Other groups e.g. SIGs are generally following good transparency practices 2. Board Directors have been asked directly about this topic and the issue of the Board not releasing minutes from meetings. 3. The Board’s infrequent meetings have not been configured to easily generate public topics, since most technical and day-to-day leadership happens in the SIGs especially the Core SIG and QA SIG. 2. Next step -- improving Board meeting norms: 1. *AGREED:*Publish (for next and future meetings) that there will be a meeting, and what the public portion of the agenda is, in advance of the meeting. 2. *AGREED:*Publish a set of public minutes within 72 hours of the conclusion of a Board meeting 3. *AGREED:*There will be a rolling element to the agenda so that items are not dropped between meetings but rather eventually addressed/resolved. 4. *ACTION*: Karsten to write and publish this set of public meeting minutes 3. New branding work underway - Karsten briefed the Board on the community efforts to consider the CentOS brand, logo, and overall branding in light of the addition of CentOS Stream. 1. https://git.centos.org/centos/Artwork/issue/1 2. https://lists.centos.org/pipermail/centos-devel/2019-November/018098.html 3. *AGREED*: Board more actively drive approving/rejecting design ideas. 4. *AGREED*: There will be a reasonable time for discussion around the potential brand changes, and the Board will ensure the discussion concludes in a timely manner. -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://theopensourceway.org gpg: AD0E0C41 | https://red.ht/sig

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2019