Some guidelines we have identified in an intra college discussion to evaluate the projects were:
- We could be looking at precisely the "contribution" and its worth in the contemporary scenario (relevance and significance).
- We could also be looking at *ability to communicate* with development team, whose members are scattered - for which proof has to be produced (that will inspire other students, if the dialogues are simple)
- We could look at *tools* and/or modified tools that were used for the work
- We could also look at the fact whether the work is available in GPL (we are rewarding Free Software - not restricted/proprietary applications developed using Free Software).
- Identify possible domains(broadly applications and system level) and classify projects to make evaluation easier and better.
The work now in pending is this
- Publishing of a potential list of tools or softwares which are available open (or identify the FOSS tools).
A list of possible tools can be of a variety of types,
- Operating Systems
- GNU/Linux
- GNU/Hurd
- ReactOS
- Integrated Development Environments
- Anjutha IDE for C/C++ development
- Eclipse for Java
- K Develop
- Quanta Web Development Environment
- Database Servers
- MySQL Database sever
- PostgreSQL
- Web Servers
- Apache
- Support tools(CASE tools)
- DIA
- Umbrello UML modeller
- cvs,svn(version control systems)
- Operating Systems
(subject to discussion)
- Then call for registering the projects with the staffs or students in charge.
- Before doing this we have to prepare a detail of what should be there in the student applications (What all he/she have to specify).