📄 a_basic_introduction.html
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head> <title></title> <link rel="stylesheet" media="screen" type="text/css" href="./style.css" /> <link rel="stylesheet" media="screen" type="text/css" href="./design.css" /> <link rel="stylesheet" media="print" type="text/css" href="./print.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><a href=start.html>start</a></br><div class="toc"><div class="tocheader toctoggle" id="toc__header">Table of Contents</div><div id="toc__inside"><ul class="toc"><li class="clear"><ul class="toc"><li class="clear"><ul class="toc"><li class="level3"><div class="li"><span class="li"><a href="#what_is_gforge" class="toc">What is GForge?</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#what_can_blackfin.uclinux.org_do_for_me" class="toc">What can blackfin.uclinux.org do for me?</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#gforge_history" class="toc">GForge History</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#blackfin.uclinux.org_history" class="toc">blackfin.uclinux.org History</a></span></div></li><li class="level3"><div class="li"><span class="li"><a href="#this_manual" class="toc">This Manual</a></span></div></li></ul></li></ul></li></ul></div></div><h3><a name="what_is_gforge" id="what_is_gforge">What is GForge?</a></h3><div class="level3"><p>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.</p><p>Traditionally GForge has been utilized for software projects, although on <a href="http://blackfin.uclinux.org" class="urlextern" title="http://blackfin.uclinux.org" rel="nofollow">blackfin.uclinux.org</a> it is also being used to develop hardware projects.</p><p>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 <acronym title="Concurrent Versions System">CVS</acronym> tree upon verification that it was correct/clean/maintainable/useful.</p></div><!-- SECTION [1-1092] --><h3><a name="what_can_blackfin.uclinux.org_do_for_me" id="what_can_blackfin.uclinux.org_do_for_me">What can blackfin.uclinux.org do for me?</a></h3><div class="level3"><p><a href="http://blackfin.uclinux.org" class="urlextern" title="http://blackfin.uclinux.org" rel="nofollow">blackfin.uclinux.org</a> can provide a centralized access point for several useful utilities and tools that could be used in a project. Some of these tools include: </p><ul><li class="level1"><div class="li"> A Website for every project </div></li><li class="level1"><div class="li"> Versioning control via <acronym title="Concurrent Versions System">CVS</acronym> </div></li><li class="level1"><div class="li"> Shell access to the server for the developers </div></li><li class="level1"><div class="li"> A website for project coordination and communication between team members: </div><ul><li class="level2"><div class="li"> <em>Discussion Forums</em><strong> </strong>- For discussions between team members </div></li><li class="level2"><div class="li"> <em>Bug tracking</em><strong> </strong>- Allow registration and administration of bugs </div></li><li class="level2"><div class="li"> <em>Support requests, patch submissions, and enhancement requests </em></div></li><li class="level2"><div class="li"> <em>Communication between project members using mailing lists </em></div></li><li class="level2"><div class="li"> <em>Sharing of documentation </em></div></li><li class="level2"><div class="li"> <em>Handling of todo lists, tasks, etc </em></div></li><li class="level2"><div class="li"> <em>File uploads/releases </em></div></li><li class="level2"><div class="li"> <em>Posting of news</em><strong> </strong>- Every project can have its own news items. </div></li><li class="level2"><div class="li"> <em>Code Snippets</em><strong> </strong>- Provides a basic knowledgebase that can contain code fragments, HOWTOs, etc.</div></li></ul></li></ul><p> 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.</p><p>The tools provided on <a href="http://blackfin.uclinux.org" class="urlextern" title="http://blackfin.uclinux.org" rel="nofollow">blackfin.uclinux.org</a> allow team members to communicate and organize their work; creating a knowledgebase of activity for all to see.</p></div><!-- SECTION [1093-2582] --><h3><a name="gforge_history" id="gforge_history">GForge History</a></h3><div class="level3"><p>GForge is a fork of the 2.61 SourceForge code, which was only available via anonymous <acronym title="Concurrent Versions System">CVS</acronym> from VA (Research\|Linux\|Software). <a href="http://gforge.org" class="urlextern" title="http://gforge.org" rel="nofollow">gforge.org</a> 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:</p><ul><li class="level1"><div class="li"> Jabber Support - System events, such as bug submissions, are optionally sent via jabber and email </div></li><li class="level1"><div class="li"> Radically easier to install - By removing SF.net-specific code, like caching and image servers, many install dependencies have been eliminated.</div></li><li class="level1"><div class="li"> New interface - The interface makes it easier to navigate as well as know your present location. </div></li><li class="level1"><div class="li"> Code cleanup - Since GForge does not need to scale to 500,000+ users, many hacks and optimizations have been removed </div></li><li class="level1"><div class="li"> Foundries and related nonsense have been removed</div></li></ul></div><!-- SECTION [2583-3888] --><h3><a name="blackfin.uclinux.org_history" id="blackfin.uclinux.org_history">blackfin.uclinux.org History</a></h3><div class="level3"><p>The <a href="http://blackfin.uclinux.org" class="urlextern" title="http://blackfin.uclinux.org" rel="nofollow">blackfin.uclinux.org</a> 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.</p></div><!-- SECTION [3889-4150] --><h3><a name="this_manual" id="this_manual">This Manual</a></h3><div class="level3"><p>This manual explains how to use the <a href="http://blackfin.uclinux.org" class="urlextern" title="http://blackfin.uclinux.org" rel="nofollow">blackfin.uclinux.org</a> website. The manual is divided into five parts: </p><ol><li class="level1"><div class="li"> <a href="getting_started.html" class="wikilink1" title="getting_started.html">Getting Started</a> </div></li><li class="level1"><div class="li"> <a href="user_specific_functions.html" class="wikilink1" title="user_specific_functions.html">User Specific Functions</a> </div></li><li class="level1"><div class="li"> <a href="project_specific_functions.html" class="wikilink1" title="project_specific_functions.html">Project Specific Functions</a> </div></li><li class="level1"><div class="li"> <a href="site_wide_functions.html" class="wikilink1" title="site_wide_functions.html">Site Wide Functions</a></div></li><li class="level1"><div class="li"> <a href="administering_a_project.html" class="wikilink1" title="administering_a_project.html">Administering a Project</a></div></li></ol></div><!-- SECTION [4151-] --></body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -