Plan for tomorrows (20070830) FESCO meeting
by Brian Pepple
Hi,
Please find below the list of topics that are likely to come up in the
next FESCo meeting that is scheduled for tomorrow, Thursday at 17:00 UTC
in #fedora-meeting on irc.freenode.org:
/topic FESCO-Meeting -- MISC -- extending mandate (permanent?) for EPEL
- nirik
/topic FESCO-Meeting -- Misc -- Automatic pushing of package updates
after 14 days? - nirik
/topic FESCO-Meeting -- MISC -- Review of new features status
http://fedoraproject.org/wiki/Releases/8/FeatureList- poelcat, jwb
/topic FESCO-Meeting -- Follow-up -- obsoleting kmod proposal:
http://fedoraproject.org/wiki/DavidWoodhouse/KmodProposal - dwmw2, f13,
|DrJef|
/topic FESCO-Meeting -- Follow-up -- Compat policy? - jeremy
/topic FESCO-Meeting -- Follow-up -- FESCo proposal template - f13
/topic FESCo meeting -- Free discussion around Fedora
You want something to be discussed? Send a note to the list in reply to
this mail and I'll add it to the schedule (I can't promise we will get
to it tomorrow, but we'll most likely will if we don't run out of time).
You can also propose topics in the meeting while it is in the "Free
discussion around Fedora" phase.
If your name/nick is on above list please update the status on the
Extras schedule pages in the wiki ahead of the meeting. That way all the
other FESCo members and interested contributors know what up ahead of
the meeting. And we will avoid long delays in the meeting -- those often
arise if someone describes the recent happenings on a topic directly in
the meeting while all the others have to wait for his slow typing...
Thanks,
/B
--
Brian Pepple <bpepple(a)fedoraproject.org>
http://fedoraproject.org/wiki/BrianPepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
16 years, 8 months
Re: Re: Zod -> Moonshine -> <blank>? Moonshine is a <blank>, <blank>
by Mike C
>On Thu, 16 Aug 2007, Matej Cepl wrote:
>I still think F8 should be called "Underline".
There is a nice chinese word "Moutai" which refers to a clear liqueur
but sounds almost the same as a Zulu word "muti" which refers to
medicine, but the word comes from the Zulu for "tree"... and the
Fedora tree of development would fit nicely into this thread, and has
international links as Fedora does!
So moutai is a suggestion for F8 if this is still being discussed?
--
mike cohler
16 years, 8 months
F8 Features--should they stay or should they go?
by John Poelstra
I would like to discuss the status of our features for F8 at tomorrow's
FESCo meeting.
https://fedoraproject.org/wiki/Releases/8/FeatureList
With Feature Freeze behind us on 2007-08-28 it is time to make some
decisions about what should live on the final approved feature list.
The feature policy is fairly clear about features that should be dropped.
see: http://fedoraproject.org/wiki/Features/Policy#drop
In accordance with this policy it would not be out of line to drop
features without recent updates or completion at 100%. Some of the more
incomplete (less than 50%) or stale features are called out in red.
Conversely if we follow this policy strictly, we will only have a few
features for F8.
https://fedoraproject.org/wiki/Releases/8/FeatureList
The easiest way for me to proceed would be to simply follow the policy
exactly as it reads, however I am sure there are cases where this would
do more harm than good. On the other hand I have made repeated requests
to some feature owners requesting updates with no reply. I also believe
that for us to build a consistent release process we need to be
consistent about doing what we say we are going to do--what is the point
of having a policy that we don't really follow?
Question for FESCo--do I have your support to follow the policy and
eliminate features not meeting the criteria or would we like an
exception process? If we would like to implement an exception policy it
should be simple enough to amend to our existing policy and for me to
track :)
Thank you,
John
16 years, 8 months
must send modifications license acceptable?
by Patrice Dumas
Hello,
In TeX Live there are at least 2 licenses with the obligation to send
modifications:
* This is dvips, a freely redistributable PostScript driver
* for dvi files. It is (C) Copyright 1986-2004 by Tomas Rokicki.
* You may modify and use this program to your heart's content,
* so long as you send modifications to Tomas Rokicki. It can
* be included in any distribution, commercial or otherwise, so
* long as the banner string defined below is not modified (except
* for the version number) and this banner is printed on program
* invocation, or can be printed on program invocation with the -?
* option.
For makeindex there is a rather classical license with:
"All modified versions should be reported back to the author."
There is a similar clause, with an additional condition, that the
assent of the copyright holders should be asked for in the
Academic Free License which is considered to be free:
http://opensource.org/licenses/academic.php
9. Acceptance and Termination. ............
If You distribute or communicate copies of the Original Work or a
Derivative Work, You must make a reasonable effort under the
circumstances to obtain the express assent of recipients to the terms of
this License.
I guess that this is considered to be free enough for Fedora, still it
seems to me that these license should be considered special, since a
patch cannot be distributed in fedora without contacting somebody, and
therefore the fedora contributors must be aware of these conditions
before touching the package. In the first 2 cases it is not that
problematic, since the change can be made without prior contact, but for
the AFL this could be very problematic, delay and complicate changes.
Lastly it seems to me that similar clauses renders the license GPL
incompatible. Am I wrong?
--
Pat
16 years, 8 months
installing more fonts by default for better international coverage
by Jens-Ulrik Petersen
Hi,
In the recent online I18n session at FUDConF8 there was some discussion
of installation defaults related to international language support, and
it was suggested that we should be installing more fonts by default to
get better desktop language display coverage out of the box.
So I would like to propose we start installing the following fonts by
default on the desktop:
fonts-ISO8859-2, fonts-KOI8-R, fonts-arabic, fonts-chinese,
fonts-hebrew, fonts-indic, fonts-japanese, fonts-korean, fonts-sinhala,
and xorg-x11-fonts.
I believe the mainstream commercial desktop OS's already do this.
dejavu-fonts and dejavu-fonts-experimental also occur in quite a few
language groups, so they might be worth including too?
Any comments or suggestions on this?
Jens
16 years, 8 months
kqemu inclusion in kernel
by Christopher Brown
Hi folks,
I've started playing around with virtualization at work and the first thing
I'd like to query is kqemu's lack of inclusion in the Fedora kernel. It was
GPL'd in February and although I realise Axel is packaging kmdl/kmods it
would be good to know if this is being queued up for mainline. If not then
can it be backported for Fedora kernels. If that is not possible then can it
be moved into the default repos to save users (me) bolting on another repo
(no offence Axel).
Please forgive dual list posting but I know DJ reads the kernel list and
might want to comment whereas I'm not sure AT does. And vice versa.
Regards
Chris
16 years, 8 months
2.6.23 and newer kernel and option ACPI_PROC_EVENT.
by Zdenek Prikryl
Hello,
In 2.6.23 and newer kernel is option ACPI_PROC_EVENT. By default is this option
disabled (in kernel-2.6.23-0.139.rc3.git10.fc8 is disabled), so file
/proc/acpi/event will not be created. But acpid and probably other user-space
daemons depend on this file, so option ACPI_PROC_EVENT should be set to "y".
So I would like to ask you, are there any others serious reasons for disabling ACPI_PROC_EVENT?
Thanks
Zdenek
16 years, 8 months
