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] https://code.djangoproject.com/wiki/Tutorials >> >> > That's in the wiki, which is (generally, except for some pages which are > locked down due to abuse in the past) editable by the community. If you > scroll to the bottom of the page, you'll see an "Edit this page" button, if > you press that you'll be able to edit the content and remove the no-longer > functioning link. > > Karen > > -- > 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 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?hl=en > . > 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: tutorial url broken
On Mon, Apr 29, 2013 at 1:52 PM, gilberto dos santos alveswrote: > > 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 due to abuse in the past) editable by the community. If you scroll to the bottom of the page, you'll see an "Edit this page" button, if you press that you'll be able to edit the content and remove the no-longer functioning link. Karen -- 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
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 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
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 handled by assigning yourself as the owner of the ticket, perhaps with a comment to indicate your intention. Of course, we cannot stop other people from working on these tickets, but this is the best way that we have to indicate that other people intend to work on an issue. You could start with this query: https://code.djangoproject.com/query?status=assigned=new=1=Accepted=1=changetime However, not everything marked "Easy pickings" really is. Also, you might want to exclude things that already have patches. Regards, Luke -- A woman's mind is cleaner than a man's. She changes it more often. (Oliver Herford) Luke Plant || http://lukeplant.me.uk/ -- 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
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 documentation, all oriented towards the Django Project ways of working. 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? Thanks, Daniele -- 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [GSoC 2013] Revamping validation functionality proposal
On Mon, Apr 29, 2013 at 6:25 AM, Christopher Medrelawrote: > 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 framework) and > "stretching" the schedule to 12 weeks? I agree that 6 weeks for writing the > framework is slightly too few, but on the other side we have to send > evaluations after first six weeks, so I think it's a good idea to have > something that works done. Look, it's up to you; my goal is to encourage you to come up with a plan that's realistically deliverable. Nearly ever summer of code student so far has overestimated how much they can get done. So I'm trying to help you come up with a proposal that matches what you can actually do. Don't forget to take Hofstadter's Law (http://en.wikipedia.org/wiki/Hofstadter%27s_law) into account! Ultimately, we're much more likely to reject an overly-ambitious proposal than an underly-ambitious one. Our goal is to see you get done what you promise to get done, so that starts with having realistic expectations. Jacob -- 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
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 permission. > > If you've got questions or comments about the tutorial, you'll have to > take that up with the owners of that site. > > Yours, > Russ Magee %-) > > On Mon, Apr 29, 2013 at 12:00 PM, gilberto dos santos alves < > gsa...@gmail.com> wrote: > >> Hi for all. >> >> Following this url [1], i found some clarify needs for this tutorial >> works nice. >> >> Please where i find these .rst files? I already search django.github.comand >> not found them. >> >> Thanks! >> >> url:: [1] >> http://www.djangorocks.com/tutorials/how-to-create-a-basic-blog-in-django/ >> >> -- >> 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 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?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > 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 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?hl=en > . > 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
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 > up with extra time, you can always use it to write more checks. 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 framework) and "stretching" the schedule to 12 weeks? I agree that 6 weeks for writing the framework is slightly too few, but on the other side we have to send evaluations after first six weeks, so I think it's a good idea to have something that works done. -- 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.