Re: tutorial url broken

thanks. already done new link for mezzanine. 2013/4/29 Karen Tracey > On Mon, Apr 29, 2013 at 1:52 PM, gilberto dos santos alves < > gsa...@gmail.com> wrote: > >> >> Hi. on this url:: [1] we have this link url:: [2] broken. >> >> url:: [1]

Re: tutorial url broken

On Mon, Apr 29, 2013 at 1:52 PM, gilberto dos santos alves wrote: > > Hi. on this url:: [1] we have this link url:: [2] broken. > > url:: [1] https://code.djangoproject.com/wiki/Tutorials > > That's in the wiki, which is (generally, except for some pages which are locked down

tutorial url broken

Hi. on this url:: [1] we have this link url:: [2] broken. url:: [1] https://code.djangoproject.com/wiki/Tutorials url:: [2] http://codingnstuff.com/2010/01/a-complete-blog-engine-using-django-in-60-minutes/ -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You

Re: Setting aside easy-pickings for sprints

On 29/04/13 15:55, Daniele Procida wrote: > Between now and then would it be possible for some very simple > tickets to be set aside for people who will then have a chance to > tackle some real issues at their first sprint, after the workshop? That sounds like a great idea. I think this can be

Setting aside easy-pickings for sprints

At the start of the sprints at DjangoCon Europe next month, I'll be holding a workshop called "Don't be afraid to commit" for people who'd like to get involved in Django projects (including Django itself of course). It'll cover: virtualenv, using GitHub, writing tests and creating

Re: [GSoC 2013] Revamping validation functionality proposal

On Mon, Apr 29, 2013 at 6:25 AM, Christopher Medrela wrote: > Jacob, as you said, I deleted django-updates part, but I ended with a > proposal taking only 9 weeks. Did you mean also scheduling more than 6 weeks > for the first part of the proposal (writing the new

Re: .rst files for tutorials of djangorocks.com

sorry. i miss this detail. 2013/4/29 Russell Keith-Magee > Hi Gilberto, > > The site you've referenced is not officially related to the Django > project. I wasn't previously aware of the site -- we'll be having words > with them for reproducing Django content without

Re: [GSoC 2013] Revamping validation functionality proposal

> > 2. I think your proposal is a bit too big. I'd general prefer to see a > less ambitious proposal with a high probability of success over a high > risk/high reward. I'd like to see you drop the "django-updates" part > of the proposal, and focus on validation and django-secure. If you end >