** Due to some issues project had to be renamed to Gach and
   correspondingly all services around it have been updated with
   latest changes by fedora infrastructure.

Gach: doing the grunt work

Fedora is known for setting high standards in RPM packaging. With a
repository that is growing each day, and our emphasis on working
upstream we have a collection of packages that makes us proud, our
derived distributors happy and our competitors envious. However to
maintain high standards we need to make sure that package review
requests get the necessary time and attention to meet the large queue
of new submissions.

Gach is an effort to take away the grunt work from the review process
and make it easier for both the reviewer and the submitter to get an
initial idea about the quality of their packages by taking a Spec/SRPM
pair and running it through Gach and getting a report.

It will be possible to do periodic audits of the entire tree and it
will be also be possible to go beyond detecting build failures and
uncover a whole bunch of other violations as well. This might be
lucrative to third parties, having a stake in the quality of the
distribution (eg., derived distributors like CentOS, academic or
enterprise users, etc.), to carry out regular quality analysis on our
repositories. Currently it is difficult, albeit possible, to do this
using a mix of RPMLint, Mock and some ad-hoc scripts. Since Gach ties
together these utilities, and adds a few customized Fedora specific
checks written by the Fedora developers themselves, one can rest
assured that the generated reports are in accordance with the latest
guidelines approved by the Fedora Packaging Committee.

Regarding the design it takes a Spec or source RPM or even RPM through
its feeder and does a review and posts its report via its reporter
interface. Feeder will have different interfaces to get input from
Bugzilla or any generic URI. Similarly, reports can be provided as
Bugzilla comments or as a local file. Our process also includes(very
much obviously) running rpmlint on input files. We plan to push all
guidelines checks to upstream rpmlint. But there are some hybrid
checks which are fedora specific require input from logs generated via
builders or multiple file inspection and are very much out of scope of
rpmlint will need to be kept in Gach. (Check table) is were inspecting
each checks one by one and decide on which are programmable and which
are not, takes place. Plan is to speed up automating guidelines once
structural architecture get working with very basic capabilities and
later on concentrate on automating guidelines. We plan to keep checks
categorized to distributions and keeping all FHS, Single Specification
etc guidelines separate so that in future this feature can be ported
to other rpm based distributions e.g smolt has been ported to all
major distributions.

My talk will explain the usability, and wonderful design of this
infrastructure feature which we are proposing for fedora 11. And how
it integrates with already existing fedora services, making them more
efficient together.

Few useful links:
   * Home Page https://fedorahosted.org/gach/wiki
   * Browse Source Code https://fedorahosted.org/gach/browser
   * Mailing List https://fedorahosted.org/mailman/listinfo/gach
   * Structural Design https://fedorahosted.org/gach/wiki/arch_image


Introduction
=============

Rakesh Pandit

Fedora Package Maintainer
Maintain 45+ packages[1]
Gach Developer[2]
Bug triage and infrastructure bits.

OpenOffice Domain Developer[3]
Working on starmath module

Inetutils GNU Project Developer[4]
Working on ping/ping6 module

Blog: http://rakesh.gnulinuxcentar.org/
Email: rakesh DOT fedoraproject DOT org,
     rakeshpandit AT openoffice DOT org

Mobile Number: +91-90960338664

[1] https://admin.fedoraproject.org/pkgdb/users/packages/rakesh
[2] http://fedorahosted.org/gach
[3] http://wiki.services.openoffice.org/wiki/DomainDeveloper
[4] http://savannah.gnu.org/project/memberlist.php?group=inetutils

--
Rakesh Pandit