You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@inlong.apache.org by do...@apache.org on 2022/06/22 10:10:57 UTC
[inlong-website] branch master updated: [INLONG-443][Website] Remove the NEWS tab on the official website (#444)
This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
The following commit(s) were added to refs/heads/master by this push:
new c02aaed62 [INLONG-443][Website] Remove the NEWS tab on the official website (#444)
c02aaed62 is described below
commit c02aaed6236b2700f8758f505c8772972d46f1a0
Author: healzhou <he...@gmail.com>
AuthorDate: Wed Jun 22 18:10:53 2022 +0800
[INLONG-443][Website] Remove the NEWS tab on the official website (#444)
---
docusaurus.config.js | 13 ----
.../2021-11-26-new-committer-join.md | 88 ----------------------
i18n/zh-CN/docusaurus-theme-classic/navbar.json | 4 -
news/2021-11-26-new-committer-join.md | 86 ---------------------
package.json | 1 -
5 files changed, 192 deletions(-)
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 9d4bc8e51..bfc88b463 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -124,11 +124,6 @@ const darkCodeTheme = require('prism-react-renderer/themes/dracula');
label: 'BLOG',
position: 'right'
},
- {
- to: '/news',
- label: 'NEWS',
- position: 'right'
- },
{
to: '/team',
label: 'TEAM',
@@ -295,13 +290,5 @@ const darkCodeTheme = require('prism-react-renderer/themes/dracula');
},
},
],
- [
- '@docusaurus/plugin-content-blog',
- {
- id: 'news',
- routeBasePath: 'news',
- path: 'news',
- },
- ],
]
});
diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog-news/2021-11-26-new-committer-join.md b/i18n/zh-CN/docusaurus-plugin-content-blog-news/2021-11-26-new-committer-join.md
deleted file mode 100644
index aff1b9b19..000000000
--- a/i18n/zh-CN/docusaurus-plugin-content-blog-news/2021-11-26-new-committer-join.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Apache InLong 迎接新 Committer 成员
----
-
-InLong(应龙) : 中国神话故事里的神兽，引流入海，借喻 InLong 系统提供数据接入能力。
-
-### Apache InLong(incubating) 简介
-
-[Apache InLong（应龙）](https://inlong.apache.org)是腾讯捐献给 Apache 社区的一站式海量数据集成框架，提供自动、安全、可靠和高性能的数据传输能力，方便业务构建基于流式的数据分析、建模和应用。
-
-InLong 项目原名 TubeMQ ，专注于高性能、低成本的消息队列服务。为了进一步释放 TubeMQ 周边的生态能力，我们将项目升级为 InLong，专注打造一站式海量数据集成框架。
-
-Apache InLong 以腾讯内部使用的 TDBank 为原型，依托万亿级别的数据接入和处理能力，整合了数据采集、汇聚、存储、分拣数据处理全流程，拥有简单易用、灵活扩展、稳定可靠等特性。
-<img src="/img/inlong-structure-zh.png" align="center" alt="Apache InLong"/>
-
-
-Apache InLong 服务于数据采集到落地的整个生命周期，按数据的不同阶段提供不同的处理模块，主要包括：
-
-- **inlong-agent**，数据采集 Agent，支持从指定目录或文件读取常规日志、逐条上报。后续也将扩展 DB 采集、HTTP 上报等能力。
-- **inlong-dataproxy**，一个基于 Flume-ng 的 Proxy 组件，支持数据发送阻塞和落盘重发，拥有将接收到的数据转发到不同 MQ（消息队列）的能力。
-- **inlong-tubemq**，腾讯自研的消息队列服务，专注于大数据场景下海量数据的高性能存储和传输，在海量实践和低成本方面有着良好的核心优势。
-- **inlong-sort**，对从不同的 MQ 消费到的数据进行 ETL 处理，然后汇聚并写入 Hive、ClickHouse、Hbase、Iceberg 等存储系统。
-- **inlong-manager**，提供完整的数据服务管控能力，包括元数据、任务流、权限，OpenAPI 等。
-- **inlong-website**，用于管理数据接入的前端页面，简化整个 InLong 管控平台的使用。
-
-### Apache InLong 社区迎来两位新 Committer
-
-在美好的11月份，周康(@healchow)、卢子杰(@TszKitLo40) 两位贡献者成功入选 Apache InLong Committer，祝贺他们！
-周康和卢子杰很早就是 Apache InLong 的贡献者，他们正在参与 InLong 0.12.0 版本的特性开发，欢迎大家在即将发布的 InLong 0.12.0 中围观他们的贡献。
-
-### 新 Committer 寄语
-
-#### 周康(@healchow)
-
-感谢 InLong 社区对我的认可，能成为 InLong 的一名 Committer，我备感荣幸，深感责任重大。
-在开源社区，来自天南海北世界各地的技术人可以一起交流碰撞，在开阔技术视野的同时，还能提升编码和协作能力，这对开发者个人来说是很好的锻炼机会。
-在为 InLong 做出贡献的同时，我对 InLong 的架构和底层技术有了更深的理解，希望能持续参与到 InLong 的开源过程中，创造更强大的 InLong。
-
-#### 卢子杰(@TszKitLo40)
-
-很高兴可以成为 Apache InLong 项目的一名 Committer ，非常感谢 InLong 社区对我的疑问给出的帮助，同时也非常感谢 InLong 社区对我的贡献的认可。
-在参与 Apache InLong 项目的开发中，我觉得是 Apache InLong 是一个正在快速成长的项目，期待越来越多的人可以参与到社区的建设中！
-
-### 新 Committer 贡献事迹
-
-#### 周康(@healchow)
-
-贡献了 InLong-Manager 的大部分功能，包括数据接入、数据源、数据存储等信息的配置，创建关联模块的资源（如 TubeMQ 的 Topic 和消费组，推送 Sort 模块需要的配置……）等等。
-InLong-Manager 是 InLong 项目的管理者，它串联起了其他的底层模块，还有很多 Feature 亟待开发，迫切地欢迎热爱开源的伙伴们来一起协作共建！
-
-#### 卢子杰(@TszKitLo40)
-
-贡献了 InLong-TubeMQ 的纯 Go SDK。Go 语言在国内越来越流行，越来越多的用户有使用 Go SDK 的需求。
-Go SDK 在 API 上保持了和 Java/C++ 版本的一致性，在业务层处理逻辑也和 Java/C++ 版本基本一致，其他语言 SDK 的使用者也可以快速上手。
-目前 Go SDK 只实现了消费功能，期待更多贡献者能一起参与生产功能的开发。
-
-### 给未来 Committer 的建议
-
-#### 周康(@healchow)
-
-加入开源，千万不要有畏惧心理。你可以先查看“如何参与贡献(https://inlong.apache.org/zh-CN/development/how-to-contribute)”， 然后 fork 代码仓库，编译、运行某个感兴趣的功能模块……
-过程中遇到问题了？恭喜你，这有可能是个 bug，也有可能是文档不完善，你可以加交流群提问，然后到这里提 Issue (https://github.com/apache/incubator-inlong/issues/new/choose)……
-到这里，你已经是 InLong 的 Contributor 了。加油，下一步就是 Committer :-)
-
-#### 卢子杰(@TszKitLo40)
-
-InLong 项目目前还处于孵化阶段，还有很多可以完善的地方，比如 Go SDK 的生产功能。开源项目刚开始上手可能比较困难，我的经验是可以先从简单的 Issue 开始，慢慢获取成就感。
-同时如果有问题可以及时和社区的小伙伴沟通，社区氛围是很nice的，大家都很愿意帮助新的伙伴。如果觉得贡献代码比较难，也可以先从贡献文档开始，期待更多的小伙伴加入 InLong 社区，一起前进。
-
-### Apache InLong(incubating) 贡献者招募
-
-Apache InLong(incubating) 当前共有 63 名 contributor，仍处在项目孵化的初期，还有很多待办事项，包括：Feature 开发、社区运营，文档翻译等，期待更多开源爱好者加入 InLong，一起将 InLong 打造成 Apache 顶级项目。
-
-以下为 InLong 项目的时间线：
-
-- 2021年11月5日，发布 0.11.0 版本
-- 2021年9月3日，发布 0.10.0 版本
-- 2021年7月12日，发起更名后第一个版本 0.9.0 投票
-- 2021年4月11日，完成社区改名，改为 Apache InLong
-- 2021年2月11日，发起社区改名变更申请
-- 2020年12月20日，进行项目改名讨论和投票
-- 2020年5月30日，按照 Apache 社区规范发布第一个社区版本
-- 2019年11月3日，进入 Apache 社区孵化
-- 2019年9月12日，TubeMQ 对外开源并捐献给 Apache 社区
-
-Apache InLong 项目官方网站：https://inlong.apache.org
-
-Apache InLong GitHub 地址 ：https://github.com/apache/incubator-inlong
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-theme-classic/navbar.json b/i18n/zh-CN/docusaurus-theme-classic/navbar.json
index 67b9fe2eb..10769df0e 100644
--- a/i18n/zh-CN/docusaurus-theme-classic/navbar.json
+++ b/i18n/zh-CN/docusaurus-theme-classic/navbar.json
@@ -23,10 +23,6 @@
"message": "博客",
"description": "Navbar item with label BLOG"
},
- "item.label.NEWS": {
- "message": "新闻",
- "description": "Navbar item with label NEWS"
- },
"item.label.TEAM": {
"message": "团队",
"description": "Navbar item with label TEAM"
diff --git a/news/2021-11-26-new-committer-join.md b/news/2021-11-26-new-committer-join.md
deleted file mode 100644
index 2a6a37dca..000000000
--- a/news/2021-11-26-new-committer-join.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Apache InLong welcomes new Committers
----
-
-InLong (应龙) is a divine beast in Chinese mythology who guides river into the sea, it is regarded as a metaphor of the InLong system for reporting streams of data.
-
-### Apache InLong(incubating) Introduction
-
-[Apache InLong](https://inlong.apache.org) is a one-stop integration framework for massive data donated by Tencent to the Apache community. It provides automatic, safe, reliable, and high-performance data transmission capabilities to facilitate the construction of streaming-based data analysis, modeling, and applications.
-The Apache InLong project was originally called TubeMQ, focusing on high-performance, low-cost message queuing services. In order to further release the surrounding ecological capabilities of TubeMQ, we upgraded the project to InLong, focusing on creating a one-stop integration framework for massive data.
-
-Apache InLong uses TDBank internally used by Tencent as the prototype, and relies on trillion-level data access and processing capabilities to integrate the entire process of data collection, aggregation, storage, and sorting data processing. It is simple to use, flexible to expand, stable and reliable characteristic.
-<img src="/img/inlong-structure-en.png" align="center" alt="Apache InLong"/>
-
-Apache InLong serves the entire life cycle from data collection to landing, and provides different processing modules according to different stages of data, including the next modules:
-
-- **inlong-agent**, data collection agent, supports reading regular logs from specified directories or files and reporting data one by one. In the future, DB collection and HTTP reporting capabilities will also be expanded.
-- **inlong-dataproxy**, a Proxy component based on Flume-ng, supports data transmission blocking, placing retransmission, and has the ability to forward received data to different MQ (message queues).
-- **inlong-tubemq**, Tencent's self-developed message queuing service, focuses on high-performance storage and transmission of massive data in big data scenarios and has a relatively good core advantage in mass practice and low cost.
-- **inlong-sort**, after consuming data from different MQ services, perform ETL processing, and then aggregate and write the data into Apache Hive, ClickHouse, Hbase, IceBerg, etc.
-- **inlong-manager**, provides complete data service management and control capabilities, including metadata, OpenAPI, task flow, authority, etc.
-- **inlong-website**, a front-end page for managing data access, simplifying the use of the entire InLong control platform.
-
-### The Apache InLong community welcomes two new Committers
-
-In a beautiful November , two contributors, Zhou Kang (@healchow) and Lu Zijie (@TszKitLo40), were successfully selected as the Apache InLong Committer. Congratulations!
-Zhou Kang and Lu Zijie were early contributors to Apache InLong. They are participating in the feature development of InLong 0.12.0. Welcome everyone to watch their contributions in the upcoming InLong 0.12.0.
-
-### What the new committer said
-
-#### Zhou Kang (@healchow)
-
-Thanks to the InLong community for recognizing me, I am honored to be a Committer of InLong, and I deeply feel the responsibility.
-In the open-source community, people from all over the world can communicate and collide together. While broadening their technical horizons, they can also improve coding and collaboration capabilities. This is a good opportunity for developers to exercise.
-While contributing to InLong, I have a deeper understanding of InLong's architecture and underlying technology, and I hope to continue to participate in InLong's open-source process to create a more powerful InLong.
-
-#### Lu Zijie (@TszKitLo40)
-
-I am very happy to be a Committer of the Apache InLong project. I am very grateful to the InLong community for their help with my questions. At the same time, I am very grateful to the InLong community for their recognition of my contribution.
-In participating in the development of the Apache InLong project, I think that Apache InLong is a rapidly growing project, and I hope that more and more people can participate in the construction of the community!
-
-### New Committer Contributions
-
-#### Zhou Kang (@healchow)
-
-Contributed to most of the functions of InLong-Manager, including the configuration of data access, data source, data storage, and other information, resources for creating associated modules (such as TubeMQ Topic and consumer groups, pushing the configuration required for the Sort module...), etc.
-InLong-Manager is the manager of the InLong project. It connects other low-level modules in series, and there are many features that need to be developed urgently. Partners who love open source are eagerly welcome to collaborate and build together!
-
-#### Lu Zijie (@TszKitLo40)
-
-Contributed the Go SDK of InLong-TubeMQ entirely. The Go language is becoming more and more popular in China, and more and more users need to use the Go SDK.
-The Go SDK maintains the API consistency with the Java/C++ version, and the business layer processing logic is the same as the Java/C++ version. Users of other language SDKs can also quickly get started.
-At present, the Go SDK only implements the consumption function, and it is expected that more contributors can participate in the development of the production function together.
-
-### Suggestions for future Committer
-
-#### Zhou Kang (@healchow)
-
-Don't be afraid to join open source. You can check "How to participate in contribution (https://inlong.apache.org/zh-CN/development/how-to-contribute)," then fork the code repository, compile and run a functional module.
-Have you encountered a problem during the process? Congratulations, this may be a bug, or it may be due to insufficient documentation. You can add a communication group to ask questions and then go to issue (https://github.com/apache/incubator-inlong/issues/new/choose).
-At this point, you are already a Contributor to InLong. Come on, and the next step is Committer :-)
-
-#### Lu Zijie (@TszKitLo40)
-
-The InLong project is still in the incubation stage, and there are still many areas that can be improved, such as the production function of the Go SDK. It may be challenging to get started with open-source projects. My experience is that you can start with simple Issues and slowly gain a sense of accomplishment.
-At the same time, if you have any questions, you can communicate with friends in the community in time. The community atmosphere is very nice, and everyone is willing to help new partners. If you find it more difficult to contribute code, you can start with contributing documents and expect more friends to join the InLong community and move forward.
-
-### Apache InLong(incubating) contributor recruitment
-
-Apache InLong (incubating) currently has 64 contributors, and it is still in the early stages of project incubation. There are still many to-dos, including Feature development, community operation, document translation, etc. We look forward to more open source enthusiasts joining InLong and bringing InLong together. Become a top-level Apache project.
-
-The following is the timeline of the InLong project:
-
-- November 5, 2021, release 0.11.0 version
-- September 3, 2021, release 0.10.0 version
-- July 12, 2021, the first version after the name change was initiated 0.9.0 vote
-- On April 11, 2021, complete the community name change and change to Apache InLong
-- On February 11, 2021, initiate a community name change application
-- On December 20, 2020, discuss and vote on the project name change
-- On May 30, 2020, the first community version was released in accordance with the Apache community specifications
-- On November 3, 2019, enter the Apache community incubation
-- On September 12, 2019, TubeMQ was open sourced and donated to the Apache community
-
-Apache InLong Project official website ：https://inlong.apache.org
-
-Apache InLong GitHub address ：https://github.com/apache/incubator-inlong
\ No newline at end of file
diff --git a/package.json b/package.json
index d5e5027c0..264cf5255 100644
--- a/package.json
+++ b/package.json
@@ -16,7 +16,6 @@
},
"dependencies": {
"@docusaurus/core": "^2.0.0-beta.21",
- "@docusaurus/plugin-content-blog": "^2.0.0-beta.21",
"@docusaurus/plugin-content-docs": "^2.0.0-beta.21",
"@docusaurus/preset-classic": "2.0.0-beta.21",
"@mdx-js/react": "^1.6.21",