Changes between Initial Version and Version 1 of HostingRequests


Ignore:
Timestamp:
Dec 21, 2007, 2:45:18 PM (16 years ago)
Author:
jmpp@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HostingRequests

    v1 v1  
     1The 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 [http://ists.macosforge.org/mailman/listinfo/macports-dev 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.
     2
     3That being said, following is a list of the top priority request tickets that are currently in progress:
     4
     5 * svn props pre-commit hook, #12594;
     6 * Trac users management plugin, #12595 (an alternative is currently being investigated);
     7 * ~~Trac e-mail notifications, #10672~~;
     8 * ~~svn post-revprop-change hook, #12593~~;
     9 * ~~real author in "From" header in svn commit log emails, #12602~~;
     10 * ~~Match current ticket field values in already existing entries, #12603~~.
     11
     12The 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=server%2Fhosting&order=priority
     13
     14Lastly, below is a list of some thoughts that might make it into formal requests once their feasibility through futher investigation is determined:
     15
     16 * 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;
     17 * investigate linking new ticketing guidelines right off the [http://trac.macports.org/projects/macports/newticket new ticket] form;
     18