help regarding google summer of code

2019-03-08 Thread Muhammad Faraz
i am taking part first time in any open source project using summer of code 
and i was think would the idea of integration django with front ends like 
vuejs will it be acceptable front end support especially  for vuejs is 
great in laravel due to watch package so i was thinking would proposal of 
creating module that make the integration of font end frame works with 
django easy will it be acceptable ?

-- 
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/5e238355-57f2-43bc-9283-37ec6be4b823%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Development story for CBV FormViews using GET

2019-03-08 Thread Kye Russell
Hi,

Sometimes it is appropriate to for a HTML form to use the GET method for
submission (usually search / filter forms).

My impression has always been that in order to build a FormView-based view
that acts on GET data, you have to override a few methods on your class
(which involves understanding how FormView works). Even as someone with a
fairly good understanding of these classes, I sometimes have to reference a
previously-written example to make sure I've got it right.

I am aware of the existence of django-filter[0] which takes care of this
for you, however at times I find it hard to justify adding it to a project
just to deal with this.

I have the following questions:

* Is my understanding of the current process correct, or is there an easier
way that I've missed?
* Is this documented anywhere? I looked at the Django 'working with forms'
documentation[1], and whilst it discusses the different scenarios in which
you'd use GET vs POST, it does not seem to discuss implementations in a CBV
context.
* Is there enough of a generic use-case where FormView / FormMixin /
ProcessFormView could be altered to support this? Or are there subtleties /
nuances in each implementation that make a generic solution hard to develop?

Sorry if this is the wrong avenue to discuss this. I am approaching it from
the position of wanting to alter Django to better support this use case,
but I'm aware that I may have just missed a Blessed method in the docs.

Kye

[0]: https://github.com/carltongibson/django-filter
[1]: https://docs.djangoproject.com/en/2.1/topics/forms/

-- 
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/CANK-ykkMtxezA9cHN8jQ_czLn6OYtdDn6JYbjNgASyyqHH-aAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: De-assigning "Easy pickings" tickets

2019-03-08 Thread Carlton Gibson
Hi Both. 

"Two months” just picked off about half the list looking at it. No real reason. 
Could easily be less. 

> Is there a bot for such a thing?

No, but bots! We need bots. 

Mariatta’s keynote at DjangoCon went over what she’s been doing with CPython. 

https://www.youtube.com/watch?v=uOLs3QeZy7M 


She’s even got helpers and such on GitHub...

There’s a backporting one. We could easily have that. 

One that looked on Trac and saw if a PR was for a New Feature and then left a 
comment saying. “Carlton, please remember to check for the ..versionadded 
annotations” would be very useful for me. :)

I’ll expect something by Monday. 

Have a good weekend all. 
C.


