Differences between revisions 3 and 13 (spanning 10 versions)
⇤ ← Revision 3 as of 2009-03-08 15:00:43 →
Size: 1877
Editor: schilly
Comment:
← Revision 13 as of 2012-03-17 19:39:36 → ⇥
Size: 4157
Editor: schilly
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from gsoc09
Line 10: Line 11:
== Note: == == Notes: ==
Line 12: Line 13:
We should take care to define delivarables for the items below. These should be doable with less than 3 months of work. We should take care to define deliverables for the items below. These should be doable with less than 3 months of work.

Here is what the FAQ says for "Ideas" lists:

  An "Ideas" list should be a list of suggested student projects. This list is meant to introduce contributors to your project's needs and to provide inspiration to would-be student applicants. It is useful to classify each idea as specifically as possible, e.g. "must know Python" or "easier project; good for a student with more limited experience with C++." If your organization plans to provide an application template, you should include it on your Ideas list.

 Keep in mind that your Ideas list should be a starting point for student applications; we've heard from past mentoring organization participants that some of their best student projects are those that greatly expanded on a proposed idea or were blue-sky proposals not mentioned on the Ideas list at all.


And this is from the [[http://groups.google.com/group/google-summer-of-code-announce/web/notes-on-organization-selection-criteria|notes on organization selection criteria]]:

 2) Do the projects on your ideas list look feasible for student developers? Is your ideas list thorough and well-organized? Your ideas list is the first place that student participants are going to look to get information on participating in GSoC, so putting a lot of effort into this list is a good thing(tm). One thing we noticed and really appreciate is how some organizations classified their ideas by easy, medium and difficult, and specifically listed the skills and background required to complete a given task. It might also be cool to expand on each idea with some places to get started research-wise (pointers to documentation or specific bugs), as well as the impact finishing a given idea will have for the organization.
Line 25: Line 38:

    The Sage notebook is a web-based AJAX application for multiple users. It allowes them to sign in to their worksheets, stored on the server. The authentication is handled by Sage. It would be very useful to connect the authentication mechanism with existing sytems like LDAP, Kerberos, Active Directory - possibly supporting single-side on systems - or other systems like OpenID (i.e. use your google or yahoo! account to log in using https://www.google.com/accounts/o8/id or http://openid.yahoo.com/ )
Line 33: Line 43:
 * Enhance export capabilities create methods for well designed PDF, LaTeX (with or without SageTeX) or ODF output.
 * master-notebook, collection of other notebooks for a script or book.
 * Permanent hyperlinks between worksheets, independent of worksheet numbering, to support multi-worksheet documents (ie books)
 * enhance history and snapshot capabilities.
 * concurrent editing of one single document: only altered cells are updated and "collision" warnings issued if more than one change happens with appropriate methods to solve it
 * read/write permission management for groups with roles (teacher is able to read notebooks, but students are not able to read each others)
 * ...
Line 34: Line 51:
 * Add task here === Community Tools ===
 * Enhance publishing of Notebook documents (i.e. like on [[http://www.sagenb.org/pub]]).
   * Wiki-like platform for editing notebooks for publishing mathematical, physical, statistical and other content.
   * tagging support, listings by tags
   * efficiently exchange usage examples, tips and ideas.

Google Summer of Code 2009

Important Dates

See the GSoC2009 FAQ for the timeline here http://code.google.com/opensource/gsoc/2009/faqs.html#0_1_timeline_5354032302481437_.

GSoC Sage Projects

All #numbers below refer to trac tickets.

Notes:

We should take care to define deliverables for the items below. These should be doable with less than 3 months of work.

Here is what the FAQ says for "Ideas" lists:

  • An "Ideas" list should be a list of suggested student projects. This list is meant to introduce contributors to your project's needs and to provide inspiration to would-be student applicants. It is useful to classify each idea as specifically as possible, e.g. "must know Python" or "easier project; good for a student with more limited experience with C++." If your organization plans to provide an application template, you should include it on your Ideas list.
  • Keep in mind that your Ideas list should be a starting point for student applications; we've heard from past mentoring organization participants that some of their best student projects are those that greatly expanded on a proposed idea or were blue-sky proposals not mentioned on the Ideas list at all.

And this is from the notes on organization selection criteria:

  • 2) Do the projects on your ideas list look feasible for student developers? Is your ideas list thorough and well-organized? Your ideas list is the first place that student participants are going to look to get information on participating in GSoC, so putting a lot of effort into this list is a good thing(tm). One thing we noticed and really appreciate is how some organizations classified their ideas by easy, medium and difficult, and specifically listed the skills and background required to complete a given task. It might also be cool to expand on each idea with some places to get started research-wise (pointers to documentation or specific bugs), as well as the impact finishing a given idea will have for the organization.

Notebook

The Sage notebook is an AJAX application similar to Google Documents that provides functionality for all mathematical software somewhat like Mathematica notebooks. It was written from scratch (in Javascript and Python) by the Sage development team, and has been used daily by thousands of people over the last year. It's one of the main killer features of Sage. This project is about improving the notebook. No special mathematical knowledge is required. Knowledge of Javascript, jQuery, Python, and general AJAX techniques is needed.

  • Authentication backend (ldap, kerberos?)
  • Refactoring
    • independent component of Sage
    • move to Django
  • Improvements to interact
  • Add support for making presentations
  • Enhance export capabilities create methods for well designed PDF, LaTeX (with or without SageTeX) or ODF output.
  • master-notebook, collection of other notebooks for a script or book.
  • Permanent hyperlinks between worksheets, independent of worksheet numbering, to support multi-worksheet documents (ie books)
  • enhance history and snapshot capabilities.
  • concurrent editing of one single document: only altered cells are updated and "collision" warnings issued if more than one change happens with appropriate methods to solve it
  • read/write permission management for groups with roles (teacher is able to read notebooks, but students are not able to read each others)
  • ...

Community Tools

  • Enhance publishing of Notebook documents (i.e. like on http://www.sagenb.org/pub).

    • Wiki-like platform for editing notebooks for publishing mathematical, physical, statistical and other content.
    • tagging support, listings by tags
    • efficiently exchange usage examples, tips and ideas.

Interfaces to Sage

Make it easier to call Sage from other applications.

  • Add task here

Potential Mentors

  • Add your name here

GSoC/2009 (last edited 2012-03-17 19:39:36 by schilly)