Community Edition #81
Comments
|
I agree with you, there is a lot of work that risk to be abandoned. I have improvement for handling HTTP Redirection, drawing ground line for air track, increase detail rendering of 2D maps so it would be nice to have a common shared community fork where all those improvements could be available. If I can help, I am available. |
|
Good, I think we need a lot of people on-board to get the community-edition going. But, first we have to wait for the NASA guys to post the community contribution guidelines (this was mentioned in pull-request #77). The pull-request labels will be needed to determine what pull-requests are fit for the community-fork. In your case, you would probably have to then create pull-requests for the various additions in this repository. If it should go to the community-fork the NASA guys will then mark it with a label "community-edition" (or whatever label is decided) where it will then be picked up by the community-fork owners and merged into that repository. |
|
I believe, as already stated on the pull-request-77 that the community fork needs some members of the board from the NASA Team so we can better coordinate integration of derivative work into stable nwwj product. |
|
@wcmatthysen Thanks for opening a dedicated issue for this discussion. The NASA team is certainly on board with a coordinated community fork. We're very busy at the moment working on sponsored feature deliverables for the Android and Web SDKs, but have this on our Kanban board to address as soon as we can. |
|
@pdavidc Any news? Would love to get started working on this. |
|
Thanks for your patience. We haven't forgotten about this need. It's on our backlog of tasks to address after we finish our current round of sponsor-requested features. |
|
I think a community edition is now more relevant than ever (just my 2 cents). |
|
I agree, it is time to create the community edition of Nasa World Wind.
What is not clear is we are allowed to do this without a prior
authorization by NASA.
Il giorno ven 5 apr 2019 alle ore 10:30 Wiehann Matthysen <
notifications@github.com> ha scritto:
… I think a community edition is now more relevant than ever (just my 2
cents).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJYth0mZEWRCN7WqCRs4NHji29B_bcq6ks5vdwmbgaJpZM4Ldu1G>
.
|
|
We do not need NASA's permission as far as I understand. It is open-source after all. We can just fork it and go our separate ways. It would be great to get their blessing though. |
|
I see there is already an official community fork for WebWorldWind. Maybe we can reach out to @emxsys to host the community edition of WorldWindJava under the WorldWindEarth banner as well. |
|
Sounds good--I somehow totally missed the announcement of the suspension of the WorldWind projects. I'd be happy to lend a hand if there's anything needed to get this initiative off the ground. |
|
perfect. we would be in as well. we have quite some potential contribution, (e.g. javaFX port) but since nasa was too refusive on merging anything, we gave up. |
|
I think we should set up a rough road-map of what we want to accomplish. I would personally like to switch the project's build system over to Maven (or Gradle for that matter) instead of the clunky, archaic way that they have built the project using Ant. I have managed to do that in my own fork of the project, so it can be done with a bit of effort. I think the JavaFX additions would be great seeing as that is where everything is moving towards nowadays. We could probably go through the current pull request list and merge a lot of the useful ones into our own version. Bug-fixes should take priority. We can also focus some effort on modernising the project by introducing some Java 8 features as we go along. I don't know how we can increase the visibility on this issue, seeing as it is quite old. It doesn't show up at the top of the issue-list on the project's GitHub page. We need to get the word out to as many other people that are interested as possible or this is not going to take off. I tried to get the fork going a year or two ago but no-one was really interested. You can see my post here on the forums as well (it never got any real traction). |
|
A community edition with an updated design would be great, count me in for
what is worth.
I think a javafx por would be great. I don't know if a javafx version would
use jogl.
Also maven would be great!
If someone builds it, we will follow :)
Cheers,
Tomas Lund Petersen
El vie., 5 abr. 2019 09:14, Wiehann Matthysen <notifications@github.com>
escribió:
… I think two pull requests that I would already consider a priority is the
JOGL upgrade (see issue #1
<#1>) and the GDAL
upgrade (see issue #146
<#146>).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB_pYAATm6AVFSIWtjxkep1s_xuWHjdeks5vdz4qgaJpZM4Ldu1G>
.
|
Not sure about the JavaFX port either. I know that JavaFX has its own 3D API. I haven't personally worked with it. I am not sure whether work has already been done to port WorldWind to run in JavaFX. But any contributions with respect to that would be a welcome addition to the community edition. I know it can at least be embedded in a SwingNode and displayed in a JavaFX application (but that is different than porting it to JavaFX's 3D API). I think we should just find a proper home for this project. It would probably be best if it lives alongside the other community editions, hence the reason I mentioned Bruce Schubert's (@emxsys) community fork of WebWorldWind. |
|
I also think we should concentrate on providing replacement for the basemap
layers that point to the nasa servers that are going down may 4rth.
Bing aereal, sentinel2, places and roads seems to me te most importants. I
guess elevations would be important to some people also.
Cheers,
Tomas
El vie., 5 abr. 2019 09:33, Tomas Lund Petersen <kotogadekiru@gmail.com>
escribió:
… A community edition with an updated design would be great, count me in for
what is worth.
I think a javafx por would be great. I don't know if a javafx version
would use jogl.
Also maven would be great!
If someone builds it, we will follow :)
Cheers,
Tomas Lund Petersen
El vie., 5 abr. 2019 09:14, Wiehann Matthysen ***@***.***>
escribió:
> I think two pull requests that I would already consider a priority is the
> JOGL upgrade (see issue #1
> <#1>) and the GDAL
> upgrade (see issue #146
> <#146>).
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#81 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AB_pYAATm6AVFSIWtjxkep1s_xuWHjdeks5vdz4qgaJpZM4Ldu1G>
> .
>
|
Yes, I think that is also important. I have a Sentinel2 layer configuration file that I can share to replace the LandSat layer. It connects directly to the EOX::Maps server to get the |
|
Again, all sounds good. Merging in pull request #1, a Gradle build, and alternative base layers would all be great. Not so sure about JavaFX, both because of OpenGL issues, and its exclusion from future JDKs, but I'm not too clued up on that stuff. Might be best to make anything that relies on JavaFX a separate optional module? As for visibility, it might be worth bumping your original thread in the forum, and posting on this one as well: https://forum.worldwindcentral.com/forum/world-wind-community/worldwind-general/158839-worldwind-suspension. Though, once a home for this project has been found then issues/features can be decided upon & tracked there, and that location can be advertised. Probably worth dropping @emxsys an e-mail to get his thoughts, if he hasn't already gotten notifications from being tagged here, and then moving forward from there. |
|
so our JavaFX port works in parallel to the Swing components. so no issue. it also uses openGL. |
|
So is this version available? Id like to give it a try.
Where can i get a hold of it?
Tks,
Tomas
El vie., 5 abr. 2019 10:21, caller <notifications@github.com> escribió:
… #155 <#155>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB_pYEgSSCIEyc3zlZ0If9En71hMESd7ks5vd03LgaJpZM4Ldu1G>
.
|
|
Yes I think that we need to create separated module of the Nasa World Wind SDK, isolating math-projection library, common utility to the core features |
|
So which are the next steps? Some one has get in touch with Bruce Schubert's? |
|
we havent polished our javaFX version jet for release... that might take some weeks in our processes. I might also need mgmt approval. Im working for a quite big company ;-) |
I bumped some threads in the forum. I think Bruce Schubert would probably be notified via GitHub as a result of all the mentions. I'll email him too just in case. |
|
Just getting up to speed on this -- does this fork already exist? I love what you guys are thinking. Having JavaFX capability but also keeping the Swing parts working would be perfect. Some other good (free) WMS layers are available here: https://developer.earthdata.nasa.gov/gibs/gibs-api-for-developers Although it requires updating the WMSTiledImageLayer to capitalize the url query parameters: |
|
And I vote for gradle |
|
A community-driven WorldWindJava, WWJ, fork does not exist to my knowledge.
Except within a few federal agencies carrying it forward for their purposes.
As for the server with the elevation data, there are good efforts already underwayby the WorldWindCentral crew, and Bruce Schubert's WorldWind.Earth activity
https://forum.worldwindcentral.com/
https://worldwind.earth/
https://worldwind.earth/elevation-server.html
https://worldwind.earth/elevation-data.html
https://gist.github.com/emxsys/f8c7a8dd5cf0060387ce50aa3f186bac
https://gist.github.com/emxsys/e3eac29221eec86d1d42525517acb3ad
|
|
Bruce got back to me and mentioned that we can host the Java version of the community-fork on WorldWindEarth (that is: https://github.com/WorldWindEarth). |
|
WoW!
Couldn't have found a better home away from home!
Looking forward to a gorgeous community complex!
|
|
NASA Ames Research Center, where the WorldWind project has been continuously hosted since 2002 had proposed a suspension of the project, but the kick-back from other Federal agencies 'encouraged' a reconsideration. So NASA is back-in-the-saddle with regard to the WorldWind project. The suspension has now been 'suspended' for a month (until May 3), but it will likely stay alive and well ad infinitum. That is not to suggest the community should not take this opportunity to accelerate this technology 'to infinity and beyond!' Controlling our own destiny so to speak, with a community effort at a global scale. This will be beautiful, and show what's possible when working in concert 'for the benefit of all.' |
|
@PJHogan, I agree. I think we should go forward with a community-fork irrespective of the suspension (or the suspension of the suspension). That is, if we can get a community fork going. A community fork could be very fruitful in my opinion in the long run, seeing as there are a lot of developers using WorldWind and benefiting from its continued development (myself included). I also pick up that there are developers that are very willing to contribute code-changes to WorldWind, but the way in which pull-requests and bug-fixes on this project has been managed the last couple of years has been very frustrating to say the least. That is not to say that myself and everyone using WorldWind are very grateful towards NASA and its developers for releasing WorldWind as an open-source project. I just think that going forward, the fork itself should be lead by the community. |
|
Wiehann, of course! |
|
@wcmatthysen I'm ready to move forward. I can create the WorldWindJava fork with issue tracker, and a "WorldWindJava" team within the WorldWindEarth GitHub organization. |
|
For consideration: https://opensource.guide/leadership-and-governance/ |
|
@emxsys Great, let's do it. I would love to help out where I can. I don't know exactly where I'll fit in, but I'd like to contribute some of my code and help with the ongoing maintenance of the code-base. Thanks for the link on the opensource leadership and governance. |
|
Wahoo! |
|
Hi Patrick, Just to clarify: nasa will host tile servers but they will probably stop writing new code. Is that a correct summary? I have seen some NASA ESA collaborations on WW over the years. Do you know the status of the ESA engagement? Thx Marco |
|
Marco, I can only read the tea leaves, but my sense is that NASA got a wake-up call and so will continue to develop WorldWind, particularly the web version, especially given ESA has been coordinating with NASA on that development for a few years now. And the ESA contribution has been HUGE! Unfortunately, the NASA 'official' numbered releases have been quite slow-on-the-draw (branches of the repository have many capabilities waiting for an 'official' release). FORTUNATELY https://worldwind.earth/ incorporates these, along with other 'select' contributions and bug fixes from the community. And I believe the ESA Copernicus Sentinel apps are also pulling from there: So, my reading is that the ESA+NASA joint effort will continue. |
|
Thx Patrick, |
|
Virtual globe technology is essential to so much operational and infrastructure management, as well as Earth status, scientific and other. This open source platform has much to offer the world, not only in terms of support, but also facilitating both the opportunity for innovation and the sharing of solutions. WorldWind is the epitome of an essential software technology 'for the benefit of all.' |
|
Just a heads-up to anyone that comes across this: The community-fork of WorldWindJava has been created at: https://github.com/WorldWindEarth/WorldWindJava Please feel free join in and contribute. We need all the help we can get to make this a success. |
|
Can someone clarify the branch we have to use for daily development, I
suppose it should be develop branch, can you confirm this?
Il giorno dom 7 apr 2019 alle ore 19:14 Wiehann Matthysen <
notifications@github.com> ha scritto:
… Just a heads-up to anyone that comes across this:
The community-fork of WorldWindJava has been created at:
https://github.com/WorldWindEarth/WorldWindJava
thanks to Bruce ***@***.*** <https://github.com/emxsys>).
Please feel free join in and contribute. We need all the help we can get
to make this a success.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJYth6HYUaKtKushP0UEXc0kAMJ81eixks5veidwgaJpZM4Ldu1G>
.
|
|
Yes, as far as I understand the develop branch is the latest unstable branch where development happens. You create a new branch that branches off from the develop branch when developing a new feature (ideally with a short name that describes the feature). Then, when the feature is ready the pull request is merged back into the develop branch. From time to time the develop branch gets merged into master when a stable release is made. |
|
Hello all, |
|
@Beak-man, are the WorldWind developers at least going to try and work with the open-source community this time? Because last time I checked, and if I can quote @pdavidc on this, the policy was:
That didn't really inspire a community to become involved in this project to be frank. But hey, that is just my 2-cents on this. Also, you might have a look at what we did over at the community-edition. We managed to fix a lot of outstanding issues that were never addressed here. Will you actually merge in those changes, or are you going to re-commit the changes as your own like @zglueck did in this pull-request? |
|
@wcmatthysen , officially speaking, the point of contact to address such inquiries can be found here. I'll tell you what I would personally like, though: Setting up the project in a similar way to this one (particularly the part about NASA's CLA) in order to improve our engagement with the open source community, which of course is part of our developer community. I'll bring it up with management and we'll see how it goes from there. |
|
Let's allow the FUTURE tohappen! |
|
@Beak-man, @PJHogan, I'm going to be honest and say that I'm a bit pessimistic about this "renewed commitment" from NASA given the history of how the WorldWind devs managed this repository. I can already see a pull-request with work being done that has already being done by the community to some extent. The JOGL upgrade was done way back in 2016 by @xranby in pull-request #1. If you are sincere with regards to getting a community involved in this project you need to interact with them. You could start by merging some of the outstanding pull-requests that should have been pulled in a long time ago. Those stale pull-requests are just sitting there cluttering up the repository and it gives the impression that contributions are not accepted by the developers of this repository. But, from what I've seen how this repository was managed, it looks like you are going to run this again as an exclusive club where only the WorldWind devs interact with one another. Hopefully I'm wrong and you guys can rebuild a community. I just get the feeling that most of the community have already left and moved on. |
|
@wcmatthysen You are quite accurate in your concern! And thanks dearly for your incredible support over the years. This repository certainly deserves the kind of respect you so accurately describe as lacking. It will be interesting to see if NASA can finally rise to the occasion. |
|
@wcmatthysen Thanks for the feedback. A couple of points. 1. You should raise your concerns to the project management folks, they can be reached via the contact page on the web site. The people who respond to you here don't make the decisions about project direction. 2. We will be reviewing the old PRs as we work on the WWJ code. PR #1 is likely invalid as we're working with the new unreleased JOGL code (last modified on Sept 4 or so.) so as to be Java 11+ compatible. |
|
@wcmatthysen A third point. The NASA version of WorldWind has to be curated in a way that makes certain government agencies comfortable with using the software. That being said, I'm hearing positive noises from project management regarding community engagement. Unfortunately, only time will tell if your pessimism is justified or not. |
|
NASA WorldWind just got new releases for Java and Web.
The news article on the shutdown seems to have been removed Instead there is now an news article that says NASA has recommitted to WorldWind Does not look like the community fork is needed. |
There is a need for a community edition of WorldWind. This will essentially be a community-managed fork that incorporates pull requests not belonging in the stable upstream version, but still being useful enough to the community that it should be maintained and kept up-to-date. See the discussion at pull-request #77 for some background on this.
The text was updated successfully, but these errors were encountered: