There’s nothing that humbles you quite like when you see people build on your work. Although a week hasn’t gone by since we introduced the Bespin project to the wider community, we have already seen contributions that have gone beyond our expectations.
Boris Bokowski, of the Eclipse community says it best:
Within a few days, 30,000 people logged into their public server, 400 people joined their discussion group, about 50 bugs were filed, several of them with patches, and many articles, blogs and even a Wikipedia entry were written.
We wanted to highlight Boris himself. Along with Simon Kaegi, he managed to accomplish something we think is very cool indeed, and all in a couple of days. He took Eclipse and paired it with Bespin. What does that mean? He took a headless Eclipse, implemented the Bespin Server API and went above and beyond the API to get data from Eclipse back to Bespin.
Take a look at the integration in action:
Here Eclipse is sending back errors and warnings about the Java source file being edited. This is great news for Java fans and beyond (as Eclipse supports many languages and platforms these days).
Then we have Jerome Velociter who kindly spent his Saturday integrating Bespin with the open source XWiki project. He added an “Edit with Bespin” button on Wiki pages, and then when you are done and save, it goes back to XWiki.
Both the XWiki and Eclipse work is exactly the kind of thing we were hoping for with the Bespin project. Having just enough code out there for us all to collaborate, but not too much of a formed product that has anything set in stone.
We also want to thank the other contributors that have been hanging out on irc, emailing the newsgroup, filing bugs and ideas, and of course contributing code.
We have been hard at work getting more and more information out there, from roadmaps to known issues to help on how to contribute code. We don’t just want the coding to be done in the open. We want the entire discussion to be open, and this will of course include design decisions, so expect to see design documents on the Wiki as key features come up in the community. The goal is for this project to be your editor.
— Dion Almaer, on behalf of the Bespin development team
Darren
wrote on
:
Luca Mauri
wrote on
:
Oscar Carballal
wrote on
:
Tristan
wrote on
: