Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] Putting "Legal Documents" into *every* repository root

Greetiings Eclipse Technical Advisory Council!

I require your advice.

I'm using the term "legal document" very loosely to mean files like README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, NOTICES, SECURITY, AI_POLICY, etc.

Our recommendations/requirements in terms of how "legal" files are represented needs to be updated. Our current recommendations were drafted some time ago and reflected the best advice of the day, based on the services available then and how we leveraged them.

I've opened an issue to discuss a change. TL:DR: I believe that a subset of these files are specific to the individual repository and must be propagated to forks, while the remaining files are specific to the project's life as an Eclipse project and can (should?) be represented in each project's .github repository as a default for all repositories.

Please express your opinions, concerns, and advice here.

Thanks,

Wayne
--

Wayne Beaton (he/him)

Head of Open Source Projects | Eclipse Foundation


Back to the top