i cut short my last post a few minutes ago as i had to attend to a meeting, and i didn't have time to issue some more problems
so here it is(in no particular order
):
1.
even if a legal entity is formed, the contributors are still human. what i mean is this: not every contributor is an IT proffesional. some of them might be university students, some of them still living with the parents, etc. so the SDK security comes into place again. having a personal computer at home where you will spend your time developing is no guarantee it is safe. maybe you have a brother, or room mate or something that has access to the computer, and it might just leak the SDK. even if it's not the forementioned case, not everybody is a security pro as to guarantee for the integrity of the computer. hack may happen, viruses may happen, etc. every participant has a different security solution (antivir,firewall, both or one of them in place or missing), different protection software. it would be a logistic nightmare to guarantee the safety of the SDK, even with the ND papers signed. it would be even more of a nightmare to align all the contributors to a specific security standard commonly agreed. because the other alternative is to have a facility, with a fortified infrastructure (as a real company) where all will come to develop, which i don't think it will happen. and if a facility like that is built, but the users won't be able to attend in person, we come back to the centralised concept with remote connections and the known drawbacks.
2.
I see everybody has ideas, and a lot of talented people seem to join the ride, but before you even have a glimpse at the SDK , you must have 2 determined and experienced persons amonst you: a game designer and a project manager/team leader. without at least one of them, you will soon find out that a lot of good ideas means nothing unless properly conceptualised,presented/developed and implemented. unfortunately, we're not talking about "space invaders" or "VGA planets" games here, games that can be written and developed by garage techies alone. a project manager (with experience, i mean, a professional one, who has worked or works in this line of field)
is a must have.hell, he doesn't have to know nothing of C++ coding, or photoshop or Maya or any of the tools of trade. he just has to be able to vision the problems and solve them (ok, ok, i'm a project manager myself
and webservices programmer, but i don't say all these things to propose myself for the job or anything
, i just try to put my 2 cents in an area no one discussed until now in this thread[dunno about the other forum though, didn't register yet] ). bottom line is that every contributor has a personal and professional life besides this project toward which it has some responsabilities. so in order for the project to take shape, a person must draw deadlines, keep in touch with other service providers, make sure everyone does his part in the agreed timeframe,etc. I know a lot of enthusiasm is spilled in this project, but for a project to come to life and evolve instead of tumbling down and becoming just another "it could've been nice" dream, it takes a few men that can look into the future and be pragmatic. i know some of you are like this, hope you don't get carried by the wave.
PS: hope you don't mind me giving an opinion here and there in the future, even if i'm not probably gonna be directly involved