Re: [ansible] [distgit/pagure] Drop --autoreload from our systemd
service file
by Todd Zullinger
Hi,
Pierre-YvesChibon wrote:
> [distgit/pagure] Drop --autoreload from our systemd service file
I noticed a few recent commits using this bracket prefix
style and I wanted to give a heads-up about how this can
cause problems, in case it's not well-known.
(If I've mentioned it before, please forgive my memory
lapse.)
Using brackets to prefix the commit message will cause grief
for any patches which are applied via 'git am', as the
contents within the brackets will be stripped.
Even after the ansible repo is available via pagure, there
are likely still times when someone will attach a patch to a
bug or send it with git send-email.
If this [prefix/area] convention is more widely adopted in
the ansible repo, it's worth keeping in mind the potential
for surprise (and subtle loss of commit message details) it
will likely cause down the road.
The prefix stripping can be avoided by passing the
'--keep-non-patch' option to git am. However, there's no
config variable to allow that to be easily set per repo, so
it'd be very easy to forget.
This has been discussed on the git list in the past. One of
the more recent discussions was from 2015:
https://public-inbox.org/git/5655D3DA.1050403@informatik.uni-hamburg.de/T/#u
I had a recent bug report filed about this as well:
https://bugzilla.redhat.com/show_bug.cgi?id=1671640
(as evidence that it surprises others still).
Hope this is helpful,
--
Todd
5 years, 2 months
Meeting Agenda for 2019-02-28 Infrastructure meeting
by Stephen John Smoogen
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2019-02-27 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby )
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 (2019-02-27)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean cverna
mkonecny mizdebsk
= 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
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
= 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 nirik will have sparse hours due to house move
#info Mass update/reboots planned for 2019-02-26 -> 2019-02-28
#info Beta Freeze Begins 2019-03-05
#info Pagure 3.2.0/3.2.1 was deployed to stg/prod/pkgs.
#info Taskotron Staging re-deployed on F29, mostly working
#info
= 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 2019-02-14 -> 2019-02-21
#info puiterwijk is on call from 2019-02-21 -> 2019-02-28
#info smooge is on call from 2019-02-28 -> 2019-03-07
#info ?????? is on call from 2019-03-07 -> 2019-03-14
#info ?????? is on call from 2019-03-14 -> 2019-03-21
#info Summary of last week: (from smooge )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
#topic Priorities for next week?
#info please put tickets needing to be focused on here
#topic Discuss: Is the Fedora pastebin still useful? - relrod
#info how many users are using it?
#info should we look at converging with CentOS one so simpler setup?
= 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, 2 months
Fedora Infrastructure Meeting Agenda for 2019-02-21
by Stephen John Smoogen
This shared document is for the next fedora infrastructure meeting.
Send on IRC a day before meeting (#fedora-noc #fedora-admin
#fedora-releng #fedora-apps)
REMINDER: There will be a Fedora Infrastructure meeting tomorrow
(20yy-mm-dd) at 15:00 UTC in #fedora-meeting-1. Please update the
gobby2 document at infinote.fedoraproject.org with any agenda items
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
On the day of the meeting send the following
REMINDER: There will be a Fedora Infrastructure meeting today
(2019-02-14) at 15:00 UTC in #fedora-meeting-1. Please update the
gobby2 document at infinote.fedoraproject.org with any agenda items
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2019-02-21 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby )
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 (2019-02-21)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
= 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
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
= 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 nirik will have sparse hours due to house move
#info Mass branching happened and it was ...
#info Mass update/reboots planned for 2019-02-26 -> 2019-02-28
#info Beta Freeze Begins 2019-03-05
#info Anitya (release-monitoring.org) 0.15.0 was released and deployed
on staging
#info Pagure 3.2.90 was deployed to stg.pagure.io. Please test
#info
= 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 2019-02-14 -> 2019-02-21
#info puiterwijk is on call from 2019-02-21 -> 2019-02-28
#info ?????? is on call from 2019-02-28 -> 2019-03-07
#info ?????? is on call from 2019-03-07 -> 2019-03-14
#info ?????? is on call from 2019-03-14 -> 2019-03-21
#info Summary of last week: (from smooge )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
#topic Priorities for next week?
#info please put tickets needing to be focused on here
#topic Discuss: Is the Fedora pastebin still useful? - relrod
#info how many users are using it?
#info should we look at converging with CentOS one so simpler setup?
= 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, 2 months
FAS query question
by Ben Cotton
Infra team,
In the interests of reducing our app load, I'm checking out possible
replacements for our elections app. One of the candidates is Helios,
which would apparently require me providing a CSV of eligible voters
for each election. Do we have a programmatic way of getting email
addresses out of FAS for different queries? For example, for some
elections, we might want the cla_fpca group, while other elections may
require cla_fpca+1 and others may require a specific group.
If that functionality doesn't exist, what does the effort to add it look like?
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 2 months