[MacPorts] SummerOfCode modified

MacPorts noreply at macports.org
Tue Mar 19 19:05:38 PDT 2013 

Page "SummerOfCode" was changed by larryv at macports.org
Diff URL: <https://trac.macports.org/wiki/SummerOfCode?action=diff&version=188>
Revision 188
Comment: format all the things
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCode
=========================================================================
--- SummerOfCode (version: 187)
+++ SummerOfCode (version: 188)
@@ -1,8 +1,8 @@
-= Google Summer of Code =
+= Google Summer of Code 2013 =
 
 [[PageOutline]]
 
-This is the main tracking page for MacPorts' Google [http://code.google.com/soc/ "Summer of Code"].
+This is the main tracking page for MacPorts’ [http://code.google.com/soc/ Google Summer of Code].
 
 [[Image(http://3.bp.blogspot.com/-couzpJZp3j0/URAgWOuBZ6I/AAAAAAAAAI8/CnlGEuPIL9M/s1600/GSoC+2013+logo.jpg, 300, link=http://www.google-melange.com/, title=Creative Commons Attribution-Noncommercial-No Derivative Works 3.0)]]
 
@@ -10,16 +10,12 @@
 
 == Applications for SoC ==
 
-{{{
+The window for submitting mentoring organization applications is '''18 March 19:00 UTC — 29 March 19:00 UTC'''.
+
+{{{
+#!comment
 #!div style="clear:left; display:block; width:100%; margin:0; padding:0;"
- 29 March is the mentoring organization application deadline. It starts March 18th.
-}}}
-
-{{{
-#!comment
-#!div style="clear:left; display:block; width:100%; margin:0; padding:0;"
- Unfortunately we have not been accepted for GSoC 2013. However, any contributions and enhancement proposals are welcome! Please see [http://guide.macports.org/#development the guide] and subscribe to
- the MailingLists!
+Unfortunately we have not been accepted for GSoC 2013. However, any contributions and enhancement proposals are welcome! Please see [http://guide.macports.org/#development the guide] and subscribe to the MailingLists!
 }}}
 
 {{{
@@ -49,25 +45,25 @@
 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].
 
 What we expect from students for their applications:
- * Write your own abstract and proposal, copying text from this idea page is not enough.
- * Show us that you fully understand your task and know what you want to do over the summer.
- * At best, include a short weekly roadmap covering how you would work on the task.
+* Write your own abstract and proposal, copying text from this idea page is not enough.
+* Show us that you fully understand your task and know what you want to do over the summer.
+* At best, include a short weekly roadmap covering how you would work on the task.
 
 What you should do before handing in an application:
- * Get familiar with the MacPorts project resources. Especially [GetMacPortsSource check out the code] and [http://guide.macports.org read the guide].
- * Read the [http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html Tcl Tutorial]
- * 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.
- * '''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.
+* Get familiar with the MacPorts project resources. Especially [GetMacPortsSource check out the code] and [http://guide.macports.org read the guide].
+* Read the [http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html Tcl Tutorial]
+* 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.
+* '''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.
 
 == Mentors ==
 
 The following committers have agreed to be mentors for SoC 2013 (append @macports.org for e-mail)
 
 ||= Name =||= Email =||= Area =||
-||Jeremy Lavergne || snc || Administrator ||
-||Clemens Lang || cal || Backup Admin ||
-||Rainer Müller || raimue || Mentoring for base, port groups, ports, ... ||
-||Lawrence Velázquez || larryv || Backup to the backup admin; mentoring for port[group]s, documentation, website ||
+||= Jeremy Lavergne =|| snc || Administrator ||
+||= Clemens Lang =|| cal || Backup Admin ||
+||= Rainer Müller =|| raimue || Mentoring for base, port groups, ports, ... ||
+||= Lawrence Velázquez =|| larryv || Backup to the backup admin; mentoring for port[group]s, documentation, website ||
 
 == Tasks ==
 
@@ -79,90 +75,86 @@
 
 ==== Binaries ==== #binaries
 
-MacPorts provides binaries but needs several enhancements. This task would include updating the chroot mechanism (ceased being functional with Snow Leopard) and adding support for variants.
-
-See also [wiki:MPAB MacPorts AutoBuild].
-
-Classification: relatively challenging to challenging task[[BR]]
-Programming language: Tcl[[BR]]
-Potential mentors: TBD
+MacPorts provides binaries but needs several enhancements. This task would include updating the chroot mechanism (ceased being functional with Snow Leopard) and adding support for variants. (See also [[MPAB|MacPorts AutoBuild]].)
+
+* Difficulty: Relatively challenging to challenging
+* Languages: Tcl
+* Potential mentors: TBD
 
 ==== Check for software update / ports needing upgrade ==== #livecheck
 
 The livecheck mechanism could be extended to automatically send reports when ports are outdated, similar to how the lint mechanism sends reports on portfile commits.
 
-Classification: easy[[BR]] 
-Programming languages: Tcl[[BR]] 
-Potential mentor: TBD 
+* Difficulty: Easy
+* Languages: Tcl
+* Potential mentors: TBD 
 
 ==== Dependencies ==== #dependencies
 
-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).
-
-Classification: very challenging task[[BR]]
-Programming languages: Tcl and C[[BR]]
-Potential mentors: TBD
+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).
+
+* Difficulty: Very challenging
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== MacPorts Port for self-management ==== #self-management
 
-The MacPorts port should be the source for updating a user's MacPorts
-installation.
-
-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
-
-Classification: challenging task[[BR]]
-Programming languages: Tcl and C[[BR]]
-Potential mentor: TBD
+The MacPorts port should be the source for updating a user’s MacPorts installation.
+
+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
+
+* Difficulty: Challenging
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Perl modules integration from CPAN ==== #cpan2port
 
-There has been [browser:contrib/cpan2port an attempt] to write a script for automatic generation of Portfiles from CPAN. This would simplify the maintenance of Perl modules in MacPorts. Revive this project and finish the script or rewrite it.
+There has been [[browser:contrib/cpan2port|an attempt]] to write a script for automatic generation of Portfiles from CPAN. This would simplify the maintenance of Perl modules in MacPorts. Revive this project and finish the script or rewrite it.
 
 Resources:
- * http://www.gentoo.org/proj/en/perl/g-cpan.xml
- * http://search.cpan.org/~bingos/CPANPLUS-0.9001/bin/cpan2dist
- * http://packages.debian.org/stable/dh-make-perl
-
-Classification: easy to medium task[[BR]]
-Programming languages: Perl and probably Tcl[[BR]]
-Potential mentor: TBD
+* http://www.gentoo.org/proj/en/perl/g-cpan.xml
+* http://search.cpan.org/~bingos/CPANPLUS-0.9001/bin/cpan2dist
+* http://packages.debian.org/stable/dh-make-perl
+
+* Difficulty: Easy to medium
+* Languages: Perl, probably Tcl
+* Potential mentors: TBD
 
 ==== Read Packages from Python's PIP (pip2port) ==== #pip2port
 
-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].
-
-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.
-
-The [browser:contrib/portfile-gen/portfile-gen portfile generator] may or be helpful.
-
-Classification: medium task[[BR]]
-Programming languages: Tcl, Python, C[[BR]]
-Potential mentor: snc
+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]].
+
+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.
+
+The [[browser:contrib/portfile-gen/portfile-gen|portfile generator]] might be helpful.
+
+* Difficulty: Medium
+* Languages: Tcl, Python, C
+* Potential mentors: snc
 
 ==== Read packages from other various package managers ==== #foo2port
 
 As above with the pip2port proposal, except with other package managers, such as [http://opam.ocamlpro.com/ opam] for ocaml packages, [http://www.haskell.org/cabal/ cabal] for haskell, [http://luarocks.org/ luarocks] for lua, [https://npmjs.org/ npm] for node.js, and so on.
 
-Classification: medium task[[BR]]
-Programming languages: Tcl, C, ocaml, haskell, lua, javascript, any other languages that come with their own package manager[[BR]]
-Potential mentor: TBD
+* Classification: Medium
+* Languages: Tcl, C, OCaml, Haskell, Lua, Node.js, etc.
+* Potential mentors: TBD
 
 ==== Automatic testing ==== #testing
 
-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.
-
-Classification: relatively easy to very challenging[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: raimue
+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.
+
+* Difficulty: Relatively easy to very challenging
+* Languages: Tcl, C
+* Potential mentor: raimue
 
 ==== Configuration and environment selftest ====
 
-Add a command to check current setup for common pitfalls (e.g. stuff
-in /usr/local), inspired by 'brew doctor' from Homebrew.
-
-Classification: easy[[BR]]
-Programming languages: Tcl, shell[[BR]]
-Potential mentor: TBD
+Add a command to check current setup for common pitfalls (e.g. stuff in `/usr/local`), inspired by Homebrew’s `brew doctor` functionality.
+
+* Difficulty: Easy
+* Languages: Tcl, shell
+* Potential mentors: TBD
 
 
 ==== Improve startupitem code ==== #startupitem
@@ -170,124 +162,101 @@
 MacPorts has the ability to automatically generate startup items for the current platform. For OS X, these are plist files for launchd which will be installed as `/Library/LaunchDaemons/org.macports.*.plist`. The current code would need a little care and could make use of options which have been added in recent releases of launchd.
 
 Features that could be useful include (but are not limited to):
- * Not using daemondo if the daemon works fine under launchd without it
- * Ability to install multiple plists
- * Support for LaunchAgents as well as LaunchDaemons
- * Installing plists in ~/Library for non-root installs if the user wants
- * only modify specific XML tags to avoid clobbering additions by user
-
-Classification: easy[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+* Not using daemondo if the daemon works fine under launchd without it
+* Ability to install multiple plists
+* Support for LaunchAgents as well as LaunchDaemons
+* Installing plists in ~/Library for non-root installs if the user wants
+* only modify specific XML tags to avoid clobbering additions by user
+
+* Difficulty: Easy
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Dependency calculation using SAT solving ==== #depcalc
 
 Implement an interface to a [http://www.mancoosi.org/cudf/ Common Upgradeability Description Format]-based SAT solver and print a summary before executing the calculated plan. If time permits you can try different solvers or implement rolling back on failure.
 There is also a [browser:trunk/dports/devel/libCUDF/Portfile libCUDF] port that might be helpful to look at.
 
-Classification: challenging task[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: cal
+* Difficulty: Challenging
+* Languages: Tcl, C
+* Potential mentors: cal
 
 ==== Reclaim disk space ==== #reclaim
 
-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)
-
-Classification: easy[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+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)
+
+* Difficulty: Easy
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Parallel execution ==== #parallel
 
-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)
-
-Classification: very challenging[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+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)
+
+* Difficulty: Very challenging
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Trace mode ==== #tracemode
 
-Improve trace mode to the point where developers (and the build
-server) could run with it always turned on.
-
-Classification: medium[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+Improve trace mode to the point where developers (and the build server) could run with it always turned on.
+
+* Difficulty: Medium
+* Programming languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Migrate muniversal into base (lipo merging) ==== #muniversal
 
-Integrate muniversal 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).
-
-Classification: medium[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+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).
+
+* Difficulty: Medium
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Fetching from version control ==== #fetchtypes
 
-Make cvs/svn/git/hg/bzr fetch types checkout into the distfiles dir
-and then export into the work dir, to avoid having to re-fetch after
-cleaning the work dir. See #16373 for more information.
-
-Classification: easy[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+Make cvs/svn/git/hg/bzr fetch types checkout into the distfiles dir and then export into the work dir, to [[ticket:16373|avoid having to re-fetch]] after cleaning the work dir.
+
+* Difficulty: Easy
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Interactive port command ==== #interactive
 
-Write an interactive command-line tool that can be used instead of the
-non-interactive port(1). 
+Write an interactive command-line tool that can be used instead of the non-interactive port(1). 
 
 The current port(1) should be viewed as batch mode reading from stdin.
 
-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.
-
-Classification: medium[[BR]]
-Programming languages: Tcl, C[[BR]]
-Potential mentor: TBD
+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.
+
+* Difficulty: Medium
+* Languages: Tcl, C
+* Potential mentors: TBD
 
 ==== Portfiles ==== #Portfiles
 
 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.
 
-Classification: medium task[[BR]]
-Programming language: Tcl[[BR]]
-Potential mentor: TBD
-
-=== Additional tasks ===
+* Classification: Medium
+* Language: Tcl
+* Potential mentors: TBD
+
+=== Secondary tasks ===
 
 ==== Task A1: Ports ====
- * Porting of additional packages to MacPorts
- * Cleanup and/or remove obsolete ports
-
-Classification: medium task[[BR]]
-Potential mentors: TBD
+
+Port additional packages to MacPorts and cleanup or remove obsolete ports.
+
+* Difficulty: Medium
+* Potential mentors: TBD
 
 ==== Task A2: Documentation and Website ====
- * Improve MacPorts documentation (see #12048 for more info, and #36957 for a more specific example of a feature that needs documenting)
- * Improve MacPorts website
- * Custom Trac plugins (see [comment:ticket:38095:2 #38095:2] for a roundup of Trac-related issues)
-
-'''Note''': Pure documentation proposals are not allowed by Google.
-
-Classification: minor task[[BR]]
-Programming languages: php, python[[BR]]
-Potential mentors: TBD
+
+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.
+
+* Difficulty: Easy to difficult
+* Languages: PHP, Python
+* Potential mentors: TBD
 
 ==== Task A3: Shell Environment ==== #shell-environment
 
@@ -295,8 +264,8 @@
 
 This task alone is most probably not enough for the whole Summer Of Code.
 
-Classification: easy task [[BR]]
-Potential mentors: raimue
+* Difficulty: Easy
+* Potential mentors: raimue
 
 
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/SummerOfCode>
MacPorts <http://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'SummerOfCode' page.
If it was not you, please report to .

More information about the macports-changes mailing list