Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]RE: Open Source
- To: <tlug@example.com>
- Subject: RE: Open Source
- From: "Jonathan Shore" <jshore@example.com>
- Date: Thu, 5 Oct 2000 10:18:41 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain;charset="US-ASCII"
- Importance: Normal
- In-Reply-To: <20001004145856.A16984@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <eIaXoB.A.22C.zj925@example.com>
- Resent-Sender: tlug-request@example.com
> From: Simon Cozens [mailto:simon@example.com]On Behalf Of Simon Cozens > > in many cases a distributed open-source approach might be the > > optimial strategy long term (not to mention giving back to the > community). > > In other cases it is not at all viable - for reasons stated earlier. > > Poppycock. You have to do all this infrastructure development anyway, > whether you run your shop open or closed source. > > Or do all your closed source projects "manage themselves"? There are quite a few differences between a small group of developers working in a geographic region version a loose group of developers distributed geographically. It takes much more time and coordination to make the later work. That said if you can invest the additional time to bring together a group of distributed developers and have a common vision - this is a win-win. For small short-term projects (I'm thinking of a week), setting up a distributed project hardly makes sense.
- Follow-Ups:
- Re: Open Source
- From: Simon Cozens <simon@example.com>
- References:
- Re: Open Source
- From: Simon Cozens <simon@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Open Source
- Next by Date: RE: Open Source
- Prev by thread: Re: Open Source
- Next by thread: Re: Open Source
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links