--- On Wed, 3/16/11, Dave Love <[email protected]> wrote: > I was assuming the private branches that have been merged > were just for > development, which is the right way to work. I didn't > mean you were keeping anything back.
While we are going to talk about merging the forks in the next Grid Engine Steeling Committee Meeting, I am not sure if we should do it in a short time. One thing is that I have not seen the contributor agreement from Univa, and the other thing is that all the code in Open Grid Scheduler is open source, so Univa and others can take the changes and merge them if needed (Dave has been looking at the changes in Open Grid Scheduler and merge them into Son of Grid Engine for a while, so this is not new). Finally, a lot of people do not believe in open-core, which Univa is going to do with its branch. So why close 2 open-source projects (Open Grid Scheduler & Son of Grid Engine) and in return only get an open-core project? -Ron > I think there's too much talk > of `forks' and so > on without considering people's intentions to collaborate, > which is what > matters, and doing everything directly in some central > repository was > never a viable way to work. > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
