Fedora

Welcoming the CentOS Community to the Red Hat family.

Welcome, CentOS community folks, to the wider family of Red Hat sponsored community projects.

Just a short bit ago, Red Hat and the CentOS Project jointly announced the creation of a formal, collaborative relationship, which effectively (for lack of a better metaphor) “adopts” the CentOS project into the family of other Red Hat-sponsored communities such as the Gluster Community, OpenShift Origin, the JBoss Community, and of course, the Fedora Project.

From the perspective of Daddy Shadowman, this is Big News, of course; from a community perspective, frankly, it’s something that I think should have been done long ago.  I know that many people, myself included, have friends contributing in one way or another to CentOS, or contribute themselves, and have long considered CentOS to be part of our ecosystem; having the “blessing,” and support, of Red Hat, is something I see as a Good Thing. More about those Good Things shortly. In the meantime:

If you haven’t read the FAQ, I encourage you to do so. I know that lots of folks generally assume that an FAQ is not going to have a lot of information, but in this case it is actually quite replete (in fact, I have joked that when printed, it weighs approximately 6 pounds), and will likely answer any questions that people might have. For those interested, there is also a webcast with Brian Stevens, our lovely CTO, at 5pm Eastern; and of course you can head on over to the CentOS Project website to get more information. (Or to get acquainted, if you aren’t. But seriously; I know you are. Come on.)

Despite the plethora of available information, I expect that there may be folks within the Fedora Project community who will have questions above and beyond the answers provided in the FAQ. The Fedora Project just recently celebrated its anniversary of 10 years as a community; both Fedora and Red Hat have grown tremendously during those 10 years, and the Fedora Project’s evolution as a community, and what Red Hat has learned during that process, has paved the way for many of Red Hat’s other communities’ successes. But more pertinently: the Fedora Project is a community that deeply cares not just about ourselves, but also about other communities, and about the state of free and open source software in general. And thus, I know some questions that may arise may come not only from our own experiences as a “Red Hat sponsored community project”, but also out of our deep knowledge of “how the sausage is made,” so to speak, and curiosities may be sparked about various technical implementation details. I’m happy to answer those questions where I can, either personally, or on the Fedora Board list; other questions might be more appropriate for other groups, such as the Infrastructure team, or even on the CentOS mailing lists themselves. I trust that most folks within the Fedora Project can figure out where to direct such questions.

That said – I’m happy to provide a bit more Fedora-related context, in the hopes that it might appease curiosities, and also because I would hate to see a perfectly good roll of tin foil go to waste on an unnecessary hat. :) And so, a few points follow:

  1. The new relationship between Red Hat and the CentOS Project changes absolutely nothing about how the Fedora Project will work, or affect the role that Fedora fulfills in Red Hat’s production of Red Hat Enterprise Linux. Fedora will continue to set the standard for developing and incorporating the newest technological innovations in the operating system; those innovations will continue to make their way downstream, both into Red Hat Enterprise Linux, CentOS, and many other -EL derivatives.
  2. Those of you who are Fedora Package Maintainers are not now suddenly obligated to maintaining anything in the CentOS Community.  Additionally, this does not affect Fedora’s EPEL work; this will continue to be something that the Fedora Project provides, as long as it wishes to do so.
  3. The Fedora and CentOS communities are not going to be “forced” somehow to work together.  Obviously, there exists a number of places where we have overlap in processes, build infrastructure software, and the like, and we certainly have the opportunity ahead of us to cooperate and share when it makes sense. The CentOS folks will be having a more transparent build system, and building out a release and infrastructure community – areas where we have expertise in what is incredibly similar tooling; similarly, they also have deep pockets of expertise in various types of automated build testing that haven’t become a critical part of Fedora’s culture yet. As I said previously – there are already numerous friendships forged between members of these two communities, and I would expect that over time, the things that make sense to collaborate on will become more obvious, and that teams from the two respective communities will gravitate towards one another when it makes sense.

