Uploaded image for project: 'Forge: FUSE Forge'
  1. Forge: FUSE Forge
  2. FUSEFORGE-104

remove downloads and source pages from the forge summary page?

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      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).

      So to avoid bad links, lets disable the links to source/downloads.

      The actual website of the projects can include links to source/downloads as the projects see fit.

      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

        Gliffy Diagrams

          Activity

          Hide
          mmcmanus Mary McManus added a comment -

          I like the idea of seeing them while it is private but hiding them for public projects.

          Show
          mmcmanus Mary McManus added a comment - I like the idea of seeing them while it is private but hiding them for public projects.
          Hide
          hmangan Heather Mangan added a comment -

          So taking the management project as an example - are we getting rid of the generic page ?
          http://fusesource.com/forge/projects/MANAGEMENT

          And replacing the link off the projects page to be the custom pages - if there is one available ie .
          http://management.fusesource.org/

          Show
          hmangan Heather Mangan added a comment - So taking the management project as an example - are we getting rid of the generic page ? http://fusesource.com/forge/projects/MANAGEMENT And replacing the link off the projects page to be the custom pages - if there is one available ie . http://management.fusesource.org/
          Hide
          jastrachan James Strachan added a comment -

          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

          Show
          jastrachan James Strachan added a comment - 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
          Hide
          hmangan Heather Mangan added a comment -

          I think that if there is a index.html present in http://fusesource.com/forge/sites/<project>/
          then direct to that page other wise use the generic page

          Show
          hmangan Heather Mangan added a comment - I think that if there is a index.html present in http://fusesource.com/forge/sites/ <project>/ then direct to that page other wise use the generic page
          Hide
          davidcporter David Porter added a comment -

          The web site model that we are using on FUSE Forge is the same as SourceForge, where you will find the following:

          1) A generic "project" site such as http://sourceforge.net/projects/docbook/, which is accessible from a list of projects (http://sourceforge.net/softwaremap/)

          2) A "public" web site for the project, such as http://docbook.sourceforge.net

          I find this model confusing, since there is duplicate information on both sites. It's also hard to distinguish the purpose of each site.

          Contrast this with Apache, where if you go to the Apache home page (http://www.apache.org/) and click a project name, you are taken to the project's public home page (http://camel.apache.org/)

          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?

          Show
          davidcporter David Porter added a comment - The web site model that we are using on FUSE Forge is the same as SourceForge, where you will find the following: 1) A generic "project" site such as http://sourceforge.net/projects/docbook/ , which is accessible from a list of projects ( http://sourceforge.net/softwaremap/ ) 2) A "public" web site for the project, such as http://docbook.sourceforge.net I find this model confusing, since there is duplicate information on both sites. It's also hard to distinguish the purpose of each site. Contrast this with Apache, where if you go to the Apache home page ( http://www.apache.org/ ) and click a project name, you are taken to the project's public home page ( http://camel.apache.org/ ) 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?
          Hide
          chirino Hiram Chirino added a comment -

          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).
          Directly linking to the custom project website is not a good option since then folks would loose the consistency.

          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.

          Show
          chirino Hiram Chirino added a comment - 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). Directly linking to the custom project website is not a good option since then folks would loose the consistency. 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.
          Hide
          chirino Hiram Chirino added a comment -

          forge retired.

          Show
          chirino Hiram Chirino added a comment - forge retired.

            People

            • Assignee:
              chirino Hiram Chirino
              Reporter:
              jastrachan James Strachan
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development