Announcing the Fedora 6 Zod live CD and live CD tools
by David Zeuthen
Hi,
After lots of feedback, bug fixing and testing of the beta live CD
announced 3 weeks ago, I'm pleased to announce the first official Fedora
live CD. This live CD is based on packages from the Fedora Core 6
(codenamed "Zod") and Fedora Extras package collections and is such 100%
free software. At a glance, the live CD features
o Linux 2.6.18
o GNOME 2.16 desktop environment
o GStreamer 0.10 multimedia framework
o X.org 7.1
o AIGLX and Compiz for 3D desktop
o Lots of applications including, but not limited to
o Beagle (Desktop Search)
o F-Spot (Photo Management)
o Evolution (Email and Calendering)
o Firefox (Web Browsing)
o Ekiga (IP telephony)
o Rhythmbox (Music Player)
o Totem (Movie Player)
o Games (Games)
o The Gimp (Graphics)
o Inkscape (Vector Graphics)
o Abiword (Word Processor)
o Gnumeric (Spreadsheet)
o nautilus-open-terminal (For the adult in you)
o Assistive Technology including the Orca screen reader
o NetworkManager is on by default
o VPN connectivity software including vnpc and OpenVPN
o Partition editing via GParted
o SELinux targeted mode including the SELinux trouble shooter
o Many many fonts; almost 100% coverage
o All the localizations included in FC6 and FC6
o All the input methods (SCIM) present in FC6
o Exclusive live CD wallpaper you won't find in FC6 or FE6!
o R/W file system so you can install software on the running live CD
o Ability to run from RAM if you have 1GB or more of memory
o and lots and lots more..
The live CD is currently only available for i386 architectures. Support
for other architectures including ppc and x86_64 is planned. The live cd
weighs around 682MB. Download from
http://download.fedora.redhat.com/pub/fedora/projects/live/FC-6-i386-live...
SHA1SUM: 8771d21af1974492424438cbe42f1bae0161ea96 FC-6-i386-livecd-1.iso
or get on the Torrent using
http://torrent.fedoraproject.org/torrents/Zod-livecd-1-i386.torrent
Feedback can be given in Bugzilla; file a bug against the component you
have an issue with.. and make it block this tracker bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=FC6LiveCDTracker
if you believe it's a live CD specific bug.
Don't get burned on Christmas shopping, burn the gift of a live CD!
====
This live CD is built using a source code based on the pilgrim project.
This is an open project and participation is encouraged and appreciated.
See these documents on how to get involved hacking on the code and what
it's all about
http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob;hb=H...
http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob;hb=H...
Participate on the Fedora Live CD mailing list and the Wiki page to make
the Fedora live CD experience even better
http://fedoraproject.org/wiki/FedoraLiveCD
http://www.redhat.com/mailman/listinfo/fedora-livecd-list
The livecd-tools and fedora-livecd packages, which is required to
rebuild the live CD, have just been submitted to Fedora Extras, see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220635
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220637
for details. Until these packages are in Extras, you can grab source and
binary i386 packages from here
http://people.redhat.com/davidz/livecd/
and start cranking out your own live CD's.
Thanks and a merry Christmas break to everyone!
David
16 years, 9 months
Announcing the Fedora 6 Zod live CD and live CD tools
by David Zeuthen
Hi,
After lots of feedback, bug fixing and testing of the beta live CD
announced 3 weeks ago, I'm pleased to announce the first official Fedora
live CD. This live CD is based on packages from the Fedora Core 6
(codenamed "Zod") and Fedora Extras package collections and is such 100%
free software. At a glance, the live CD features
o Linux 2.6.18
o GNOME 2.16 desktop environment
o GStreamer 0.10 multimedia framework
o X.org 7.1
o AIGLX and Compiz for 3D desktop
o Lots of applications including, but not limited to
o Beagle (Desktop Search)
o F-Spot (Photo Management)
o Evolution (Email and Calendering)
o Firefox (Web Browsing)
o Ekiga (IP telephony)
o Rhythmbox (Music Player)
o Totem (Movie Player)
o Games (Games)
o The Gimp (Graphics)
o Inkscape (Vector Graphics)
o Abiword (Word Processor)
o Gnumeric (Spreadsheet)
o nautilus-open-terminal (For the adult in you)
o Assistive Technology including the Orca screen reader
o NetworkManager is on by default
o VPN connectivity software including vnpc and OpenVPN
o Partition editing via GParted
o SELinux targeted mode including the SELinux trouble shooter
o Many many fonts; almost 100% coverage
o All the localizations included in FC6 and FC6
o All the input methods (SCIM) present in FC6
o Exclusive live CD wallpaper you won't find in FC6 or FE6!
o R/W file system so you can install software on the running live CD
o Ability to run from RAM if you have 1GB or more of memory
o and lots and lots more..
The live CD is currently only available for i386 architectures. Support
for other architectures including ppc and x86_64 is planned. The live cd
weighs around 682MB. Download from
http://download.fedora.redhat.com/pub/fedora/projects/live/FC-6-i386-live...
SHA1SUM: 8771d21af1974492424438cbe42f1bae0161ea96 FC-6-i386-livecd-1.iso
or get on the Torrent using
http://torrent.fedoraproject.org/torrents/Zod-livecd-1-i386.torrent
Feedback can be given in Bugzilla; file a bug against the component you
have an issue with.. and make it block this tracker bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=FC6LiveCDTracker
if you believe it's a live CD specific bug.
Don't get burned on Christmas shopping, burn the gift of a live CD!
====
This live CD is built using a source code based on the pilgrim project.
This is an open project and participation is encouraged and appreciated.
See these documents on how to get involved hacking on the code and what
it's all about
http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob;hb=H...
http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob;hb=H...
Participate on the Fedora Live CD mailing list and the Wiki page to make
the Fedora live CD experience even better
http://fedoraproject.org/wiki/FedoraLiveCD
http://www.redhat.com/mailman/listinfo/fedora-livecd-list
The livecd-tools and fedora-livecd packages, which is required to
rebuild the live CD, have just been submitted to Fedora Extras, see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220635
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220637
for details. Until these packages are in Extras, you can grab source and
binary i386 packages from here
http://people.redhat.com/davidz/livecd/
and start cranking out your own live CD's.
Thanks and a merry Christmas break to everyone!
David
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
16 years, 9 months
Announcing FUDCon Boston 2007
by Greg DeKoenigsberg
WHAT: Fedora Users and Developers Conference
WHEN: Friday, February 2nd, 2007
WHERE: Boston University, Boston MA, USA
===
On Friday, February 2nd, Fedora enthusiasts will gather at Boston
University for the annual appearance of the world-famous groundhog Fedora
Phil. According to legend, if Fedora Phil sees his shadow, there will be
six more weeks of Fedora test releases.
OK, so there's no groundhog. But there's no place like FUDCon to meet and
greet the luminaries of the Fedora community.
This year's FUDCon Boston will be a little bit different. We'll be
following the BarCamp model. A BarCamp is basically an "un-conference";
rather than have a bunch of canned tracks, the goal is to get a bunch of
interesting people together to discuss whatever they are passionate about.
Everyone gets together in the morning and pitches their own sessions. If
it's about Fedora, great. If it has nothing to do with Fedora, that's
great too. (Juggling is a popular session at a lot of BarCamps.)
Rest assured, though: there will be lots of sessions about Fedora. If you
want to learn more about Fedora, there's no better place on Earth to do
it.
If you're interested, sign up early: space will be somewhat limited. Just
go to the BarCamp wiki and add your name:
http://barcamp.org/FudconBoston2007#ATTENDEES
If you think you might be interested in running a session, put your
session proposal on the wiki:
http://barcamp.org/FudconBoston2007#SESSIONS
===
For those who are interested in deeper participation, we'll also be having
a hackfest on Saturday and Sunday. If you'd like to participate, respond
to me off-list for more information.
See you at FUDCon Boston 2007!
--g
-------------------------------------------------------------
Greg DeKoenigsberg || Fedora Project || fedoraproject.org
Be an Ambassador || http://fedoraproject.org/wiki/Ambassadors
-------------------------------------------------------------
16 years, 9 months
RPM -- plans, goals, etc.
by Max Spevack
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There has been a lot of discussion in the past few months about RPM -- its
present state, its future plans, and its leadership team. In particular,
the Fedora Project has received numerous requests asking us, "what are you
guys doing about RPM?"
Here is our answer, in a few words. Then if you want more, you can read
the rest of this note:
The Fedora Project is leading the creation of a new community around RPM.
One in which the leaders can come from Fedora, from Red Hat, from Novell,
from Mandriva, or from anywhere. Job #1 is to take the current RPM
codebase and clean it up, and in doing so work with all the other people
and groups who rely on RPM to build a first-rate upstream project.
==========
The Fedora Board has spoken with Fedora stakeholders both inside and
outside Red Hat, developers/maintainers in Novell, and other parties who
rely on RPM as the foundation for their distributions. We wanted to make
sure those parties agreed that this was the right thing to do for their
respective communities. We touched base with some of these people at the
recent LSB conference, and the overwhelming community opinion there was in
favor of what we are outlining here.
At the most fundamental level, we begin with two points:
(1) RPM is an important piece of technology, not just for Fedora or for
Red Hat, but for many other distributions and users. Its stability and
maintenance are critical.
(2) Red Hat realizes the need to build a strong community of contributors
around RPM, that the upstream of RPM needs to be handled in a manner which
allows contributors and developers to have maximum freedom in their
modifications, and that those modifications can be easily shared across
distributions.
Expanding on that:
(3) RPM, as a file format, is good at what it does and capable of being
the core of a Linux distribution. From the Fedora perspective, we are not
particularly interested in making any grand deviations from it at this
time.
(4) RPM, as an application, has a fairly mature feature set that we are
very interested in stabilizing and bug fixing. Furthermore, we want to
make sure that RPM is a stable and simplified base for the building of
other technologies on top of it. Down the road, we might be interested in
exploring a variety of new features, but we don't believe that should be
the initial focus of our efforts.
Ultimately, the Fedora Project and Red Hat are committed to seeing RPM be
as healthy and vibrant as many other large open source projects -- GNOME,
Xorg, etc -- consumed and contributed to by many companies, users,
distributions, and developers. Our overall goal for RPM is to ensure that
is has consistency, reliability, and stability.
We switch now to a handy Q&A format:
Q -- So what, specifically, are you doing with RPM? And where is the work
going to happen?
We have set up a new repository, wiki, and webspace -- external to any
distribution or company -- for RPM, to which anyone can contribute. A
reboot of the upstream, if you will. We don't expect that everyone will
be running the same version of RPM, or run with the same patches, but we'd
like for there to be a single place that everyone can refer to as
upstream, and be able to contribute patches.
There is already a contributor base that exists around RPM -- engineers
within Red Hat, Novell, Mandriva, and other organizations. We don't want
to leave those people behind -- we want to do a better job of
collaborating and accepting their work.
Everything will live at rpm.org, with a relaunched wiki, code repository,
and mailing lists. As for rpm.org itself, its hosting and maintainership
is outside of Red Hat, and is being generously provided by Duke
University.
Q -- How is that different from what currently exists?
What we're doing here is collecting together everyone who has a stake in
the future of RPM and building a healthy community around it. This
involves major bug fixing, development work, performance work and making
regular, predictable releases. As it stands today, we don't have these
things. This is a good first step. Could you call it a fork? Maybe. But
we're doing it because we think it's the right thing to do, for
distributions all the way down to the individual users of RPM.
Q -- Where is all this stuff going to happen? What's the public mailing
list and wiki? What *EXACTLY* is Fedora or Red Hat going to do?
Short answer -- http://rpm.org
Over the past few years, engineers from Red Hat and other companies, as
well as a community of independent contributors, have been working on and
maintaining their own versions of RPM -- sometimes sharing patches,
sometimes not. It is important that these contributions move through an
upstream process like many other projects do, in order to maintain a
healthy community and proper checks and balances.
To that end, Red Hat is adding an additional engineer that works full time
on upstream issues including patch reviews, community development, etc.
Additionally other Red Hat engineers will contribute to RPM like any other
open source project -- working on the release-engineering parts of RPM
such as rpmbuild, and doing maintenance work.
Additionally, here are some of our initial goals:
* Give RPM a full technical review, based off of RPM 4.4.2. This is the
common base for Novell and Red Hat. Look what vendors have on top of
4.4.2 and work towards a shared base. Figure out which pieces or code
paths are unnecessary, poorly implemented, or receive little to no use,
and either clean them up or clear them out. Make RPM simpler.
There's a lot of folks out there who are using RPM, including the various
Red Hat/Fedora based distros, Suse, and Mandriva, just to name a few.
Simplificaion and focus on the parts of RPM that are core to these
stakeholders is a good way to start.
* In turn, this gives us a chance to do a better job with bug fixes.
Squashing bugs that already exist, or closing out bugs that are related to
parts of RPM that are superfluous.
* Give RPM the stability that it needs to continue to be the cornerstone
of many distributions.
* Enhance the rpm-python bindings, which includes understanding and
gathering together the work that already exists in this area.
Most importantly, this work will be done in the community, fully
transparent with the help of the community and RPM stakeholders outside of
Red Hat or Fedora. This is all about incremental steps, not blowing
everything away and starting from scratch.
Q -- When is all of this happening?
Starting now. Planning and review happening over the next 3-6 months, at
rpm.org. Implementation happening appropriately alongside that planning,
as in most any free software project. Initially, Paul Nasrat is the
primary developer/maintainer dedicated to RPM from Red Hat. At the same
time, we want to make sure that leadership has a chance to develop and
emerge, rather than be mandated.
Q -- How did we end up here?
This is the part of the email in which Red Hat takes some accountability
for the current situation:
* Several years ago, the maintainer of RPM worked for Red Hat. When he
left, he continued his own work on RPM, which he acknowledges is a fork.
And that's fine -- we support anyone's right to fork, since forking is one
of the paths to innovation in open source software.
* Red Hat didn't commit the necessary resources to RPM following that
departure.
* RPM, without a strong upstream, has languished as a result.
* The community has (rightfully) been demanding that the situation be
fixed, and this is the first step in that effort.
- --
Max Spevack
+ http://fedoraproject.org/wiki/MaxSpevack
+ gpg key -- http://spevack.org/max.asc
+ fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFgYzyL9vLRloXzyERAtbwAJ9vvFk9JgiyIV0wmqcRNpS818NLGwCgnHX5
606VyFF7nCwtY24obdDN+ws=
=qQA7
-----END PGP SIGNATURE-----
16 years, 9 months
fedora project is hiring
by Max Spevack
As of today, Red Hat has an open position within the Fedora Project.
http://redhat.hrdpt.com/cgi-bin/a/highlightjob.cgi?jobid=1810
The job is for a Fedora Infrastructure leader. No point in writing more
here, since I wrote the job description that you'll read if you click the
link above.
There is no location restriction on this job. It can be performed from Red
Hat's headquarters in Raleigh NC, from our Westford MA office, or from a
remote location, as long as the person is willing to travel to Raleigh,
Westford, or various data centers as needed.
Hiring regulations *require* that anyone who is interested submit their
resume through the online application process. However, if you would *in
addition* send an email to me as well, that certainly wouldn't be a bad
thing.
--
Max Spevack
+ http://fedoraproject.org/wiki/MaxSpevack
+ gpg key -- http://spevack.org/max.asc
+ fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21
16 years, 10 months
