very great task! 2013/9/8 German Larrain <[email protected]>: > I know there are different opinions on this topic but if anyone is > interested, I created a repo for the tutorial. The idea is to have branches > and tags that match those of the documentation. > > https://github.com/glarrain/django-tutorial-source-code > > A nice advantage of that is to be able to compare how the resulting code of > the official tutorial changes between releases. Others are: > > Be able to check that the tutorial is correct (it's kind of difficult to > spot mistakes from the documentation, either rendered or rst), i.e. the code > works (in fact, I think I discovered a bug in the current master, which I > will file in trac ASAP). > Let the user compare at the end of the tutorial the code he/she typed with > the one in the repo. > > Best regards, > Germán > > On Wednesday, January 16, 2013 11:28:42 PM UTC-6, Russell Keith-Magee wrote: >> >> >> >> On Thu, Jan 17, 2013 at 1:17 PM, Daniel Greenfeld <[email protected]> >> wrote: >>> >>> >>> >>> On Wednesday, January 16, 2013 4:43:14 PM UTC-8, Russell Keith-Magee >>> wrote: >>>> >>>> Hi Daniele, >>>> >>>> On Thu, Jan 17, 2013 at 7:07 AM, Daniele Procida <[email protected]> >>>> wrote: >>>>> >>>>> >>>> 2) This is what version control is for. I'd much rather see someone do >>>> the tutorial and use version control on their own repository, rather than >>>> just pull down the latest version of a repo that contains all the code they >>>> need. >>>> >>>> Following point 2, it might be worth suggesting that people use version >>>> control during the tutorial. I'm not suggesting we turn the Django tutorial >>>> into a parallel tutorial on git, but seeding the idea in people's heads has >>>> the benefit of reinforcing best practice (you do version control everything >>>> you do, right?), and makes it easier to work around the rollback problems >>>> you describe; if they don't know what version control is, they might be >>>> encouraged to go investigate, and as a result, another code-fairy gets >>>> their >>>> wings :-) >>> >>> >>> There are already third-party versions of the Django tutorial that also >>> instruct on source control and TDD. These are great, and wonderful, but I >>> feel they overwhelm beginner Django developers with too much. >> >> >> To be clear -- I'm not suggesting we try and make the Django tutorial a >> parallel tutorial on source control. I'm just suggesting that we drop a >> gentle hint at the start of the tutorial, to the effect of: >> >> "If you know how to use a source control system (like Git), you might want >> to set up your tutorial directory as a repository. >> >> If you don't know how to use a source control system, don't worry. You >> don't need to know anything about source control to complete this tutorial. >> However, source control systems are incredibly useful tools that are used >> widely in software development, and you'd be well advised to learn how to >> use them." >> >> and then, after completing relevant blocks of work: >> >> "If you're using source control on this project, now would be a good time >> to commit what you've done." >> >> The aim is to encourage best practice, or at least make users *aware* of >> best practice, but leave the details up to them. >> >> Yours, >> Russ Magee %-) >> > -- > 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. > For more options, visit https://groups.google.com/groups/opt_out.
-- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- 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. For more options, visit https://groups.google.com/groups/opt_out.
