Project licenses are not recognized by GitHub and are being flagged in PMC reports about open-developer-platform

[mcleo-d]

@brntbeer, is this something you can help champion within GitHub?

[brntbeer]

@mcleo-d I’ll take a look. In the mean time what’s the PMC program?

[mcleo-d]

Hi @brntbeer - The PMC are the Program Management Committee, so the people accountable for leading FINOS programs.

For example, @jbjonesjr is the PMC lead for FINOS Financial Delivery Accelerator and the owner of these types of report for the FINOS FDX program.

Hope helps?

James.

[brntbeer]

@mcleo-d ok. hi. quarantinebrent here and reading this now =)

• What is this report? Is it possible the report is not working correctly?
• What does it mean when you say "GitHub does not recognize them?" It looks recognized to me? is it an API thing?

digging into some things myself in the interim but just wanted to get this moving

[mcleo-d]

Hey @brntbeer

Great to hear from you, I hope you're safe and well? 🤒

I've tagged @maoo too as the issue was reported by FINOS DevOps and the story created by me for reporting and fixing.

Let's get you the information you need 🚀

James.

[mcleo-d]

Hi @udalmik

Tagging you on this item as it relates to the following PR raised by @brntbeer 🤜💥🚀

• finos/plexus-interop#170

Speak soon,

James.

[mcleo-d]

@brntbeer and @udalmik

Thank you for collaborating on finos/plexus-interop#170. It's great to see the pull request merged into the Plexus Interop project 💪

@maoo - Can you help determine if this item is closer to being completed now @brntbeer has helped debug the format of the license information.

@brntbeer - Are there any pointers you noticed that can be communicated to the team so we can learn for next time? 😸

Many thanks,

James.

[brntbeer]

@brntbeer - Are there any pointers you noticed that can be communicated to the team so we can learn for next time? 😸

I think the best thing to do is to reach out to support about this (as they typically have more bandwidth to look into things) AND also ping me on an issue like here, especially if it needs escalated and you're not getting attention on it.

Additionally, if things aren't being detected, i'd just try to re-render a license and see if there's some wonky line endings or something else that may be causing any detections to be bad.

[maoo]

TY @mcleo-d @brntbeer - before engaging with GitHub Support, I'd make sure the LICENSE file is fixed, as it still contains issues, see my last comment - finos/plexus-interop#170 (comment)

If the proposed change doesn't fix the issue either, we can escalate to GitHub Support. WDYT?

[brntbeer]

@maoo yeah, i'd just open a support ticket, include a link to here, the PR in question and say "brent is equally confused, as he copy and pasted our license into another repo and it immediately worked"

[maoo]

@brntbeer - Done! Ticket is #628400

[maoo]

Found the fix! Thanks for the GitHub Support team.

I've renamed LICENSE_HEADER to FILE_HEADER and add-license-headers.bat to add-file-headers.bat. Now Apache-2.0 shows on the top right of https://github.com/maoo/plexus-interop page.

PR submitted to finos/plexus-interop#171

[maoo]

All done! Closing issue.