I'm willing to work on 1), but less happy about 2) and 3) - partly because I don't have the expertise to write detailed content.
Giles Robertson -----Original Message----- From: Curtis L. Olson [mailto:[EMAIL PROTECTED] Sent: 18 October 2004 15:45 To: FlightGear user discussions Subject: Re: [Flightgear-users] "Flyable" aircraft There was a push for a while to produce a newsletter, but it's more work than you'd think. Good layout tools for a nice looking newsletter seem to be proprietary. We had two people working on a first newsletter issue, but that seemed to fall through. Basically, it's a *lot* of work. A newsletter would be great, but I personally have too many irons in the fire already. We need to find other volunteers to organize it and put it together, and still more volunteers to write content. We need to find something with enough time that they can follow up and remind people to finish their articles, with enough time to write a few things themselves, and with enough time to follow through, get the newsletter out, and be able to do it monthly or quarterly. We collect a lot of developers and aviation enthusiasts here, but we are still looking for that elusive publishing expert who also happens to be a fan of flightgear and open source (and has some consistant amounts of spare time to volunteer.) Regards, Curt. Geoff wrote: >I have had enormous fun with all of a/c in fg over the past >five years or so. In my opinion, one of the nicer things >about fg is that one is able to see things develop. If a >model does not seem to work well (or at all), I just leave >it a while and sooner or later I return to find an >improvement. If something seems weirdly out of kilter I >browse the dev archives, and I usually find that a >fix is under discussion there. I am not picking a fight >with anyone who thinks differently, but for me this is the >essence of using open source software. > >One thing that I would love to see would be an occasional >news letter from the developers - posted here or and/or on >the website every quarter or so - explaining the >general thrust of development. I know that one can read dev >for that, but the issues there tend to be very detailed and >it is difficult for an outsider to see the wood for the >trees. Such a newsletter could also be used to ask users to >monitor particular areas under development for bugs. > >I do appreciate that every hour spent by (eg) Curt on the >newsletter would be an hour less of code (or just having a >life away from fg). Even so, it would be nice ...... > > -- Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
