[opensource-dev] Third party viewer policy
brent.tubbs at gmail.com
Tue Feb 23 12:45:01 PST 2010
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.
On Tue, Feb 23, 2010 at 12:37 PM, Robin Cornelius <robin.cornelius at gmail.com
> On Tue, Feb 23, 2010 at 8:31 PM, Soft Linden <soft at lindenlab.com> wrote:
> > Mike's correct.
> > If you see any wording that's ambiguous about that, let us know.
> > _______________________________________________
> Well you seem to have spelled the end of my debian/ubuntu project, I
> can not meet the tems of the third party viewer policy:-
> "On your software download page or in another location that a user
> must visit before installing the Third-Party Viewer, you must disclose
> the following:"
> I cannot do this with an apt-repository, the user can bypass every
> possible webpage or description field. and the fact the policy says
> this is a MUST. The only possible way to do this is to create a custom
> program that displays a screen during the install hook of the package
> and aborts the package install. This can no longer be accepted in to
> the main debian or ubuntu repositories.
> Also it appears that i cannot use the snowglobe logo or name, even
> though i'm basicly building from almost prestine source. I though this
> was the entire point of the snowglobe rebranding, but now we are
> exactly where we were with secondlife 12 months ago.
> Policies and (un)subscribe information available here:
> Please read the policies before posting to keep unmoderated posting
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the opensource-dev