Fellow Report - January 16, 2015

[Tim Graham]

Triaged

---

https://code.djangoproject.com/ticket/26069 - Docs for 
MyModel._meta.get_fields_with_model() missing info about 'is_relation' 
(accepted)

https://code.djangoproject.com/ticket/26066 - Admin changelist could handle 
a table wider than the screen more elegantly (accepted)

https://code.djangoproject.com/ticket/26068 - Django 1.8: KEY constraint 
for parent model missing in m2m [regression] (worksforme)

https://code.djangoproject.com/ticket/26073 - Last-Modified http header not 
set to the latest last-mod in multi-maps sitemaps (duplicate)

https://code.djangoproject.com/ticket/26080 - Add field.on_delete to all 
relational fields (wontfix)

https://code.djangoproject.com/ticket/26076 - SessionBase's _hash method's 
variable key_salt need add a dot to be a complete class path (wontfix)

Authored



https://github.com/django/django/pull/5968 - Fixed #26048 -- Made admin 
selenium tests use implicitly_wait()

https://github.com/django/django/pull/5971 - Fixed #23868 -- Added support 
for non-unique django-admin options in docs.

https://github.com/django/djangoproject.com/pull/618 - Added 
CorporateMember.notes field.

https://github.com/django/djangoproject.com/pull/620 - Alphabetized 
corporate members page.

https://github.com/django/djangoproject.com/pull/622 - Added 'donation 
amount' to the corporate member signup form.

https://github.com/django/djangoproject.com/pull/623 - Limited docs to 
building only if source files have changed.

Reviewed/committed

--

https://github.com/django/django/pull/5560 - Fixed #25684 -- Made runserver 
use logging for request/response output.

https://github.com/django/django/pull/5951 - Fixed #25385 -- Allowed 
importing views.generic.View from views.View.

https://github.com/django/django/pull/5967 - Fixed #26071 -- Fixed crash 
with __in lookup in a Case expression.

https://github.com/django/django/pull/5602 - Fixed #25697 -- Made default 
error views error when passed a nonexistent template_name.

Reviews of core dev work


https://github.com/django/django/pull/5964 - Fixed #25858 -- Bound abstract 
model application relative relationships.

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1189233b-c064-4ffd-af60-4b20d2b0f614%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Report - January 16, 2015

[Tino de Bruijn]

Hi Tim,

Here a non-core-team perspective. Although I haven't worked on any Django
bugs or code lately, I do frequently read this mailinglist. It was nice to
see your weekly status updates (and Berker's), the updates and work on
release blockers and the releases themselves. I got the feeling Django
development has made a lot more continuous progress these last months.


Tino

On Tue, Jan 20, 2015 at 1:46 PM, Josh Smeaton 
wrote:

> Definitely. I don't think any of the patches I've written have sat without
> review for longer than a day or two. The turn around on feedback has been
> amazing. I really hope this program is picked up again. Thanks Tim and
> Berker.
>
> - Josh
>
>
> On Tuesday, 20 January 2015 17:16:39 UTC+11, Anssi Kääriäinen wrote:
>>
>> You can of course include what I wrote.
>>
>> A little known fact is that since DuTH I have committed two patches
>> myself, yet authored several patches my self. I have essentially stopped
>> using my commit bit. I did this mostly to test how a workflow where Django
>> contributors do not commit their patches themselves would work. I have to
>> say this has worked extremely well for me. My patches have been reviewed
>> and committed in timely manner. I hope the same is true for other
>> contributors, too.
>>
>>  - Anssi
>>
>> On Monday, January 19, 2015 at 7:21:17 PM UTC+2, Tim Graham wrote:
>>>
>>> Thanks, Anssi. By the way, we are compiling testimonials to help in the
>>> fundraising efforts. Do you mind if we include those two sentences from
>>> you? (feel free to add a couple more sentences if you like). If anyone else
>>> would like to share one, please send them my way. I am especially
>>> interested in non-core team members perspective on the program. Also, feel
>>> free to share any general feedback (positive or negative) -- even if you
>>> don't want it posted as a testimonial on the fundraising page. Thank you!
>>>
>>> On Monday, January 19, 2015 at 5:20:49 AM UTC-5, Anssi Kääriäinen wrote:

 On Friday, January 16, 2015 at 10:19:15 PM UTC+2, Tim Graham wrote:
>
> Here’s my final report for the 3 month fellowship pilot. I hope the
> DSF’s fundraising efforts will be successful and I’ll have an opportunity
> to "be back" soon. :-)
>

 From my point of view the fellowship pilot has been a huge success. The
 amount of tickets and patches worked on during the pilot is astounding.

 A very big thank you, and lets hope the fundraising program is
 successful.

  - Anssi

>>>  --
> 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/e1fca5db-f1d2-48dc-9905-391723803cb8%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CANQFsQD7-eMjv-5AxtVb%2B80WpTsWyxFT%3DFYYaf851EBAdnMvzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Report - January 16, 2015

[Josh Smeaton]

Definitely. I don't think any of the patches I've written have sat without 
review for longer than a day or two. The turn around on feedback has been 
amazing. I really hope this program is picked up again. Thanks Tim and 
Berker.

