Plan for tomorrow's Fedora Infrastructure meeting - 2016-02-11
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-02-11 at 18: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
--
= Introduction =
This shared document is for the next fedora infrastructure meeting.
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 (2016-02-11)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= 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 Started spring cleaning with ibiblio hosts - 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 or 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 Spring cleaning - kevin
#topic
= 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 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.)
Schedule:
2016-02-11 - ansible installing - kevin
2016-02-18 - ?
#topic Learn about: ansible installing - kevin
= Meeting end stuff =
#topic Open Floor
#endmeeting
8 years, 1 month
Fedora People v2
by Chaoyi Zha
Hey all!
After a brief discussion with Ralph on IRC about redesigning the people
page, I've rewritten the people index page generation script in Python,
Jinja, and DataTables.
The previous Fedora People page generation script consisted mainly of bash
concatenation running in a large loop. For this next iteration, I kept most
of the data acquisition commands intact, running the bash commands through
subprocess and parsing the data in Python. However, I've cleaned up the
code significantly and now pass the data through a Jinja template to write
the final page HTML.
Here is a demo: https://cydrobolt.fedorapeople.org/people2/
Source: https://github.com/fedora-infra/people2
As requested by Ralph, this iteration includes nice libravatar user icons
loaded lazily ;)
I'm hoping to implement this as a drop-in replacement for the current
Fedora people generation script, which generates this page:
http://people.fedoraproject.org
This script requires Jinja (python-jinja2) to execute.
Any feedback or constructive objections would be appreciated! Feel free to
ping me in #fedora-apps.
Thanks,
Chaooyi
8 years, 1 month
Additional account with read DB access
by Aurelien Bompard
Hey folks,
Matt would like read access on HyperKitty's production database to collect
some statistics[1], and I wondered if we have a procedure for this kind of
request.
[1] https://fedorahosted.org/fedora-infrastructure/ticket/5070
Should it be done via a script that would be stored in our ansible repo?
I'm pretty sure I don't have the permissions to touch the private repo
though. If it's the right way, who should I ping about that?
Thanks!
Aurélien
8 years, 1 month
MirrorManager 1.4.x in the repos
by Matt Domsch
MM team - it doesn't make sense to keep MM 1.4.4 in the Fedora and EPEL
repos any more, if ever it did. However, the mirrormanager-client package
is convenient to have for mirror admins. Would someone care to package MM
2.x and push to the repos, or should I deprecate (and block from F24) the
mirrormanager-1.4.4 package?
Thanks,
Matt
8 years, 1 month
[release] pagure: 1.0.2
by Pierre-Yves Chibon
Good Morning everyone,
I just cut a new release of pagure: 1.0.2
Another bug fix release and here is the corresponding changelog:
* Thu Feb 04 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.0.2-1
- Update to 1.0.2
- Rework the PR page (Ryan Lerch)
- Add ssh_info to blacklist in default config (Ryan Lerch)
- Restyle the ssh_info page (Ryan Lerch)
- Fix hiding the preview pane when creating an issue (Ryan Lerch)
- Indicate the number of comments on the PR when listing them (Ryan Lerch)
- Fix showing the links to issues when previewing a comment
- Ensure some more that the page number isn't below 1
- Do not show the edit and delete buttons to everyone when adding a comment via
SSE
- Update the requirements.txt for a missing dependency on Ubuntu (vanzhiganov)
- Improving sorting the release tags in the release page (Clement Verna)
This is running smoothly in both stg and prod :)
Happy hacking,
Pierre
8 years, 1 month
pagure tickets brainstorming
by Kevin Fenzi
So, a number of our applications/projects have moved from github or
fedorahosted to pagure, which is coming along nicely. :)
We do have a number of "projects" on fedorahosted that aren't really
software projects, but use fedorahosted almost completely for trac.
trac is... not enjoyed by many, so it would be nice to look at what we
would need to add to pagure tickets handling in order to cover those
cases so we could look at moving some of these 'projects' over to
pagure. ;)
So, first many projects use the trac "wiki" for a page with docs on how
to file tickets, etc. I think pagure docs already should handle this
case very nicely, although perhaps there should be an option to make
the 'docs' page the default for a project instead of 'overview' ?
Pagure also has blocking/deps and private tickets.
Now, on to the things I think might be desired:
* Custom ticket statuses (some projects use this to make statuses that
are more descriptive for their project, like "upstream" or "accepted"
or whatever. This might require splitting the status of tickets to
open or closed 'status' and have a seperate 'resolution' or
something.
* Tagging of issues. Tons of projects use a 'meeting' keyword to mark
tickets they want to discuss in meetings. A way to display only
tagged tickets would be good and a bonus would be a irc friendly
meeting output to copy and paste. I see a "Tags:" field, but not how
to populate it. Is this in progress?
* A way to cc or bcc a group of people on all tickets in a project. Do
we already have this?
* Milestones (but I am not sure how much these are used). Some projects
have "Fedora 24 Alpha" "Fedora 24 Beta" type milestones for things to
be finished before some event. Perhaps we just want to drop this idea
in favor of some kind of deadline listing and emiting a message when
the deadline is reached? "This ticket was supposed to be done by now!"
* Templates. We use these a lot in infrastructure. Basically when
filing a new issue there's a list of templates and when someone
selects one it sets the initial contents and assigned and such. These
are handy for making sure users give the needed info for a type of
request.
* Theres a batch modify plugin that lets you modify a bunch of tickets
at once. I don't think this is critical, but might be nice to have.
* Is there a way to completely delete a ticket? Sometimes we have done
that on trac for spam tickets.
Thats all I can think of off hand... can other folks think of things we
use trac tickets for in the projects that are primarily using trac only?
kevin
8 years, 1 month
[release] anitya: 0.8.0
by Pierre-Yves Chibon
Good Morning everyone,
I just cut a new release of anitya: 0.8.0
Here is the corresponding changelog
* Thu Feb 04 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.8.0-1
- Update to 0.8.0
- Include a dockerfile in the sources and adjust the README on how to use it
(Tomas Tomecek)
- Include the project when sending a fedmsg notification about a flag
- Add the possibility to set the version_prefix when creating a project
- Add a test button to test a regex/backend without registering the version in
the DB (useful for debugging)
- Fix the pagure backend when the JSON returned does not contain tags
- Javascript fix: default attributes don't exist in JS (Patrick Uiterwijk)
- Fix the github backend when the homepage ends with a slash (Chaoyi Zha)
- Improved UI for projects not found by proposing to add said project
(Prashant-Surya)
This is now happily running in prod.
Thanks to everyone involved!
Happy versioning,
Pierre
8 years, 1 month
Plan for tomorrow's Fedora Infrastructure meeting - 2016-02-04
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-02-04 at 18: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
--
= Introduction =
This shared document is for the next fedora infrastructure meeting.
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 (2016-02-04)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= 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 More work on ansible network config in base role - kevin/doteast
#info Apprentice nag email went out for this month, please answer it! - kevin
#info consolidated our virt-install commands down to just a few - kevin
#info New installs should be able to dynamically grow cpu/mem and have watchdog - kevin
#info Setup our virthosts to use qemu-kvm-rhev now - kevin
#info Cleaned up a bunch of depreciated syntax in ansible, just a few more to go - 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 or 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 Infrastructure Year In Review Article
#link https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
Added Gobby Doc "Infra 2015 YIR"
#topic Spring cleaning - kevin
= 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 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.)
Schedule:
2016-02-04 - Learn about bodhi2 - lmacken
2016-02-11 -
#topic Learn about: ?
= Meeting end stuff =
#topic Open Floor
#endmeeting
8 years, 1 month