(Moved to Vote) Proposal for a TWC Redistributable Unit Repository

[Pnutmaster]

I'm just a messenger...

Well alright, I'm going to go ahead and propose this formally here, in hope that someone will come along and move it into the Prothalamos in the Curia if you guys like it.

Curial Decision: Unit Repository

Total War Unit Repository

The Unit Repository is a collection of works, submitted by members of the Total War Community, under the Generic Public License. This work is available to be reused in any modification of the Total War franchise.

The Repository is to be maintained and kept up to date by a Citizen (Chief Warden) appointed by Hex, and any other Citizens (Co-Wardens) the Chief Warden appoints.

Wardens

The Hexagon Council will appoint a Citizen to act as Chief Warden, who will have the duties listed hereafter:

• Uploading new and updated files in a timely fashion.
• Keeping the forum list of units correct and current.
• Making sure applicants and entries conform to the requirements set forth in this proposal.
• Keep the list of keywords current.
• Arbitrating any ownership or crediting issues.
• Contacting Authors whose files receive complaints.
• Appointing Citizens to Co-Wardens to help him in his duties, and/or resigning as Chief Warden if he is unable to fulfill his duties.
• Following all duties and procedures set forth in this Decision.

Submission Protocol

1. Applicant assembles files into a .zip document, with specifications outlined in the "Zip File Protocol" section.
2. Applicant sends the document to a Warden, who uploads the file to the FTP server, and makes the appropriate post in the Unit Repository Forum.

Zip File Protocol

The .zip file will contain the following:

1. Required: All requisite texture files for the unit
2. Required: Screenshot and/or render of unit
3. Required: Assurance that unit actually loads into target game
4. Required: keywords.txt, as specified by the "Keyword Protocol" section of this Decision.
5. Required: credits.txt, as specified in the "Credits Protocol" section of this Decision.
6. Mesh file(s) for the unit.
7. EDU additions required for the unit.
8. MODDB additions required for the unit.
9. Unit Card for the in-game Unit Description Scroll.
10. User Interface Icon for the in-game Battle UI.
11. Unit description, either for the Unit Description Scroll, or an informal description.

Keyword Protocol

The applicant will describe his unit by choosing any number of only the following words:
[A list of keywords will be given here after discussion in a Curial Committee]

If he seeks additional keywords, he must request so of the Warden, who will then add the keyword to the above list.

Credits Protocol

Every uploaded file must contain a text file listing all credits, named "credits.txt". Inside, will be listed the credited person(s) for each of the zip file's contents. If the work is derivative of someone else's, it is expected that it will be stated as such in the credits.

All work submitted to the Repository is licensed under the GPL, and any work that is a derivative of any Total War asset is restricted by the respected EULA (End User License Agreement) as well.

Forum Protocol

A forum will be created for the Unit Repository, only postable by the Wardens. Inside, there will be a series of threads arranged into groupings based on [the decision of a Curial Committee]. Each unit will have its own post.

The post will contain the keywords specified by the Applicant, a full-size image of the unit, a direct link to the file on the FTP server via an anonymous FTP account (no username or password required), the name of the Applicant, the files included, and any additional information requested by the Applicant or deemed by the Warden.

Removal Procedure

If a file is found to be illegal or deceiving in its contents or credits, it is to be taken down by the Warden. The Warden is to seek explanation from the Applicant, and restore the file or not at the Warden's discretion.

If a file receives a sufficient amount of complaints as deemed by the Warden, for issues of substandard quality, he is to discuss the File with the Applicant for possible removal, at the Applicant's discretion. If the Applicant is not available, the decision is left to the Warden.

Professor420 did not specify where the repository should be located, or if he thought it warranted its own subforum; it would seem suited to the Mod Workshop, but that is, of course, for the Curia to ultimately decide.

[Zuwxiv]

This seems like a really cool idea. I remember working on some of the "Lost units" for Rome, and I always had problems finding a collection of all the units that were found. But with this Unit Repository, you could have a library of units to add to your game quickly and easily.

And doing that makes a big difference in the game - for example, in Rome Vanilla, the britons are very lacking in unit types. But adding some chosen archers, druid cavalry, and a different type of woad warrior makes for some awesome battles and a much more interesting campaign, IMO.

I would definately support this proposal.

[gigagaia]

Could this, instead of being a whole new thing, be merged into the modding registry, and the warden be the Registrar?

[Garbarsardar]

Excellent idea, I support this proposal.

*In the case that what giga said is feasible and prof agrees, I support this course of action aswell.

[Tacticalwithdrawal]

I support, this is a really good idea

Could this, instead of being a whole new thing, be merged into the modding registry, and the warden be the Registrar?

that makes a lot of sense - particularly if it could be developed further to include sharing between us and other sites.

[makanyane]

I support but just two questions.

Is this being proposed for RTW units as well? I think it would be useful if it were - I'm sure there are a lot of unused models around, and new RTW mods are still being started. I noted it does now say loaded into 'target game' but the M2TW version of DMB seems to be only one referred to - could we clarify? If it is for both games you'd either need two of it one in each workshop or a central location in / adjacent to registry might work better.

Why is it necessary to use an 'anonymous FTP' system as distinct from current dl system? And are our technical guys happy with doing that?

[vikrant]

i love this porpasal
but i think this dude should get some credit too
http://www.twcenter.net/forums/showthread.php?t=86208

[Amroth]

I support.

[Tom Paine]

