X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=ZZy8VTpEtTuVTyyRISeRlB8QgAJ1tKOk9bYM3SMVXdc=; b=qOmtLomH7kHZy0fn4/+nqulgEHONy8K0J8cFbLOCeMtwOQhxZgBVSrYIKQAC7rv+mg aZMwO99j1kfqwqibLwlyAh5SImTXp9HjCUcdivOdTV+Z8M3VyKGj11077f4EHSc01zEX iiymosCPKTiwgObrMUWL8+eR3auKOyiI/fSJwe/CelkkHXLpzWD7Lqu6rj7gh754DMxP EWIsLx8cdjI5JxtPJEPp4GwWDcrOU0Dt3IoKVEh2rLRjA3sOY+DAkN0KFYVgPz10+H2B 7C8/m7dgcZKPmGd/vmtzA66DA8MNJNo2EOXG2Nl4PqoRYC55Fjcsmsvu5pcfLpkvg9bM cP4Q== MIME-Version: 1.0 X-Received: by 10.152.4.103 with SMTP id j7mr3088393laj.92.1442099671476; Sat, 12 Sep 2015 16:14:31 -0700 (PDT) In-Reply-To: References: <201509111624 DOT t8BGOPYV000685 AT envy DOT delorie DOT com> <201509111732 DOT t8BHWnF7005271 AT envy DOT delorie DOT com> <960028A6-F16B-4276-B838-E9F0D2959A6F AT noqsi DOT com> <55F32375 DOT 2020505 AT ecosensory DOT com> <201509111941 DOT t8BJfqWl010427 AT envy DOT delorie DOT com> <201509112020 DOT t8BKKBgI012564 AT envy DOT delorie DOT com> <201509112058 DOT t8BKwF3b013774 AT envy DOT delorie DOT com> <6341DF3E-543D-4E36-9B01-6B5B950208C4 AT noqsi DOT com> <9D45499A-BC67-4B2F-A285-34C49ECC20B0 AT noqsi DOT com> <55F451F4 DOT 8000100 AT ecosensory DOT com> <55F47539 DOT 9090006 AT ecosensory DOT com> Date: Sat, 12 Sep 2015 23:14:31 +0000 Message-ID: Subject: Re: [geda-user] About reinventing the wheel, and how to avoid it From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8CNEbo2030637 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, Sep 12, 2015 at 10:15 PM, John Doty wrote: > > On Sep 12, 2015, at 3:44 PM, Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > >> On Sat, Sep 12, 2015 at 12:08 PM, John Doty wrote: >>> >>> On Sep 12, 2015, at 12:55 PM, John Griessen wrote: >>> >>>> On 09/12/2015 11:53 AM, John Doty wrote: >>>>> On Sep 12, 2015, at 10:25 AM, John Griessen wrote: >>>>> >>>>>>> On 09/12/2015 10:51 AM, John Doty wrote: >>>>>>>>> Test cases are important, but I don’t think it’s necessary to have add-on modules maintained with the core sources in order to test them together. >>>>>>> >>>>>>> >>>>>>> Why? Roland made a clear case for that. >>>>> Successful projects like Python keep core and add-ons separate. >>>> >>>> We don't have enough people to act like the python project. >>> >>> There are 51 megabytes of contributions from 83 contributors on gedasymbols.org. We’re *already* acting like the Python project, except we’re pretending we aren’t. All I am hearing is 83 people have accumulated a lot of contributions and that we are perhaps squandering an opportunity by not finding a way to verify them and package them in a release of some kind. >> And gedasymbols is not well used, or well-tested, or particularly >> accessible to the uninitiated. > > We could certainly do better. I know I have said this before but we need a tool that lets people sign each others contributions as having been tested with a given part, in simulation and what ever else. I know it will make the size of the stuff there larger but it would also mean we could look at the more endorsed stuff and pull it into a central distribution. >> It great to separate things into >> modules but there's no point in not storing and distributing them >> together with the core distribution. > > I think many would find a 50 MB distribution a bit much. Simply distributing a mixed bag of stuff with the core will not relieve confusion. I also see the success of the core/addon approach in other projects. It helps interface discipline when they are kept separate. Indeed. Like most people I keep a spreadsheet with which ones I have made and what they go to, if i have used them and additional notes. Perhaps having a standard way to share that info would be of more value than just having the symbols and footprints themselves. Could we all agree on a CSV column list and then put it at the root of our respective repo's? > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/