MPL "tailoring" question

[Wes Bethel]

greetings,

in conjunction with a recently announced open source project, we
intend to use MPL 1.1 as the basis for our open source license.
however, some modifications to MPL 1.1 are necessary in order to
tailor it to our particular project. we have minor concerns about
how such tuning may delay obtaining OSI certification for the
license, and are curious about the community's experience in
such matters.

a draft version of our license may be inspected at:

	http://openrm.sourceforge.net/license.html

that license file clearly shows what was removed from MPL 1.1 and
what was added. in brief, none of the license terms were modified;
it's still MPL 1.1. "Netscape" was replaced with R3vis, and we
assert rights to Branded Code, much in the same way that Netscape
asserted similar rights to their browser code. as per the terms
of MPL, the name of our license was changed so that it is no
longer MPL, but the R3vis Open Source License. otherwise, there
are no changes.

the MPL appears to have tunable parameters engineered in to the
license. one would assume that using these handles in the intended
fashion would not cause any significant delays in obtaining OSI
certification. 

specifically, is OSI likely to approve use of their mark for our
project with this license (at the above URL)?

your feedback is appreciated. happy holidays!
wes
-- 
\\///\\\/\/\/\\\/\/\/\/\\\\/\/\///\/\/\\/\/\/\\\/\/\//\\/\\//\\\\\\////\
Wes Bethel                                             wbethel at r3vis.com
R3vis Corporation                                          www.r3vis.com
Phone: (415) 898-0814                                fax: (415) 898-2814
\\///\\\/\/\/\\\/\/\/\/\\\\/\/\///\/\/\\/\/\/\\\/\/\//\\/\\//\\\\\\////\