Distributed Development of Closed Source Software?

An anonymous reader queries: "After being laid off recently, I got in touch with a few uni friends. We've now decided to start developing some software in our respective spare time(s), which we may consider commercializing depending on how it goes. We've come across a problem that I am sure is not very new. We are all in different countries and different time zones. How do we best collaborate given that we have such a diverse team." "Currently we think we need a service that provides the following:

1) CVS or some variant, subversion is fine
2) Bug tracking / issue tracking (bugzilla etc)
3) Discussion board with password protection (phpBoard / cute cast)
4) Some software that lets us book meetings in different time zones. (Calendar system which takes timezone differences into account)
5) Telnet (SSH) access is preferred
6) Shouldn't cost an arm and a leg

We are perfectly willing and capable of setting up some of it ourselves, if the service lets us log in via telnet. I know there are lots of services like this for open source development, but are there any for closed source? Have people used some service like this? A cost/feature comparason would be nice, if that information is available."

Comments

One opinion

[aminorex]

I've been doing distributed development since 1992. I advise using IRC as the primary means of coordination. You can use Yahoo Messenger chat rooms for free voip meetings, but you'd probably be better off running your own Asterisk server and using SIP phone hardware, since every software voice system I've ever seen sucks. CVS is the old work horse, but subversion is what has traction now, so there's little point in clinging to CVS.

You need a server somewhere. If you are a collection of real-live software developers, probably every last one of you has at least one server online, so it seems odd that you would be looking for a commercial service that gets to own your "closed" source code.
If you actually can't use one of your members' server installations for some reason, just rent a dedicated host and configure these things. None of them are terribly difficult to setup or manage. Any compentent linux admin, given a debian root prompt, could have them all up and running in a matter of an hour or so.

What is your problem?

[jotaeleemeese]

Sometimes I wonder if some people get the full open source,closed source thing at all.

Look buddy, OSS differs from CSS only in how you decide to license it.

The software is the same for bunny's sake, there are no tools that magically will convert your software in OOS or CSS just by using them.

Your question is frankly inane and I wonder why the editors found worth posting (slow day out there guys?).

In regards to distributed development, you seem to have nailed down the tools you need (once you go live plese let us know the name of your software, your awarness of security, telnet????, is pretty reassuring).

Seeing as you're going commercial

[DrSkwid]

If you want the proper answer to your commercial question then you need to ask me in my commerical consultant capacity, reasonable rates available.

Re:Seeing as you're going commercial

[0x0d0a]

Second your comment. Seriously, why would someone ask this? They had no reason to mention "closed source" at all except to annoy people.

Here's why they mention "Closed Source" :

[DrSkwid]

3. DESCRIPTION OF SERVICE

SourceForge.net is a website owned and operated by OSTG for the purpose of fostering software development and content creation under Open-Source Initiative ("OSI")-approved licenses or other arrangements relating to software and/or content development that may be approved by OSTG (the "Purpose").