Kyle Maxwell wrote:
But some decisions are starting to leave me in the cold
Err..well...i'm going to give red hat a pretty long lead time on when I expect them to get this whole external communication thing close to the right ballpark. I'm not prepared to read anything sinister into why rhl is down or whatever.Hell I'm shocked it had as much information as it did for the 3.2 days it was up (almost like they knew what they were getting into...they know better now i think :->). But if a significant amount of discussion was generated by the "right" people during those 3.2 days, enough to make a significant portion of that written material inconsistant with bleeding edge ideas...then I say its better to pull the site down..better no info than misleading info. The keys to the kingdom haven't changed hands yet....i'd rather see some significant fits and starts early on...than a big badass policy gotcha later.
Beginnings are hard...this shift towards rhl-"the project" is going to probably need a significant honeymoon window where users and developers..especially the more fervent ones...are going to have to allow for some really bone-headed obvious mistakes from people who live on that corporate side of the fence. I have no expectation that this is going to be a smooth transition during this beta phase. Consider this a proto-project phase....or maybe it would be best to call the project concept alpha level...where the project framework isn't stable enough to make it worth professional documentation. I fervently hope that the machinery for this "project" will be in place by the end of this beta phase.
I've beat the trademark dead horse only because its an existing policy that red hat's to make sure is updated to make sense in terms of the lack of boxsets in the upcoming release. A lot of the other issues that people seem to have with red hat right now on how to effectively communicate with the community are new issues that need new policy... and i get the feeling the hatters didn't shine the flashlight that far ahead when taking that first step towards the project concept. This isn't going to be a linear progression from closed to open...consider the loss of rhl site as the first coffeetable red hat stumbled into and had to backup to step around while groping for a plan. Luckily I don't have to worry about production systems. But as it stands...is anything all that different than a year ago when it comes to deciding if you were going to deploy the next red hat release (other than the lack of boxsets and the oem issues that causes)? I think it helps to think of this beta as still a traditional beta....the community project still needs a lot of flushing out...as a concept its alpha. I can just imagine how much internal discussion is being generated....and I can only hope the hatters show as good a sense of knowing how to schedule a "release" of the project framework as they do about pushing out distro releases.
-jef"i love it when a plan comes together...now...if we only had a plan...though I'd settle for a plan for making a plan"spaleta