X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <55F51834.2010300@xs4all.nl> Date: Sun, 13 Sep 2015 08:31:16 +0200 From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] About reinventing the wheel, and how to avoid it References: <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> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Reply-To: geda-user AT delorie DOT com John Doty wrote: > On Sep 12, 2015, at 5:14 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > >>>>> 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. >> > This may be relevant: > > http://www.cpan.org/misc/ZCAN.html > > Or maybe not, I don’t know. But we are getting back to the original topic, sort of ;-) > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > > > Hi, Read the above link until here: When designing your author/module/whatever hierarchy *think scalability*. We originally got it wrong in one spot by having all authors as subdirectories in one single directory which quickly became a bottleneck. (The solution to this was simply to 'hash' based on the leading two characters of the user ids.) Think also several different views to your data: by author, by module, by category, by date, by keywords, and so forth. Don't think only hierarchical views will be enough: you will need searching capabilities. Kind regards, Bert Timmerman.