Re: [GSoC 2013] contribute to django-deployer for deploying django to PaaS easily

Hi Russell and Florian, A bit late to the party, but hopefully there's still time for this GSoC proposal to be considered. I'm the maintainer of django-deployer. It was initiated at the DjangoCon 2012 sprint and recently revisited at the PyCon 2013 spri

Re: [GSoC 2013] Better, smarter forms

Hi Nicholas, Thanks for the proposal. It's a good start, and with a little tuning, I think it would make a great project for the GSoC. As as noted on the other thread, there's a lot of overlap here with floppyforms, and with a previous GSoC project to make forms customisable. HTML5 widgets and F

Re: GSOC: Deadline soon!

Hi Nicholas, I agree that there's a lot of overlap between your proposal and django-floppyforms -- but I still think there's some scope for a very interesting GSoC project. There may be only 2 days left, but that's still time for a couple more revisions before the deadline. I'll leave some commen

Re: Ticket 19445

Hi Luke, On 05/01/2013 04:31 PM, Luke Plant wrote: > Can I get some feedback on what to do about ticket 19445? > > https://code.djangoproject.com/ticket/19445 > > I have re-opened this ticket because I don't think it was addressed > satisfactorily. I apologise in advance that this is a bit invol

Ticket 19445

Hi all, Can I get some feedback on what to do about ticket 19445? https://code.djangoproject.com/ticket/19445 I have re-opened this ticket because I don't think it was addressed satisfactorily. I apologise in advance that this is a bit involved! The fundamental problem is that the validation ro

Re: GSOC: Deadline soon!

Yes indeed! I heard about it around the April 27. With a few more days left, I might have been able to review my proposal, but I will simply concentrate on finding work this summer. I* *would still love to have my proposal chosen, but I cannot put all of my eggs in that basket. On Wed, May 1, 2013

Re: GSOC: Deadline soon!

On 05/01/2013 01:38 PM, Nicolas Bouliane wrote: > It seems that I have underestimated the barrier of entry to the Google > Summer of Code. With so many hoops to jump through and very little time > left, I will not play against the odds. I understand; it is late in the process to be starting on a p

Re: GSOC: Deadline soon!

It seems that I have underestimated the barrier of entry to the Google Summer of Code. With so many hoops to jump through and very little time left, I will not play against the odds. I still look forward to contributing to Django, but not as a GSoC student. On Wed, May 1, 2013 at 2:04 PM, Carl Me

Re: GSOC: Deadline soon!

On 05/01/2013 11:18 AM, Nicolas Bouliane wrote: > Reading the description of django-floppyforms, I realize most of these > features are overlapping with those in my proposal. > > What do you think would be advisable from that point? In general, I think your proposal would benefit from additional

Re: GSOC: Deadline soon!

On Wed, May 1, 2013 at 8:10 PM, Jacob Kaplan-Moss wrote: > On Wed, May 1, 2013 at 7:38 AM, Satinderpal Singh > wrote: >> I wish to be a part of GSoC, and i have a plan to improve some >> features of forms of the Django, like adding different formats such as >> tables with different layouts. Also

Re: GSOC: Deadline soon!

Reading the description of django-floppyforms, I realize most of these features are overlapping with those in my proposal. What do you think would be advisable from that point? On Wed, May 1, 2013 at 1:11 PM, Carl Meyer wrote: > On 05/01/2013 11:04 AM, Carl Meyer wrote: > > I was the mentor for

Re: GSOC: Deadline soon!

On 05/01/2013 11:04 AM, Carl Meyer wrote: > I was the mentor for that GSoC project, and the reason for its failure > is that the Django template language proved too slow for the > template-based system we proposed for rendering form widgets and form > layouts; form-rendering speed suffered by an or

Re: GSOC: Deadline soon!

That's what I gathered from the various tidbits of information, but I will try looking at the archives. It's a shame, because it was a fantastic idea. Even to this day, it's pretty hard to properly customize form elements. On Wed, May 1, 2013 at 1:04 PM, Carl Meyer wrote: > Hi Nicolas, > > On 0

Re: GSOC: Deadline soon!

Hi Nicolas, On 05/01/2013 10:52 AM, Nicolas Bouliane wrote: > I have done as suggested and submitted my proposal in the mailing list. > I heard about the Google Summer of Code /very/ recently, but hopefully > I'll be able to submit an accurate and sensible proposal on time! > > Coincidentally, I

Re: GSOC: Deadline soon!

I have done as suggested and submitted my proposal in the mailing list. I heard about the Google Summer of Code *very* recently, but hopefully I'll be able to submit an accurate and sensible proposal on time! Coincidentally, I am also proposing changes to the Forms API, and I must say it is ver

[GSoC 2013] Better, smarter forms

Linked here is my proposal for the 2013 Google Summer of Code. As suggested by Jacob Kaplan-Moss, I am in the process of reviewing it to include timelines and more detailed information about my skillset. Nonetheless, I would really appreciate to have your feedback regarding the propositions con

Re: GSOC: Deadline soon!

On Wed, May 1, 2013 at 7:38 AM, Satinderpal Singh wrote: > I wish to be a part of GSoC, and i have a plan to improve some > features of forms of the Django, like adding different formats such as > tables with different layouts. Also some improvements in the default > form settings in the Django, l

Re: GSOC: Deadline soon!

On Tue, Apr 30, 2013 at 12:12 PM, Andrew Godwin wrote: > Hi everyone, > > It's great to see all the GSOC proposals on the list and the feedback being > useful, but I feel I should remind you all that the deadline is this Friday, > May 3rd, at 7pm UTC (so 11am if you're on the west coast of the US,

Re: Test failures under Oracle

Hi, now that the 1.6 release plan is out, I'd like to push this topic again. If you are using Oracle, now is the time to fix those bugs. Personally I am toying with the idea of dropping Oracle support from core if we can't ensure it's quality. Regards, Florian -- You received this message be

Re: design decisions for django-mssql: (switching on autocommit and remote proxy) advice wanted.

On 1 mai 2013, at 02:18, Russell Keith-Magee wrote: > On Tue, Apr 30, 2013 at 9:45 PM, VernonCole wrote: > 1) The transaction logic will change drastically for django 1.6. For the > supported backends it makes good sense to simply change that in the > repository. However, it is reasonable to e