Hi, Some of us in the desktop team are looking into taking some of the spec-files-extra packages and making them available for OpenSolaris. I'd like to invite the people working on SFE to work with us on these packages. What we need to do is: - make sure the spec file builds - it's the latest available stable version - works reasonably well
Ideally, we need an owner for each package, who will look after it: keeps it up-to-date, interfaces with the upstream community (reports bugs and/or submits fixes). This effectively means becoming the opensolaris maintainer of the package. We will also need help with testing and filing bugs -- this is far less commitment than maintaining a package. I suggest we use the new opensolaris.org bugzilla for tracking bugs. I'll post an initial list of packages that are under consideration shortly. To be officially part of opensolaris/ indiana, all this needs to be done under the opensolaris umbrella. We can do this in the JDS project or revive the pkgbase project and use its svn repository. In any case, people involved in this will need an opensolaris.org account (if they don't have one yet). More details about svn access will come later. This repository will have to be more controlled than SFE but still easy to contribute to. Again, I think the JDS/pkgbase approach of light-weight code reviews should work just fine. The Desktop Release Engineering team can do regular builds and the Desktop QA team will do some testing. Currently the process for integrating into indiana is not completely clear and not at all straight forward, unfortunately. Since Sun is involved in producing the binaries, we need to complete a lot of paperwork (legal reviews, etc) so things take longer than we hope. We are working on making the process smoother. The good news (for non-Sun people ;) is that this is something Sun employees will have to look after, so you don't need to worry about it. We will also need to complete ARC review. Again, this is something that the JDS team will look after, but help is appreciated (identifying imported and exported interfaces, etc.) As always, comments welcome. Laca
