What everyone has been waiting for . . . word from Admin. To be honest, I was just really busy, and 200 replies in a single post kinda scared me away for awhile . . .
I have several thoughts concerning:
1) community project
5) project goal
1) So lets start from the beginning. I've been dreaming of a SoR community project for about 6 months now, but felt that you guys aren't really ready yet. For example, most of you have only built one robot . . . So I figured I'd dream for another 6 months until you guys get more experienced then start up a topic similar to this. But I guess you guys have the motivation now
so my answer is: OK! Yes!
2) Now, I am a firm believer in what I call a 'functional anarchy'. Meaning you put a whole bunch of well meaning motivated intelligent people together, and you don't need a leader. However, many of you have issues on keeping focus and so I'll make some leadership like decisions. I don't really like being a leader, its hard work, but I'm fully capable of keeping you guys on target . . .
3) So now to my next point. As mentioned earlier, modularity isn't an option - it is required for this project to work. We all need to agree on standards of dimensions, voltages, communication interfaces, etc. A few of you have already started discussing this and I think its on track so I won't say any more than I 100% support modularity and standarization.
4) Money is a great motivator. Long story short, I will reach into my pocket and help bank roll this project. Yeap, I will pay for it! But money isn't free . . . sub-projects I financially support must have a great tutorial written to go with it. I also will create mini-contests for money - for example, the best designed module gets $50 from me or something like that. I am also thinking I'll reimburse anyone who makes a great module that uses my Axon (for the full cost of it). I'd have to think more about this so don't quote me on it yet. Opinions welcome.
5) Now this is the most important point I want to make. What if the goal of this project wasn't to do something like make a one-off robot, but instead create the first open source robotics platform in the world? If we all pull together, we can change the world of robotics like open source software has done to PCs. I think SoR is in a position that no one else is to make this happen. And what would we need to do to make this happen?
a) create a set of robot standards
b) develop modules
c) write tutorials
Obvious eh? We already have made progress on all three points.
So here is the defined mission I am proposing:
A) We start a thread on robot standards (there is a lot to say on this, so lets leave it to a new thread I just created)
B) We develop modules. Design a module, write a tutorial on it, you can even develop it into a product and sell on your own if you want. The only condition is that your product is open source and follows our agreed standards.
C) Everyone help grow the community, and document your robots! We are all better off and can build robots faster if we work together. Try building a robot without going to SoR if you don't believe me
Now commenting on what everyone else has said . . .
we all specialized in certain Fields. dunk with his internet control, airman00 with his butler bot voice recognition. but we are all saying we need one leader and i think that is true try admin for example if he was the leader he would see over the entire project. then we should have group leaders (programming, contruction)
cooldog, I entirely agree. If we all specialize on a particular area that we are good at, we can focus more and get more done.
Also we will need a open source programming area as well. Where functions for each module on a pic and avr are already made and you just download the code to go with each one and tie them together with your own code. It has potential but needs to be managed and a good system developed to manage the files and projects.
I can offer project space, but someone else would have to manage that.
does anyone think we need a 3.3v supply? personally i think 5v is a better choice and people can regulate down to 3.3v if they need on a particular board.
dunk, my Axon has a 3.3V regulator built in that can supply up to ~76mA if I remember correctly . . .
licencing. who owns this? how do we stop someone else from patenting out work? i think we need a template Open Source type licence that anyone can copy into their project.
dunk, I think whoever develops a module owns rights to it. we should follow the open source rules similar to software . . . thoughts anyone?
everyone alright with Eagle for board schematics?
i personally am with the idea of a subforum for the SOR project. it'll be alot easier to find threads about it, than having to look in every section for the SOR PROJECT heading.
Here is where my leadership comes into play . . . for all project posts, make sure this is in the subject line:
SoR Project: [title here]
If it gets crowded, I'll create a new section.
Ok just to add a little organization to the coming projects I created a list of potential modules. This will be added to and modified over time to include who is working on what module so that people don't do more then one without combining their work.
asellith, great idea!
About making plastic casings for parts, perhaps that should be a project/tutorial on its own?
And lastly, if we were to use my Axon, I'd have to standarize the software for modularity. I'll make this a priority and get the info out to you guys as soon as I can.