Hi!

thanks for your quick answer.

Shell Xu:
> Hi, u:
> 
>     That's very interesting. Let's see what happened one by one.
> 
>     First of all, source code are not been "deleted". It's just a branch
> called "rm". If you switch branch to master, code is still been there (
> https://github.com/shadowsocks/shadowsocks/tree/master).

You're correct. My mistake. However this branch has been set as main branch.

>     Next thing is really interesting. You can find my commit in repository (
> https://github.com/shadowsocks/shadowsocks/commit/3b242bee5eb191599a0d051497003127986ea290).
> But if you click "Browse files", and pull to the end. It tunes out at the
> time I did the packaging job, the repository address is "
> https://github.com/clowwindy/shadowsocks/wiki"; (its wiki), and License is
> MIT.
>     Yes, I did the right job at that time. The repository is modified,
> translated to someone else, and license changed.

ack. Thanks for clarifying this. I actually did not see a release of
this version at all.

>     I followed commit logs, and here is the log which license changed. (
> https://github.com/shadowsocks/shadowsocks/commit/ce805f0aeaea03646e01b623c4e2185f63a3562f).
> The whole project are re-licensed to Apache to protect the name of
> contributors. It's happened far after my work, even after Debian accept it.
> (according here: https://packages.qa.debian.org/s/shadowsocks.html, it's
> 2014-09-16) In this situation, I think the old code still can be used under
> MIT, and new code can only be used under Apache. So I should use new
> license if package new one. But I don't have to update package to follow
> the new license.

Correct.

>     As you might noticed, shadowsocks is a software which designed to
> broken the GFW. So it's not weird that government wanna erase this whole
> project. The main author (clowwindy) was found by police, and have a little
> conversation. (which we call it "drink tea") He is forbidden to maintain
> the project, even talk about it. So I don't trust any commit after that
> time. (just before 2015-08-20) Because government might inject something in
> it after that time.

Thanks for clarifying this.

>     Here is the thing I wanna do.
> 
>     I'll update the package to version 2.8.2 in stretch. (of course, it's
> not a "release", because the author never planed to release at the time
> been called for "tea". and of course, under Apache License) That will be
> the final version. Any "new" version after that time should been review
> carefully.

Fair enough.

>     And, I'll remove this project from Debian in next release (after
> stretch). Because we should had something new at that time. (Or hopefully,
> we can finally get ride of GFW at that time)

Let's hope so!

I'll retitle this bug report accordingly then.

Cheers!

Reply via email to