>From a docs perspective, I'd rather not be responsible for reviewing tutorials from XYZ companies and having to worry about merging updates to them, etc. A curated wiki page seems like a reasonable place to start if someone wants to coordinate that. I am a bit afraid we will might be overwhelmed with requests to endorse various companies, but I guess the "rules" you mentioned might help filter the candidates a bit.
On Thursday, June 4, 2015 at 7:48:55 PM UTC-4, Josh Smeaton wrote: > > There's definite room for improvement with regards to the deployment story > at the end of the tutorial. I don't think pointing people to hosting > companies is the right way to go though, because they're not getting > information on how to deploy from those links. > > > There could be an argument to document possible free hosting platforms, > but the django project generally avoids advertising any particular company > > What if the Django docs included deployment tutorials provided that they > were contributed by those companies? We could have rules for whether or not > we'd accept/list the tutorial, and then provide links to each of them at > the end of the Django tutorial. By linking to many we'd absolve ourselves, > somewhat, of blessing any particular company. But having them included > directly within our documentation system gives them the authority and > accuracy that random tutorials around the net might not provide. > > On Friday, 5 June 2015 09:41:15 UTC+10, Markus Amalthea Magnuson wrote: >> >> Would it make sense to have at least something about live deployment at >> the end of the tutorial? >> >> Among other things, it could mention >> https://code.djangoproject.com/wiki/DjangoFriendlyWebHosts and/or >> http://djangofriendly.com/ >> >> On Thu, Jun 4, 2015 at 11:25 PM, Marc Tamlyn <marc....@gmail.com> wrote: >> >>> Heroku also offers free hosting of a sort. The DSF has nowhere near the >>> financial muscle or human resources to provide such a service. There could >>> be an argument to document possible free hosting platforms, but the django >>> project generally avoids advertising any particular company (or third party >>> package for that matter). >>> >>> On 4 June 2015 at 16:23, Tim Graham <timog...@gmail.com> wrote: >>> >>>> PythonAnyware provides free hosting and that's what the Django Girls >>>> tutorial uses: http://tutorial.djangogirls.org/en/deploy/README.html >>>> >>>> I don't think the Django Software Foundation needs to build a service >>>> like that. >>>> >>>> >>>> On Thursday, June 4, 2015 at 11:08:01 AM UTC-4, Markus Amalthea >>>> Magnuson wrote: >>>>> >>>>> Had discussions on an idea during DjangoCon Europe that I thought I'd >>>>> just throw out there on this list as well: >>>>> >>>>> What if the Django project provided free hosting for small projects, >>>>> so that any newcomer who went through the tutorial or similar could >>>>> actually deploy their application somewhere in as few steps as possible, >>>>> a >>>>> mini-Heroku of sorts. I think it could be of immense value for someone >>>>> who >>>>> built their first thing to show it to their friends without having to >>>>> delve >>>>> deep into devops. This could be coupled with easy instructions on how to >>>>> move that application to proper hosting such as Heroku or AWS. >>>>> >>>>> There are so many aspects of this that would have to be solved (how to >>>>> limit, auth, etc.), so this is just testing the idea. What do you think? >>>>> >>>> -- >>>> 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-develop...@googlegroups.com. >>>> To post to this group, send email to django-d...@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/23d32e1c-d31f-4043-81b9-0338c0298cf8%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/django-developers/23d32e1c-d31f-4043-81b9-0338c0298cf8%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> 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-develop...@googlegroups.com. >>> To post to this group, send email to django-d...@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/CAMwjO1HKMY6NohAjwhrg0tm%2BQErp5Yd7eCtTKbwugJkuZnM-Kw%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/django-developers/CAMwjO1HKMY6NohAjwhrg0tm%2BQErp5Yd7eCtTKbwugJkuZnM-Kw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> 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/34bbde46-95a2-40a3-9c27-17a235af1409%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
