Fix issues needed prior to graduation #2544
Comments
|
@zeagord can you do me a favor and hunt the issue tracking our need to click "Scan Repository Now" and cite it under the first bullet point? I think I've lost a fair amount of time so far forgetting for a half hour to click this and I think we need to track this somewhere in our domain. |
|
Wow I'm bad at GH notifications nowadays. On it right now. |
|
added some tasks coming out of https://lists.apache.org/thread.html/81b6cb8d23f287ec95f80f0ede0c00601a600d54a30a1bf4e7423283@%3Cdev.zipkin.apache.org%3E cc @apache/zipkin-committers |
|
I've asked if maybe someone can help donate a new logo as that is easier than explaining how a logo already used widely is somehow exclusively now the property of apache |
|
@adriancole Good to have this issue. I forgot to share this. Docker image relatedSkyWalking DockerHub repositories have been asked having potential branding issue as well, just before one month before graduation, because of the same name and same logo. This is the last thing I deal with before graduation proposal. I moved the SkyWalking's to ASF official docker repo |
|
@wu-sheng can you share any issue with details about this, jira or github? right now, we publish via quay.io and we have access there and also dockerhub. I've noticed in ASF often we don't have full access to things.. can you share some details? |
This comes from Justin as well, but in private ml. And our mentor, Ignasi, explained the concerns. The reason is very similar to the concerns of openzipkin logo. ASF doesn't want to make the confusions about which things belong to ASF or 3rd party, especially when the INFRA controlled by the same people in the PMC.
Right now, several PMC members(Hongtao Gao mostly) publish the docker image to dockerhub directly. |
|
On the docker topic, as I understand it, the problem is advertising a third party image. Clearly, there is no requirement to even have a docker image. For example, Kafka produces none, though the commercial company behind it does. I can grok not wanting to be a sneaky ad for a commercial package, but I don't know where exactly a problem would be in mentioning images that predated apache and are completely non-commercial in nature. It seems odd that Apache would actually have a problem with a healthy ecosystem that produces tools for it to the point where it intentionally wants you to make it hard to find them. However, we seem to be in a culture which is against things and I am tired of arguing against the grain for sensible pragmatism. I think the work and confusion involved in splitting our docker images between the openzipkin namespace and apache namespace is more of a burden than instructing people manually how to find docker images. What that seems to mean is deleting references to the openzipkin images until the leadership in ASF decide that OSS ecosystems are nothing to be afraid of. |
|
@adriancole could you explain what the |
|
Sorry @jeqo, since @adriancole is still off, will try to help you here. This file is generated by https://issues.apache.org/jira/browse/MPOM-218 it was not generated anymore. Hope it helps. |
|
DEPENDENCIES is not a blocker per https://lists.apache.org/thread.html/4edaa84d2425b40f252f0ea0b1dbf7b8ca8299fd6d23de7f9df62d85@%3Cgeneral.incubator.apache.org%3E but it is a nice-to-have. removing from this issue description now. |
|
on the logo, we have a rough understanding that LINE (brokered by @syleeeee) will offer a logo to use for Apache Zipkin (different than OpenZipkin). Thanks in advance for the help! Next step is to discuss on the mailing list https://lists.apache.org/list.html?dev@zipkin.apache.org
|
|
Closing this as Zipkin has withdrawn from the Apache Incubator. |
For each of the below, please cite a mail thread or closed issue when ticking the box.
The text was updated successfully, but these errors were encountered: