After due consideration, I think updating djangobook.com should not be a GSOC project. Why not?
First, the book is owned by the authors and Apress, not the Django project. The Django community has no control. This probably runs afoul of some sort of GSOC rule. Second, it's representative of something that is at least partly a commercial effort. In theory, Apress could take the revised content and publish it as a third edition. While I'm not opposed to the commercial selling of books at all, I think Google would take significant exception to GSOC funds being used this way. Third, I think providing example projects for the tutorial chapters is not worthy of a GSOC project. It's too much of a low-hanging fruit and people have certainly done it already. I know because people try to do this with Two Scoops of Django's chapters (search GitHub and you'll find some attempts). Fourth, because of the third issue, we risk complaints of plagiarism. The content already exists, it's just a matter of finding it. GSOC funding for code examples that already exist? No. No. No. Bad idea! Daniel Greenfeld On Monday, February 24, 2014 2:28:41 AM UTC-8, Tom Evans wrote: > > On Sat, Feb 22, 2014 at 5:31 PM, Devashish Badlani > <[email protected]<javascript:>> > wrote: > > Sir, > > > > > > Sample projects with the updated Django 1.6.2,use of latest modules in > each > > of them and an helpful documentaion ,would certainly enhance the value > of > > DjangoBook is what I feel > > > > How would this work? The book currently admonishes readers that: > > """ > The community edition of The Django Book is in transition. While the > book mentions Django version 1.4 in places, the vast majority of the > book is for Django version 1.0 > """ > > So you will write sample projects aimed at 1.6.2 for each chapter in a > book written for 1.0? This does not seem wise. > > Cheers > > Tom > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/c1720c55-3b90-42e4-9045-9c06b8b99e84%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
