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-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, 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

FOSDEM 2023 Distributions Devroom - Call for Participation

[Justin W. Flory (he/him)]

*# **FOSDEM 2023 Distributions Devroom - Call for Participation*

We're excited to announce that the Distributions Devroom is returning to
FOSDEM 2023, in-person in Brussels for the full day on Sunday, February 5.
The call for proposals is now open.


*## About the Distributions Devroom*

The Distributions Devroom is run by and for the people who build, package,
and contribute to distributions of Linux and other software. Distributions
remain a critical part of modern IT infrastructure, whether running on bare
metal or in containers, from supercomputers to edge deployments. The
Distributions Devroom provides a forum to share best practices on the
entire distribution lifecycle, from building and integration to long-term
support and security fixes.


*## Call for Proposals*

We welcome submissions targeted at contributors interested in issues unique
to distributions, especially in the following topics:

* Growing, participating, and working with communities around distributions
* Automating building and testing to minimize human involvement
* Cross-distribution collaboration on common issues
* Distribution construction, installation, deployment, packaging, and
content management
* Balancing new code and active upstreams versus security updates and
minimization of breaking changes
* Delivering architecture-independent software
* Working with vendors and including them in the community
* The future of distributions and emerging trends
* Non-engineering topics inside of distribution communities (e.g.
documentation, marketing, internationalization, design, community
operations, etc.)
* Creating a secure supply chain by evaluating upstream components and
providing a secure source for downstreams


*## Important Dates*

* Submission Deadline: Dec 20th 2022
* Acceptance notifications: Dec 31th 2022
* Final schedule announcement: Jan 14th 2022


*## Process*

1. Register a FOSDEM Pentabarf account[1] and sign in.
2. Visit the FOSDEM CFP[2] and click "Create Event".
3. Make sure "Track" is set to "Distributions devroom" for wranglers to
receive your submission!
4. Complete the form with your presentation details.

Make sure your submission has the following details:

* Title
* One-paragraph abstract
* Longer description including the benefit of your talk to your target
audience, including a definition of your target audience.
* Approximate length / type of submission (talk, BoF, …)
* Links to related websites/blogs/talk material (if any)

[1] https://penta.fosdem.org/user/new_account
[2] https://penta.fosdem.org/submission/FOSDEM23


*## About FOSDEM*

FOSDEM is a free event for software developers to meet, share ideas and
collaborate. Every year, thousands of developers of free and open source
software from all over the world gather at the event in Brussels. FOSDEM
hosts dozens of developer rooms, where community members run tracks on
various topics.

-- 
*Cheers*,
*Justin W. Flory* (*he/him*) ||  j...@redhat.com ||  jwf.io
*Fedora* Community Action & Impact Coordinator
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-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Fedora-spins] Introducing Shells to Fedora spins community

[Justin W. Flory]

Hi Zlatan, welcome to the Spins mailing list! It is good to see you
here. Sounds like you are doing interesting work.

Out of curiosity, have you thought of using existing Fedora Spins or
Editions in Shells.com, such as Fedora IoT Edition, Fedora KDE Spin, or
Fedora i3 Spin?

For packaging help and advice, I recommend checking out the Devel
mailing list. This is the largest mailing list in the project where you
will generally find folks who are more familiar with packaging. I CC'd
the list in my reply.

Let us know if you have any questions for us, or if there is anything
you get stuck on. Again, welcome! :)


- jwf


On 3/22/21 5:43 PM, Zlatan Todoric wrote:
>
> Hello to the entire Fedora community!
>
> Shells (shells.com) started in June 2020 from the founders of Private 
> Internet Access (PIA).  Our goal for our desktop as a service is to close the 
> digital divide by bringing different desktops to the masses, enabling 
> developers to test and build better product
s, and providing a new wave of developers the opportunity to explore a 
different approach to the convergence of their desktops and apps.
> Ease of use (reinstallations take a couple of clicks and less than a minute 
> to finish), free backups via snapshots, and high speeds (500Mbps up/down) are 
> already some of the features available through Shells.
>
> We already have several Linux distros available and more are incoming weekly, 
> and we want to have a polished Fedora experience as well. While we have 
> Fedora on the list, we submitted our trademark request and are working 
> through the details and would like to invite you for further collaboration 
> between Fedora and Shells to create a better Fedora experience and 
> potentially even create a spin!
>
> Relevant ticket:
> https://pagure.io/Fedora-Council/tickets/issue/349
>
> Our Github repositories:
> https://github.com/Shells-com
> https://github.com/Shells-com/linux-scripts/blob/master/oscfg/fedora.sh <- 
> current way of building Fedo
ra
>
> As stated per the ticket and conversations, Fedora kernel is a must for it to 
> be accepted for the trademark, and your assistance will be key as we want to 
> ensure a polished experience (i.e. proper management of disk resize and 
> bootloader, packaging shells-helper, and other default packages). We look 
> forward to any helping us maintain the Fedora OS and being a part of our 
> future as we take virtual cloud computing to the next level!  Thanks!
>
> Kind regards,
> Zlatan (Systems Engineer and Project Manager at Shells)
> ___
> spins mailing list -- sp...@lists.fedoraproject.org
> To unsubscribe send an email to spins-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/sp...@lists.fedoraproject.org
> Do not reply to spam on the
list, report it: https://pagure.io/fedora-infrastructure
>

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


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

i3 Spin staging site now available

[Justin W. Flory]

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/

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.

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

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


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


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

i3 – State of the SIG, January 2021

[Justin W. Flory]

Hi folks, following up on our postponed meeting for today, this is a
short recap of progress on the Fedora i3 Spin as we pick back up after
the new year.

