[g-a-devel]Build sheriff permission ...
- From: Michael Meeks <michael ximian com>
- To: BAUM-dev <BAUM-dev basso SFBay Sun COM>, Padraig O'Briain <Padraig Obriain sun com>, Erwann Chenede <erwann chenede sun com>, Bill Haneman <bill haneman sun com>, David Bolter <david bolter utoronto ca>
- Cc: accessibility mailing list <gnome-accessibility-devel gnome org>
- Subject: [g-a-devel]Build sheriff permission ...
- Date: 09 Aug 2002 10:25:31 +0100
Hi you guys,
If you're reading this, you own a module that is not playing ball well
[ probably by accident ] with the rest of the project. To be fair I just
fixed 'at-poke' as well. It seems word of this sort of thing hasn't
spread to the a11y community.
Anyhow; to facilitate a wider adoption of A11y code - and to enable it
to be snapshotted easily, it is really important to add the following
lines to a 'HACKING' file in your cvs module:
" Build sheriff commits are welcome - in accordance with the
relevant build sheriff constraints. "
That is - if you agree with the guidelines, which are these:
http://mail.gnome.org/archives/gnome-hackers-readonly/2002-March/msg00051.html
[ They should be on developer.gnome.org too, but it seems some
mis-management somewhere made that not happen. ]
It'd be really great to see this in:
gail, at-spi, gok, gnopernocis, gnome-mag
As at the time of inititation of this process, there is still only 1
build sheriff who is Jacob Berkman, a man of taste, discretion etc. who
knows more of autotools than the average maintainer will ever know :-)
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]