Sorry for this rant but..
waheed wrote:
* what are the development tools employed?
- Development tools are Assembly, c/c++, and for windows core, eith vb/vc or some bettre one.
I think this question was supposed to be more like: What bug-tracking tool you use? What source control system do you use? Do you have project management tools that you plan to use?
* have you set up a code repository, and what VCS are you using?
- We are setting these up, our website is
www.maqron.com which is under server shift, but u can have some info there about us.
VCS stands for "Version Control System". Example include open source tools like CVS (which has some issues but at least it's both free and tested) and Subversion (which is supposed to fix the biggest problems with CVS), and commercial ones include at least Visual SourceSafe (which sucks btw, but is still better than nothing), Perforce (which I have no experience with) and a few others.
About your website, other than the "our vision" style "say nothing", there's no content so I find it rather useless for any of us as it currently is. Btw, you should really check your site with browser-settings that forbids unreadably small text, since the layout has a small problem as soon as text is scaled up a bit.
(I admit that I did not try with smaller fonts so the problem MIGHT be totally unrelated to font-sizes).
* what license is it developed under?
- It will reside under GPL for home use and from Organizational/comercial use, we shall/can charge.
1) it's not GPL anymore if you limit to whom it applies. If it's GPL, then anybody, including corporations may use it, modify it, distribute it, sell it, and pretty much everything, provided it stays under the GPL.
2) Even if you DID dual license on the basis that GPL version doesn't receive official support while your corporate version does, it is likely that any potential contributors limit YOUR right to use their contributions, so that in the end you have your own code under dual license, and other peoples code under only GPL. Having a dual license might also discourage contributions somewhat.
* what is the programming language of choice?
- Development tools are Assembly, c/c++, and for windows core, eith vb/vc or some bettre one.
Notice that you are not really going to use VB to implement anything, before you have basicly copied everything real Windows have to the point that you can run normal graphical Windows programs on top of it.
* what, in your eyes, would motivate those hanging around here - each one with a project of his/her own - to spend time on your project instead?
- YES this is the question, My point of view is we shall work under a team and each team will be assinged tasks collectivly. There will be some team leads, some project Manages. Tasks will be assigned to PMs or TLs and they will know their team and will divide the work according to their needs. Each tasl done, e.g a team develops Media Player, shall have its own names on credits etc. And whenever we shall have any donation and sponsors, we shall distribute that in all. e.g we have sponsor for media development, major part will go to media team.
So either you are not answering the VERY valid question, or you are trying to say that ONCE you have sponsors, people that work for the sponsored projects are going to get money.
I find it unlikely that you find sponsors really soon, and even if you do, I still find it unlikely that any developers will be able to get enough sponsored money (after you take your share, I suppose) that money would be a real motivator at all.
I think that if you are really going to get contributors, you need to rethink your plan first. I'd start by figuring out what is going to be your contribution to the community, ie. why do people benefit from you. Given the popularity of ReactOS (no offence Candy or anyone) most people interested in running Windows in the first place are already happily using Microsoft's original.
Personally, I'd prefer people making Wine better, so that if once in a while I have to run a Windows application, I could do it directly from my Linux box.
But I know, it is not sufficient to convince people to work with us.
Indeed.