Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 18:00UTC (1:00pm EST, 19:00 CET) in #fedora-meeting on irc.freenode.net.
Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9
= Followups =
= New business = #topic #1110 systemd preset for ipmi .fesco 1110 https://fedorahosted.org/fesco/ticket/1110
#topic #1111 systemd preset for ipmievd .fesco 1111 https://fedorahosted.org/fesco/ticket/1111
= Open Floor =
For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9
If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.
Thank you, -Toshio (IRC: abadger1999)
On Tue, Apr 30, 2013 at 07:37:03AM -0700, Toshio Kuratomi wrote:
If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.
Please clarify the Guidelines for release names:
https://fedoraproject.org/wiki/Guidelines_for_release_names | Names must not contain any shell metacharacters.
This does not match the definition from man bash(1): | metacharacter | A character that, when unquoted, separates words. | One of the following: | | & ; ( ) < > space tab
IMHO best would be to just write "Names must not contain any of the following characters: <to be completed>" to avoid any inaccuracies.
Regards Till
On Wed, May 01, 2013 at 05:21:26PM +0200, Till Maas wrote:
On Tue, Apr 30, 2013 at 07:37:03AM -0700, Toshio Kuratomi wrote:
If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.
Please clarify the Guidelines for release names:
https://fedoraproject.org/wiki/Guidelines_for_release_names | Names must not contain any shell metacharacters.
This does not match the definition from man bash(1): | metacharacter | A character that, when unquoted, separates words. | One of the following: | | & ; ( ) < > space tab
IMHO best would be to just write "Names must not contain any of the following characters: <to be completed>" to avoid any inaccuracies.
Thanks, added as:
#topic Clarify release name guidelines - Explicitly list blacklisted characters
-Toshio
Le Mer 1 mai 2013 17:53, Toshio Kuratomi a écrit :
#topic Clarify release name guidelines - Explicitly list blacklisted characters
Since UTF-8 contains many glyphs with similar shapes and uses, the guideline needs to first explicitly state that release names must be encoded in UTF-8, and second list the forbidden glyphs with their codepoint number (to avoid ambiguities).
Once upon a time, Nicolas Mailhot nicolas.mailhot@laposte.net said:
Le Mer 1 mai 2013 17:53, Toshio Kuratomi a écrit :
#topic Clarify release name guidelines - Explicitly list blacklisted characters
Since UTF-8 contains many glyphs with similar shapes and uses, the guideline needs to first explicitly state that release names must be encoded in UTF-8, and second list the forbidden glyphs with their codepoint number (to avoid ambiguities).
I don't think so, because I don't think the shell recognizes anything but the 7-bit characters as "special".
Le Ven 3 mai 2013 15:17, Chris Adams a écrit :
Once upon a time, Nicolas Mailhot nicolas.mailhot@laposte.net said:
Le Mer 1 mai 2013 17:53, Toshio Kuratomi a écrit :
#topic Clarify release name guidelines - Explicitly list blacklisted characters
Since UTF-8 contains many glyphs with similar shapes and uses, the guideline needs to first explicitly state that release names must be encoded in UTF-8, and second list the forbidden glyphs with their codepoint number (to avoid ambiguities).
I don't think so, because I don't think the shell recognizes anything but the 7-bit characters as "special".
My point is precisely that only some glyphs with this look need to be blacklisted, so for people to know which squiggle is allowed and which squiggle is forbidden you need to explicitly state the codepoint of the forbidden squiggle.
On Tue, Apr 30, 2013 at 7:37 AM, Toshio Kuratomi a.badger@gmail.com wrote:
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 18:00UTC (1:00pm EST, 19:00 CET) in #fedora-meeting on irc.freenode.net.
Apologies, it was pointed out to me that the listed local time didn't
match up with current UTC. To figure out when the meeting is happening in your local timezone, please use:
date -d '2013-05-01 18:00 UTC'
from the command line or read http://fedoraproject.org/wiki/UTCHowto for graphical and online tools.
-Toshio
devel@lists.stg.fedoraproject.org