In short: Nothing is really changing for those of us in the Fedora Project, at least in any way that we don’t choose to change ourselves. But 10 years of our own evolution as a project certainly doesn’t mean that we’re done growing, learning, changing over the next 10 years, and beyond. As the CentOS Project continues to nurture and grow its own community, I expect that many of those community members will naturally more interested in understanding how to influence the future of RHEL – the thing that eventually becomes CentOS – which is, of course, the space where we in the Fedora Project shine. While this was possible before, the “blessing” by Red Hat allows the CentOS project latitude that didn’t really exist before as far as “reaching out.” The great opportunity for Fedora now is not only to help those community members make that trip over the bridge from the downstream community to our upstream community, but also to tap into the wealth of end-user expertise and hands-on experience that is had by the collective community of CentOS users – and seriously, THERE ARE A LOT OF THEM – and to really listen, to create a feedback loop from those ultimate end-users back to the developers who are creating what will become the next generation of Red Hat Enterprise Linux. And make it even better.

(Those are those Good Things to which I previously referred, BTW.)

I hope that everyone in the Fedora Project can join me in welcoming CentOS to the Big Happy Family.  I talked to Karanbir Singh, my counterpart in the CentOS project, on the phone yesterday, and expressed this, but it’s something I mean from the bottom of my heart, and isn’t just for him, or my other new coworkers (Jim Perrin, Johnny Hughes, Fabian Arrotin – welcome, guys!) — but really, for all of the extended CentOS Community: I really hope that this goes smoothly for you guys. And if you have questions, about anything – I’m here, and I’m sure many others in the Fedora Project will be here too. We’ve been down many of the paths that you guys will see in the future – and hope that you guys can benefit from our past experiences. So don’t hesitate to ask. Really.

Congratulations to all of you.

Board Meeting, & user survey thoughts.

Greetings, live from LinuxCon in Sandy Eggo.

Two things I want to talk about:

First up: Fedora Board Meetings.  We do a public IRC meeting every other week, on Wednesdays, at 18:30 UTC (11:30 pacific, 2:30pm eastern, or use a time converter that I’ve conveniently already preset with the time in this link.

These meetings are open to everyone. We set aside time at the beginning of every Board IRC meeting to take questions/concerns/comments/otherwise from folks who wish to join the meeting (we used to do this at the end, but it always seemed to fall into the “we ran out of time” situation). So consider this a friendly reminder, or an announcement for those who didn’t previously know, that you are welcome to join and observe, participate, etc. – sometimes we have no questions, and sometimes there is lively discussion.

If you’re not familiar with IRC yet, this page is a good place to start.  We meet in the #fedora-meeting channel on irc.freenode.net. There is also a wiki page with some light information about meeting structure and protocol for Board meetings, which is useful to read as well.

Second: I wanted to type a bit about user surveys.  It’s an old board ticket, but has particular interest to me, and I’ll elaborate on why that is. :)

So way back in Ye Olden Days, I was a new person to the Fedora Marketing team.  One of the first things I was very interested in was the idea of market research – I’ll get to my interests there in a moment – and making a page about moving forward with some various aspects of research was, literally, the third thing I ever put on the Fedora wiki. The first two things were release name suggestions. That was September of 2009.  We embarked on the epic journey of Lime Survey packaging, and, well, eventually I got sidetracked by other things (FUDCon, becoming employed, etc.)

But the idea is still near and dear to my heart.  Before Red Hat, before the motherhood period of being a stay at home mom, before Intel, I worked at a industry analyst firm, cranking out reports on server, PC, PDA (yes, I just dated myself) usage, sales, dissection of usage by vertical markets and size of business, etc.  I find data fascinating.  And part of that job was surveying people for various things.

