projectroles.php
来自「Software Testing Automation Framework (S」· PHP 代码 · 共 236 行
PHP
236 行
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head> <title>Software Testing Automation Framework (STAF)</title></head><body><?phprequire "top.php";require "navigate.php";?><!-- Insert text for page here --><tr><td><center><a name=top><h1>STAF Project Roles</h1></center><p><font face="arial, helvetica" color="#1e029a" size="4"><b>Overview</b></font><p>The STAF project is a collaborative software development project dedicatedto providing an open source, freely available, multi-platform,multi-language framework designed around the idea of reusable components,called services, that provides a testing automation framework with whichyou can build your automation solution. This document describes thecomposition of the project and the roles and responsibilities of the participants.</p><font face="arial, helvetica" color="#1e029a" size="4"><b>Roles in the STAF Project</b></font><p>There are various roles people play in the STAF project. The more youcontribute, and the higher the quality of your contribution, the moreresponsibility you can obtain.</p><h3>User</h3><p><em>Users</em> are the people who use STAF, without contributing code ordocumentation to the project. Users are encouraged to participate throughthe forums and mailing lists, asking questions, providing suggestions, andhelping other users. Users are also encouraged to report problems usingthe <a href="http://sourceforge.net/tracker/?group_id=33142&atid=407381">Bug tracking system</a> and request new features using the<a href="http://sourceforge.net/tracker/?group_id=33142&atid=407384">Request For Enhancement (RFE) tracking system</a>. Anyone can be a user.</p><h3>Contributor</h3><p>A user who contributes back to STAF becomes a <em>contributor</em>.Contributors are the people who <a href="contributions.php">contributeenhancements, bug fixes, documentation, or other work</a> that isincorporated into the system. A contributor does not have write accessto the source code repository. Anyone can be a contributor.</p><h3>Committer</h3><p>A contributor who gives frequent contributions can be promoted to a<em>committer</em>. Committers have write access to (a subset of) thesource code repository, and are developer members of the STAF SourceForgeproject. Committers should only commit code that they have writtenthemselves (not code obtained from other contributors). All majorcontributions from a committer should be reviewed by one or more coreteam members before potential inclusion into the CVS repository. Part ofthe processing of contributions by a committer includes conductingreasonable due diligence to satisfy themselves that proposed contributionscan be licensed under the terms of the CPL.</p><p>A contributor can become a committer by the following sequential process:<ol><li>They are nominated by an existing core team member,</li><li>At least 2 other core team members support their nomination, and</li><li>The STAF Steering Committee approves the nomination by majority vote</li></ol></p><p>Becoming a committer is a privilege that is earned by contributing andshowing good judgement. It is a responsibility that should be neithergiven nor taken lightly. Active participation on the forums and mailinglists is a responsibility of all committers, and is critical to thesuccess of the project. Committers are responsible for proactivelyreporting problems via the bug tracking system, and annotating problemreports with status information, explanations, clarifications, or requestsfor more information from the submitter.</p><p>At times, committers may go inactive for a variety of reasons.The project relies on committers who respond to discussions in aconstructive and timely manner. A committer that is disruptive, does notparticipate actively, or has been inactive for an extended period may havehis or her commit status removed by the STAF Steering Committee.</p><h3>Core Team Member</h3><P>A committer who gives frequent and valuable contributions can be promotedto a <em>core team member</em>. Core team members have write access tothe source code repository, and voting rights allowing them to affect thefuture of the project. The members of the core team are responsible forvirtually all of the day-to-day technical decisions associated with theproject. They are the gatekeepers, deciding what new code is added to thesystem. All contributions will be processed by one or more core teammembers before potential inclusion into the CVS repository. Part of theprocessing of contributions by a core team member includes conductingreasonable due diligence to satisfy themselves that proposed contributionscan be licensed under the terms of the CPL. The core team member(s) shalluse his/her reasonable judgement to determine if the contribution can becontributed under the STAF project licensing policy.</p><p>A committer can become a core team member by the following sequentialprocess:<ol> <li>They are nominated by an existing core team member,</li> <li>At least 2 other core team members support their nomination, and</li> <li>The STAF Steering Committee approves the nomination by majority vote</li></ol></p><p>Becoming a core team member is a privilege that is earned by contributingand showing good judgement. It is a responsibility that should be neithergiven nor taken lightly. Active participation on the forums and mailinglists is a responsibility of all core team members, and is critical to thesuccess of the project. Core team members are responsible for proactivelyreporting problems in the bug tracking system, and annotating problem reportswith status information, explanations, clarifications, or requests for moreinformation from the submitter. The core team also ensures that nightlybuilds are run on key supported platforms, performs regression testing beforereleasing a new version of STAF or one of its services, and opens defects totrack regression test failures. A subset of the core team does most of thismonitoring, however all core team members are expected to investigateregression test failures that might have been caused by a source code changethey committed.</p><p>At times, core team members may go inactive for a variety of reasons.The project relies on active core team members who respond to discussionsin a constructive and timely manner. A core team member that is disruptive,does not participate actively, or has been inactive for an extended periodmay have his or her commit status removed by the STAF Steering Committee.</p><h4>Current Core Team Members</h4>The STAF project currently contains three subprojects, each with its owncore team. Individuals are often members of more than one of the subprojects.Members of the STAF Steering Committee are members <em>ex officio</em> of allsubproject core teams. In the tables below, Steering Committee members areonly listed on projects where they actively participate as core team members.<h5>STAF Core Team</h5><table><tr><td><ul> <li><a href="mailto:dave2268@users.sourceforge.net">David Bender</a>, IBM Austin</li> <li><a href="mailto:joefh@users.sourceforge.net">Joef Huang</a>, IBM Toronto</li> <li><a href="mailto:slucas@users.sourceforge.net">Sharon Lucas</a>, IBM Austin</li> <li><a href="mailto:crankin_work@users.sourceforge.net">Charles Rankin</a>, IBM Austin</li></ul></td></table><h5>STAX Core Team</h5><table><tr><td><ul> <li><a href="mailto:dave2268@users.sourceforge.net">David Bender</a>, IBM Austin</li> <li><a href="mailto:slucas@users.sourceforge.net">Sharon Lucas</a>, IBM Austin</li> <li><a href="mailto:crankin_work@users.sourceforge.net">Charles Rankin</a>, IBM Austin</li></ul></td></table><h5>Services Core Team</h5><table><tr><td><UL> <li><a href="mailto:dave2268@users.sourceforge.net">David Bender</a>, IBM Austin</li> <li><a href="mailto:slucas@users.sourceforge.net">Sharon Lucas</a>, IBM Austin</li></ul></td></table><h3>Steering Committee</h3><p>The STAF Steering Committee (SC) is a small group that is responsiblefor the strategic direction and success of the project. This governingand advisory body is expected to ensure the project's welfare and guideits overall direction. The SC is also authorized to create newsubprojects, each with its own core team.</p><p>The initial STAF SC consisted of the founding core team members.Thereafter, to become a member of the SC, an individual must be nominatedby a member of the SC, and unanimously approved by all SC members.The goal is to keep the membership of the SC very small. In the unlikely event that a member of the SC becomes disruptive to theprocess or ceases to contribute for an extended period, the member may beremoved by unanimous vote of the remaining SC members.</p><h4>Current Steering Committee</h4><table><tr><td><ul> <li><a href="mailto:dave2268@users.sourceforge.net">David Bender</a>, IBM Austin</li> <li><a href="mailto:slucas@users.sourceforge.net">Sharon Lucas</a>, IBM Austin</li> <li><a href="mailto:crankin_work@users.sourceforge.net">Charles Rankin</a>, IBM Austin</li></ul></td></table></td></tr><!-- end of text for page --><?phprequire "bottom.php";?></body></html>⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?