[Openfirst-cvscommit] www/htdocs/doc/tut/howto index.php,1.4,1.5 technology.php,1.5,1.6
Brought to you by:
xtimg
From: Tim G. <xt...@us...> - 2005-05-24 22:58:11
|
Update of /cvsroot/openfirst/www/htdocs/doc/tut/howto In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9826 Modified Files: index.php technology.php Log Message: Add mention of the Bugzilla caveat where new versions can render previous templates worthless, add information about Volunteer Profiles, Hackergotchies. Index: technology.php =================================================================== RCS file: /cvsroot/openfirst/www/htdocs/doc/tut/howto/technology.php,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** technology.php 1 Jan 2005 21:19:49 -0000 1.5 --- technology.php 24 May 2005 22:57:48 -0000 1.6 *************** *** 41,45 **** <p>Bugzilla (<a href="http://bugzilla.openfirst.org/">http://bugzilla.openfirst.org/</a>) keeps track of bug reports and feature requests for both source code and documentation. Issues of an administrative nature may also be posted on Bugzilla. As a contributor to the openFIRST project you should register for a Bugzilla account using your @openfirst.org e-mail address. Only e-mail addresses that are @openfirst.org show up in the bug crusher statistics on the openfirst.org site and installations of the openFIRST System. To be credited as having crushed a bug, the bug must be finished (eg marked CLOSED, FIXED, etc.) but not DUPLICATE and the bug must be assigned to you at the time it is closed.</p> ! <p>Automated bug reports are filed by openFIRST installations and are clearly marked as such. You, as one who browses Bugzilla should change the subject of Automated bug reports to better reflect their content and/or mark them as DUPLICATE if applicable. Automated bug reports are reported through <a href="http://bugzilla.openfirst.org/openfirst/">http://bugzilla.openfirst.org/openfirst/</a> and bug crusher statistics are available at <a href="http://bugzilla.openfirst.org/openfirst/bugcrushers.php">http://bugzilla.openfirst.org/openfirst/bugcrushers.php</a>. The style sheet and design information for the Bugzilla site is present within the CVS repository in the <b>htdocs/bugzilla</b> directory of the <b>www</b> module.</p> <h2><a name="updatesystem">openFIRST Update System</a></h2> --- 41,45 ---- <p>Bugzilla (<a href="http://bugzilla.openfirst.org/">http://bugzilla.openfirst.org/</a>) keeps track of bug reports and feature requests for both source code and documentation. Issues of an administrative nature may also be posted on Bugzilla. As a contributor to the openFIRST project you should register for a Bugzilla account using your @openfirst.org e-mail address. Only e-mail addresses that are @openfirst.org show up in the bug crusher statistics on the openfirst.org site and installations of the openFIRST System. To be credited as having crushed a bug, the bug must be finished (eg marked CLOSED, FIXED, etc.) but not DUPLICATE and the bug must be assigned to you at the time it is closed.</p> ! <p>Automated bug reports are filed by openFIRST installations and are clearly marked as such. You, as one who browses Bugzilla should change the subject of Automated bug reports to better reflect their content and/or mark them as DUPLICATE if applicable. Automated bug reports are reported through <a href="http://bugzilla.openfirst.org/openfirst/">http://bugzilla.openfirst.org/openfirst/</a> and bug crusher statistics are available at <a href="http://bugzilla.openfirst.org/openfirst/bugcrushers.php">http://bugzilla.openfirst.org/openfirst/bugcrushers.php</a>. The style sheet and design information for the Bugzilla site is present within the CVS repository in the <b>htdocs/bugzilla</b> directory of the <b>www</b> module. Upgrades to Bugzilla may require remaking these templates in order for the Bugzilla site to function as expected.</p> <h2><a name="updatesystem">openFIRST Update System</a></h2> *************** *** 91,94 **** <p>Important Note: the <b>config</b> module is <b>depreciated</b>. Please use the base module instead. That is to say, <b>don't use the config module</b>. The idea behind the move from <b>config</b> to <b>base</b> is that using <b>base</b> a common index page could be created, and resources such as images that are used throughout the site could be in one place (Release technicians rename base to openfirst when distributing the base package. On the webserver, modules are installed within the root of the base module [eg openfirst/guestbook or base/guestbook]. This is why some modules may <b>appear</b> to use the config module, when in fact they do not). The reason that the <b>config</b> module is still in CVS, is because very old versions of openFIRST used to use it. SourceForge doesn't allow the removal of modules; and even if it did, config is part of the history of the project. <b>config</b> remains in the CVS repository on the off chance that someone running a very old version may want to upgrade/patch their install, in which case the <b>config</b> module provides all of the patches up until the point that it became unsupported (which was after the last official release that made use of the module).</p> ! <p><center><a href="roles.php">Previous</a> | <a href="index.php">Table of Contents</a> | <a href="glossary.php">Next</a></center></p> \ No newline at end of file --- 91,103 ---- <p>Important Note: the <b>config</b> module is <b>depreciated</b>. Please use the base module instead. That is to say, <b>don't use the config module</b>. The idea behind the move from <b>config</b> to <b>base</b> is that using <b>base</b> a common index page could be created, and resources such as images that are used throughout the site could be in one place (Release technicians rename base to openfirst when distributing the base package. On the webserver, modules are installed within the root of the base module [eg openfirst/guestbook or base/guestbook]. This is why some modules may <b>appear</b> to use the config module, when in fact they do not). The reason that the <b>config</b> module is still in CVS, is because very old versions of openFIRST used to use it. SourceForge doesn't allow the removal of modules; and even if it did, config is part of the history of the project. <b>config</b> remains in the CVS repository on the off chance that someone running a very old version may want to upgrade/patch their install, in which case the <b>config</b> module provides all of the patches up until the point that it became unsupported (which was after the last official release that made use of the module).</p> ! ! <h2><a name="profiles">Volunteer Profiles</a></h2> ! <h3>Applies to: All</h3> ! <p>Those wishing to create a <a href="http://www.openfirst.org/developers/">volunteer profile</a> (previously called developer profile) must check out the www module from CVS and add their profile to the www/htdocs/developer directory then edit index.php of that directory in order to have their profile listed. Alternatively, contact a developer/administrator to have them do this on your behalf. Information about the "Hackergotchi" section of the Volunteer Profiles follows.</p> ! ! ! <h2><a name="hackergotchi">Hackergotchi</a></h2> ! <h3>Applies to: All</h3> ! <p>Those wishing to create a "Hackergotchi" character may do so. The dimensions recommended are 80 pixels by 80 pixels. To have the Hackergotchi used for news postings, etc. on the main site, using CVS add it to the www/htdocs/image/hackergotchi directory. The Hackergotchi image should be named using your SourceForge.net username and should be of type PNG, JPEG or GIF; the filename must be all lowercase letters. A tutorial on how to create Hackergotchi images is available at <a href="http://www.livejournal.com/users/wouterverhelst/21322.html">http://www.livejournal.com/users/wouterverhelst/21322.html</a>.</p> ! <p><center><a href="roles.php">Previous</a> | <a href="index.php">Table of Contents</a> | <a href="glossary.php">Next</a></center></p> \ No newline at end of file Index: index.php =================================================================== RCS file: /cvsroot/openfirst/www/htdocs/doc/tut/howto/index.php,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** index.php 5 Jan 2005 18:06:24 -0000 1.4 --- index.php 24 May 2005 22:57:47 -0000 1.5 *************** *** 68,71 **** --- 68,73 ---- <li><a href="technology.php#database">MySQL/Database Software</a></li> <li><a href="technology.php#cvs">CVS</a></li> + <li><a href="technology.php#profiles">Volunteer Profiles</a></li> + <li><a href="technology.php#hackergotchi">Hackergotchi</a></li> </ul> </li> |