|
|
| (28 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | Leveraging collective intelligence for software development (as described [http://code-recommenders.blogspot.com/2010/08/eclipse-and-academia-briding-gap.html here]) has huge potential to revolutionize the way how we interact and work with our IDEs today. Furthermore, leveraging the wisdom of the software engineering crowds can happen in many different ways. Hence, code recommenders is seeking for contributors in many different areas ranging from test engineers to Plug-in developers, JDT experts, up to usability experts providing feedback about issues that kill the code recommenders experience. Below you find a short description of contributions we highly appreciate.
| |
| | | | |
| − | = JDT Experts =
| |
| − | Code Recommenders consists of two major parts: (i) a code analysis engine and (ii) a set of Eclipse RCP plug-ins that extend the Eclipse Platform and Eclipse JDT in particular. Especially code recommenders' code completion plug-ins heavily use JDT and JDT internal APIs. To improve Code Recommenders' code completion engines in terms of performance and functionality we are seeking JDT experts or those that want to become JDT experts.
| |
| − |
| |
| − | = Plug-in Developers =
| |
| − | Around code completion, code recommenders provides several UI features like views, editor extensions etc. that rely on standard Eclipse RCP extension points. To improve usability of these parts we are seeking RCP plug-in developers that take responsibility on things like user customization, views, and the '''crowd-sourced usage data collector'''.
| |
| − |
| |
| − | = WALA Code Analysis Experts =
| |
| − | This topic is probably the one with the smallest target audience :-) For our code analysis we use the [wala.sourceforge.net IBM WALA byte code toolkit] which is an excellent toolkit for analyzing code. It comes with a interprocedural control-flow graphs, abstract interpretation capabilities, fix point iteration etc. Code Recommenders aims to continuously improve its analysis in terms of precision and (especially) performance. If you are familiar with WALA - or want to learn about it - we welcome your contributions!
| |
| − |
| |
| − | = Tool Leads =
| |
| − | Code Recommenders is not just a set of code completion engines. It's rather a set of tools ranging from code completion to code search, from bug detection to stacktrace search engines, and crowd-sourced code snippets to extended Javadocs. A plenty of opportunities to take a lead on. Checkout the [[Recommenders/Proposal]] for a brief summary of the planned tools and contact us on the dev mailing list.
| |
| − |
| |
| − | = Test Engineers =
| |
| − | Code Recommenders aims to continuously deliver its software. This requires a high quality test suite. However, building great test suites needs excellent test engineers! If you are an experienced test engineer, and would like to support us in creating a continuous delivery platform for Code Recommenders contact us on the dev mailing list. We are currently building on Hudson and start out building automated test suites for Eclipse RCP plug-ins and analysis engines as well.
| |
| − |
| |
| − | = Usability Experts =
| |
| − | Actually, every user is a usability expert in its own right but only few of us take the time to provide usability feedbacks and to tell the development team what kills the user experience. Thus, code recommenders seeks users that aim to provide usability feedback and unsparing critiques of the tools. Without this feedback the development teams wastes time and efforts in directions that may turn out as complete mistakes in development. The earlier the team gets feedback and help in prioritizing things the better and faster code recommenders can grow. Thus, we need your support. A perfect forum for these kinds of contributions is the [http://eclipse.org/forums/eclipse.recommenders/ forum].
| |
| − |
| |
| − | = Documentation Writers and Reviewers =
| |
| − | Granted, it looks like an escape when a development team is searching for documentation writers. However, one of the hardest challenges in writing documentation is matching your audience. Technical writers are trained for this and thus we would greatly appreciate your help on user and developer documentation. If you think documentation is unclear and needs refinement, please point out this issue and report them to the [http://eclipse.org/forums/eclipse.recommenders/ forum]. Also, user and developer documentation is hosted in this wiki which allows to improve it quite easily. We encourage you to jump in and improve code recommenders' documentation.
| |
| − |
| |
| − | = Something left over? =
| |
| − | This list is neither exhaustive nor has any particular order. If you would like to share your thoughts or even want to contribute your tool just contact us on the [http://eclipse.org/forums/eclipse.recommenders/ forum].
| |
| − |
| |
| − | [[Category:Recommenders]]
| |
