Thank you for the clarification Alex,

1) I'll add the the "Licensed to the Apache Software Foundation (ASF)"
comment block on every files with the google material reference like this:

////////////////////////////////////////////////////////////////////////////////
//
//  Licensed to the Apache Software Foundation (ASF) under one or more
//  contributor license agreements.  See the NOTICE file distributed with
//  this work for additional information regarding copyright ownership.
//  The ASF licenses this file to You under the Apache License, Version 2.0
//  (the "License"); you may not use this file except in compliance with
//  the License.  You may obtain a copy of the License at
//
//      http://www.apache.org/licenses/LICENSE-2.0
//
//  Unless required by applicable law or agreed to in writing, software
//  distributed under the License is distributed on an "AS IS" BASIS,
//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//  See the License for the specific language governing permissions and
//  limitations under the License.
//
//
//  This product bundles Google Material fonts and icons available under a
//  CC-BY-4.0 license.
//  For details, see <src\spark\material\assets\fonts\Roboto.swf>.  Source
//  for these fonts and icons are available at:
//  https://github.com/google/material-design-icons
//
////////////////////////////////////////////////////////////////////////////////


2) I'll provide the signed ccla[2] and ccla[3]. But where do I submit the
ccla?


Thanks,
Rui

2016-03-22 14:41 GMT+00:00 Alex Harui [via Apache Flex Users] <
[email protected]>:

>
>
> On 3/22/16, 3:54 AM, "Rui Cruz" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=12334&i=0>> wrote:
>
> >This is just a skin.. and I also have full support from my company :)
>
> Hi Rui,
>
> The key question is whether your company is the true "owner" of these
> files.  If you are an employee then usually the company owns the work.  If
> you did this work after hours without any company resources, then it
> depends on your employee agreement.  For me, my employer even owns after
> hours work.
>
> Assuming the company owns these files, because it is an existing code
> base, the normal process is to fill out a Software Grant [1] and have it
> signed by someone in the company who is authorized to sign contracts.
>
> However, I think that because this is "just a skin", it would be ok to
> have someone who is authorized to sign the much simpler CCLA [2] and
> authorize you to sign an ICLA [3] which are needed anyway so you can make
> changes in the future to these files in an Apache repo.
>
> [1] https://www.apache.org/licenses/software-grant.txt
> [2] https://www.apache.org/licenses/cla-corporate.txt
> [3] http://www.apache.org/licenses/icla.pdf
>
> The reason for all of this paperwork is so that users of your code can
> trust that Apache has checked the files truly can be used under the Apache
> License.  It is sort of like knowing the food you eat has been inspected.
> Otherwise some potential users and contributors might shy away from using
> and contributing.
>
> >
> >I think the apache licence on each file would be fine (maybe when I merge
> >the develop branch is a good time for that).
> >
> >do I have to reference the material design from google too
> >(fonts/guidelines/icons)? If yes, can you provide me the text/example
> >please? (I think its all creative commons)
>
> It depends on if you have included these fonts and icons in the set of
> files.  If you have, assuming there isn't any "source code" for the
> fonts/guidelines/icons involved, you would add to the LICENSE some text
> like:
>
> This product bundles Google Material fonts and icons available under a
> CC-BY-4.0 license.
> For details, see <path to folder(s) containing fonts and icons>.  Source
> for these fonts and icons are available at:
> https://github.com/google/material-design-icons
>
> Thanks,
> -Alex
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12334.html
> To unsubscribe from Spark components with Material Design, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11042&code=aW5mby5ydWljcnV6QGdtYWlsLmNvbXwxMTA0Mnw0OTE5NTg4MDE=>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://apache-flex-users.2333346.n4.nabble.com/Spark-components-with-Material-Design-tp11042p12337.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Reply via email to