af83 is hiring Drupal developers!

af83.com is an open-source web development company headquartered in Paris. We build music and digital artist communities and are expanding into the green lifestyle movement. Our clients are some of the largest media companies in Europe, including French mobile service provider SFR, and Universal Music Europe.

We are currently expanding our San Francisco office to serve US and international clients, and are looking for web developers experienced with Drupal. Our SF office is located in a gorgeous SoMa loft (PariSoMa) and anchors a coworking community as well as hosting tech (and wine) events.

You DO NOT need to speak French for this position.
You DO need to speak Drupal.

Qualifications:

• Experienced with PHP and MySQL
• Experienced with Drupal, including developing or customizing modules
• Someone who can work well alone, but also with a team

Skills preferred - in one or more of these areas:

• Implementation of page mock-ups in standards-compliant CSS/ xHTML
• Javascript / jQuery / Prototype
• Flash / Flex
• Alternate CMS’s (Joomla, Typo3, etc)
• Website development project management

Your specific skill set can be matched up with others among the AF83 team. You will be working with a local and international team on several concurrent projects.

Salary DOE • Benefits included • Flexible schedule

To apply or for further information, please send an email to Greg Beuthin on the contact page.
In the email, please:

• Point us to 2-3 websites you have been instrumental in developing (at least one in Drupal).
• Indicate what part of these sites you were responsible for (basic build, customization, theming, etc).
• Tell us of a challenge you faced when building the site, and how you resolved it.

Technorati Tags: Drupal, af83, parisoma

Drupal’N'Go

DrupalNGo

Ah, makes me proud. The French Drupal community (of which my current employer AF83 is a core supporter) is taking the WineCamp style models, and going to host a DrupalCamp with the specific goal to barn-raise a Drupal website for one lucky French NGO. It’s called, in a smart blend of pun and brand, Drupal’N'Go.

(There is discussion whether this is specific to NGOs, or French non-profits in general. Regardless of specific designation, I think the idea is to pick an organization that supports a broader social good instead of a local sports org, which could also be a nonprofit).

A few of the breadcrumbs that led here:

• The original WineCamp Calaveras (California) - which had a significant Drupal presence. (My notes here).
• A follow-up on the the Drupal website built - as a dare, really - at the first WineCamp.
• Some notes about WineCampFrance organized by intrepid French nonprofit-tech evangelist Gregoire Japiot (also the idea man behind Mapovino). Fwiw - our WineCampFrance organizing site has since been taken down since the spin off projects moved elsewhere. This WineCamp was also heavily represented by Drupal folks.
• Notes (in French) about the first Drupal Meetup in Paris; and planning notes about this upcoming Drupal’N'Go.

Technorati Tags: drupal, af83, drupalngo, winecamp

Where’s the open map data?

One of the first people I talked to when I was at WhereCamp several weeks ago was a guy from GeoCommons. Now this is the kind of thing that I get excited about - people putting up virtual warehouses to encourage people to store open data. In this case, geo-coded data.

Of course, one of the first things I did was look for geo-coded data on wine appellations. Unfortunately, there’s nothing there. In fact, I’ve looked high and low for open-licensed geo data for US wine appellations, with no luck. (Yes, Vestra has this info for sale. But if we buy it, we can’t share it, right?) If Mapovino has to code this ourselves, then it’s going to set us back a little bit. In the end, our aim would be to then publish the kml / geo-coded data on… GeoCommons, for example.

The appellation data itself is publicly available from several federal sources (here, for example). The challenge is that the appellations are defined in natural language, and according to USGS maps, not latitude / longitude. So there’s some translation work that needs to happen. There are a few different ways of taking this descriptive data and turning it into KML files (my first idea involves using the hiking software Topo, but that’s another story) - but it will require a human and many hours.

In the end, even emails to the TTB (the wing of the ATF that focuses on non-terrorist related activities) and the USGS have turned up empty handed - they all pointed me to the narrative description files I’ve found before.

