Allow mailinglist and repository variables to be available into the project template

[rick@…]

As when auto-generating overview pages, I find it of great use to present my users some additional information like the Mailinglist and Repository, which they could use. I do want to allow users to specify this kind of variables themselves, to avoid being the middle-man every times.

As most of 'traditional' software projects also seems to have the variables mailing list and repository the attached patch might be useful.

[rick@…]

Patch to allow Repository and Mailinglist to be available to admin and template interface

[rick@…]

Sample snippet of project template code we use at ​http://www.wirelessleiden.nl/projects with use of this new features

<li py:for="project in projects" py:choose="">
  <a py:when="project.href" href="$project.href"
     title="$project.description">$project.name</a><br />
     <em>$project.description</em><br />
     <table>
     <tr><td><em>Project page </em></td><td>:</td><td><a href="$project.href">$project.href</a></td></tr>
     <tr><td><em>Mailinglist</em></td><td>:</td><td>
      <div py:choose="">
          <div py:when="project.mailinglist">
              <a href="mailto:$project.mailinglist">$project.mailinglist</a> -
              <a href="http://$project.mailinglist_domain/mailman/listinfo/$project.mailinglist_name">info</a> -
              <a href="http://$project.mailinglist_domain/mailman/archive/$project.mailinglist_name">archives</a>
          </div>
          <div py:otherwise="">None</div>
      </div>
      </td></tr>
      <tr><td><em>Repository </em></td><td>:</td><td>
       <div py:choose="">
           <div py:when="project.repos">
               <a href="$project.repos">$project.repos</a>
           </div>
           <div py:otherwise="">None</div>
       </div>
      </td></tr>
     </table>
  <py:otherwise>
    <small>$project.name: <em>Error</em> <br /> ($project.description)</small>
  </py:otherwise>
</li>

[ebray]

I'm not so sure about mailing list. Not every project has a mailing list as such—seems like it would make more sense as a plugin or something.

Having a way to enter a canonical base URL for the project's repository seems more useful, though I don't know how that would work with multi-repository support.

[Remy Blank]

I would also tend to suggest implementing this in a plugin. Linking to the repository URL is tracked in #1781.