As I’ve blogged about before, in the past few months I’ve been working a lot on Fedora Community with John Palmieri, Luke Macken, and Spot Callaway. Fedora Community currently focuses on making all you Fedora package maintainers out there even more super awesome (hard to do considering where we’re starting from 🙂 ) and later on we’re hoping to add some apps and workflows to support the wider Fedora contributor community as well.
Well, dude, it’s out, RIGHT NOW. Why are you still reading this blog post? Come on. Get over there right now and start being more awesome.
Wow, you made it this far down the blog post. Okay. Hmm. I’ll have to entice you with a little more information maybe. For some reason making it as easy as clicking on this link is still not convincing you. “What is this Fedora Community thing anyway?” you ask yourself. “Why would I ever want to use this thing?”
Welp, good thing you asked, and good thing we prepared for this! Check out our two-part podcast with Luke and John to hear all about what Fedora Community is, why you would want to use it, how it will make you awesomer as a package maintainer (and even how you might find it useful if you aren’t a package maintainer), how it works under the hood, and more:
Wow, still here reading the blog, eh? Hmm. Maybe you’re more into the visual than the aural. All right. So we’ve also got this awesome tour that walks you through a sampling of screenshots from Fedora Community and explains each. Also, it has a cool picture of Mike McGrath and you’re just going to have to click on over if you wanna see! (Besides don’t you want to be as cool as Kyle?:
If you are still reading this, and you are still not convinced you really want to just go on ahead and check out Fedora Community, well, there is not much I can do except remind you how much of a super hero Jesse is. I mean, come on, man. Don’t you want to be just like Jesse? Go on and give it a try.
P.S. John and Luke are also super heroes and have been a pleasure to work with on this project. They’ve structured Fedora Community such that it’s easy for other folks to come in and develop apps on top of it quickly and easily and they are great folks to work with to boot. So, if you’re interested in whipping together a Fedora Community app you’ve no excuse not to. 🙂 Go on and get started at fedoracommunity.fedorahosted.org.
P.P.S. mad props to jbowes who totally coined the term ‘paintain’ – I love it!
Congratulations to everyone on the team for this awesome new site. When people start digging into Fedora Community and the underlying Moksha framework, they are going to flip their lids. This is the future of open collaboration on the web — no strings, no boundaries. The infrastructure of participation has arrived!
> If you are still reading this, and you are still not convinced you really want to just go on ahead and check out Fedora Community
I did. It didn’t work at all. Testing Fedora sites in Konqueror should be a requirement, and if it doesn’t work, that should be a blocker.
If only Konqueror was not so crappy as a web browser, maybe. Till then, it is for all practical purposes, irrelevant.
Konqueror is not a standards-compliant browser nor does it handle javascript in a manner supportive of new web technologies like this.
Not working in Konqueror is not a blocker and I personally feel it unreasonable to suggest it should be.
Konqueror is standards-compliant. For example, it passes ACID2 perfectly and has a higher score on ACID3 than the latest stable Firefox.
What exact JavaScript doesn't it handle? Have you reported it to the KHTML developers?
And in any case, it is certainly possible to work around it. Many sites all around the web work just fine with Konqueror. Heck, web developers all around the world make sites work in IE which is much less standards-compliant than Konqueror!
I feel it unreasonable to release a Fedora-branded web app which doesn't work with the default browser of one of Fedora's primary/permanent spins.
Do the ACID tests take into account Javascript functionality? If so, I would question it as a valid test of compliance at least with new web technologies like JQuery and AJAX. Konqueror doesn't handle some basic JQuery calls from what I am told which is why Fedora Community does not support it. I did not work on the implementation (besides the CSS) for Fedora Community so I do not know the specifics of how Konqueror fails – I would not be the appropriate person to file a bug.
Does Facebook work fine with Konqueror? Google Calendar? WordPress?
IE has the market share and user base to justify spending time on making it work, so that is why even though it is not standards-compliant, web application developers feel it necessary to support it (btw, we don't support IE either. If Fedora Community works in IE then it's a miracle.)
Fedora is a GNOME-based distribution. The default desktop for Fedora is GNOME. We support Firefox, the default browser for GNOME.
ACID3 includes JavaScript tests (ACID2 was all CSS though).
If JQuery does not work in Konqueror, JQuery is broken and needs to be fixed. (It's a third-party framework, not part of the JavaScript standard. It claims "cross-browser" compatibility, but Konqueror is noticeably absent from their list.) It's the web apps' job to work in user's browsers.
> Fedora is a GNOME-based distribution.
Fedora is a distribution with 2 desktops as part of permanent spins, a 3rd one on an actively-maintained official spin and a 4th one advertised as a new feature in Fedora 10 and available in the repositories since. As much as you Desktop Team folks would like all other desktops gone, it ain't gonna happen. KDE SIG is here to stay, whether you like it or not. Ignoring its existence is not a viable road for Fedora.
My blog is not the place for your agenda. Please take it elsewhere.
Um, and by the way, I'm not on the Desktop Team.
The comment that I mentioned above:
Fedora Community is officially supported in WebKit and Gecko based browsers.
Could probably be rephrased to:
Fedora Community is supported on the following browsers:
http://docs.jquery.com/Browser_Compatibility
Fedora Community is officially supported in WebKit and Gecko based browsers.
We use jQuery, a "cross-browser" javascript library, and a variety of jQuery plugins.
If these do not work in your browser, then the upstream of the library or plugin should be notified.
As far as I can tell, Konqueror is choking on '$f = $(f)', where f is a string of HTML. Unfortunately, Konqueror lacks a competent JavaScript debugger, so I'm not sure where to go from there.
Thankfully, this is an open source, so people who care about certain edge cases can come in and fix them.
There are a couple of broken links (bad URLs) in the article: one for Kyle’s website and another for the community website itself (in the same paragraph with Kyle’s).
Thanks, should be fixed now 🙂
[…] Launchpad, only it’s 100% open source. There’s a great introductory blog post on it here, by Máirín Duffy. Go read […]