[release] pkgdb2: 2.5
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new pkgdb2 release: 2.5.
Here is the corresponding changelog:
* Mon Sep 19 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.5-1
- Update to 2.5
- Fix the pkgdb-sync-bugzilla so that it converts pkgdb collection to BZ product
in the right place
- Add the possibility to run pkgdb under Vagrant (Ryan Lerch)
- Specify rel="noopener noreferrer" to link including target='_blank'
- Fix pkgdb2.api.extras to be more robust when extracting the summary of a bug
- Make all the database table lower case to be more postgresql friendly
- Add the date of the request when listing the pending ACLs requests
- Fix the runserver script when running it with --profiler
This is happily running in stg and prod.
Happy packaging!
Pierre
7 years, 7 months
Update on the mailing-lists
by Aurelien Bompard
Hey!
Last Friday I deployed a new version of the Mailman / Postorius /
HyperKitty stack on prod. There are a lot of improvements, but one of the
most visible (and maybe the main reason for writing those changes) is the
login system. Previously, we mainly relied on Mozilla Persona and FAS. As
you may know, Persona will be shut down soon (end of November), so we can't
rely on it anymore.
The new system implements more external login providers *and* local
authentication, with the classical workflows (user signup, email
verification, password reminders, etc). This is for people who don't have
or don't want to use external login providers.
When I deployed it, I had feedback from people on the infra group that it
creates another user database that isn't managed and audited as well as
FAS, and that if people are willing to signup to Mailman, they might as
well signup to FAS.
The problem is: former Persona users have been migrated to local accounts
(because there soon won't be an external reference to point at anyway) and
those people must still be able to access their accounts. They currently do
that by requesting a password ("I forgot my password" process).
They can't login through another external service and just add their
existing address, since it is not allowed to add an address belonging to
another user.
I've thought about that over the weekend and I think we could just disable
user signup by redirecting users to FAS. This way existing Persona users
could still request a password and login, but the bulk of new users would
just create accounts in FAS. Of course we would sill have a database with
passwords for some users, but since (to my knowledge) former Persona users
can't be migrated to FAS directly, I don't think we can avoid that.
For those who had nightmares for too long with the Mailman 2 plaintext
password storage and fear it's coming back, rest assured that the passwords
are hashed and salted by Django. There may even be pepper and garlic.
That said, security vulnerabilities in Django are always possible, but
we're using the long term support release and I'm following updates.
This is what I propose changing the signup page to:
https://lists.stg.fedoraproject.org/accounts/signup/
Please correct my wording if it needs to.
Thoughts, suggestions?
Aurélien
7 years, 7 months
Meeting Agenda Item: Introduction Serhii Aheienko
by Serhii Aheienko
Hi everyone! I'd like to join your community and help (and improve some
skills too :) ).
My IRC handle
- skala
Skills that I have/would like to learn:
- I attended a bunch of python courses and have some practical
experience on it.
- On my free time I'm playing around with vagrant and ansible.
- Have some systems administration experience (windows; ubuntu/centos a
little)
7 years, 7 months
Plan for tomorrow's Fedora Infrastructure meeting - 2016-09-15
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-09-15 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-09-15)
#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 bodhi stakeholders meeting to sync up on a bunch of things - bowlofeggs
#info inactive apprentices dropped - kevin
#info new sigul in production - patrick
#info reinstalled sign-vault03 and upgraded secondary-vault01 - kevin/patrick
#info new koji tags for infrastructure packages (epel7, f25, f24) - patrick
#info new wiki in staging using openid - kevin / patrick
#info bodhi-backend01.stg moved to f24 - kevin
#info bodhi-backend01 and autosign01 removed - 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 Freeze coming up soon. What to get done before then? - kevin
#topic mass update/reboot cycle next week?
#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 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 7 months
New contributor introduction
by Amit Kumar Singh
Hello everyone am from Ranchi, Jharkhand. I love to code in python and am also contributing to mozilla
7 years, 7 months
mirror lists plan
by Kevin Fenzi
Greetings.
We currently have 3 lists associated with mirrors. 2 of them are still
located at redhat.com and we want to move them over to our
infrastructure.
mirror-admins(a)lists.fedoraproject.org
This list is open to all (but only allows posting to subscribers, I
moderate it and adrianr also does). This is usually the list we have
people with questions or issues post to to get help mirroring.
mirror-list-announce(a)redhat.com
This list was for announcing new releases and sizes for mirrors so they
would know to sync up and how large our next release was and to expect
more traffic. It was setup back in the Fedora Core days so it was
restricted to only approved mirror admins (because it would get notice
of releases before they were public).
mirror-list-d(a)redhat.com
This was another Fedora Core days list thats restricted to list admins
to discuss space issues or mirroring problems or whatever.
So, I propose we do this:
* Make a new mirror-announce list.
* Mass invite mirror-list-announce(a)redhat.com people to it.
* Make it open to all, but moderated
* Mass invite mirror-list-d(a)redhaat.com subscribers to mirror-admins
list.
* Mail redhat.com lists and close them to new posts.
Then, moving forward we send announcements about upcoming releases to
mirror-announce and important changes (like archiving a release or a
new mirroring tool or whatever).
Thoughts? Other ideas?
kevin
7 years, 7 months
[release] pagure: 2.5
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of pagure: 2.5.
Here is the corresponding changelog:
* Tue Sep 13 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.5-1
- Update to 2.5
- Don't track pagure_env (venv) dir (Paul W. Frields)
- Setting Mail-Followup-To when sending message to users (Sergio Durigan Junior)
(Fixed by Ryan Lerch and I)
- Fixed the tickets hook so that we dont ignore the files committed in the first
commit (Clement Verna)
- Fix behavior of view of tree if default branch is not 'master' (Vivek Anand)
- Fix checking the release folder for forks
- Improve the Remote PR page
- Improve the fatal error page to display the error message is there is one
- Avoid issues attachment containing json to be considered as an issue to be
created/updated (Clement Verna)
- Allow the <del> html tag (Clement Verna)
- Specify rel="noopener noreferrer" to link including target='_blank'
- Show in the overview page when a branch is already concerned by a PR
- Fix viewing a tree when the identifier provided is one of a blob (not a tree)
- Port all the plugins to `uselist=False` in their backref to make the code
cleaner
- Fix pagure_ci for all sort of small issues but also simply so that it works as
expected
- Make the private method __get_user public as get_user
- Improve the documentation (fix typos and grammar errors) (Sergio Durigan
Junior)
- Drop the `fake` namespaces in favor of real ones
- Add the possibility to view all tickets/pull-requests of a project (regardless
of their status)
- Paginate the pages listing the tickets and the pull-requests
- Add the possibility to save a certain filtering on issues as reports
- Add support to our local markdown processor for ~~striked~~
This is happily running in stg, will update prod soon :)
Happy hacking!
Pierre
7 years, 7 months