My main concern is that it might appear that Django officially endorses the website, and that it might not be clear to developers that Django isn't directly involved with all those third party packages - which could be potentially harmful.
I'm also think that if you start linking to a grid for pagination, that you should do so for alternative form libraries, template engines, maybe even ORM-stuff if that exists. Basically for every (small or big) component that Django offers. Markus explained it better by using the term 'scattered all over the documentation'. I would have no problems with a page/section in the docs where libraries or resources like djangopackages.com are linked, centralized in a single place. You lose the relevance on the subject at hand though. DRF links to extensions, where I assume that Tom has checked all of them and deemed them worthy. It links to a known set of packages, and to me it seems that Tom officially endorses them and finds the quality sufficicient. That's something you don't get with a link to a grid comparison where the content can change multiple time per day. On Monday, February 1, 2016 at 12:06:23 PM UTC+1, Federico Capoano wrote: > > It seems like a good proposal, It would be good to know why Sergei doesn't > think it is appropiate for Django to add links to third party package > comparison grids. > > django-rest-framework links to third party extensions in its documentation > and this had a positive effect on the whole DRF ecosystem. > > Federico > > > On Monday, February 1, 2016 at 10:39:44 AM UTC+1, guettli wrote: >> >> This ticket was closed as invalid: >> https://code.djangoproject.com/ticket/26159 >> >> {{{ >> >> Here comes a pull request to add a link to the djangopackages comparison >> grid "Pagination". >> Background: The pagination in django core is only very basic. Most people >> want more. I think re-use helps more then re-inventing :-) >> }}} >> >> >> {{{ >> sergei-maertens >> >> Resolution set to invalid >> Status changed from new to closed >> >> I don't think the docs are the appropriate place to point out >> alternatives. I feel if Django starts going down that road, then you should >> do the same not only for pagination, but for forms, views, other db >> adapters, other template engines... I think it's a slippery slope. >> >> While I think that djangopackages.com is a great resource, I'm not sure >> if it (and no other resources) should be 'officially endorsed' by Django in >> the docs. >> }}} >> >> I think a lot of time gets wasted by re-inventing stuff. Yes, programmers >> love to program. But time have >> changed. There are a lot of great re-usable apps and libraries and >> programmers who wants to >> get things done use them. >> >> What do you think for *this* issue: the docs for pagination should point >> to the comparison grid or not? >> >> Regards, >> Thomas Güttler >> >> -- 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/c00ea768-7559-4145-9ec5-a49c1bec6f39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
