This is an automated email from the ASF dual-hosted git repository.
shaofengshi pushed a commit to branch document
in repository https://gitbox.apache.org/repos/asf/kylin.git
The following commit(s) were added to refs/heads/document by this push:
new 700c285 update on how to contribute
700c285 is described below
commit 700c2854110d5f0be0a93bc4f9ad1083d8f88aa6
Author: shaofengshi <shaofeng...@apache.org>
AuthorDate: Fri Feb 16 10:42:56 2018 +0800
update on how to contribute
---
website/_dev/howto_contribute.md | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/website/_dev/howto_contribute.md b/website/_dev/howto_contribute.md
index 737f8b9..4eb7a9a 100644
--- a/website/_dev/howto_contribute.md
+++ b/website/_dev/howto_contribute.md
@@ -16,22 +16,24 @@ Both code and document are under Git source control. Note
the purpose of differe
* `document`: Document branch
## Components and owners
-Apache Kylin has several sub-components. And for each component we will
arrange one or multiple component owners.
+Apache Kylin has several sub-components. To better help the community's
growth, we arrange one or multiple component owners for each component.
-Component owners is listed in the description field on this Apache Kylin [JIRA
components
page](https://issues.apache.org/jira/projects/KYLIN?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page).
The owners are listed in the 'Description' field rather than in the 'Component
Lead' field because the latter only allows us to list one individual whereas it
is encouraged that components have multiple owners.
-
-- Component owners are volunteers who are expert in their component domain and
may have an agenda on how they think their Apache Kylin component should
evolve. The owner needs to be an Apache Kylin committer at this moment.
+- Component owners are volunteers who are expert in their component domain.
The owner needs to be an Apache Kylin committer or PMC at this moment.
- Owners will try and review patches that land within their component’s scope.
-- Owners can rotate, based on his aspiration.
+- Owners can rotate, based on his aspiration and community need.
- When nominate or vote a new committer, the nominator needs to state which
component the candidate can be the owner.
-- If you're already an Apache Kylin committer and would like to be a volunteer
as a component owner, just write to the dev list and we’ll sign you up.
+- If you're already an Apache Kylin committer or PMC memeber and would like to
be a volunteer as a component owner, just write to the dev list and we’ll sign
you up.
+
+- All the project plan, decisions are still managed by Apache Kylin PMC.
- If you think the component list need be updated (add, remove, rename, etc),
write to the dev list and we’ll review that.
+Component owners is listed in the description field on this Apache Kylin [JIRA
components
page](https://issues.apache.org/jira/projects/KYLIN?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page).
The owners are listed in the 'Description' field rather than in the 'Component
Lead' field because the latter only allows us to list one individual whereas it
is encouraged that components have multiple owners.
+
## Pick a task
There are open tasks waiting to be done, tracked by JIRA. To make it easier to
search, there are a few JIRA filters.
--
To stop receiving notification emails like this one, please contact
shaofeng...@apache.org.
