Re: [GSoC 2016] Please Critique (Condition API - Related to Auth)

Thanks for the response, Tim. On Saturday, April 23, 2016 at 8:04:02 AM UTC+8, Tim Graham wrote: > > Hi Connor, > > Unfortunately we didn't have anyone sufficiently intrigued by your ideas > who wanted to mentor it. In case you'd like to try again next year, I'd > suggest to get involved in the

Re: [GSoC 2016] Please Critique (Condition API - Related to Auth)

Hi Connor, Unfortunately we didn't have anyone sufficiently intrigued by your ideas who wanted to mentor it. In case you'd like to try again next year, I'd suggest to get involved in the project and start submitting patches as you're able. Mentors are more wiling to invest their time to help so

Re: [GSoC 2016] Please Critique (Condition API - Related to Auth)

Hello all, Is there any chance I could get some feedback on why this was not accepted? I am a little surprised since Jacob Kaplan-Moss seemed to indicate to me over IRC that this was very likely to get an award for GSoC. Thanks, Connor On Saturday, March 26, 2016 at 12:47:52 AM UTC+8, Connor Boy

Re: [GSoC 2016] Please Critique (Condition API - Related to Auth)

> On your last point: This may be a very bad idea from the beginning, but I'd hope to experiment with making a wrapper object for form.cleaned_data whose (the wrapper object's) .__getattribute__() returns the value for that key in form.cleaned_data. For example: calling wrapper.name would get t

Re: [GSoC 2016] Please Critique (Condition API - Related to Auth)

This is excellent! Thank you for your comments, they are very helpful and thorough–far from amateur. I'll address some of them in no particular order, starting with: >The 'access' conditions must be passed or else any action will be rejected and no acknowledgement will be made that it had to do

Re: [GSoC 2016] Please Critique (Condition API - Related to Auth)

Hi Connor, Overall I find it pretty cool that work on this has been started. There are a few questions I'd like to ask on this proposal. In this example: class ReadingDelete(UserPassesTestMixin, DeleteView): model = Reading def test_func(self): user = self.reques

[GSoC 2016] Please Critique (Condition API - Related to Auth)

Hello Everyone, I would love to hear your critiques on my proposal <https://gist.github.com/cascadianblue/2856bea128dd1b3f4d0f> and original idea for GSoC 2016, hopefully before the deadline tomorrow–although I plan on pursuing it no matter what, so any critique at any time would be w

Re: [ GSOC 2016 ] Proposal for template profiling and optimization

I am really sorry to the community. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googleg

Re: [ GSOC 2016 ] Proposal for template profiling and optimization

On Thu, Mar 24, 2016 at 6:36 AM, Florian Apolloner wrote: > Sorry, but this is no proposal -- this is a bad joke. You will need to put > way more work into > Florian - While this is true, this is an excessively harsh way of delivering the news. We have no reason to believe that Girish is activel

Re: [ GSOC 2016 ] Proposal for template profiling and optimization

Sorry, but this is no proposal -- this is a bad joke. You will need to put way more work into it… On Wednesday, March 23, 2016 at 7:05:13 PM UTC+1, girish ramnani wrote: > > > After reading through the db source code of django I realized the > complexity of adding a standard interface for NoSQL

Re: [ GSOC 2016 ] Proposal for template profiling and optimization

Sorry, but this is no proposal -- this is a bad joke. You will need to put way more work into On Wednesday, March 23, 2016 at 7:05:13 PM UTC+1, girish ramnani wrote: > > > After reading through the db source code of django I realized the > complexity of adding a standard interface for NoSQL col

[ GSOC 2016 ] Proposal for template profiling and optimization

After reading through the db source code of django I realized the complexity of adding a standard interface for NoSQL column database, and i realized that it will require more than summer (for me). Also the changes in the framework were affecting many parts such as migrations,meta ,forms etc .

Re: GSoC 2016: Draft Proposal on SQLAlchemy Integration with django

Hi Tim, I have been sick for few days so couldn't work fully on the proposal. To give you have some idea on what I will be doing: * creating a django-sqlalchemy package like flask-alchemy/pyramid_alchemy which user can use on any regular django project under installed app. The package will nee

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

