--- On Sat, 9/10/11, William Bryce <[email protected]> wrote:
> Hi Ron, 
> 
> I suggest you take your 'tin foil hat off' Ron. 

Hmm, so you were claiming me starting a flame war. Guess who is doing it now?

In other successful open source projects, there is transparency. With Univa not 
disclosing what is open and what is close, I don't think we can should continue 
this "working together" discussion or even bring it up again in the near future.

 -Ron


> Initially we thought that we should ask
> people to assign copyright to Univa if they want to include
> fixes  but we continued to discuss and we were
> discussing that if we do have copyright assignment that it
> be assigned to an 'independent 3rd party' i.e. not Univa but
> something that we all have a stake in.  
> 
> But you can believe what you want to believe Ron.
> 
> Bill.
> 
> On 2011-09-09, at 11:44 AM, Ron Chen wrote:
> 
> > Bill, please stop misleading the list. This is EXACTLY
> this kind of tactics that I am against.
> > 
> > I am not talking about not putting copyright to my
> code (my code is under SISSL, and Univa Grid Engine has 10
> features that were developed by me.)
> > 
> > What I was referring to is copyright reassignment. You
> have requested me to reassign the copyright of my code to
> Univa not long ago, I am suprised that you could mix up the
> two.
> > 
> > -Ron
> > 
> > 
> > 
> > --- On Fri, 9/9/11, William Bryce <[email protected]>
> wrote:
> >> I agree with Hung-Sheng, 
> >> 
> >> You should put copyright on your code, and in
> regards to
> >> Ron's comments.  I won't comment - Ron can
> have a flame
> >> war with himself :-)
> >> 
> >> Bill.
> >> 
> >> On 2011-09-09, at 11:22 AM, LaoTsao wrote:
> >> 
> >>> IMHO, every code need copy right
> >>> especial someone else try to make $ out of
> your code
> >>> my 2c
> >>> 
> >>> Sent from my iPad
> >>> Hung-Sheng Tsao ( LaoTsao) Ph.D
> >>> 
> >>> On Sep 9, 2011, at 10:40, Ron Chen <[email protected]>
> >> wrote:
> >>> 
> >>>> --- On Fri, 9/9/11, Mark Dixon <[email protected]>
> >> wrote:
> >>>>> I'm still a bit fuzzy on what
> differentiates
> >> the efforts,
> >>>>> and am concerned that the projects
> might not
> >> be pulling in a
> >>>>> common direction to benefit the
> community as a
> >> whole.
> >>>> 
> >>>> Mark,
> >>>> 
> >>>> In fact our existance benefits the
> community --
> >> did you know that we fixed the memory accounting
> bug on
> >> Linux in the Open Grid Scheduler back in Aug last
> year, and
> >> Son of Grid Engine copied our fix? And Univa Grid
> Engine
> >> 8.0.0 still has that bug *as of today*, and its
> customers
> >> need to wait for 8.0.1 to get a fix.
> >>>> 
> >>>> And I hightly doubt Univa would put as
> much effort
> >> as it is now and add the hwloc support into the
> open core if
> >> we did not announce our hwloc support back in
> April:
> >>>> 
> >>>> http://gridscheduler.sourceforge.net/projects/hwloc/GridEnginehwloc.html
> >>>> 
> >>>> Also, I strongly believe that Univa will
> now put
> >> more effort in to get GPU integration, IPv6
> support, SGI MPT
> >> integration, etc into the open core ASAP as we are
> working
> >> on those features in Open Grid Scheduler.
> >>>> 
> >>>> When there is no competition, most
> businesses tend
> >> not to work hard to gain market share - and I
> don't think
> >> Univa is different.
> >>>> 
> >>>> 
> >>>>> Isn't this what the steering committee
> was
> >> aiming to improve?
> >>>>> As far as I can see, there's been no
> news
> >> posted to
> >>>>> gridengine.org since February.
> >>>> 
> >>>> The page is old, and Stephen Dennis quited
> Univa
> >> as well.
> >>>> 
> >>>> 
> >>>>> I'm not trying to have a go at anyone,
> I think
> >> everyone
> >>>>> wants what is best for the community:
> I'm just
> >> hoping for a
> >>>>> bit more constructive discussion about
> what
> >> that might be
> >>>>> :)
> >>>> 
> >>>> 
> >>>> I have a tendency not to trust companies,
> as a lot
> >> of them are somewhat dishonest and lack of
> integrity in
> >> order to gain a customer or two. I have not
> totally written
> >> off Univa yet, but what Univa posted on the
> website about
> >> open source Grid Engine is not true (and the ones
> most piss
> >> me off are "UGE Wins Hands Down" & "Free Grid
> Engine
> >> isn't Free"?) -- so at this point working with
> Univa is out
> >> of the question.
> >>>> 
> >>>> And even outout the stupid market tactics,
> Univa
> >> is never clear what would be put in the open core
> and what
> >> is closed source. I am not signing the copy right
> assignment
> >> - they can continue to copy my code and feature as
> they
> >> wanted.
> >>>> 
> >>>> -Ron
> >>>> 
> >>>> 
> >>>> 
> >>>>> 
> >>>>> 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
> >>>>> 
> >>>> 
> >>>> 
> >>>>
> _______________________________________________
> >>>> users mailing list
> >>>> [email protected]
> >>>> https://gridengine.org/mailman/listinfo/users
> >>> 
> >>>
> _______________________________________________
> >>> users mailing list
> >>> [email protected]
> >>> https://gridengine.org/mailman/listinfo/users
> >> 
> >> William Bryce | VP of Products 
> >> Univa Corporation - 1001 Warrenville Road, Suite
> 100 Lisle,
> >> Il, 65032 USA 
> >> Email [email protected]
> >> | Mobile: 512.751.8014 | Office: 905.237.4462 
> >> 
> >> 
> 
> William Bryce | VP of Products 
> Univa Corporation - 1001 Warrenville Road, Suite 100 Lisle,
> Il, 65032 USA 
> Email [email protected]
> | Mobile: 512.751.8014 | Office: 905.237.4462 
> 
> 

_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to