Mr. President- there is in fact a Workshop upload, and we did in fact add you and JamminR as collaborators.
The main reason we set this up is because I pointed out these unofficial uploads to Megiddo:
http://steamcommunity.com/sharedfiles/filedetails/?id=379185562http://steamcommunity.com/workshop/filedetails/?id=379186890These Workshop uploads of ULX and ULib have 6700 and 3100 subscribers respectively, which is a decent amount. The uploader must have made some changes to get it working without any txt files included, but a quick peruse through the changes didn't show anything out of the ordinary, except that it is rather out of date. Then again, so is our release version.
------
Skimming through the Steam Subscriber Agreement, sections 6A and 6B:
http://store.steampowered.com/subscriber_agreement/Essentially, the main concern is likely to be this line here (in regards to generic User-Generated Content in general, not just Steam Workshop uploads):
You grant Valve and its affiliates the worldwide, non-exclusive, right to use, reproduce, modify, create derivative works from, distribute, transmit, transcode, translate, broadcast, and otherwise communicate, and publicly display and publicly perform, your User Generated Content, and derivative works of your User Generated Content, in connection with the operation and promotion of the Steam site.
Now, I'm certainly not a legal expert, but to me, this means that we give Steam the right to actually distribute our content- this covers all of the legal mumbo-jumbo terms in terms of electronic transferring of data. The create derivative works part is further explained in section 2B with regards to Steam Workshop uploads:
(a) Valve may make modifications necessary to make your Contribution compatible with Steam and the Workshop functionality or user interface, and (b) Valve or the applicable developer may make modifications to Workshop Contributions that are accepted for in-Application distribution as it deems necessary or desirable to enhance gameplay.
And finally, one last thing they note which makes me feel much more at ease with the whole thing:
You may, in your sole discretion, choose to remove a Workshop Contribution from the applicable Workshop pages. If you do so, Valve will no longer have the right to use, distribute, transmit, communicate, publicly display or publicly perform the Workshop Contribution, except that (a) Valve may continue to exercise these rights for any Workshop Contribution that is accepted for distribution in-game or distributed in a manner that allows it to be used in-game, and (b) your removal will not affect the rights of any Subscriber who has already obtained access to a copy of the Workshop Contribution.
------
Megiddo and I are working through a few changes to ULX/ULib that we should probably make you guys aware of. I wanted to add some kind of update check and notification to let users know when their version of ULX or ULib was out of date. To accommodate this, we've split ULib and ULX into their own repositories, and then we've added Git Hooks for our Git clients to automatically update a date (unix timestamp) in a file. See the following:
https://github.com/TeamUlysses/ulx/blob/master/ulx.buildhttps://github.com/TeamUlysses/ulx/blob/master/.git_hooks/post-commitWe can then use this as a quick HTTP fetch check to see if the build timestamp listed on GitHub matches the local one on the client, and then notify about updates. Workshop updates happen automatically, so that should help our goal in keeping users up-to-date. Note that we will differentiate between Release and Dev installations when doing update checking, and workshop will always be our latest Release build.
Additionally, our version notation is changing slightly, mostly to fix the old SVN <Unknown Revision> issue- Megiddo made a quick Google doc to note specifics, but the general idea would be:
Release version: ULX v3.41
Git version: ULX v3.41d (18 Nov 2015)
- Latest release version plus a date applied-- This version would be newer than release 3.41
Workshop version: ULX v3.41w
- Identical to Release version. Since workshop downloads are much harder to modify, this version can be noted as likely not to have any core ULX files modified.
Also, Megiddo has created a Trello board to help us manage various ULX3, ULib, and ULX4 tasks. I think we should get you guys access as well, but I'll leave that up to Megiddo.
Wow, I ended up ranting about a lot of stuff. This tends to happen when we get free time and actually get to do some development!
