Re: Roseline Bassey - Community Architect Intern Introduction

[Justin W. Flory (he/him)]

Welcome to the Fedora community, Roseline! 🎉 I'm excited to have you as an
intern over the next few months. 💪🏻

I also put this in my last reply, but for anyone curious about how the
Outreachy internships are being conducted, you can see the intern issue
tracker on GitLab [1] for more
information.

[1] – https://gitlab.com/fedora/commops/interns/

On Mon, May 27, 2024 at 2:40 PM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:

> Hello, Roseline!
>
> On Monday, 27 May 2024 at 17:26, Roseline Bassey wrote:
> [...]
> > I’m excited to bring my experience and skills and to contribute to and
> > support various Fedora teams and the broader community during my
> > internship.
>
> Welcome to Fedora!
>
> Regards,
> Dominik
> --
> Fedora   https://fedoraproject.org
> Deep in the human unconscious is a pervasive need for a logical universe
> that
> makes sense. But the real universe is always one step beyond logic.
> -- from "The 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, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
*JWF* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗
*Fedora is a registered Digital Public Good
*

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
--
___
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: Tosin Adesola - Community Architect Intern Introduction

[Justin W. Flory (he/him)]

Welcome to the Fedora community, Tosin! 🎉 Looking forward to working with
you over the next few months. 💪🏻

For anyone curious about how the Outreachy internships are being conducted,
you can see the intern issue tracker on GitLab
[1] for more information.

[1] – https://gitlab.com/fedora/commops/interns/

On Mon, May 27, 2024 at 8:52 AM Priscila Gutierres 
wrote:

> Good to see you here Tosin.
> Welcome :-)
>
> On Mon, May 27, 2024 at 9:51 AM TosinDoreen  wrote:
>
>> Hello Fedora folks!🫡
>>
>> I'm Tosin Adesola, excited to join your ranks as a community architect
>> intern. I'm calling Nigeria home, and while my Linux experience is mostly
>> through Outreachy, I'm eager to dive deeper into the Fedora universe.
>>
>> Community building is my jam – I love bringing people together,
>> coordinating events, and making sure everyone feels included. I'm thrilled
>> to bring that passion to Fedora and learn all I can about Git, tech
>> writing, and crafting engaging social content. Let's collaborate!
>>
>> Connect with me on:
>>
>> Email: tosindor...@gmail.com
>> Matrix: @tosin_doreen:matrix.org
>> --
>> ___
>> 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
>>
> --
> ___
> 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
>


-- 
*JWF* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗
*Fedora is a registered Digital Public Good
*

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
--
___
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: Introduction: Adrian Edwards - Fedora Community Architect Intern

[Justin W. Flory (he/him)]

Welcome to the Fedora community, Adrian! 👋🏻

On Tue, May 21, 2024 at 3:33 PM Adrian Edwards 
wrote:

> Hello Fedora devel mailing list,
>
> My name is Adrian and i'm a CS student at RIT who is minoring in Free and
> Open Source Software. I wanted to send this out briefly to introduce myself.
> I'll be working as a Fedora Community Architect Intern during my time with
> Red Hat in Boston (US/Eastern TZ) and I'm excited to learn about the Fedora
> community. One particular recurring interest of mine has been wondering how
> to encourage more of the people who benefit from open source to support it
> or give back in some way so that working on smaller, independent open
> source passion projects that others rely on can become as common as making
> a living working on corporate-controlled open source and improve the
> stability of the system as a whole (here's an [amazing podcast episode](
> https://www.npr.org/2024/05/17/1197959102/open-source-xz-hack) i recently
> heard about the recent XZ hack that makes a really good point about public
> goods at the end).
>
> Maybe this is a bigger goal than I'll realistically be able to tackle in
> the next few months in my current role, but I hope to at least learn as
> much as possible about Fedora and surrounding communities to see where
> there may be opportunities for me to make a difference.
>
> If you need to reach me, I'll do my best to monitor the following places:
>   - Fedora Discussions: @moralcode
>   - Matrix: @moralcode:fedora.im
>   - Email: moralc...@fedoraproject.org
>
> Adrian Edwards
> --
> ___
> 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
>


