jsFoo is about building entire web apps in JavaScript, whether using Node.js in the backend or Backbone.js in the front-end. At this event, we’re seeking the best JS programmers from across India to present on how they do it and how you can do it too.

Check out the session proposals and vote on the proposals you like.

The event does not have a website yet. This is your early notice. As a commitment to JS, we’re building the event’s website using Node.js. Here’s an experimental corner that uses WebSockets to livestream the #hasgeek IRC channel from Freenode. You should consider hanging out in the channel too.

Special thanks to Aditya Yadav (@NetRoY), who built it.

Early Geek ticketing is already open. The event is on October 1 in Bangalore. We surveyed 20+ potential venues across Bangalore last week and will announce the selected venue within the week (venues can be forgetful unless the booking was made in cash, but I’ve been travelling through the past month, so it’ll be a few more days). Get your ticket now.

We are also accepting sponsorships for jsFoo. We’re working on the sponsor kit and will put it out in a few days, but it’s roughly on the same lines as Scaling PHP in the Cloud. See that event’s sponsor document (PDF).

Do tell your friends about jsFoo. If you are a JS guru and would like to present, add a session proposal. We’ll make the schedule on Sep 10th based on the most voted-up proposals.

Our next event is on Scaling PHP in the Cloud.

Most apps are designed around single server deployments. One VPS with one WordPress or Drupal install, or maybe something you built with CodeIgniter. Scaling up from there to a multi-server deployment is often a challenge. You have to think in entirely new ways, from cache invalidation to database sharding to deploying the same code on multiple servers.

Scaling PHP in the Cloud is a one day conference on tackling these challenges. The event is on July 9, 2011, in Bangalore. Registrations and the call for sponsors will open later this week, but the call for speakers is now open.

To submit, head to http://funnel.hasgeek.com/phpcloud/

The event has a Barcamp-inspired format. Anyone can propose to speak, or can propose a topic and request someone else to speak. We found a venue that can take over 400 people. To help bring some order for that large a gathering, we’re taking submissions in advance, with public voting. The selection team (currently Aditya Sengupta, @aditseng, and Nigel Babu, @nigelbabu, but you can also join) will draw up a tentative schedule from the most popular proposals. We will publish this schedule as a guide to the event, to help participants plan their day, but will have many open slots for anyone else to step up and speak.

The venue has three halls and we’ll have three parallel tracks to group sessions under:

• Development – On writing software for distributed environments
• Deployment – On managing all those servers and services in the cloud
• Business – On how any of this makes business sense

Lectures, demos, workshops, case studies — they’re all welcome. Tell us how to use some tool, how to architect code for the cloud, or how your company manages its servers and why you’re a great place to work at (wink!).

At the end of the day, we’d like everyone to go home not with some fuzzy notion of why something is good, but a solid sense of what they should do next. This is an event for hands-on geeks.

Your sessions don’t necessarily have to be about PHP. This is an event on scaling in the cloud, and with PHP being as popular as it is, we use that as the reference point: sessions have to make sense to someone working with PHP. Your session could be about deploying with Fabric or legal jurisdictions for cloud hosting, not involving PHP at all, but still relevant to a PHP developer.

The event has a nominal registration fee to cover expenses, but speakers who make the selection team’s cut get a free pass (we’ll refund your ticket if you bought one already).

Head over to http://funnel.hasgeek.com/phpcloud/ and submit a proposal, or vote on the current submissions. We’ll add support for comments in another day — you can then ask proposers to clarify their proposals as needed.

Like everything we do at HasGeek, the Funnel is an open source app. You can contribute to the code, use our website for your own community events (just ask us to add an event) or fork the code and install your own instance. We’re coding furiously behind the scenes even as you read this. Expect new features to appear every day over the next few days. The code: https://github.com/hasgeek/funnel

HasGeek, on the other hand, is in the business of talking to developers. We evangelize upcoming technology that shows promise, and the true test of its viability is in whether you can find a job that uses it.

A job board that connects these two makes perfect sense, so we built one. It’s in beta with many rough edges, but poke around and tell us what you think. Are the available job types and categories appropriate? Should there be more, or fewer? What is the primary criteria by which you look for a job? By the location? Whether it’s full or part-time? Whether programming or management oriented?

We want to structure navigation around the way people look for jobs, so your feedback is important. We will be rapidly iterating with ideas to get it in shape in time for AndroidCamp on April 1.

AndroidCamp is an unconference, supported by participants for participants. Specifically, independent developers and startups. If you’d like to have an early lead on shaping the event before registrations open, head over to the discussion group.

Click here to view the embedded video.

Signing up for BankSimple's beta invite list

Confirmation notice after signing up

Update: Further reading: Conversational applications by Sandeep Shetty.

We don’t have access to an internet connection at the venue and will be running off 3G data cards. Unfortunately, we lost a data card in Hyderabad when packing up, so there’ll be no webcast this time. Our reduced bandwidth is now limited to use by speakers. We will have the whole event on tape though.

In 2009 we announced that the HTML5 specification at the WHATWG was progressing to Last Call. The plan at the time was to finish the specification this year and publish a snapshot of “HTML5” in 2012. However, shortly after that we realised that the demand for new features in HTML remained high, and so we would have to continue maintaining HTML and adding features to it before we could call “HTML5” complete, and as a result we moved to a new development model, where the technology is not versioned and instead we just have a living document that defines the technology as it evolves.

…
The HTML specification will henceforth just be known as “HTML”, with the URL http://whatwg.org/html.

Regardless of the timing, the end of version numbers for HTML is something we have pointed out at DocType HTML5. If the lack of a version number in the <!DOCTYPE html> declaration was not obvious enough, here now is the official word.

What, then, is to be made of W3C’s new HTML5 logo that’s drawn ire for conflating independent standards? What does the 5 stand for now that WHATWG has dropped it from their spec? My take: the battle to keep “HTML5” as a reference to the markup spec version was lost over a year ago. Apple started using “HTML5” as an umbrella term for modern web standards to explain why Flash was not allowed on iOS. Google followed suit with Android and Chrome, and media amplification has taken it to the point of no return.

HTML5 is the new Web 2.0. It now refers to the lofty possibilities of the modern web browser rather than a specific technology. The industry loves its version numbers and 5 is a great leap up from 2, skipping a “Web 3.0”. WHATWG could not have picked a better time to drop the version number from their living spec.