Meeting Agenda Item: Introduction Ryan Housand
by Ryan Housand
Hello all,
IRC Handle:
tuxxie
Programming Languages:
bash
python(wish to learn)
golang(wish to learn)
Systems administration skills:
I have been working as a Linux Administrator sense the late 90's,
currently as the Lead Systems Engineer with Empowered(Aflac). I have
experience with the following technologies.
Git
Ansible
Ldap
Ovirt
FreeIPA
Nginx
SeLinux
HAProxy
Networking(Linux system, Cumulus)
I am very willing to learn any technologies not listed above. I have
been using Fedora for years and look forward to giving back to the
project.
Ryan
5 years, 9 months
[Release] pagure 4.0.4
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of pagure: 4.0.4
This is a bug and security fix release.
Here is its changelog:
4.0.4 (2018-07-19)
------------------
.. note:: This release fixes CVE-2018-1002155, CVE-2018-1002156,
CVE-2018-1002157, CVE-2018-1002153
- Ensure the project's description does not contain any javascript (Michael
Scherer)
- Prevent the project's URL to be anything other than an URL
- Escape any html people may have injected in their author name in commits
(Michael Scherer)
- Do not serve SVG inline (Michael Scherer)
- The four items above constitute CVE-2018-1002155
- Catch exception raised by pagure-ci when it fails to find a build on jenkins
- Fix RELATES and FIXES regex to cover projects with a dash in their name
- Support calls from jenkins indicating the build is started
- Ensure we check the required group membership when giving a project away
- Add missing titles to the milestones table in the settings
- Properly inform the user if they are introducing a duplicated tag
- Only select the default template when creating a new ticket
- Fix the subscribe button on the PR page
- Fix updating a remote PR
- Fix showing the 'more' button on the overview page
- Multiple fixes to the pagure-milter
- Fix triggering CI checks on new comments added to a PR
- Fix logging and the SMTPHandler
- Do not notify everyone about private tickets (CVE-2018-1002157)
- Make the settings of a project private (CVE-2018-1002156)
- Ensure the git repo of private projects aren't exposed via https
(CVE-2018-1002153)
- Do not log activity on private projects
- Drop trollius-redis requirement (Neal Gompa)
It's currently running in staging where I'm doing some testing. Since it's a
security release, unless there are really big issues, I will be pushing it to
production, even if I need to do a 4.0.5 release later.
Happy hacking!
Pierre
5 years, 9 months
Fedora Infrastructure Proposed Meeting Agenda 14:00 UTC 2018-07-19
by Stephen John Smoogen
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-07-19 at 14:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2018-07-19)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info tflink is on extended PTO
#info FLOCK in Dresden is 2018-08-08->2018-08-13?
#info visit to PHX2 will be happening 2018-08-15->2018-08-18
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic Oncall
#info Smooge is on call from 2018-07-19->2018-07-26
#info Kevin? is on call from 2018-07-26->2018-08-02
#Info Smooge is on call from 2018-08-03->2018-08-14
#info ??? is on call from 2018-08-15->2018-08-23
#info Summary of last week: (from relrod)
#topic flock 2018 - dresden - kevin
who can make the infrafixfest workshop?
who can make the infra plan and hackfest?
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
5 years, 9 months
Meeting Agenda Item: Introduction Juan Martinez
by Juan Martinez
Hi,
IRC Handle: queue-tip
Programming languages:
bash
perl 5
learning python
some ruby
System administration skills:
I have worked as Linux Administrator in environments ranging in size
from small, community ISPs to DoD data centers. The majority of
systems I've administrated for work have been RHEL and CentOS.
I'm familiar with a wide range of tech including: git, ansible,
haproxy, kvm, apache, nginx, mariadb, and postgresql
I've been a Fedora user since Red Hat Linux was discontinued. I'm
looking forward to contributing back to the project that's given me
so much throughout the years.
Juan
--
Juan Martinez <redhat(a)martinez.cx>
5 years, 9 months
Meeting Agenda Item: Introduction Ryan Housand
by rhousand75＠gmail.com
Hello all,
I will keep this email short only containing information requested on
the GettingStarted wiki.
IRC Handle:
tuxxie
Programming Languages:
bash
python(wish to learn)
golang(wish to learn)
Systems administration skills:
I have been working as a Linux Administrator sense the late 90's,
currently as the Lead Systems Engineer with Empowered(Aflac). I have
experance with the following technologies.
Git
Ansible
Ldap
Ovirt
FreeIPA
Nginx
SeLinux
HAProxy
Networking(linux system, Cumulus)
I am very willing to learn any technologies not listed above. I have
been using Fedora for years and look forward to giving back to the
project.
Ryan
5 years, 9 months
Meeting Agenda Item: Introduction Ryan Housand
by rhousand75＠gmail.com
Hello all,
I will keep this email short only containing information requested on
the GettingStarted wiki.
IRC Handle:
tuxxie
Programming Languages:
bash
python(wish to learn)
golang(wish to learn)
Systems administration skills:
I have been working as a Linux Administrator sense the late 90's,
currently as the Lead Systems Engineer with Empowered(Aflac). I have
experance with the following technologies.
Git
Ansible
Ldap
Ovirt
FreeIPA
Nginx
SeLinux
HAProxy
Networking(linux system, Cumulus)
I am very willing to learn any technologies not listed above. I have
been using Fedora for years and look forward to giving back to theproject.
5 years, 9 months
Fedora Infrastructure Proposed Meeting Agenda 14:00 UTC
by Stephen John Smoogen
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-07-12 at 14:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2018-07-12)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info bowlofeggs is on PTO
#info abompard is on PTO
#info pingou is on half-time PTO
#info tflink is going on extended PTO
#info major Ibiblio outage 2018-07-10 (completed)
#info FLOCK in Dresden is 2018-08-08->2018-08-13?
#info visit to PHX2 will be happenening 2018-08-15->2018-08-18
#info Currently deplying new version of OSBS in prod - cverna
#info pkgdb is now json flat file (relrod/mizdebsk)
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic Oncall
#info Kevin is on call from 2018-07-06->2018-07-12
#info Relrod is on call from 2018-07-12->2018-07-19
#info Smooge is on call from 2018-07-19->2018-07-26
#info Kevin? is on call from 2018-07-26->2018-08-01
#info Smooge is on call from during FLOCK
#info Summary of last week: (from Kevin)
#topic Flock Talks People want to see
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
5 years, 9 months
pkgdb shutdown
by Rick Elrod
Greetings all,
We had meant to turn off pkgdb *last* July (2017), but due to various
services
depending on it, we kept it running as read-only for the past year. I am
pleased
to announce we have finally shut down the service after replacing the
last known
in-use API endpoint (/api/collections/) with a static JSON file. If you
notice
anything else still trying to query pkgdb, please let us know on the
list or in
#fedora-admin.
Thank you,
Rick
5 years, 9 months