I agree with Jani that you should think about trying to make the proposal accommodate different JavaScript frameworks. You might look at https://github.com/jrief/django-angular, for example, for inspiration. Just thinking about what problems Django should be trying to solve, I'm wondering if cl

Re: GSoC 2016: Draft Proposal on SQLAlchemy Integration with django

I've never used SQLAlchemy myself, so I can't really comment on it without the technical details of what you would actually be doing. On Friday, March 18, 2016 at 8:11:12 AM UTC-4, Asif Saifuddin wrote: > > Hi, > > I have been working for preparing a proposal on SqlAlchemy integration > with dja

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

On 20.03.2016 14:59, Lover Di wrote: Hi, I have been working for preparing a proposal about a new feature for Django. I'm posting my draft proposal to Gist and want to know my idea is OK or not. So I can proceed with the right approach. Any suggestions or advice are welcome. Abstract of m

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

I don't have enough enough knowledge on how GSoC works and what the django team expects from people proposing projects but if it was me I would rather have a very well implemented, tested and with a good level of customization client side validation than two not so well features but that's up to

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

The client side validation is a very good idea, other frameworks such as ASP.NET MVC already has some basic client side validation tied to model fields (equivalent to django forms) and also provides a very easy way to add custom javascript validation and tie to the model/form. For the second pa

[GSoC 2016]Proposal: Validity check at client and dynamic form framework

Hi, I have been working for preparing a proposal about a new feature for Django. I'm posting my draft proposal to Gist and want to know my idea is OK or not. So I can proceed with the right approach. Any suggestions or advice are welcome. Abstract of my proposal: - Automatically generate s

Re: [ GSOC 2016 ] providing standard interface for NoSQL databases

In the beginning I thought about making an api which supports column databases such as cassendra but would mean that i would need to first find commonalities between all 3 ( column , document and relational ) but such commonalities would be lesser and so finally i would require to create a sepa

GSoC 2016: Draft Proposal on SQLAlchemy Integration with django

Hi, I have been working for preparing a proposal on SqlAlchemy integration with django. While I haven't done with in detail proposal and in depth technical specs, I'm posting my very draft proposal to understand If the broader strokes of my approach are nearly OK and I should proceed with the c

Re: [ GSOC 2016 ] providing standard interface for NoSQL databases

There are two goals when it comes to document DB support. First goal is to allow usage of models written specifically for document oriented databases. This is something that should be possible to achieve even if there are some hard problems to solve. The other goal is to allow usage of any Django m

Re: [ GSOC 2016 ] providing standard interface for NoSQL databases

It would also be worthwhile looking into the prior art on this topic. We had a GSoC project for non-relational data stores a few years back, and came to the conclusion that it probably wasn’t viable. You can dig into the archives to find out why. If you’re interested in adding non-relational suppo

Re: [ GSOC 2016 ] providing standard interface for NoSQL databases

It sounds like by "NoSQL DBS" you mean specifically "Document store DBMS". Is this correct? (I'm sure most people know my rant about how "NoSQL" is a misnomer, and it's really "Non-relational" that people mean - it's not SQL per se they're avoiding, it's the relational model) The NoSQL/Non-

[ GSOC 2016 ] providing standard interface for NoSQL databases

Hello, I would like to propose providing a standard interface for NoSQL databases . Some the points to consider are: 1. The *Fields *which are used to define the schema of the sql databases can also be used to provide in No sql databases. 2. In NoSQL dbs ,developers usually store data

Re: GSoC 2016

The best thing you can do to improve your chances to be accepted as a Django GSoC student is to start contributing now. Read up on ​Django’s contribution documentation and make yourself known to the core team by your contributions

GSoC 2016

Hello! I'm brazilian software engineering student and am interested in contribute to django in GSoC. I would to contribute with https://code.djangoproject.com/wiki/SummerOfCode2016#Improvingthelesspopulardatabasebackends How can I get started to contribute? -- You received this message because

Re: GSOC 2016

ted on > contributing to Django and thereby proceed with GSOC 2016. Please guide! > > Thanks and regards > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this grou

GSOC 2016

Hi, I am a computer science undergraduate. I want to get started on contributing to Django and thereby proceed with GSOC 2016. Please guide! Thanks and regards -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django i