Search results

[12:28] <abadger1999> Is octave ready? [12:30] <spot> would someone like to talk to Alex and/or Orion to see if its ready?

...ease leave it as type "New' so that it can be evaluated to be promoted to "Ready"

# Quite unlikely to be ready for Fedora 12

We're now ready to roll the creation of an official Fedora Live CD into the Fedora release

15:00 <@mmcgrath> Alllright, we ready to have a meeting? 15:20 < dgilmore> mmcgrath: i think postfix is ready

...|| RahulSundaram || Time critical. Within 10 days maximum. Will have to be ready for FC5. See [https://www.redhat.com/archives/fedora-marketing-list/2006-Ma

# The Feature Wrangler reviews page for completeness and marks it as ready for review at FESCo's next meeting by changing it to [[:Category:FeatureRea

...ory and module information are registered in Transifex, and the project is ready to accept translation submissions. ...file containing Mike's translatable messages and works on them. Once he is ready to submit them, he selects his file for upload in Transifex, writes a short

...n the path to helping the Fedora Infrastructure group and then when you're ready for more, read through the [[Infrastructure/GettingStarted#What_do_I_do_nex * When you are ready to send your [mailto:infrastructure@lists.fedoraproject.org introduction to

...finished quickly. There will be minimal number of packages after they are ready with customizations. The whole system will be less vulnerable to attack. <!-- When your feature page is completed and ready for review -->

* According to [[ReleaseEngineering/Meetings/2007-apr-16]] believed to be ready for F7 (16-APR-07)

...an mature, enterprise-grade, fault tolerant, multi-hyerpvisor, production-ready IaaS platform. <!-- When your feature page is completed and ready for review -->

(18:36:11) ClausReheis: but for the rest I am ready

...{{result|fail|te_IN}}||||Add new VM dialog box has untranslated messages, "Ready to begin installation of ", "Gb available in the default location" and coup

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...s of moving the rest of our websites to this setup. When you have changes ready post them somewhere! Your fedorapeople.org storage site is a PERFECT place

* Get the compiler packages ready.

[11:27] <spot> alright, thats all the items which are ready for review right now (SysVInit and EclipsePlugins still need attention from [11:28] <spot> which isn't even remotely ready.

<!-- When your feature page is completed and ready for review -->

...n on the new release, demos, speeches and, at last, but not least, friends ready to answer all your questions.

[12:25] <scop> let's do the whole shebang when it's ready [12:29] <scop> at least ready for discussion

...f folks want to help out beforehand. Here is a list of packages currently ready to be reviewed: https://bugzilla.redhat.com/buglist.cgi?quicksearch=mingw32

* Status: Everything is ready from the event organizer * i don't think new fc5 media will be ready for this date, if they can, i may ask for some.

The benefit is to show that Fedora is ready for deployments in the real world where economics values are produced, eg. <!-- When your feature page is completed and ready for review -->

...g on introducing a more KDE native application as a replacement once it is ready, but that may not happen as part of this change. <!-- When your change proposal page is completed and ready for review and announcement -->

14:59 < mmcgrath> Yo, we about ready to have a meeting? 15:02 < mmcgrath> Ready for a meeting?

The Fedora for Power team is ready to take the cat out of the bag for the beta release of Fedora 19, "Schrödi

...irror. The interface being simple will not require much efforts to produce ready to use fedora for the administrators.

* The Eclipse SDK itself is ready to go with 3.2.2. Ben Konrath is tracking down a recently-introduced gcj p

! Ready

** Live USB Creator for Linux (pretty much ready, currently [https://copr.fedorainfracloud.org/coprs/mbriza/liveusb-creator/ ** Live USB Creator for Windows (pretty much ready, we just need to get a signing key)

When the mentor is comfortable that the candidate is ready to become a full ambassador, the ''Mentor Status'' should be updated to 'Me

...or off, so if you're really busy you can block incoming chats until you're ready for them. You can also interact with your friends via a messaging tray buil Fedora 16 introduces HekaFS, a cloud-ready version of GlusterFS that includes additional authentication & authorizatio

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

Where there are certain drivers which are almost ready to be merged upstream and which Fedora would benefit from shipping, we have

<!-- When your spins page is completed and ready for review,

Screenshots of upcoming Fedora Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use t

[12:42] <spot> PackagingDrafts/Lisp still isn't ready, i need to spend some time working on that one with the author ...hall I just post a message to the packaging-list when I've got a new draft ready?

<!-- When your change proposal page is completed and ready for review and announcement --> ...is not regression. The infra & configurations changes for Pungi should be ready.

* (Will link to material on libvirt.org when it is ready). <!-- When your feature page is completed and ready for review -->

...X11], [http://bugs.freedesktop.org/show_bug.cgi?id=39295 accountsservice]) ready. <!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

The parts of OpenStack that are ready will be included in Fedora. There is no special contingency plan required. <!-- When your feature page is completed and ready for review -->

# '''PR ready''': the code migration is done and under review

...colspan="2" style="color: #407a40">Probably F21 or F22 before it's really ready</td></tr>

...ing the event owner for the release event to offer the $100USD that Max is ready to send them.</td></tr> ...an="2" style="color: #488888">right, but I don't want to penalize the ones ready for money while we wait for the other 2</td></tr>

* The code is not ready for Thrift v0.9.1 available in Fedora 21, however Flume code can builds usi

...it will not keep Fedora 19 from being released if OpenShift Origin is not ready. ...igin are independent of each other and the release. If a cartridge is not ready in time, it can be skipped.

...kal> email was fine .. I'll start pushing people to get some presentations ready 15:14 < marek> spevack: DVDs are already in the office, ready for fudcon :)

| [[User:vanhonit| Hon Nguyen]] || Ready to share || 02/27/2014 || 03/03/2014 | [[User:bckurera| Buddhike Kurera]] || Ready to share (with Uditha?) || 02/27/14 || 03/03/14

Have a functional, working spin ready, which allows the user to use the various educational open source applicati

* '''The bodhi2 cli isn't ready yet, but is being worked on''' - Until the full bodhi2 cli is available you

! Ready

==== Is Wayland ready? ====

* ia64 is almost ready to do an F9 release | style="color: #407a40" colspan="2" | ia64 is ready to do an F9 release, well almost. They need us to issue an updated fedora-

If the feature isn't ready upstream in time, it will not be part of our xorg rpms. <!-- When your feature page is completed and ready for review -->

...update to the protocol, the existing mDNS/DNS-SD standards can serve as a ready replacement and actually has been used in CUPS for many years now. If this feature is not ready by the deadline, revert back to cups-1.5.4.

<!-- When your feature page is completed and ready for review -->

No other packages depend on this feature (and vice-versa). If not ready the associated lvm2 thinp code, if included in lvm2, will error out accordi <!-- When your feature page is completed and ready for review -->

* get my English blog ready

Screenshots of upcoming Fedora Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use t

* Get Conga interface ready for manipulating the various config files (/etc/cluster/cluster.conf, /etc/ <!-- When your feature page is completed and ready for review -->

...uplication_service|ABRT Test Day on 2012-04-26]], page does not look to be ready yet ...to poke abrt team about the test day planned for 04-26 and ensure they're ready in time or it is postponed

* The Polkit1 Authentification agent is not ready to use with KPackageKit.

** Investigate replacing network initscripts with systemd-networkd (if it is ready; ifcfg-* file compatibility is probably a requirement) <!-- When your change proposal page is completed and ready for review and announcement -->

* Michael asks: Do we have concrete plans on how to make sure that FE5 is ready with the release of FC5? (For instance, to document whether and when to reb

# Be ready for RHEL beta testing before the alpha snapshot is taken, gaining another t # Ship your enterprise-ready version with the RHEL GA.

* ok we are ready for everything i think, we had a meeting yesterday evening ...'t have any schwag, i asked for some but i was answered that they won't be ready for the event

<!-- When your feature page is completed and ready for review -->

...r block device has SUBSYSTEM="block", and is basically the "this device is ready" event.

<!-- When your feature page is completed and ready for review -->

19:00 < thl> | everyone ready for FESCo meeting? 19:00 * | scop is ready in a few minutes, don't wait

<!-- When your feature page is completed and ready for review -->

...ays try to have GlusterFS as a guide in the project I participate and I am ready to do what will be need to get everything done in time since I will be cont

these were actually ready only on the last day of the expo (Saturday

** Package nearly ready, using Debian's build.xml to avoid need for maven ** Packages nearly ready (no dependencies)

[16:29:40] mspevack: ok, well I'm about ready to call the meeting adjourned, unless anyone has random questions for me.

The purpose of this spin is to create a ready-to-go development environment for contributing to educational projects insi ...n project, but never found the time to set up and get started? We've got a ready-to-go contributors' (not just code!) environment for you!

...or surely witch room will be ours. Luckily the first scheduled room wasn't ready for us, but few moments later we have received the new one, thanks to the L

Screenshots of upcoming Fedora Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use t

<!-- When your feature page is completed and ready for review -->

...to help review the packages and the kick-start files as and when they are ready.

...user will be informed about available updates only once they are actually ready to be installed. <!-- When your feature page is completed and ready for review -->

...s or construct yourself those abstract questions then the presstext is 90% ready! development the spin was ready now.

...concept of this plugin. This feature will polish that further and make it ready for general use. (See also this [https://bugzilla.redhat.com/show_bug.cgi?

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

Mark your calendars, and get ready to go exploring: The release of Fedora 16, codenamed "Verne," is scheduled ...oved features to support cloud computing, including '''HekaFS''', a "cloud ready" version of '''GlusterFS''', including additional auth*/crypto/multi-tenanc

<!-- When your change proposal page is completed and ready for review and announcement --> Projects that are not ready to port to pydantic v2 may use the <code>pydantic.v1</code>

* Ready by KO/Calligra 2.4

The computer is now ready for use.

* 3D support will not be provided, it's not ready for end-users on any chipset. <!-- When your feature page is completed and ready for review -->

The computer is now ready for use.

# Be ready for RHEL beta testing before the alpha snapshot is taken, gaining another t # Ship your enterprise-ready version with the RHEL GA.

#*# Week 1: Get ready with Package Splitting and packaging methods. Pick up packages to be split #*# Week 1: Get ready with Package Splitting and packaging methods. Pick up packages to be split

...nt_project/show/google/gsoc2009/redhat/t124024692194). It will be useable (Ready for consumption) by the end of GSoC period. It is not a big change to the d <!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

== Procedure when Ready for Publication ==

...ortant | Don't forget! | Feel free to join us actively again, once you are ready to!}}

...ntinue to be shipped in KDE 3 versions as long as the KDE 4 version is not ready. In future versions of Fedora, these will be gradually replaced by KDE 4 ve

...| JeremyKatz || 2006-11-16 || We're pretty sure that Red Hat management is ready to make this move, but we need to go over our plans with them, just in case

If the NetworkManager implementation is not ready, we may still provide the libvirt initscripts backend. In order to use this If the libvirt side is not ready, but the NetworkManager bits are then at least we can stop telling people t

* Upstream will also look at dropping individual features if they are not ready in time

<!-- When your feature page is completed and ready for review -->

The Fedora brand needs some minor updates to make it Publican 4 ready. Probably just book titles in HTML, and renaming a CSS file for the -web su ...ican 2 running on it so that we can stage documents there that are not yet ready for even the "drafts" section of the main docs site. The most important use

<!-- When your feature page is completed and ready for review -->

* Activities plan must be ready by 05 Oct 2014

.../www.transifex.net/projects/p/firstboot transifex]|| THIS IS CURRENTLY NOT READY TO TEST ....com/projects/p/system-config-firewall transifex] || THIS IS CURRENTLY NOT READY TO TEST

#** koji-mash integration (if ready) ...p://denver.car2go.com/ car2go], multiple cars parked outside of our venue, ready to go

| '''Make new cloudlet ready (with 2-3 nodes) with latest OpenStack and make available for testing''' || | '''MirrorManager 2''' The code is mostly ready, we just need a few more tests and a deployment plan. || [[User:Pingou | Pi

* A docker container running track, ready to deploy on short notice with minimal efforts.

#*# Week 1-Week 2 : Get ready with all the requires shell scripts for ftp, samba and nfs shares.

** This decision needs a stand-alone wiki page for ready reference--we shouldn't be referring to mail archives for things like this

...e no impact on unrelated packages or the system as a whole if they are not ready on time. <!-- When your feature page is completed and ready for review -->

** If support in anaconda for kernel-core is not ready in time, it should ship without it. The main change would not be affected b <!-- When your change proposal page is completed and ready for review and announcement -->

...n on the new release, demos, speeches and, at last, but not least, friends ready to answer all your questions.

(10:35:27) iWolf: Estimated budget should be ready by this weekend.

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

Python implementation is not yet ready, will be provided later. Python implementation is not yet ready, will be provided later.

Ready to get your free preview sample? Go ahead and swipe one straight from the

* Have a USB image burning device ready

...to help review the packages and the kick-start files as and when they are ready.

...release has been fully tested and approved at the "Go/No-Go" meeting it is ready for release to the Fedora mirrors.

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

The booth has to be ready at Wednesday, Max 11th at '''09.00''' (9am). Booth setup will take place on

* being ready/having the capacity to help out users with migration of their custom legacy <!-- When your change proposal page is completed and ready for review and announcement -->

Where you can find all kind of ready prepared Marketing Material, Talking Points, Projects, pressmaterial, etc.

#* '''GOAL:''' Determine if draft is ready for final review, and if so, move to Pending Review status

<!-- When your feature page is completed and ready for review -->

...-on demonstration, for the latter many software packages are installed and ready to be used immediately. <!-- When your spins page is completed and ready for review,

<!-- When your change proposal page is completed and ready for review and announcement -->

Now Your virtual machine should be ready, open Boxes on the receiving / destination computer and turn it on

<!-- When your feature page is completed and ready for review -->

* Proposal owners: The developers must get a kickstart ready for a big data image that has the Hadoop ecosystem installed and configured <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

* ''martix to ensure spice test day is ready on time'' - it was ready and went ahead fine ...and [[Test_Day:2013-06-06_FreeIPA_Two_Factor_Authentication]] both looked ready to go, kparal was working on a live image for NM test day

** Article in CommBlog. - Draft ready, review pending.

* Disable/remove func. Should be ready to do.

<!-- When your change proposal page is completed and ready for review and announcement -->

...ork, and how the Fedora community might differentiate this Spin from other ready-to-use i3 implementations already in the open source ecosystem. ...solicit early feedback. An excited group of users in our IRC/Telegram are ready to help.

<!-- When your change proposal page is completed and ready for review and announcement -->

Now your ready to extract the tarball using the graphical user interface or the following

Screenshots of upcoming Fedora Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use t

<!-- When your feature page is completed and ready for review -->

# Put in any idea that helped you as a mentor determine if a student is ready to work on your project. It could be coding, packaging, writing, or other

...n the 'exclude' button, so as to see a dialog opened, with a wide text box ready to receive your package names.

14:59 <@mmcgrath> Meeting! You guys about ready? 15:20 < dgilmore> speaking of ldap. FDS should be ready Very soon now for a review for Fedora

<!-- When your feature page is completed and ready for review -->

...n on the new release, demos, speeches and, at last, but not least, friends ready to answer all your questions.

|Final release slogan is ready for websites/design

...s working out a way for the rawhide build/sync process to signal that it's ready for smoke testing</td><td class="time">13:15</td></tr> ..." style="color: #407a40">notting: we can't tell $process when the bits are ready in RDU</td><td class="time">13:18</td></tr>

** Assess whether CMake upstream is ready, possibly help patch the holes <!-- When your feature page is completed and ready for review -->

** The modules required have already been packaged and are ready for review, see {{bz|800720}}. |Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review.

<!-- When your change proposal page is completed and ready for review and announcement -->

When an agent is ready to work on the ticket that agent should lock the ticket by selecting the "l

...n on the new release, demos, speeches and, at last, but not least, friends ready to answer all your questions.

=== New Documents Ready for Translation === looking good", which are ready for packaging.

<!-- When your feature page is completed and ready for review -->

...e no impact on unrelated packages or the system as a whole if they are not ready on time. <!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...to help review the packages and the kick-start files as and when they are ready.

<!-- When your feature page is completed and ready for review -->

|Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review. ** eclipse, eclipse-wtp (when ready), eclipse-jboss-tools (when ready)

...dora Power Team is pleased to announce the release of Fedora 22 for Power, ready to run on your next generation servers. Fedora 22 is a game-changer for th

The parts of OpenStack that are ready will be included in Fedora. There is no special contingency plan required.

<!-- When your feature page is completed and ready for review -->

...nd ensure [[Test_Day:2013-03-28_System_Certificates]] will be in shape and ready to go ahead for Thursday, or delay the event'' - the Test Day went ahead as * [[Test_Day:2013-04-02_OpenStack|OpenStack Test Day]] was ready to go, but announcement mails had not been sent out

LXDE should be ready for Fedora 10 <!-- When your feature page is completed and ready for review -->

...task schedule] for upcoming version, the beta release announcement must be ready to occur on release day. Work on the announcement can begin at any time but

Virtualization users will have a more production ready mechanism for snapshotting than QEMU previously supported (no loss of uptim <!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...56.php Migrating from PHP 5.5.x to PHP 5.6.x] (work in progress, should be ready for final) <!-- When your change proposal page is completed and ready for review and announcement -->

* According to [[ReleaseEngineering/Meetings/2007-apr-16]] believed to be ready for F7 (16-APR-07)

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

Documentation of the collection will be provided as soon as collection is ready. <!-- When your change proposal page is completed and ready for review and announcement -->

If the feature is not ready in time, it will simply not be included in F13, and nm-applet will appear a

...19 15:29:39 tchung Good news. we now have F7 DVDs and LiveCDs produced and ready to ship.

This section is for packages which will most likely not be ready in time for Fedora 9. It is kept separate to make it clear that these packa

...eally needed. The Rails 3 rpms and dependency tree is built, verified, and ready to go. Just working its way through the Fedora process now. Should a blocke

<!-- When your feature page is completed and ready for review -->

* If XI2 is not ready for 1.7 or xorg-x11-server-1.7 is not ready in time for F-12, we stick with the current version 1.6.

* my report on (LinuxTag) is ready and in review at Florian;

...a "preview" - significant functioning code is shipping, but we are not yet ready to finalize everything and declare that all interfaces and data formats are <!-- When your change proposal page is completed and ready for review and announcement -->

...and Push to updates-candidate || || Needed some time before docs.fp.o so ready for beta compose ...|| Apr 23 we will begin building the release RPM so any translations not ready by then will not make it to GA

...les will be announced on the Fedora mailing lists and planet when they are ready.

...e="color: #407a40" colspan="2" | how do we start?! LaserJock: we're almost ready with a spin for F9 | colspan="3" | * sdziallas suggests to get this preview release ready, try to do kind of PR (get more people in here! :) and move on then

<!-- When your feature page is completed and ready for review -->

...ady to the Whiteboard field, indication that the review request is not yet ready, because of some issues they report. After you have addressed them, please ...elps other possible reviewers to notice that the review request is not yet ready for further review action.

...e if any of GitLab's gems are already packaged. Kastello has many packages ready for EPEL6, so it will be helpful later when packaging for EPEL begins. Wrap up things and get ready for the midterm evaluation. Modify current objectives based on what achieve

** builds can be started once kde tag is ready

...ar. When your splash screen (if you have one) disappears, your desktop is ready for use. You can now launch applications to access the Internet, manage fi

<!-- When your feature page is completed and ready for review -->

We are now ready for testers to take part in dist-hg evaluation. Please let JesseKeating kn ...can make changes to the spec file, bump the revision, etc... when you're ready to commit and push changes to the server:

...to poke abrt team about the test day planned for 04-26 and ensure they're ready in time or it is postponed'' | style="color: #407a40" | OK, who's ready for some qa meeting awesomeness?

*** Basic python library for cryptsetup entrypoints is ready

...lized translations for UNetbootin (current version is English-only, but is ready for translation via Qt Linguist).

* '''If you are ready to provide your own CD/DVD, please refer to [[Distribution/FreeMedia/India/

* Work with 3rd-party repo owners whenever possible to help them get ready for F7

# '''QtAda''' - Ada bindings for QT - ''ready for review'' <!-- When your feature page is completed and ready for review -->

...is currently in final stages of preparation for beta 2 release. Should be ready for GA on target with Fedora 15 as of 02/03/11. <!-- When your feature page is completed and ready for review -->

...ething else. It's OK to step away for a few minutes until you feel you're ready to help again. Better that the channel go understaffed for that time than

Once you're ready to again activate the new p11-kit module, use:

...at one place is very difficult. The proposed project will help in creating ready-made image(s) with the required packages and pose a solution for the proble

<!-- When your feature page is completed and ready for review -->

Watch the page to see when is taken/completed. If needed submit when ready to [[MailTo(admin AT fedoraproject DOT org)] ...start working on a new graphic change the status to reflect is taken. When ready, change the status again and either submit the graphic to [[MailTo(admin AT

<!-- When your feature page is completed and ready for review -->

...colspan="2" | Well everything is getting ready slowly as usual. But we are ready and will have 8 ambassadors on the booth, which is huge :) &lt;MrTom&gt; i' ...se media from the same order as for the other European events. Posters are ready and we will get banners, too. &lt;fabian_a&gt; Is there anyone who would li

...n on the new release, demos, speeches and, at last, but not least, friends ready to answer all your questions.

<!-- When your feature page is completed and ready for review -->

...socket file and wait until it is available before reporting the service is ready. Using this and other refinements one has a good chance of being able to ma ...w in the process. Saying that 'just becuase the process exists', that it's ready is broken. Wait for the daemon to return. Or the script that you launch to

|<ul><li>The first module is ready for further testing by the organization and then deployment.</li></ul> |<ul><li>The second module is ready for further testing by the mentors and then deployment.</li></ul>

Since this is brand new functionality, if it isn't ready in time, nothing has changed. We just drop this feature page.

| design of the whole thing, only parts are ready

...ailored to specific purposes. This is one of the tailored ones — OpenShift ready to run. <!-- When your change proposal page is completed and ready for review and announcement -->

| style="color: #8c4a4a" | Rathann: Was alternatives ready? https://fedoraproject.org/wiki/PackagingDrafts/UsingAlternatives | style="color: #818144" | it'll be ready in a minute

<!-- When your feature page is completed and ready for review -->

...new domain (transifex.com). This largely affects translators and should be ready early. ...from Tx v0.7.4 to 1.1-devel. This largely affects developers and should be ready before the translation deadline.

...r 0.88.0 is now built and awaiting bodhi push. The feature is complete and ready for testing. The final Activity list to actually be shipped as part of the

| [[User:slankes|Sven Lankes]] || Get zoneadmin tarball ready for inclusion in fedora and package it || || {{note}}

...on on the new release, demos, speeches and, at last but not least, friends ready to answer all your questions.

#* When the page is ready for review, the page is added to category [[:Category:Spins_Ready_For_Wrang * When you feel your Spin kickstart and page are both ready for review, do the following:

...is currently in final stages of preparation for beta 2 release. Should be ready for GA on target with Fedora 15 as of 02/03/11. <!-- When your feature page is completed and ready for review -->

*Copy [http://tekkamanninja.fedorapeople.org/boards/arndale/images/ the ready-made Fedora Remix image] onto an 4GB (or larger, I use an 8GB/16GB Class 10 The SD card is ready. Now let’s prepare the Arndale!

In order for us to organize ourselves and be sure we have the people ready to help you, please send an email to the infrastructure list: https://lists

<!-- When your feature page is completed and ready for review -->

[ ] Emcee check session location is ready (IRC/other platform)

...e a kernel with realtime patches as found at PlanetCCRMA. Since this isn't ready for F14, this spin instead relies on reducing unwanted system and user serv <!-- When your spins page is completed and ready for review,

* Preparing to be ready at time

None needed - this is a new feature and can be safely deferred if it is not ready.

* '''TESTING/BATCHED''' - Your package is ready to go stable, and will wait until the next Tuesday's update batch to be mar * '''TESTING/STABLE''' - Your package is ready to go stable, and will wait until the next daily update push.

<!-- When your change proposal page is completed and ready for review and announcement -->

...long with the test case or package if its tagged as 'this is currently not ready to test' - Noriko

..."text" style="color: #407a40">kanarip: are you going to have the templates ready when we release it to mirrors?</td><td class="time">13:26</td></tr> ...7a40"> f13</th><td class="text" style="color: #407a40">again, it has to be ready at release time</td><td class="time">13:28</td></tr>

<!-- When your feature page is completed and ready for review -->

15:21 < warren> Perhaps let packagedb takeover owners.list if it becomes ready. 15:37 < mmcgrath> Smolt is up and ready, I've been adding some queries, breaking some things, this and that.

12:14 <@wwoods> mether: yes, but they aren't ready yet, and they'll need an upstream place to do development 12:16 < mether> if they are not ready for the distribution, are they ready enough for rawhide or fedora extras-devel

| application/pdf, application/x-pdf || .pdf || PDF || Documents ready for printing and viewing, held in the PostScript format in a compressed PDF

...got the big black usability box somehow. How do you put it together to get ready to run usability tests? Learn here!

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

This pre-planning should mean everything is ready and any major issues should have been shaken out before we "pull the trigge <!-- When your feature page is completed and ready for review -->

| <!-- subtask -->migrate to taskotron instead of tunir, when tasktron is ready (non-blocker) | <!-- status --> (Not ready / dropped)

15:00 < dgilmore> Everyone here and ready for the meeting? 15:29 < dgilmore> Legacy buildsys is setup and ready

* Not ready until 2010-07-12 * Not ready until 2010-07-23