http://fusesource.com/issues This file is an XML representation of an issue en-us 3.13.2 335 26-11-2008 Enterprise http://fusesource.com/issues/browse/FUSEFORGE-104 it can be confusing when projects have no downloads yet (the default) and when projects use both svn and git (with git only for the website). <p>So to avoid bad links, lets disable the links to source/downloads.</p> <p>The actual website of the projects can include links to source/downloads as the projects see fit.</p> <p>Maybe we only show those source links on the forge page if its a private project? As its handy when stuff starts up, before a site is created</p> FUSEFORGE-104

remove downloads and source pages from the forge summary page?

Improvement Major Open Unresolved Hiram Chirino James Strachan Wed, 3 Jun 2009 13:48:19 +0000 (UTC) Fri, 12 Jun 2009 13:01:49 +0000 (UTC) 1.1 Forge Rails Application 0 I like the idea of seeing them while it is private but hiding them for public projects. <p>So taking the management project as an example - are we getting rid of the generic page ?<br/> <span class="nobr"><a href="http://fusesource.com/forge/projects/MANAGEMENT">http://fusesource.com/forge/projects/MANAGEMENT^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p>And replacing the link off the projects page to be the custom pages - if there is one available ie . <br/> <span class="nobr"><a href="http://management.fusesource.org/">http://management.fusesource.org/^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> So I'm thinking we just remove the download links from the generic page for all public projects; we just then link to the website on the generic project page I think that if there is a index.html present in <span class="nobr"><a href="http://fusesource.com/forge/sites/">http://fusesource.com/forge/sites/^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span>&lt;project&gt;/<br/> then direct to that page other wise use the generic page The web site model that we are using on FUSE Forge is the same as SourceForge, where you will find the following: <p>1) A generic "project" site such as <span class="nobr"><a href="http://sourceforge.net/projects/docbook/">http://sourceforge.net/projects/docbook/^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span>, which is accessible from a list of projects (<span class="nobr"><a href="http://sourceforge.net/softwaremap/">http://sourceforge.net/softwaremap/^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span>)</p> <p>2) A "public" web site for the project, such as <span class="nobr"><a href="http://docbook.sourceforge.net">http://docbook.sourceforge.net^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p>I find this model confusing, since there is duplicate information on both sites. It's also hard to distinguish the purpose of each site. </p> <p>Contrast this with Apache, where if you go to the Apache home page (<span class="nobr"><a href="http://www.apache.org/">http://www.apache.org/^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span>) and click a project name, you are taken to the project's public home page (<span class="nobr"><a href="http://camel.apache.org/">http://camel.apache.org/^{<img class="rendericon" src="https://fusesource.com/issues/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span>)</p> <p>So my question is, if we remove the generic "project" page entirely for public projects, as Amanda and Heather suggest, do we lose any functionality?</p> Since the forge provides a project directory interface, I think it's important that there is a consistent view page for the project details (across projects). <br/> Directly linking to the custom project website is not a good option since then folks would loose the consistency. <p>I do think the current generic detailspage could use more work. Lets work on fixing that up. I recommend that folks start by submitting mockups screen shots of how the details page could be improved.</p> Date of First Response Wed, 3 Jun 2009 14:33:37 +0000 (UTC)