Provide author guidance notes on multi-license github repositories

[only1chunts]

User story

As a author
I want some guidance on how to appropriate multiple licenses in my github repo
So that I can describe the licenses of the files in my github repo appropriately

Acceptance criteria

Given I am an author thats been told to use multiple licenses in my GitHub repo
When I look for how to do that in GigaDB.org
Then I find a how to guide somewhere (probably in the FAQs?)

Additional Info

There are cases when an author lumps their example data files into the github repo along with their codebase, its convenient for access, but daat cannot be licenses in the same way as code or creative works so we need to tell authors how to put different licenses on the different files.

There are some useful notes here

Product Backlog Item Ready Checklist

• Business value is clearly articulated
• Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
• Dependencies are identified and no external dependencies would block this item from being completed
• At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
• This item is estimated and small enough to comfortably be completed in one sprint
• Acceptance criteria are clear and testable
• Performance criteria, if any, are defined and testable
• The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

• Item(s) in increment pass all Acceptance Criteria
• Code is refactored to best practices and coding standards
• Documentation is updated as needed
• Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
• No deviation from the team technology stack and software architecture has been introduced
• The product is in a releasable state (i.e. the increment has not broken anything)