allow component lieutenant for component owner in doc

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1483128 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stack 2013-05-16 00:01:12 +00:00
parent e520b99455
commit 0a4f837096
1 changed files with 2 additions and 2 deletions

View File

@ -95,7 +95,7 @@ until the justification for the -1 is addressed.
<section xml:id="community.roles"> <section xml:id="community.roles">
<title>Community Roles</title> <title>Community Roles</title>
<section xml:id="OWNER"> <section xml:id="OWNER">
<title>Component Owner</title> <title>Component Owner/Lieutenant</title>
<para> <para>
Component owners are listed in the description field on this Apache HBase JIRA <link xlink:href="https://issues.apache.org/jira/browse/HBASE#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel">components</link> Component owners are listed in the description field on this Apache HBase JIRA <link xlink:href="https://issues.apache.org/jira/browse/HBASE#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel">components</link>
page. The owners are listed in the 'Description' field rather than in the 'Component page. The owners are listed in the 'Description' field rather than in the 'Component
@ -103,7 +103,7 @@ Lead' field because the latter only allows us list one individual
whereas it is encouraged that components have multiple owners. whereas it is encouraged that components have multiple owners.
</para> </para>
<para> <para>
Owners are volunteers who are (usually, but not necessarily) expert in Owners or component lieutenants are volunteers who are (usually, but not necessarily) expert in
their component domain and may have an agenda on how they think their their component domain and may have an agenda on how they think their
Apache HBase component should evolve. Apache HBase component should evolve.
</para> </para>