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; bh=MN7jVbhVTnCkXIGUbIW9mutfIA50nR5PWhiOnp0226A=; b=G1qtjZCnjSXDzC8dFAJI3kx/OYFZ0UvM+Euema8pdw4srO22PLFE9Y/xRPZ78F+23C yEeO0AcFugyrjMWTo1v21Vzl/JWkx1lS9j0G1O72f2/stkSTaah7zOowSefgzNtN6I7D jqjuy0Ko1wBp9t0tXc8BPNSNoOPJVohjvig1GGZef9NgXnyMBuergAQjFDF11RUrfSxg +yfTgHEfCiXUEdUzodupH3ue+pxAQDUi8B8HfQl+IiAhA16pyCz7jZkIUXvX06c4xBuK EVw51OjW01Jdt/rCJzZFGi+HBEGv+XmUc3uw3Y1iS74O6GL6KRbHHctExBogbWQB7N9X jm5A== MIME-Version: 1.0 X-Received: by 10.107.18.84 with SMTP id a81mr52159023ioj.14.1435937521709; Fri, 03 Jul 2015 08:32:01 -0700 (PDT) In-Reply-To: References: <1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de> <20150703030409 DOT 32398 DOT qmail AT stuge DOT se> Date: Fri, 3 Jul 2015 08:32:01 -0700 Message-ID: Subject: Re: [geda-user] gEDA/gschem still alive? From: "Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a113ed82ae6b7650519fa41b5 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 --001a113ed82ae6b7650519fa41b5 Content-Type: text/plain; charset=UTF-8 On Thu, Jul 2, 2015 at 8:38 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > Peter hit on a number of good points there. If we were to really > measure how a piece of open source software is doing I think a less > crude measure would be based on how long and how many bugs have been > reported and unresolved. > > When was the last time any one here spotted a bug in gschem? > It has been very stable but the current release (1.8.2) has been out for several years. Ver 1.9 has some nice features that I woud like to use but until it is blessed and pushed out to all the repo packagers then I will stay with the older one that is an easy apt-get install away. Does gEDA still run on windows? I have heard rumblings that it is currently broken. Bit rot is real. Unless you are actively testing with the newest distros then any open source project will sink into decay. You also have the big issues like the choice of scheme as gEDAs scripting language and the gEDA file formats. Is there anything to gain by changing and if so then what would be better and how do we transition? John Eaton --001a113ed82ae6b7650519fa41b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Jul 2, 2015 at 8:38 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> = wrote:
Peter hit on a number of good poin= ts there. If we were to really
measure how a piece of open source software is doing I think a less
crude measure would be based on how long and how many bugs have been
reported and unresolved.

When was the last time any one here spotted a bug in gschem?

It has been very stable but the current release (1.8.= 2) has been out for several years. Ver 1.9 has some nice features that I wo= ud like to use but until it is blessed and pushed out to all the repo packa= gers then I=C2=A0 will stay with the older one that is an easy apt-get inst= all away.

Does gEDA still run on windows? I have heard=C2= =A0 rumblings that it is currently broken. Bit rot is real. Unless you are = actively testing with the newest distros then any open source project will = sink into decay.


You also have the big issues like th= e choice of scheme as gEDAs scripting language and the gEDA file formats. I= s there anything to gain by changing and if so then what would be better an= d how do we transition?



John Eaton

<= div>
--001a113ed82ae6b7650519fa41b5--