Sorry for the late reply. Just came back from a business trip starting
from Monday. This year is tough, especially for small infra tech
companies in China, so most mentors are busy struggling to support the
company's business. That's partly the reason why this project has 6
mentors. We have limited time but we still want to help the project
and more mentors can back up each other.

I used to work at Xiaomi, from 2016 to 2021. I know these guys, they
have the passion to contribute to open source, although they are not
much familiar with open source. That's also the reason why I accept
their invitation to be the mentor of this project.

On the OzHera project, it is still in a very early open source stage,
so we agree that it is better to polish it for a while before joining
the incubator. Thanks to all the people in this thread for pointing
out the problems. The mentors will help the project to solve these
problems, or at least introduce a plan on how the problem will be
solved.
Including but not limited to
1.Split the mono repo and give OzHera a separated repo. So we can make
clear the scope of donation, and also make sure that OzHera can be
built and run separately.
2.Build the process for decision making and code contributing, follow
the open source and Apache way.
3.On the dependencies in Category X, it requires code changes, so it
is not easy to have a clear deadline. The mentors will help the
project to have a clear path on removing these dependencies. Mysql
connectors and ES are widely used and lots of Apache projects have
already solved the problem, so I'm optimistic this can also be solved
in OzHera.
4.About the potential IP conflicts with Alibaba, the two teams have
already reached a consensus offline and the issue has been closed. And
it is another part in the mono repo, not OzHera, so it will not
introduce any risks to ASF. The mentors will check OzHera carefully
and try to avoid other potential IP conflicts.
5.Internationality improvements. Introduce English version for the
documentation and also change the official developing language to
English. Since the main users are Chinese, the mentors will discuss
with the project team on how to balance.
6.On other things like the differences compared to Apache Skywalking,
the mentors will make sure to include the information in the next
proposal.

Thanks again. Hope we can be back soon.

tison <wander4...@gmail.com> 于2023年9月8日周五 01:02写道:
>
> After a detailed review of the proposal, I'd suggest the champion check the
> content of the proposal before starting the discussion:
>
> > Documentation about Linkis can be found at
> https://github.com/XiaoMi/mone/blob/master/ozhera-all/README.md . Following
> links provide more information:
>
> Linkis?
>
> > The contributors of OzHera are actively involved in Apache community
> projects, and every member can access the project roadmap, issues, and code
> through various channels such as mailing lists and JIRA. By entering the
> Apache incubator, we believe OzHera can receive broader promotion and
> participation from companies and individuals.
>
> I don't find OzHera has associated "Mailing list and JIRA".
>
> > In this project, exceptional contributors are recognized and rewarded,
> fostering a collaborative and inclusive environment where decisions and
> project development are driven by capabilities and contributions.
>
> No evidence to show promoted contributors. The two proposed initial
> committers contributed trivial works just before a few days this proposal
> last modified.
>
> * Detoxify - https://github.com/XiaoMi/mone/commits?author=Detoxify
> * kongniancp - https://github.com/XiaoMi/mone/commits?author=kongniancp
>
> > elasticsearch Apache License, Version 2.0
>
> I agree that a single dependency entry bug is not easy to find. However, MySQL
> and ES are required as the storage of this project. If you check the
> essential architecture of this software, it should be noticed.
>
> > mysql-connector-java The GNU General Public License, Version 2
>
> You may ask the project to group dependencies by its license and then you
> can find dependencies licensed by GPL or other Category X licenses.
>
> Best,
> tison.
>
>
> Sheng Wu <wu.sheng.841...@gmail.com> 于2023年9月7日周四 21:07写道:
>
> > Sheng Wu <wu.sheng.841...@gmail.com> 于2023年9月6日周三 22:52写道:
> > >
> > > They are already beginning to remove the screenshots and comments that
> > > have proved the UI copy behaviors.
> > > They had known that and did that intentionally.
> > >
> > > Screenshots, https://twitter.com/wusheng1108/status/1699432297429114959.
> > > Now, if you see the issue again, it is
> > > gone.https://github.com/XiaoMi/mone/issues/689
> > >
> > > They have admitted their UIs are similar(most likely directly
> > > referring) to Aliyun Yunxiao commercial services. (Translation from
> > > their top3 maintainer's feedback)
> > >
> > > Anyway, I think the evidence is clear, there are bigger issues than
> > > `too-early-to-join`.
> > > AFAIK, the project and the maintainers are not suitable for ASF
> > > culture, even hard to say good enough in the OSS culture.
> > >
> > > More and more China local foundation members and PPMC members are
> > > showing up to share their concerns and consensus of saying NO to the
> > > project.
> > > They have all the right to do things on their own, but let's keep the
> > > foundation and incubator safe from this kind of chaos.
> >
> > One update, Xiaomi Inc. and Aliyun Inc. seem to have some confident
> > agreement on this issue.
> > The issue title has been updated as `have settled`(translated from
> > Chinese).
> > And original complaint had been removed too.
> >
> > I want to point out, this doesn't mean it is good for the foundation.
> > From the current statement, we can only guess there are conflicts, but
> > they have an agreement.
> > But they don't declare that the UI design is IP clearance.
> > This should be hold as a potential IP issue.
> >
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > > tison <wander4...@gmail.com> 于2023年9月6日周三 22:36写道:
> > > >
> > > > > attaching the screenshot
> > > >
> > > > I don't see an attachment in your email. If you paste the screenshot
> > > > inline, it can be filtered out by mailing list policy. You can attach a
> > > > file or upload it to an external image hosting service.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > >
> > > > Sheng Wu <wu.sheng.841...@gmail.com> 于2023年9月6日周三 21:23写道:
> > > >
> > > > > One more update.
> > > > > With this project being noticed by this project, the parent project
> > is
> > > > > facing the challenge of copying from Ali Yunxiao, which is one of the
> > > > > Aliyun commercial services.
> > > > > Ref source in CN, https://github.com/XiaoMi/mone/issues/689,
> > attaching
> > > > > the screenshot in case of the owner deleted this issue.
> > > > >
> > > > > The good thing is, that this is not the ASF and incubator issue, we
> > > > > don't have an obligation to prove this is true or false.
> > > > > But this is a validation of my feelings that this project was not
> > > > > audited carefully, although one of them declared they are.
> > > > >
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > > Calvin Kirs <k...@apache.org> 于2023年9月6日周三 20:15写道:
> > > > > >
> > > > > > Is this a (community) with only 38 issues?
> > > > > > There are tons of commits from the community. How does the decision
> > > > > > happen? ok, I saw this, relying on Gitter[1] with only 6 people
> > and 8
> > > > > > messages?
> > > > > >
> > > > > > pls forgive me, after reviewing your proposal
> > > > > > I really don’t know how to describe it.
> > > > > >
> > > > > > [1]https://app.gitter.im/#/room/#monegrow_community:gitter.im
> > > > > >
> > > > > > On Wed, Sep 6, 2023 at 6:14 PM Zhiyong Zhang <goodj...@apache.org>
> > > > > wrote:
> > > > > > >
> > > > > > > Without Mone, OzHera can be used independently. Currently, in
> > addition
> > > > > to Xiaomi, there are also some external manufacturers using or
> > researching
> > > > > it. Mone is a larger collection within Xiaomi, and we are
> > considering open
> > > > > sourcing all of it in the future (which includes cicd rpc,
> > registration
> > > > > center, container management, stress testing system, API platform,
> > gateway,
> > > > > tunnel governance, etc.)
> > > > > > >
> > > > > > > On 2023/09/05 17:45:24 Xuanwo wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > Thanks for the interesting proposal first!
> > > > > > > >
> > > > > > > > I would like to understand the connection between Xiaomi/mone
> > and
> > > > > OzHera. Will OzHera be transferred from Xiaomi/mono to
> > > > > apache/incubator-ozhera while keeping the rest of the code
> > unchanged? Can
> > > > > OzHera be used independently without Xiaomi/mono?
> > > > > > > >
> > > > > > > > On Tue, Sep 5, 2023, at 11:11, Yu Xiao wrote:
> > > > > > > > > Dear incubator community,
> > > > > > > > >
> > > > > > > > > I would like to propose OzHera[1] as a new apache incubator
> > > > > project, you
> > > > > > > > > can find the proposal[2] of OzHera for more detail.
> > > > > > > > >
> > > > > > > > > OzHera is an application performance observation platform
> > that
> > > > > centers
> > > > > > > > > around applications,
> > > > > > > > > integrating metric monitoring, link tracing, logs, alerts,
> > and
> > > > > other
> > > > > > > > > capabilities.
> > > > > > > > > The Hera platform has the following core features:
> > > > > > > > >
> > > > > > > > > ** Embrace Cloud Native
> > > > > > > > > Complies with the Opentracing standard, integrating multiple
> > star
> > > > > > > > > open-source products such as OpenTelemetry,
> > > > > > > > > Grafana, Prometheus, ES, CAdvisor, etc. At the same time,
> > Hera
> > > > > deeply
> > > > > > > > > adapts to K8S,
> > > > > > > > > providing one-click deployment on K8S through operator.
> > > > > > > > >
> > > > > > > > > ** Precise: Availability Metrics
> > > > > > > > > We have defined corresponding availability metrics for
> > common RPC
> > > > > > > > > (Dubbo, HTTP, etc.) requests.
> > > > > > > > > These request-scope metrics are automatically extracted from
> > > > > tracing
> > > > > > > > > by Hera, and during extraction,
> > > > > > > > > we enhance the ability to recognize business error codes.
> > > > > > > > > A single metric can accurately express the exceptions
> > encapsulated
> > > > > by
> > > > > > > > > RPC and business processing.
> > > > > > > > >
> > > > > > > > > ** Quick: Metrics-Tracing-Logging Linkage
> > > > > > > > > Based on traceId, it links the alarm -> metrics -> link ->
> > log
> > > > > closed loop.
> > > > > > > > > From the moment the alarm card touches the user, the user can
> > > > > quickly
> > > > > > > > > view the link and log situation related to this alarm,
> > > > > > > > > greatly improving the efficiency of problem locating.
> > > > > > > > >
> > > > > > > > > ** Economical
> > > > > > > > > Less than 0.1% storage cost, satisfying 99.9% of tracing
> > demands
> > > > > > > > > OzHera achieves the recognition of abnormal calls (error
> > span,
> > > > > > > > > abnormal business error codes,
> > > > > > > > > error logs, single span time exceeding 1 second, etc.) and
> > ensures
> > > > > the
> > > > > > > > > storage of data for the entire call link of abnormal traces.
> > > > > > > > > For normal traces, we adopt a default random sampling
> > strategy of
> > > > > one
> > > > > > > > > in ten thousand.
> > > > > > > > >
> > > > > > > > > ** Enterprise-level Observable Products
> > > > > > > > > Complete account, permission, application management
> > mechanisms,
> > > > > > > > > allowing users to quickly implement within the enterprise and
> > > > > connect
> > > > > > > > > to the enterprise’s own account, application deployment
> > system,
> > > > > etc.
> > > > > > > > > It can also quickly dock with enterprise office software to
> > achieve
> > > > > > > > > alarm touch. Core links are well decoupled for rapid scaling,
> > > > > > > > > and for large volumes of tracing, we have implemented tail
> > > > > sampling strategies,
> > > > > > > > > able to support high qps, real-time observable demands of
> > high
> > > > > > > > > timeliness systems.
> > > > > > > > >
> > > > > > > > > [1] https://github.com/XiaoMi/mone/tree/master/ozhera-all
> > > > > > > > > [2]
> > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/OzHeraProposal
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Yu Xiao
> > > > > > > > >
> > > > > > > > > ASF Member
> > > > > > > > > Apache ShenYu V.P.
> > > > > > > > > Apache Incubator PMC
> > > > > > > > >
> > > > > > > > >
> > > > > ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > > > --
> > > > > > > > Xuanwo
> > > > > > > >
> > > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best wishes!
> > > > > > CalvinKirs
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to