- Josh

On Tuesday, 20 January 2015 17:16:39 UTC+11, Anssi Kääriäinen wrote:
>
> You can of course include what I wrote.
>
> A little known fact is that since DuTH I have committed two patches 
> myself, yet authored several patches my self. I have essentially stopped 
> using my commit bit. I did this mostly to test how a workflow where Django 
> contributors do not commit their patches themselves would work. I have to 
> say this has worked extremely well for me. My patches have been reviewed 
> and committed in timely manner. I hope the same is true for other 
> contributors, too.
>
>  - Anssi
>
> On Monday, January 19, 2015 at 7:21:17 PM UTC+2, Tim Graham wrote:
>>
>> Thanks, Anssi. By the way, we are compiling testimonials to help in the 
>> fundraising efforts. Do you mind if we include those two sentences from 
>> you? (feel free to add a couple more sentences if you like). If anyone else 
>> would like to share one, please send them my way. I am especially 
>> interested in non-core team members perspective on the program. Also, feel 
>> free to share any general feedback (positive or negative) -- even if you 
>> don't want it posted as a testimonial on the fundraising page. Thank you!
>>
>> On Monday, January 19, 2015 at 5:20:49 AM UTC-5, Anssi Kääriäinen wrote:
>>>
>>> On Friday, January 16, 2015 at 10:19:15 PM UTC+2, Tim Graham wrote:

 Here’s my final report for the 3 month fellowship pilot. I hope the 
 DSF’s fundraising efforts will be successful and I’ll have an opportunity 
 to "be back" soon. :-)

>>>
>>> From my point of view the fellowship pilot has been a huge success. The 
>>> amount of tickets and patches worked on during the pilot is astounding.
>>>
>>> A very big thank you, and lets hope the fundraising program is 
>>> successful.
>>>
>>>  - Anssi
>>>
>>

-- 
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/e1fca5db-f1d2-48dc-9905-391723803cb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Report - January 16, 2015

[Anssi Kääriäinen]

You can of course include what I wrote.

A little known fact is that since DuTH I have committed two patches myself, 
yet authored several patches my self. I have essentially stopped using my 
commit bit. I did this mostly to test how a workflow where Django 
contributors do not commit their patches themselves would work. I have to 
say this has worked extremely well for me. My patches have been reviewed 
and committed in timely manner. I hope the same is true for other 
contributors, too.

 - Anssi

On Monday, January 19, 2015 at 7:21:17 PM UTC+2, Tim Graham wrote:
>
> Thanks, Anssi. By the way, we are compiling testimonials to help in the 
> fundraising efforts. Do you mind if we include those two sentences from 
> you? (feel free to add a couple more sentences if you like). If anyone else 
> would like to share one, please send them my way. I am especially 
> interested in non-core team members perspective on the program. Also, feel 
> free to share any general feedback (positive or negative) -- even if you 
> don't want it posted as a testimonial on the fundraising page. Thank you!
>
> On Monday, January 19, 2015 at 5:20:49 AM UTC-5, Anssi Kääriäinen wrote:
>>
>> On Friday, January 16, 2015 at 10:19:15 PM UTC+2, Tim Graham wrote:
>>>
>>> Here’s my final report for the 3 month fellowship pilot. I hope the 
>>> DSF’s fundraising efforts will be successful and I’ll have an opportunity 
>>> to "be back" soon. :-)
>>>
>>
>> From my point of view the fellowship pilot has been a huge success. The 
>> amount of tickets and patches worked on during the pilot is astounding.
>>
>> A very big thank you, and lets hope the fundraising program is successful.
>>
>>  - Anssi
>>
>

-- 
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/ba97fbc2-1849-4e24-b682-fb8bfdce305e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Report - January 16, 2015

[Carl Meyer]

On 01/19/2015 10:21 AM, Tim Graham wrote:
> Thanks, Anssi. By the way, we are compiling testimonials to help in the 
> fundraising efforts. Do you mind if we include those two sentences from 
> you? (feel free to add a couple more sentences if you like). If anyone else 
> would like to share one, please send them my way. I am especially 
> interested in non-core team members perspective on the program. Also, feel 
> free to share any general feedback (positive or negative) -- even if you 
> don't want it posted as a testimonial on the fundraising page. Thank you!

I can't provide a non-core-team perspective, but I'd certainly echo what
Anssi said - I think the program was a great success. I haven't put
together the stats to confirm this, but it definitely seemed to me that
the fellowship program resulted in more code review, faster turnaround
on pull requests and tickets, and much better adherence to a release
schedule than we've ever had before. I very much hope it returns (and my
company has just become a sponsor member of the DSF to help that happen.)

Feel free to use any of that as testimonial if it's useful, and reword
as needed :-)

Carl

-- 
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/54BD3ED7.8030606%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: Fellow Report - January 16, 2015

[Tim Graham]

Thanks, Anssi. By the way, we are compiling testimonials to help in the 
fundraising efforts. Do you mind if we include those two sentences from 
you? (feel free to add a couple more sentences if you like). If anyone else 
would like to share one, please send them my way. I am especially 
interested in non-core team members perspective on the program. Also, feel 
free to share any general feedback (positive or negative) -- even if you 
don't want it posted as a testimonial on the fundraising page. Thank you!

On Monday, January 19, 2015 at 5:20:49 AM UTC-5, Anssi Kääriäinen wrote:
>
> On Friday, January 16, 2015 at 10:19:15 PM UTC+2, Tim Graham wrote:
>>
>> Here’s my final report for the 3 month fellowship pilot. I hope the DSF’s 
>> fundraising efforts will be successful and I’ll have an opportunity to "be 
>> back" soon. :-)
>>
>
> From my point of view the fellowship pilot has been a huge success. The 
> amount of tickets and patches worked on during the pilot is astounding.
>
> A very big thank you, and lets hope the fundraising program is successful.
>
>  - Anssi
>

-- 
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/490e2218-2e6c-41f4-a625-0778ff2d237a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Report - January 16, 2015

[Anssi Kääriäinen]

On Friday, January 16, 2015 at 10:19:15 PM UTC+2, Tim Graham wrote:
>
> Here’s my final report for the 3 month fellowship pilot. I hope the DSF’s 
> fundraising efforts will be successful and I’ll have an opportunity to "be 
> back" soon. :-)
>

>From my point of view the fellowship pilot has been a huge success. The 
amount of tickets and patches worked on during the pilot is astounding.

A very big thank you, and lets hope the fundraising program is successful.

 - Anssi

-- 
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/60abca77-1294-4597-822f-3f4c52401713%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fellow Report - January 16, 2015

[Tim Graham]

Here’s my final report for the 3 month fellowship pilot. I hope the DSF’s 
fundraising efforts will be successful and I’ll have an opportunity to "be 
back" soon. :-)


On Monday, I reviewed the last couple of tickets before the 1.8 feature 
freeze. On Tuesday, we had the security release. I’ve been working in the 
background on putting that release together for the last month or so. The 
rest of the week was focused on polishing the master branch and fixing 
regressions to get it in a good state for today's release of 1.8 alpha 1. 
If all goes well, we’ll get lots of testers and will be able to release a 
more polished "beta" in about a month.

Report for week ending January 16, 2015:

Triaged

---

https://code.djangoproject.com/ticket/24112 - Inconsistency in 
TestCase.assertInHTML (accepted)

https://code.djangoproject.com/ticket/24086 - No pre_migrate signal is 
emitted if rolling back the migration history (worksforme)

https://code.djangoproject.com/ticket/24148 - test_combined_expression test 
failure on Windows/Python 2 (created)

https://code.djangoproject.com/ticket/24155 - Make migration generation 
more deterministic (accepted)

https://code.djangoproject.com/ticket/24142 - extra() field overwritten 
when using union on two querysets (accepted)

Authored



https://github.com/django/django/pull/3899 - Fixed #22603 -- Organized 
django.db.backends classes

https://github.com/django/django/pull/3923 - Fixed #24135 -- Made 
RenameModel rename many-to-many tables.

Reviewed/committed

--

https://github.com/django/django/pull/3889 - Fixed #23878 -- Move Query and 
Prefetch documentation

https://github.com/django/django/pull/3897 - Fixed #24124 -- Changed 
context_processors in the default settings.py

https://github.com/django/django/pull/3825 - Fixed #24031 -- Added CASE 
expressions

https://github.com/django/django/pull/3876 - Fixed #24089 -- Added check 
for when ModelAdmin.fieldsets[1]['fields'] isn't a tuple.

https://github.com/django/django/pull/3847 - Fixed #23712 -- Fixed KeyError 
with BaseForm._html_output()

https://github.com/django/django/pull/3926 - Fixed #24148 -- Documented the 
bug with case expressions in SQLite < 3..0.

https://github.com/django/django/pull/3879 - Fixed #9893 -- Allowed using a 
field's max_length in the Storage.
https://github.com/django/django/pull/3918 - Fixed #24146 -- Fixed a 
missing fields regression in admin checks.

Reviews of core dev work



https://github.com/django/django/pull/3883 - Multiple template engines - 
continued

https://github.com/django/django/pull/3868 - Fixed #24060 -- Added OrderBy 
Expressions

https://github.com/django/django/pull/3878 - Fixed #24092 -- Widened base 
field support for ArrayField.

https://github.com/django/django/pull/3890 - Fixed #24123 -- Used all 
available migrations to generate the initial migration state

https://github.com/django/django/pull/3891 - Fixed #24129 -- Added 
indicator that migrations are rendering the initial state

https://github.com/django/django/pull/3913 - Fixed #24147 -- Prevented 
managers leaking model during migrations

https://github.com/django/django/pull/3894 - Fixed #24075 -- Prevented 
running post_migrate signals when unapplying initial migrations of 
contenttypes and auth

https://github.com/django/django/pull/3920 - Fixed #24152 -- Deprecated 
GeoQuerySet aggregate methods

-- 
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/b1676d67-aaa1-4c03-adfa-dee12f55d3ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.