| 52 | | * Write your own abstract and proposal, copying text from this idea page is not enough. |
| 53 | | * Show us that you fully understand your task and know what you want to do over the summer. |
| 54 | | * At best, include a short weekly roadmap covering how you would work on the task. |
| | 48 | * Write your own abstract and proposal, copying text from this idea page is not enough. |
| | 49 | * Show us that you fully understand your task and know what you want to do over the summer. |
| | 50 | * At best, include a short weekly roadmap covering how you would work on the task. |
| 57 | | * Get familiar with the MacPorts project resources. Especially [GetMacPortsSource check out the code] and [http://guide.macports.org read the guide]. |
| 58 | | * Read the [http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html Tcl Tutorial] |
| 59 | | * Subscribe to the mailing lists [http://lists.macosforge.org/mailman/listinfo/macports-dev macports-dev] and [http://lists.macosforge.org/mailman/listinfo/macports-users macports-users] if you do not already read them. Don't be too shy to post. |
| 60 | | * '''Get in contact! ''' Most important is to discuss your contribution ideas with potential mentors by e-mail, on the MacPorts development list or the IRC channel before applying. |
| | 53 | * Get familiar with the MacPorts project resources. Especially [GetMacPortsSource check out the code] and [http://guide.macports.org read the guide]. |
| | 54 | * Read the [http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html Tcl Tutorial] |
| | 55 | * Subscribe to the mailing lists [http://lists.macosforge.org/mailman/listinfo/macports-dev macports-dev] and [http://lists.macosforge.org/mailman/listinfo/macports-users macports-users] if you do not already read them. Don't be too shy to post. |
| | 56 | * '''Get in contact!''' Most important is to discuss your contribution ideas with potential mentors by e-mail, on the MacPorts development list or the IRC channel before applying. |
| 67 | | ||Jeremy Lavergne || snc || Administrator || |
| 68 | | ||Clemens Lang || cal || Backup Admin || |
| 69 | | ||Rainer Müller || raimue || Mentoring for base, port groups, ports, ... || |
| 70 | | ||Lawrence Velázquez || larryv || Backup to the backup admin; mentoring for port[group]s, documentation, website || |
| | 63 | ||= Jeremy Lavergne =|| snc || Administrator || |
| | 64 | ||= Clemens Lang =|| cal || Backup Admin || |
| | 65 | ||= Rainer Müller =|| raimue || Mentoring for base, port groups, ports, ... || |
| | 66 | ||= Lawrence Velázquez =|| larryv || Backup to the backup admin; mentoring for port[group]s, documentation, website || |
| 100 | | This task consists of implementing a new dependencies engine for MacPorts. The current dependency engine properly deals with installing packages, but it does not deal satisfactorily with [ticket:126 dependencies on variants] (and versions), uninstalling and upgrading. This very challenging task requires a complete formalization of the use cases (installation, upgrade, uninstallation) and of the user needs before any implementation, as well as a deep understanding of the dependency relations (required for fetching, building, configuring; static and dynamic linking; dependence at runtime). |
| 101 | | |
| 102 | | Classification: very challenging task[[BR]] |
| 103 | | Programming languages: Tcl and C[[BR]] |
| 104 | | |
| | 94 | This task consists of implementing a new dependencies engine for MacPorts. The current dependency engine properly deals with installing packages, but it does not deal satisfactorily with [[ticket:126|dependencies on variants]] (and versions), uninstalling and upgrading. This very challenging task requires a complete formalization of the use cases (installation, upgrade, uninstallation) and of the user needs before any implementation, as well as a deep understanding of the dependency relations (required for fetching, building, configuring; static and dynamic linking; dependence at runtime). |
| | 95 | |
| | 96 | * Difficulty: Very challenging |
| | 97 | * Languages: Tcl, C |
| | 98 | * Potential mentors: TBD |
| 108 | | The MacPorts port should be the source for updating a user's MacPorts |
| 109 | | installation. |
| 110 | | |
| 111 | | Currently the MacPorts port is used to build the .dmg installer for MacPorts that is used for the initial installation of MacPorts, and port uses the "selfupdate" mechanism for maintaining the MacPorts installation. The selfupdate mechanism is (at least not documented as such) not accessible through the MacPorts API and does not use the MacPorts mechanisms for maintaining ports |
| 112 | | |
| 113 | | Classification: challenging task[[BR]] |
| 114 | | Programming languages: Tcl and C[[BR]] |
| 115 | | Potential mentor: TBD |
| | 102 | The MacPorts port should be the source for updating a user’s MacPorts installation. |
| | 103 | |
| | 104 | Currently the MacPorts port is used to build the .dmg installer for MacPorts that is used for the initial installation of MacPorts, and port uses the “selfupdate” mechanism for maintaining the MacPorts installation. The selfupdate mechanism is (at least not documented as such) not accessible through the MacPorts API and does not use the MacPorts mechanisms for maintaining ports |
| | 105 | |
| | 106 | * Difficulty: Challenging |
| | 107 | * Languages: Tcl, C |
| | 108 | * Potential mentors: TBD |
| 122 | | * http://www.gentoo.org/proj/en/perl/g-cpan.xml |
| 123 | | * http://search.cpan.org/~bingos/CPANPLUS-0.9001/bin/cpan2dist |
| 124 | | * http://packages.debian.org/stable/dh-make-perl |
| 125 | | |
| 126 | | Classification: easy to medium task[[BR]] |
| 127 | | Programming languages: Perl and probably Tcl[[BR]] |
| 128 | | Potential mentor: TBD |
| | 115 | * http://www.gentoo.org/proj/en/perl/g-cpan.xml |
| | 116 | * http://search.cpan.org/~bingos/CPANPLUS-0.9001/bin/cpan2dist |
| | 117 | * http://packages.debian.org/stable/dh-make-perl |
| | 118 | |
| | 119 | * Difficulty: Easy to medium |
| | 120 | * Languages: Perl, probably Tcl |
| | 121 | * Potential mentors: TBD |
| 132 | | MacPorts should be able to more readily install python packages from pip. We don't want to integrate the build/installation process of PIP, simply parse information or eggs it provides for various packages. This information will then be used to generate a Portfile, akin to [browser:contrib/cpan2port/cpan2port cpan2port]. |
| 133 | | |
| 134 | | There may be instances where MacPorts package names don't match up with pip's. In this case, pip should be the authority and all improperly named MacPorts packages should be replaced by a renamed copy. Verbose automation of this step, akin to the portcheckup script, is ideal. |
| 135 | | |
| 136 | | The [browser:contrib/portfile-gen/portfile-gen portfile generator] may or be helpful. |
| 137 | | |
| 138 | | Classification: medium task[[BR]] |
| 139 | | Programming languages: Tcl, Python, C[[BR]] |
| 140 | | Potential mentor: snc |
| | 125 | MacPorts should be able to more readily install python packages from pip. We don't want to integrate the build/installation process of PIP, simply parse information or eggs it provides for various packages. This information will then be used to generate a Portfile, akin to [[browser:contrib/cpan2port/cpan2port|cpan2port]]. |
| | 126 | |
| | 127 | There may be instances where MacPorts package names don't match up with pip’s. In this case, pip should be the authority and all improperly named MacPorts packages should be replaced by a renamed copy. Verbose automation of this step, akin to the portcheckup script, is ideal. |
| | 128 | |
| | 129 | The [[browser:contrib/portfile-gen/portfile-gen|portfile generator]] might be helpful. |
| | 130 | |
| | 131 | * Difficulty: Medium |
| | 132 | * Languages: Tcl, Python, C |
| | 133 | * Potential mentors: snc |
| 146 | | Classification: medium task[[BR]] |
| 147 | | Programming languages: Tcl, C, ocaml, haskell, lua, javascript, any other languages that come with their own package manager[[BR]] |
| 148 | | Potential mentor: TBD |
| | 139 | * Classification: Medium |
| | 140 | * Languages: Tcl, C, OCaml, Haskell, Lua, Node.js, etc. |
| | 141 | * Potential mentors: TBD |
| 152 | | MacPorts project currently includes a [source:trunk/base/tests test framework] to test features of the infrastructure. However, the tests do not cover all the code and they are not executed on an automatic basis. This task consists of extending the test framework and could be broadened to develop a code coverage technology for MacPorts to make the infrastructure more robust to future changes. |
| 153 | | |
| 154 | | Classification: relatively easy to very challenging[[BR]] |
| 155 | | Programming languages: Tcl, C[[BR]] |
| 156 | | |
| | 145 | MacPorts currently includes a [[source:trunk/base/tests|test framework]] to test features of the infrastructure. However, the tests do not cover all the code and they are not executed on an automatic basis. This task consists of extending the test framework and could be broadened to develop a code coverage technology for MacPorts to make the infrastructure more robust to future changes. |
| | 146 | |
| | 147 | * Difficulty: Relatively easy to very challenging |
| | 148 | * Languages: Tcl, C |
| | 149 | * Potential mentor: raimue |
| 173 | | * Not using daemondo if the daemon works fine under launchd without it |
| 174 | | * Ability to install multiple plists |
| 175 | | * Support for LaunchAgents as well as LaunchDaemons |
| 176 | | * Installing plists in ~/Library for non-root installs if the user wants |
| 177 | | * only modify specific XML tags to avoid clobbering additions by user |
| 178 | | |
| 179 | | Classification: easy[[BR]] |
| 180 | | Programming languages: Tcl, C[[BR]] |
| 181 | | Potential mentor: TBD |
| | 165 | * Not using daemondo if the daemon works fine under launchd without it |
| | 166 | * Ability to install multiple plists |
| | 167 | * Support for LaunchAgents as well as LaunchDaemons |
| | 168 | * Installing plists in ~/Library for non-root installs if the user wants |
| | 169 | * only modify specific XML tags to avoid clobbering additions by user |
| | 170 | |
| | 171 | * Difficulty: Easy |
| | 172 | * Languages: Tcl, C |
| | 173 | * Potential mentors: TBD |
| 194 | | Improve 'port clean' to be able to delete distfiles for a specified |
| 195 | | version, and all distfiles not needed by currently installed versions of |
| 196 | | ports. |
| 197 | | |
| 198 | | In general, add an action for reclaiming disk space, which would delete old |
| 199 | | distfiles and archives and uninstall inactive ports (and anything else |
| 200 | | that would help) |
| 201 | | |
| 202 | | Classification: easy[[BR]] |
| 203 | | Programming languages: Tcl, C[[BR]] |
| 204 | | Potential mentor: TBD |
| | 186 | Improve `port clean` to be able to delete distfiles for a specified version, and all distfiles not needed by currently installed versions of ports. In general, add an action for reclaiming disk space, which would delete old distfiles and archives and uninstall inactive ports (and anything else that would help) |
| | 187 | |
| | 188 | * Difficulty: Easy |
| | 189 | * Languages: Tcl, C |
| | 190 | * Potential mentors: TBD |
| 208 | | When an action will run targets on multiple ports, run them in |
| 209 | | parallel when possible and sensible (requires tracking dependencies |
| 210 | | between both targets and ports and figuring out the maximum reasonable |
| 211 | | parallelism, e.g. several ports can fetch at once on a fast connection |
| 212 | | but you only want one 'make -j8' at a time) |
| 213 | | |
| 214 | | Classification: very challenging[[BR]] |
| 215 | | Programming languages: Tcl, C[[BR]] |
| 216 | | Potential mentor: TBD |
| | 194 | When an action will run targets on multiple ports, run them in parallel when possible and sensible (requires tracking dependencies between both targets and ports and figuring out the maximum reasonable parallelism, e.g. several ports can fetch at once on a fast connection but you only want one 'make -j8' at a time) |
| | 195 | |
| | 196 | * Difficulty: Very challenging |
| | 197 | * Languages: Tcl, C |
| | 198 | * Potential mentors: TBD |
| 229 | | Integrate muniversal into base. Not just a direct copy-and-paste, but |
| 230 | | in a way that makes sense and preserves the way portfiles are expected |
| 231 | | to behave (which the current portgroup doesn't). |
| 232 | | |
| 233 | | Classification: medium[[BR]] |
| 234 | | Programming languages: Tcl, C[[BR]] |
| 235 | | Potential mentor: TBD |
| | 210 | Integrate the [[source:trunk/dports/_resources/port1.0/group/muniversal-1.0.tcl|muniversal portgroup]] into base. Not just a direct copy-and-paste, but in a way that makes sense and preserves the way portfiles are expected to behave (which the current portgroup doesn't). |
| | 211 | |
| | 212 | * Difficulty: Medium |
| | 213 | * Languages: Tcl, C |
| | 214 | * Potential mentors: TBD |
| 254 | | An interactive tool would ask for user input to resolve many situations |
| 255 | | that cause port(1) to simply error out. For example, if you try to |
| 256 | | install a port and one of its dependencies conflicts with something |
| 257 | | already installed, it could ask if you want to deactivate the installed |
| 258 | | one and its dependents. |
| 259 | | |
| 260 | | Classification: medium[[BR]] |
| 261 | | Programming languages: Tcl, C[[BR]] |
| 262 | | Potential mentor: TBD |
| | 230 | An interactive tool would ask for user input to resolve many situations that cause port(1) to simply error out. For example, if you try to install a port and one of its dependencies conflicts with something already installed, it could ask if you want to deactivate the installed one and its dependents. |
| | 231 | |
| | 232 | * Difficulty: Medium |
| | 233 | * Languages: Tcl, C |
| | 234 | * Potential mentors: TBD |
| 282 | | * Improve MacPorts documentation (see #12048 for more info, and #36957 for a more specific example of a feature that needs documenting) |
| 283 | | * Improve MacPorts website |
| 284 | | * Custom Trac plugins (see [comment:ticket:38095:2 #38095:2] for a roundup of Trac-related issues) |
| 285 | | |
| 286 | | '''Note''': Pure documentation proposals are not allowed by Google. |
| 287 | | |
| 288 | | Classification: minor task[[BR]] |
| 289 | | Programming languages: php, python[[BR]] |
| 290 | | Potential mentors: TBD |
| | 254 | |
| | 255 | Improve MacPorts [query:status!=closed&component=guide|server/hosting|website|wiki documentation, website and Trac system]. Note that pure documentation proposals are not allowed by Google. |
| | 256 | |
| | 257 | * Difficulty: Easy to difficult |
| | 258 | * Languages: PHP, Python |
| | 259 | * Potential mentors: TBD |
