Highlight codebox jcink how to#
Highlight codebox jcink portable#
Highlight codebox jcink code#
Highlight codebox jcink license#
Highlight codebox jcink professional#

This complexity is useful for situations where you want workspaces to be portable from computer to computer, or where you want developers to avoid having to setup additional tools on their localhost system. Che and CodeBox both have an IDE client, but Che also has a lot of technology around defining workspaces, establishing the runtimes within, and then dealing with project types.

Where CodeBox was strong as the IDE client, Che was going to focus on the workspace. We had to bumble and stumble around with a couple of really bad releases before we centered in on what we felt was the important abstraction - a developer workspace. Aaron and Samy had other ambitions, and Codenvy had a bit of a different orientation, so the puzzle pieces didn't fit at the time.Įclipse Che was heavily influenced by Codebox. This was before Eclipse Che existed as an open source initiated and CodeBox was doing quite well. There was a point about 4 years ago where we had considered merging projects. The acquirers (stewards) of the project had made numerous public commitments to maintenance of the project, and they did not follow through on those commitments. I agree with Aaron that it is a bit sad to see Codebox go unmaintained.

Highlight codebox jcink professional#

Building a world-class IDE, business and open-source project, requires a champion/leader, is a good leader, Codebox currently has no leader or champion which hinders it's success moving - Aaron and Samy are a lot nicer and professional than they need to be. I like his approach of focusing on the enterprise use case whilst also building a sustainable open-source project (I would like to believe Codebox somewhat helped sway them in that direction). I have great respect for him, he's smart, pragmatic and his involvement in the Codebox threads shows that he cares. Samy and I actually considered partnering up with a long time ago (pre-Codebox).

Highlight codebox jcink how to#

I would actively recommend you take a look at them and figure out how to combine your efforts. Codenvy / Eclispe Che lead by Cloud 9 (acquired by Amazon / AWS)īoth projects are well maintained and actively developed by commercial entities.Given the current status and lack of lead or sponsor of the project, I would recommend two alternatives: However since it's open-sourced under the fairly liberal Apache 2.0 license, you should be able to safely fork it. The company that acquired Codebox had originally promised to maintain and develop Codebox, but hasn't really followed through.Īs pointed out, transferring ownership would be complicated, and I can not help out, since we no longer legally own the IP.

Codebox was sold ~2 years ago, because Samy and I wanted to focus on GitBook.

Highlight codebox jcink license#

We intend to maintain the current source, license for the parts that we are incorporate and continue to publish the fork under the same license Apache and I (the original Codebox authors), no longer own the open and closed source IP related to Codebox. We would also like to applaud the team who created this awesome project and appreciate you releasing it under a liberal Apache 2.0 license.

However, if we are not able to contribute/make changes, we have no option than going ahead with the fork. If the maintainers/authors of codebox, would like us to continue maintaining this project, we would like to start contributing to the same project without forking it. We, hereby would like to convey the intent to fork this project. After going through the commit history, long pending pull requests, and dormant status of this project, we have come to a conclusion that we may have to fork this project. Prior to this, we would have to rely on multiple VMs, which would turn out to be expensive on resources, and in many cases, would not work on a personal laptop.Įven though, the basic features are great, we need to start adding new features, making changes to suit our multi node environment. We are using codebox along with docker to build/simulate multi node cluster running inside a single VM.

Highlight codebox jcink code#

What we love about it is in addition to the IDE, it also comes with a terminal built in, unlike a lot of other alternatives.Īt School of Devops, we conduct trainings for ops folks, who need to write automation code and deploy to a cluster of nodes. Codebox is such a amazing product, that even if this has no recent updates, it still continues to work well with the base features.