This is a really interesting project that I have some experience on it and want 
to leave some comments.

## Put on my IPMC member hat

- About the community.

You said there are some external manufacturers using or researching it, I saw 
there are 3 in the GitHub readme, one of which is Xiaomi itself. And because 
the users are logged in the main page, I want to know which part of the repo do 
they use? Do they use the OzHera or do they use the other parts such as CI/CD 
in the repo? My further question is, if the OzHera is extracted from the repo, 
are the users still interested in using it or prefer to use the original repo 
since it has more components?

- About the contributors.

There are totally 12 contributors in the ozhera-all folder, which is also the 
target folder that you want to donate to incubator, half of them are employees 
of Xiaomi, the other half are unknown, maybe there are more from Xiaomi, is 
there really a community that is interested in the project if they are not 
hired to develop the project?


    17  oujinliang <oujinli...@gmail.com>                           Xiaomi, 
from the GitHub profile
    14  shanwb <shanwenb...@xiaomi.com>                             Xiaomi, 
from the commit author's email
    12  EricDing <128116675+sada...@users.noreply.github.com>
    10  shanwb <shanwenb...@sina.cn>
     6  gaoxihui <gaoxi...@xiaomi.com>                              Xiaomi, 
from the commit author's email
     7  wtt <1136220...@qq.com>
     3  张校炜 <zhangxiaow...@xiaomi.com>                            Xiaomi, from 
the commit author's email
     2  caobaoyu <caoba...@xiaomi.com>                              Xiaomi, 
from the commit author's email
     2  wodiwudi <40229449+wodiw...@users.noreply.github.com>
     1  Hobo <43409327+treasurej...@users.noreply.github.com>       Xiaomi, 
from the GitHub profile
     1  kongniancp <chenpeng_sm...@163.com>
     1  rikaaa0928 <w1zirn1...@gmail.com>

- About the initial committers.

As I said, there are 12 contributors in the target folder, but some of them are 
not in the 12 committers, can you elaborate why is the case? After all, I don't 
think a contributor who contributes to the other parts (say A) of the project, 
can be a initial committer of another part (say B), unless you can explain, 
what did they contribute to the project.

Overall, I feel like this project is in a very early stage where it haven't 
gain enough users or contributors to start a journey in ASF incubator.

## Put on my ex-Alibaba employee hat

The parent project of the proposed project, called Mone, is a copy of Alibaba 
Aone, especially the CI/CD subproject, the entire user interface is exactly the 
same as Alibaba's Flow product when I worked for Flow at Alibaba, although now 
the UI of Flow has changed a little bit, they look still resemble very much. I 
was shocked when I saw the screenshots and feel terrible for the plagiarism. I 
am in doubt whether the OzHera has similar issues and whether the project is 
properly audited by Xiaomi's legal team.

Just right when I'm composing this email, I saw the reply[1] from the team to 
my ex-colleague's doubt in copying their product, the team doesn't admit it's 
copy when the UI is exactly the same, now I don't think the team has a good 
understanding of branding or copyright, I'm pessimistic whether they can deal 
with the branding issues in ASF.

https://github.com/XiaoMi/mone/issues/689#issuecomment-1708439445

I'm really frustrated by the team and their attitude towards their violating 
copyright.

> On Sep 5, 2023, at 11:11, Yu Xiao <xia...@apache.org> 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
> 


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

Reply via email to