Plan for tomorrow's Fedora Infrastructure meeting - 2015-06-25
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2015-06-25 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 (2015-06-25)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
#topic GSoC student update - kushal
= 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 Large outage and issues last thursday-saturday, great work fixing things - everyone
#info work moving forward on people01 replacement for people03 - kevin
#info Mailman3 migrations started - abompard
https://fedoraproject.org/wiki/Mailman3_Migration
https://fedoraproject.org/wiki/User:Abompard/HyperKittyDeploymentPlan
#info koschei now in production, announcements soon - koschei team
#info kevin will be out from 2015-06-27 to 2015-07-05 - kevin
= 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
#topic - mdomsch - Retire MM 1.4.4 from Fedora and EPEL repos
Not sure I can attend, but I see no reason to keep mirrormanager 1.4.4 in the Fedora 23
repositories. We have a couple choices:
1. transition owner to someone and let them put mirrormanager 2.x into the repos
2. orphan and delete MM 1.4.x from FC23, let the releases in FC21-22 remain as-is
Happy to do whichever the team desires, and if someone with pkgdb admin rights wants
to take care of it too, don't wait on me. Thanks! -mdomsch
(P.S. it's in EPEL repos too, follow the same logic).
#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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
8 years, 10 months
[release] MirrorManager2: 0.3.0
by Pierre-Yves Chibon
Good morning everyone,
I just cut and pushed a new release of MirrorManager2: 0.3.0
Here is its changelog:
* Wed Jun 24 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.3.0-1
- Update to 0.3.0
- Fix the --delete action of the umdl (Adrian Reber)
- If the user is not an admin, keep the existing admin_active settings
- Only MM2 admins are allowed to change the always_up2date flag of a mirror
- Also fix the mm2_crawler logrotate script like the one for umdl (Adrian Reber)
The third item listed there was quite annoying as it was making every mirror
admin visiting their mirror page to disable their mirror using the admin_active
field (so a field they do not have access to).
The fix of the umdl --delete should allow us to remove all the alpha/beta
information present in the DB and that are not needed.
Have a nice day,
Pierre
8 years, 10 months
GitHub contributors and the FPCA
by Pierre-Yves Chibon
Good morning everyone,
Few weeks I asked spot about the status of the FPCA with regards to contributors
sending pull-requests via GitHub. Spot replied to me a couple of weeks ago with
the following answer which I thought I should share since we are several
managing projects on GitHub:
===
> * The second use-case I had a thought about was the github use-case. We have
> more and more projects hosted on github, from a bunch of different teams.
> People contributing to these projects via github do not have to sign the FPCA,
> is this a problem?
> I am always un-sure about this part, so it might be just me but when I
> contribute to a project that is GPL/MIT/BSD/...-licensed my work is
> automatically licensed under the license of the project, right?
> If so, then I guess it's fine FPCA-wise :)
Well, there is nothing legally that makes your contributions magically
under a license, with the notable exception of Apache and derived
licenses. Richard Fontana argues (rather reasonably) that there is an
expectation that contributions to an upstream project, without a clear
and explicit licensing statement, are thus safe to interpret as being
under the same license as that upstream project. However, there is no
current legal framework to back that up. The risk is admittedly minimal
that a change will come in, we'll merge it, and later, that person will
claim it is under some odd non-free or incompatible license, but it is
not zero.
I would personally prefer it if we either confirmed that people
submitting changes to our projects were either signers of the FPCA or
provided explicit licensing information. This could be done by asking
them in the merge request something like "Please confirm that you give
us permission to use this change under the same license terms as the
rest of this code."
===
I went through the list of contributors on some of my projects and already found
3 persons who contributed without signing the FPCA (which is great: outside
contributors \ó/, and less so: have now to ask them to confirm their
contributions is under the same code as the project).
With pagure gaining features, I am considering more and more moving some of my
projects there :)
Pierre
8 years, 10 months
[release] anitya: 0.6.0
by Pierre-Yves Chibon
Good morning everyone,
I just released a new version of anitya: 0.6.0 and here is its changelog:
* Wed Jun 24 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.6.0-1
- Update to 0.6.0
- Update to the latest bootstrap fedora (Ralph Bean)
- Feature/prettier flash system (David Gay)
- Fix README (Ralph Bean)
- Add a system to flag projects to the anitya admins (David Gay)
- Adjust the rubygems backend to use versions API (Vít Ondruch)
- Fix the unit-tests suite
- Add a haskell Stackage backend (Jens Petersen)
- Add a pagure backend
This is now happily running in prod :)
Thanks to everyone who contributed to this new release!
Pierre
8 years, 10 months
[release] pagure: 0.1.18
by Pierre-Yves Chibon
Good morning again everyone,
As promised I cut a new pagure release: 0.1.18
Here its changelog:
* Mon Jun 22 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.18-1
- Update to 0.1.18
- Fix the eventsource server for CORS
- Fix showing/checking the merge status of a PR
So now we have the eventsource server work fine with CORS correctly configured!
Enjoy,
Pierre
8 years, 10 months
[release] pagure: 0.1.16 and 0.1.17
by Pierre-Yves Chibon
Good morning everyone,
On Thursday last week I have cut a new release of pagure: 0.1.16
Here is its changelog:
* Thu Jun 18 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.16-1
- Update to 0.1.16
- Clone all the remote branches when cloning a project
- Allow online editing to a new branch or any of the existing ones
- Allow the <hr /> html tags in markdown
- Add eventsource support in the ticket and pull-request pages
The biggest feature being this last one, the event source support.
Seeing that there was a few bugs in that release when testing it in stg (as well
as that it required some configuration changes), 0.1.16 never made it to prod.
This morning I cut a new release: 0.1.17
Here is its changelog:
* Mon Jun 22 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.17-1
- Update to 0.1.17
- Fix for missing docs of API issue add comment (Kunaal Jain)
- Fix the systemd init file
- Be more careful about the URL specified, it may be of the wrong format in the
eventsource server
- Allow configuring the port where the event source server runs in the
configuration
- Fix bug in filter_img_src introduced with its moved to the backend library
This one has been pushed to both stg and prod and is happily running there.
However, I found out that the eventsource server had some CORS integration issue
which I managed to fix in prod and for which a pull-request is currently opened,
so expect a 0.1.18 later today with these fixes :)
Happy hacking!
Pierre
8 years, 10 months
Meeting Agenda Item: Introduction Kinokoio
by Ivan Pacheco
Hello, I'm Kinokoio. I would to like to join the Infrastucture team in order to gain experience. I have been using Linux since 2010 and I am a minimalist user. I also know how to read bash scripts, read/write Python/PHP, C/C++ programming experience and general system administration and virtualization knowledge.
Hope I am useful to the team and I'll appreciate some help to get started.
8 years, 10 months
RE: infrastructure Digest, Vol 109, Issue 14
by Ivan Pacheco
> From: infrastructure-request(a)lists.fedoraproject.org
> Subject: infrastructure Digest, Vol 109, Issue 14
> To: infrastructure(a)lists.fedoraproject.org
> Date: Tue, 16 Jun 2015 12:00:05 +0000
>
> Send infrastructure mailing list submissions to
> infrastructure(a)lists.fedoraproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure
> or, via email, send a message with subject or body 'help' to
> infrastructure-request(a)lists.fedoraproject.org
>
> You can reach the person managing the list at
> infrastructure-owner(a)lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of infrastructure digest..."
>
>
> Today's Topics:
>
> 1. [release] fedocal 0.14 (Pierre-Yves Chibon)
> 2. [release] pagure: 0.1.14 (Pierre-Yves Chibon)
> 3. Meeting Agenda Item: Introduction Jean Vicelli (jean vicelli)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 15 Jun 2015 15:31:48 +0200
> From: Pierre-Yves Chibon <pingou(a)pingoured.fr>
> To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
> Subject: [release] fedocal 0.14
> Message-ID: <20150615133148.GD5352(a)carmine.pingoured.fr>
> Content-Type: text/plain; charset="utf-8"
>
> Good morning everyone,
>
> I have just released a new fedocal version: 0.14
>
> Here is its changelog:
> * Mon Jun 15 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.14-1
> - Update to 0.14
> - Add an API endpoint presenting a shield if the user is currently in a meeting
> - Sanitize the text generated by markdown to avoid potential XSS
>
> Deployed in both stg and prod.
>
>
> Enjoy!
>
> Pierre
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 181 bytes
> Desc: not available
> URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150...>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 15 Jun 2015 17:44:53 +0200
> From: Pierre-Yves Chibon <pingou(a)pingoured.fr>
> To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
> Subject: [release] pagure: 0.1.14
> Message-ID: <20150615154453.GF5352(a)carmine.pingoured.fr>
> Content-Type: text/plain; charset="utf-8"
>
> Good morning everyone,
>
> I have just released and pushed a new version of pagure: 0.1.14
>
> The changelog is pretty big and quite a number of bugs have been fixed and RFE
> implemented.
> Here it is:
> * Fri Jun 12 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.14-1
> - Update to 0.1.14
> - Remove all new lines characters from the ssh key uploaded
> - Adjust the URL in the footer to point to https://pagure.io/pagure
> - Fix displaying the time of a comment
> - Forbid the use of spaces in group name
> - Do not get the list of not-merged commits if there is only 1 branch in the
> repo
> - Display the error message if pagure.lib.add_group raises an exception
> - Add a new setting enforcing that all commits in a PR are signed-off by their
> author
> - Enforce that all commits are signed-off by the author if the repo is
> configured for this
> - Also check for the signed-off status before merging a pull-request
> - Adjust online-editing to allow specifying which email address to use in the
> commit
> - Add an avatar_email field to projects
> - Change the PullRequest's status from a Boolean to a Text restricted at the DB
> level (Allows to distinguish Open/Merged/Closed)
> - Show in the pull-request view who merged the pull-request
> - Specify who closed the pull-request in the API output
> - Catch GitError when merging and checking merge status of a PR
> - Hide the form to create pull-requests if the user is not an admin of the repo
> - Replace the Pull-Request button by a Compare button if the user it not a repo
> admin
> - Set the title of the tab as URL hash to allow directly linking to it
> - Adjust the API to be able to distinguish API authentication and UI
> authentication
> - Fix API documentation to create new issues
> - Drop the status from the requirements to open a new issue via the API
> - Expand the list of blacklisted project names
> - Have the code tags behave like pre tags (html tags)
> - Allow project to specify an URL and display it on their page
> - Strip the ssh keys when writing them to the authorized_keys file
> - Disable javascript in all the markdown fields
> - Validate early the input submitted in the forms (using more or less strict
> regex)
> - If the session timed-out, redirect to the setting page after authentication
> and inform the user that the action was canceled
> - Catch PagureException when adjusting the project's settings
> - Redirect the /api endpoint to the api documentation place
> - Fix how is retrieved the list of emails to send the notification to
> - Sanitize the html using bleach to avoid potential XSS exploit
> - Do not give READ access to everyone on the tickets and pull-requests repos to
> avoid leaking private tickets
> - Adjust the unit-tests for all these changes
>
>
> Hope you like it!
>
> Pierre
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 181 bytes
> Desc: not available
> URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150...>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 15 Jun 2015 20:04:44 -0300
> From: jean vicelli <jcvicelli(a)gmail.com>
> To: infrastructure(a)lists.fedoraproject.org
> Subject: Meeting Agenda Item: Introduction Jean Vicelli
> Message-ID:
> <CALCABKtw2OskcH=TERddyU+_XnwKazbtsFKOv7Xf5QMY9fswcQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello Fedora-Infrastructure!
>
> My name is Jean( IRC: jcvicelli ), I'm from Curitiba, Brazil and I've been
> working with infrastructure for a while, with both Linux and Windows
> servers. I'm also a bash script and python developer!
> I can easyly spend 4 to 5 hours a week contributing, out of my work
> time(utc -3)..
>
> Appreciate some help to get started!
>
>
> --
>
>
> att.
>
> *Jean Carlo Vicelli*
>
> <http://br.linkedin.com/in/jeanvicelli>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150...>
>
> ------------------------------
>
> _______________________________________________
> infrastructure mailing list
> infrastructure(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>
> End of infrastructure Digest, Vol 109, Issue 14
> ***********************************************
8 years, 10 months
MM 1.4.4 in Fedora 23?
by Matt Domsch
Team - I see no reason to keep MirrorManager 1.4.4 in Fedora 23, do you? I'm happy to pkgdb change owners to someone else so you can upgrade it to MM 2.x, or it can be orphaned and dropped (so few users, I don't think it needs to live in the OS repositories).
Thoughts?
Thanks,
Matt
--
Matt Domsch
Senior Distinguished Engineer & Executive Director
Dell | Software Group, Office of the CTO
8 years, 10 months
Plan for tomorrow's Fedora Infrastructure meeting - 2015-06-18
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2015-06-18 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 (2015-06-18)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
#topic GSoC student update - kushal
= 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 Got the runroot plugin working in our production koji - threebean / nirik
#info arm03-packager and arm03-qa instances announced and reinstalled with f22 - nirik
#info production koji store mounted ro on koji01.stg - nirik
#info grew storage for secondary arch kojis - nirik
#info fixed fed-cloud09 playbook to be idempotent for check/diff at least - nirik
#info initial people01 setup in ansible/rhel7. Still needs work - nirik
#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
= 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: fedmsg - threebean
= Meeting end stuff =
#topic Open Floor
#endmeeting
8 years, 10 months
