[os-engineering]
FW: [os-infrastructure] Re:Model discussionboileddry(er)
Stephen Ball
Stephen.Ball at ingres.com
Mon Jun 30 17:44:11 PDT 2008
Yes, for sure this is true. If we were in a position where we still had
B1 in the code and we wanted to release Ingres into open source without
it; that would be impossible without removing it from the code first;
unsurprisingly, that's exactly what we did, we removed it when we first
went open source, which is why we have no B1 support in the code today.
If we were doing it again today, I think taking a new branch and
removing it from the branch before releasing that into open source is a
better option. Fortunately we are not in that same position today, as
far as I know, any of the items still in the code that we do not want to
release to open source are in isolated directory trees, and I don't
foresee there being any things we would add in the future that would not
be open source...so from a practical stand-point this is not a real
issue.
Steve
-----Original Message-----
From: Joseph M. Abbate
Sent: Monday, June 30, 2008 11:59 PM
To: Stephen Ball
Cc: Discussions about the infrastructure needed to support a true
opensource community; Open Source Engineering
Subject: Re: [os-engineering] FW: [os-infrastructure] Re:Model
discussionboileddry(er)
Hi Steve,
Stephen Ball wrote:
> I'm figuring "trunk" may not necessarily mean "all of main", if there
> were any non open source parts presumably we would exclude them from
> Subversion. But don't we have that issue no matter what model we
choose?
>
The question in my mind is how do you define those "parts". If it's
something easily restricted to a given set of Piccolo directories, then
may be fairly easy. If I understand correctly, that's how OpenROAD
could release its 4GL code as open source without releasing the 3GL
pieces which for the most part live in other Piccolo directories. We
similarly "removed" spatials from Ingres DBMS open source, because most
of it was in common!adf!ads. However, if you look at change 469243
where you removed B1 security support, you had to touch (edit) 380 files
all over the source tree. Conversely, although I don't know much about
Project D, I'm guessing that would affect various areas of PSF and QEF.
There is therefore a high likelihood that changes will affect existing
directories and existing files, i.e., not neatly separable "parts".
Joe
More information about the opensource-infrastructure
mailing list