Note: Currently new registrations are closed, if you want an account Contact us

Difference between revisions of "FOSS project identification and indexing"

From FSCI Wiki
(New page: Some guidelines we have identified in a intra college discussion to evaluate the projets were #. We could be looking at precisely the "contribution" and its worth in the contemporary scen...)
 
(mailing list added)
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Some guidelines we have identified in a intra college discussion to evaluate the projets were
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 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 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 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).
# 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.
# Identify possible domains(broadly applications and system level) and classify projects to make evaluation easier and better.


the work now in pending is this
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).
# Publishing of a potential list of tools or softwares which are available open (or identify the FOSS tools).
#. Then call for registering the projects with the staffs or students in charge.
A list of possible tools can be of a variety of types,
#. 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).
##Operating Systems
##Programming Platforms
##Integrated Development Environments
##Database Servers
##Web Servers
##Programming Languages
##Support tools(CASE tools)
(add or delete if you wish)
# 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).


please all of you join us and help us in this task
* '''[http://groups.google.com/group/fci-education-discuss Discuss]'''

Revision as of 16:59, 30 June 2007

Some guidelines we have identified in an intra college discussion to evaluate the projects were:

  1. We could be looking at precisely the "contribution" and its worth in the contemporary scenario (relevance and significance).
  2. 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)
  3. We could look at *tools* and/or modified tools that were used for the work
  4. 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).
  5. Identify possible domains(broadly applications and system level) and classify projects to make evaluation easier and better.

The work now in pending is this

  1. 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,

    1. Operating Systems
    2. Programming Platforms
    3. Integrated Development Environments
    4. Database Servers
    5. Web Servers
    6. Programming Languages
    7. Support tools(CASE tools)

(add or delete if you wish)

  1. Then call for registering the projects with the staffs or students in charge.
  2. 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).
Retrieved from "https://wiki.fsci.in/index.php?title=FOSS_project_identification_and_indexing&oldid=3213"