The Apache Group $($AG$),$ the informal organization of people responsible for guiding the development of the Apache HTTP

Server Project, consisted entirely of volunteers, each having at least one other $$real$$ job that competed for their time. For

this reason, none of the developers could devote large blocks of time to the project in a consistent or planned manner,

therefore requiring a development and decision$-$making process that emphasized decentralized workspaces and

asynchronous communication. AG used email lists exclusively to communicate with each other, and a minimal quorum

voting system for resolving conflicts. The selection and roles of core developers are described in Fielding $[1999].$ AG

members are people who have contributed for an extended period of time, usually more than six months, and are

nominated for membership and then voted on by the existing members. AG started with $8$ members $($the founders$),$ had $12$

through most of the period covered, and now has $25.$ What we refer to as the set of $$core developers$$ is not identical to the

set of AG members$$ core developers at any point in time include the subset of AG that is active in development $($usually $4$

to $6$ in any given week$)$ and the developers who are on the cusp of being nominated to AG membership $($usually $2$ to $3).$

Each AG member can vote on the inclusion of any code change and has commit access to CVS $($if he or she desires it$).$

Each AG member is expected to use his or her judgment about committing code to the base, but there is no rule prohibiting

any AG member from committing code to any part of the server. Votes are generally reserved for major changes that would

affect other developers who are adding or changing functionality. Although there is no single development process, each

Apache core developer iterates through a common series of actions while working on the software source. These actions

include discovering that a problem exists, or new functionality is needed, determining whether a volunteer will work on the

issue, identifying a solution, developing and testing the code within their local copy of the source, presenting the code

changes to the AG for review, and committing the code and documentation to the repository. Depending on the scope of the

change, this process may involve many iterations before reaching a conclusion, although it is generally preferred that the

entire set of changes needed to solve a particular problem or add a particular enhancement be applied in a single commit.

Question $3(10$ Marks$)$

Votes are generally reserved for major changes that would affect other developers who are adding or changing functionality.

Apply the five $(5)$ agile process approaches in principle of software engineering in relation to the Apache Group that can

enhance the operational processes.