Alex wrote:Hi guys,
Just throwing out a call for ideas on how we can improve NZFF, either by changing things already here, or adding new things.
I've had a quick look around and at the moment am seeing whether it would be possible to add a cool video/voice/text chat system, and/or teamspeak. Although this depends on the cooperation of our hoster to add these as we don't have access to the command line prompt of the server; hopefully I should be able to give an update in a few weeks.
So, what things would you like to see added or changed? Please throw in your ideas here, so we can check them out!
Alex
Hi Alex
The thing I like about this forum, based on what I've seen over the last few weeks having recently become a member, is the number of developers hanging around. Other NZ FS forums I've been to seem to be more focussed around using the technology, rather than making it. The other cool thing about it is that we're mostly New Zealanders, so people understand some of the challenges/limitations of developing add-ons that are unique to our part of the world. I posted a question in here that was the same as one I posted on two other forums and had a response here within less than a day. On the two other forums, the question I wrote just sat in there and rotted and never got one response.
Personally, I'd like to see something happen to try and harness the creative minds and skills of the developers on here, to ensure we're all working toward the same goal
This is going to sound a little soapbox-ish and irrelevant but bear with me... One of the gripes I have with open source software is that there are so many developers, all doing their own thing, and releasing their work to the world. You end up with tens or even hundreds of different programs that all do the same thing. I've so often pondered how dominant Open Source Software could be if it were built with a single unified goal in mind. So many developers started from scratch and created a program from start to finish. They all re-invented the wheel. Think of the number of man-hours in producing one e-mail client. Then imagine how many man-hours are involved in producing 50. Now... how good would ONE mail client be, if all those developers were working on it together?
I'm not saying that the add-ons people are creating in here are necessarily open source, but that I think we could learn from some of the inherent flaws in the open source model.
I notice we have a list of freeware files, and payware files on this forum. That's a really good start.. What I personally think should happen next is that we developers come up with a goal. For example: 'to reproduce the scenery and aircraft of present-day New Zealand as accurately as possible'. If a product already exists out there which contributes to this, great. If it's payware, great. If it's freeware, great. All these products get put on a single list. If there is payware scenery out there that is of a high enough standard, there should be no need to reproduce a freeware version. What sense does that make? It's just a waste of resources. The same person who was going to develop a freeware version of say Real NZ's Wellington scenery, for instance, can pour their time and effort into making something else that contributes to this big goal. Once it's being worked on, it goes on the list so nobody else spends time replicating what has already been done. Or... they make contact with the developer and ask if they need a hand with anything.
This will be good for both freeware and payware developers imho. Over time, we can formulate a 'wishlist' and if you (like I am right at this moment) are looking for a project that you can produce to a high enough standard to sell, then you can start with one from the wishlist since you know there will be an audience for it.
Is this making any sense at all? Effectively, this thing would start by being a spreadsheet, showing projects that are either completed (payware and freeware), or under construction. Then people could suggest wishes and these would get added to the bottom. There are a few management things we could introduce to ensure that if developers go missing in action (such as Jason Grooms, author of Pro Controller, or Lee Swordy author of AFCAD) that their work is still useable by others.
I don't know... I'm on a real soapbox here and maybe I should get off it and see what others think before saying much more.
Richard