Myself Vijay Gharge from Mumbai, India. I am avid linux user and am using
linux since 2004.
Currently am working with telco / isp and am hanlding servers running linux
mainly RHEL as well as providing telco application support.
I spend most of the time on linux networking, bash & perl scripting, os and
application installations along with basic c, php knowledge.
Am interested assiting / contributing to the open source community. Kindly
guide me towards putting my efforts in open source contribution!
I'm planning to do a partial mass-rebuild for Python 2.7.
This would cover all Python 2 users within the distribution, roughly
Some notes can be seen at:
I hoped to start this tomorrow (2010-07-21) at 16:00 UTC, but it looks
like I need to wait until at least after the outage that's due for that
time . Further, I'm still waiting to hear back to see if the build
should be done with the "gold" linker, rather than "gnu-ld" . I will
delay the build until after a decision is made on this.
This may mean that I'll wait until 2010-07-22.
Some areas of uncertainty remain:
- the script to do this, as written, assumes no build ordering is
needed. I know that some ordering is needed, and plan to manually order
the first four builds which I hope is the bulk of it, but it's not clear
to me if more is needed; I'm running some tests to try to better
Hope this makes sense
Start End Name
Tue 03-Aug Tue 17-Aug Alpha Infrastructure Change Freeze
Have you found something that is working really well in your schedule?
Or maybe you've found something you believe would work better in the
Update the schedule retrospective page now to capture all of the
important details as they happen:
As per http://fedoraproject.org/wiki/Infrastructure/GettingSponsored I
am removing from both the waiting queue and the testers list
administrators who have either been waiting for a long time or have
not logged into the test systems in the last 3-6 months.
This is meant to be routine security audit and not punitive.
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines
So it is probably time to have a dev.fedoraproject.org. Why? Well,
toshio had mentioned having others do some of the 'sysadminy' tasks so
developers can focus on development.
Also Luke had an analogous request wrt community and staging but before I
go setting things up some topics for discussion:
1) Security staging and production are identical. Since production data
regularly gets migrated to staging people that have access to one, might
as well have access to the other. Generally our staging environment is
mostly used for integration work, some load work as well.
2) Should we run development from rpms that get edited (like live patches)
or should we run them from scm(ish) checkouts. I generally vote for the
latter as it feels more useful in a development lifecycle. But we should
come up with a quick standard for how to store this stuff. something like
3) I don't want this to be all fancy. All of our apps run in their own
namespaces so we should be able to get by with one or two app dev servers
and we should be able to use them without a reverse proxy.
Questions comments? It'd be nice to just throw them all together on a
couple of hosts in their own namespace. It'll help find issues with them