> On 8 Mar 2019, at 21:29, Tobias McNulty  wrote:
> 
> Also generally in favor. Is there a bot for such a thing? It would be nice to 
> get a reminder a week or two *before* the unassign happens, either to prompt 
> an update OR an early self-unassign (if the person is not in fact working on 
> the ticket anymore and just didn't remember it was still assigned to them).
> 
> Tobias
> 
> On Fri, Mar 8, 2019, 3:22 PM Markus Holtermann  > wrote:
> Hi Carlton,
> 
> my only question would be why you picked 2 months over 1 or 3. Generally in 
> favor. I think de-assigning somebody after $time of inactivity on a ticket is 
> fair, regardless of the complexity of the ticket.
> 
> /Markus
> 
> On Fri, Mar 8, 2019, at 8:30 PM, Carlton Gibson wrote:
> > Hi all. 
> > 
> > We don't have many Easy Pickings tickets, they're all assigned, and get 
> > assigned quickly, but don't often get closed. 
> > 
> > Looking at the current batch...
> > 
> > https://code.djangoproject.com/query?status=assigned=new=1=id=status=changetime=1=changetime
> >  
> > 
> > 
> > ... I'd like to suggest that after 2 months we de-assign them, so they 
> > can get picked up by people looking, who are likely not 
> > willing/able/whatever to take over an assigned ticket themselves. 
> > 
> > Any thoughts/objections to that as a policy? 
> > 
> > Thanks. 
> > 
> > Kind Regards,
> > 
> > Carlton
> > 
> > 
> > 
> > 
> >  -- 
> >  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/7bb67aa2-c898-4b97-a43a-eba38c00e00e%40googlegroups.com
> >  
> > 
> >  
> >  >  
> > >.
> >  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 https://groups.google.com/group/django-developers 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/8c599482-9c8e-4335-a5ff-7ffac96e94f8%40www.fastmail.com
>  
> .
> 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 

Re: De-assigning "Easy pickings" tickets

2019-03-08 Thread Tobias McNulty
Also generally in favor. Is there a bot for such a thing? It would be nice
to get a reminder a week or two *before* the unassign happens, either to
prompt an update OR an early self-unassign (if the person is not in fact
working on the ticket anymore and just didn't remember it was still
assigned to them).

Tobias

On Fri, Mar 8, 2019, 3:22 PM Markus Holtermann 
wrote:

> Hi Carlton,
>
> my only question would be why you picked 2 months over 1 or 3. Generally
> in favor. I think de-assigning somebody after $time of inactivity on a
> ticket is fair, regardless of the complexity of the ticket.
>
> /Markus
>
> On Fri, Mar 8, 2019, at 8:30 PM, Carlton Gibson wrote:
> > Hi all.
> >
> > We don't have many Easy Pickings tickets, they're all assigned, and get
> > assigned quickly, but don't often get closed.
> >
> > Looking at the current batch...
> >
> >
> https://code.djangoproject.com/query?status=assigned=new=1=id=status=changetime=1=changetime
> >
> > ... I'd like to suggest that after 2 months we de-assign them, so they
> > can get picked up by people looking, who are likely not
> > willing/able/whatever to take over an assigned ticket themselves.
> >
> > Any thoughts/objections to that as a policy?
> >
> > Thanks.
> >
> > Kind Regards,
> >
> > Carlton
> >
> >
> >
> >
> >  --
> >  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/7bb67aa2-c898-4b97-a43a-eba38c00e00e%40googlegroups.com
> <
> https://groups.google.com/d/msgid/django-developers/7bb67aa2-c898-4b97-a43a-eba38c00e00e%40googlegroups.com?utm_medium=email_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 https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/8c599482-9c8e-4335-a5ff-7ffac96e94f8%40www.fastmail.com
> .
> 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMGFDKQbnRa_gaNjEdGyHyjXpAe0%2BA1qFo_JNfWpjARh6X%2BPrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: De-assigning "Easy pickings" tickets

2019-03-08 Thread Markus Holtermann
Hi Carlton,

my only question would be why you picked 2 months over 1 or 3. Generally in 
favor. I think de-assigning somebody after $time of inactivity on a ticket is 
fair, regardless of the complexity of the ticket.

/Markus

On Fri, Mar 8, 2019, at 8:30 PM, Carlton Gibson wrote:
> Hi all. 
> 
> We don't have many Easy Pickings tickets, they're all assigned, and get 
> assigned quickly, but don't often get closed. 
> 
> Looking at the current batch...
> 
> https://code.djangoproject.com/query?status=assigned=new=1=id=status=changetime=1=changetime
> 
> ... I'd like to suggest that after 2 months we de-assign them, so they 
> can get picked up by people looking, who are likely not 
> willing/able/whatever to take over an assigned ticket themselves. 
> 
> Any thoughts/objections to that as a policy? 
> 
> Thanks. 
> 
> Kind Regards,
> 
> Carlton
> 
> 
> 
> 
>  -- 
>  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/7bb67aa2-c898-4b97-a43a-eba38c00e00e%40googlegroups.com
>  
> .
>  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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/8c599482-9c8e-4335-a5ff-7ffac96e94f8%40www.fastmail.com.
For more options, visit https://groups.google.com/d/optout.


De-assigning "Easy pickings" tickets

2019-03-08 Thread Carlton Gibson
Hi all. 

We don't have many Easy Pickings tickets, they're all assigned, and get 
assigned quickly, but don't often get closed. 

Looking at the current batch...

https://code.djangoproject.com/query?status=assigned=new=1=id=status=changetime=1=changetime

... I'd like to suggest that after 2 months we de-assign them, so they can 
get picked up by people looking, who are likely not willing/able/whatever 
to take over an assigned ticket themselves. 

Any thoughts/objections to that as a policy? 

Thanks. 

Kind Regards,

Carlton



-- 
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/7bb67aa2-c898-4b97-a43a-eba38c00e00e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: GSoC 2019 Update

2019-03-08 Thread Carlton Gibson
Hey Matthew. Good issue, yes.  Thanks. 

Hey Tim. Yes, you're probably right...

 I was going to leave GSoC, but people asked and my tick, if I've got one, 
is "widen the pool of contributors" — so it seemed worth the effort to at 
least fill in the form. 

Maybe we get an applicant. Maybe we don't. 

Regardless, I'm using it as an opportunity to pull together ideas on how 
people can get going contributing. 

This was the big take-away from DjangoCon last year for me, so, 
ever-so-slowly-as-ever-in-oss I'm trying to make moves there. 

In part, I want to keep a Project Idea list going all the time. (I'd also 
like to keep "Are you a student? We're keen on GSoC" going all year too, 
since I totally agree that the gap between new-year and now isn't long 
enough to really get to know anyone...) 

So, if people have project ideas, I still want to hear them. 

I hope that makes sense. 
(I'm quite optimistic about this stuff really.) 

Kind Regards,

Carlton

-- 
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/6b1ad5c8-90f1-4e46-838b-dcc4234b5d85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.