X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 207.224.51.38
X-Authenticated-UID: jpd AT noqsi DOT com
Content-Type: multipart/signed; boundary="Apple-Mail=_D673BCDD-0123-4E14-B065-31B335A8F0AC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] A lesson from gnet-makefile
X-Pgp-Agent: GPGMail 2.5.2
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <CAM2RGhTg=nT4aXqdiRz+OmHJ3WiMJntiTZyOH3AdFBZ8dEyT4w@mail.gmail.com>
Date: Wed, 21 Oct 2015 11:54:54 -0600
Message-Id: <DA7D969B-6516-4633-831C-FFADA38E1807@noqsi.com>
References: <1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com> <34B17816-9EA5-45FD-BFB4-9D623A8D3D87 AT noqsi DOT com> <CAM2RGhR+K+dvDdXsbk0Y6LN=-7RhhG5wvtG4i0k4+uMgzd=H0w AT mail DOT gmail DOT com> <201510210954 DOT 46552 DOT ad252 AT freeelectron DOT net> <CAM2RGhTg=nT4aXqdiRz+OmHJ3WiMJntiTZyOH3AdFBZ8dEyT4w AT mail DOT gmail DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
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


--Apple-Mail=_D673BCDD-0123-4E14-B065-31B335A8F0AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 21, 2015, at 11:30 AM, Evan Foss (evanfoss AT gmail DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> On Wed, Oct 21, 2015 at 9:54 AM, al davis (ad252 AT freeelectron DOT net)
> [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>> On Tuesday 13 October 2015, Evan Foss (evanfoss AT gmail DOT com) [via
>> geda-user AT delorie DOT com] wrote:
>>> We could prototype it via a plugin but in the long term it
>>> should really be in the core.
>>=20
>> Maybe, but maybe you should rethink  plugins.
>>=20
>> Gnucap takes the approach of putting as much as possible in
>> plugins.  Anything that can be a plugin is required to be a
>> plugin.  A set of plugins is distributed with core, but they are
>> still plugins.
>=20
> While I agree the fact is that this change will make possible a whole
> family of plugins that will use it. That is half the justification for
> putting it in the core. The other half is that the same functionality
> for handling flattened nets is also in the core for the same reason so
> splitting their locations would be architecturally confusing to new
> people.

But the first problem is understanding which functions should be in the =
core. That requires understanding the FFI and the Scheme functions built =
atop it.

>=20
>>> To be honest I find your
>>> "don't touch the core you will break something" attitude
>>> kind of insulting.
>>=20
>> Don't touch core if you can do it in a plugin is good policy,
>> but core needs to develop too.
>=20
> John's fear (which he later admitted was miss placed in this
> situation) was over someone making changes that required updating all
> gnetlist backends.

Not simply that. A change that broke just one back end might actually be =
harder to deal with. And a change that couldn=92t be undone in a back =
end would be very bad.

>=20
>> There needs to be some discipline in how core changes are done.
>> Having a bunch of developers all messing with "master" leads to
>> a big mess.
>=20
> 1. No one was considering doing that. They just rolled out a package
> server side for managing a hierarchy of user accounts.
> 2. I intentionally opted out of having commit privileges to the master
> so someone else will have to approve it.
>=20
>> In Gnucap, all work on core is done in branches.  A branch is
>> considered ready to merge when it is shown to work correctly,
>> has test cases, is formatted correctly, announced and discussed
>> on the developer list, and its branch can be merged to master or
>> unstable as a fast-forward merge.  When ready, the branch is
>> pushed to unstable for final review and then to master after a
>> few weeks.  So, master is always "considered stable".
>=20
> How branches are managed is a matter of some debate but I am not
> involved in that.
>=20
>=20
> --
> Home
> http://evanfoss.googlepages.com/
> Work
> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
>=20

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



--Apple-Mail=_D673BCDD-0123-4E14-B065-31B335A8F0AC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJWJ9FuAAoJEF1Aj/0UKykRuTcQAJeH/2Ak7wIqpUraIGqOmeXF
TPag8+jUYOqzt6pKT9Uu2bGXQN+1yAmQnoqXsos4Wo5udrlITM7Il8upTtz62GWW
ZxrTdtlTpMWX6bT9v0xPDjQlzpLB333uaJ0Q/jksYo5ATfun5GBtGOBb1wBWvhcd
dTr6a5eS87q4eFCcU5I/oOnKY5vIILNZLOUEfMKbQBRG11t6DQ1EiCcGK1dMuOLF
HayTnsCDFA0PwBuc6dgc+/EG6AO3D3C1XCiWRy9V7yLX9AyXgNxZojKiIV23J6Zr
YKOnqEnPDHxe8pDKuAHegA9clTSzFZlPr7tKI4tSSYDaKamJfvivdAeMExPkwDHf
hZ6YXmJkw41cbMxDQ2606VHmOQqkCeMMltyXadiaWtMqqEWTMLk5Wnpv9xPny/mM
T4oqhcKiS8/1s+zrfonXow0Mfz7o1yj3OAUQxuH5uIE2MIXn/amsBQX53csF4EPt
Ma8gLsOylSGYSEAzaqX56e2kQgefwjwNvSZcWESt5mSNFWZAfx0zCvTjawtXBRDs
CgzfoHk4h/LAoxXvYcb8EWwczGKRHy1gxxDscQ/nwC74c0cA9Uf2wtyZrBehylb6
AiVEXMoztMB6YnFo38HTRGWEuOVGC+F7gqrmQ1U7VcqWOOXINCZWVGEr6Ny2syBW
guZre+7a9v5TyoRhfqhg
=sXJu
-----END PGP SIGNATURE-----

--Apple-Mail=_D673BCDD-0123-4E14-B065-31B335A8F0AC--