FW: SPAM LOW: [openmoko-announce] Crossroads

"Mike Strock" <[email protected]> Tue, 13 Mar 2007 10:05:27 -0700
Newsgroups gmane.network.wireless.seattle.general
Message-ID <!&!AAAAAAAAAAAYAAAAAAAAAAWYZ3QlvDNAlsNtXaRN1nxChAAAEAAAAPY5K2x6UBVNox2IL+9T8jUBAAAAAA==@myhomeoffice.org>
I thought someone on this list might know something/someone who could help
the OpenMoko folks out....

Mike Strock
[email protected]

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Sean Moss-Pultz
Sent: Tuesday, March 13, 2007 9:51 AM
To: community; [email protected]
Subject: SPAM LOW: [openmoko-announce] Crossroads

Dear Community,

OpenMoko is built around the philosophy that far more knowledge exists 
outside the walls of a corporation than within. Internally, we're
struggling with two issues. So we're throwing this out, hoping that some
of you have can help us move past our current crossroads: 
  
  1) We can't find a WiFi Chipset with GPL'ed drivers -- We know 
  this has been discussed (to death) on this list, but as we're 
  beginning work on the next summer hardware refresh we still can't seem
  to find a vendor that meets our strict requirements: Namely, we refuse
  to put anything binary in the kernel. 

  Marvell has some nice for larger devices (the 8388). But we need
  one specifically for mobile phones (like the 8686). If somebody 
  can help us find the right vendor, we'll give you a free Neo1973. 
  
  If you're a vendor and want to work with us to GPL your driver, we'll 
  give you lots of business -- and a free phone ;-) 


  2) We don't have enough UI / Application developers -- If anybody 
  meets (or knows somebody who can meet) the following qualifications:

    	* >= 2 years experience with GTK
    	* object oriented design and implementation w/ GObject
    	* experience with writing GUI applications from scratch,
    	* has software quality assets like:
          o writing maintainable and reusable code
          o refactoring
          o design patterns
          o identifying and extracting common application code 
            into frameworks 

  Familiarity with collaborative development tools such as:

    	* bugtracker,
    	* source control management,
    	* wiki,
    	* mailing lists 

  is a necessity.

  We've love to talk with you! Please email [email protected] with 
  links to your previous work and a resume if you have one. (The latter 
  is nowhere near as important as the former.)

Thanks in advance for any help!

-Sean




_______________________________________________
Talk mailing list
[email protected]
http://seattlewireless.net/mailman/listinfo/talk