Welcome, Guest. Please login or register.

Author Topic: Aminet Copyright Upload Dilemma  (Read 11253 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline cgutjahr

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 697
  • Country: 00
    • Show all replies
Re: Aminet Copyright Upload Dilemma
« on: September 02, 2007, 02:17:12 AM »
Quote

But, as I mentioned above, I'm more concerned about how Aminet would interpret his statement.

We (Aminet) usually do not check licenses of sources uploaded more than twelve years ago when moderating a new upload - if you wouldn't have mentioned it, nobody (neither us nor the original author) would have noticed ;-)

But now that you did mention it, there's only one possible answer we can give you: If the author does not want you to distribute modified versions, we of course can't host a modified version. Trying to get in touch with the original author was the right thing to do.

Quote

while Aminet asserts that I am forbidden to upload any copyrighted material.

"Copyright" and "License" are two different things. Pretty much everything on Aminet is copyrighted, but all of it comes with a license that allowes free distribution (either by everybody, or at least by Aminet).
 

Offline cgutjahr

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 697
  • Country: 00
    • Show all replies
Re: Aminet Copyright Upload Dilemma
« Reply #1 on: September 03, 2007, 12:37:06 AM »
Quote

The original document says, and I Quote:
Quote

Feel free to redistribute this archive as often as you like. Just do me a favor and don't change it. These files should be in the archive...[Lists files in archive]


Well, I tend to agree with Exie, he wants his original distribution not to be changed, creating a completely new distribution shouldn't be a problem.

Quote

If I upload it as a new archive, under a new version, would that be acceptable?

I'd say yes, given the limited information I have so far. Just upload it and make sure to refer to the original archive in your readme, we'll have a closer look at it then.