I have a simple proposal, which I hope will reduce the overhead and
contention that many of us have felt.
For the folks looking to integrate software many for consumption in
Indiana -- lets figure out how to get this into an IPS repo somewhere (I
believe IPS repos work now for Indiana at least), so we can make the
Indiana folks (users and developers alike) happy.
Those cases probably don't need to come before ARC right now --
particularly since IPS itself isn't covered by ARC. Instead, just keep
a record of what FOSS software is in the IPS, and it can be part of a
"master list of initial software" that is included with the Indiana/IPS
ARC case, if/when it comes before ARC. (Also, it appears that the
Indiana CTeam, if there is one, isn't requiring ARC approval for
commitment.)
The FOSS packages which need to ship as part of Nevada -- they should
still come before ARC. Hopefully those packages have wider appeal, or
somehow fill some kind of architectural gap/vision beyond "make all FOSS
software available".
My guess is that a lot of the packages that are interesting to a small
minority of people probably don't really need to be in *Nevada*, and
hence can probably skip the overheads associated with integration there.
-- Garrett