Highlights:

* Status update on ISO builds
* Help wanted with i3 Spin release prep
* i3 package group
* Roadmap and other resources

Full details below.

~jwf



== Status update on ISO builds

Kickstarts are mostly complete. Some decisions are still pending[1], but
these will be finalized before the Completion Deadline (testable)[2] on
2021-02-09.

Next step is to coordinate with RelEng by submitting a Pull Request to
the fedora-kickstarts repo. We hope to have this in advance of the
Completion Deadline so we can organize a Test Day event with the QA team
using officially-built ISOs.



== Help wanted with i3 Spin release prep

The i3 SIG is looking for help to prepare for the F34 release. Two good
issues for newcomers are to help us take screenshots[3] and write an
elevator pitch[4] of the Spin. Th
ese will be used on the Fedora Spins
website[5].

We are also looking for help with workflows to release our kickstarts
and submit them downstream to the fedora-kickstarts[6] repo. For more
info, see the i3 SIG ticket[7].



== i3 package group

Additionally, we are also working on a new package group to land in time
for the Software String Freeze on 2021-01-26. A list of proposed
packages can be found in the i3 SIG documentation[8].



== Roadmap and other resources

Follow the progress of the Fedora i3 Spin on our Pagure Roadmap[9].
Currently we are on track for Fedora 34, but we could always use help
from enthusiastic early adopters to help us prep for release day.

That's all! We'll use this email recap as a starting point on our next
text meeting on 19 January 2020 at 16:00 UTC in #fedora-i3 /
#fedora-i3:matrix.org.



[1]  https://pagure.io/i3-sig/Fedora-i3-Spin/issue/26
[2]  https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
[3]  htt
ps://pagure.io/i3-sig/Fedora-i3-Spin/issue/30
[4]  https://pagure.io/i3-sig/Fedora-i3-Spin/issue/31
[5]  https://spins.fedoraproject.org/
[6]  https://pagure.io/fedora-kickstarts
[7]  https://pagure.io/i3-sig/Fedora-i3-Spin/issue/29
[8]  https://docs.fedoraproject.org/en-US/i3/package-groups/
[9]  https://pagure.io/i3-sig/Fedora-i3-Spin/roadmap

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


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


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

Any interest? ButterManager and grub-btrfs

[Justin W. Flory]

Hi all!

ngompa and I were talking to the upstream maintainer of the
ButterManager backup tool about packaging for Fedora. Upstream is ready
to collaborate on a RPM spec file if there is an interest in packaging
for Fedora:

https://twitter.com/eloygara/status/1344006727583330305

https://github.com/egara/buttermanager

https://github.com/Antynea/grub-btrfs

The maintainer is willing to work with someone on a package and possibly
host it upstream:

https://twitter.com/eloygara/status/1344309377101164546

There is interesting functionality for Btrfs snapshots here. The idea of
being able to jump into any given system snapshot from the GRUB boot
menu is appealing to me. :-)

Neither Neal or I have time to pick these up as new packages, but I
wanted to share the package on devel@ in case anyone were interested in
bringing this to Fedora users now that Btrfs is the default filesystem.

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


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


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

F34 comps groups addition: i3, i3-extended

[Justin W. Flory]

Hi all,

I am looking for feedback and review on fedora-comps#569, which adds new
package groups, an environment, and category for the i3 window manager:

https://pagure.io/fedora-comps/pull-request/569

This is the first time I have made edits to the comps file. So a sanity
check to make sure I did this right for a new desktop environment would
be helpful, especially about inheriting the right set of default packages.

This matches the drafted package group as found in the Fedora i3 SIG's
package groups:

https://docs.fedoraproject.org/en-US/i3/package-groups/

Per the documentation for comps, I wanted to use this thread as a way to
get feedback on the change before it gets merged.

Thanks!

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


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


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

Re: main vs master: no more localization :(

[Justin W. Flory]

Hi Jean-Baptiste,

On 12/8/20 6:06 PM, Jean-Baptiste wrote:
> 
> Hello,
> 
> our localization system, for every single doc component is broken.
> 
> The reason is the change of branch from "master" to "main".
> 


I do not understand how this happened. Only a handful of Fedora Docs
repos have switched from `master` to `main`. Did the changing of a few
repos have an impact on the translations build script? If so, which
repos specifically caused localization to break?


> the question I have: how could we have better testing of changes?
> 
> 
> Thanks for your understanding,
> 


I am still confused how it happened. If any docs repo can break the
localization tooling by changing the default branch, this seems like a
bug with the tooling. Right now, no mass branch renames have happened
yet, although this is planned in the near future:

https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main


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


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


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

Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)

[Justin W. Flory]

Sounds to me like good opt-out documentation is in order. 


\--
Cheers,
Justin W. Flory (he/him)
https://jwf.io
Sent from ProtonMail mobile




\ Original Message 
On Nov 24, 2020, 09:19, Joël Krähemann < jkraehem...@gmail.com> wrote:
Hi all,
For short, NO! I want to be able to shutdown pipewire in order to get instant
ALSA access.
This was a real pain until pulseaudio recognized what they need to do:
systemctl --user stop pulseaudio
systemctl --user stop pulseaudio.socket
killall pulseaudio

Didn't look at pipewire, yet. Finally, please consider to shutdown the
process completely as desired.

publickey - EmailAddress(s=foss@jwf.io) - 0x570E854F.asc
Description: application/pgp-keys


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

[2020-10-25] Møte (meetbot.fp.o) developer meeting notes and recording

[Justin W. Flory]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi all,

Today, the Fedora Møte team met for one-hour on a Jitsi call. We set up
development goals and began splitting up the backlog for two-week
sprints. A video recording is below:

