Package installation on pt4.fp.o
by Paul W. Frields
I installed the following packages from epel-test repo onto
publictest4:
drupal6-advanced-help.noarch 0:1.2-2.el5
drupal6-auto_nodetitle.noarch 0:1.2-4.el5
drupal6-ctools.noarch 0:1.8-4.el5
drupal6-flexifilter.noarch 0:1.2-2.el5
drupal6-footnotes.noarch 0:2.5-1.el5
drupal6-rules.noarch 0:1.4-3.el5
I can't install the drupal6-views_bulk_operations package until
drupal6-views is available. That's Jon Ciesla's package, as seen in
this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=646610
We actually need CCK as well, which is this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=646611
Note that publictest4 is on EL-5 right now. I'm hoping that we'll be
able to move to EL-6 at some point. The state of these packages is
the same on EL-5 and EL-6, though -- so we need to work through this
issue one way or the other.
Jon, Volker -- how should we proceed here?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
12 years, 2 months
[Insight] Meeting recap 2011-02-28
by Paul W. Frields
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting-1/2011-02-28/insight.2011...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting-1/2011-02-28/insight.2011...
Log:
http://meetbot.fedoraproject.org/fedora-meeting-1/2011-02-28/insight.2011...
Meeting summary
---------------
* Roll call! (stickster, 20:00:45)
* LINK: http://publictest09.fedoraproject.org/drupal/ <-- Insight test
instance (stickster, 20:04:16)
* Status of action items (stickster, 20:04:25)
* LINK:
http://meetbot.fedoraproject.org/fedora-meeting/2011-02-17/insight.2011-0...
<-- Last meeting Thursday 2011-02-17 (stickster, 20:04:43)
* stickster has done all his action items from that list! :-)
(stickster, 20:05:06)
* stickster thinks we're still waiting on the puppet module from
smooge to be completed. stickster got him a file list for the
manifest (stickster, 20:05:50)
* asrob got added to sysadmin-test (stickster, 20:06:32)
* Status (stickster, 20:06:37)
* LINK:
http://tatica.fedorapeople.org/Fedora_Artwork/Insight/styles.css
(tatica, 20:10:13)
* ACTION: asrob remove calendar for now, and re-add it after we get a
database copy for the staging and production instance. (stickster,
20:22:30)
* The new Calendar now really requires jQuery UI module, so we'll need
to package that too, in phase 2 (stickster, 20:23:01)
* The FAS authentication, feed and FWN content functions all appear to
be working fine. So what we need now is to complete the
puppetization. (stickster, 20:27:40)
* ACTION: tatica to provide a bit of breathing space between subhead,
breadcrumb, and main content (stickster, 20:30:30)
* ACTION: stickster send email to logistics + smooge to ask about
puppetization progress and next steps. (stickster, 20:33:25)
* All other business (open floor!) (stickster, 20:33:47)
* LINK:
http://tatica.fedorapeople.org/Fedora_Artwork/Insight/drupal-tatica.png
(tatica, 20:41:41)
* ACTION: stickster produce list of 'yum list installed' for smooge
(stickster, 20:44:25)
Meeting ended at 20:50:40 UTC.
Action Items
------------
* asrob remove calendar for now, and re-add it after we get a database
copy for the staging and production instance.
* tatica to provide a bit of breathing space between subhead,
breadcrumb, and main content
* stickster send email to logistics + smooge to ask about puppetization
progress and next steps.
* stickster produce list of 'yum list installed' for smooge
Action Items, by person
-----------------------
* asrob
* asrob remove calendar for now, and re-add it after we get a database
copy for the staging and production instance.
* smooge
* stickster send email to logistics + smooge to ask about
puppetization progress and next steps.
* stickster produce list of 'yum list installed' for smooge
* stickster
* stickster send email to logistics + smooge to ask about
puppetization progress and next steps.
* stickster produce list of 'yum list installed' for smooge
* tatica
* tatica to provide a bit of breathing space between subhead,
breadcrumb, and main content
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (74)
* tatica (38)
* asrob (27)
* smooge (8)
* zodbot (4)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
12 years, 3 months
Re: L10N migration to transifex.net
by Ruediger Landmann
[note: CCed to logistics list as suggested; see below]
On 02/22/2011 03:02 AM, Jared K. Smith wrote:
> On Sun, Feb 20, 2011 at 10:33 PM, Ruediger Landmann
> <r.landmann(a)redhat.com> wrote:
>> This decision has greatly saddened and disappointed me. With all respect
>> to Dmitris and his team, to me, it seems like Fedora is giving up a key
>> part of our infrastructure and our independence.
> Sorry for the slow response -- I wasn't keeping up with email for much
> of the weekend, and didn't see this thread until this morning. I
> understand your point here regarding our independence, but I don't see
> any vendor lock-in here. The software is the same open-source
> software we'd be running on our intrastructure -- it's just that
> Indifex has offered to take care of the hosting/upgrades/maintenance
> of it for us. Because it's open source and we have the ability to
> host it ourselves at any time, it really comes down to a matter of
> trust. Personally, I can say that I unequivocally trust Dimitris,
> because I've seen the work he's done in Fedora both as a contributor
> and a former member of the Fedora Board.
Thanks Jared; and sorry for my slow reply too. I don't think anything is
gained by further haste at this point, and I've been taking some time to
think through my responses.
First, can we please clear the air of any notion of vendor lock-in? That
has never been a concern of mine, and I hope that I have not said
anything to suggest that it was. I think we can agree that you can be
dependent on someone or something even without being locked in. You
otherwise understand what I'm saying about dependence, so really, the
point of contention is "only" whether in this case, the dependence is
good, bad, or indifferent! :)
Second, I'd like to put the question of trust aside as well. Dimitris
has certainly established his credentials and bona fides within our
community. When you suggest that the move to Transifex.net comes down
to "a matter of trust" you risk reframing the discussion from "do we
think that moving Fedora's translation infrastructure to an external
provider is a good idea or not?" to "do we trust Dimitris or not?" It's
just not fair to personalize the discussion that way, and I would hate
to think that anybody would equate "doesn't support the move to
transifex.net" with "doesn't trust Dimitris".
>> Therefore, I have obtained permission from my manager to put time and
>> resources into packaging Transifex 1.1 for fedoraproject.org. I have
>> also had the time and skills of two Red Hat sysadmins allocated to get
>> Fedora's own instance of Transifex upgraded and migrated ASAP.
> That's fine, but you need to coordinate that with both the
> Infrastructure team and the rest of the L10N team. Having spoken to
> the Infrastructure team about this several times over the past few
> days, I know their first concern is going to be the dedication of
> these resources. In other words, they're not just looking for someone
> who can upgrade us to 1.0 (or 1.1-dev) now, but *guaranteed resources*
> to keep it upgraded and maintained and bugs fixed over the *long
> haul*.
Of course! :) I am working on getting something formalized in this
direction. Are the terms of the Fedora Project's service-level agreement
with Indifex a matter of public record? (and will performance reports be
publicly available to the community?)
>> I believe that if the Fedora Localization Project is open to the idea,
>> we could have an up-to-date and fully functional local instance of
>> Transifex 1.1 available within a week.
> With all respect Rudi, it's not just about the Localization team... We
> had meetings last week between the L10N team, the Infrastructure team,
> the Docs team, FESCo, the Fedora Program Manager, and myself. We
> weighed all the pros and cons of the move, and we decided as a group
> to move forward with the migration to transifex.net. We migrated the
> translations to transifex.net last Friday. We've got a deadline of
> having the transifex client packaged up and ready to go for package
> maintainers by this coming Friday. Any delay (or switch to another
> platform) adds additional burden to our L10N team, especially when
> we're already past the string freeze and into their translation time.
Understood, and I agree that added delay and uncertainty at this point
would pose a significant and unfair burden to translators. I'm sorry
that other options were not made available earlier. Thank you very much
for raising the issue with the Board (as you related in your follow-up
email, not quoted here) and I concur that it makes more sense to revisit
this after F15 is out the door. Your firm hand on the rudder is
appreciated :)
I'm a little confused by the nature of the meetings you're talking about
though. I was only at the docs meeting, and that didn't seem to include
any weighing up of options. For that matter, the L10n meeting didn't
either, based on the logs -- it reads to me more like a fait accompli.
On the subject of the L10n meeting: I'm in a difficult position. I'm
proud to number some of the people who participated in that meeting
amongst my friends, so I *really* don't want to single out specific
people or comments in the log. Also, IRC doesn't capture the nuances of
human communication very well and I can't discount the possibility that
I'm badly misreading the tone of the meeting. So, all I can do is invite
anyone who's interested to go and read the log at
http://meetbot.fedoraproject.org/fedora-meeting/2011-02-15/fedora-meeting...
One specific thing in there that does confuse me though is the vote that
occurs about 96 minutes into the meeting; I don't really understand what
was going on there or how it fits together with the idea that the
decision about where to host Fedora's translation infrastructure wasn't
just up to the Fedora Localization Project. I'd appreciate clarification
from anyone who was at the meeting.
>> I also want to take this opportunity to thank Dmitris for his extremely
>> generous offer to host this massive project on behalf of Fedora.
>> However, apart from the reasons I gave earlier, I also can't help but
>> feel that this direction would be grossly unfair on Dmitris and his
>> business. Indifex is, after all, a commercial venture, and server
>> resources and bandwidth aren't free of charge -- especially on the scale
>> contemplated for Fedora. Just before I came to work for Red Hat, I owned
>> a small IT business myself, and know that every penny counts! :)
> I don't think Dimitris would have made us the offer to host our
> translations if he would have thought that it would be unfair to
> Indifex. I agree that Indifex is a commercial venture and that the
> work they're offering does cost them money, but if Dimitris and
> company are OK with that, how can I argue against it? On the
> maintenance/upgrades side of things, that's work they already have to
> do for their other clients. On the bandwidth side of things, I'm sure
> they'll yell if their bandwidth costs get too high, and then we'll
> make a determination on whether to compensate them for bandwidth, move
> to being self-hosted again, or find some other solution.
Great :) Like I said, it's a very generous offer by Dmitris and Indifex,
and whether or not I personally agree with the move, I applaud the
commitment that it shows.
So there's room in the Fedora budget to compensate Indifex if the need
arises?
> May I also suggest that we move this discussion to the logistics
> mailing list, since the discussion needs to include more people than
> just the Docs or the Translation teams?
of course -- CCing them in.
In conclusion, I'm really conflicted here, because on the one hand I
don't want to strain friendships or to be obstructionist, but on the
other hand I feel compelled to speak up about a decision (and a process)
that disturbs me.
Cheers
Rudi
12 years, 3 months
Reminder: Fedora 14 Alpha Readiness Meeting 2011-02-24 @ 19:00 UTC (2PM US Eastern/11 AM US Pacific)
by Robyn Bergeron
date: 2011-02-24
place: irc.freenode.net #fedora-meeting
time: 19:00 UTC (2 PM Eastern)
This Thursday February 24, 2011, we will meet to make sure we are
coordinated and ready for the public release of the Fedora 15 Alpha
release (tentatively scheduled for) on Tuesday, March 1, 2011. We will
meet on Thursday regardless of the outcome from the Wednesday, February
23 "Go/No-Go Meeting."
http://lists.fedoraproject.org/pipermail/logistics/2011-February/001109.html
I'm sending this out to the more or less the same people as Fedora 14
(with a few changes that I have already verified). Let me know if there
have been changes for the Fedora 14 release or arrange an alternate from
your team. This meeting works best when we have representatives from all
of the teams so we'll be looking for the following people to attend or
send a representative.
Ambassadors -- Pierros Papadeas
Design -- Máirín Duffy
Documentation -- Zach Oglesby
FESCo -- Kevin Fenzi
Fedora Engineering Manager -- Tom "Spot" Callaway
Fedora Project Leader -- Jared Smith
Infrastructure -- Stephen Smoogen
Marketing -- Robyn Bergeron
Quality -- James Laska
Release Engineering -- Dennis Gilmore
Translation -- Noriko Mizumoto
Websites -- Ricky Zhou
See you tomorrow!
Robyn
12 years, 3 months
Fedora 15 Alpha to slip by one week
by Robyn Bergeron
Today at the Go/No-Go meeting[1] we decided to slip the Alpha by one week.
The slip is due to a blocker bug affecting a number of non-US keyboard
layouts, including German and French[2], which does not currently have a
fix or a reasonable workaround. All other blocker bugs are currently in
VERIFIED, or alternately, have workarounds documented in F15_Common_bugs.
At this time, we are not adjusting later milestone dates.
We will continue with the F15 Alpha readiness meeting tomorrow, as
previously announced on the logistics mailing list, and will have
another F15 Alpha Blocker Bug meeting Friday.
Thanks for your understanding. We will meet again next week for another
GO/NO-GO meeting.
-Robyn
[1]
http://meetbot.fedoraproject.org/fedora-meeting/2011-02-23/fedora-meeting...
[2] https://bugzilla.redhat.com/show_bug.cgi?id=676827
12 years, 3 months