-- 
*JWF* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗
*Fedora is a registered Digital Public Good
*

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
--
___
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

[Last call, due Thu 11 April] Join us! Restarting Community Ops team meetings in 2024

[Justin W. Flory (he/him)]

Hi Fedora Devel,

I wanted to echo this Community Blog post
<https://communityblog.fedoraproject.org/restarting-community-ops-2024/>[1]
on the Devel list. This is the final week that the meeting poll is open for
the Community Operations team meetings. This is a gradual comeback for the
team since its pause in 2019/2020.

If you are interested, please fill the meeting poll
<https://rallly.co/invite/xVPA5fJISpXB>[2] by end-of-day on Thursday, 11
April.

Full details below.

=== === ===

After a long pause since 2019, the Fedora Community Operations (CommOps)
team
<https://docs.fedoraproject.org/en-US/commops/contribute/commops-landing/>[3]
will hold an inaugural meeting in support of the recently-approved Community
Ops 2024 Reboot
<https://fedoraproject.org/wiki/Initiatives/Community_Ops_2024_Reboot>[4]
Community Initiative. *Please fill the meeting day/time poll
<https://rallly.co/invite/xVPA5fJISpXB>[2] if you are interested by
Thursday, 11 April 2024*.
Bringing back the team in 2024

After a bit of a break—thanks to **cough cough** COVID—the Community Ops
team is revving up again! We’ve got big plans, like the Fedora Linux 40
Release Party in May and diving into the Community Initiative
<https://fedoraproject.org/wiki/Initiatives/Community_Ops_2024_Reboot>[4]
proposed from February to October this year.

The first meeting will be co-chaired by Alberto Rodriguez Sanchez
<https://fedoraproject.org/wiki/User:Bt0dotninja>[5] (bt0dotninja), Robert
Wright <https://fedoraproject.org/wiki/User:Rwright>[6] (rwright), and Justin
W. Flory <https://fedoraproject.org/wiki/User:Jflory7>[7] (jflory7).

But here’s the deal: *we need your help*. We want to invite the community
to be a part of the new team. This includes community members who have
either been around for a long time or a short time.
Fill in the meeting day/time poll

So, help us mark the calendars! Our first meeting is happening between
April 15th and 19th, 2024. But we need your input to lock down the perfect
time. *Fill the meeting day/time poll
<https://rallly.co/invite/xVPA5fJISpXB>[2] and let us know what works for
you*. A decision on the team meeting date/time will be posted on Friday, 12
April 2024.

Let’s make this restart a success together! If you have questions, drop a
comment to this post on Fedora Discussion
<https://discussion.fedoraproject.org/t/join-us-restarting-community-ops-team-meetings-in-2024/111336>
[8].

[1] — https://communityblog.fedoraproject.org/restarting-community-ops-2024/
[2] — https://rallly.co/invite/xVPA5fJISpXB
[3] —
https://docs.fedoraproject.org/en-US/commops/contribute/commops-landing/
[4] — https://fedoraproject.org/wiki/Initiatives/Community_Ops_2024_Reboot
[5] — https://fedoraproject.org/wiki/User:Bt0dotninja
[6] — https://fedoraproject.org/wiki/User:Rwright
[7] — https://fedoraproject.org/wiki/User:Jflory7
[8] —
https://discussion.fedoraproject.org/t/join-us-restarting-community-ops-team-meetings-in-2024/111336

-- 
*Cheers*,
*Justin W. Flory* (*he/him*) || 📧 j...@redhat.com || 🔗 jwf.io
*Fedora* Community Architect
TZ=America/New_York (UTC-4) 🕗
*Fedora is a registered Digital Public Good
<https://app.digitalpublicgoods.net/a/10035>*

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
--
___
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: xz backdoor

[Justin W. Flory (he/him)]

More about this is now published on the Fedora Magazine as well in this
statement:
https://fedoramagazine.org/cve-2024-3094-security-alert-f40-rawhide/

