Is a way to automatically set your own default permissions on your prims as they are created?

[Madeline McMinnar]

I am working with a team of builders/ scripters on several projects that involve collaborative building.  Sometimes several people might work on one build.  For example, one person might build it, another texture it and someone else will script it.  Sometimes several people will build part of the same object or modify something they didn't create.  We use group tags and check the share feature in the building tool, and allow each other to edit our objects,  but that doesn't seem to be enough.  Is there a way to set your own default next owner permissions the way you do when uploading textures, so that you don't have to remember to change it on every prim? 

Also, I know there are other people who build collaboratively.  What suggestions do you have for making the process as easy as possible?  What solutions hav eyou come up with? 

 

[KarenMichelle Lane]

Madeline,

Two ways come to mind.

1) Create a Master Object Folder with standard objects, pre-textured and sized and oriented as you wish with all permissions set accordingly - Then pass those out to the whole team to use in creating new objects for the project.

2) Using Phoenix or Firestorm - you can have everyone specify the object creation defaults - This is harder as it's like herding a clutch of cats and making sure everyone sets the defaults the same is out of your control.

Advanced Project Management

The other way is to create a Boss Avatar responsible for checking parts out and in of a collaborative build to the person assigned to the next build / scrip[ting activity on the project plan. The project team member then checks the part of the project they have in inventory back to the Boss at regular intervals so that you maintain a version of each step of the building project.