[g-a-devel]Patch to 'HACKING' file in at-spi



Hi:

Inline is the diff for a patch to at-spi's HACKING file.  The only
significant change to policy is this: we are going to explicitly request
that maintainer patches of significant content (i.e. my patches and
Marc's) are posted to this list for comment prior to commit, preferably
for a minimum of 24 hours.  We hope that this will improve code quality,
stimulate discussion, and prevent breakage due to misunderstanding.

Best regards,

Bill

-----------


========= begin included diff =======

Index: HACKING
===================================================================
RCS file: /cvs/gnome/at-spi/HACKING,v
retrieving revision 1.1
diff -u -r1.1 HACKING
--- HACKING	11 Mar 2002 22:00:09 -0000	1.1
+++ HACKING	19 Aug 2002 11:22:07 -0000
@@ -1,22 +1,23 @@
 Contributing to AT-SPI:
 
-Bill Haneman (bill haneman sun com)
-
 AT-SPI is a complex package, with lots of dependencies.  We
 (maintainers) are not experts in every area; we welcome contributions
 and corrections.  However we do ask that all changes to AT-SPI go
 through the normal patch approval process (i.e. diff -u).
 Please post patches to gnome-accessibility-devel gnome org; if in 
-doubt you may wish to email maintainers ahead of time.
+doubt you may wish to email questions ahead of time. 
 
-The current maintainers are myself and Marc Mulcahy 
-(marc mulcahy sun com). 
+The current maintainers are Bill Haneman (bill haneman sun com) 
+and Marc Mulcahy (marc mulcahy sun com).  As a general rule,
+Non-trivial maintainer-submitted patches should be posted to 
+gnome-accessibility-devel for comment and informational purposes 
+prior to commit.
 
 "Build Sheriff" patches are welcome and are exempt from the
 normal approval process, provided:
 
-(a) it can be confirmed that the Solaris build does not regress,
-as many of our users are based on Solaris and SPARC;
+(a) care is taken that the Solaris build does not regress,
+as at-spi is a cross-platform package;
 (b) the build patches are, generally speaking, not controversial.
 
 At any rate we appreciate being told where we've screwed up, so

=============





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]