Meeting reminder
by Mike McGrath
Sorry for the short notice but just a reminder we have a meeting in about
5 minutes. Considering the outage this weekend it would be good for
people to attend so more people know exactly what is going on.
-Mike
14 years, 4 months
Re: Docs Installation Guide - Submission and Download problem
by Paul W. Frields
On Fri, Dec 04, 2009 at 10:51:59AM +0200, Dimitris Glezos wrote:
> 2009/12/3 Ruediger Landmann <r.landmann(a)redhat.com>:
> > On 12/02/2009 05:47 PM, Dimitris Glezos wrote:
> >>
> >> Rudi, you could clear the cache and refresh it.
> >>
> >
> > Really? How do I do that? I'd thought that a button like that would be useful for the
> > maintainer of a project
>
> This button is available on the web interface on component pages for
> maintainers.
>
> > , not least of which because changes to a POT in the repo don't automatically
> > trigger a refresh (of course!) while submissions of updated POs do.
>
> This functionality has been available in Transifex for a while, it's
> just that Fedora is still running an old (and unmaintained) version.
Diego posted the summary of what needs to be done here:
https://fedorahosted.org/fedora-infrastructure/ticket/1455#comment:10
In short, we need a few people to step up and help with the process
Diego posted.
We already do have a L10n Admin group[1] that should be overseeing and
managing this process, to ensure a successful rollout for translators.
Their charter is to maintain the infrastructure for translators, and
this clearly falls into that area. I've heard from two of the people
in that group that they can't do all this work themselves, but haven't
heard from Ankit or Asgeir about it.
What I would suggest is that Diego should help with bullet #4 on that
list, as it probably requires the greatest degree of specific
technical knowledge, in this case a database upgrade. The rest of the
work on that ticket could likely be done entirely by the remainder of
the team, maybe with limited input from Diego. It would be helpful
for Asgeir or Ankit to help manage this set of tasks in collaboration
with Diego, who has appropriate package access. (I'm cc'ing Ignacio
directly as well, so he can add appropriate CVS access for any other
people who are willing to help maintain the EL-5 package used on our
Infrastructure.)
Without help, it's doubtful there will be a new Transifex rolled out,
and that means some of the problems people are experiencing will
continue, even though they're already fixed upstream. I'm cc'ing the
docs, devel, and infrastructure lists to see if any of the people in
areas well served by translators are willing to help see this project
through. It's time to pull together, guys, and see if we can help the
translators who give so much across the whole Fedora Project.
* * *
[1] https://fedoraproject.org/wiki/L10N/Tools#Website
--
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/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 4 months
devsergio
by Sergio Araujo
workrecipient(a)gmail.com
14 years, 4 months
Intro ---Hi
by Arun
Hello All,
My name is Arun from INDIA,
I've been using fedora at home/office since version FC 3. I'm a C and Java
programmer. I have a little experience with Perl.
I've worked as a Data Center/Infrastructure Engineer. I've worked with RH
7.3, 8, 9(testing project); RHES/AS 3, 4; FC 3,4,5,6; VxWorks Linux
(Motorola Hardware testing project).
Now I'm with HP working as a UX/LX Engineer. I'm also preparing my thesis in
Cluster computing to register my Ph.D
I'm not sure where I can start start helping. Looking forward to Infra
Structure team.
Regards
*++Arun*
*Quote:* Imagination is more than knowledge
14 years, 4 months
Introduction
by Patrick Day
Hello All,
My name is Patrick Day, and I have been using Fedora for a few years now,
and I absolutely enjoy working with it. I like it so much in fact that I
have decided to contribute to the Fedora community. I have been a Software
Test Engineer in many different facets (I will also sign up for the QA
project) for about 4.5 yrs, and as such I gained valuable experience in
writing scripts, programming, and debugging; I seek to contribute whatever I
can. I am interested in the infrastructure project because I would to refine
and improve my programming skills in general. If anyone has any questions
about my experience please feel free to contact me.
- Patrick
14 years, 4 months
Intro
by John Stanton
Hi,
I always suck at these things, but here goes.
I have been using Fedora for the past year and am loving it. I am
looking to gain more experience and skills. Also I am wanting to
contribute however I can to the fedora project.
I can also contribute 20gb of space and around 900GB to 1000GB of
bandwidth per month.
Skills/Experience:
System Administration:
* RHCE Certified, Red Hat Enterprise Linux, Fedora, Ubuntu.
Development:
* Perl, Shell scripting, Very little Python(Looking to learn).
Networking:
* TCP/IP in both Internet and LAN related aspects.
* DNS, Apache, NFS.
TRAINING/CERTIFICATION:
* Red Hat Certified Engineer (RHCE) #805009697437335.
* RH300 Red Hat Linux Networking and Security Administration.
* Red Hat Certified Technician (RHCT) #605008014222023.
* RH133 Red Hat Linux System Administration.
* ITIL V3 Certificate.
* ITIL V3 Foundations Challenge Course.
* Perl Programming.
* CompTIA Security+, Network+, A+.
* Microsoft MCP (Windows XP).
If anyone wants to know more about me or my experience just ask.
John
14 years, 4 months
[ANNOUNCEMENT] Red Hat Bugzilla 3.4 Upgrade Public Beta
by James Laska
Greetings,
I am sending this on behalf of Dave Lawrence and the bugzilla team at Red Hat. Fedora uses this instance of bugzilla too.
Please forward this on to any appropriate lists that were missed.
Thanks,
James
==========================
Greetings,
The Red Hat Bugzilla team is happy to announce the first public beta
release of the next version of Red Hat Bugzilla based on the upstream
3.4 code base.
Please test drive at:
https://partner-bugzilla.redhat.com
Over the years Red Hat has made substantial customizations to Bugzilla
to fit into the Engineering tool chain. Over time the upstream has
incorporated some of these customizations or solved them in different
ways. Upgrading reduces our customization footprint (and thus
maintenance) while bringing many bug fixes & enhancements.
The main area of focus for our public betas are stability. Functionality
that currently works in our 3.2 code base should continue to work as
expected in the new 3.4 release. These include various ajax
optimizations, needinfo actor support, frontpage.cgi, product browser,
several various UI enhancements, and of course the XMLRPC API.
Please feel free to point your various scripts and third party
applications that use the XMLRPC API at the test server to make sure
they continue to function properly.
There are numerous other changes behind the scenes that we haven't
listed. The goal is to make sure that functionality that people have
come to expect in 3.2 is possible in the new system.
There are also numerous new features/fixes that are part of the upstream
3.4 release. For more detailed information on what has changed since the
last release, check out the Release Notes page.
The database is a recent snapshot of the live database so should be
useful for testing to make sure the information is displayed properly
and changeable. Also with a full snapshot it is possible to test for any
performance related issues. Email has been disabled so that unnecessary
spam is not sent out. So feel free to make changes to bugs to verify
proper working order.
We are asking for everyone to get involved as much as possible with
testing and feedback on the beta releases to help us make this the most
robust and stable release possible.
Please file any enhancement requests or bug reports in our current
Bugzilla system at bugzilla.redhat.com. File them under the Bugzilla
product and relevant component with the version 3.4. With everyone's
help we can make this a great release.
Thanks The Red Hat Bugzilla Team
14 years, 4 months
Meeting Log - 2009-12-03
by Ricky Zhou
20:00 < mmcgrath> #startmeeting
20:00 < zodbot> Meeting started Thu Dec 3 20:00:39 2009 UTC. The chair is mmcgrath. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00 < zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00 * mmcgrath see's an a-k
20:00 < mmcgrath> a-k: you going to fudcon by chance?
20:01 < mmcgrath> #topic who's here?
20:01 < a-k> Nope. Sorry. It would probably be great.
20:01 * mmcgrath is
20:01 * ricky
20:01 -!- zodbot changed the topic of #fedora-meeting to: who's here?
20:01 * abadger1999 here
20:01 * a-k is
20:01 < mmcgrath> a-k: that's the nice thing about fudcons, there's always another one in the future :)
20:01 * SmootherFrOgZ is
20:01 < dgilmore> mmcgrath: present
20:01 < mmcgrath> SmootherFrOgZ: you fudconing it?
20:01 -!- tmz [n=tmz@fedora/tmz] has joined #fedora-meeting
20:01 < SmootherFrOgZ> mmcgrath: yep
20:01 < mmcgrath> excellent.
20:02 < Ac-town> ello'
20:02 * ricky will unfortunately be buried in finals/work for FUDCon/The Move :-(
20:03 < mmcgrath> ricky: that's ok, it happens.
20:03 < mmcgrath> well, lets get started.
20:03 < mmcgrath> #topic Meeting Tickets
20:03 -!- zodbot changed the topic of #fedora-meeting to: Meeting Tickets
20:03 * mmcgrath is slowly pulling it up
20:03 < mmcgrath> and no meeting tickets.
20:03 < mmcgrath> well that's easy
20:03 < mmcgrath> #topic FUDCon
20:03 -!- zodbot changed the topic of #fedora-meeting to: FUDCon
20:03 < mmcgrath> so lots of us will be at fudcon
20:04 < mmcgrath> who all at the meeting is going?
20:04 * nirik won't be making it this time, happy to hang out on irc if I can provide input for anyone/anything tho.
20:04 < mmcgrath> aww
20:04 * dgilmore will be tehre
20:04 < ricky> To all that are going, have a safe trip :-)
20:05 -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has joined #fedora-meeting
20:05 < mmcgrath> Well, hopefully nothing will go completely bad.
20:05 < mmcgrath> lets talk a bit about what infrastructure related stuff will be going on
20:05 < mmcgrath> J5: ping
20:05 < mmcgrath> lmacken: ping
20:06 * abadger1999 will be if thisplane gets me to BOS for the bus :-)
20:06 < mmcgrath> Will you guys be having any sort of moksha / fedora community hackfests?
20:06 < J5> mmcgrath: hey, I haven't planned any as I want to concentrate on the messaging stuff
20:06 < mmcgrath> ah, so a specific focus on getting plans ready for qpid?
20:07 < J5> mmcgrath: for me at least. I think luke is doing some moksh stuff
20:07 < mmcgrath> abadger1999: do you have any F-I specific hackfests?
20:07 < abadger1999> J5: You and Oxf13 leading that together?
20:07 < abadger1999> mmcgrath: At least jds2001 and I will be working on pkgdb together.
20:07 < J5> abadger1999: 0xf13 is running the hackfest and there are two other amqp talks
20:08 < abadger1999> mmcgrath: I want to work on a little light porting to amqp
20:08 < abadger1999> And then I'm running a Packaging Committee hackfest that may take most of my hackfest time.
20:08 < mmcgrath> yeah, I think mdomsch wanted a crash course in how to dance with amqp
20:09 -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has quit Remote closed the connection
20:09 < mmcgrath> I'm planning on having a virt_web hackfest for those interested in web based virtualization
20:10 < mmcgrath> but that's only mildly F-I related.
20:10 < SmootherFrOgZ> cool
20:10 < mmcgrath> that's really all I've got on FUDCon, anyone have anything else?
20:11 < mmcgrath> alllrighty
20:11 < mmcgrath> #topic The Move
20:11 -!- zodbot changed the topic of #fedora-meeting to: The Move
20:11 < mmcgrath> so yeah, did everyone see my announcement on this?
20:11 < mmcgrath> https://fedorahosted.org/fedora-infrastructure/ticket/1845 <--- there it is!
20:11 < mmcgrath> so I'm a little worried about how this whole move is going to go.
20:12 -!- easter_egg [n=freeman(a)201-75-22-126-ma.cpe.vivax.com.br] has quit "System going down for system halt NOW ><"
20:12 < mmcgrath> lots of stuff that was supposed to be done weeks ago is still not done.
20:12 < mmcgrath> and I have no ETA on when it will get done.
20:12 < mmcgrath> and this has thrown a massive wrench into our plans.
20:12 < mmcgrath> which is why the "Services still in question" in ticket 1845 is so large.
20:13 < Ac-town> What needs to be done?
20:13 -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has joined #fedora-meeting
20:13 < mmcgrath> Ideally, the 5 servers we have in the new colo would be powered on and networked right now.
20:13 < mmcgrath> That way I could do a dump and load of our databases on it.
20:14 < mmcgrath> we'd have a short down time for our databases.. but then on actual move day, they'd stay up.
20:15 < mmcgrath> Ac-town: but right now we're blocking on network.
20:15 < mmcgrath> and it's not a matter of getting an IP address for those hosts.
20:15 < mmcgrath> they have to design the new vlan, hook us up to the core switches, and expose us to the internet.
20:15 < mmcgrath> and I just have no idea the status of all that at this time.
20:15 < lmacken> mmcgrath: pong; yeah, I'm hoping to get people interested in a Moksha / Fedora Community hackfest
20:16 < mmcgrath> lmacken: coolz
20:16 < abadger1999> mmcgrath: Have they pushed out our timeline any more?
20:16 < abadger1999> (ie, no longer the end of the year to be moved) ?
20:16 < mmcgrath> abadger1999: nope. The move happens on the 12th.
20:16 < abadger1999> okee dokee
20:16 < mmcgrath> I've already got flight and hotel booked.
20:16 < mmcgrath> it's amazing to me this was supposed to be done in late november :-/
20:17 < mmcgrath> lmacken: is fedoracommunity only deployed in PHX?
20:17 < lmacken> mmcgrath: deployed on app1-7, iirc..
20:17 * mmcgrath wonders if since it doesn't have a data layer if it could be moed to the services that will remain up section.
20:17 -!- fraggle_ [n=fraggle(a)bea13-2-82-239-143-199.fbx.proxad.net] has quit Remote closed the connection
20:17 < mmcgrath> k, that's good.
20:18 < mmcgrath> So I guess for this to work we need just 2 things
20:18 < mmcgrath> 1) vpn
20:18 * ricky wouldn't be surprised if FAS being down cascaded into making fedoracommunity down or useless :-(
20:18 < mmcgrath> 2) databases.
20:18 < mmcgrath> ricky: that's a good question
20:18 < mmcgrath> abadger1999: if FAS is down, is anonymous browsing on our TG apps down?
20:18 < abadger1999> mmcgrath: yes
20:19 < abadger1999> mmcgrath: We might be able to fix that with tg2 but tg1 will gobust.
20:19 < mmcgrath> K
20:19 < mmcgrath> so lets prioritize the applications
20:19 * abadger1999 boarding
20:19 < mmcgrath> the account system has to be up or everything else doom sticks.
20:19 < ricky> abadger1999: Have a nice flight
20:20 < mmcgrath> the voting app should stay up because there's voting going on
20:20 < mmcgrath> abadger1999: be safe, wear shoes!
20:20 < ricky> Hehe
20:20 < abadger1999> Shoes? What are those?
20:20 < mmcgrath> armor for your feet!
20:20 < SmootherFrOgZ> haha
20:21 < mmcgrath> Oh! and mail
20:21 < mmcgrath> ugh
20:21 < mmcgrath> it's ok if zodbot isn't around for a while.
20:21 < ricky> Is there a legal issue related to mail>
20:21 < mmcgrath> ricky: there are.
20:21 < mmcgrath> I have a meeting with eric this afternoon about some of this stuff.
20:21 -!- pjones [n=pjones@fedora/pjones] has quit "Terminated with extreme prejudice - dircproxy 1.2.0"
20:21 < ricky> Would it be acceptible to route through Red Hat MXes from outside of PHX?
20:22 -!- SMParrish_mobile [n=smparris(a)32.128.93.244] has joined #fedora-meeting
20:22 < ricky> **acceptable
20:22 -!- pjones [n=pjones@fedora/pjones] has joined #fedora-meeting
20:22 < mmcgrath> ricky: that's on my list of questions for this afternoon.
20:23 < mmcgrath> I'm almost tempted to have pkgdb and bodhi in the down column just to help protect the data.
20:24 < mmcgrath> but bodhi is publically used to get info about security updates and things, and that is important.
20:24 < abadger1999> lmacken: Can bodhi survive w/out pkgdb up?
20:24 < lmacken> abadger1999: should be able to... update submissions won't work, obviously
20:24 < ricky> If bodhi is up, then db must be up, which means that fas/pkgdb can be up as well
20:25 -!- SMParrish_mobile [n=smparris(a)32.128.93.244] has quit Client Quit
20:25 < ricky> Will pushes continue to happen during the outage?
20:25 < lmacken> actually, it still may work w/o the pkgdb, but I assume koji will be done so it will break submissions anyway
20:25 < mmcgrath> ricky: the thing is they might be up on a grossly underpowered machine
20:25 < ricky> If not, then the email notifications from bodhi will be up to date
20:25 < ricky> Ah
20:25 < mmcgrath> ugh, this problem is so easy to solve if the hardware had been installed.
20:26 < mmcgrath> the other thing I'm not clear on is even if the network is online right now, will it stay online through the move?
20:26 < mmcgrath> For all I know they might be switching out gear during that time.
20:26 < mmcgrath> also on my list of questions...
20:26 < mmcgrath> anyway, does anyone have any other questions about this?
20:26 < abadger1999> mmcgrath: Do we need new update submission for security updates?.... thinking yes... unless we can just route everything through admins or something.
20:26 < mmcgrath> I suspect we'll be talking about it in greater detail.
20:26 < mmcgrath> abadger1999: I've been talking with releng about how to do an emergency package push if need be.
20:27 -!- ivazquez [n=ivazquez@fedora/ignacio] has joined #fedora-meeting
20:27 < abadger1999> k
20:27 < mmcgrath> since the whole buildsystem will just be gone, it's likely we'd be doing all of it out of band anyway
20:27 * ricky wonders when the netapp will be moved and what will go with that
20:27 < mmcgrath> but if a 0 day comes out for ssh as soon as we close the truck, I think we have a plan in place for it.
20:27 < mmcgrath> ricky: the netapp will be moved at the same time
20:27 < ricky> Ah, OK.
20:28 < ricky> Also just curious - will the move come with DNS changes for everything?
20:29 < mmcgrath> yeah
20:29 < ricky> Yow
20:29 < ricky> That's pretty big :-(
20:30 < ricky> So we'd probably need to change the netapp address and the internal bugzilla address and all of our other references to .phx.fedora.redhat.com :-(
20:30 < mmcgrath> yep, lots of major stuff going on and another reason it's so bad there's so many unanswered questions at this time.
20:31 < ricky> Er, fedora.phx.redhat.com
20:31 * ricky sees why running our own DNS would have been nice :-/
20:32 < mmcgrath> We actually will be running our own DNS by the end of this, but we'll still have to rely on their dns servers because they refuse to let us do outbound dns requests.
20:33 < mmcgrath> Ok, does anyone have anything else to discuss with that? If not I'll open the floor
20:35 < mmcgrath> ok
20:35 < mmcgrath> #topic open floor
20:35 -!- zodbot changed the topic of #fedora-meeting to: open floor
20:35 -!- mdomsch [n=Matt_Dom(a)24.174.2.245] has joined #fedora-meeting
20:35 < mmcgrath> a-k: how goes the great search search?
20:35 * nirik is happy to help with anything from here on the move or coverage while people are at fudcon.
20:35 < mmcgrath> nirik: thanks
20:36 < a-k> I don't think huzaifas has been able to evaluate candidates lately, but I need to follow up with him.
20:36 < a-k> I think we'll still have some candidates for public testing in January.
20:36 * ricky will try to be kind of around between finals studying
20:36 < bochecha> I wanted to add something about the search engine topic
20:36 < a-k> That's it from me, so take it.
20:36 < mmcgrath> bochecha: sure
20:36 * lmacken is working on some Moksha/Fedora Community demos for this weekend that use Fedora's AMQP broker.
20:36 < bochecha> don't know exactly where you guys are on the subject, but today at work I learned about Whoosh, a Python search engine that we're going to use for our apps
20:37 < lmacken> Hoping to get a lot of AMQP movement this weekend
20:37 < bochecha> it's not listed on the wiki page or the ticket in trac, so I thought I'd let you know about it, in case you hadn't considered it yet
20:37 < lmacken> bochecha: interesting
20:37 < mmcgrath> a-k: ^^ you guys looked at whoosh at all?
20:37 < bochecha> http://whoosh.ca/
20:37 -!- dwmw2 [n=ctrlprox(a)twosheds.infradead.org] has joined #fedora-meeting
20:37 < a-k> I can add it to the list.
20:37 < mmcgrath> cool
20:37 < mmcgrath> bochecha: thanks
20:37 < a-k> Most of the problems with search engines is they're just search engines.
20:38 < a-k> You have to write your own apps to interface with them.
20:38 < mmcgrath> yeah
20:38 < a-k> I'm trying to avoid those.
20:38 < mmcgrath> +1 to not writing and maintaining stuff we don't have to
20:38 < mmcgrath> Ok, anyone have anything else they'd like to discuss?
20:39 < mmcgrath> If not we'll close the meeting
20:40 < mmcgrath> ok
20:40 < mmcgrath> closing in 10
20:40 -!- brunowolff [n=bruno(a)cerberus.csd.uwm.edu] has joined #fedora-meeting
20:40 < mmcgrath> #endmeeting
20:40 -!- zodbot changed the topic of #fedora-meeting to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel for meeting schedule
20:40 < zodbot> Meeting ended Thu Dec 3 20:40:16 2009 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot .
20:40 < zodbot> Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2009-12-03/fedora-meeting...
20:40 < zodbot> Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2009-12-03/fedora-meeting...
20:40 < mmcgrath> thanks for coming everyone!
20:40 < zodbot> Log: http://meetbot.fedoraproject.org/fedora-meeting/2009-12-03/fedora-meeting...
14 years, 4 months
Elections and infrastructure
by Paul W. Frields
Although Mike McGrath and the Infrastructure team don't expect the
server relocation to affect our upcoming elections, we want to make
sure the community's ability to vote is not unnecessarily affected
given the timing.
The original voting period was December 8-15, and the infrastructure
move is occurring over the weekend of the 12th:
https://www.redhat.com/archives/fedora-announce-list/2009-December/msg000...
https://fedorahosted.org/fedora-infrastructure/ticket/1845
I talked this morning with Mike, John Rose, and Nigel Jones, and
here's the plan we arrived at:
* The voting period will start on December 5 instead of December 8.
This ensures that, no matter what unforeseen circumstances occur,
there will be a full weekend of uninterrupted voting time available
to all community members. All townhalls will be finished by that
point, since none are planned for FUDCon at this time.
* Although Mike and the Infrastructure team believe they can keep the
elections open throughout the move, in the event of any substantial
outage (8 hours or more), we will extend the end of voting by an
additional day. For any additional day of outage, we'll extend the
end of voting by another additional day. Again, we aren't expecting
to have to do this, but it's better for us to have a plan ahead of
time.
* Nigel is preparing a change to the elections app that will allow a
logged in user to check the accuracy of a previously recorded vote.
This will give an additional measure of confidence in the election
system, even in the event of a brief outage. If any user detects a
problem, they can report it via IRC, email to the infrastructure
list, or a Trac ticket.
* Mike is preparing a blog post to the Planet to further spread the
word about the infrastructure move. Nigel and I will also post blog
entries about the information you see here, and I'll send out
announcements to the appropriate mailing lists.
--
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/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 4 months
Reminder about the test servers
by Mike McGrath
If you are in sysadmin-test or have access to the publictest servers,
please note those servers aren't for general purpose whatever you want to
use them for servers.
You've been granted access to them to work on specific projects, if a new
project comes up please file an RFR and discuss on the list before you
start working on it.
-Mike
14 years, 4 months