Why I think this type of thing is useful? A few reasons. From strictly a “how many” perspective, which was the bulk of my reporting at that point, it’s incredibly useful data to a variety of information-consumers; if i manufacture parts for a PC, it’s helpful to know that if I make, say, memory for laptops, that it is unlikely that I will sell 4 billion pieces of memory, if we generally assume 1 or 2 sticks per laptop, and worldwide sales of laptops are 150 million per year. You laugh, yes, but I have seen forecasts in my time that wound up equating to “45 set top boxes per man, woman, and child, sold in one year.” At Intel, I was on the data-consumer side of this, looking at new opportunities for specific chips, so looking at this type of data could help me establish how big a market was, vs. how much we were already selling into it, etc. And finding new markets altogether was always awesome.

From a more general usage survey perspective – which was more in line with size-of-business segmentation that I did – that type of information is useful to vendors for tailoring their needs to different types of markets, or identifying which ones they can serve the best.  For illustration: If businesses between 1 and 5 employees typically use cell phones to conduct business operations, because they don’t want to screw around with maintaining phone infrastructure, and businesses between 1000 and 5000 employees use some sort of PBX or VOIP stuff, and I am a vendor that is selling a magical pink unicorn that makes VOIP dead simple and lowers costs, I could tailor the targeting/marketing of the small businesses, because they don’t have existing solutions and because they struggle with barriers to implement, and target the enterprises differently (cost savings, etc).

Anyway. My point is this: I find it interesting, I find it gives useful information to people.

We’ve talked a lot in Fedora over the years about where we are going, what we are going to do, etc. It’s always controversial.  I think one of the key sticking points is this, and again, I love metaphorical illustrations, so: If you have a group of friends, and you want to go to dinner, you have to pick a place that works for everyone’s diet, you have to pick something within budget, etc. Lots of considerations.  You never, ever say, “Let’s go to dinner in Paris,” and assume that works.  Particularly if you are not close to Paris, if you don’t have a plane, and you only have a boat.  If you live in Paris, then that’s totally attainable.  When you go to dinner, you consider where you are starting from.

But we often lack any consensus, at least, in my humble, often-wrong opinion, about Where Fedora Is Today.  And in many discussions, I see a wide variety of assumptions about usage, and they have vast differences, like, oceans-apart, totally conflicting differences. Coming to agreement on how to solve a problem when there’s no common understanding of the underlying assumptions… well, that’s kind of like, making a map to dinner in Paris that only covers the last mile of walking, and doesn’t cover the “where we started from, and do we have a plane” type of stuff. I’ve probably mentioned about 40 times that I’m sort of into planning things, so I think this is a good first piece of that type of thing.

So. Still with me? Haha.

A few good things to note about user surveys:

  • Doing them consistently (ie: with the same questions or only slightly changing what you are assessing), on a yearly basis, can give you a good way to measure “things.” “Things” being – if you focus on addressing a certain area, for example – you can see if the work done made a measured difference in following years.
  • Much of it is about writing good, clear questions.  Unbiased questions, without a particular slant to them.
  • Be clear when working with folks to develop the survey about if you’re looking for opinions or actual data.  “What is your opinion of __________” is different from “what is your primary use of _______.”

I’m really thinking of the usage data points for this survey – how do you use Fedora, what applications do you typically use, what type of hardware (desktop/laptop), that type of thing. But I’m still rattling ideas around in my head – we’ll probably tackle this more fully in marketing-land, though it has been, as I mentioned, a board ticket for some time.  There’s also other ideas along the lines of doing strictly community-people surveying, but we shall see. And of course things like – tooling – figuring out a process for translations – figuring out how to get the word out to a lot of places that we’re doing surveying – etc.

Anyway: I think it’s an important thing to do. It helps to plan, prioritize, and give people new ideas about ways to contribute or places to improve things, and a way to measure improvements or progress (aka: mustard).  I’ll write more about what kinds of specific questions I’m thinking about and how people can get involved over the coming days.

And with that: I am off to keynotes and booth duty. :)

From the wayback machine: Tales from LinuxFest Northwest

(Note: things have been a bit hectic since attending this a while back. Teehee.)

