Changes between Version 5 and Version 6 of SummerOfCode2013

Timestamp:

Apr 12, 2013, 9:57:50 AM (11 years ago)

Author:

Andrew Godwin

Comment:

--

SummerOfCode2013

@@ -17 +17 @@
 Student application period opens April 22 and ends on May 3.
 
-If you'd like to get started on your proposal early, we'll be looking for a few things.  
+If you'd like to get started on your proposal early, we'll be looking for a few things. Note that we've widened our project scope this year! 
 
  * You'll need to have a concrete task in mind (some ideas are below) along with a solid idea of what will constitute "success" (you tell us).  
- * If your proposal is a single large feature, you'll need to present a detailed design specification. This proposal should be posted to [http://groups.google.com/group/django-developers django-developers], where it can be refined until it is accepted by the developer community.
+ * If your proposal is a single large feature, library or site, you'll need to present a detailed design specification. This proposal should be posted to [http://groups.google.com/group/django-developers django-developers], where it can be refined until it is accepted by the developer community.
  * We'll want to know a bit about you -- links to previous work are great, if any.  If you're proposing something ambitious, you'll need to convince us that you're up to the task.
  * You'll also need to provide us with a schedule, including a detailed work breakdown and major milestones so your mentor can know if and when to nag you :)
@@ -28 +28 @@
 Don't feel limited to the ideas below -- if you've got a cool project you want to work on, we'll probably be able to find you a mentor.  We plan on approving as many projects as we possibly can.
 
-'''Note: we're looking for projects that add value to Django itself - ''not'' application/CMS projects that use Django.'''
+We're accepting any GSOC proposal that fits one of the following three categories:
 
-You should also note that as far as proposals go, we don't make a distinction between a GSoC project and any other proposal for a new feature. When you contribute code, you will be expected to adhere to the same contribution guidelines as any other code contributor. This means you will be expected to provide extensive tests and documentation for any feature you add, you will be expected to participate in discussion on [http://groups.google.com/group/django-developers django-developers] when your topic of interest is raised. If you're not already familiar with [http://docs.djangoproject.com/en/dev/internals/contributing/ Django's contribution guidelines], now would be a good time to read them. 
+ * Work on Django itself - such as the ORM, forms, etc. This is what we've traditionally accepted GSoC entries in.
+ * Work on tools to support Django - the dashboard (https://dashboard.djangoproject.com/) is a good example of an existing tool that would have fitted into this category.
+ * Work on libraries that supplement or add new features to Django to ease development - South and Django Debug Toolbar are good examples of existing projects that would have fitted here.
+
+We're **not** looking for people to work on existing third-party libraries - we aren't able to guarantee commit access to them. We may allow an exception if a maintainer of the library in question agrees to help mentor beforehand.
+
+The broadening in scope is to allow people to work on new ideas to help Django development and developers without tying you down to having to implement it in the core codebase (and thus ruling out some projects that might otherwise be useful). We're still going to be strict with what we accept - you'll need to provide a strong use case for your idea and show that it would be useful to a majority of developers or significantly improve the development of Django itself.
+
+We're not looking for small groups of incremental updates - like "improve Django's Trac" - nor are we looking for impossible tasks, like "replace Trac with this brand new issue tracker I'm writing". What you propose should be achievable within the time period of GSoC and something the core developers can help mentor you on.
+
+Note that when you contribute code, you will be expected to adhere to the same contribution guidelines as any other code contributor. This means you will be expected to provide extensive tests and documentation for any feature you add, you will be expected to participate in discussion on [http://groups.google.com/group/django-developers django-developers] when your topic of interest is raised. If you're not already familiar with [http://docs.djangoproject.com/en/dev/internals/contributing/ Django's contribution guidelines], now would be a good time to read them - even if you're not applying to work on Django core directly, we'll still want the same level of contribution.
 
 == Communication ==