Anyways interested in your thoughts about the pros for closed source and th potential pitfalls (if that's the right way to frame it?) of that model and what you think coders engaged in a closed source model may wish to consider if/when they opt to leave a project for good / a long long time.. ?
Doesn't WikiLeaks have something similar to this?
An encrypted/password protected Torrent that contains the D'Bridge source code. The password only gets released if Nick's PC doesn't contact it for over 12 months.
opensource is nice :)
A wise man told me "I'm afraid now this is a knee-jerk response in a way you may not like to hear".
For years as a Fido developer I have had the pleasure of receiving Echomail, Netmail and Internet email about why D'Bridge is not open source. And when I state my logical reasons why, most of the time I am looked upon as an idiot because I don't publish source code like Mystic, HPT and Synchronet.
Anyways interested in your thoughts about the pros for closed source and the potential pitfalls (if that's the right way to frame it?) of that
model and what you think coders engaged in a closed source model may wish to consider if/when they opt to leave a project for good / a long long time.. ?
The D'Bridge source code is in the hands of a couple people, in the event that something happens to me... and no, not by autoerotic asphyxiation.
The legacy must live on...
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 25 |
Nodes: | 8 (0 / 8) |
Uptime: | 22:57:57 |
Calls: | 1,890 |
Calls today: | 1 |
Files: | 11,074 |
Messages: | 933,716 |