I had the pleasure of attending LinuxFest Northwest, in Bellingham, Washington, April 28th and 29th.  This was my second year at the event, and the folks who put on this event continue to impress me with a great show.

Don’t get me wrong – I’m of the opinion that most of the regional, community-grown, Linux fests/cons/expos are just fantastic,  but all in their own individual ways. So here’s a quick wrap-up of what I find awesome about LFNW:

  • Location, location, location.  It’s beautiful up in Bellingham – and the event is held at Bellingham Technical College, which has plenty of rooms, a decently-sized (though increasingly packed with more people) area for booths, and a great outdoor area where they have grilled lunch each day. Despite being 2 hours north of Seattle, they still manage to draw a good-sized crowd, and it’s close enough to Portland and Vancouver (the Canada one, as well as the Washington one) to have people driving or taking the train from out of town. This year’s party was at the SPARK Museum of Electrical Invention, which in itself is worth checking out – absolutely fascinating exhibits there.
  • No keynotes.  Yes, I know some people like keynotes, and I do too, but at a two-day event it feels sometimes like… well, like you’re missing out on the chance to choose from 6 more sessions, more if they do morning and evening keynotes. People get to dig in to what they’re really interested in, which is cool.
  • Awesome booth attendance. Seriously, lots of great questions here – not a lot of drive-bys for free swag, but plenty of good, engaged conversation.  Which made the moment when someone came to the booth and I asked if they had a question, and they looked at me and said, “Oh, it’s a *technical* question,” as they nodded towards Jeff in the other half of the booth, as though I was, you know, somehow incapable of answering those Hard Questions…. well, forgiveable. :)
  • I never feel like it’s a giant sales pitch here – sure, there are vendors with booths, and lots of donations to the raffle, but you never feel like you’re bombarded with overwhelming advertisements for sponsors.

I gave a presentation on Fedora – a general “Who we are, what we do, what’s coming in F17″ presentation – which was well-received, albeit by a slightly small crowd.  Which tends to be the case when you present in one of the last slots on the second day, which is much more lightly attended.  The first day’s sessions were absolutely overflowing; several sessions I tried to attend were literally completely packed, to the point that they were not letting additional folks in due to fire code regulations.  LFNW, at least from my perspective, seems to have a more hands-on, and perhaps slightly more technical, audience, and the session lineup – voted on by the community – reflects that audience.

The booth turned out well this year, despite some last-minute wrangling; a huge thanks to Leslie Hawthorn for driving to someone’s house in Portland and grabbing the reportedly very stained Fedora tablecloth, which was temporarily separated from its event box, washing it, and overnighting it directly to Jeff’s hotel at LFNW (it was beautiful and pristinely clean!).  The famna folks also cobbled together some of the last bits of north american swag, including F16 media, stickers, balloons, pens, and a few XXXL shirts, and got it to the event.

Aside from that – in addition to meeting new people and talking to them about Fedora, it’s always good to get some facetime with other Fedora folks, and I again enjoyed meeting up with Jeff Sandys this year, who organized our booth presence.  Jesse Keating and Greg DeKoenigsberg were also in attendance, and I spent a lovely meal with them catching up on life/work/things, and lots of other good folks were around as well.

 

Fedora 17: The beefiest release yet. With a side of awwwwwwww.

For those who missed this morning’s beefalicious news: Fedora 17, “Beefy Miracle,” has been released into the world, ready for consumption by freedom-lovers everywhere.

You can read the full release announcement here, but that’s not what this post is about, really.

One of the things I truly, ahem, relish about our community is our ability to play well with others.  And I think we’re doing an exceptional job of that lately.  It’s easy to look at a list of features and say, “Woo! We haz something,” but looking at the ties and bonds we are making from the Fedora Project to other communities is what’s really impressive.  When you look at things like having JBoss AS7 in F17, or having the newest version of OpenStack in F17, it’s not just “in” — it’s really apparent that we’re not just packaging something up, but we’re building bridges between communities.  People who have never been exposed to Fedora before may take their first proverbial bite, so to speak, because of their participation in these other communities; conversely, people who have never used JBoss AS7, or any of the other of the number of projects that you see in F17, may finally give it a try, simply because it’s available, and it works.  It’s mutually beneficial, and, well, it’s just rockin’.

