On Tue, May 29, 2012 at 4:52 AM, Mark Dixon <[email protected]> wrote: > Fair enough, but please note that I'm not advocating any particular license > here, I'm just trying to understand the issues around copyright assignment > of contributions.
We just want to leave the option available to us. We just need a license that we can use to add value to the whole ecosystem. > I'm still in the dark about why OGS wants it. We stayed with the Grid Engine open source project for over 10 years, and we will at least spend another 10 years with Grid Engine - so if something comes up in the future we will need the option to do something. And if over a decade of track record does not convince you, then we can of course put something on our homepage saying something similar to "if the Open Grid Scheduler project maintainers decide to close the source, then others can pick up the maintainership" - I think I sent something similar to the list before, but mailing list messages do get lost quickly :-P > Is this why OGS is asking for copyright assignment - to replace the execd > and shepherd? What's the problem you're trying to solve here? We are not trying to solve anything yet - I was using it as an example. > It still sounds like a large job. I can imagine that the 30,000 lines of > dedicated execd code can be replaced with something rather smaller these > days, but there's all the libraries like the CULL and GDI that it depends > on. Rather you than me: I hope it's worth it. It's more like 10,000 lines of code in execd if you exclude all the PDC & PTF code, the copyright header, comments, etc in the core execd. If we were to rewrite execd, then CULL and GDI are on the list of things to be replaced as well - but we are talking about the very far future. I actually like the code architecture that has a cleaner separation of API, rather than just issuing lower level GDI operations and let the client side operate on the results. > Is this the gridscheduler-developers sourceforge list? > > I tried looking for a button to push or address to email to join it, but > didn't have any luck. The web frontend doesn't show anything posted to it > recently - is archiving turned off? > > If you were willing to let me on, I'd very much appreciate it. Ah, we created the lists on the Open Grid Scheduler project homepage but ended up joining this list on gridengine.org. We are on the dev list of gridengine.org as well. Let's use the lists on gridengine.org. (We now use the lists on the Open Grid Scheduler project homepage for people to discuss very specific project issues - but as most of the code changes & usage issues are common to all 4 Grid Engine implementations, there's no point in forking the discussions.) > Is this the reason why people don't seem to like SISSL? As a person who is slightly against GPL, SISSL is not a bad license at all. SISSL is similar to the Apache license. Other than the naming requirement, SISSL is a retired license - and Google Code originally did not accept SISSL projects, or otherwise Open Grid Scheduler would now be hosted on Google rather than on SourceForge. > IANALL, but I'm not sure they had much choice: it was a modification to > existing SISSL-licensed files. The difference is that Univa has an agreement with Sun (so they say - we have never seen the agreement) so that they can workaround the naming part. However, if you license code under SISSL again, then you don't necessary agree to their agreement and can impose the naming requirement on their product again. I believe they are smarter than that, and may be they word the SISSL slightly differently in their contributor agreement. > It's in an email from me to [email protected], dated 9/12/2011 with subject > "[PATCH] Fix PE task array job failure due to missing job script on execd". > > I'm happy for any of the gridengine forks to take it (hint). Thanks, I think I've seen that one before... at least the title - but then again, mailing list messages get lost quickly, and may be I did not pay attention as I was & am always busy with many things :-D Let me revisit it again later this week. Rayson > > > Mark > -- > ----------------------------------------------------------------- > Mark Dixon Email : [email protected] > HPC/Grid Systems Support Tel (int): 35429 > Information Systems Services Tel (ext): +44(0)113 343 5429 > University of Leeds, LS2 9JT, UK > ----------------------------------------------------------------- _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
