Contributors and Advisors
The success of an open source project depends on involvement of a wider community. We are lucky that from early on in the project, we have the support of the following friends, whether in terms of code contribution, design advice, or simply integrating OpenI into their own products or projects.
|Sandeep Giri||sandeep_giri||Project Admin||sandeep_giri at users.sourceforge.net|
|Dinesh Simkhada||simk318||Developer||simk318 at users.sourceforge.net|
|Sujen Maharjan||sujenmaharjan||Developer||sujenmaharjan at users.sourceforge.net|
|Suman Singh||sumansingh||Developer||sumansingh at users.sourceforge.net|
|Maya Thapa||mkhasu||Developer||mkhasu at users.sourceforge.net|
|Prakash Gautam||prakash_gautam||Developer||prakash_gautam at users.sourceforge.net|
|Dipendra Pokhrel||dpokhrel||Developer||dpokhrel at users.sourceforge.net|
|jcarvajal||jcarvajal||Tester||jcarvajal at users.sourceforge.net|
|Jim Porzak||jporzak||Developer||jporzak at users.sourceforge.net|
|paul lucas||paullucas||Developer||paullucas at users.sourceforge.net|
|Pedro Casals||pedrix||Developer||pedrix at users.sourceforge.net|
|Jagan Mohan||pjmohan||Tester||pjmohan at users.sourceforge.net|
|Sherman Wood||sgwood||Developer||sgwood at users.sourceforge.net|
|Uddhab Pant||urpant||Developer||urpant at users.sourceforge.net|
OpenI could not be at this stage of development had it not been for the groundbreaking work done by various open source projects . Here are some key open source projects that have helped us tremendously:
- JPivot: JPivot is a JSP custom tag library that renders an OLAP table and let users perform typical OLAP navigations like slice and dice, drill down and roll up. It uses Mondrian as its OLAP Server. JPivot also supports XMLA data source access.
- Mondrian: Mondrian is an OLAP server written in Java. It enables you to interactively analyze very large datasets stored in SQL databases without writing SQL.
- R Project: R is a free software environment for statistical computing and graphics. It compiles and runs on a wide variety of UNIX platforms, Windows and Mac OS.
- JFreeChart: JFreeChart is a free Java class library for generating charts, including:
- Pie charts (2D and 3D);
- Bar charts (regular and stacked, with an optional 3D effect);
- Line and area charts;
- Scatter plots and bubble charts;
- Time series, high/low/open/close charts and candle stick charts;
- Combination charts;
- Pareto charts;
- Gantt charts;
- Wind plots, meter charts and symbol charts;
- Wafer map charts;
- JasperReports: JasperReports is a powerful open source Java reporting tool that has the ability to deliver rich content onto the screen, to the printer or into PDF, HTML, XLS, CSV and XML files.
OpenI is available under GNU Public License version 2(GPL v2).
The third party libraries and jars utilized by OpenI will be available under their original licenses. We have ensured that we are not using any third party software whose license conflicts with GPL . A complete list of 3rd party licenses is available in a file called “3rd-party-licenses.txt” contained within the OpenI distribution.
Copyright and Community Contribution
This is one of those topics that is not clearly stated in most open source projects, so we are making sure we clearly state our position here.
If you create a new module or a new source code file, the copyright belongs to you, the original author of the source code file. However, in order for us to include that source code file in the OpenI distribution, you must agree to make the source code available under the same GPL terms used by OpenI. Otherwise legally OpenI can’t include your contribution.
For contributions that come in the form of bug fix or patches to existing source code files, the copyright will still be owned by the original author – however, the contributor will be acknowledged in the source code header section as well as in the contributor list maintained at this OpenI web site.
Again, we want to build a community here and a big part of that is giving credit where credit is due. Community contributors don’t get paid to write code. A formal public acknowledgment (and thank you) is the best way we can acknowledge the contributors. And we should also keep our license and copyright policies in alignment with developing a broader sense of community.