I'm hesitant to allow zip files on the forums due to the potential security issues for people who download and run them. Before someone points out that the same security issues exist for art, bear in mind a couple things:
Generally speaking, if something claiming to be art comes with an executable file, people will be suspicious of it.
Art gets a lot more attention then forum posts. If someone tries to upload something nasty, it's a lot more likely that it will be noticed quickly.
qubodup brings up a good point about OGA not being a software site. I'm not completely opposed to hosting certain kinds of art software, but if it's going to happen a lot, I'd prefer it to have its own section so it doesn't get mixed up with search results.
As it stands, the official word from the top is that I'm allowing it in this instance. If software uploads become a frequent thing, we're going to need to come up with some way to deal with them. But for the moment, I don't see any reason to make a big deal out of it.
Finally, a word on licensing: The licenses we have here are (for the most part) more appropriate for art. In a case like this, the best solution would be to choose a license from the available list, and then put in your notes that the program is additionally available under some other (more code-appropriate) license as well.
My dad had a stroke over the weekend and I haven't been around to approve posts. I apologize for the inconvenience.
Also, for the record, we get a tremendous volume of spam attempts, so as much as I'd love to turn off the spam filter, I can't do it. If I did, we'd be inundated with far more spam than I could manage. It's unfortunate that it occasionally gets false positives.
I'm not saying you necessarily should't. It's just not a license that was written with source code in mind, so I'm not aware if there are any odd consequences to using it. It's possible it might also render it incompatible with the GPL and some other licenses, but I'm not sure about that.
(Incompatible meaning that you can't mix the source code in with your own work, not that you can't use it alongside your work.)
In the interest of making sure we don't succomb to link rot, can you upload a current source snapshot? (I noticed you linked to your github repo, which is good. That's definitely the preferred method of getting the source, but I just want to make sure we keep an archive of it here.)
Thanks :)
Bart
P.S. I'm not sure what the implications of using CC-BY as a source code license are. You may want to consider dual licensing it with something more standard like the LGPL or MIT or something, just in case.
You can make someone download a zip file with a plain HTML link, too.
Big discussion here.
I'm hesitant to allow zip files on the forums due to the potential security issues for people who download and run them. Before someone points out that the same security issues exist for art, bear in mind a couple things:
qubodup brings up a good point about OGA not being a software site. I'm not completely opposed to hosting certain kinds of art software, but if it's going to happen a lot, I'd prefer it to have its own section so it doesn't get mixed up with search results.
As it stands, the official word from the top is that I'm allowing it in this instance. If software uploads become a frequent thing, we're going to need to come up with some way to deal with them. But for the moment, I don't see any reason to make a big deal out of it.
Finally, a word on licensing: The licenses we have here are (for the most part) more appropriate for art. In a case like this, the best solution would be to choose a license from the available list, and then put in your notes that the program is additionally available under some other (more code-appropriate) license as well.
Bart
The reason we use Drupal is because it's easy to add custom code to it. Drupal can't do what OGA does out of the box.
Done. Also, I tweaked the spam filter a bit, so hopefully it won't give you any more trouble.
My dad had a stroke over the weekend and I haven't been around to approve posts. I apologize for the inconvenience.
Also, for the record, we get a tremendous volume of spam attempts, so as much as I'd love to turn off the spam filter, I can't do it. If I did, we'd be inundated with far more spam than I could manage. It's unfortunate that it occasionally gets false positives.
This is awesome. :)
Is your war game called "Call of Honor", by any chance? ;)
I'm not saying you necessarily should't. It's just not a license that was written with source code in mind, so I'm not aware if there are any odd consequences to using it. It's possible it might also render it incompatible with the GPL and some other licenses, but I'm not sure about that.
(Incompatible meaning that you can't mix the source code in with your own work, not that you can't use it alongside your work.)
Greets!
In the interest of making sure we don't succomb to link rot, can you upload a current source snapshot? (I noticed you linked to your github repo, which is good. That's definitely the preferred method of getting the source, but I just want to make sure we keep an archive of it here.)
Thanks :)
Bart
P.S. I'm not sure what the implications of using CC-BY as a source code license are. You may want to consider dual licensing it with something more standard like the LGPL or MIT or something, just in case.
I'm sure I sound like a broken record, but excellent work, as always. :)
Pages