Subj : NetRunner source
To   : MRO
From : echicken
Date : Wed Aug 19 2020 11:48:32

  Re: NetRunner source
  By: MRO to echicken on Wed Aug 19 2020 00:54:29

 MR> what it all boils down to is from day one he did not want to be open sourced and he wanted to find a
 MR> reason to yank it. 

And by then it's too late; the mirroring and forking that he wanted to avoid is already done.

 MR> i'm not sure if someone really stuck their name on mystic bbs. 

If they did, it's a natural consequence of going open source and not something to be surprised by.

Were I in his shoes, I would *want* other people to rename and take credit for their forks and variants. As long as they're giving as much credit to him as the original license demands, that's fine.

It's okay if people fork the project and make a mess or never do anything with it. GitHub etc. are rife with good intentions and fizzled efforts. Sometimes there are useful changes that someone else can work from.

The main thing is that it be made clear who wrote what, so that the original author doesn't receive a bunch of confusing requests to support someone else's junk.

 MR> we talked about this at length on zeronet and he got really pissed. he really does not like open
 MR> source, he does not like collaboration. that's his right, though. the truth is he put mystic source 

Yep. Sucks that he closed it up, but it's his project and his choice. I'm surprised that he caved to pressure to open it up in the first place, given his low tolerance for the consequences. I suppose it was a learning experience.

I've had kind of the opposite curve, being quite embarrassed of my shitty code early on and defensive because I'd worked hard on it. Took me some time to learn to deal with criticism and disagreements on how things should be done, etc. If you can get past all of that, there's a lot of room for growth and improvement.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com
 þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

.