| [eclipse.org-members-committers] Upcoming Reviews, April 20-27/2011 |
|
Greetings folks. Three reviews are scheduled for this week. As is their tradition, the EGit and JGit projects have combined their respective 0.12.0 releases [1] into a convenient single review document. EGit and JGit is playing a very important role as we move forward with making Git first-class at Eclipse. One of the key success criteria for Git at Eclipse is the creation of a "quality team provider and tooling for git" [2]. I believe that EGit is well on the way to satisfying that criteria, but we need your assistance (your feedback in particular) to make that happen. The Eclipse SMILA project's 0.8.0 release review [3] is also on the schedule. SMILA is an extensible framework for building search solutions to access unstructured information in the enterprise. Besides providing essential infrastructure components and services, SMILA also delivers ready-to-use add-on components, like connectors to most relevant data sources. We've added some new proposals. The BPMN 2.0 Modeler [4] provides a graphical modeling tool which allows creation and editing of BPMN ( Business Process Modeling Notation ) diagrams. The tool is built on Eclipse Graphiti and uses the BPMN 2.0 EMF meta model currently being developed within the Eclipse Model Development Tools (MDT) project. You've probably heard a lot about Orion over the past couple of months. It's time for Orion to leave the incubator and become a proper Eclipse project. The Orion project's [5] focus is creating components, services, and libraries for building web-based development tools. This includes browser client infrastructure built using widely adopted web technologies such as HTML, _javascript_, and CSS. Also included is server-side infrastructure needed by such development tools. This includes infrastructure supporting file management, search, user management, preferences, generic source control, compare, file history, editors, and user interface widgets and controls required to build development tools. In other news... Git has been gaining significant momentum at eclipse.org. Most of our new projects select Git for their repository, and a great many existing projects have migrated [6] their source code repositories to Git. We recently set up a process by which our Git repositories are automatically mirrored on GitHub [7]. We've done some of the exploratory work required to move our website CVS over to Git [8] as well. The replication of Git repositories to GitHub makes it far easier to get your project code into the hands of others. Having our code automatically mirrored on GitHub is a great way to lower barriers and invite more participation and contribution in a project. To make sure that your Git repositories are mirrored on GitHub, you need to ensure that your Git repositories are specified in your project metadata (via the portal). Providing this information has the added benefit of making your project's Git commit information available in Dash [9]. Thanks, Wayne [1] https://bugs.eclipse.org/bugs/attachment.cgi?id=193590 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=293192 [3] https://bugs.eclipse.org/bugs/attachment.cgi?id=193711 [4] http://eclipse.org/proposals/soa.bpmn2-modeler/ [5] http://eclipse.org/proposals/eclipse.orion/ [6] http://wiki.eclipse.org/Git/Migrating_to_Git [7] https://bugs.eclipse.org/bugs/show_bug.cgi?id=332970 [8] https://bugs.eclipse.org/bugs/show_bug.cgi?id=324116 [9] http://dash.eclipse.org |