On 10 Jun 2011, at 22:00, David Greaves wrote: > Hi all > > It's good to see continued interest in BOSS and the associated participants. > > I see that several of the projects have been cloned (well, not cloned, just > copied for some reason) at: > https://gitorious.org/meego-boss > and there is some active development there. > > I do hope the plan is to co-operate with the upstream team - we're really not > that far away ... #meego and #meego-arm usually :) > > There are commits going back to January ... and as far as I'm aware we've > never really been approached to discuss how these tools are evolving in MeeGo > RE. We've had a couple of merge requests (incidentally - gitorious doesn't > seen to notify very well so if you talk to us we'd look at them a *lot* > faster). I know Islam has made several enquiries about changes to your tools > but we didn't get any reply. > > There must be some mistake because I'm sure the RE team would *never* ignore > the "work with upstream" policy they ask others to follow.
What exactly are you referring to here that has not been upstreamed? Most of the work being done in the above mentioned project are new participants. The only big changes are to IMGer, but there are loads of reasons for doing so. > > In fact I was only vaguely aware BOSS was being used in MeeGo RE - and that > is decidedly odd considering I'm the architect for them and have presented on > the tools at both the MeeGo conferences. You can even see how some people > would get a little paranoid about here :) Then someone probably did not want to tell you? :) We have been using BOSS for the almost 8-9 months now, boss was initiated to be used on MeeGo, I am not sure exactly why you are wondering it is being used in MeeGo. The question is: Is BOSS a MeeGo project? You not being aware of it being used in MeeGo is baffling me and if you think about it, answers most of your questions. > > I know Intel pulled the entire RE team from the SF conference - maybe we'd > have had a chance to discuss it there ... sadly we'll never know. > > Anyhow, as you may know we're hoping to provide a more productised > installation: > http://wiki.meego.com/Release_Infrastructure/BOSS/Installation > > Would it make sense to simply join our team and talk directly about your > requirements? > > For example it would be nice if the work in could be aligned with : > http://wiki.meego.com/Release_Infrastructure/BOSS/Roadmap > > So... what do you think? Can I expect some more communication and some > proposed patches? Yes, sure. Communication goes both ways as we know. When did you last ask MeeGo release engineering about their requirements and input to the above? Where are all of those requirements and plans mentioned above are coming from btw? Anas > > 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 _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
