Re: GSOC-2015, Newbie, Want to contribute to Django development and also try my hand in GSOC

[Cody Scott]

You are not too late for GSOC 2015. 

Here is some more information with potential projects. 
https://code.djangoproject.com/wiki/SummerOfCode2015

On Thursday, 12 March 2015 07:23:42 UTC-4, Saurabh Jain wrote:
>
> Hello,
>  My name is Saurabh Jain, currently pursuing bachelors degree in 
> Computer Science. I want to contribute to the development of Django. I have 
> worked upon Django as user but have no experience related to its 
> development. Can anyone please help me to get started with it ? I know that 
> its too late to start now for GSOC 2015, but still I would like to 
> contribute to the organisation no matter whether I get selected or not.
>
> Thanks   
>

-- 
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...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/bfb10e00-5983-4167-844c-3c5bd09b67a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Why can't you have a list in a model?

[Cody Scott]

Why can't you store lists in a model?

You can create another model and use a foreign key to that.

But if you just want to put one CharField in that model and that model 
doesn't really have a name that fits well with your app, you should be able 
to just specify that you are going to have a list of string in the model.


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

How do features get decided for a release?

[Cody Scott]

I know that I can look at the 1.7 release notes to see what is to come in 
the next release.

How do django developers decide what features to work on?

Is there a minimum time between releases?

Is there a minimum quota for fixed bugs for a release?

Is there ever a poll to see which features the community wants?

Is there another way that developers get what the community wants?


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b4759c89-e99d-4928-8a22-7694ef903de0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How do features get decided for a release?

[Cody Scott]

How do you decide which version to put a feature in?

Why wasn't migrations in 1.6?


On Thu, Oct 24, 2013 at 12:01 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:

>
> On Thu, Oct 24, 2013 at 10:45 AM, Cody Scott wrote:
>
>> I know that I can look at the 1.7 release notes to see what is to come in
>> the next release.
>>
>> How do django developers decide what features to work on?
>>
>> Is there a minimum time between releases?
>>
>> Is there a minimum quota for fixed bugs for a release?
>>
>> Is there ever a poll to see which features the community wants?
>>
>> Is there another way that developers get what the community wants?
>>
>
> Hi Cody,
>
> Django development -- like most open source development -- doesn't happen
> in the same way as commercial development. We don't sit down, decide
> features that we want, develop a plan, track progress against that plan,
> and deliver those features.
>
> We're an entirely volunteer driven organisation, and the thing about
> volunteers is that you don't have any carrots or sticks to drive the
> development process. I can't compel anyone to work on anything -- and if I
> punish people for not meeting my expectations, I'll probably find that my
> volunteers go away pretty quickly.
>
> Open source development means you have to recalibrate your thinking around
> how software gets developed.
>
> There isn't a minimum time between releases. We put out releases when we
> need to. We've historically put out point releases on a roughly annual
> timeframe, because that's matched our rate of development (and takes into
> account how much ; however, the 1.6 release is on track to be a 7 month
> development process.
>
> There isn't a minimum quota of bugs. The bugs that get fixed are the bugs
> that people provide patches for, and the core team can find sufficient time
> to review and commit.
>
> There isn't any sort of formal process for deciding what will be added.
> The features that are added are the features that volunteers feel
> sufficiently motivated to drive through the development process. Sometimes
> this means that features stay on the todo list for a long time, and
> sometimes it means that a feature goes from concept to completion in a
> matter of weeks.
>
> In essence, the community is getting *exactly* what it wants… in the sense
> that anyone who wants something bad enough is able to put in the time to
> develop a feature, and will drive it to completion.
>
> So - to answer the specific question -- Django 1.6 is about to be released
> (we just pushed our release candidate, which means the final is a matter of
> a week or so away). Django 1.7 is currently in feature development. The
> only features we can guarantee will be in Django 1.7 are those that we've
> already committed (most notably, migrations, and a couple of others that
> are listed in the release notes). I can take a guess at a couple of others
> that are *likely*, based purely upon the work that I myself am doing, and
> what I've heard other core team members talking about. However, until any
> of that code is committed, it's all speculative.
>
> Yours,
> Russ Magee %-)
>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-developers/M6ny4k476dk/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAJxq84-agEjQE35sUUyj%3D4WKAnBbovaJKG8Ag6V35%2B%3DAdMBQBQ%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAFUqbeCtP643hqk5TpP341xBdqiMxnpeAKhNSR%3DeoLXaF5mYJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Model Docs Questions

[Cody Scott]

I've been reading the documentation and have some questions about certain 
behaviour. 

1
Why does calling .clear() on a intermediate model, delete the intermediate 
models?

source

>>> Membership.objects.all()
[, ]
>>> beatles.members.clear()
>>> Membership.objects.all()
[]

I thinkk that the Membership models should still exist but just not be 
associated with the Group model.

2
Why can't you call create on a intermediate model and pass the required 
fields?
For example.
>>> john = Person.objects.create(name="John Lennon") 
>>> beatles.members.create(person=john, date_joined=date(1960, 8, 1), 
invite_reason="Wanted to form a band.")

3
Why do Q objects use '&', '|' and '~' for AND, OR and NOT when python uses 
'and', 'or' and 'not'? 
source

4
Due to how inheritance works, you have to set both pk and id to None: 

django_blog.pk = None 
django_blog.id = None 
django_blog.save() # django_blog.pk == 4

source

Why is this?

5

When using aggregate why do you get a dictionary instead of a value?

# Average price across all books. 
>>> from django.db.models import Avg 
>>> Book.objects.all().aggregate(Avg('price')) 
{'price__avg': 34.35}

So you have to do 
average_price = Book.objects.all().aggregate(Avg('price')) ['price__avg']

6.

Why do Max, Sum, etc take a string a parameter while .filter() does not? 
Are they inconsistent to easier tell them apart?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/87e6de2a-72bb-476f-bbec-610f7fefa41f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

GSoC Project Ideas

[Cody Scott]

The Google Summer of Code 2014 Project Ideas seems to be outdated. 

https://code.djangoproject.com/wiki/SummerOfCode2014


Test framework cleanup - Is this still relevant with the new Django 1.6 
django-discover-runner?Improved error reporting - Is this still relevant 
with the new validations in Django 1.7?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/55926f41-5855-4da4-975b-2c699e8e065b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.