Since there are many GREAT wire tools rapidly disappearing, due to developers abandoning, bugs in the forums, etc, I created an Unofficial Wire Extras SVN. This contains a collection of useful tools in which to excel your wire addiction.
Also, many people were saying that the wire SVN has been a bit stale, with updates slowing to a crawl. Many have also asked if things posted to the wire addons should be added to the SVN as well.
I personally object, I would rather have the wire team choose what should be ported into the official SVN. Remember, for every tool that they put in there, they become responsible for it. This tends to take away valuable time for important functions.
I am adding in wire tools, gadgets, and sents as I find them. I will ask permission first, before adding an item into the repository; if I don't get an answer, and there is no license expressed which forbid redistribution and modification, it will be added anyways. Simply request removal if you are the developer (and can prove it), and it will be removed.
The SVN is located here:Rules of inclusion:
- Cannot conflict with any existing official wire addon, nor any other addon from the extras repository. Should a conflict develop, it must be fixed immediately or placed in a broken branch should someone decide to try and remake it.
- All work cannot have an exclusive copyright. Wire is a group project at it's core, which means people should be allowed to use your code at any time, so long as credit is given. This is what drives it. You may choose a License of your choice, and it will be noted, but it should be compatible with the "Free Software" philosophy. Otherwise, your work will be protected by the latest version of the GPL (currently v3).
- Any major modifications to someone else's work while they are actively developing it needs to be submitted to them.
- Contributors take responsibility for what they commit. For example, if you commit something that you weren't allowed to, then you have the responsibility to remove it, including any implications resulting from the violation.
- Cannot commit anything which supplies or relies on a DLL or another mod. Not all hosts want DLLs running on their systems, and SVN doesn't always give a choice. We don't need broken addons either, should the host decide not to install a prerequisite.
- EXCEPTION to above rule: if an addon does NOT explicitly rely on a copyright model, or addon not included in this SVN, then it may be committed. An exception to this rule would be permission to distribute and use said model, but this will be evaluated on case by case basis.
- Not a rule, but highly recommended: The functions and use of the items going into the repository need to be well documented (does not apply to the lua code, just the in-game item). It is not right to force other people to try and figure out what you were trying to achieve. Valid choices of documentation are: In game help menu, and/or readme.
/trunk repository (Tortoise autolink)
You can get a list of the current addons in the readme!
No username, no password. Install to an addons folder, your choice of the name. I have included a readme which lists the addons, their developer, home thread, and license (if expressed) to the best of my abilities.
Broken Branch:
People can take up projects there and fix them, then release them under a new project name. Might be a little empty, as I will only add projects if the developer is no where in sight, no license was expressed, and would be a useful contribution. Please BROWSE the following link, and then checkout the project you want to fix.
/broken repository
All addons are protected by the GPL v3, copyright by their respective developers, 2007, 2008, unless otherwise stated.
How to Contribute:
I can accept contibutors for this repository, and I will evaluate on a case by case basis. Just ask in this thread.
If you have an addon that I have not contacted you for inclusion, then ask in this thread as well, including a link.
Current Addons:
Readme.txt
Where to ask questions:
This thread pertains to the UWSVN; it is not a support thread for the included tools. Please view the readme.txt in the repository, and look for the tool in question, and ask your question in the linked thread. If you cannot find the tool, ask what package it is apart of, and we will point you to the thread. The ONLY exception to this rule, is if there IS NO home thread.
We cannot answer tool questions because we didn't make them. This is a consolidated repository, not a dev repository.


LinkBack URL
About LinkBacks





.



Reply With Quote





Bookmarks