And for that, and for so many other things: I thank you all, for being stellar community superstars, for being amazing friends, for embracing others with open arms, for scratching that itch and reaching out to other communities, and for staying up all night (multiple times), and showing the world what the open source way is truly about.

In conclusion: I promise that no corn was harmed in the making of this blog post, despite apparent corniness levels. Corn can be used for corn dogs, who are relatives to the Beefy Miracle. And we wouldn’t want that.

Go out. Download Fedora 17. Enjoy this release.  Lots of mustard — and you know that that means progress. :)

Feeling awesome because of addition!

This post, dear friends, is about one thing:

ROBYN FEELING PRETTY AWESOME, because I actually figured out how to do something.

Behold!!! Can you spot the awesome?

Yup. That’s right: The newly added, handy-sandy Trac SumFieldsPlugin has been converted into actual usage within a trac instance, and actually configured and made into queries by MOI!

Now, I know some of you are sitting there still wondering why on earth this is actually useful to anyone (while others of you are probably making grand fistpump movements and thinking of all the awesomeness this could bring).  So I’ll give you the nutshell version:

Right now, the way budget tracking works for things like Regional Support (money Ambassadors spend for events, swag, media, etc.) and for Premier Fedora Events (FUDCons and FADs) is this: People decide to spend money, we (someone with a Red Hat credit card) pay up front, or we reimburse people, sometimes before an event, sometimes after an event (or purchase, etc.)  The money spent (and thus, money leftover for the quarter or year) are tracked manually in a wiki page by the budget owner.

Unfortunately, we haven’t come up with better ways to plan out expected spending for a whole year, or to track actual expenses (for, say, an event where hotel or other expenses are incurred) directly in Trac; the receipts wind up going to the budget owner, and then they have to figure out how to aggregate everything.  It’s not efficient, and I think that with the proper mechanisms in place, that the Ambassadors and FUDCon owners and payment-makers could be more self-sufficient in terms of the tracking.

This is why the above picture is so cool: The SumFieldsPlugin allows you to do queries, and specific a field (and then column) to do Sums on.  For the above example, it is summing up spending for Q1 and Q2 of FY13, in North America (component), and only for regional spending (not fudcons). For the below example, it is showing all spending, by quarter, by region, for both Regional Support AND FUDCons.

To summarize: I am pretty jazzed about working this into an improved workflow, which a number of ambassadors are already talking about doing, which can help all of us to be less dependent on a wiki page, and even be more proactive when thinking about where spending is going for the year (for example, we could have estimated costs vs. actual costs).

Also: Thanks to a few people, of course – Spot and Nirik for doing some packaging work on a few plugins, cwickert for reviewing, to all for helping out with getting it pulled into our trac instance and for not thinking I’m c-c-c-crazzzy (outside of, you know, normal circumstances).  And to Max for grinning wildly as he reads this, right before he sends me a note telling me how totally awesome this is, I’ll just thank you ahead of time. :D

Finally: I know it’s disappointing, but BigGiantConference is not an actual Real Event :)

Attention, North American Ambassadors who have any substantial quantities of swag or media

If you are an Ambassador in North America, and you have any substantial quantity of swag or media, PLEASE, for the love of pi day, put your information in these tickets:

Media ticket: http://fedorahosted.org/famna/ticket/30

Swag ticket: http://fedorahosted.org/famna/ticket/29

Seriously: We have a ton of events coming up before F17 is out, and what seems to be a serious lack of media, and an unknown quantity of swag, aside from stickers.  This is making planning difficult. You don’t have to count one by one, but if you can make a rough guess and put it in the ticket VERY SOON, that would be super awesome, so that we can figure out how to plan accordingly for these various events.

