There's a pretty big DB schema change that I'd like to do in HyperKitty,
and since it involves a primary key I expect a downtime of several hours,
possibly a day (more precise testing going on)
The good news it that mailman will keep running, only the web UIs will be
down (HyperKitty & Postorius, the admin UI).
It's a change that I've put off for a while, but the more we wait the
longer the downtime will be (because it depends on the size of the email
What time do you think would be the less worse for such a change? After
freeze break next week? After General Availability (whenever that is) ?
I have a feeling that after freeze break is better because the folks who
use the web UIs to read email may also be those who will need to
communicate more after the GA, to discuss communication and reviews.
I don't mind starting the migration on a weekend of course, to impact less
Thanks for your input.
I recently started re-writing the fedmsg documentation. Since its
primary users are people in Fedora Infrastructure, I'd love your
feedback on the first draft.
There's a pull request where you can leave comments on the diff,
but I also built the documentation so you can see what it really
The current docs: https://fedmsg.readthedocs.io/en/latest/
The proposed docs: http://jcline-fedmsg.readthedocs.io/en/reorg-docs/
I'm particularly interested in how you find the organization of the
proposed docs. Is the order weird/unexpected/confusing? Is there a
section you think is missing? Do they go into enough detail?
Any feedback would be greatly appreciated (either on GitHub or here via
Good Morning Everyone,
I cut a new version of pagure earlier today: 3.4
Here is its changelog:
* Mon Jul 31 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.4-1
- Update to 3.4
- Fix layout breakage in the doc
- Update the refresh-gitolite action of pagure-admin for the new interface
- Stop using readlines() to drop the trailing new line character
- Fix logging by properly formatting the message
- Fix the issue count in the My Issues page (Vivek Anand)
- Add a configuration key to disable deleting branches from the UI
- Add a configuration key to disable managing user's ssh key in pagure
- Fix the vagrant environment (Clement Verna)
- Fix branch support for the git blame view
- Update the PR ref when the PR is updated
- Add a configuration key to disable the deploy keys in a pagure instance
- Fix login when groups are managed outside of pagure
- Fix setting up the git hooks when there is no DOCS_FOLDER set
- Fix installing up the pagure hooks when there is no DOCS_FOLDER set
As you can see most of the changes are related to deploying pagure on dist-git,
small bug fix and some more configuration options.
This is happily running in stg.pagure.io and src.stg.fp.o/pagure though we
already found (and fix) our first bug in 3.4, meaning there will likely be a
3.4.1 before we deploy pagure in prod.
COPR now operates with packages solely from official Fedora repositories.
This was requested in https://pagure.io/fedora-infrastructure/issue/5166 as
a condition to get the Fedora Infra support. I would like to ask for the
support now as this condition is finally satisfied \o/.
Perhaps this could be reflected in:
- the Service Level Expectations that are being prepared
- removing the user message on COPR homepage
- change of the domain back to fedoraproject.org (?)
- moving COPR to a platform where the support is actually possible
I particularly like the idea of running COPR solely in OpenShift or in RHOSP
10+ with having builders as OpenShift pods but this is not really my
I am happy this is finally going somewhere.
I wanted to bring up ticket #6162 on the list to see if there might be
anyone else who can help out with this problem:
Currently, the Community Blog is an unusable state for writing / editing
any posts. This wasn't a time-sensitive problem before, but when I filed
the ticket, I forgot that the Elections are coming up next week, and all
nominated candidates for Council / FESCo / FAmSCo publish their
interviews on the Community Blog.
I fell behind a bit for the last few months, but I understand that the
Fedora Magazine is in a more standardized set-up than the Community
Blog. I think bringing the Community Blog into parity with the Magazine
would resolve this, but I don't know how the set-up is configured
currently. I've tried to do all I can to debug the issue from my part,
but I've hit a wall for what I can do.
If there's anyone that can help with this before next week, this would
be a huge help! Thanks.
Justin W. Flory
Good day all!
My name is Chris and I go by the IRC handle of ole88. I was AtlSmitty
for a hot minute and decided to change it. I have used and/or tinkered
with C, C++, C#, Cobol, SQL, PowerShell, bash (years ago) and have
currently been learning Python in my spare time. I am a system
administrator in my day job working primarily with Microsoft and VMware
products, but we are venturing into Red Hat very soon. I love to
learn, so I am open to learning new languages, scripting tools and
applications to assist the team in any way I can.
I hold VCP5-DCV and VCP6-DCV at present and have aspirations for
additional VMware certifications as well as RHCSA and RHCE in the near
future. I am open to any tasks that will allow me to learn how things
are done and new skills to assist the team. I have started working on
the Service Level Expectations data to help move that effort forward.
As far as the SLE effort goes, if anyone can provide the service type
each application should be listed in, that will help fill in that gap
in my current data. I will post what I have to the ticket for anyone
to review and comment on. If I left anything out or you have questions
for me, let me know.
I look forward to working with everyone!
There will be an outage starting at 2017-08-04 21:00 UTC, which will last
approximately 15 hours.
To convert UTC to your local time, take a look at
date -d '2017-08-04 21:00 UTC'
Reason for outage: important HyperKitty database schema change
* HyperKitty, the mailing-list archives and reading interface
* Postorius, the mailing-list administration interface
Mailman will not be affected, emails sent to the lists will continue to be
delivered during the outage, but they will not be archived at that time
(the archiver will be offline). The emails delivered during the outage
will be added to the archives when they are back online.
Ticket Link: https://pagure.io/fedora-infrastructure/issue/6184
Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.