https://youtu.be/gpLPDgYRIvA

Some highlights from our meeting:

* Five high-level goals for Møte:
1. Full support for Python 3
2. Convert simple Flask site to a full web app with FE/BE component
3. Mobile support for responsiveness (no refreshing the full D.O.M.)
4. Fully-automated deployment for new updates
5. Continuous integration testing for developers

Some of these things are partially done already, but need additional
follow-up (e.g. Py3 support, CI testing pipeline).

We are using a GitHub Project Board on github.com/fedora-infra to track
and measure our sprints:

https://github.com/orgs/fedora-infra/projects/8?fullscreen=true

Interested in joining the team? Find us in #fedora-mote on Freenode IRC
or join us on Element/Matrix:


https://matrix.to/#/!gbiuxNuMUuCiOywHsr:mozilla.org?via=matrix.org=mozilla.org=t2bot.io

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

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wmgEARYIABAFAl+Vr/cJEBa1xZdT1mbAAAoJEBa1xZdT1mbA8u8BAL2At4kg
2qUCMZ3M7Q83Im1gdUxiqkBEv8lefR2nx0ybAP9872echdYTwd5XbX2/NE67
6z0+bzYd4Uacnqv0VcrmDg==
=vU6T
-END PGP SIGNATURE-


publickey - foss@jwf.io - 570e854f.asc
Description: application/pgp-keys


publickey - foss@jwf.io - 570e854f.asc.sig
Description: PGP 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

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

[Justin W. Flory (he/him)]

