[
https://issues.apache.org/jira/browse/SENSSOFT-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated SENSSOFT-308:
----------------------------------
Description:
Apache SensSoft's name is changing! (Passed by Unanimous Vote!)
For each nomination submitted to [email protected], perform
research on the name to confirm that it is clear of "collisions" with other
products in the same class. "Collisions" can include both infringement on
protected marks (Trademarks), as well as brand confusion with other similar
products that would make it difficult to discover our products. As outlined in
ASF Guidelines, this exercise is both due diligence and marketing
([http://www.apache.org/foundation/marks/pmcs.html]).
Each nomination will be investigated in separate tickets in the
[PODLINGNAMESEARCH|[https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-142?filter=allopenissues]|https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-142?filter=allopenissues].].
For ease of reference and tasking progress, we will create sub-tasks under
this ticket linking to relevant PODLINGNAMESEARCH tickets. Note that all
research artifacts and findings need be documented in the PODLINGNAMESEARCH
tickets. These tickets have nice templatized structures to ensure the right
searches are being accomplished.
was:
Apache SensSoft's name is changing! (Passed by Unanimous Vote!)
For each nomination submitted to [email protected], perform
research on the name to confirm that it is clear of "collisions" with other
products in the same class. "Collisions" can include both infringement on
protected marks (Trademarks), as well as brand confusion with other similar
products that would make it difficult to discover our products. As outlined in
ASF Guidelines, this exercise is both due diligence and marketing
([http://www.apache.org/foundation/marks/pmcs.html]).
Each nomination will be investigated in separate tickets in the
[PODLINGNAMESEARCH|https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-142?filter=allopenissues]
project (with each research task represented in sub-tasks under SENSSOFT-308,
cross listed . Each subtask will link to a wiki page that will allow us to
capture research for that name. Templatized wiki pages will ensure that we are
doing the right research.
To perform an appropriate search, use internet search tools (e.g., search
engines) to search for usage of nominated project names and for technical terms
to see if similar names are used by similar products (e.g., user logs, user
activity software, clickstream, etc., etc.).
There are two required searches: Google (or similar), and USPTO. Details and
instructions for searching USPTO can be found on the linked Wiki page below.
> [NAME SEARCH] Research Nominated Names
> --------------------------------------
>
> Key: SENSSOFT-308
> URL: https://issues.apache.org/jira/browse/SENSSOFT-308
> Project: SensSoft
> Issue Type: Task
> Reporter: Joshua Poore
> Assignee: Joshua Poore
> Priority: Major
>
> Apache SensSoft's name is changing! (Passed by Unanimous Vote!)
>
> For each nomination submitted to [email protected], perform
> research on the name to confirm that it is clear of "collisions" with other
> products in the same class. "Collisions" can include both infringement on
> protected marks (Trademarks), as well as brand confusion with other similar
> products that would make it difficult to discover our products. As outlined
> in ASF Guidelines, this exercise is both due diligence and marketing
> ([http://www.apache.org/foundation/marks/pmcs.html]).
> Each nomination will be investigated in separate tickets in the
> [PODLINGNAMESEARCH|[https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-142?filter=allopenissues]|https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-142?filter=allopenissues].].
> For ease of reference and tasking progress, we will create sub-tasks under
> this ticket linking to relevant PODLINGNAMESEARCH tickets. Note that all
> research artifacts and findings need be documented in the PODLINGNAMESEARCH
> tickets. These tickets have nice templatized structures to ensure the right
> searches are being accomplished.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
