We have a great new Wiki / Manual which is actually being I think very helpful for all of us.
But there is a Huge - Seemingly Intractable Problem. At least in my estimation of things:
No the Iris isn't the problem, It's a really great 3DR copter, probably the best one available for the price - period.
Mostly its just here to get your attention and point to the actual problem.
The problem is the wiki is viewed as the exclusive property of 3DR: essentially for the dissemination of information about 3DR products and the firmware that runs on them.
This is not true for the DIYDrones website, only the Wiki and it has produced such significant conflict that I resigned as director of the wiki because of the conflict my more liberal approaches were causing.
Don't get me wrong, 3DR is underwriting this whole venture including the DIYDrones web site, but the Wiki is the persistant and coherent reference that allows us to put information important to us in a place for all to see.
Neither DIYDrones Blogs or Discussions have the sort of persistence and coherence necessary for a body of reference and instructional material.
I am especially distressed because I was truly central in importing almost all of the files from the previous wiki to this one and in updating most of them considerably.
I think it is fair to say that at this point at least 75% percent of the wiki pages contain major editing and additions by me and the only reason it is that small is that lately their have been more contributors - especially Randy.
Indeed, I also think the wiki should primarily support our open source firmware and hardware and such hardware as works with it and favoring 3DR is certainly understandable.
But I also feel very strongly that DIYDrones now serves as a central information hub for people who know nothing about Multicopters and drones and that we are missing both an opportunity and an obligation by not also thoroughly addressing those needs as well.
In particular I have written the following pages that are currently living in the APMCopter Wiki section that are at the moment a considerable cause of discord:
Which I consider one of my best.
Several of the pages are directly built off of members Blogs, answers to repeated forum or Blog questions and they all seek to provide guidance in areas of obviously common interest to many members.
Lately I was told that these were not considered appropriate for the Wiki because they didn't stick close enough to the mandate of providing information for APM firmware and hardware installation, set up and tuning.
And I was directed that a DIYDrones Blog or discussion would be more appropriate.
My consideration of this is that they are completely inadequate for this and simply fade into non-existence in a few weeks.
And they do not provide anything like a rich enough format for this sort of important information.
I went to a hell of a lot of trouble to learn about the Wiki and how to edit optimally in it and to make full use of it's features in the belief at the time that it was a democratized wiki for all to contribute to.
And now I am told to say what I think is important in a format without persistence or form.
Of course I am not happy about this, but it is, in fact, entirely beside the point.
What is the point is how can we get this information to be available for our DIYDrones users without either conflicting with 3DR or with the Wiki / Manuals primary reason for existence of providing information for our Open firmware and Open hardware.
I would think either a separate Wiki section within each major wiki section or a separate wiki section entirely.
But in either case it is necessary to convince 3DR of the necessity for this because as it stands they view their ownership position as not having room for this - in so far as I have been led to believe and understand.
If yoiu do not care or think that this descision is 3DR's tomake and should stand as it is fine - repond and let me and 3DR know you are in complete agreement with them.
If you think that there needs to be a centralized, persistent and non specific to APM/Pixhawk hardware and APM firmware resource on the DIYDrones site speak up or forever hold your peace.
And suggestions of form and method are also appreciated (though I think the WP wiki which I have spent over a year learning the ins and outs of are pretty excellent).