Stephen: > I've attached a fast track writeup for RRDTool. I would appreciate any > comments from people. > > I am particularily wondering about which arc to send this to?
These ARC materials are not particularly clear about how RRDTool will be used. I think it would be easier to determine if this should be ARC'ed via LSARC or PSARC if we had more information about who will consume these interfaces. For example, if a main consumer is a project that is going to be measuring system performance statistics (e.g. the # of octets passed through the FDDI interface of your router), then this sounds more like a PSARC case. If the main consumer is a desktop program, then LSARC makes more sense. > and about importing volatile interfaces and the > requirement for signed contracts with the owners of those interfaces. You need a contract to import Volatile interfaces, unless you are in the same consolidation. So, if this project is in the JDS consolidation, you don't need a contract for libart_lgpl. Otherwise you do. Note that if this project is a part of the JDS consolidation, then you might be able to make use of the existing JDS libfreetype contract. You should probably ask the Xserver team if this is okay, though. http://jdswiki.ireland.sun.com/twiki/bin/view/ARC/GnomeImportedInterfaces http://sac.eng.sun.com/arc/LSARC/2001/384/commit.materials/contract-01 I remember, about a year ago, we discussed with LSARC whether we needed to get a contract to use GCC to build a few JDS components (liboil and libcdio - though we no longer shiop libcdio). I remember that it was determined we did not need a contract. So I don't think you need a contract for libgcc. By the way, in what case do you see libgcc is Volatile? It seems to be External in this case: http://sac.sfbay/PSARC/2004/742/mail Brian