I am happy to be acting as a conduit for Professor420 (we all know I don't have experience enough to be saying the following...):

A couple things:

As far as the Registry, this should remain separate. Ideologically it is similar, but practically, it is entirely different and they have nothing in common. There is nothing to keep the Registrar from being the/a Warden, but formally, the two entities should be separate.

Is this being proposed for RTW units as well?

I'm going to suggest it is for M2TW only at this. This may take a while to get set up, and RTW modding is slowly dying off (certainly the smaller mods that would benefit from this... the remaining ones are the stronger total conversions, I gather). We should look towards the future, and focus on M2TW, though I'd imagine there is nothing stopping people contributing RTW units... it may be a simple issue of using a RTW or M2TW keyword for the unit... my rationale is that the RTW units will fall out of use relatively quickly and be left taking up space, though there is nothing keeping someone from porting them to M2TW.

Why is it necessary to use an 'anonymous FTP' system as distinct from current dl system? And are our technical guys happy with doing that?

Setting it up via the AFTP is overall much simpler for a variety of reasons. Firstly, it is much simpler organizationally, in my opinion at least. The downloads area can get unwieldy and very unstandardized, and such a system as this relies on being standardized, yet still be powered by the grassroots... it is a dichotomy not easily achieved but one we must work for.
Second, and far more importantly, it moves the files off of TWC's server, reducing load. It is possible that the Warden will have access to a host of FTP accounts from a variety of members who provide voluntary hosting, and he can upload the files wherever he sees fit (the fastest server with the most room and load to spare). None of the files are actually hosted at TWC, but the distribution of the files all fits in seamlessly with the forum via the AFTP links.

Note also, please, that Professor420 also wants to change a section of this; the appropriate licence, he feels, is more this one: http://creativecommons.org/licenses/by-nc/2.5/


I might add that, based on Prof's... simplified... explanation for me ("Redistributable Unit Repository Proposal for Dummies and Ozy"...) I support this strongly.

[Erich von Manstein]

I support this proposal. It is a good one and could be used as a template for future game mods.

[the Black Prince]

i like this plan with but one exception

If we go with the original Proposal, the Warden should be created as a Curial Officer by amending that Section of the Constitution to add him in.

If we include this as part of the registrar's work, we'd still need to amend the Registrars job description

[Virgil]

support. And i'll help in any way possible.

[Ragabash]

Professor420 asked me to post this here.

Curial Decision: Unit Repository

Total War Unit Repository

The Unit Repository is a collection of works, submitted by members of the Total War Community, under the Creative Commons Attribution Non-Commercial License 2.5. This work is available to be reused in any modification of the Total War franchise.

The Repository is to be maintained and kept up to date by a Citizen (Chief Warden) appointed by Hex, and any other Citizens (Co-Wardens) the Chief Warden appoints.

Wardens

The Hexagon Council will appoint a Citizen to act as Chief Warden, who will have the duties listed hereafter:

• Uploading new and updated files in a timely fashion.
• Keeping the forum list of units correct and current.
• Making sure applicants and entries conform to the requirements set forth in this proposal.
• Keep the list of keywords current.
• Arbitrating any ownership or crediting issues.
• Contacting Authors whose files receive complaints.
• Appointing Citizens to Co-Wardens to help him in his duties, and/or resigning as Chief Warden if he is unable to fulfill his duties.
• Following all duties and procedures set forth in this Decision.

Submission Protocol

1. Applicant assembles files into a .zip document, with specifications outlined in the "Zip File Protocol" section.
2. Applicant sends the document to a Warden, who uploads the file to the FTP server, and makes the appropriate post in the Unit Repository Forum.

Zip File Protocol

The .zip file will contain the following:

1. Required: All requisite texture files for the unit
2. Required: Screenshot and/or render of unit
3. Required: Assurance that unit actually loads into target game
4. Required: keywords.txt, as specified by the "Keyword Protocol" section of this Decision.
5. Required: credits.txt, as specified in the "Credits Protocol" section of this Decision.
6. Mesh file(s) for the unit.
7. EDU additions required for the unit.
8. MODDB additions required for the unit.
9. Unit Card for the in-game Unit Description Scroll.
10. User Interface Icon for the in-game Battle UI.
11. Unit description, either for the Unit Description Scroll, or an informal description.

Keyword Protocol

The applicant will describe his unit by choosing any number of only the following words:
[A list of keywords will be given here after discussion in a Curial Committee]

If he seeks additional keywords, he must request so of the Warden, who will then add the keyword to the above list.

Credits Protocol

Every uploaded file must contain a text file listing all credits, named "credits.txt". Inside, will be listed the credited person(s) for each of the zip file's contents. If the work is derivative of someone else's, it is expected that it will be stated as such in the credits.

All work submitted to the Repository is licensed under the Creative Commons Attribution Non-Commercial License 2.5, and any work that is a derivative of any Total War asset is restricted by the respected EULA (End User License Agreement) as well.

Forum Protocol

A forum will be created for the Unit Repository, only postable by the Wardens. Inside, there will be a series of threads arranged into groupings based on [the decision of a Curial Committee]. Each unit will have its own post.

The post will contain the keywords specified by the Applicant, a full-size image of the unit, a direct link to the file on the FTP server via an anonymous FTP account (no username or password required), the name of the Applicant, the files included, and any additional information requested by the Applicant or deemed by the Warden.

Removal Procedure

If a file is found to be illegal or deceiving in its contents or credits, it is to be taken down by the Warden. The Warden is to seek explanation from the Applicant, and restore the file or not at the Warden's discretion.

If a file receives a sufficient amount of complaints as deemed by the Warden, for issues of substandard quality, he is to discuss the File with the Applicant for possible removal, at the Applicant's discretion. If the Applicant is not available, the decision is left to the Warden.

[makanyane]

I support, including revision to license type.

[Amroth]

I still support.

[Tom Paine]

I [re]affirm support for the draft with revision of the licence.

[Spiff]

Moved to vote Here