The infrastructure team will be having it's weekly meeting tomorrow,
2017-03-02 at 19:00 UTC in #fedora-meeting 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.
kevin
--
This shared document is for the next fedora infrastructure meeting.
= 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 (2017-03-02)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions
= 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 koji prod -> stg sync done. The script(s) need a lot more work - kevin
#info magazine and communityblog are now backed up - kevin and patrick
#info package maintainer instancees are moved to the fedorainfracloud - kevin
#info fedorahosted.org retired! - kevin
#info lots of redirects and migration work to finish off some projects - kevin
#info el5 signing key expired, patrick fixed it - patrick
#info March apprentice nag email out, respond today! - kevin
#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
= Apprentice office hours =
#topic Apprentice Open office hours
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 gsetup 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 info 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hiya,
Unfortunately, we haven't been able to migrate freemedia to pagure
completely yet. I think pausing freemedia until we can complete the
migration would be OK. I really hope to get it done in the next few
weeks. There just are too many pieces that need updating:
https://pagure.io/pagure/issue/1223
In the meantime, would it be possible to disable new tickets on the
trac and permit volunteers to work with the ones that have already been
filed?
- --
Thanks,
Regards,
Ankur Sinha "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJYt0ziAAoJEPjYwL66yJi96KUIAJ1DvVQggWLY5wT5yAoEINzE
WZfAxCb8KZqBF9721Xsp+8CCUce35mqZWZpEozTmc/AOOT6sgVjHkp2r0Z2A+VV3
plBWn3WLv4jyaPYrtD0nNVAMEwoaQPOqvxx8Zuwp6FjGHJwtj/+1wRl15IUDAizT
5qF5eczqVowh3nljT73nnwUK/RtmAwI/pM5RJ6+Dr6qbnc0MS2vTk3lC+ua8/71I
cP6pHspeYLE1ppQss3nL5QHyM/qWZFkgsH0BOsFrS5/+Xvt3cbZAJ7ujGhBiyLKO
EF9xos8qjZ/46FVNzDvlYrp4wqPeMyiadZKBmH5lBGpjVS8rYE0lv0AtQZ7Y3NE=
=5lLr
-----END PGP SIGNATURE-----
There is an outstanding bug report
https://bugzilla.redhat.com/show_bug.cgi?id=1423753 that came up in
the Fedora Server meeting today.
Does someone know who can make this fixed? And who owns the Amazon AMI
account so it can be fixed quickly in the future?
--
Stephen J Smoogen.
Greetings!
I am a member of the Fedora Design team and am currently working on redesigning the EasyFix site (https://fedoraproject.org/easyfix/)
I want to add category labels for the different skill sets required to complete issues on EasyFix. Eg. HTML, Python, Scala, JavaScript, so that issues can be sorted by skill set required (if possible).
If someone close to the EasyFix project was able to share data about the types of skill sets requested for Easyfix issues, it would really help me out.
Kindest regards,
Kathryn