I'm wondering about the following. I think the "based on X" conversation is already happening at a general level and I believe participation at that level is better, since this will probably be simple and generic and VP Brand Management will likely take a position that applies to us also.
I thought "powered by X" was also being discussed at a cross-project level. I may have been mistaken. The conversations went across different lists and I lost track. I suspect VP Brand Management may set a policy there too. I think in practice there will always have to be treatment on an individual-case basis. Any cookie-cutter test would be simply a starting point for a negotiated agreement that could be rescinded if an user of the marks violates the agreed conditions. I have no prediction how that would go. Those were somewhat open discussions that arose out of what happens if someone distributes builds of unreleased code, and what about when someone other than the project distributes binaries of released code, with none to significant alternations. How can the Apache Project marks be used under those conditions? It would be good to see what conclusions have been reached, if reached yet, and rely on that broader analysis if possible. I didn't think there was any notion of required labelling so much as indicating how one of those distributions could indicate relationship in a way that did not violate trademarks. I am not certain there was anything about required based/powered but rather conditions under which those would be allowed to be used, although others, including Dave may have raised the prospect. We should look again there. What were your take-aways from those discussion, Dave? - Dennis -----Original Message----- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Saturday, August 29, 2015 18:13 To: dev@openoffice.apache.org Subject: Re: Limiting Trademark Policy Discussion (was RE: [REPORT] PMC 2015-07 Private-List ...) As me from my soapbox: [ ... ] I think that the project should have an open source code test for Powered By that applies to all. The rights to use are clear for all. The obligations spelled out. Benefits given equally. [ ... ] Once we have a proposal that the community likes we can go through any type of confirmation or clearance the Brand committee requires. I expect that this discussion should proceed carefully and not rush into set form but instead collect ideas focusing on different parts. There must be an opportunity to heal rifts with respect for all. Are you open to that discussion? Are you open to any and all to that discussion? This process is not against any group, but for all. Regards, Dave [ ... ] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
