No, I think that as a principle that prevents us from inadvertently or short-sightedly putting ourself into a locked-in position vis-a-vis a contractor, this kind of statement of principle is exactly what we need. Henrik on 2004-12-03 5:45 pm Leslie Daigle said the following: > Hang on... are we not getting too detailed again, at the > risk of over-constraining ourselves? > > As has been mentioned on this thread -- we (IETF) may well want > to take advantage of non-open-source software, if it's the > most effective & efficient choice. I'm thinking specifically > of contracting with a provider that has their own software tools. > > Neither should we be constraining ourselves to choose from > providers with open source tools, nor should we be requiring > that *all* features we ask to add to those tools be available > as open source, or freely to the IETF, etc. > > Taking the step back -- the principle was that the IETF should > retain the rights to, ability to access, and ability to move > the data it creates. Period. > > Sensible ways of achieving that include (but are not limited > to) working with open source tools and/or ensuring we retain ownership > of any software that touches that data. Others include > using reasonably accessible off the shelf software (one Excel > program is much the same as the next...), or agreeing on > data interchange formats. Let's not try to make the laundry list > in this document. > > Leslie. > > Harald Tveit Alvestrand wrote: >> >> >> --On fredag, desember 03, 2004 10:19:23 +0100 Henrik Levkowetz >> <henrik@xxxxxxxxxxxxx> wrote: >> >>> >>> What about this text, (added to 2.2.6): >>> >>> "As a matter of principle the IAOC and IAD should ensure that any >>> contracts for IASA clearly designate that any software, databases, >>> and websites developed should be available to the IETF with no >>> restriction by the contractor. Software should be open source and >>> data should be made available to the IETF in machine-readable >>> format, also in cases where it may be inadvisable to make the data >>> openly available." >>> >> >> this works for me (my only problem is stylistic - it's somewhat long for >> a principle, so may fit better in the "details" sections, if a place can >> be found for it). >> >> >> >> >> >> _______________________________________________ >> Ietf mailing list >> Ietf@xxxxxxxx >> https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf