Fedora

Fedora, Red Hat, RHEL 7, & Open Source. (Or: How RHEL 7 is literally “Beefy.”)

Many of you probably noticed (or were gleefully anticipating) the release of Red Hat Enterprise Linux 7 today. Which means it’s a really super day to be a Red Hat employee — seeing the culmination of so much open source work come together as the next major version of our flagship product is pretty inspiring.

Of course, I have a unique perspective on this process, having been the Fedora Program Manager (aka: schedule wrangler) and Fedora Project Leader over the Fedora 15 – Fedora 20 time frame, and RHEL 7 is largely based on Fedora 19, with bits of 20 pulled in as well. So much of what I’m reading today about the features and capabilities of RHEL 7 is very much a reminder of many points in those release cycles, and the effort and sweat the Fedora Project community put into that work. (And in some cases, blood and tears as well. Well, maybe not blood. But probably hot dogs.)

To give a bit more insight into this process, without truly taking you down the rabbit hole, here’s the short version of how Fedora integrates technologies, and serves as the upstream for Red Hat Enterprise Linux:

  • Hundreds of upstream project communities are working every day to improve their own code bases. At certain points determined by those communities, they release versions of their projects.
  • Fedora Project community members, who are often also involved with those upstream communities, will work to integrate new projects and updated releases of existing projects into its distribution, Fedora; and in fact, the inspiration to create new, innovative technologies in the Linux distribution space often evolves out of the community as well. Fedora is released approximately every 6 months, and strives to have the latest-and-greatest versions of those projects available. This makes for a fast-paced, cutting-edge distribution that offers a view into innovations that many folks have not otherwise tried.
  • Every few years, Red Hat Enterprise Linux will take a snapshot of Fedora at a time when they feel it has evolved a feature set that is compelling and rich in new capabilities that the market is ready for, and will shape that over time into a major release of RHEL.  In today’s case – RHEL 7.

I thought it would be fun to look back over the past several releases of Fedora and take a look at some of the most innovative features that were developed and integrated into Fedora over that time period which have now made their way into RHEL 7.

  • systemd (introduced in Fedora 15) – “a system and session manager for Linux, compatible with SysV and LSB init scripts,” to quote the project page itself. The project has continued to innovate since that point, introducing additional enhancements in subsequent releases, such as these in Fedora 19:
  • USB network redirection (Fedora 16) – the ability to redirect a USB device to another machine on a network. Most notably useful for connecting a USB device from one machine to another inside a qemu-kvm virtual machine.
  • Anaconda, the installer, got a major facelift in the form of a new UI (Fedora 18), and enhancements “under the hood” also enable easier integration of new storage technologies  in the future into the installation experience.
  • Storage management enhancements, including a command line utility, and library (libStorageManagement) that provides an open source storage API for storage area networks and network attached storage (introduced in Fedora 18.)
  • Virt improvements everywhere. Including:
    • virtio-rng (Fedora 19), making entropy available from the host to guests, preventing entropy starvation
    • Live VM migration without shared storage (Fedora 19), doing… well, just that. Eliminating the need for shared storage in a live VM migration.
  • High Availability & cluster changes and improvements, including the move from rgmanager to Pacemaker (Fedora 17).
  • Firewalld became the new firewall solution in Fedora 18, enabling firewall changes to be applied without rebooting (among many other features).

And that, my friends, is quite literally the tip of the iceberg. Over the course of Fedora 14, 15, 16, 1718, and 19, more than 250 features, upgrades, or significant changes (such as defaults) were made to packages in Fedora.  And as a result – features you’ll find in RHEL 7 have largely already received thorough testing and use, and are very much ready for prime-time, enterprise usage. (Which is why, as noted in the blog post title, RHEL 7 is Beefy — as “Beefy Miracle” was the release name of Fedora 17. I suppose the most accurate way to put it would really be to say that RHEL 7 has partial Beefy content.)

While not all of the changes or features made Fedora have made their way into RHEL 7, a significant portions of those that have are documented in the RHEL 7 Release Notes. And for those that didn’t, many of them have been made available through Fedora’s EPEL (Extra Packages for Enterprise Linux) repositories, thanks to the awesome Fedora Project community members who do this work.

So if you see someone playing with RHEL 7 today and they look a bit overwhelmed at all the newness, give them this tip: There may be a lot of new in RHEL 7, but Fedora is already building the future of RHEL 8, *right now* – so if they want to get a leg up on the next major release, or if they want to influence what that next release looks like, Fedora is the place to do it.

Thanks to you, I’m much obliged…

…for such a pleasant stay.

When one prepares to retire from the Fedora Project Leader position, there are two places in which to look for inspiration in writing their “departure advisory”:

  • Past notices of intentions to retire, such as those of my lovely predecessors Max Spevack and Paul Frields
  • Led Zeppelin lyrics

And thus, this blog post will draw a bit from both of those — but I will look to Page/Plant to kick it off:

“And to our health we drank a thousand times… it’s time to ramble on.”

(Note: A thousand times may be an inaccurate estimate.)

I’ve been in the Fedora Project Leader role for a bit over two years now, and was the program manager for Fedora for nearly a year and a half before that; needless to say, Fedora has been my full time and lots of my other time job for a long time now. Being in this role certainly is humbling and daunting at times, and amazingly gratifying at others, but it has also afforded me an almost overwhelming opportunity to learn about anything and everything going on in open source outside the Fedora universe, with the hopes of bringing those people, projects, and ideas into our folds. Some of it is incredibly interesting, and some of it brings incredibly creative thinking into solving problems that we face in the technology space today — and, like those before me, it has also led me inevitably into exploring new opportunities.

With Fedora 20 well behind us, and Fedora.next on the road ahead, it seems like a natural time to step aside and let new leadership take the reins. Frankly, I shouldn’t even say “the road ahead” since we’re well-entrenched in the process of establishing the Fedora.next features and processes, and it’s a rather busy time for us all in Fedora-land — but this is precisely why make the transition into new leadership as smooth as possible for the Fedora Project community is so important.  It’s a good time for change, and fresh ideas and leadership will be an asset to the community as we go forward, but I also want to make sure it’s not going to distract us from all the very important things we have in the works.

I’ve informed the Fedora Project Board already of my intentions, and my friends, Red Hat management and family are all aware and supportive of my decision to move onwards. Red Hat engineering and management, as the employer of the FPL, will obviously be involved in the transition process, and the Fedora Board will continue to be advised and consulted during the process as well. While what it is *exactly* that I’m doing next is still to-be-determined, I will be sticking around to help with transition tasks, general FPL-edification, and generally ensure a smooth turnover into the New World, after the proverbial torch is passed.

And “after” is a key word here, of course: Today is not my last day, or anything like that. I’m just letting everyone know of my plans to, well… Ramble On.

Stay tuned for updates.

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 :)