world leader in high performance signal processing
Trace:

Differences

This shows you the differences between two versions of the page.

a_basic_introduction [2006/12/08 01:02]
vapier
a_basic_introduction [2007/01/10 22:40] (current)
vapier update links and such
Line 1: Line 1:
-====What is GForge?====+====== A Basic Introduction ====== 
 + 
 +===== What is GForge? =====
 GForge was developed by the Open Source community as an environment in which to host projects in a way that the code, documentation, binaries etc. were publicly accessible to all who wished to see them. Members of the community could use the software that was developed, and contribute feedback, bugs, ideas, suggestions, and even help to develop code/modules/documentation/resources for the software. GForge was developed by the Open Source community as an environment in which to host projects in a way that the code, documentation, binaries etc. were publicly accessible to all who wished to see them. Members of the community could use the software that was developed, and contribute feedback, bugs, ideas, suggestions, and even help to develop code/modules/documentation/resources for the software.
  
-Traditionally GForge has been utilized for software projects, although on [[http://blackfin.uclinux.org|blackfin.uclinux.org]] it is also being used to develop hardware projects.+Traditionally GForge has been utilized for software projects, although on [[bf>|blackfin.uclinux.org]] it is also being used to develop hardware projects.
  
 Generally, everyone has read access to the data associated with a project, with (some of) the developers having write access to the data. Usually there is a maintainer of the code (the project leader or the person who registered the project) and contributors who email any changes to the code that they developed - bug fixes, additional functionality to - which the maintainer may then add to the code in the CVS tree upon verification that it was correct/clean/maintainable/useful. Generally, everyone has read access to the data associated with a project, with (some of) the developers having write access to the data. Usually there is a maintainer of the code (the project leader or the person who registered the project) and contributors who email any changes to the code that they developed - bug fixes, additional functionality to - which the maintainer may then add to the code in the CVS tree upon verification that it was correct/clean/maintainable/useful.
  
  
-====What can blackfin.uclinux.org do for me?==== +===== What can blackfin.uclinux.org do for me? ===== 
-[[http://blackfin.uclinux.org|blackfin.uclinux.org]] can provide a centralized access point for several useful utilities and tools that could be used in a project. Some of these tools include: +[[bf>|blackfin.uclinux.org]] can provide a centralized access point for several useful utilities and tools that could be used in a project. Some of these tools include: 
   *  A Website for every project    *  A Website for every project 
   *  Versioning control via CVS    *  Versioning control via CVS 
Line 21: Line 23:
     *  //File uploads/releases //     *  //File uploads/releases //
     *  //Posting of news//** **- Every project can have its own news items.      *  //Posting of news//** **- Every project can have its own news items. 
-    *  //Code Snippets//** **- Provides a basic knowledgebase that can contain code fragments, HOWTOs, etc.+    *  //Code Snippets//** **- Provides a basic knowledge base that can contain code fragments, HOWTOs, etc.
  
 The tasks and the tracker items (to track bugs, patches, support requests, enhancement requests) can be classified using status, priority or category. The system also provides a classification system of the projects, a user profile, and a user rating system. The tasks and the tracker items (to track bugs, patches, support requests, enhancement requests) can be classified using status, priority or category. The system also provides a classification system of the projects, a user profile, and a user rating system.
  
-The tools provided on [[http://blackfin.uclinux.org|blackfin.uclinux.org]] allow team members to communicate and organize their work; creating a knowledgebase of activity for all to see.+The tools provided on [[bf>|blackfin.uclinux.org]] allow team members to communicate and organize their work; creating a knowledge base of activity for all to see.
  
  
-====GForge History====+===== GForge History =====
 GForge is a fork of the 2.61 SourceForge code, which was only available via anonymous CVS from VA (Research\|Linux\|Software). [[http://gforge.org|gforge.org]] is not a project hosting platform, it is merely an implementation of the GForge code. The creators of GForge believe that the functionality is important not only to the Open Source community, but to the wider business community. Since VA has not released the source in over one year, despite their promises to the contrary, a fork was necessary to ensure a viable open source version of the codebase. The GForge project was formed and is maintained by Tim Perdue - the original author of much of the original SourceForge web code. Major changes are present in the current GForge codebase: GForge is a fork of the 2.61 SourceForge code, which was only available via anonymous CVS from VA (Research\|Linux\|Software). [[http://gforge.org|gforge.org]] is not a project hosting platform, it is merely an implementation of the GForge code. The creators of GForge believe that the functionality is important not only to the Open Source community, but to the wider business community. Since VA has not released the source in over one year, despite their promises to the contrary, a fork was necessary to ensure a viable open source version of the codebase. The GForge project was formed and is maintained by Tim Perdue - the original author of much of the original SourceForge web code. Major changes are present in the current GForge codebase:
   *  Jabber Support - System events, such as bug submissions, are optionally sent via jabber and email    *  Jabber Support - System events, such as bug submissions, are optionally sent via jabber and email 
Line 36: Line 38:
   *  Foundries and related nonsense have been removed   *  Foundries and related nonsense have been removed
  
-====blackfin.uclinux.org History==== +===== blackfin.uclinux.org History ===== 
-The [[http://blackfin.uclinux.org|blackfin.uclinux.org]] website was started by a group of volunteers in January 2004 as a place to help facilitate open source development around the Blackfin processor from Analog Devices.+ 
 +The [[bf>|blackfin.uclinux.org]] website was started by a group of volunteers in January 2004 as a place to help facilitate open source development around the Blackfin processor from Analog Devices.
  
  
-====This Manual==== +===== This Manual ===== 
-This manual explains how to use the [[http://blackfin.uclinux.org|blackfin.uclinux.org]] website. The manual is divided into five parts: +This manual explains how to use the [[bf>|blackfin.uclinux.org]] website. The manual is divided into five parts: 
   -  [[Getting Started]]    -  [[Getting Started]] 
   -  [[User Specific Functions]]    -  [[User Specific Functions]]