wiki:InfrastructureRequests

Version 11 (modified by jmpp@…, 16 years ago) (diff)

--

The purpose of this page is to consolidate and track pending infrastructure requests our project has submitted to its Mac OS Forge host. When thinking about a functionality you may desire at the server level, keep in mind that Mac OS Forge is not only shared with other projects but also that it does not have a staff of dedicated system administrators to cater to every single request. Therefore please refrain from submitting any infrastructure related ticket before presenting a valid case for it on the MacPorts development list and gathering at least some consensus over your proposal. Generally speaking, it's best to channel such requests through the MacPorts management team (jberry, jmpp & mww), since they are the ones in most frequent communication with Mac OS Forge admin personnel and as a result have a better feel for the state of current infrastructure and/or pending requests.

That being said, following is a list of the top priority request tickets that are currently in progress:

  • Trac e-mail notifications, #10672 (done!);
  • svn post-revprop-change hook, #12593 (done!);
  • svn props pre-commit hook, #12594;
  • Trac users management plugin, #12595 (an alternative is currently being investigated);
  • real author in "From" header in svn commit log emails, #12602 (done!);
  • Match current ticket field values in already existing entries, #12603 (done!).

The full list of open infrastructure requests can be found through the following trac search: http://trac.macports.org/projects/macports/query?status=new&status=assigned&status=reopened&component=infrastructure&order=priority

Lastly, below is a list of some thoughts that might make it into formal requests once their feasibility through futher investigation is determined:

  • Investigate extending trac's privileges engine to restrict non MacPorts team members from using some values, like setting a ticket to the MacPorts x.y milestone;
  • investigate linking new ticketing guidelines right off the new ticket form;