[FEATURE] Append MPL headers on source
See original GitHub issue🚨🚨 Feature Request
- A new implementation (Improvement, Extension)
Is your feature request related to a problem?
Hub currently uses Mozilla Public License (MPL), which requires the following header (from Exhibit A of the license) to be attached to source.
This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.
We need help appending MPL headers on source (where appropriate).
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (18 by maintainers)
Top Results From Across the Web
boost::mpl: How to generate pre-generated header files for ...
I want to code a state machine which has a reaction list with more than 50 entries. I found here some python scripts...
Read more >Mozilla License Headers
This page gives copy-and-pasteable license headers for Mozilla code. When adding license headers to new files to be checked in to the Mozilla...
Read more >authentication-headers/MPL-2.0 at master
library for the generation of email authentication headers - authentication-headers/MPL-2.0 at master · ValiMail/authentication-headers.
Read more >Setting an MPL Log Level at a Message Level in SAP CPI
Let's add the mentioned header to the earlier used request message, set the header's value to debug and send the amended request to...
Read more >Releasing Project Source Code Under MPL 2.0
Is it acceptable to add MPL 2.0 license notice header to each project source file ? Project Source File Example:
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@KrishnaChaitanya1 done, thanks for helping us 👍
@KrishnaChaitanya1 could you remove
test/filtering2/meta.json
and the like files from the commit? That might be a fix. Afterwards, make a PR. It’d be easier to check the with the CI output