It looks
like Marc and I started at the same time (but he got in
ahead). Here's my response anyway...
Note that it is important that the project operate in an
open and transparent manner. There needs to be a so-called
"level playing field" where all comers can participate
equally. If there is a perception that the project is an
"HP Project", then that will dissuade the community from
participating.
It's okay to indicate that the work is being done by HP,
but you need to take care with your website and
communications to make it clear that the project is not
owned by HP and that participation is welcome.
More comments/answers in line.
Wayne
On 09/11/14 11:30 AM, Zafrir, Harar
wrote:
1.
score
Trademark ownership
score is a part of an existing
HP Software product, but was not publically used by
anyone outside Eclipse Foundation yet.
·
Should
the
Trademark Transfer Agreement be signed? If so –
who is authorized (as far as EF can say) to sign it by
the name of “HP Software”?
·
Will
that agreement also cover logo images? (agreement seems
to refer to TM and domain names only)
AFAIK, the Eclipse Foundation has
already claimed the trademark so a transfer agreement is
not necessary.
AFAIK we don't tend to explicitly trademark project logos.
As an Eclipse project, you need to take care to not
infringe on the trademarks of others; if HP decides to
give a logo to the project, they have to treat the logo as
the project's property and HP would have to follow the
same rules as everybody else regarding their use (see
below).
Janet or Mike will correct me if I'm mistaken.
2.
Mentioning
score in HP Software’s publications
Which
rules are apply when mentioning / referring to score
as an Eclipse Foundation open source project – in HP
Software publications?
You can find answers to your trademark questions here:
https://www.eclipse.org/legal/logo_guidelines.php
(look for "Proper Usage of Eclipse Project Names and
Logos")
3.
EPL
v1.0 was not approved yet by HP Software
HP Software has a process for
approving code to be contributed as an Open Source
project.
This process was initially
launched with the request to approve Apache v2.0
license.
Later on (following the
progress we made with Eclipse Foundation), we have added
the request to include EPL v1.0 as well.
This process was not completed
yet, so at the moment we only have approval for Apache
2.0, and approval for EPL 1.0 is pending.
·
Is
it possible to temporarily use Apache 2.0 only?
·
If
not – could we delay our code contribution until we
receive our final approval?
Since score is dual licensed, the code needs to be
contributed as such. In the meantime, don't make any code
available until you've secured permission to contribute it
under the project licenses.
So... wait to initiate the initial contribution process
until after you've gotten the necessary internal
permissions.
4.
Copyright
HP Software
We would like to keep a
copyright notice for HP Software – for all the code
included in the initial contribution.
Does that comply with Eclipse
Foundation licenses and guidelines?
Please do keep the copyright. It is standard practice that
the copyright be retained by the owner.
Please see
https://www.eclipse.org/legal/copyrightandlicensenotice.php
5.
Released
artifacts group ID
·
Must
we change group ID to org.eclipse?
·
Can
we use com.hp.score?
Bundle names and Java packages should
all be changed to org.eclipse.score.*.
I believe that for Maven, we've been using the convention
of including the project name, so the Group ID would be
org.eclipse.score.
There's more here:
https://wiki.eclipse.org/Development_Resources/HOWTO/The_Eclipse_Code_Namespace_Policy
6.
Using
HP’s logo in project content – inside Eclipse Foundation
What
rules apply when we use HP Software’s name / logo
inside Eclipse Foundation project pages?
We
can see for example in BIRT, that ACTUATE logo is
present.
Could
we use HP Software’s logo the same way?
The rule
is that member companies that are contributing ongoing
resources (i.e. at least one commit every three months) to
a project can display their logo on the project page.
Given that HP is a member and that there is an ongoing
effort to get the code contributed, it would okay to
include an HP logo and link on the project page.
We display company logos automatically on the project
information pages (based on commits in the associated git
repositories).
e.g. https://projects.eclipse.org/projects/soa.stardust
More here:
https://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata#Company_Logos