`: 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

Re: Fedora 32 System-Wide Change proposal: Drop Optical Media Release Criterion

[Justin W. Flory]

> Kamil wrote:
> 
> This has been a long discussion. Let me sum up some answers and
> misunderstandings, as a member of the QA team.
> 

Hey Kamil, I wanted to say thanks for adding this perspective. I missed this 
post in my last reply because there are a lot of posts. I learned a lot about 
Fedora QA reading this just now. :)

> To reply to Justin Flory about Fedora Mindshare Committee - I think this is
> more of an engineering decision, really. Of course you'll find users who
> will want optical boot 100% supported (and that's true probably about
> anything). The question is how much testing we can provide and whether we
> want to block the whole release train on such issues, and that's likely
> just an engineering prioritization. Of course it's good to have user
> feedback.
> 

I think I misrepresented my point by mentioning the Mindshare Committee 
specifically. Instead of it being exclusively an engineering decision, can it 
not be an engineering and community decision? By raising the importance of 
user/community feedback, I don't mean to undermine engineering feedback and 
discussion. But in this specific area (i.e. hardware changes), Fedora has not 
done a good job engaging regions of the world that often have vastly different 
standards of consumer-grade hardware.

This might not affect people **using** Fedora for enterprise purposes but it 
does impact the ability of people like volunteers to **access** Fedora on their 
own machines, especially when contributing guidelines across Pagure projects 
often assume the reader runs Fedora. I think we undervalue the role of older 
consumer hardware because we look at it from an enterprise-demands P.O.V. A lot 
of the feedback that comes into Fedora comes from that perspective. 
Consumer-grade hardware varies more and not everyone has access to the same set 
of resources.

If it feels like I'm harping, it is because there are already some frustrations 
in the non-engineering parts of the Fedora community and my concern is that 
this Change would be one more loss for the volunteer community. For 
perspective, we have existing communities of people in regions who could be 
adversely affected by this Change:

https://communityblog.fedoraproject.org/tag/latam/

https://communityblog.fedoraproject.org/tag/india/

> Regarding Miro Hrončok's proposal "let QA skip testing, but block on it if
> somebody else finds the problem" - yes, it's possible. QA is by definition
> best effort, even though we've considered a full test matrix coverage
> somewhat mandatory lately. We do practice this approach for many criteria
> for which we don't even have test cases written. In terms of boot support,
> though, I'm not particularly fond of it. Without regular QA testing, this
> will have a tendency to get discovered very shortly before Final release,
> and then people will be just mad at QA for not detecting it sooner.
> 

Is it absurd if it blocked an N+1 release? I don't have enough perspective if 
this could reduce the pinch point around a release day while also still 
validating the importance of these issues to the community.

Alternatively, this could make the requirements too complex where few people 
remember this rule in practice.

> If anyone wants to make sure optical media breakage doesn't happen -
> please, help us. We announce new candidate composes in test-announce list
> regularly. Download the image, burn it, install it, and fill out the
> correct field in the installation matrix. Do this from time to time during
> pre-branching period, and regularly for every proposed Beta and Final
> release candidate. We'll be very grateful. And that is independent on
> whether optical media keep being blocking or are no longer blocking. The
> test feedback is always helpful. And if the bugs are on our radar, we'll do
> our best to have them resolved by the final release day.
> 

I wonder what a way of handing these tests off to the community (with some 
guidance from Fedora QA team) might look like.
___
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 32 System-Wide Change proposal: Drop Optical Media Release Criterion

[Justin W. Flory]

> Miro Hrončok wrote:
> 
> The devel list is the first place where developers gather feedback. The idea 
> to 
> reach a committee (whether FESCo or Mindshare) before reaching to devel is 
> hence 
> entirely wrong in my opinion. Committees should rubber stamp community 
> decisions, not drive them.
> 

I agree that committees should not drive decisions. I did not mean to undermine 
the role of the Devel list in discussing technical ideas and getting wider 
feedback from the development community. I guess there is not an easy 
equivalent of the Devel list to Fedora's non-engineering community.


> As for users communities, yes, that is a good idea. However, so is first 
> discussing this within the engineering contributors community and only once 
> there is a consensus, involve advocacy / user communities for more feedback.
> 

Is there a plan or process for collecting advocacy / user community feedback 
for more feedback?

My concern is this step will not be deemed critical or important enough, and it 
will be glossed over. I'm not opposed to development discussions, but I don't 
see where user community feedback fits into the existing Change process. Maybe 
I am missing something obvious.


> Hence, I disagree with what you say - discussing this on the devel list first 
> is 
> the best thing to do IMHO.

This is not how I wanted to represent my position. I'm sorry to have made it 
appear that way.


> Adam Williamson wrote:
> 
> There is no "why" behind this Change "other than eliminating an
> admittedly tedious task for the QA team". That's the whole thing. There
> aren't any "private RH BZ customer tickets". Why would RH customers
> care about whether or not Fedora blocks on physical optical media
> booting?

The QA team has increasing demands for the ways Fedora is changing, and I also 
understand how optical drives are not part of those increasing demands. But to 
me, there is an opportunity to find a middle ground approach that reduces the 
work for the QA team without causing panic and fear in user communities in 
Global South communities that optical drives will be unsupported.

Also I'm sorry about the "private RH BZ customer tickets" comment. Sometimes I 
am a little jaded as a community volunteer because there are some decisions 
made that I cannot always understand or follow. It was distracting for me to 
mention it here in this discussion and I didn't intend to make a jab.


> Adam Williamson wrote:
> 
> If there are all these thousands of people out there who care deeply
> about the optical media...wouldn't it be nice if some of them turned up
> and helped run the tests once in a while?
> 

It would be nice, but this assumes a lot of the people who are most affected. 
Contributing to Fedora in free time is a privilege. Some companies strictly 
forbid employees from contributing to open source despite using it. Using 
presence of unpaid volunteers as a metric of engagement and interest does not 
match up to me.

That said, I think there is opportunity to improve in attracting contributors. 
If it is important to continue the optical drive validation work, it would be 
cool to see Test Day events or a page in the Fedora Docs sites about how to run 
through the QA tests for optical drive validation. We could rally more people 
to do these things but we have not made a good-faith attempt yet at reaching 
those people and inviting them to the table. I'm not sure where to find this 
test case information myself!


> Very very rarely. As Chris Murphy wrote, by pure coincidence one showed
> up the day before yesterday (to be clear, it has nothing at all to do
> with this Change proposal, the proposers of the Change were not aware
> of that bug until well after the Change was submitted). Before that the
> last time I can find, by searching my Bugzilla mail box for relevant
> words at least, is 2015:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1250440
> 
> the last time we had a *fatal* issue that I can find is 2014:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1148087
> 
> Note, the testing isn't *hard* to do, really, it's just tedious and
> time consuming. Not just the act of running the test (though that does
> take quite a while, between the burning process and the boot, media
> check and install itself), but the fact that it means we need to ensure
> we have at least a couple of people who still have access to a DVD
> burner and blank media.

I'm warming up to an idea that focuses on empowering the community to lead this 
work in a sustainable way without mandating the QA team to test these every 
release. If I could suggest first steps to one way to "hand-off" to the 
community, it might be like this:

1. Publish "Fedora QA test cases" somewhere in the Fedora Docs site for QA: 
https://docs.fedoraproject.org/en-US/qa-docs/
2. Write test cases based on the manual work done currently and how to validate 
success; publish in docs site
3. Write Community Blog post to point out to 

Re: Fedora 32 System-Wide Change proposal: Drop Optical Media Release Criterion

[Justin W. Flory]

Hi all,

I was surprised to see this Change be proposed without engagement with the 
Fedora Mindshare Committee or reaching out to the advocacy / user communities 
for more feedback. There are a lot of people this Change could impact and I am 
concerned many of those voices are not represented in this discussion or on 
this list.

Is there any data or supporting evidence to support back this Change? Other 
than private RH BZ customer tickets? I am really curious to know the "why" 
behind this Change other than eliminating an admittedly tedious task for the QA 
team to perform. I am thinking about this from two points-of-view:


(1) This change affects people differently in different regions of the world

The Fedora community has large user and contributor communities all over the 
world. Historically, our Ambassadors/Advocates relied on DVD media in these 
regions to install Fedora and promote it at events, because there is not always 
reliable, consistent Internet connection in parts of these regions. 
Additionally, the hardware that exists in these regions is often 
previous-generation hardware that does not mirror the same hardware advances in 
the West.

Without more data on DVD media usage to support this Change, I am concerned of 
the impact of this Change on Fedora user and advocacy communities that may 
still rely on this as a vital deliverable to support their community work in 
promoting Fedora globally.


(2) USB media were always turned down in the Fedora budget requests for 
Ambassadors/Advocates throughout the last decade.

In the Ambassador/Advocate community, there are volunteers from North America / 
Europe who advocated for Fedora USB keys for years. Throughout my five or six 
years in Fedora now, these requests from the community were always turned down 
because of cost. If memory serve me correctly, the cost of mass-producing USB 
media for our community was $100s of USD, if not $1000s, more.

So, the other consequence of this Change could be that we leave a lot of people 
doing valuable community work behind, because DVD media is no longer release 
blocking and Fedora community advocates can't get USB keys funded. (Except, 
somehow, Fedora-branded USB keys were acquired for past FOSDEM events, I don't 
remember seeing this decision work its way through the community though.)

From a non-engineering / Fedora community perspective, I am strongly -1 to this 
proposal without more data to support this. I think a better approach to inform 
this decision is to collaborate with the Mindshare Committee on collecting 
feedback from the wider community about this Change. Holding it here on this 
mailing list is not enough because only the most active, most passionate people 
are likely to join this discussion.


> Juts a random idea, not very thought-out:
> 
> Could we keep optical media bugs reported by users as blocking, but not 
> require 
> it during validation testing?
> 
> 
> aka: Fedora QE would no longer have to verify optical media works.
> but: If a tester finds an optical media  bug, it is still blocking.
> 
> That would still have 2 of the 3 listed benefits. The remaining benefit is 
> arguable (is optical media a corner case? there are no corners on DVD).

For what it's worth, I like Miro's idea a lot but also haven't thought about it 
extensively. I think this could prioritize these issues as release-blocking 
when we don't have enough data to understand the impact of this Change, but it 
also saves a lot of time and effort on the QA team for shipping releases to 
focus on other things. Another piece of feedback I'd be interested to know is 
how often serious issues do come up when testing optical media, or if the issue 
is that it is just a lot of manual work that is hard to do.

Some of my 2¢.
___
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: Introduction for gaming packaging/maintaining

[Justin W. Flory]

On 4/8/19 1:32 PM, Karsten Andreas Artz wrote:
> Hi guys,
> 
> my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2
> years (Fedora 26). My programming skills are on Python, Java/Java
> Script, and C/C++. But acutally I prefer mostly Python hacking. I
> studied B.A. of Arts History, Archaeology and Cath.Theology. Besides
> this, I can speak a lot of languages: German, English, French, a bit
> Italian and Spanish.
> 
> It would be glad starting contributing on Fedora as a maintainer.
> Therefore I hope to work on a small project soon.
> I'm interested in games packaging, but I don't know where to start.
> 

Hi Andi, welcome to the mailing lists. :)

The Games SIG is a good place to find more information about what help
is needed to improve the gaming experience on Fedora. In the past couple
months, there were a few discussions from people needing help on a few
small things. Hopefully someone more informed than me can offer some
pointers since I am not a games packager.

Happy to have you here in the community!

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



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://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

Fwd: white_dune fedora sponsoring

[Justin W. Flory]

This came to the Games SIG mailing list owner address. Cross-circulating
this post a bit:


On 12/24/18 7:29 AM, J. Scheurich wrote:
> Hi,
> 
> I need fedora sponsoring for white_dune
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1658153
> 
> | Games SIG might be interested.
> 
> white_dune is a tool for creating VRML/X3D.
> 
> Beside general 3D data, VRML/X3D can be used in webgl browser games.
> white_dune has support for programming VRML/X3D with JavaScript like in
> this example:
> 
> https://wdune.ourproject.org/examples/warbird.html
> 
> so long
> MUFTI

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

fedora-bookmarks: Four PRs needing review

[Justin W. Flory]

Hi all, could a maintainer review these four PRs on the fedora-bookmarks
package?

https://src.fedoraproject.org/rpms/fedora-bookmarks/pull-requests

It would be cool to see these merged. I'm not sure what the process is
for requesting review on PRs in dist-git.

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



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://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

Say thanks during Fedora Appreciation Week (Nov. 5-11)

[Justin W. Flory]

This year, the first-ever Fedora Appreciation Week will run from Monday,
November 5th to Sunday, November 11th. Fedora Appreciation Week is an
annual event organized by the Fedora Community Operations (CommOps)
team. It’s a week-long event to celebrate efforts of Fedora Project
contributors and to say “thank you” to each other.

This year, the Appreciation Week runs during the fifteenth anniversary
of the Fedora Project. The Fedora Project has changed in many ways since
2003, but not the importance of our contributor community. This is a
week to celebrate the friends, colleagues, and contributors who are part
of this fifteen-year open source saga. Learn more about the event here.

https://fedoramagazine.org/say-thanks-appreciation-week-2018/

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@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

Say thanks during Fedora Appreciation Week (Nov. 5-11)

[Justin W. Flory]

This year, the first-ever Fedora Appreciation Week will run from Monday,
November 5th to Sunday, November 11th. Fedora Appreciation Week is an
annual event organized by the Fedora Community Operations (CommOps)
team. It’s a week-long event to celebrate efforts of Fedora Project
contributors and to say “thank you” to each other.

This year, the Appreciation Week runs during the fifteenth anniversary
of the Fedora Project. The Fedora Project has changed in many ways since
2003, but not the importance of our contributor community. This is a
week to celebrate the friends, colleagues, and contributors who are part
of this fifteen-year open source saga. Learn more about the event here.

https://fedoramagazine.org/say-thanks-appreciation-week-2018/

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Re: Picard Version 2.0.3 is available

[Justin W. Flory]

On 10/14/18 12:49 PM, Gerald B. Cox wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1603193
> 
> Hello, this record has been open since July with no response from the
> maintainer.  I'm not actually sure if this has dedicated maintainer or
> is just reliant on proven packagers.
> 
> Another user has even provided a spec file which builds fine, so it's
> not like it will take alot of time to push the update.
> 
> If no one wants to build it, someone please give me access and I'll
> submit the build.
> 
> Thanks!
> 

I am happy to help someone test this package. I would really like to see
this package updated. :)

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



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://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: [commops] Re: Introduction

[Justin W. Flory]

Some examples of C projects in Fedora:

https://wiki.gnome.org/action/show/Projects/OSTree

http://www.freedesktop.org/wiki/Software/systemd/

http://cockpit-project.org/

http://www.gnome.org/gnome-3/source/

I mostly picked these examples from this page:

https://whatcanidoforfedora.org/en#coding#c

But I've also added the Fedora development list in case anyone else has
better examples of C/C++ projects in Fedora than what I am familiar
with. Someone else may also chime in with more info than what I have. :-)

On 06/10/2018 03:36 PM, Alexander Marek wrote:
> To whom it may concern,
> 
> Is there any opportunities to do C++ or C coding as well with the fedora 
> project? I'm looking to beef up my knowledge of the language through 
> experience.
> 
> Regards,
> Alexander Marek
> 
> Sent from my iPhone
> 
>> On Jun 10, 2018, at 4:32 PM, Justin W. Flory  wrote:
>>
>>> On 05/08/2018 08:35 AM, Alexander Marek wrote:
>>> To whom this may concern,
>>>
>>> My name is Alex and I'm studying Cybersecurity, with plans to go into
>>> the IT/Information Security field. Recently I've been studying for my
>>> Red Hat Certified System Administrator certification and hope I can
>>> bring my new skillset to help benefit my favourite distribution. I plan
>>> to pass my Offensive Security Certified Professional certification by
>>> the end of August. Alongside this, I'm currently taking college courses
>>> part time.Hopefully I can be useful, and I'm looking forward to seeing
>>> what the Fedora Project has in store!
>>>
>>
>> Hi Alexander! Thanks for your patience on a reply. Welcome to the Fedora
>> Project! We're happy to have you here with us.
>>
>> It sounds like you have a solid background in infrastructure management
>> and IT. Have you considered checking out the Infrastructure Apprentice
>> program? It seems like the opportunities to contribute there are more in
>> line with your skills.
>>
>>https://fedoraproject.org/wiki/Infrastructure
>>
>>https://fedoraproject.org/wiki/Infrastructure/GettingStarted
>>
>>https://fedoraproject.org/wiki/Infrastructure_Apprentice
>>
>> I've added the Fedora Join mailing list to this reply. If you have
>> further questions about getting involved and making a first
>> contribution, I recommend asking there.
>>
>>
>> https://lists.fedoraproject.org/admin/lists/fedora-join.lists.fedoraproject.org/
>>
>> Hoping to see you around in the community!
>>
>> -- 
>> Cheers,
>> Justin W. Flory
>> jflo...@gmail.com
>>
> ___
> Fedora Community Operations (CommOps) mailing list -- 
> comm...@lists.fedoraproject.org
> To unsubscribe send an email to commops-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/comm...@lists.fedoraproject.org/message/SS32UUAEQBRGPW5FSFNDA5OU7AHWFJZ7/
> 

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



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://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/U6REKX6JZNVIZWOJ3AUYTJME4SYORUMD/

Interviews on the Fedora Infrastructure Hackathon 2018

[Justin W. Flory]

Hi all!

This week, the Fedora Infrastructure team is convening for a Hackathon
from April 9-13 at Fredericksburg, VA. The hackathon is intended to help
the team leap ahead for several critical Fedora and CentOS initiatives.
Dennis Otugo, a member of the CommOps team, interviewed members of the
Fedora Infrastructure team to ask what the goals for the hackathon are
and why it is needed.

Read more on the Community Blog:


https://communityblog.fedoraproject.org/fedora-infrastructure-hackathon-2018/

Thanks Dennis for putting the interview together, and thanks to the
interviewees for their answers on short notice. :-)

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [games-sig] Re: Can we revise the games packaging guidelines wiki page?

[Justin W. Flory]

On 03/28/2018 02:21 PM, Michael Thomas wrote:
> On 3/28/18 1:17 PM, Artur Iwicki wrote:
>> I took a look at "SIG/Games/Packaging" page [1] on the Fedora wiki, and it 
>> seems to be quite old - the revision history says the last edit was made in 
>> May 2008, which places it at close to 10 years old.
>> Could we possibly revise the packaging guidelines to make sure they don't 
>> contradict the general guidelines - and if they do, have a clear "yes, this 
>> contradicts the main guidelines, do it either way" message?
> 
> I'd be happy to make any changes needed if folks point them out.
> 

I am +1 to making modern revisions to this SIG's guidelines, but I am
unable to offer much technical insight for these changes.

In May 2008, Windows XP / Vista were in wide use, Steam was not yet in
the eye of the mainstream gaming world, and Fedora was approaching five
years old. A lot of things in technology, gaming, and Fedora have
changed since May 2008. :-)

The best way to move forward, as I see it, is to draft proposed /
revised changes. If you have a draft with proposed changes, it is easier
to collect feedback on those changes. I am not much of a packager, so I
cannot contribute much technical insight. However, I am happy to help
gather feedback and formally adopt any new guidelines, once a draft is
ready.

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Council Elections - July/August 2017 - Result announcement

[Justin W. Flory]

On Wed, Aug 16, 2017, Jan Kurik wrote:
> I do not see the conflict of interests here. Justin is one of
> volunteers (for several election cycles already) who contacts all
> candidates at the beginning of Campaign period providing them with
> instructions how to work with CommOps team to publish their
> interviews. I really do not think that people helping with
> administrative work behind elections should be punished by their
> exclusion from nominations.
> 
> Anyone in the community can add a question into the questionnaire
> during the nomination period. And it is free will of a nominee which
> questions he/she answers in the interview.
> 

Hi all,

Thanks for your interest in the election process – I appreciate everyone
that has offered constructive feedback on ways to improve the election
process. Together with Jan, this is something that CommOps has been
trying to help assist with and promote more engagement and interest in
the elections.

The questionnaire process is open for the community to add their own
questions for candidates during the election process on the wiki. As
with previous release cycles, CommOps helps create HTML interview
templates to make it easier for candidates to answer the questions and
get their interviews posted. This happened in this PR:

https://pagure.io/fedora-commops/pull-request/113

Once the campaign period started, I checked for any new questions, then
merged the PR and personally emailed the templates to all candidates.

There was a lot of feedback and comments about ways the Election app
could be improved as well.

https://pagure.io/elections

After talking with some members of the Infrastructure team, hopefully
after this election cycle ends, a newer version of the Elections app
with an improved design a few other things will be online in time for
the next election. However, there's still a lot of work that needs to be
done. There are a few issues already filed, including…

* Add support for Fedora Badges (in the same style as Nuancier)
* Nominate candidates from Elections app
* Submit questionnaire questions from Elections app
* Add eligibility checks for candidates

This isn't comprehensive, but if you have suggestions, please feel free
to file an issue in the meanwhile:

https://pagure.io/elections/issues

Or better yet, if you'd like to help with development on this project,
there's definitely a strong need for some improvements that could have a
significant impact on overall engagement, interest, and participation in
the elections. For a start, it could probably use some love to move over
to Python 3. :)

Thanks again for everyone that has offered constructive feedback on the
elections!

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Warning before sudo pip'ing?

[Justin W. Flory]

I'm not a member of the SIG, but as someone who did this in the past
before learning proper practices, I would find this *extremely* helpful,
especially when running certain software that explicitly tells the user
to run this, even with it being bad practice.

A big +1 from me…

On 02/10/2017 07:31 PM, Neal Becker wrote:
> Having been badly burned by sudo pip install in the past, I agree that a
> warning is appropriate, with a suggestion to use pip install --user
> 
> On Fri, Feb 10, 2017 at 1:28 PM Tomas Orsava <tors...@redhat.com
> <mailto:tors...@redhat.com>> wrote:
> 
> Hi!
> On the last FESCo meeting while discussing the sudo pip Fedora [Change],
> maxamillion proposed that it might be useful to issue a warning when a
> user tries to run pip with root privileges--as in most cases it's not
> what they should be doing (`pip install --user` is usually more
> appropriate).
> 
> What do you think?
> 
> [Change] https://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe
> 
> Regards,
> Tomas Orsava
> ___
> python-devel mailing list -- python-devel@lists.fedoraproject.org
> <mailto:python-devel@lists.fedoraproject.org>
> To unsubscribe send an email to
> python-devel-le...@lists.fedoraproject.org
> <mailto:python-devel-le...@lists.fedoraproject.org>
> 
> 
> 
> ___
> python-devel mailing list -- python-devel@lists.fedoraproject.org
> To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
> 

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org

Re: Python 3.6 beta release in F26 Rawhide?

[Justin W. Flory]

On 10/17/2016 10:57 AM, Nick Coghlan wrote:

On 18 October 2016 at 00:49, Charalampos Stratakis <cstra...@redhat.com> wrote:

The current URL should be https://beaker.qa.fedoraproject.org/ if that is the 
one you have in mind.


Indeed it is, thank you!

Cheers,
Nick.



Hi everyone, I'm observing and chiming in late to this discussion. My 
understanding from reading this thread is that it's intended to package 
3.6 for Rawhide and eventually having it made as a Change in F26.


If 3.6 is going to be hitting Rawhide, would anyone be interested in 
writing an announcement / tips for testing on the Fedora Magazine? I 
think this would be a highly-interesting article to our readers to know 
that 3.6 is in Rawhide, and there may be some people who are willing to 
jump in and help test if they knew the opportunity was there.


Thanks everyone!

--
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org

Re: Python 3 porting: 50% done in Rawhide 

[Justin W. Flory]

On 08/11/2016 09:48 AM, Petr Viktorin wrote:

Hello,
As of now, http://fedora.portingdb.xyz shows that we are 50% done
porting Fedora packages to Python 3. This is a big magic milestone; if
you're looking for a reason to celebrate, this is it! :)


Meanwhile, let me talk about what the number means and what the next
steps are.
50% packages are "done" in Rawhide. "Done" is defined as either
"Released"/"green" (packages that are either py3-only, or have py3 and
py2 variants packaged), or "Dropped"/"gray" (package won't be ported,
but there's a py3-compatible alternative packaged in Fedora -- for
example: "python" is dropped because "python3" is available;
"python-numeric" is dropped in favor of "numpy" even though the API s
are different).

The classification of "green" packages is mostly automatic, and it's not
perfect -- for example, python-twisted is green even though not all of
the submodules are ported yet, and nothing checks if the packaged py3
versions actually works. For cases when there's a problem with the
automatic process, manual overrides or notes can be put in
[fedora-update.yaml].

Portingdb tracks Rawhide; Fedora 25 is currently missing about 4
packages to get to 50%. It might very well get to 50% before the release.


Now, what's next?
I can't speak for everyone involved, but at Red Hat's python-maint team,
we'll tone down the focus on getting as many packages ported as
possible. This led to us picking the low-hanging fruit, which is better
left to people that are just getting started. We'll be around to answer
questions, provide hints, and otherwise help others get the badges
instead of stealing them for ourselves :)

Instead, we should shift our focus from porting specfiles to upstream
projects. At this point, if some software is easy to port it was
probably ported already; what we're left with are either tough nuts to
crack or projects with few people relative to the codebase size. Some
projects that come to mind that could use attention are GTK, Mercurial,
Samba, wxPython, PySide, Koji & Fedora infra, Ansible.
I don't know yet what our priorities should be here, but that's the
general direction.

But even if it won't be *our* focus, RPM porting is still open – you can
[contribute] toward the remaining 50%! Badges are waiting :)


[fedora-update.yaml]
https://github.com/fedora-python/portingdb/blob/master/data/fedora-update.yaml

[contribute] http://fedora.portingdb.xyz/howto/



Hi Petr! This is an awesome update to hear!!

Do you mind if I copy+paste this as a post into the Community Blog 
as-is? If you are able to log in [1] to the CommBlog, I can assign 
authorship credit to you (if you haven't signed already before).


Congrats team on the 50% milestone!!!


 [1]  https://communityblog.fedoraproject.org/wp-login.php

--
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org

Fedora Elections July 2016 - Voting now open

[Justin W. Flory]

The Campaign period of Elections for the Fedora Council and Fedora 
Engineering Steering Committee (FESCo) are now over. As of this morning, 
voting is now open.



== Candidate Interviews ==

There is one seat open on the Fedora Council (contested by two 
candidates) and four seats open on FESCo (contested by five candidates). 
Most candidates have published their platforms and answered questions 
from the official Questionnaire form on the Community Blog.


For your convenience, you can read this post, which lists all of the 
candidates and links to their interview (if applicable).



https://communityblog.fedoraproject.org/2016-july-elections-interviews/

Please take a moment to review the post as you prepare to vote.


== Eligibility ==

Both the Fedora Council and FESCo have different eligibility requirements.

* Fedora Council: Requires Fedora account (FAS), signed the CLA agreement
* FESCo: Requires Fedora account, signed the CLA agreement, member of 
one other "non-CLA" group in FAS


Voting takes place in the Elections application:

 https://admin.fedoraproject.org/voting/


== Voting ends: 2016 July 25, 23:59 UTC ==

Voting ends promptly on Monday, July 25, 2016, at 23:59 UTC. Voting will 
then close and candidates will be announced thereafter.


For more information about the voting process, you can review the wiki 
page for Fedora Elections.


 https://fedoraproject.org/wiki/Elections



Best of luck to all candidates running! For all voters, make sure you do 
get your vote in and participate in helping elect members of Fedora's 
leadership bodies.


--
Cheers,
Justin W. Flory
jflo...@fedoraproject.org





signature.asc
Description: OpenPGP digital signature
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproject.org

Fedora Elections July 2016 - Voting now open

[Justin W. Flory]

The Campaign period of Elections for the Fedora Council and Fedora 
Engineering Steering Committee (FESCo) are now over. As of this morning, 
voting is now open.



== Candidate Interviews ==

There is one seat open on the Fedora Council (contested by two 
candidates) and four seats open on FESCo (contested by five candidates). 
Most candidates have published their platforms and answered questions 
from the official Questionnaire form on the Community Blog.


For your convenience, you can read this post, which lists all of the 
candidates and links to their interview (if applicable).



https://communityblog.fedoraproject.org/2016-july-elections-interviews/

Please take a moment to review the post as you prepare to vote.


== Eligibility ==

Both the Fedora Council and FESCo have different eligibility requirements.

* Fedora Council: Requires Fedora account (FAS), signed the CLA agreement
* FESCo: Requires Fedora account, signed the CLA agreement, member of 
one other "non-CLA" group in FAS


Voting takes place in the Elections application:

 https://admin.fedoraproject.org/voting/


== Voting ends: 2016 July 25, 23:59 UTC ==

Voting ends promptly on Monday, July 25, 2016, at 23:59 UTC. Voting will 
then close and candidates will be announced thereafter.


For more information about the voting process, you can review the wiki 
page for Fedora Elections.


 https://fedoraproject.org/wiki/Elections



Best of luck to all candidates running! For all voters, make sure you do 
get your vote in and participate in helping elect members of Fedora's 
leadership bodies.


--
Cheers,
Justin W. Flory
jflo...@fedoraproject.org





signature.asc
Description: OpenPGP digital signature
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Request for Review: Python marketing brochure

[Justin W. Flory]

Hello all,

Brian (bprofitt / bkp) recently helped finish the final proposed version 
of the brochure we plan to use in the field for quick information about 
Fedora + Python.


If some Pythonistas could help review the brochures and make sure the 
content checks out and sounds good, your help would be appreciated!


You can find the latest copies of the brochure in this ticket.

https://fedorahosted.org/marketing-team/ticket/219

To help prevent communications from being lost in cross-posted mailing 
lists, if anyone who is able could give a +1 / -1 in the ticket, that 
would be appreciated! Thanks all.


--
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
python-devel mailing list
python-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org

Re: [Marketing] Help Getting Started - Python Talking Points and Meetings

[Justin W. Flory]

Hi James,

On 03/18/2016 03:41 PM, James Bishop wrote:

Hi Justin

The biggest question I have right now is whether I need to be a part of
the marketing group to log in to the other sites. I have an FAS
account, and the CLA has been signed, but when I try to sign on to the
TRAC, I get a "you are not allowed here" message, and the wiki tells me
that my login info is bad.


Yes, the best place to add some more info would definitely be the Trac. 
The reason why you are unable to log in is because there are some 
temporary limitations added to the wiki and all Trac instances to block 
a recent bout with spambots attacking both services. You should stop by 
in #fedora-admin and ping either puiterwijk or nirik to add your FAS 
account to the antispam-ack group. This limitation is actually due to be 
lifted sometime today, but if you are unable to log in still, please let 
the folks know there and they can help get you logged in!



As for what I <3 about Python in Fedora, I would say that it comes down
to the fact that the packages I need are in the repos, so I can manage
everything with one package manager, and the ease of transition to RHEL
instances. That said, I didn't really choose Fedora as a Python
developer, but as someone who appreciates free software and Fedora's
stance on it.



That kind of feedback is definitely good to hear. Whatever your 
experience or profession is, adding that in somewhere for consideration 
should definitely happen. Let's see if we can get your Trac permissions 
resolved and then add that to the ticket.


--
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
python-devel mailing list
python-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org