From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 14: Line 14:
Dennis Gilmore announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000633.html</ref>:
Dennis Gilmore announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000633.html</ref>:


"There is an ongoing outage at this time in PHX2.  The exact start time is not yet known and the ETA to be fixed is not yet known.
"There will be an outage starting at 2010-07-09 22:00 UTC, which will last approximately 48 hours.


To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref> or run:
To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
or run:


date -d '2010-07-05 01:00'
date -d '2010-07-09 22:00 UTC'


=====Reason for outage:=====
=====Reason for outage:=====  
 
Migrating the underling storage used by koji.  as well as upgrading to koji
Several people are experiencing issues connecting to various Fedora
1.4.0
services (see below).  The cause for these issues seems to be network
related and it is impacting different people differently.  Some see packet
loss, other see complete connectivity loss and other still aren't having
any issues at all.
 
Some services listed as unaffected would have been impacted previously to
this announcement but as we became aware of the issue have made some
changes to bring those services back online. Those services include
bodhi, the account system, pkgdb, main website/wiki, community and
mirrormanager.


=====Affected Services:=====
=====Affected Services:=====
Buildsystem - http://koji.fedoraproject.org/


=====Unaffected Services:=====
BFO - http://boot.fedoraproject.org/
Bodhi - https://admin.fedoraproject.org/updates/
Bodhi - https://admin.fedoraproject.org/updates/
Buildsystem - http://koji.fedoraproject.org/
CVS / Source Control
CVS / Source Control
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
Docs - http://docs.fedoraproject.org/
Email system
Email system
=====Unaffected Services:=====
Fedora Account System - https://admin.fedoraproject.org/accounts/
Fedora Account System - https://admin.fedoraproject.org/accounts/
Fedora Community - https://admin.fedoraproject.org/community/
Fedora Community - https://admin.fedoraproject.org/community/
BFO - http://boot.fedoraproject.org/
Docs - http://docs.fedoraproject.org/
Fedora Hosted - https://fedorahosted.org/
Fedora Hosted - https://fedorahosted.org/
Fedora People - http://fedorapeople.org/
Fedora People - http://fedorapeople.org/
Line 62: Line 51:
Wiki - http://fedoraproject.org/wiki/
Wiki - http://fedoraproject.org/wiki/


Ticket Link<ref>https://fedorahosted.org/fedora-infrastructure/ticket/2255</ref>
Ticket Link<ref>https://fedorahosted.org/fedora-infrastructure/ticket/2266</ref>


Contact Information:
Contact Information:
Line 70: Line 59:
<references/>
<references/>


====Fedora 14 Feature Submission Deadline is One Week Away (2010-07-13)====
====REMINDER: Test machine resources for package maintainers====


John Poelstra reminded<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000630.html</ref> the community of the upcoming Fedora 14 feature submission deadline:
Kevin Fenzi reminded<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000634.html</ref> the community of the availability of test machine resources for package maintainers:


"This email serves as the last reminder for the Fedora 14 Feature Submission Deadline--Tuesday, July 13, 2010.  After this date newly
"Greetings.  
submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo.


Accepted Fedora 14 features so far<ref>https://fedoraproject.org/wiki/Releases/14/FeatureList</ref>
I'd like to remind package maintainers that there are some test machine resources they can use to help them in maintaining Fedora
packages.  


If you are a current feature page owner, thank you for submitting your feature for Fedora 14 and contributing to the next release of Fedora. If you haven't updated your feature page in the last month it would be a great help to every one if you would do so now.
See<ref>https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers</ref> for more information and FAQ.  


As we start to reach deadlines and test releases for Fedora 14, more and more people will query the feature pages.  We'd love to know that what they find is current and correct.
Recent changes include:


Thank you,
- I have added a RHEL6b2 test machine. This may help EPEL-6 maintainers check for packages or test/debug their packages.
John


More information:
- EOL Fedora release test machines have been taken down, but I still have the disk images, etc. If anyone needs some information about a
  Fedora 14 Schedule<ref>https://fedoraproject.org/wiki/Releases/14/Schedule</ref>
  F9, F10, F11 machine, contact me and I will try and bring up the instance for you to use on a temporary basis.  


  Fedora Feature Process<ref>https://fedoraproject.org/wiki/Features/Policy</ref>
Please see the above page or contact me directly for any more information.  


<references/>
Happy maintaining!


====Licensing Guidelines Update - Please Read====
kevin"


