From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19508 invoked by alias); 23 Jul 2008 20:04:33 -0000 Received: (qmail 19501 invoked by uid 22791); 23 Jul 2008 20:04:32 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_05,KAM_MX,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Jul 2008 20:04:14 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6NK4CDm005307 for ; Wed, 23 Jul 2008 16:04:12 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6NK4CUI021230; Wed, 23 Jul 2008 16:04:12 -0400 Received: from opsy.redhat.com (vpn-10-51.bos.redhat.com [10.16.10.51]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6NK4B4h026722; Wed, 23 Jul 2008 16:04:11 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 3EF5C378245; Wed, 23 Jul 2008 14:04:05 -0600 (MDT) To: Frysk List Subject: Re: meeting References: From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Wed, 23 Jul 2008 20:04:00 -0000 In-Reply-To: (Tom Tromey's message of "Tue\, 22 Jul 2008 15\:20\:31 -0600") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00062.txt.bz2 Tom> I reset the bridge using a trick to try to work around its Tom> timezone woes. I used this successfully once last week -- I hope Tom> it works again tomorrow. It did, yay. Tom> My agenda items are: [...] Some outcomes: * Thiago is happy with the decision. As far as we can tell he was the only non-RH person on the call. * There is some confusion about our relationship to gdb. This is understandable, IMO, since it is a bit vague. Basically I think the best way to think about this project is that it is a development branch with reasonably specific goals (see the earlier threads). * Speaking of the goals, an action item for everyone is to look at the roadmap and see (1) if anything is missing, and (2) what you are interested in working on. For #1, Sami asked about the state of non-stop multi-thread debugging. There are patches on the list. Andrew asked about the multi-process work, but we don't really know enough about it yet -- the discussion on the gdb list seems to be preliminary investigation. * There was general consensus that we should not reuse the frysk list for this work. So, we will set up a new list. Project name ideas that I remember: gdb-- Hmm, that is the only one I wrote down, but I know Phil had another one. "--" seems a bit dismal to me, but "++" seems a bit arrogant :) How about "Project Pelican"? Or anything else. Please. I'd like to settle this today, so... respond. * Where to host? Lots of hosting choices out there, but sourceware seems like the default. We all have accounts, we have access, etc. I'd like to get things set up ASAP, say today. * Talked about source control some. Jim Meyering is setting up a git mirror of gdb CVS. We'll use this as our upstream and have our own git repository. Andrew brought up gdb's eventual move to svn. We can revisit our choices if/when that happens. * We talked about our planned process. The basic change is introducing universal patch review. The scratch idea is: - All patches must be reviewed by someone other than the author. - I forgot to mention this, but Apache-like, a strong objection should stall a patch until a rough consensus is reached. - Anybody "in the project" can review a patch. In fact, I think it is pretty important that everybody do reviews. - Proposed patch review guidelines: * Does it have internal documentation (comments)? * Does it follow upstream coding style? * Does it have external documentation, if needed? * Does it have a test case, if needed? * Is it clear/complete/etc? Andrew asked about how we will decide to accept new contributors into the fold. I think we'll solve this when it comes up. * Action items, for me: - Set up hosting, mailing list - Send consolidated roadmap to the new list (Probably process stuff too) - Send announcement to gdb list Tom