Twitter github

Posts Tagged with “eclipse”

2018 Eclipse Simultaneous Release Name: Photon

Hey Eclipse friends, as part of my duties on the Eclipse Planning Council, we have worked with the Eclipse Foundation EMO and wider community to finalize the Oxygen+1 simultaneous release name (see bug 510201 for details): Photon

Thanks to everyone who voted in the community!

@EclipseFdn Neon+1 Name: Oxygen

Oxygen (a pretty important element for life) is now the name of the Eclipse Foundation Neon+1 release:

oxygen

See bug 485861 for more details.

Git Ketch multi master replication in JGit

Google is contributing a new a new multi-master implementation to JGit called Git Ketch (based on the Raft consesnus algorithm).

More information is on the JGit mailing list and on Gerrit if you’re interested in this important feature.

@EclipseFdn Neon+1 Name

The vote for the Eclipse Foundation’s Neon+1 name is over (see bug 485861):

  1. Oxygen (Condorcet winner: wins contests with all other choices)
  2. Odyssey loses to Oxygen by 121–112
  3. Osiris loses to Oxygen by 141–94, loses to Odyssey by 131–97
  4. Opal loses to Oxygen by 136–95, loses to Osiris by 112–109
  5. Oberon loses to Oxygen by 143–98, loses to Opal by 115–110
  6. Orpheus loses to Oxygen by 142–90, loses to Oberon by 121–99
  7. Ozone loses to Oxygen by 152–61, loses to Orpheus by 111–103
  8. Ohm loses to Oxygen by 152–69, loses to Ozone by 103–99
  9. Oceana loses to Oxygen by 161–54, loses to Ohm by 103–94
  10. Oort loses to Oxygen by 158–63, loses to Oceana by 116–78

Screen Shot 2016-01-14 at 9.37.03 AM Pending legal approval, Eclipse Oxygen will be the name for Neon+1

Eclipse Code of Conduct

At the recent Eclipse Foundation board meeting this week in Toulouse as part of EclipseCon France, the committer representatives helped move forward a code of conduct for the Eclipse community. As for a bit of background, the request for this initially came from bugzilla and also the LocationTech working group which was looking for a code of conduct for its community. The board opted for a simple code of conduct based on the Contributor Convenant, see this email from Mike Milinkovich:

I am very pleased to announce that the Eclipse Foundation Board of Directors approved a Community Code of Conduct[1] at their meeting earlier this week at EclipseCon France. This brings the Eclipse community in line with the best practices for open source communities around the world.

Our community already has a strong culture of respect and professionalism. Neither I nor the Board expect anyone’s behaviour to change as a result of this. This is simply codifying the high expectations we already meet in terms of professionalism, respect, and simply courtesy.

I agree with Mike and couldn’t have said it better, we have a great community and this simply codifies our high expectations.

SourceForge Hijacking Open Source Project Downloads

Today I read about how SourceForge is hijacking nmap downloads through their old SourceForge account…

This is just plain naughty behavior in open source land… SourceForge has previously done this with the GIMP project and inserted adware into the download. They even created a response page based on the criticism from that incident stating that:

This is a 100% opt-in program for the developer, and we want to reassure you that we will NEVER bundle offers with any project without the developers consent.

Outside of this just being dubious behavior, this looks to be a lie based on what the  nmap developers have stated. Also, what is concerning is that who knows what other open source projects SourceForge is trying to do this for.

This should be a lesson and even a wake up call to open source projects who use external services like SourceForge… there’s inherent risk if the tide of the business you depend on changes.

Furthermore, this is another reason hosting your project at a quality open source foundation can be beneficial as they generally won’t do these type of shenanigans as they protect your projects best interests. These open source foundations can also help you secure a trademark for your project which can help fight against these types of issues.

Stay diligent!

UPDATE: A response from SourceForge

Malicious Open Source Contributions

Yesterday, an interesting happened within the Eclipse Foundation community where someone sent a malicious code review

We generally don’t see this type of thing in open source communities (mostly just contributions without tests), but I believe malicious contributions will continue and become more frequent. The opportunity is just there for bad actors and open source code is embedded all over the place, from your desktop, to your mobile devices to vehicles.

Looking back, there’s been some notable opportunities for bad actors to inject malicious code. One example I recall in particular is RubyGems and SSL and another more prominent example was when the Kernel.org servers were hacked:

Good times, stay diligent.

Naming Mars+1 (2016 @EclipseFdn Release)

It’s that time of year that members of the Eclipse Foundation Planning Council help spearhead the community-based naming process of the next Eclipse release (slated for 2016).

The rules are contained in this bug where you can submit names for consideration. Here are the guidelines for names:

The rules and procedure for naming Mars+1 will be similar to what has happened in the past. The name should be alphabetically greater than “M”

Preference will be given to “N” names, but no strict rule that others would not be considered. Preference given to names that fit the “moon”, “heavenly body gods”, or “scientists” themes we’ve had in the past.

I’m suggested Nova or Neutrino to start, but have taken a liking to Neptune as a potential option:

NeptuneHave a better suggestion for a name? Well put it in the bug before we call for an official vote in the coming weeks.

Thank you!

 

Eclipse Luna+1 Name: Mars

After some legal issues with the initial name, the name of the Luna+1 release will be called Mars.

eclipsemars

Mars is a fine name and also great planet. Thank you to everyone who voted and participated in the process. We at the Eclipse Planning Council appreciate your patience.

Comments Closed

10 Years of the @EclipseFdn and the Board Election

There’s been a couple of interesting milestones recently at the Eclipse Foundation. A few weeks ago, the Eclipse Foundation celebrated its 10th anniversary and even refreshed its logo. The most interesting part of the anniversary is that Eclipse is more than just a community around an extensible IDE, it’s a place to foster open industry collaboration to develop new open platforms. There are now Working Groups that span industries from automative, to location area technologies to the internet of things.

Eclipse Working Groups

It’s also great to see Benjamin Cabé join the Eclipse Foundation to grow interest around the iot.eclipse.org technology stack. At the board, I wanted to see the Eclipse Foundation hire another evangelist for many years now, it’s nice to see that finally happen!

Also, related to that, it’s Eclipse Board election time! I have the honor to run again along with a set of great candidates.

vote-1

You can read my position statement and reach out to me over email or via @cra at anytime if you have questions. I’m proud of what we have accomplished over the last few years and would be honored to continue to represent committers.

If you haven’t received an email with the subject “Eclipse Board Elections 2014” and you’re a eclipse.org committer, reach out to EMO@eclipse.org to ensure you have voting privileges. We could always use a greater turn out of committers voting, it takes no more than a few minutes to do and you have a chance to influence the direction of the Eclipse Foundation.

Happy voting!