[alberto]

Originally Posted by arjun

I hope you are right.

But the reason I asked that is that long time ago Hrv posted something that got stuck in my head. May be I got wrong impression because of that. I had hard time finding that post but i finally found it.

http://www.cfd-online.com/Forums/ope...-openfoam.html

Here is his post:




From this post, I got the impression that Hrv wanted GGI to be part of extnd project only. This is why I asked the question that what happens to features that are NOT part of openfoam of openCFD.

How this whole thing going to go further.

Since the GGI module is part of -extend, and -extend is under the GPL, the idea of "keeping the code in -extend only" does not work. Whoever can use that part of the code and re-use the code, as long as the original copyright statement is maintained. I assume the problem is exactly this second point, and the lack of recognition for the work done in "-extend".

Best,

[arjun]

Originally Posted by alberto

Since the GGI module is part of -extend, and -extend is under the GPL, the idea of "keeping the code in -extend only" does not work. Whoever can use that part of the code and re-use the code, as long as the original copyright statement is maintained. I assume the problem is exactly this second point, and the lack of recognition for the work done in "-extend".

Best,

Thanks for clarification.

so I take it as openCFD can lift the code from extnd version and use it with their version all they have to do is 'recognize' that work is done in -extend.

Means , those who are going to use SGI openFOAM would be able to use GGI just as -extnd version (if someone added the code into sgi-openfoam).

[alberto]

Originally Posted by arjun

Thanks for clarification.

so I take it as openCFD can lift the code from extnd version and use it with their version all they have to do is 'recognize' that work is done in -extend.

Means , those who are going to use SGI openFOAM would be able to use GGI just as -extnd version (if someone added the code into sgi-openfoam).

Yes, all what you have to do is keep the original copyright statement, and, if you change the code in a relevant manner, add your copyright statement. It's not exactly "lifting", since who releases a code under the GPL knows that the license implies this.

There is a formal problem acknowledging copyright of -extend: the "original Author" of the code is not written in the header of the files, and the copyright statement is replaced by a generic "Copyright retained by the original Author". In other words, you don't know who owns that copyright, since "original Author" could be anybody, and "-extend" is not an entity (company, person, ...).

Best,

[wouter]

Originally Posted by arjun

I hope you are right.

But the reason I asked that is that long time ago Hrv posted something that got stuck in my head. May be I got wrong impression because of that. I had hard time finding that post but i finally found it.

http://www.cfd-online.com/Forums/ope...-openfoam.html

Here is his post:




From this post, I got the impression that Hrv wanted GGI to be part of extnd project only. This is why I asked the question that what happens to features that are NOT part of openfoam of openCFD.

How this whole thing going to go further.

The way I read this is that Hrv wanted his functionality in OpenCFD OpenFoam, but OpenCFD and Icon wanted sponsering from costumers to add Hrv's functionality in their OpenFoam.

[santiagomarquezd]

About contributions, Bruno Santos posted this in LinkedIn:

http://www.openfoam.com/mantisbt/view.php?id=276

It has an answer form H.

Rregards

[wyldckat]

Greetings to all,

Originally Posted by santiagomarquezd

About contributions, Bruno Santos posted this in LinkedIn:

http://www.openfoam.com/mantisbt/view.php?id=276

It has an answer form H.

Yeah, I forgot to post that link here in the forum... sorry about that. To complement the history line, I made the bug report a while after the post #4 here on this thread:

Originally Posted by wyldckat

But this paragraph sort-of hits a nerve on the news release:

As most news reports around the world, it lacks specific information... such as: "make their own contributions" to where and/or to whom?
Oh well, same old, same old This is what the Internet is for I can only assume that GitHub's social coding is what they had in mind...

I guess I jumped the gun in light of the news, but after all of the previous issues around the trademark and copyright... that seriously looked like a bug to me Oh well... being awake at 2am can sometimes be as dangerous as alcohol

Best regards,
Bruno

[Canesin]

Hi all,

Just to drop some lines of my views here.. that maybe bring some new intel.

Since 2009 SGI is not the same SGI as it was, the middle of 2009 SGI has meet the bankruptcy and acquisition by Rackable Systems.. SGI was going to be removed from NASDAQ as it has not the minimum requirements anymore for having stock trading.

For more read: http://www.vizworld.com/tag/sgi-bts/