Incidentally: FAMNA meetings are back to a weekly thing, if you haven’t been paying attention, and we have a handful of awesome new folks stepping up to wrangle events, and meetings seem to have a pulse again, which is awesome! We’re practically on the edge of the summer conference season already, so if you have an interest in owning an event as an Ambassador, please attend a meeting and speak up.

Saying thank-you.

It probably shouldn’t be, but sometimes it’s easy to overlook giving people thanks for helping you out.  I just wanted to give props to a few people:

  • mizmo, for helping out with a PR request for screenshots of F16. Done beautifully. Thank you.
  • spot, for packaging a handful of trac plugins for me.  And for making me laugh. :)
  • inode0, for taking the reins in FAmNA meetings on getting events rolling and actually making mustard. I mean progress.
  • codeblock, for putting up with me till 2am one night last week while I putzed around with enabling trac plugins and needed refreshes… numerous times.
  • spevack, for taking my phone calls for advice (and trolling.) More than I could ever count. :)
  • gholms, for being the steadfast, always-there helper of all things cloudy. You’re awesome.

That is all :)

Updates, Tidbits, Beefiness, and so forth

Greetings! It’s time for another occasional episode of… Random Things In Fedora Robyn Wants To Tell You About!

  • F17 Alpha has gone GOLD. Gold is the color of mustard. Mmm, the sweet taste of progress.  Per yesterday’s Go/No-Go meeting, RC4 met all of the Alpha release criteria, and we are shipping F17 Alpha on Tuesday, February 28.
  • The Alpha Release Readiness Meeting is TODAY, February 23rd.  You can read the announcement of the meeting here, but to recap: It’s a meeting that gathers many team leaders to check in on their progress/readiness for the release of F17 alpha on Tuesday, and provides them a nice forum for any cross-team logistical planning that needs to happen. We’ll be meeting at 20:00 UTC (3pm Eastern, 12pm Pacific, 6am on the 24th Noriko’s time… thanks for getting up so early, Noriko!)
  • Fedora Engineering “Open House” on IRC is TODAY: Per Spot’s email to the announce list earlier this week, there will be a Fedora Engineering Open House meeting on IRC today, at 18:00 UTC.  As he graciously pointed out in his follow-up email, that time translates to 1:00pm EST. The open house will be taking place in #fedora-meeting on irc.freenode.net.  The plan for today is to briefly present some of the upcoming projects that the Fedora Engineering team will be working on, and then gather feedback, suggestions, and comments. For more information about the Fedora Engineering team, read their wiki page; to catch a preview of their plan for the upcoming fiscal year (which runs March to February, in case anyone was wondering), read their FY13 plan.

I’m super delighted at getting Alpha out ON TIME, according to schedule.  We haven’t done that since Fedora 10.  There were a ton of moving parts in this one – between /usr move stuff, a mass rebuild with GCC, and numerous other potential pitfalls, we still managed to navigate to getting things out the door on time, and I think a huge amount of credit for that belongs to folks in QA and release engineering for really thinking ahead about coordinating all of these things. Kudos, guys.

Of course, we’re not out of the woods yet, and as I’m sure you suspected, I have upcoming reminders about the schedule:

  • Feb. 28 – Alpha Release
  • Mar. 13 – Software translation deadline
  • March 20 – Beta Change Deadline, also the Features 100% complete deadline. People with features: Pay attention to that 100% percentage, and keep your feature pages up to date, please!
  • Apr 3 – Beta Release
  • Apr 23 – Final Change Deadline
  • May 8 – F17 Final Release

I’ll be frank: While we all want to relish in the glory of an on-time alpha, there is still an a-bun-dance of work to be done. Let’s continue kicking buns and see if we can repeat the progress for Beta!

Adventures in FPLing: The two-week mark, and what I do all day