[[User:spot|Tom "spot" Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000631.html</ref> a revised Red Hat licensing guidelines:
<references/>


"Hello Fedora!
====Fedora 14 Feature Submission deadline is tomorrow (2010-07-13)====


Please take a moment and read this email. There's cake in it for you.
John Poelstra reminded<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000635.html</ref> the community of the July 13 deadline for features for Fedora 14:


Upon the advice of Red Hat Legal, we have slightly amended the Fedora Licensing Guidelines<ref>https://fedoraproject.org/wiki/Packaging:LicensingGuidelines</ref>. The following section has been added:
"The Fedora 14 Feature Submission Deadline is TOMORROW.  After tomorrow, newly submitted features will be targeted for Fedora 15 unless an
exception is granted by FESCo.


  Subpackage Licensing
Accepted Fedora 14 features so far<ref>https://fedoraproject.org/wiki/Releases/14/FeatureList</ref>.


  If a subpackage is dependent (either implicitly or explicitly) upon a
Thank you,
  base package (where a base package is defined as a resulting binary
John
  package from the same source RPM which contains the appropriate
  license texts as %doc), it is not necessary for that subpackage to
  also include those license texts as %doc.


  However, if a subpackage is independent of any base package (it does
More information:
  not require it, either implicitly or explicitly), it must include
  Fedora 14 Schedule: https://fedoraproject.org/wiki/Releases/14/Schedule
  copies of any license texts (as present in the source) which are
  applicable to the files contained within the subpackage.


*****
  Fedora Feature Process: https://fedoraproject.org/wiki/Features/Policy


Basically, what this means is this: If you maintain a package, and that package generates subpackages, then each subpackage must either include a copy of the appropriate licensing texts (as available in the source), or it must Require (either implicitly or explicitly) another subpackage which does include the appropriate licensing texts.
<references/>


Unfortunately, there is no good way for us to determine which packages are out of compliance with this new guideline and will need to be fixed. (If http://rpm.org/ticket/116 was ever implemented, it would be possible...) However, we can identify packages which are likely
====Meeting logs enhancement====
candidates to be affected by this change. Thanks to Seth Vidal, I was able to generate a list of packages and subpackages, sorted by
maintainer. The list was generated by querying rawhide for a list of source packages where:


* At least one subpackage was generated that did not have an exact name match to the source package name AND
Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000636.html</ref>:


* That subpackage did not depend on any other source packages.
"Greetings.  


Maintainers should look at the bottom of this email for the list.
Thanks to some scripting work from Mike Mcgrath, there's a enhancement to our meeting logs site available:


=====FAQ=====
You can now go to<ref>http://meetbot.fedoraproject.org/teams/</ref> and see a per directory listing of meetings grouped by their meeting name. This would allow you for instance to see all the fesco meeting logs and browse them at your leisure, without having to find the right dates for meeting by going to:<ref>http://meetbot.fedoraproject.org/teams/fesco</ref>


Q. Why are we doing this?
It's important that people running IRC meetings use the '#meetingname' command to name their meeting, and always keep the same name there so
A. The intent is to ensure that the appropriate license texts (as available in the source) are installed on the running system for all
the logs appear under the same team name moving forward.  
binary packages.


Q. Should I add explicit Requires: to another subpackage for the sole reason of complying with this new guideline?
Hopefully this helps people find and review logs of our meetings.  
A. No. You should not add Requires simply for this licensing requirement. Instead, you should include duplicate copies of the
relevant license texts (as available in the source).


Q. I thought duplicating files in a spec was forbidden?
kevin"
A. This is a permitted exception to that.


Q. You keep saying "as available in the source", what does that mean?
<references/>
A. It means you do not need to manually add license texts if they are not included by the upstream in the source tarball. However, if they are missing, you should ask upstream to add them.


Q. My package generates a -docs (or -javadocs) subpackage, which doesn't depend on any of the other subpackages, but the docs are under a
====Upcoming Bugzilla Changes: Rawhide Rebase====
different license from the code in the other subpackage(s), what should I do?
A. You should make sure that the -docs/-javadocs subpackage has the correct License: tag, matching the files included, and be sure that the
appropriate license texts are included as %doc in the -docs/-javadocs.


Q. My package generates a foo and foo-libs package. foo has the license files, and foo depends on foo-libs, but foo-libs doesn't have any
Jeff Raber announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000637.html</ref>:
license files in it. What should I do?
A. You have two options here. You can either move the license texts from foo to foo-libs or duplicate the license texts in both packages. Moving the license texts is an acceptable option in this case because it ensures that if foo-libs is installed, the license texts are present, and if foo is installed, it will pull in foo-libs, thus, the license texts are present.


Q. What is the capital of the Republic of Ghana?
"Greetings,
A. Accra.


Q. What happens if I don't do this?
I hope everyone is well. This e-mail is intended to inform you about the upcoming bugzilla changes happening around July 27, 2010 (Rawhide bug rebase) and what you need to do, if anything.
A. Well, eventually, I'll go through and make the change myself. You will also suffer a horrible horrible curse.


Q. Do I need to make this change in stable branches?
We will be automatically changing the version for most rawhide bugs to Fedora 14. This will result in regular bugs reported against rawhide during the Fedora 14 development cycle being changed to version ‘14' instead of their current assignment, ‘rawhide’.   This is to align with the branching of Fedora 14 from rawhide and to more accurately tell where in the lineage of releases the bug was last reported.
A. No, but you can if you want to. Rawhide is the only place that is a MUST fix.


Q. Do I need to push an update for this change?
Note that this procedure does not apply to bugs that are open for the ‘Package Review’ component or bugs that have the ''FutureFeature'' or ''Tracking'' keywords set. They will stay open as rawhide bugs indefinitely.
A. No, please don't. If you're already working on an update for other reasons and you want to do this (say, to keep the spec in sync with
rawhide), you can.


Q. Do I need to build (not just commit) this change in rawhide?
If you do not want your bugs changed to version ‘14‘, add the FutureFeature keyword. If you need help changing a large amount of bugs manually, we’d be glad to help. Stop by #fedora-bugzappers on irc.freenode.net and we’ll gladly help you.
A. Please do. Don't forget to bump the release and add a changelog entry.


Q. Why can't we just have a "fedora-licenses" package which has copies of all the licenses in Fedora and just always install it?
More about these processes is here<ref>https://fedoraproject.org/wiki/BugZappers/HouseKeeping</ref>
A. Maintaining that package would be a huge pain. We have a LOT of licenses in Fedora and they change all the time, often without notice.
However, if you'd like to write some code to help us minimize duplicate license files on the filesystem with a "common-licenses" package, then you should look at<re>http://rpm.org/ticket/116</ref>. Have I mentioned that I'd like that functionality added to rpm?


Q. Why don't you add that functionality to rpm?
Jeff Raber
A. Everytime I look at the rpm source code, blood starts dripping from my eyes, and it scares my newborn son, Jimmy. It also makes it hard to see the code.


Q. Some of the packages on your list don't need any changes to meet this guideline, what should I do?
Fedora Bugzappers volunteer triage team<ref>https://fedoraproject.org/wiki/BugZappers</ref>"
A. I'm sure there are some false positives here. Heck, _most_ of my packages which were flagged by this script did not need any changes, but
some of them did. The only way to be sure was to have an informed human check. Just let me know that you checked them and they're okay. Please do this by sending me email, either by replying to this email on the list or emailing me directly. Telling me via
IRC/AIM/Twitter/Facebook/Identi.ca/LinkedIn/MySpace/ICQ/CarrierPigeon just means I will forget about it.


Q. Hey, one of my packages didn't end up on your list, but it needed to be fixed to meet this guideline, why wasn't it on the list?
<references/>
A. There are plenty of other situations that we couldn't account for where a package would need to be changed to meet this guideline. If you
think about it for a while, I'm sure you can come up with some. The case that Seth scripted was simply the most common one I could think of.
 
Q. I fixed my packages! Now what?
A. Please email me (either in reply to this email on the mailing list, or in private) and let me know which packages you fixed.
 
Q. What about the packages owned by "orphan"?
A. Well, it sure would be nice if a provenpackager could check these packages and fix them as appropriate, then let me know (via email).
Thats the sort of thing that makes me feel like buying you a drink the next time our paths cross. But hey, if no one does it, I'll get to it eventually.


Q. What about new packages?
===Fedora User Announcements===
A. All packages from this moment onward must meet this requirement. New packages, old packages, red packages, blue packages.


Q. I have another question which you did not answer here?
A. Ask me, I'll do my best to answer.


Q. I'm confused by all of this?
A. Sorry. Let me know what you don't understand and I'll try to make it clearer.
Q. Why are you always making me do things?
A. Because I can! No, really, this is one of those "things we should have been doing all along", so we need to just bite the bullet and get
it done.
Q. Hey you promised me cake, I read all this way! Where is my cake?
A.
          )
        (.)
        .|.
        l7J
        | |
    _.--| |--._
  .-';  ;`-'& ; `&.
& &  ;  &  ; ;  \
\      ;    &  &_/
  F"""---...---"""J
  | | | | | | | | |
  J | | | | | | | F
  `---.|.|.|.---'
What? You thought the cake was a lie?
Okay. Here's the list of packages that I think might be affected by this. Reminder: You need to check these packages and fix any which need
fixing, then email me and let me know which ones you checked/fixed. Thanks!
Ed.: please see the original posting<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000631.html</ref> for the list of packages, as it is quite long. 
~spot"
<references/>


===Fedora Events===
===Fedora Events===

Revision as of 01:08, 15 July 2010

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Pascal Calarco

  1. ↑ http://lists.fedoraproject.org/pipermail/announce/
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/
  3. ↑ http://fedoraproject.org/wiki/Events

Fedora Development News

Outage: Koji upgrade/migration - 2010-07-09 22:00 UTC

Dennis Gilmore announced[1]:

"There will be an outage starting at 2010-07-09 22:00 UTC, which will last approximately 48 hours.

To convert UTC to your local time, take a look at[2] or run:

date -d '2010-07-09 22:00 UTC'

Reason for outage:

Migrating the underling storage used by koji. as well as upgrading to koji 1.4.0

Affected Services:

Buildsystem - http://koji.fedoraproject.org/

Unaffected Services:

BFO - http://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ CVS / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Translation Services - http://translate.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/

Ticket Link[3]

Contact Information:

Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000633.html
  2. ↑ http://fedoraproject.org/wiki/Infrastructure/UTCHowto
  3. ↑ https://fedorahosted.org/fedora-infrastructure/ticket/2266

REMINDER: Test machine resources for package maintainers

Kevin Fenzi reminded[1] the community of the availability of test machine resources for package maintainers:

"Greetings.

I'd like to remind package maintainers that there are some test machine resources they can use to help them in maintaining Fedora packages.

See[2] for more information and FAQ.

Recent changes include:

- I have added a RHEL6b2 test machine. This may help EPEL-6 maintainers check for packages or test/debug their packages.

- EOL Fedora release test machines have been taken down, but I still have the disk images, etc. If anyone needs some information about a 

 F9, F10, F11 machine, contact me and I will try and bring up the instance for you to use on a temporary basis.

Please see the above page or contact me directly for any more information.

Happy maintaining!

kevin"

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000634.html
  2. ↑ https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers

Fedora 14 Feature Submission deadline is tomorrow (2010-07-13)

John Poelstra reminded[1] the community of the July 13 deadline for features for Fedora 14:

"The Fedora 14 Feature Submission Deadline is TOMORROW. After tomorrow, newly submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo.

Accepted Fedora 14 features so far[2].

Thank you, John

More information: 

  Fedora 14 Schedule: https://fedoraproject.org/wiki/Releases/14/Schedule

  Fedora Feature Process: https://fedoraproject.org/wiki/Features/Policy
  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000635.html
  2. ↑ https://fedoraproject.org/wiki/Releases/14/FeatureList

Meeting logs enhancement

Kevin Fenzi announced[1]:

"Greetings.

Thanks to some scripting work from Mike Mcgrath, there's a enhancement to our meeting logs site available:

You can now go to[2] and see a per directory listing of meetings grouped by their meeting name. This would allow you for instance to see all the fesco meeting logs and browse them at your leisure, without having to find the right dates for meeting by going to:[3]

It's important that people running IRC meetings use the '#meetingname' command to name their meeting, and always keep the same name there so the logs appear under the same team name moving forward.

Hopefully this helps people find and review logs of our meetings.

kevin"

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000636.html
  2. ↑ http://meetbot.fedoraproject.org/teams/
  3. ↑ http://meetbot.fedoraproject.org/teams/fesco

Upcoming Bugzilla Changes: Rawhide Rebase

Jeff Raber announced[1]:

"Greetings,

I hope everyone is well. This e-mail is intended to inform you about the upcoming bugzilla changes happening around July 27, 2010 (Rawhide bug rebase) and what you need to do, if anything.

We will be automatically changing the version for most rawhide bugs to Fedora 14. This will result in regular bugs reported against rawhide during the Fedora 14 development cycle being changed to version ‘14' instead of their current assignment, ‘rawhide’. This is to align with the branching of Fedora 14 from rawhide and to more accurately tell where in the lineage of releases the bug was last reported.

Note that this procedure does not apply to bugs that are open for the ‘Package Review’ component or bugs that have the FutureFeature or Tracking keywords set. They will stay open as rawhide bugs indefinitely.

If you do not want your bugs changed to version ‘14‘, add the FutureFeature keyword. If you need help changing a large amount of bugs manually, we’d be glad to help. Stop by #fedora-bugzappers on irc.freenode.net and we’ll gladly help you.

More about these processes is here[2]

Jeff Raber

Fedora Bugzappers volunteer triage team[3]"

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000637.html
  2. ↑ https://fedoraproject.org/wiki/BugZappers/HouseKeeping
  3. ↑ https://fedoraproject.org/wiki/BugZappers

Fedora User Announcements

Fedora Events

Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (June 2010 - August 2010)

  • North America (NA)[1]
  • Central & South America (LATAM) [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]
  1. ↑ http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29
  2. ↑ http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2
  3. ↑ http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3
  4. ↑ http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4

Past Events

Archive of Past Fedora Events[1]

  1. ↑ http://fedoraproject.org/wiki/FedoraEvents/PastEvents

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Announcements&oldid=186402"