Changes between Version 2 and Version 3 of SummerOfCode2018


Ignore:
Timestamp:
03/22/2018 10:18:59 AM (12 months ago)
Author:
Adam (Chainz) Johnson
Comment:

fix some typos

Legend:

Unmodified
Added
Removed
Modified
  • SummerOfCode2018

    v2 v3  
    3030Don'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.
    3131
    32 We're accepting any GSOC proposal that fits one of the following three categ.ories:
     32We're accepting any GSOC proposal that fits one of the following three categories:
    3333
    3434 * Work on Django itself - such as the ORM, forms, etc. This is what we've traditionally accepted GSoC entries in.
     
    7373Quoting Loic on the [https://code.djangoproject.com/ticket/22298 ticket]: "My biggest issue with it is that it's a very naive approach to a complicated problem. It doesn't really fit with today's development practices where a project can easily grow to hundreds of static assets, where javascript offers concepts like AMD, where CSS gained preprocessors like LESS or SASS and where files are concatenated for performance.
    7474
    75 Having each input widget pull it's own assets can also be a performance footgun, and IMO it's hardy something we should recommend."
     75Having each input widget pull its own assets can also be a performance footgun, and IMO it's hardy something we should recommend."
    7676
    7777You will need to come up with a design here. There are a variety of third-party libraries from which you might glean best practices however the frontend tech world is currently in a state of reinvention so it might be hard to develop a suitable API that's suitable now but not in the future.
Back to Top