I’m approaching the two-week mark in FPL-hood.  Now that I’m kind of over the “learn about all these new things” hump, getting through transitioning tasks, and the talk to Media People stuff, I think I’m settling in a bit more into the actual Getting Things Done part of the job. Which is pretty cool, and a nice place to be.

Although we have a nice wiki page about the FPL position itself, and what it vaguely entails, there’s not a concrete list of “what the FPL does,” and certainly FPL to date has brought their own personality to the job, and as such, has had their own list of tasks and to-dos.  Of course, there are things the FPL does that wind up being fairly obvious to the community; some of these are actually laid out on the handy-dandy FPL schedule.  Most of the scheduled stuf revolves around PR-things, like ensuring (by writing it) that Red Hat puts out a press release at release time, that we’re doing Feature Stories on some of the more high-profile features, that we’re sending USB keys with previews of the new release to press folks, etc., though there are other things (checking in with election wrangler to make sure elections happen, and the like).

But, of course, those aren’t the only things, and attending/running board meetings isn’t the “other thing,” either.  Not everything the FPL does is going to be front-and-center obvious to the whole community; not everyone is on every mailing list, not everyone is in all irc channels at all times.  Transparency is important in this job, and I’d like to do as good as humanly possible in that regard; while blogging, obviously, is one way to keep everyone up to date on what I’m up to, it’s not comprehensive.

To that end, I’m experimenting a bit with a wiki page I made, that essentially is my “to-do/done” list – you can check it out here. My hope is that it will provide a nice record of what I’m planning to do and getting done, and give a reasonable, without being completely obnoxious in detail, view of what the job entails.  I’ve got it divided up into fairly-immediate (week-ish), short-term (month-ish) and long-term goals; we’ll see if that format works out well, or not.

Feedback welcome, of course. :)

Problem Solvers of Fedora: Unite and Solve Problems…

(Sorry, Moz.)

I had a nice chat with inode0 last* weekend. For those of you who don’t know John, he is one of our awesome North American Ambassador mentors, a brave community credit card holder, a frequent Elections wrangler (including this cycle), the man behind community promotions such as stickers/casebadges for contributors and the more recent tee-shirt raffle, and has helped out with countless Premier Fedora Events.  And you should all thank him for his tireless efforts, his dedication to transparency in Fedora, and his ability to bring wise words at many junctures. Right now. Because he rocks.

I’ll just hang out here a minute while you do that. Seriously.

Anyhoo: In passing, we discussed the (totally awesome) Fedora multi-desktop media that we have had since F15 for distribution by Ambassadors. I know he’s also discussed this to some extent or another with Toshio and Rex, but I figured I’d give it some love and attention in the form of….

… asking someone to SOLVE THIS PROBLEM!

Here’s the quick and dirty summary, kids: We have this awesome media that we hand out, and those receiving it have no idea where to easily find the checksums to verify the media (and apparently, people do ask about where this information is published). We also have this handy-dandy website, which I’ll refer to abbreviative-ly as Get Fedora, which has a link to verify your media, but appears to only cover downloaded media.  Additionally: there are questions as to whether or not these compilations are signed, should be signed, etc. by release engineering.

I seeketh a person who wants to tackle said problem.  It involves coordinating with the websites team and release engineering and possibly the design team (do we want to put a link on media sleeves about how to verify media?) and itsuptoyoutofigureoutwhoelse.

If you’re interested, stake your claim on the logistics mailing list. (HINT: You will probably want to make copious use of this mailing list to solve this problemo. It’s the awesome place for cross-team coordination of All Things Fedora.) And then get going!

“My only weakness is: a list of tasks…..” :)

* Note: My other only weakness, apparently, is PRESSING THE PUBLISH BUTTON on a blog post; I was sitting here thinking, Gosh, I can’t believe nobody responded to that, and LO AND BEHOLD, it’s in my drafts bucket… for the past week. Sadface. Better late than never, eh?