I am glad to hear all the stuff you mentioned:) Thanks, David. - jf.ding
On Mon, Jun 13, 2011 at 05:12:51AM -0700, David Greaves wrote: > On 13/06/11 12:13, Jian-feng Ding wrote: > > Hi, David > > > > Some clarification: > > 1. As Anas said, most of the projects in > > https://gitorious.org/meego-boss are staging > > ones, which will be moved back to the official place, say, > > http://meego.gitorious.org/meego-infrastructure-tools > > Good to hear. > > > 2. For boss.git, notify participant, and ruote-amqp-pyclient, Li Yi and > > I created clones from the "upstream" ones, > > based on the commit point which we are using in current production > > environment. > > Why? > > Because these projects had many dramatically changes in the last > > several months with incompatibility. Our > > production instances can be be updated or upgraded frequently. We > > need keep the compatibility in a safer places. > > I think it is also the typical work model of open source projects. > > Yes, I can understand that. Hopefully we can establish release branches which > only take bugfixes and support deployments in the future. > > > 3. I feel there are not too many overlap parts of the deployment of > > MeeGo production cycles and the Nokia environment. > > Most the "official" part of changes and document are focused on Nokia > > env only, and we can not learn the details > > until now. So the running components in MeeGo env were developed and > > deployed based on our own understanding and > > feature requirement. > > For these incoherent parts, I think we need not to merge together. > > True - but I'll also say that we engineers want to make sure that the Nokia > funded work meets the original (and not yet cancelled) objectives of being > useful for the community. So we want the main MeeGo release version to be > supported as well as any versions of systems used by MeeGo vendors. > > > 4. We DO try to and like to merge back the changes to the "upstream" git > > tree, if the changes are compatible and > > valuable. Of course it is just in a start stage, but it will be more > > frequently and fluently, I hope. > > OK. Look forward to it. > > > 5. For SF MeeGo conference, I DID like to go there to meet you guys to > > talk about the BOSS. But the committee didn't > > think my BOSS related presentation was important enough:) > > Yeah, That's a shame. I hope that the next conference will want more from the > 'MeeGo systems' areas. In the meantime maybe we should have some irc meetings > and possibly a conf call? I'm going to work on rewriting the wiki pages that > cover the systems we use 'soon' :) That may help set an agenda. > > David > > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
