Plan for tomorrow's Fedora Infrastructure meeting (2013-09-18)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-09-18 at 19:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
10 years, 7 months
GitLab packaging progress and discussion about deployment on fedorahosted
by Achilleas Pipinellis
Dear infra team and others that this mail may concern,
As many of you know (I hope :p), one of this year's GSoC projects, is
to package GitLab and all its dependencies for Fedora and later for
EPEL. There have been at least 3 discussion threads about this since
March [0][1][2][3].
I have been in contact with GitLab's core team and we talked about how
we could all work together to make this happen and how GitLab could be
eventually deployed in fedorahosted as an alternative git service. For
the time being there are 2 major show-stoppers:
1) GitLab uses some forked gems.
These are the forked gems by GitLab which add some extra functionality
or fix some bugs of the original gem:
Upstream | GitLab
-------------------------------------
grit | gitlab-grit
grack | gitlab-grack
gollum-lib | gitlab-gollum-lib
omniauth-ldap | gitlab_omniauth-ldap
pygments.rb | gitlab-pygments.rb
-------------------------------------
Vit Ondruch, my mentor, pointed me in these FESCO [4] and FPC [5]
tickets, which pretty much conclude that:
"FESCo is fine with forks as long as they are parallel installable and
don't interfere with each other."
and
"The FPC does not see a need for additional guidelines relating to
forks at this time, they should be treated like any other package."
I also raised this issue in #fedora-devel today and they told me the
same thing FESCo concluded.
I think GitLab's forks don't abide by FESCo's verdict, as both original
and forked gem are called with the same library, eg. require 'grit', so
there is no distinction between them.
I am cc'ing Sytse Sijbrandij from GitLab's core team to talk about what
changes could be made in order for the forks to get accepted.
2) The feature of public browserability for non logged in users is not
yet implemented.
This long awaited feature is the major show-stopper for getting GitLab
deployed on fedorahosted. Quoting Sytse's proposal:
> Of the two improvements I think that 2) is the most necessary. Without
> a public project UI Fedora will not switch to GitLab. There is already
> a public project git clone functionality in GitLab. Opening up more of
> the project such as issues might load to in-advert exposure of issues.
> Therefore we want to do it only on a major version upgrade. We started
> with GitLab 6.0 a week ago and would like to merge this fast so it can
> be included in the beta released on July 22. If Axilleas works on this
> then Dmitriy is prepared to coach him, this will be needed since this
> feature will impact the whole application.
>
> Our proposal would be to:
> A) Start working on the public UI immediately
> B arrange a online meeting between Fedora and GitLab.com people to talk
> about packaging
> C) have beta version of GitLab run on a demo server with Fedora project
> on August 1
> D) aim to have GitLab in production for all Fedora projects on
> September 1
>
> Of course this is just a proposal. We have too little knowledge of the
> Fedora project to make a proper plan.
The initial plan of the GSoC proposal is to package GitLab,
but since I talked about it with Sytse I thought it would be more
productive to bring the discussion here and sort some things out all
together.
Thank you all for your time,
Axilleas
[0]
https://lists.fedoraproject.org/pipermail/infrastructure/2013-March/01263...
[1]
https://lists.fedoraproject.org/pipermail/infrastructure/2013-April/01273...
[2]
https://lists.fedoraproject.org/pipermail/infrastructure/2013-April/01275...
[3]
https://lists.fedoraproject.org/pipermail/infrastructure/2013-May/012885....
[4] https://fedorahosted.org/fesco/ticket/810
[5] https://fedorahosted.org/fpc/ticket/148
--
GPG : 0xABF99BE5
Blog: http://axilleas.github.io
FAS : https://fedoraproject.org/wiki/User:Axilleas
10 years, 7 months
Some question\Ideas Wiki Admin?
by Frank Murphy
This didn't seem to fit the trac-ticket system.
Some question\Ideas
Following on member(s) that may have left the project
and\or sub-group(s).
I am getting delivery failure on *(a)fp.o email aliases.
Is that a good indicator of someone having left the fp.o?
How can it be made certain\ is certainty possible?
If so, are they auto removed from fp.o
Old wiki user pages?
Content can be cleared,
can old stuff be deleted?
There appears to be many such "needs love" pages.
Came across:
https://www.mediawiki.org/wiki/Extension:DeleteBatch
--
Regards,
Frank
I now wear a mask to breathe at night
www.frankly3d.com
10 years, 7 months
Introduction
by Miroslav Suchý
Hi,
I've been on this list for a while, but mostly passive. I want to change that. So let me formally introduce myself.
My name is Miroslav Suchý (sometime I use short name Mirek).
I'm using Linux from previous millennium. I'm Red Hat employee since 2006.
I worked on RHN, Spacewalk and Katello in past. Since this summer I have been working on Copr.
I would like to attend meetings and submit RFR for Copr when it becomes ready.
You can catch me on #fedora-buildsys during day (of European TZ).
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
10 years, 7 months
New Contributor Loïc Maury
by Loïc Maury
Hello,
My name is Loïc Maury, and I have just registered to the fedora project
for contribute to infrastructure.
I use Fedora since five years now, and I am very enthusiastic to contribute.
I am particularly interested by project idea for infrastructure and by
functional programming (Haskell, Erlang, Lisp).
Thank you
Loïc
10 years, 7 months
Plan for tomorrow's Fedora Infrastructure meeting (2013-09-12)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-09-12 at 19:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
10 years, 7 months
freeze break request: add requesting ip address to geoip
by Kevin Fenzi
The gnome folks would like to also start using our geoip service (at
least for now), but their code expects to also find the ip address that
requested in the results. They are going into a freeze tomorrow, so
they would really prefer this land today.
We have tested in stg and they have run their tests against stg just
fine.
I also talked with anaconda folks who currently use this and they don't
think there will be any issues with adding a new ip:address result in
the output json for them.
Thanks to Xavier for poking at this!
+1s?
kevin
--
diff --git a/modules/geoip-city-wsgi/files/geoip-city.wsgi
b/modules/geoip-city-wsgi/files/geoip-city.wsgi index 3a00f60..9435820
100755 --- a/modules/geoip-city-wsgi/files/geoip-city.wsgi
+++ b/modules/geoip-city-wsgi/files/geoip-city.wsgi
@@ -59,6 +59,7 @@ def application(environ, start_response):
response.status_code=code
return response(environ, start_response)
+ results['ip'] = client_ip
results = json.dumps(results)
response.headers['Content-Length'] = str(len(results))
response.write(results)
10 years, 7 months
