Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 17397 invoked by uid 500); 1 May 2001 04:12:39 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 17385 invoked from network); 1 May 2001 04:12:37 -0000 Received: from unknown (HELO platinum.allaire.com) (63.109.196.16) by h31.sny.collab.net with SMTP; 1 May 2001 04:12:37 -0000 Received: from gamebox (namaste.ne.mediaone.net [24.218.162.35]) by platinum.allaire.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 15HCD4C0; Tue, 1 May 2001 00:12:46 -0400 Message-ID: <012b01c0d1f4$f1a19da0$0b00a8c0@gamebox> From: "Glen Daniels" To: References: Subject: Re: The current messaging code Date: Tue, 1 May 2001 00:12:31 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > I'm going to -1 "ignoring zip files" as I think having somewhat of a > > consensus on proposed major changes is best to get before actually making > > those changes to the primary code base. Especially when there are others > > in the group who are actively using/modifying the code while the major > > changes are being proposed. > > What concerns me most is that it appears that every member of this "team" > has been working on their very own virtual branch for quite a while, and in > general is unable or unwilling to play well with others. Sam is right. Long-term branching is a bad idea, and in general an absolutely key factor for this team is to start acting like one. We're not doing a great job of communicating about designs, changes, areas of responsibility that we're each interested in, and what we're working on. We need to get better at this if we hope to come out with a solid product! We've got a bunch of smart people working in kind of a haphazard way at the moment, and what we need is for those same people to be parts of a functional whole working with a shared vision towards a common goal. James is also right. Sometimes code is the best way to communicate ideas which may not yet have buy-in by the group, and as such I also support posting ideas this way (which is why James and I both posted .zips last week). Especially for changes that affect the way major chunks of the codebase work. Yes, you can go too far working out of the main line, but I think I'd rather see occasional .zips posted than frequent checkins which get -1'ed. In any case, I hope everyone is at the IRC chat tomorrow, as it seems like we have a lot of good discussion fodder. :) --Glen