Community Edition

[wcmatthysen]

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.

[caller]

Thx Patrick, So we should still go full speed ahead on the java and android side with our community approach. 😊

[PJHogan]

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.' Thanks for your contribution of this wonderful gift to the world!

[wcmatthysen]

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 (@emxsys).

Please feel free join in and contribute. We need all the help we can get to make this a success.

[quonn77]

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 (@emxsys 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 https://github.com/NASAWorldWind/WorldWindJava/issues/81#issuecomment-480611293, or mute the thread https://github.com/notifications/unsubscribe-auth/AJYth6HYUaKtKushP0UEXc0kAMJ81eixks5veidwgaJpZM4Ldu1G .

[wcmatthysen]

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.

[Beak-man]

Hello all, Fortunately, WorldWind has received renewed commitment from NASA for continued development and support. More information in the project's website: https://worldwind.arc.nasa.gov/news/2019-08-21-project-update/

[wcmatthysen]

@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:

It's also worth noting that NASA World Wind is an open source project, but is closed development. Our NASA administrator can provide more insight into this if you'd like. We accept pull requests sparingly.

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?

[Beak-man]

@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.

[PJHogan]

Let's allow the FUTURE tohappen! Get this planet onto one page for spatial data! Come on NASA and community! Please find a way to get it together 'for the benefit of all.'

[wcmatthysen]

@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.

[PJHogan]

@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.

[markpet49]

@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.

[markpet49]

@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.

[DJViking]

NASA WorldWind just got new releases for Java and Web.

Web WorldWind 0.10.0 and WorldWind Java 2.2.0 are now available on GitHub. The new version of Web WorldWind addresses potential vulnerabilities in the code and underlying packages. The new version of WorldWind Java focuses on upgrading to Java 11 and JOGL 2.4 as well as a switch to Apache 2.0 license. WorldWind’s API remains largely unchanged in this release and we are committed to maintaining a consistent API in future releases. More information on the release can be found at these links: Web WorldWind 0.10.0 and WorldWind Java 2.2.0.

Please direct questions to our new email address: arc-worldwind@mail.nasa.gov.

The news article on the shutdown seems to have been removed https://worldwind.arc.nasa.gov/news/...ension-notice/

Instead there is now an news article that says NASA has recommitted to WorldWind https://worldwind.arc.nasa.gov/news/...roject-update/

Does not look like the community fork is needed.