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=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=I8slSDan1bNynsbdtm0cj5C2va1Vtg5QQO3ntwany2E=; b=EVqSQh/2RlhVAnZbeC5M44YKSDEB8B7r1uv6F+/22Pm0shs1aAaNixOdmccrWtutLW 5anWfgNhPYzr89z8gvqdIo9uosYHe5iovR+t5z9xq126SRZVXLKczJ19LkIVJXT62F5V wu8E6FzO1nDAxrCghf5XXeWmmtwWm0uWjIq3fA+uMy5Uju+Ms7WIJ6hWXdum1YeF42oy M/x0pbQS5v/V7DqEAjCiuLPiFmSpDPdWkLog50Rf8Q3NbbCOHMDcfHU+FL37r+jHsm4a g8XlUgv/ELBYXa3xRaga7zmSe/MD8QBarjq6D6gXYbQvJgkXhQ4NksLSA7JVeMhjvoVa 8liw== MIME-Version: 1.0 X-Received: by 10.60.246.43 with SMTP id xt11mr6654603oec.48.1450792252357; Tue, 22 Dec 2015 05:50:52 -0800 (PST) In-Reply-To: References: <20151221030451 DOT 02399163eb3e40f21c622c41 AT gmail DOT com> <20151221203331 DOT 20837 DOT qmail AT stuge DOT se> <20151222002012 DOT a88d7fe32a9336855eccd1d0 AT gmail DOT com> <201512220412 DOT tBM4CJxb018546 AT envy DOT delorie DOT com> Date: Tue, 22 Dec 2015 13:50:52 +0000 Message-ID: Subject: Re: [geda-user] Proposing a New Hierarchical Data Structure? From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: text/plain; charset=UTF-8 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 22 December 2015 at 04:39, wrote: > Nope. As far as I understood, we are considering the very first step of a > roadmap. The first step is about how to pick a file format or data > structure. Peter proposed a specific standard and listed a lot of pros. > > My point is only this: not having the standard freely available is a con > that we should not ignore. This is true.. and I've pointed one of the key players in the AP210 standard at this discussion thread, to see if any impact might be made on the situation. Personally, I doubt we can change the situation... the ISO is big and ugly, and we are _tiny_. If anyone had doubt about the reality of this, open source EDA is almost irrelevant in the "real world"... no-one cares, and our desire to see / use / contribute to a particular standard will not likely result in anything. It would be nice to change that (make open-source EDA more relevant), but it will take a lot of time and effort. We would first need to get over the under-developer-resourcing, the identity / goals arguments (AKA "community problems") gEDA has had in the past, and we will need to learn how to cooperate and collaborate with other open-source projects (like KiCAD). We (open source EDA) need a MUCH bigger mind/market share to effect change. Peter