SGI has been bought by U$45M and nas now the market value of U$479.84M.
You all know who is almost down ?? CRAY, it has now a market capital of only U$188.64M .. my opinion ?? Supermicro or SGI should buy CRAY the faster they can, before HP or IBM do so.

Back to OpenFOAM case ... Rackable System them changed it own name to SGI and started to look to correlated business to add to their portfolio.. So if OpenCFD has the same fate of COPAN it is going to have it mark diluted in SGI .. but the product has evolved and is now one strong sell for them. So we OpenFOAM user can hope that from the new SGI corporate culture that OF is going to have it's team expanded, the product will remain open and the most important thing.. it will receive marketing force.. not now, they are going to make it more commercial looking now.. but in some months wait to see OpenFOAM banners here in the forum.

[alberto]

http://investors.sgi.com/releasedeta...leaseID=600055

[elvis]

Hi all
=>This move changes the shape of the CFD market by offering an open CFD platform and a complete solution - hardware and software designed to work together.

This looks like a vendor lock in.
You can get a "minimalistic" Openfoam-version for those machines like the Cray XE6, .... Or a SGI-OF.

[akidess]

Originally Posted by elvis

Hi all
=>This move changes the shape of the CFD market by offering an open CFD platform and a complete solution - hardware and software designed to work together.

This looks like a vendor lock in.
You can get a "minimalistic" Openfoam-version for those machines like the Cray XE6, .... Or a SGI-OF.

Imagine you have an SGi computing cluster with OpenFOAM, and a couple years later you decide to replace your cluster with a Cray - nothing stops you from taking the OpenFOAM you have and running it on your Cray. Ergo, no vendor lockin.

Also, we are in the comfortable position that we already have a great working alternative - OpenFoam extend.

[Linse]

It seems because of the change of the github from OpenCFD to OpenFOAM also the update via "git pull" fails. At least for my case it showed merge problems.

The former page of OpenFOAM and the instructions for a git-download are not yet updated, it seems.

At the moment I am rebuilding, but I guess afterwards it will be fine again. I'll keep you posted, but you better keep in mind: If you do a "git pull", at the moment it might cause more time demand than a simple update before...


Update:
A complete new install seems to solve the problem and the system seems to be working again.

[wyldckat]

They're still doing the transition... but here's what's on the GitHub page of the old repo: https://github.com/OpenCFD/OpenFOAM-2.0.x

OpenFOAM README for version 2.0.x
OpenFOAM is now released by the OpenFOAM Foundation

On the 8th of August 2011 the copyright of OpenFOAM was transferred from and by OpenCFD Ltd. to the newly formed OpenFOAM Foundation. The new location for the OpenFOAM-2.0.x repository is http://github.com/OpenFOAM/OpenFOAM-2.0.x
Download and installation instructions

* To install from the OpenFOAM Foundation Git repository, see http://www.OpenFOAM.org/git.php
* If you wish to upgrade your existing OpenFOAM-2.0.x repository to the new version from the OpenFOAM Foundation, in the file
o

OpenFOAM-2.0.x/.git/config

o change
o

url = git://github.com/OpenCFD/OpenFOAM-2.0.x.git

o to
o

url = git://github.com/OpenFOAM/OpenFOAM-2.0.x.git

o and then
o

git pull

My guess is that most of the team is still in either on vacation or in training at SGI.

[alberto]

I am a bit surprised that all these doubts come out at this point, when a foundation is created to manage the code as a FOSS project. I often criticised OpenCFD for not accepting contribution, however I have to say they provided an excellent service to us, maintaining the code, fixing bugs in real time, and keeping procedures simple. Maybe they deserve some credit, and it is time to stop thinking to the worst. Spreading FUD does not help anybody, and at the moment there is no element to consider the acquisition negatively.

[Linse]

Just tried and I can verify: If one changes the .git/config before one tries to do the "git pull" everything seems to work as usual. Just running the ./Allwmake at the moment...

@Alberto: I guess it simply is the fear of the unknown. We simply will have to see what comes next. And actually I am quite sure the people at SGi will not be as stupid as to kill a really good working horse.
OpenFOAM might not bring in any license fees. But I am sure the courses/support and the custom-made ports are a real cash-cow if they are marketed well. Which works only if OF is well-spread due to its free nature.