I've created a group which is called, appropriately enough, "Wiki Build". The group is open invite and free to join. ANYONE is welcome to join this group, come to the fairly large Wiki Build land in Dalton, and contribute to Wiki Build by building new objects or editing existing objects that were contributed by other builders. The first iteration of this project will mostly serve to help us all learn HOW it should work, so there are only a few simple rules for contributers right now, which you're all welcome to help me revise. I feel that these simple ground rules will help the project to flow smoothly.
First of all, each build, or iteration, will last for a predetermined length of time. For now, we'll make that 30 days. Each build will have ONE "anchor object" that can not be edited (although it can be added to). For the first build, I've chosen a wooden sailing ship in a small harbor as the anchor object.
The purpose of this anchor object is to set an overall vague "theme" for the build, which contributions should build upon. At the end of the 30 day period, we will take a bunch of pictures, have a party, etc, and then wipe out this iteration. Then, everyone will be welcome to rez a new "anchor object", and the group will vote on which object to start the next build with. By the way, Wiki Build's first contributor has already built a dock linking the wooden sailing ship to the land.
I hope this is a good example of how the project will work.The second rule for this project controls HOW objects are to be contributed. It is important to keep in mind that Wiki Build is NOT a sandbox, but a collaborative community build. With this in mind, any prims that you contribute must have certain permissions set, which will allow other group members to revise them (and yes, even remove them) at will.
You must have the Wiki Build group active when building, so that your objects will be associated with the right group. You must also turn on the "share with group" check box on each prim. Finally, you must turn on all three checkboxes under the permissions for the next owner. When you set your prims up in this way, it will allow anyone participating in the project to revise them. At this time, it is not required to DEED the prims that you contribute to the group. Simply turning on "SHARE with group" should be okay.
The final rule is that all contributions must be wholly within the property line of the Wiki Build land, BELOW cloud height, and COMPLETELY PG in nature, as Dalton is a PG sim. That's it for rules, for the time being. I'd like to use the first iteration of this project mainly so we can all explore HOW we should structure it. I'd like to figure out a lot of things from this iteration.
First of all, I'd like to figure out if there is even any interest in collaborative building projects.
I'd also like to figure out what kind of ground rules we need, and what roles and permissions the group will need when 1.12 is released. For example, under what circumstances can you edit or remove someone else's work? Can you just do it? Should you talk with them first? Should there be a "core team" of some sort? Also, how will we deal with grief? I'm sure that LOTS of questions like this will pop up during the next month. We'll have to have some meetings and decide what the answers are together.Finally, a few notes on the land. The current Wiki Build lot is a little larger than 1/4 sim. This leaves a lot of prims to be desired.
If we run out though, that's okay. We can edit things to make them more prim-efficient, or even remove things that aren't as important to the build as we had thought. We will have to work together to figure out the right protocols for this as well.Also, I will get a donation box up soon. If there proves to be a lot of interest in Wiki Build, and donations can support tier on an island, I'll probably get one for us. I hope that a lot of people will participate in this project, and that we will all make a lot of new friends, and have a great time building together and learning from each other.