Re: SPI resolution 2012.09.13.bg.1, TideSDK as associated project

On Thu, Aug 25, 2011 at 02:07:57PM -0600, Bdale Garbee wrote:
> TideSDK is used to create multi-platform desktop apps using HTML5, CSS3
> and JavaScript. It is the current, community-based incarnation of the
> former Titanium Desktop. The code is all licensed Apache v2.0, and
> based on my conversations with the project leader David Pratt, there
> appear to be no unusual issues or needs. The project is gaining
> momentum and needs a destination for pending corporate donations.

In a web search, I found this Google Groups thread mentioning a licensing issue to resolve related to the old TiStudio license from Appcelerator:

https://groups.google.com/forum/#!topic/titanium-desktop-transition/L3BhEgSjb4c

My understanding from reading that thread and the TideSDK blog is that
Appcelerator was interested in resolving the issue, which is great. However
before I can vote yes I do need to understand the current state of that
resolution, and if it's not fully resolved, what the plan is. SPI can certainly
leverage its legal entity status to accept copyright assignment or sign some
contract to solve the issue if needed, but TideSDK should be past the stage of
substantive negotiations before associating with SPI.

The rest of what I mention in this mail will not interefere with me voting yes.

One typo fix:

> 4. David Pratt is recognised by SPI as the authoritative decision maker
> and SPI liaison for TideSDK. Successors will be appointed by concensus
> of the TideSDK Team as defined on the tidesdk.org web site.

s/concensus/consensus/

The same issue exists as in the OBF resolution - we should probably archive a
copy of the relevant part of the TideSDK website and ask David, or failing that
the TideSDK Team, to notify us when David's role or the Team membership
changes.

Interesting also that the authoritative decision maker and the body which can
choose another authoritative decision maker are distinct.... I'm increasingly
agreeing with Ian that we should figure out a better phrase than "authoritative
decision maker" and revise all of our project relationships, with consent of
course, before any of our projects have a divisive succession battle.

- Jimmy Kaplowitz
jimmy(at)spi-inc(dot)org