nickchalko 2004/03/16 12:53:11 Added: blog/BoardReports 20040317.txt Log: March Board Report.
PR: Obtained from: Submitted by: Reviewed by: CVS: ---------------------------------------------------------------------- CVS: PR: CVS: If this change addresses a PR in the problem report tracking CVS: database, then enter the PR number(s) here. CVS: Obtained from: CVS: If this change has been taken from another system, such as NCSA, CVS: then name the system in this line, otherwise delete it. CVS: Submitted by: CVS: If this code has been contributed to Apache by someone else; i.e., CVS: they sent us a patch or a new module, then include their name/email CVS: address here. If this is your work then delete this line. CVS: Reviewed by: CVS: If we are doing pre-commit code reviews and someone else has CVS: reviewed your changes, include their name(s) here. CVS: If you have not had it reviewed then delete this line. Revision Changes Path 1.1 gump/blog/BoardReports/20040317.txt Index: 20040317.txt =================================================================== PREVIEW March 2004 report to the ASF Board Preview at http://gump.chalko.com/gb/blog/BoardReports/?preview=true&smm=y&permalink=20040317.txt <hr/> <!-- Copyright 2004 The Apache Software Foundation Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <p> Most of the past few weeks has been filled with infrastructure stuff. </p><p> We've successfully migrated web-site, CVS module, bug-tracking and the mailing list to gump.apache.org - many thanks to the infrastructure team for making the transition that smooth. </p><p> All Apache committers have been Gump committers with the old setup and this still remains true. We want to get as many people involved as possible when it gets to maintaining the project metadata. This is the reason that we've been sticking to CVS for now since we can reach most Apache committers that way. Gump will probably be one of the last projects that make the transition to Subversion. </p><p> Work on the project bylaws has started and we expect to have them ready for the next board meeting. Gump is unique when it comes to committer status so we'll have to put some thoughts into the definition of that role. </p><p> Gump has been quite successful in pointing out problems in some builds recently and we are happy that most of them have been resolved between projects easily. Our biggest problem right now is building Avalon, but this may be due to the fact that Gump is using a different build system than Avalon more than anything else. Once Gump supports Maven as a build option, things may become easier for Avalon. </p><p> We continue improving the Python rewrite of Gump and have come quite a long way already. Since nobody of us is anywhere near a Python guru, we may be doing things far more complicated than necessary. Any help is welcome. 8-) </p><p> The short-to-mid-term future steps for Gump are : <ul> <li>get dedicated ASF hardware to run Gump on - <i>currently working on getting it running on Moof but we are really looking forward to the new gump-dedicated machine</i>. </li> <li>expand Gump's reach beyond building Java projects. </li> <li>improve the way Gump works by trying to find an computationally feasible way to nagging the offender and not the offended, improve the usability/effectiveness of gump reports, find ways to increase adoption by making social pressure of nagging more effective and ease the effort required for users to update their project descriptors. </li> <li>start thinking on how to provide feedback for legal dependencies checkings </ul> </p> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
