I see what you're saying Chuck. It's almost like you stop evolution (natural selection, if you will) when you accept a "winner" for the trunk. The positive to weigh against is that you remove instability form external projects like this. It's a great project, but it could turn south quickly without being fully supported. To be honest, I'm even on the fence myself, but it's worth mentioning for others to weigh in.
On Sep 16, 10:55 am, Chuck Harmston <ch...@chuckharmston.com> wrote: > There's a negative side to contrib: once an app is included, it stifles > innovation on that particular app (because it is tied to release cycles and > must maintain full backwards compatibility) and discourages other developers > from innovating in that same area. > > In order to get an application included to contrib, you'll need to make a > compelling case that the community will gain by its inclusion in contrib. > Yes, easy-thumbnails is great, but the only argument you've provided is that > you don't want development to die, as it did on sorl_thumbnails (which is > still a functional piece of software, by the way). That's a legitimate fear, > but where do you draw the line? What about django-registration? Or > django-taggit? > > Further discussion from DjangoCon (skip ahead to 22:12 for discussion on > contrib, though I recommend the entire > talk):http://djangocon.blip.tv/file/4112452/ > > On Thu, Sep 16, 2010 at 12:41 PM, Brian O'Connor <gatzby...@gmail.com>wrote: > > > > > Yeah, I'm aware, that's why I said '_was_ the de facto standard' :) > > > easy-thumbnails is what I had in mind when I was agreeing with you. I > > think it's a great piece of software that satisfies most people's needs for > > image manipulation within a web development environment, and being in > > contrib will allow people to use another package if they don't like it. > > > On Thu, Sep 16, 2010 at 12:37 PM, Yo-Yo Ma <baxterstock...@gmail.com>wrote: > > >> sorl-thumbnails is over. The two developers who were maintaining it > >> have started to different projects. One relies on ImageMagik and is > >> probably not as easy for the crowds. The other is "easy-thumbnails". > > >> On Sep 16, 10:33 am, "Brian O'Connor" <gatzby...@gmail.com> wrote: > >> > I have absolutely no pull in decision making, but maybe my message will > >> > count towards a "community voice". > > >> > I think that including an image thumbnail package that integrates into > >> the > >> > database as easily as sorl.thumbnail and easy_thumbnail are is a great > >> > idea. From what I can tell, sorl.thumbnail was the de facto standard > >> for > >> > getting thumbnails in to Django, and I think it has just as much of a > >> place > >> > in Django contrib as some of the other contrib apps do. I don't think > >> it > >> > belongs in the core, but contrib seems like an excellent place for it to > >> go > >> > along with the other batteries in the pack. > > >> > On Thu, Sep 16, 2010 at 12:24 PM, Yo-Yo Ma <baxterstock...@gmail.com> > >> wrote: > >> > > I have no data to support the following assertion, but it's not too > >> > > unreasonable: More people probably need thumbnail images than they > >> > > need comments. Comments are most used on blogs, whereas thumbnails can > >> > > be used on blogs, e-commerce, photo hosting, social networking, > >> > > project management, et al. It's not to say that we don't need > >> > > "contrib.comments", just that I wouldn't want to lose easy_thumbnails. > > >> > > On Sep 15, 11:32 pm, "David P. Novakovic" <davidnovako...@gmail.com> > >> > > wrote: > >> > > > Actually, that really did sound negative. Sorry :) > > >> > > > Is there a trac ticket open to address this issue? Generally it'd be > >> > > > better to get discussion happening over a ticket and if there are > >> > > > serious issues that need to be addressed then they can be discussed > >> > > > here. > > >> > > > I know it'd be nice to get things like easy-thumbnails accepted into > >> > > > django.contrib , but the truth is that this probably falls outside > >> of > >> > > > things that that should be in contrib. Contrib isn't really an > >> easier > >> > > > way to get stuff into django, it still has to satisfy a bunch of > >> > > > conditions like the rest of the code in the core. > > >> > > > The real question is not "can it be included?" but why is it a > >> problem > >> > > > that this is a third party lib at the moment? Is there a strong case > >> > > > that it be better if it was part of django core or does it do its > >> job > >> > > > just fine the way it is now? > > >> > > > David > > >> > > > On Thu, Sep 16, 2010 at 3:09 PM, David P. Novakovic > > >> > > > <davidnovako...@gmail.com> wrote: > >> > > > > I don't want to sound negative, but answering your own question > >> before > >> > > > > anyone else can doesn't change the answer ;) > > >> > > > > D > > >> > > > > On Thu, Sep 16, 2010 at 3:00 PM, Yo-Yo Ma < > >> baxterstock...@gmail.com> > >> > > wrote: > >> > > > >> Is there any plans to incorporatehttp:// > >> > > github.com/SmileyChris/easy-thumbnails/ > >> > > > >> into django.contrib? I have seen so many apps/libraries come into > >> and > >> > > > >> go out of existence ( > >>http://code.djangoproject.com/wiki/ThumbNailsfor > >> > > > >> instance mentions sorl-thumbnails which is no longer being > >> developed). > >> > > > >> I just turned the key with easy-thumbnails and voila. It's like > >> magic, > >> > > > >> but not. It's easy enough to see what's going on behind the > >> scenes. > > >> > > > >> This is something that, with the help of the core and other > >> > > > >> contributors, could be really great. It works for me as it it is, > >> but > >> > > > >> it may not work for a more "enterprise" application that uses S3, > >> etc. > >> > > > >> It might not be highly efficient (I wouldn't know). It might have > >> bugs > >> > > > >> that I just haven't noticed yet. I'm mentioning all of this > >> because I > >> > > > >> know somebody will say, "Why move it into Django if it's doing > >> just > >> > > > >> fine as a separate project?". After experiencing the bliss I > >> thought > >> > > > >> I'd drop a line here about it, and see what you guys thought. > > >> > > > >> -- > >> > > > >> You received this message because you are subscribed to the > >> Google > >> > > Groups "Django developers" group. > >> > > > >> To post to this group, send email to > >> > > django-develop...@googlegroups.com. > >> > > > >> To unsubscribe from this group, send email to > >> > > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > >> <django-developers%2bunsubscr...@googlegroups.com<django-developers%252bunsubscr...@googlegroups.com> > > >> > > . > >> > > > >> For more options, visit this group athttp:// > >> > > groups.google.com/group/django-developers?hl=en. > > >> > > -- > >> > > You received this message because you are subscribed to the Google > >> Groups > >> > > "Django developers" group. > >> > > To post to this group, send email to > >> django-develop...@googlegroups.com. > >> > > To unsubscribe from this group, send email to > >> > > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > >> <django-developers%2bunsubscr...@googlegroups.com<django-developers%252bunsubscr...@googlegroups.com> > > >> > > . > >> > > For more options, visit this group at > >> > >http://groups.google.com/group/django-developers?hl=en. > > >> > -- > >> > Brian O'Connor > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Django developers" group. > >> To post to this group, send email to django-develop...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > >> . > >> For more options, visit this group at > >>http://groups.google.com/group/django-developers?hl=en. > > > -- > > Brian O'Connor > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django developers" group. > > To post to this group, send email to django-develop...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-developers?hl=en. > > -- > * > --- > Chuck Harmston* > ch...@chuckharmston.comhttp://chuckharmston.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
