[opensource-dev] Third party viewer policy

Carlo Wood carlo at alinoe.com
Wed Feb 24 16:12:46 PST 2010

On Tue, Feb 23, 2010 at 12:45:01PM -0800, Brent Tubbs wrote:
> For a while I've been batting around the idea of creating an SVN-bot to enable
> much-improved version control for inworld scripts; a must-have when you're
> developing as part of a team.  The same-creator policy on content export would
> seem to prohibit that though.
> I realize that you probably don't want to have different rules for each
> different content type, but the one-size-fits-all rule in the current policy
> doesn't fit scripts well at all.

I didn't even READ the TVP all that well, I'm just going to
stubbornly use my own common sense. If anything that is not
common sense is going to be enforced then by all means I don't
want to be part of SL anymore.

In this case the common sense says: If something is full perm,
you may export it. Second Inventory does this, and I doubt
that is suddenly made illegal.

Scripts that a team work on are definitely full-perm (from the
point of view of SL permissions), so you can export it all
you like.

Carlo Wood <carlo at alinoe.com>

More information about the opensource-dev mailing list