So it looks like we’re gonna need an intern and some USGS maps. Know someone who wants to trade drawing skills for some wine?

Technorati Tags: mapovino, af83

Mapovino: Google-mapping and social-networking and wikipedia-ing

It’s very difficult to describe what we are aiming for with the Mapovino project without getting caught up in Web2.0 buzzword bingo; or, going the other route, being so pretentious that it’s we’re sooo different that we shun any words that sound vaguely like the “read-write web”. Sigh. Below are my best thoughts in words so far….

(We’re having a demo and wine-tasting in San Francisco soon. Contact me if you’re interested!)
————————————–

Mapovino is a wine-mapping website incorporating GoogleMaps to showcase geographically distinct wines and the stories behind these wines.

Mapovino is interactive:

• Users can add comments, photos, link to maps in their blogs, and even add blog links on the map.

Mapovino is encyclopedic:

• It will pull wine and geography information from Wikipedia and other public information sources. This secondary user-generated content further enables users to interact with Mapovino.

Mapovino is information and referral:

• Mapovino will not sell wines; instead, it will point to where to find the wine in stores and restaurants.

Mapovino will be driven by wine fans, helped by Mapovino staff:

• Producers will not have the burden entering information about their wines and vineyards - fans of their wines can help input that information. Mapovino staff will highlight producers, and post in-depth articles and interviews. Producers can control their own entries, but do not have to do anything specific for their wines to appear on the site.

Mapovino is in development:

• To be part of the conversation, please email “greg.beuthin” in front of “@af83.com”

Technorati Tags: mapovino, af83, terroir

We’re hiring! AF83 is looking for a Drupal developer!

Read all about it over here. 

My contact info is on the linked page - yep, you’d be talking to me.  (The position is based in San Francisco…)

Technorati Tags: af83, drupal

Garage shop to Enterprise, Drupal style

It’s been quite a drastic couple of years for me in the Drupal world - from medium-sized Drupal site implementation, to tiny scale DIY projects and ongoing support, now back to an enterprise-level Drupal shop.

I started learning 4.7 several years ago, working on my own site.  At the time I was at CompuMentor, by then a sizable technology nonprofit, and with my background in project management I was put in charge of a couple of $20-$40k Drupal projects - which turned out quite well, I might add, thanks in huge part to design and implementation partner FloatLeft.  I was also one of a handful of staff singing the praises of this open-source CMS, not only to nonprofit clients but to CompuMentor as well, which has now not only adopted the technology on a large scale, but exerts its gravitational pull on a galaxy of great independent nonprofit Drupal consultants.

I changed jobs and went to a school part time, where I began nudging at ePortfolio development on Drupal.  I was also keeping a hand in some small - tiny - DIY projects.  I learned a hell of a lot about how far you can take Drupal without coding - and where you hit some real limitations unless you’ve got PHP skills.

Now I’m doing work for large a web development shop.  Perhaps more like a department store.  It didn’t quite strike me until I read an (old) post by Josh over at Chapter Three:  a lot of Drupal shops (in fact, many of the ones I am familiar with) are not prepared to handle enterprise-level Drupal development and support.  Support especially.  One of the commenters on his post nails it - the challenge is with enterprise-level Service Level Agreements.  Most 3-10 person dev shops don’t have extra bodies to ensure all-hands-on-deck when something goes south; at least, not at that scale.

Now I’m working with a company that does this kind of thing on a regular basis, and does have the bodies and experience to do it.  AF83 has a history of building and supporting large community sites answerable to, for example, one of France’s biggest telecom agencies.  You better believe they’ve got a wicked SLA.

And now all of a sudden, I worried we’re too big.  Most of the Drupal calls for work are asking for a developer or two, billable at an hourly rate.  For companies to request enterprise-level production, Drupal shops need to prove an ability to build and support these kinds of sites - which they won’t do unless they see a market for them. It’s a chicken-and-egg situation - and I’m not sure which one is us….

Technorati Tags: drupal, af83, enterprise-level, compumentor

Powered by ScribeFire.