1 #include "top.h" 2 #include "index.h" 3 #include "bodytop.h" 4 #include "navbar.h" 5 6 <h3>What is <em>Husky</em>?</h3> 7 <blockquote> 8 The goal of this project is to develop a complete freeware suite of Fidonet 9 applications, running under Linux and other multitasking/multiuser systems. The suite 10 should be comparable to now existing (and partly commercial) OS/2 systems.<br> 11 Most of the software here is GPLed unless otherwise specified.<br> 12 To keep the configuration simple and reliable, all applications should use one set 13 of configuration-files. 14 </blockquote> 15 16 <h3>Latest News</h3> 17 <blockquote> 18 <ul> 19 <li>Latest File <a href="http://sourceforge.net/project/showfiles.php?group_id=1332">Releases</a>.</li> 20 <li>Husky Project <a href="http://sourceforge.net/news/?group_id=1332">News</a>.</li> 21 </ul> 22 </blockquote> 23 24 <h3>Fido-area and mailinglist</h3> 25 <blockquote> 26 The international developer and support echo for Husky is called <tt>FIDOSOFT.HUSKY</tt>. 27 It is routed through the WWB and gated to a mailinglist. If you can not get the echo, ask 28 <a href="mailto:mtt@tichy.de">Matthias Tichy</a> or 29 <a href="mailto:tobi@physcip.uni-stuttgart.de">Tobias Ernst</a> for a binkp, ISDN 30 or analog feed to this echo, or you can subscribe/unsubscribe to the mailinglist 31 (which is gated with the echo) using 32 <a href="http://lists.sourceforge.net/mailman/listinfo/husky-discuss">lists.sourceforge.net</a> 33 and write your articles to <a href="mailto:husky-discuss@lists.sourceforge.net">husky-discuss@lists.sourceforge.net</a>. 34 There is also a FTN fileecho called fidosoft.husky. It carries release source 35 archives of the husky project software; i.E., none of the latest files are hatched there, only 36 stable releases. 37 </blockquote> 38 39 <h3>CVS Server</h3> 40 <blockquote> 41 If you want write access to our cvs-server, register into sourceforge.net 42 and write message to one of Husky Project Managers. If you want read-only 43 access, use anonymous cvs login. 44 <a href="cvs.html">Read more about our cvs-server...</a><br> 45 </blockquote> 46 47 <h3>Daily Snapshots</h3> 48 <p>Daily snapshots and daily diff files are available as <em>tar.gz</em> files.</P 49 50 <ul> 51 <li>via filerequest at 2:240/5034, filenames: husky/<i>module</i>-latest.tar.gz, 52 husky/<i>module-YYMMDD</i>.tar.gz. and husky/<i>module-YYMMDD</i>.diff.gz. 53 <li>via mailinglist: (husky-diffs@lists.sourceforge.net). You can 54 subscribe/unsubscribe using 55 <a href="http://lists.sourceforge.net/mailman/listinfo/husky-diffs">lists.sourceforge.net</a> 56 <li>via http from <a href="cvs2">here</a> (Debian Linux packages: <a href="debian">here</a> 57 </ul> 58 59 Each diff is available as text: 60 <ul><li>via mailinglist: (husky-cvs@lists.sourceforge.net). You can 61 subscribe/unsubscribe using 62 <a href="http://lists.sourceforge.net/mailman/listinfo/husky-cvs">lists.sourceforge.net</a> 63 </ul> 64 65 You should understand that the latest snapshot archives are generated automatically, 66 are untested, and can contain all sorts of bugs and problems. If you are a new user, 67 you should not start with the snapshots. Instead, try getting a stable version from 68 one of the links in the navigation bar. 69 70 </blockquote> 71 72 <h3>Contact information</h3> 73 <blockquote> 74 Check out the <a href="team.html">Husky Team</a> page for details on how to contact 75 a member of the Team, or each project page if you want to contact the author of 76 a particular program. Keep in mind that although the author or authors of each project are the 77 <em>main</em> contact, they are not the only one that can be contacted about a project.<br> 78 Note also that you can reach almost every member of the Team in the official echo (or the 79 gated mailinglist). 80 </blockquote> 81 82 <small>Last update: 22 December 2006</small> 83 84 #include "bottom.h" 85