Thank you to all of our Fedora first responders who stopped something that
could have been much worse. We should feel proud here. As far as Fedora and
our ecosystem is concerned, the exploit failed.

https://floss.social/@jwildeb...@social.wildeboer.net/112181976426765177

On Fri, Mar 29, 2024 at 2:01 PM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:

> Hi,
>
> wow: https://www.openwall.com/lists/oss-security/2024/
>
> I think at this point we clearly cannot trust xz upstream anymore and
> should
> probably fork the project.
>
> Kevin Kofler
> --
> ___
> 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
>


-- 
*JWF* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗
*Fedora is a registered Digital Public Good
*

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
--
___
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: F38 election results

[Justin W. Flory (he/him)]

Ah! Well, that would explain it… sometimes my timezone math is bad. 😅
Seems everything is on track. Let me know if anything seems amiss with this
election round.

Cheers,
Justin (he/him)
Sent from mobile

On Tue, Jun 13, 2023, 14:46 Miro Hrončok  wrote:

> On 13. 06. 23 15:21, Justin W. Flory (he/him) wrote:
> > The link is working right for me. Try now?
>
> It works now. I believe it was published at 08:00 UTC and I was looking at
> it
> at 07:43 UTC. Your email was sent at 07:00 UTC.
>
> --
> 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://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: F38 election results

[Justin W. Flory (he/him)]

The link is working right for me. Try now?

Cheers,
Justin (he/him)
Sent from mobile

On Tue, Jun 13, 2023, 08:43 Miro Hrončok  wrote:

> On 13. 06. 23 9:00, Justin W. Flory (he/him) wrote:
> > For more details, visit the Community Blog post:
> > https://communityblog.fedoraproject.org/fedora-linux-38-election-results
> > <
> https://communityblog.fedoraproject.org/fedora-linux-38-election-results>
>
> Error 404
>
> --
> 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://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

F38 election results

[Justin W. Flory (he/him)]

Greetings, all! The elections for the Fedora Linux 38 cycle have completed.


*## Fedora Council*

Sumantro Mukherjee is elected to the Fedora Council.

*## Fedora Engineering Steering Committee (FESCo)*

The following candidates are elected to FESCo:

   - Stephen Gallagher
   - Neal Gompa
   - Major Hayden
   - Tom Stellard

*## Fedora Mindshare Committee*

David Duncan is elected to the Fedora Mindshare Committee.


Congratulations to all those elected and thank you to the candidates and
voters. I will process the "paperwork" to update memberships and
documentation over the next 1-2 weeks.

For more details, visit the Community Blog post:
https://communityblog.fedoraproject.org/fedora-linux-38-election-results

-- 
*Cheers*,
*Justin W. Flory* (*he/him*) || 📧 j...@redhat.com || 🔗 jwf.io
*Fedora* Community Architect
TZ=America/New_York (UTC-4) 🕗

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
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: Election Status?

[Justin W. Flory (he/him)]

On Thu, May 25, 2023 at 5:54 PM Gary Buhrmaster 
wrote:

> On Thu, May 25, 2023 at 8:58 PM Justin W. Flory (he/him) 
> wrote:
> >
> > The elections are now scheduled to start on Monday, 29 May and end on
> Sunday, 11 June. Documentation and schedules are being updated.
> >
> > On Thu, May 25, 2023 at 6:55 AM Josh Boyer 
> wrote:
> >>
> >> On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster
> >>  wrote:
> >> >
> >> > I do understand why RedHat itself will not announce
> >> > who got laid off, but the Council members should have
> >> > been informed (I hope!) at the time, and should have
> >> > worked on an announcement to the community, even
> >> > if all they could say was "stay tuned, we are working
> >> > it out".
> >>
> >> The Council members were not informed in advance.  They found out
> >> about the layoffs at the same time the public did, and also found out
> >> about Ben's specific role only after he informed others he was
> >> impacted.
> >
> >
> > This isn't incorrect but I do want to clarify the timeline because it is
> what I would have wanted to know as a community member and there are events
> that may appear to be conflicting in the timeline (e.g. Ben's blog and my
> LinkedIn recommendation for him). We did have some advance notice before
> the general public. Ben mentioned the Red Hat reductions were announced in
> the US on 24 April and that was when we found out. We knew Ben's last day
> was 12 May. That was as much advance notice that we had.
> >
> > The week of 24 April was not productive. It was a shocking week for
> nearly everyone. But we did start transitioning Ben's work before his final
> day and his blog post, which is why you are seeing incredibly helpful
> Fedorans who are stepping up right now and picking up the slack in Ben's
> absence (thank you folks!). There are going to be gaps. Some things will
> fall through the cracks. But we will get through this. Calling out slippage
> as Fedora Council tickets is likely the most effective way for (1) problems
> to be identified and noticed, and (2) for Fedora leadership to take steps
> at resolving those problems.
>
> And, while I can understand that the days
> after April 24th may not have been comfortable,
> and taking advantage of access to Ben while
> he was still available was a good thing, I do
> believe some member of the Council should
> have started working on the note to the
> Community to be sent on (or about) May 15th
> with something of the form that RH's staff
> redundancies have resulted in the elimination
> of the position of Fedora Program Manager,
> and the Council is working through how the
> existing roles and responsibilities of the Council
> will be revised (downwards?), and redistributed
> given the reduction of staffing, and if anyone
> sees something getting dropped, create a ticket
> (properly wordsmithed by someone with actual
> skills in writing words, of course).
>
> I think we all appreciate that everyone is
> stepping up and trying their best.  Thank you!
>
> But I will continue to believe that we(*) should
> not have had to find out about the changes
> when the elections did not happen, which was
> the point of my request that this be taken as
> a learning opportunity about better
> communications for the next time (which
> may have nothing to do with future
> redundancies, as people can leave, or have
> life emergencies, and those can impact
> ongoing activities).
>
> Thank you for your consideration.
>
>
>
> (*) I was aware of it personally because
> it was posted elsewhere, but clearly a lot
> of people seemed to have been surprised.
> I do not believe that should happen.
>
>
I agree that it should not have happened this way.

-- 
*jwf* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
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: Election Status?

[Justin W. Flory (he/him)]

The elections are now scheduled to start on Monday, 29 May and end on
Sunday, 11 June. Documentation and schedules are being updated.

On Thu, May 25, 2023 at 6:55 AM Josh Boyer 
wrote:

> On Wed, May 24, 2023 at 9:34 PM Gary Buhrmaster
>  wrote:
> >
> > I do understand why RedHat itself will not announce
> > who got laid off, but the Council members should have
> > been informed (I hope!) at the time, and should have
> > worked on an announcement to the community, even
> > if all they could say was "stay tuned, we are working
> > it out".
>
> The Council members were not informed in advance.  They found out
> about the layoffs at the same time the public did, and also found out
> about Ben's specific role only after he informed others he was
> impacted.
>

This isn't incorrect but I do want to clarify the timeline because it is
what I would have wanted to know as a community member and there are events
that may appear to be conflicting in the timeline (e.g. Ben's blog and my
LinkedIn recommendation for him). We did have *some* advance notice before
the general public. Ben mentioned
 the Red Hat
reductions were announced in the US on 24 April and that was when we found
out. We knew Ben's last day was 12 May. That was as much advance notice
that we had.

The week of 24 April was not productive. It was a shocking week for nearly
everyone. But we did start transitioning Ben's work before his final day
and his blog post, which is why you are seeing incredibly helpful Fedorans
who are stepping up right now and picking up the slack in Ben's absence (*thank
you folks!*). There are going to be gaps. Some things will fall through the
cracks. But we will get through this. Calling out slippage as Fedora
Council tickets is likely the most effective way for (1) problems to be
identified and noticed, and (2) for Fedora leadership to take steps at
resolving those problems.

-- 
*jwf* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
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: Election Status?

[Justin W. Flory (he/him)]

On Wed, May 24, 2023 at 6:35 PM Tom Stellard  wrote:

> I've filed a ticket here:
>
> https://pagure.io/Fedora-Council/tickets/issue/457
>
>
Thanks Kevin and Tom for getting this flagged as a Council ticket.

-- 
*jwf* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
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: Election Status?

[Justin W. Flory (he/him)]

Hi Gary, hi all,

Thanks for filing the Fedora Council ticket and flagging this. Ben trained
me on the election process and transferred ACLs to me before his final day
at Red Hat. I dropped the ball on continuity. I will run the elections this
round. The timing with Red Hat Summit this week, the F38 release party next
week, and ongoing Flock logistics ended up spilling over.

On Wed, May 24, 2023 at 3:37 PM Tom Stellard  wrote:

> Maybe this has happened and I missed it, but it would nice if the Council
> put
> out a statement acknowledging the position has been eliminated and
> explaining
> what will happen next.
>

Matthew and I were working on something to share with the community and
wanted to publish last week, but for several reasons, it hasn't been
timely. I hope to have more in hand soon.

-- 
*jwf* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
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: The new version of Fedora Messaging Notifications will arrive this week

[Justin W. Flory (he/him)]

Congratulations on the new release, and thanks team for the hard work on
modernizing FMN over the past several months.

On Mon, Apr 24, 2023 at 9:31 AM Aurelien Bompard 
wrote:

> Hi folks!
>
> The "FMN replacement" team has finished writing the new version of our
> notification system, and we are ready to deploy!
>
> We plan on:
> - deploying the new version on https://notifications.fedoraproject.org
> this week,
> - keep the old one around but move it to
> https://apps.fp.o/notifications-old
> - redirect from https://apps.fp.o/notifications to the new place.
> (fp.o being an abbreviation for fedoraproject.org)
>
> You will thus still be able to access the current FMN, and it will
> keep running until F39. Due to the difference in features, we can't
> import existing rules into the new system, so we encourage you to
> create new rules that suit you as soon as the new system is up and
> running.
>
> The change of URLs will happen with the planned outage set for
> 2023-04-24 08:30 UTC (this Wednesday), see ticket 11266
>  for details.
>
> If you have issues with the new FMN, please open infra tickets at:
> https://pagure.io/fedora-infrastructure/new_issue
>
> We hope you will enjoy the simpler UI and faster processing speed that
> the new FMN brings.
>
> Cheers!
> Aurélien
> ___
> 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, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
*jwf* (*he/him*) || 📧 j...@redhat.com
TZ=America/New_York (UTC-4) 🕗

While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
___
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

[2020-10-20] Fedora i3 SIG Meeting Minutes

[Justin W. Flory (he/him)]

4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 
Cheers,
Justin W. Flory (he/him)
https://jwf.io
TZ=America/New_York




OpenPGP_signature
Description: OpenPGP digital signature
___
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

Metrics: Package updates each release and package review time

[Justin W. Flory (he/him)]

Hi all,

CommOps received a request to build metrics for (1) what packages are
updated every Fedora release, and (2) how long on average package
reviews take; however, we do not have capacity to take this request. Per
discussion at Nest, I am following up on Fedora Infrastructure list to
explore if there is capacity elsewhere for this work.

The ticket with this request was opened by Brian Exelbierd in March
2018. The CommOps team first approached this work two years ago, but our
volunteer team does not have capacity to meet this request:

https://pagure.io/fedora-commops/issue/144

At Nest, we briefly discussed with cverna in the CommOps metrics hack
session that this request is more likely a question of which system to
query and how (versus building new tooling or collecting new data).

I was actioned to open a discussion on the Infrastructure mailing list
to explore if this is of interest to the Fedora Packaging community. If
so, the C.P.E. team may be able to redirect this request to the right place.

I am closing the CommOps ticket once I send this mail, but I am happy to
move the request to a new Pagure issue in a different repo if someone is
interested in taking up this request.

Thanks!

-- 
Cheers,
Justin W. Flory (he/him)
https://jwf.io
TZ=America/New_York



signature.asc
Description: OpenPGP digital signature
___
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