[Openfirst-cvscommit] www/htdocs/doc/tut/howto technology.php,1.9,1.10
Brought to you by:
xtimg
Menu
▾
▴
[Openfirst-cvscommit] www/htdocs/doc/tut/howto technology.php,1.9,1.10
|
From: Tim G. <xt...@us...> - 2006-02-23 17:47:36
|
Update of /cvsroot/openfirst/www/htdocs/doc/tut/howto In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3319 Modified Files: technology.php Log Message: Update the Technology requirements to reflect that the project now requires PHP 4.3 at minimum Index: technology.php =================================================================== RCS file: /cvsroot/openfirst/www/htdocs/doc/tut/howto/technology.php,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** technology.php 15 Jul 2005 22:54:26 -0000 1.9 --- technology.php 23 Feb 2006 17:47:28 -0000 1.10 *************** *** 17,21 **** <h3>Applies to: All</h3> ! <p>The openFIRST project maintains the <a href="http://www.openfirst.org/">openfirst.org</a> e-mail addresses (eg. <a href="mailto: ti...@op...">ti...@op...</a>). These addresses are most often set to forward to a contributors personal e-mail account by an administrator. E-mail addresses are assigned as fir...@op.... If you did not get an e-mail address assigned to you when you joined, or would like to change the address that mail is forwarded to, contact an administrator.</p> <p>A series of mailing lists is also maintained. See the <a href="information.php#mailinglists">Mailing lists heading</a> of the <a href="information.php">Information and Resources section</a> for more information about these mailing lists.</p> --- 17,22 ---- <h3>Applies to: All</h3> ! <p>The openFIRST project maintains the <a href="http://www.openfirst.org/">openfirst.org</a> e-mail addresses (eg. <a href="mailto: ti...@op...">ti...@op...</a>). These addresses are most often set to forward to a contributors personal e-mai ! l account by an administrator. E-mail addresses are assigned as fir...@op.... If you did not get an e-mail address assigned to you when you joined, or would like to change the address that mail is forwarded to, contact an administrator.</p> <p>A series of mailing lists is also maintained. See the <a href="information.php#mailinglists">Mailing lists heading</a> of the <a href="information.php">Information and Resources section</a> for more information about these mailing lists.</p> *************** *** 23,27 **** <h2><span id="webbrowser">The web browser</span></h2> <h3>Applies to: All</h3> ! <p>Since the openFIRST project is inherently web-based it is expected that contributors have at least a basic understanding of the usage of a web browser. It is recommended especially for those working with code/html to make use of the <a href="http://www.mozilla.org/firefox/">Firefox</a> web browser. There are a wide variety of plugins which are of use to website developers and general users (in Firefox, see <b>Tools</b> - <b>Extensions</b> - <b>Get More Extensions</b> for a catalogue of the available Firefox extensions).</p> <h3>Applies to: Developer, Patch Writer, Webmaster, Documentation Writer</h3> --- 24,30 ---- <h2><span id="webbrowser">The web browser</span></h2> <h3>Applies to: All</h3> ! <p>Since the openFIRST project is inherently web-based it is expected that contributors have at least a basic understanding of the usage of a web browser. It is recommended especially for those working with code/html to make use of the <a href="http://w ! ww.mozilla.org/firefox/">Firefox</a> web browser. There are a wide variety of plugins which are of use to website developers and general users (in Firefox, see <b>Tools</b> - <b>Extensions</b> - <b>Get More Extensions</b> for a catalogue of the available ! Firefox extensions).</p> <h3>Applies to: Developer, Patch Writer, Webmaster, Documentation Writer</h3> *************** *** 30,35 **** <ul> <li><b>Live HTTP Headers</b> - View HTTP headers of a page and while browsing.</li> ! <li><b>netcrafttoolbar</b> - Blocks Phishing Sites (can also be used to look up in depth information about where a website is hosted, by whom, etc which may be of particular use for detecting obscure configuration problems that are applicable to all users of a particular web host).</li> ! <li><b>Checky</b> - Easy to use interface to many free and commercial online validation and analysis services. Validate and analyse HTML, XHTML, CSS, RDF, RSS, XML, WAI, Section 508, P3P, hyperlinks, metadata and many more. Adds a context and tools menu.</li> <li><b>Fangs Screen Reader Emulator</b> - Renders a text version of a web page similar to screen reader output.</li> <li><b>LinkChecker</b> - Checks the validity of links on any webpage.</li> --- 33,40 ---- <ul> <li><b>Live HTTP Headers</b> - View HTTP headers of a page and while browsing.</li> ! <li><b>netcrafttoolbar</b> - Blocks Phishing Sites (can also be used to look up in depth information about where a website is hosted, by whom, etc which may be of particular use for detecting obscure configuration problems that are applicable to all use ! rs of a particular web host).</li> ! <li><b>Checky</b> - Easy to use interface to many free and commercial online validation and analysis services. Validate and analyse HTML, XHTML, CSS, RDF, RSS, XML, WAI, Section 508, P3P, hyperlinks, metadata and many more. Adds a context and tools men ! u.</li> <li><b>Fangs Screen Reader Emulator</b> - Renders a text version of a web page similar to screen reader output.</li> <li><b>LinkChecker</b> - Checks the validity of links on any webpage.</li> *************** *** 41,66 **** <h2><span id="html">HTML</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Webmaster, Documentation Writer</h3> ! <p>The openFIRST project tries when possible to produce valid HTML (matching the particular doctype of any given document). In most cases, the standard currently used is HTML 4. Pages should have valid HTML and should be checked with the W3C HTML Validator at <a href="http://validator.w3.org/">http://validator.w3.org/</a> or a similar tool. It is suggested that you be familiar with HTML, and the HTML standard itself available at <a href="http://w3.org/MarkUp/">http://w3.org/MarkUp/</a> rather than just blindly following a validator.</p> ! <p>The openFIRST project site, and the software created by the project should be as accessible as possible. More information about making web pages accessible is available from the Web Accessibility Initiative at <a href="http://w3.org/WAI/">http://w3.org/WAI/</a>. An Accessibility testing tool called Bobby™ is available at <a href="http://bobby.watchfire.com/bobby/html/en/index.jsp">http://bobby.watchfire.com/bobby/html/en/index.jsp</a>.</p> <h2><span id="css">CSS</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Webmaster</h3> ! <p>The openFIRST project tries when possible to sue valid CSS when possible. The current version of the Cascading Style Sheets standard that is used is CSS 2. It is recommended that stylesheets and pages be checked using the CSS validator at <a href="http://jigsaw.w3.org/css-validator/">http://jigsaw.w3.org/css-validator/</a> or a similar tool. It is suggested that you use the CSS standard for reference; the standard is available at <a href="http://w3.org/Style/CSS/">http://w3.org/Style/CSS/</a>.</p> ! <p>Where possible, CSS should be used to make web pages more accessible. More information about making web pages accessible is available from the Web Accessibility Initiative at <a href="http://w3.org/WAI/">http://w3.org/WAI/</a>. An Accessibility testing tool called Bobby™ is available at <a href="http://bobby.watchfire.com/bobby/html/en/index.jsp">http://bobby.watchfire.com/bobby/html/en/index.jsp</a>.</p> <h2><span id="bugzilla">Bugzilla</span></h2> <h3>Applies to: Administrator, Developer, Documentation Writer, Patch Writer, Webmaster</h3> ! <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>Jobs which are suitable for those people with only an entry level of experience with the openFIRST project are (or should be) <a href="http://bugzilla.openfirst.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=%5BJJ%5D">marked with the [JJ] tag</a>. Junior Jobs are typically expected to take under an hour to research/isolate (if required) and implement.</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><span id="updatesystem">openFIRST Update System</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Webmaster</h3> ! <p>The openFIRST Update System is currently under development at <a href="http://update.openfirst.org/test/">http://update.openfirst.org/test/</a>. The goal of the system is to create a simple interface for end users to remotely install and manage any number of openFIRST installations. The system will be able to automate installation of updates and security patches, and communicates directly with the end-user's web server, preventing users on slow connections from having to undergo the lengthy download process to get the full openFIRST system. Third parties will be able to submit packages to be managed by the openFIRST Update System, and can mark security updates, new versions, etc. which will notify end users who have set their preferences as such.</p> <p>The openFIRST Update System resides in the <b>update</b> module of the openFIRST CVS repository.</p> --- 46,85 ---- <h2><span id="html">HTML</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Webmaster, Documentation Writer</h3> ! <p>The openFIRST project tries when possible to produce valid HTML (matching the particular doctype of any given document). In most cases, the standard currently used is HTML 4. Pages should have valid HTML and should be checked with the W3C HTML Valid ! ator at <a href="http://validator.w3.org/">http://validator.w3.org/</a> or a similar tool. It is suggested that you be familiar with HTML, and the HTML standard itself available at <a href="http://w3.org/MarkUp/">http://w3.org/MarkUp/</a> rather than jus ! t blindly following a validator.</p> ! <p>The openFIRST project site, and the software created by the project should be as accessible as possible. More information about making web pages accessible is available from the Web Accessibility Initiative at <a href="http://w3.org/WAI/">http://w3.o ! rg/WAI/</a>. An Accessibility testing tool called Bobby™ is available at <a href="http://bobby.watchfire.com/bobby/html/en/index.jsp">http://bobby.watchfire.com/bobby/html/en/index.jsp</a>.</p> <h2><span id="css">CSS</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Webmaster</h3> ! <p>The openFIRST project tries when possible to sue valid CSS when possible. The current version of the Cascading Style Sheets standard that is used is CSS 2. It is recommended that stylesheets and pages be checked using the CSS validator at <a href="h ! ttp://jigsaw.w3.org/css-validator/">http://jigsaw.w3.org/css-validator/</a> or a similar tool. It is suggested that you use the CSS standard for reference; the standard is available at <a href="http://w3.org/Style/CSS/">http://w3.org/Style/CSS/</a>.</p> ! <p>Where possible, CSS should be used to make web pages more accessible. More information about making web pages accessible is available from the Web Accessibility Initiative at <a href="http://w3.org/WAI/">http://w3.org/WAI/</a>. An Accessibility test ! ing tool called Bobby™ is available at <a href="http://bobby.watchfire.com/bobby/html/en/index.jsp">http://bobby.watchfire.com/bobby/html/en/index.jsp</a>.</p> <h2><span id="bugzilla">Bugzilla</span></h2> <h3>Applies to: Administrator, Developer, Documentation Writer, Patch Writer, Webmaster</h3> ! <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 co ! ntributor 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>Jobs which are suitable for those people with only an entry level of experience with the openFIRST project are (or should be) <a href="http://bugzilla.openfirst.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__& ! ;product=&content=%5BJJ%5D">marked with the [JJ] tag</a>. Junior Jobs are typically expected to take under an hour to research/isolate (if required) and implement.</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">htt ! p://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 requir ! e remaking these templates in order for the Bugzilla site to function as expected.</p> <h2><span id="updatesystem">openFIRST Update System</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Webmaster</h3> ! <p>The openFIRST Update System is currently under development at <a href="http://update.openfirst.org/test/">http://update.openfirst.org/test/</a>. The goal of the system is to create a simple interface for end users to remotely install and manage any n ! umber of openFIRST installations. The system will be able to automate installation of updates and security patches, and communicates directly with the end-user's web server, preventing users on slow connections from having to undergo the lengthy download ! process to get the full openFIRST system. Third parties will be able to submit packages to be managed by the openFIRST Update System, and can mark security updates, new versions, etc. which will notify end users who have set their preferences as such.</ ! p> <p>The openFIRST Update System resides in the <b>update</b> module of the openFIRST CVS repository.</p> *************** *** 68,72 **** <h2><span id="shellaccess">Shell Access</span></h2> <h3>Applies to: Administrator, Developer, Webmaster</h3> ! <p>All developers, webmasters, and administrators are able to access the SourceForge.net Project Shell Server via SSH at <b>shell.sourceforge.net</b>. A suitable SSH client for Windows is PuTTY, and is available at <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html</a>; many other operating systems already include an SSH client, on UNIX or Linux consult <tt>man ssh</tt> for more information. To login, you should use your SourceForge.net username and passsword. It is recommended, for the sake of convenience, that upon logging into the system for the first time, you perform these command:</p> <p><tt>ln -s /home/groups/o/op/openfirst openfirst</tt></p> --- 87,93 ---- <h2><span id="shellaccess">Shell Access</span></h2> <h3>Applies to: Administrator, Developer, Webmaster</h3> ! <p>All developers, webmasters, and administrators are able to access the SourceForge.net Project Shell Server via SSH at <b>shell.sourceforge.net</b>. A suitable SSH client for Windows is PuTTY, and is available at <a href="http://www.chiark.greenend.or ! g.uk/~sgtatham/putty/download.html">http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html</a>; many other operating systems already include an SSH client, on UNIX or Linux consult <tt>man ssh</tt> for more information. To login, you should use ! your SourceForge.net username and passsword. It is recommended, for the sake of convenience, that upon logging into the system for the first time, you perform these command:</p> <p><tt>ln -s /home/groups/o/op/openfirst openfirst</tt></p> *************** *** 78,82 **** <tt>./updatesite.sh</tt></p> ! <p>Administrators and webmasters of other openFIRST sites may be able to access them via SSH using a different login name and password. If you require shell access to one of these other sites, or to the SF.net Project Shell Server, contact an administrator.</p> <p>...</p> --- 99,104 ---- <tt>./updatesite.sh</tt></p> ! <p>Administrators and webmasters of other openFIRST sites may be able to access them via SSH using a different login name and password. If you require shell access to one of these other sites, or to the SF.net Project Shell Server, contact an administra ! tor.</p> <p>...</p> *************** *** 84,92 **** <h2><span id="php">PHP</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Release Technician, Webmaster</h3> ! <p><a href="http://www.php.net/">PHP</a> is the language used to write the vast majority of the code that openFIRST uses/distributes. When writing/patching openFIRST software it may be assumed that the user is using at least PHP version 4. PHP 3 is no longer officially supported by the openFIRST project. Some of the openFIRST servers run PHP4 versions and others run PHP5; when writing code, you should test with both PHP4 and PHP5.</p> <h2><span id="asp">ASP</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Release Technician, Webmaster</h3> ! <p>Very little of the project is written in ASP at the moment, and the ASP versions have been unmaintained for quite some time now. The original creator of the ASP modules graduated before the project had any real plan for replacing graduated developers. Ideally we'd find someone who could take them over, but the focus is on the PHP versions of modules. If you happen to be interested in bringing the ASP versions up to date (with features that parallel the PHP versions of modules) contact an Administrator.</p> <h2><span id="database">MySQL/Database Software</span></h2> --- 106,117 ---- <h2><span id="php">PHP</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Release Technician, Webmaster</h3> ! <p><a href="http://www.php.net/">PHP</a> is the language used to write the vast majority of the code that openFIRST uses/distributes. When writing/patching openFIRST software it may be assumed that the user is using at least PHP version 4.3 (released December, 2002). PHP 3 and versions of PHP prior to 4.3.0 are no ! longer officially supported by the openFIRST project. Some of the openFIRST servers run PHP4 versions and others run PHP5; when writing code, you should test with both PHP4 and PHP5.</p> <h2><span id="asp">ASP</span></h2> <h3>Applies to: Administrator, Developer, Patch Writer, Release Technician, Webmaster</h3> ! <p>Very little of the project is written in ASP at the moment, and the ASP versions have been unmaintained for quite some time now. The original creator of the ASP modules graduated before the project had any real plan for replacing graduated developers. ! Ideally we'd find someone who could take them over, but the focus is on the PHP versions of modules. If you happen to be interested in bringing the ASP versions up to date (with features that parallel the PHP versions of modules) contact an Administrat ! or.</p> <h2><span id="database">MySQL/Database Software</span></h2> *************** *** 98,104 **** <h2><span id="cvs">CVS</span></h2> <h3>Applies to: Administrator, Developer, Documentation Writer, Release Technician, Webmaster</h3> ! <p>CVS is used by the openFIRST project for version control. It allows multiple contributors to work on the project at one time without interfering with one another's work. CVS can merge different changes to a file in an intelligent way; but it's merging attempts should be verfied manually just to be certain. To login to CVS, use your SourceForge.net username and password.</p> ! <p>One possible route for accessing the CVS repository is using Smart CVS (<a href="http://www.smartcvs.com/">http://www.smartcvs.com/</a>). Documentation about how to configure Smart CVS 3 (the newer version) is available at <a href="http://www.openfirst.org/cvs/smartcvs3/">http://www.openfirst.org/cvs/smartcvs3/</a> and documentation for Smart CVS 2 (an older version) is available at <a href="http://www.openfirst.org/cvs/smartcvs/">http://www.openfirst.org/cvs/smartcvs/</a>. There are other CVS clients which will work, and may be more suited to your personal preference. It is recommended that contributors who will be using CVS, especially Administrators, also skim/read the SourceForge.net Project Documentation pertaining to CVS available at: <a href="http://www.sourceforge.net/docman/?group_id=1">http://www.sourceforge.net/docman/?group_id=1</a> (the documentation includes a list of several alternatives to SmartCVS at <a href="http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1#howtoaccess">http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1#howtoaccess</a>). Read-only access to the CVS repository is available through a web browser using viewcvs at <a href="http://cvs.sourceforge.net/viewcvs.py/openfirst/">http://cvs.sourceforge.net/viewcvs.py/openfirst/</a>; but at the current time, viewcvs does not keep in perfect sync with the cvs repository as developers see it; it lags behind a bit.</p> <p>Some general rules for CVS include:</p> --- 123,135 ---- <h2><span id="cvs">CVS</span></h2> <h3>Applies to: Administrator, Developer, Documentation Writer, Release Technician, Webmaster</h3> ! <p>CVS is used by the openFIRST project for version control. It allows multiple contributors to work on the project at one time without interfering with one another's work. CVS can merge different changes to a file in an intelligent way; but it's mergi ! ng attempts should be verfied manually just to be certain. To login to CVS, use your SourceForge.net username and password.</p> ! <p>One possible route for accessing the CVS repository is using Smart CVS (<a href="http://www.smartcvs.com/">http://www.smartcvs.com/</a>). Documentation about how to configure Smart CVS 3 (the newer version) is available at <a href="http://www.openfir ! st.org/cvs/smartcvs3/">http://www.openfirst.org/cvs/smartcvs3/</a> and documentation for Smart CVS 2 (an older version) is available at <a href="http://www.openfirst.org/cvs/smartcvs/">http://www.openfirst.org/cvs/smartcvs/</a>. There are other CVS clien ! ts which will work, and may be more suited to your personal preference. It is recommended that contributors who will be using CVS, especially Administrators, also skim/read the SourceForge.net Project Documentation pertaining to CVS available at: <a href ! ="http://www.sourceforge.net/docman/?group_id=1">http://www.sourceforge.net/docman/?group_id=1</a> (the documentation includes a list of several alternatives to SmartCVS at <a href="http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1#howt ! oaccess">http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1#howtoaccess</a>). Read-only access to the CVS repository is available through a web browser using viewcvs at <a href="http://cvs.sourceforge.net/viewcvs.py/openfirst/">http://c ! vs.sourceforge.net/viewcvs.py/openfirst/</a>; but at the current time, viewcvs does not keep in perfect sync with the cvs repository as developers see it; it lags behind a bit.</p> <p>Some general rules for CVS include:</p> *************** *** 108,121 **** </ul> ! <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><span id="profiles">Volunteer Profiles</span></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><span id="hackergotchi">Hackergotchi</span></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 --- 139,159 ---- </ul> ! <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 in ! dex 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 t ! he 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 openFIRS ! T 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 upgra ! de/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><span id="profiles">Volunteer Profiles</span></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><span id="hackergotchi">Hackergotchi</span></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/hackergo ! tchi 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> |
