but by the time you write 1186 characters to say me and some others aren't contributing you can write 2 lines for the newsletter what you made on last aircraft effects. to copy devel notes to the changelog - you can go ahead and do it if you believe it ought to be done - don't suggest that someone else does it, this makes no sense in a wiki - remember all others are waiting for you to do it - because they by and large tick the same way.Īnd, again in answer to the original question by IcecodeGL, the answer why the newsletter is deteriorating is because other people think just like you Thorsten Posts: 12367 Joined: Mon 8:33 am It's a wiki - it makes no sense to suggest e.g. So the solution is that if you think something is important/useful etc., you go ahead and do it if you can spare the time (and before you go claim that I preach water and drink wine, I spent the last days documenting how to add effects to an aircraft as well as bringing the Vostok wiki up to speed). The trick is to recognize we don't get anything done by waiting for someone else to do it. If you're waiting for someone else to do something, chances are that others are also waiting. So if you don't want to do some task for some reason, chances are others do not either. To a first approximation, it's fairly reasonable to assume that (some) other people tick pretty much like you do. Icecode GL Posts: 648 Joined: Thu 12:17 pm Location: Spain Callsign: icecode Version: GIT OS: Fedora Reiterating myself, in my opinion, making the newsletter some kind of release notes in the FG release page would solve both points a) and b), while probably worsening point c). With relevance I mean it's not a hidden wiki page with 3 lines of content. So the solution to the first two problems is to give the newsletter more relevance. They think their work is too insignificant to be included on the newsletter.They don't even remember the newsletter exists.They think it's pointless (for one reason or another).Why don't people write for the newsletter? Several possibilities: We can all agree the root problem is the lack of people writing for the newsletter. I guess those notes are directed to people, or did you write them because you "believe in them"? And since you have an academic background: I guess the fun part is the research itself, not writing the white paper to document all the work. A better comparison would be your ALS technical notes. Writing about what you have already done is not really challenging or fun. Developing is fun and can be done for your own amusement or to challenge yourself. But you are confusing the development itself with the writing about it (and apparently me as well since my analogy was terrible). ![]() I do these things for myself because I enjoy them. I haven't contributed enough (or long enough) to this project to have any relevance deciding this, but maybe some people more involved with the project or the wiki specially find it interesting. With a bigger gap between editions the newsletter might get more protagonism, "transforming" into something like a magazine. Just have a look at the latest issues of the newsletter - they are just a paragraph or two long. Instead of a monthly newsletter, maybe a quarterly or even a biannual edition would be more benefitial. I'm not here to discuss the reasons, but to propose a solution. Maybe it's a general lack of interest on it, lack of developers who post their latest progress on it or maybe just a general lack of writers. However in the last few years/months the newsletter has seen less and less contributions. Sometimes I just limited myself to "using" FG instead of actively being involved on it, so the newsletter was a good place to keep in touch with the latest stuff. I've been following FlightGear for many years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |