Neo900-Planning

Plans on Neo900 which won't happen without your help

It's way beyond the "we need help" state.
It's in the "do it yourself or nothing gets done" state since start of year already.
(Joerg-Neo900)

WE NEED MORE PEOPLE

ANY PEOPLE

WITHOUT YOU NEO900 WILL DIE

DUMP YOR SHYNESS AND "I CAN'T DO IT" AND GO OVER HERE

Intro

The previous model of developing Neo-900 wasn't up to a task so let's take a deep breath and think together what to do next.

This is the page for community-based planning and stuff.

Feel free to join the discussion. Proposals to move a discussion to a more appealing platform are ok. Any proposals are ok. Nothing is set in stone anymore.

CONTACT

• Site is www.neo900.org
• List with contacts is http://neo900.org/contact
• IRC: #neo900 (Freenode)

Status of the project:

• v0 and v1 prorotypes. V1 was about testing modem and some mechanics. - DONE

• v2 prototype for LOWER board (1 out of 2 boards) - [CURRENT]:

  • Schematics - DONE

  • Layout - [CURRENT] more details and tech issues/planning

  • Testing - DREAMS

• v3 prototype (both UPPER and LOWER boards) - PINK DREAMS

• Production and shipping - WET PINK DREAMS

WORK

v2 pcb layout

HOW TO DO:

• Forget fear
• ask Joerg-Neo900 or houkime in #neo900 (freenode IRC)
• get your hands on copy of the layout (Joerg is afraid of "chinese copycats" so it is an individual application)
• start your own branch
• Try to do sth with this mess and learn sth while doing.
• No valid result obtained IS TOTALLY OK.
• quick video tour on neo900 pcb

System administration

HOW TO DO:

• Forget fear
• Ask Joerg-Neo900 or atk in #neo900 (freenode IRC)
• Help out.

Focus:

• make collaboration on the project easier

Might involve:

• Getting to know very old stuff in order to get rid of it.
• Getting insulted by people not willing to know GIT (Joerg).

Must involve:

• you eventually becoming omnipotent master of GIT.

Example (from Joerg):

• create/install a wikiwiki on neo900.org servers for a better community-driven todo and specs page etc

Other Example (very anticipated):

• Assess the currently used by neo900 gitsystems and make the contribution process more friendly and/or clear for random people out there. NOT JUST FOR HARDCORE PEOPLE. For examples of relatively friendly approaches, see SparkFun.
• Neo900 is a potentially nice project for people to learn mobile development, so under no circumstances those should be driven away.
• Probably adding a support for fork+pr contribution flow will help.

Social (can be mixed with others)

HOW TO DO:

• forget fear (no, really)
• ask Joerg-Neo900 in #neo900 (freenode IRC)
• Annoy other project people with questions and start discussions.
• Twitter, Facebook, Youtube, blogs, forums whatever you like.
• Challenge:Make Joerg write a post on Git hatred and gather 100k likes under it.

< PROPOSE YOUR DREAM WORK HERE >

{!}THIS PAGE IS UNDER CONSTRUCTION: PARTICIPATE!{!}