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: Wed, 4 Oct 2000 17:32:34 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain;charset="iso-2022-jp"
- Importance: Normal
- In-Reply-To: <20001004143258.B4491@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <2OHYFB.A.G6B.g0u25@example.com>
- Resent-Sender: tlug-request@example.com
> From: Frank BENNETT [mailto:bennett@example.com] > > Hmm. Pardon me for intruding on the discussion, but this puzzles me. How > does one decide whether enough demand exists, and if the answer > is "yes", what > decision on disclosure follows from that? Good question - I think I know where you're going with this. Two ways both with advantages and disadvantages: * put the source out there and see * guess The first approach is not as simple as one might think. Requires placement, procedure, a little "marketing", documentation, and some work to take it out of its environment. The success of the response will depend on all of these. Simply placing the source as-is is much less likely to attract developers or users of the app/env. As for guessing, if my application is tightly bound to a specific environment, and that within a small niche of interest for most users, I would have to do a lot of work to make it appeal or be usable by a larger base. This is something I cannot afford to do at the moment. JS
- Follow-Ups:
- RE: Open Source
- From: "Scott M. Stone" <sstone@example.com>
- References:
- Re: [Group Etiquette]
- From: Frank BENNETT <bennett@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: managing multiple window managers
- Next by Date: Re: sending mail out
- Prev by thread: Re: [Group Etiquette]
- Next by thread: RE: Open Source
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links