Please note:The SCons wiki is now restored from the attack in March 2013. All old passwords have been invalidated. Please reset your password if you have an account. If you note missing pages, please report them to webmaster@scons.org. Also, new account creation is currently disabled due to an ongoing spam flood (2013/08/27).
Differences between revisions 4 and 5
Revision 4 as of 2007-03-30 22:17:20
Size: 2062
Editor: cpe-24-161-165-15
Comment: Mark which advertisements were done
Revision 5 as of 2008-03-12 02:47:01
Size: 2065
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * --(Gather the information about what should be contained in a proposal. It's currently scattered and needs to be collected in one place.)-- [2007-Feb-18: Done, at least a [:GSoC2007/Proposal:solid draft] - JGN]  * --(Gather the information about what should be contained in a proposal. It's currently scattered and needs to be collected in one place.)-- [2007-Feb-18: Done, at least a [[GSoC2007/Proposal|solid draft]] - JGN]
Line 13: Line 13:
  * [:SconsProjects:Projects/companies that use SCons].   * [[SconsProjects|Projects/companies that use SCons]].
Line 26: Line 26:
   * [:SconsProjects:Projects/companies that use SCons], both web pages and mailing lists.    * [[SconsProjects|Projects/companies that use SCons]], both web pages and mailing lists.

Checklist for Google Summer of Code 2007

  • Gather the information about what should be contained in a proposal. It's currently scattered and needs to be collected in one place. [2007-Feb-18: Done, at least a solid draft - JGN]

  • Identify mentors right away [2007-Mar-8 sample done]

  • Possibly create a mentors@scons mailing list if we have enough. [2007-Feb-22 done]

  • Get ideas written up sooner and figure out how to write better task suggestions.

  • Mine for ideas wherever we can:
    • Ideas from last year.

    • Requests for enhancements and new features in the issues database.

    • Defects (bugs) in the issues database.

    • Advertisements on scons-dev and especially on scons-users mailing lists.

    • Advertisements on scons.org and scons.tigris.org web pages.
    • Projects/companies that use SCons.

    • Where else? Update SummerOfCode if other sources are found so that we won't forget them in future.

  • Be prepared for Google's announcement:
    • Have the web pages done before the application period so Google can audit them.

    • Get our application in to Google immediately, so they have plenty of time to look us over and confirm that we are a viable candidate.

    • Use a name that better says what we do [2007-Mar-8 done]

  • Advertise our participation to drum up more submissions. We will be listed on Google's own heavily-advertised web pages, but there are plenty of other places:
    • Mailing lists (scons-users primarily, but also scons-dev).

    • www.scons.org and scons.tigris.org web pages.

    • Related third-party sources:
      • tigris.org
      • python.org (they mention Python-powered projects in their own SoC pages)
      • sourceforge.net (although that's a tenuous connection)
      • Projects/companies that use SCons, both web pages and mailing lists.

    • Where else? Update SummerOfCode if other sources are found so that we won't forget them in future.

GSoC2007/CheckList (last edited 2008-03-12 02:47:01 by localhost)