[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Making it easy for new users

From: Felix Ruess
Subject: Re: [Paparazzi-devel] Making it easy for new users
Date: Sat, 29 Sep 2012 12:31:52 +0200

Hi all,

the wish for a step-by-step guide is coming up repeatedly and is definitely what is missing for new users.

It would be really great if someone in the community would take it into his/her hand.
That doesn't mean that it needs to be written solely by that person, we just need someone who will coordinate this a bit
(with hopefully other people helping out) to make sure it's consistent and be persistent enough to see to it that we actually have a finished guide at the end.

Basically don't by shy about editing wiki pages, be concise (also have the courage to actually delete some outdated info or move it to more appropriate pages), be persistent...
If there is something unclear, make a note in the wiki and ask on the list.

Maybe you? Yes, you in front of the screen there ;-)

Different pages were started with intents similar to this, but never finished:

GettingStarted pages, which should be merged into one.
A lot of the information there is also redundant and can be probably removed.
E.g. there is probably no point in duplicating installation instructions, unless you think it really helps.

I just quickly added some pages to the old page.

Cheers, Felix

On Fri, Sep 21, 2012 at 10:39 PM, Jorn Anke <address@hidden> wrote:
I just have gone through the configuration process for the second time, first now with success. I must say I think the wiki/documentation has improved greatly since my last try - about a year ago.

From my experience and perspective, what I think might be useful to new users would be;
1. A step by step guide, with small goals and targets, and with references to the existing wiki pages. Eg.
- establish contact with the board, (usb and wireless),
- get the connected sensors/modules up and running, one by one, (gps, ir/imu, RC rx, etc)
- add servos
- add flight control code, (mine are compiling ok, but I have no clue about their meaning yet).

The idea is to start with very little code in the airframe file, then to add the bits and pieces one by one.

2. Provide a standard header/naming convention for the airframe files and other config files,
It is tedious work to browse through all of them (several times over) searching for useful bits of code.

3. Hmm, I think that was it.

Thanks for a fantastic project, and for your patience with us newbies!


Paparazzi-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]