| 42 | | == Mentors == |
| 43 | | |
| 44 | | The following committers have agreed to be mentors for SoC 2010 (append @macports.org for e-mail) |
| 45 | | |
| 46 | | ||'''Name''' ||'''Email''' ||'''Area''' || |
| 47 | | ||[wiki:juanger Juan Germán Castañeda Echevarria] || juanger || GUI, MPWA || |
| 48 | | ||[wiki:perry Perry Lee] || perry || || |
| 49 | | ||[wiki:raimue Rainer Mueller] || raimue || Administrator, config files, rev-upgrade, depcheck || |
| 50 | | ||[wiki:snc Jeremy Lavergne] || snc || || |
| 51 | | ||[wiki:wms William Siegrist] || wms || Backup Administrator || |
| 52 | | |
| 53 | | {{{ |
| 54 | | #!comment |
| 55 | | ||[wiki:armahg George Armah] || GUI, Framework || armahg || |
| 56 | | ||James Berry || MPWA || jberry || |
| 57 | | ||[wiki:blb Bryan Blackburn] || Logging, self-management, general || blb || |
| 58 | | ||[wiki:snc Jeremy Lavergne] || Helping hand || snc || |
| 59 | | ||[wiki:perry Perry Lee] || Co-mentoring || perry || |
| 60 | | }}} |
| 61 | | |
| 69 | | |
| 70 | | ==== Configuration files handling ==== #configfiles |
| 71 | | |
| 72 | | MacPorts has no way to track configuration files. Currently if a configuration file is part of a port it will get overwritten on every upgrade which makes it less useful. At the moment, many ports only install default configuration files and the user has to copy it to the original location. But this always requires manual action and the user is not informed of updates in this configuration file. |
| 73 | | |
| 74 | | For this task, investigate how other package management systems handle this. Find the best way to support it in MacPorts and implement it. See also #2365. |
| 75 | | |
| 76 | | Classification: easy to medium task[[BR]] |
| 77 | | Programming languages: Tcl[[BR]] |
| 78 | | Potential mentor: raimue |
| 79 | | |
| 80 | | ==== Graphical user interface ==== #GUI |
| 81 | | |
| 82 | | Extend and improve the existing [wiki:MacPortsGUI basic GUI] which has been implemented as part of GSoC 2008/2009. Pallet is at the moment functional to install/uninstall ports, but for example it cannot handle variants yet. Also, it is slow if you have many ports installed. |
| 83 | | |
| 84 | | Some feature proposals: |
| 85 | | * Variant selection |
| 86 | | * Interactive dependency tree/graph |
| 87 | | |
| 88 | | The GUI is driven by the MacPorts Framework, which acts as an wrapper of the MacPorts Tcl API to Objective-C. To enhance the GUI you will probably have to implement the respective features in the framework first. |
| 89 | | |
| 90 | | It would be your task to identify possible improvements for the GUI. This can either be new features or (speed) improvements to existing ones. |
| 91 | | |
| 92 | | Resources: |
| 93 | | * [wiki:MacPortsGUI] |
| 94 | | * [wiki:MacPortsGUIFAQ] |
| 95 | | * [wiki:MacPortsFramework] |
| 96 | | * Pallet port |
| 97 | | |
| 98 | | Classification: medium task[[BR]] |
| 99 | | Programming languages: Objective-C and Tcl[[BR]] |
| 100 | | Potential mentors: juanger |
| 101 | | |
| 102 | | ==== MacPorts Web Application (MPWA) ==== #mpwa |
| 103 | | |
| 104 | | A very good start has been made on a Web Application for MacPorts to serve as a basis for easier user submission and maintenance of ports, not to mention monitoring of port build status, browsing of ports, etc. This work is known as MPWA and is written in Ruby on Rails. This task is to complete the work on MPWA so that it is usable for day to day usage by the MacPorts community. Work is needed on user credentials and authentication, port dependency integration, port submission and tracking, etc. This is a very exciting project and can help MacPorts scale to support a larger community. |
| 105 | | |
| 106 | | Read more about the [source:contrib/mpwa/doc MPWA design and model] and look at the [source:contrib/mpwa/ existing code]. |
| 107 | | |
| 108 | | Classification: moderate, with good follow through vision, and architecture required[[BR]] |
| 109 | | Programming languages: Ruby, perhaps a bit of Tcl[[BR]] |
| 110 | | Potential mentor: juanger |
