eclipsefdn-project-adopters merge requestshttps://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters/-/merge_requests2024-03-28T15:15:02Zhttps://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters/-/merge_requests/263chore: Remove broken configmap operation2024-03-28T15:15:02ZZachary Sabourinchore: Remove broken configmap operation* chore: Remove broken configmap operation* chore: Remove broken configmap operationZachary SabourinZachary Sabourinhttps://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters/-/merge_requests/258Iss #198 - Switch project filter to use industry_collaborations for WG2024-03-22T20:19:32ZMartin Lowemartin.lowe@eclipse-foundation.orgIss #198 - Switch project filter to use industry_collaborations for WG* Iss #198 - Switch project filter to use industry_collaborations for WG
Resolves #198* Iss #198 - Switch project filter to use industry_collaborations for WG
Resolves #198https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters/-/merge_requests/207Draft: Add information about organization logos2024-03-19T13:02:54ZChristopher Guindonchris.guindon@eclipse-foundation.orgDraft: Add information about organization logos## Summary
Add additional information in the README.md of this project about organization logos.
This MR hopes to solve some concerns that were reported by @carmendelgado via this issue:
https://gitlab.eclipse.org/eclipsefdn/marketing/...## Summary
Add additional information in the README.md of this project about organization logos.
This MR hopes to solve some concerns that were reported by @carmendelgado via this issue:
https://gitlab.eclipse.org/eclipsefdn/marketing/-/issues/1643#note_1121529
## Changes
1. Added a section on logo licenses to cover logos from organizations that are typically copyrighted by them.
2. Added a new section in the adopter's issue template asking the user to confirm they have permission to contribute the org logo. I am also asking them to provide information about their current relationship with that organization.
3. Created a new MR template to ensure that we ask the same question if the user decides to provide the logos via an MR instead of an issue.
## Concerns
We actually don't have a proper way to validate that a user is actually an employee. Could we reduce some of the risks by requiring that every user that provides a logo to this project must have an ECA on file with us before we include it?
//cc @croundy @shmacdonald