You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as we keep here all different brand-related graphics we need to make sure it is clear how people can use them from a license perspective.
It is not that obvious for people that IP of the project belongs to Linux Foundation and probably whatever people want they can do with these graphics (as long as they follow guidelines)
investigate what other LF projects use for license, creative commons or something else and create a proper license file in the repo
add to readme a clear note, explanation if people can freely use the graphics and if they need to, maybe reference to asyncapi.com or stuff like that
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
I agree a license should be specified. Being as this is all under the Linux Foundation I am going to assume I can copy these logos, etc. but a license would clearly specify such things.
as we keep here all different brand-related graphics we need to make sure it is clear how people can use them from a license perspective.
It is not that obvious for people that IP of the project belongs to Linux Foundation and probably whatever people want they can do with these graphics (as long as they follow guidelines)
The text was updated successfully, but these errors were encountered: