Changes between Version 191 and Version 192 of SummerOfCode
- Timestamp:
- Mar 20, 2013, 6:13:15 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SummerOfCode
v191 v192 34 34 }}} 35 35 36 === General Info ===36 === General info === 37 37 38 38 For future reference you may check the [http://www.google-melange.com/ Google SoC website]. You will find more information on their page on [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students]. … … 41 41 There are several things to consider. We are willing to support and mentor students who want to gain an experience by working on The MacPorts Project. We have many ideas for potential internship subjects, yet we are open to anything that is both interesting and relevant to MacPorts. Motivated students do not necessarily need to know Tcl language beforehand, especially if they already know several script languages such as Python, Ruby, PHP or Perl. 42 42 43 === For the MacPorts project ===43 === For the MacPorts Project === 44 44 45 45 The best way to apply is to first make contact with us, either by sending a mail to the MacPorts developer [http://lists.macosforge.org/mailman/listinfo/macports-dev "mailing list"], to the potential mentors listed below, or to IRC members on #macports on [http://freenode.net/ FreeNode]. … … 72 72 Please note that this list is absolutely '''not exclusive'''! If you have any idea about what you want to see improved in MacPorts, you are free to propose this as your own project. In any case, we recommend to talk to mentors before writing your application. 73 73 74 === Core Tasks ===74 === Core tasks === 75 75 76 76 ==== Binaries ==== #binaries … … 98 98 * Potential mentors: TBD 99 99 100 ==== MacPorts Port for self-management ==== #self-management100 ==== MacPorts port for self-management ==== #self-management 101 101 102 102 The MacPorts port should be the source for updating a user’s MacPorts installation. … … 121 121 * Potential mentors: TBD 122 122 123 ==== Read Packages from Python's PIP (pip2port) ==== #pip2port123 ==== Read packages from Python's PIP (pip2port) ==== #pip2port 124 124 125 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]]. … … 149 149 * Potential mentor: raimue 150 150 151 ==== Configuration and environment selftest ==== 151 ==== Configuration and environment selftest ==== #envcheck 152 152 153 153 Add a command to check current setup for common pitfalls (e.g. stuff in `/usr/local`), inspired by Homebrew’s `brew doctor` functionality. … … 234 234 * Potential mentors: TBD 235 235 236 ==== Portfiles ==== # Portfiles236 ==== Portfiles ==== #portfiles 237 237 238 238 Sweep through all Portfiles and look for useful opportunities to add more built-in Tcl functions that make Portfiles more (usefully) terse, powerful, flexible or easier to write. I'm sure there is an entirely family of helper functions yet to be written here. … … 244 244 === Secondary tasks === 245 245 246 ==== Task A1: Ports ====246 ==== Ports ==== #ports 247 247 248 248 Port additional packages to MacPorts and cleanup or remove obsolete ports. … … 251 251 * Potential mentors: larryv 252 252 253 ==== Task A2: Documentation and Website ====253 ==== Documentation and website ==== #docs 254 254 255 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. … … 259 259 * Potential mentors: larryv 260 260 261 ==== Task A3: Shell Environment ==== #shell-environment261 ==== Shell environment ==== #shell-environment 262 262 263 263 Add support for providing basic and port-provided environmental services to users in the `~/.profile`, `~/.cshrc`, and `~/.xinitrc` files, so that instead of manipulating the user's .profile to modify certain paths, the installer could append "`source /opt/local/etc/bash.rc`" to the end of a user's .profile file and that bash.rc would source all the files in `/opt/local/etc/bash.d`.