I'm probably not the one who should try to answer this, since I haven't been around when the relevant decisions were taken, but whatever...
Stefan Teleman wrote: > yes, there are three very good reasons: > > 1. we don't know what exactly would be hosted there. In the ideal world, specs & patches. > 2. we don't know the rationale behind the decision of splitting the > existing cvsdude SCM to another SCM, and which is now being proposed for > yet another migration to a third SCM. I also don't know what was the rationale behind having a mesh of 2-3 different SCMs, but having one SCM for specs & patches, like workspaces of other projects using pkgbuild, seems like a good idea to me. > 3. we don't know the rationale behind any of the decisions regarding > inclusion, or exclusion of kde4 dependencies. If there are questionable dependencies (even hosting a spec file is a problem, right?), then this would be a major one, sorry for reopening that... Pavel Heimlich wrote: > would it have any benefits? who has the time to do that? I for one am not particularly interested in learning yet another cms or whatever, just for the sake of residing inside slightly nicer domain. Not sure what you mean by another CMS, it could be the same one. > plus there might be issues with some of the dependencies possibly viewed as infringing some software patents only valid in the country of opensolaris.org origin, I guess ... > > I'd rather see a proper mirror structure plus clearly defined roles and deputees so that it does not go downhill when one person goes offline for a week and things get fuzzy Right. Could we take the same path as, for example, SFE and create the repository on some publicly hosted service? hnhn -- Jan Hnatek jan.hnatek at sun.com
