zhongjiajie commented on a change in pull request #886:
URL: 
https://github.com/apache/incubator-seatunnel/pull/886#discussion_r776153469



##########
File path: .asf.yaml
##########
@@ -0,0 +1,41 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+github:
+  description: SeaTunnel is a distributed, high-performance data integration 
platform for the synchronization and transformation of massive data (offline & 
real-time).
+  homepage: https://seatunnel.apache.org/
+  labels:
+    - data-integration
+    - high-performance
+    - offline&real-time

Review comment:
       > Depending on how you understand it, I prefer one. Because we provide 
it at the same time.
   
   IMO, labels have two functions, tell user/dev what is our focus on, the 
other is for search engines. And I prefer to separate them is for the search 
engine side, cause one or two words is both clearly for user/dev.
   
   I am not sure we could hint in github/google in use one word, with the 
search `real time data integration` or some thing like that




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to