-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual material for stages used in annoucement of projects without logos #217
Comments
Even though the incubating neck isn’t in the right spot, I like these!
|
The bottom of the incubating eggshell should probably line up with the bottom of the sandbox eggshell |
Also, "Project" is used for software/code efforts and now specifications/specs. Do we want to broaden the graphics to reflect "Technical Initiative" or "TI" so that it would be applicable to WGs, SIGs, and Projects? |
I think these graphics are great! I agree with CRob's point that it'd be good to broaden the scope, unless we can have variants for WGs and SIGs? |
I suggest just removing "Project". These are awesome! |
I suggest re-naming the second category to "Hatching" and moving "Incubating" to replace sandbox! Best to not mix metaphors! |
You have a point but sandbox and incubating are already commonly used across LF. |
Looks great. Thank you! |
I've uploaded these as individual files (thanks @hythloda ) for use: https://github.com/ossf/tac/tree/main/files/images |
We have these generic badges for the stages of each project to accompany the blog posts for announcements. We find it difficult to announce projects without visual materials like logos, so these materials will be used when projects are announced and do not have logos yet (such as sandbox projects coming into OpenSSF).
Below are the designs and we would love feedback before we start using them.
An alternative solution would be to provide logos to all incoming projects via the operating model that is in the works. However, that is a larger discussion beyond the scope of this issue.
The text was updated successfully, but these errors were encountered: