Summary from yesterdays (mini) FESCo meeting

[Jeff Spaleta]

On 12/29/06, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> It would be nice if such a template was officially embeded into the
> review process docs and was maintained to always reflect the latest
> review/guidelines requirements.

As a reviewer and a packager, I'm always concerned that the liste of
items I need to check as a matter of policy will shift under my feet.
The packaging policy does evolve, and will continue to evolve, and I
do my best to adhere to the stated guidance. If I'm not reading over
the guidelines as I do any reviews, I'm garunteed to miss a policy
change.  Boiling down requirements into a template, especially a
template that could highlight in some way 'newness' of specific policy
items would help notify me of policy shifts over time.  I can't
reasonably assume that the guidelines I remember from 3 months ago are
completely appropriate now.  If we had an embedded template that was
sorted such with 'newness' of individual policy items could be quickly
guaged it would help my efficiency immensely because I could
concentrate my time on re-reading the guidance of the specific policy
items which have been updated recently. Right now I spend too much
time reading over all the guidance looking for changes everytime I do
a review.

For example if .desktop policy changes again next month, a template
could put the desktop related check item at the end of the list,
perhaps with a effective-as-of date. This would tell me as a reviewer
that I need to go back and make a detailed reading of the desktop
policy in the guidelines because it's changed since the last time I
ran a review or submitted a package.

-jef