I've just opened a ticket for this issue. The problem is that the label is
not escape. There is no such issue with change_list.html.
https://code.djangoproject.com/ticket/33946#ticket
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribution
Apologies for some reason I didn't get any replies to my inbox! If you'd
like to tag me on any WIP PRs I'm willing to lend a hand and test.
On Thursday, 7 April 2022 at 22:19:44 UTC+10 revan...@almabase.com wrote:
>
> Hi Josh,
>
> I am also interested to work on this ticket. I am also aware of h
Hi Josh,
I am also interested to work on this ticket. I am also aware of how can I
execute this. It would be great if I could contribute as I am eagerly
waiting to have my first contribution to Django. However, I would also be
happy to help anyone who is willing to contribute.
Thanks,
Revanth
Hi Josh, all
I am interested to work on this ticket, this would be my first time
contributing.
I have read and worked through the article "Writing your first patch for
Django". I should be fine with the getting started part.
I am looking for someone reach out to personally to get my thoug
I've just created a ticket for supporting robust on_commit handlers that I
think might be a good first ticket for somebody looking to get into
contributing to Django.
https://code.djangoproject.com/ticket/33616
I'd be more than happy to review any patch and provide guidance if
required. It's b
Hi David
I think this is a good idea. The contributing guide says to look for easy
pickings tickets as a good way to get started, but there are hardy any, so
there’s a bit of a disconnect there.
I don’t think there’s any harm in a false positive, so don’t be shy. 😃
Thanks!
C.
On Wed, 10 Feb
Hey,
As a new contributor, I can say that it's been hard to find tickets flagged
as 'easy pickings', been constantly looking for those and not able to catch.
Today, as you mentioned, I went through a few ones that were not classified
as 'easy pickings' but sounded easi
Hi David, I agree with your definition of easy as "ideal first issue" but I
don't think aiming for a certain number of easy tickets makes sense. If
those issues are quickly solved, then what happens... mark the next 20-30
easiest tickets? I'd say feel free to mark any ticke
Hi all,
tl;dr - I'm proposing we make more use of the 'easy pickings' flag on trac
and should aim to have 20-30 tickets with this flag. More options here will
hopefully help new contributors. If there is support, I'm happy to help
review tickets to push the number up.
TC+6, 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
Non-fellow agreeing here too :)
On Mon, 18 Mar 2019 at 12:08, Mariusz Felisiak
wrote:
> Totally agree!
>
> Best,
> Mariusz
>
> W dniu piątek, 8 marca 2019 20:30:11 UTC+1 użytkownik Carlton Gibson
> napisał:
>>
>> Hi all.
>>
>> We don't have man
Totally agree!
Best,
Mariusz
W dniu piątek, 8 marca 2019 20:30:11 UTC+1 użytkownik Carlton Gibson
napisał:
>
> 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
Given no dissenting voices, I'll act on this.
I'll deassign the stalest tickets and leave a comment for more recently
updated ones.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from t
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.
> >
> &g
lexity 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.
> >
>
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&status=new&easy=1&col=i
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&status=new&easy=1&col=id&col=status&col
da wrote:
>>
>> On Tue, Sep 5, 2017, Alexander Lyabah wrote:
>>
>> >A lot of articles that I've read say that I should start with ticket
>> from
>> >Easy pickings.
>>
>> >The problem is that there are not that many tickets I can choo
t; On Tue, Sep 5, 2017, Alexander Lyabah >
> wrote:
>
> >A lot of articles that I've read say that I should start with ticket from
> >Easy pickings.
>
> >The problem is that there are not that many tickets I can choose from.
> All
> >of them are al
ind one?
On Tuesday, September 5, 2017 at 5:06:20 PM UTC+3, Daniele Procida wrote:
>
> On Tue, Sep 5, 2017, Alexander Lyabah >
> wrote:
>
> >A lot of articles that I've read say that I should start with ticket from
> >Easy pickings.
>
> >The problem i
e&col=version&desc=1&order=id
and pick a Component that you're interested in and have some experience
using. Just because a ticket isn't marking "easy pickings" doesn't mean
it's not suitable for new contributors. Feel free to ask in #django-dev if
you n
, Daniele Procida wrote:
> On Tue, Sep 5, 2017, Alexander Lyabah wrote:
>
> >A lot of articles that I've read say that I should start with ticket from
> >Easy pickings.
>
> >The problem is that there are not that many tickets I can choose from. All
> >of them
On Tue, Sep 5, 2017, Alexander Lyabah wrote:
>A lot of articles that I've read say that I should start with ticket from
>Easy pickings.
>The problem is that there are not that many tickets I can choose from. All
>of them are already assign.
>
>Maybe I can start with
Hi guys,
A lot of articles that I've read say that I should start with ticket from
Easy
pickings
https://code.djangoproject.com/query?status=assigned&status=new&easy=1&stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=component&co
On Fri, Aug 21, 2015 at 7:35 AM, Tim Graham wrote:
> In my experience the "easy pickings" flag is ill-defined and insufficient
> for describing the difficulty of a ticket. I don't want to get stuck in
> categorizing tickets just for the sake of it, but I think a drop down
I never liked the "easy pickings" flag either. Your proposed change would
be a good way to identify the technical ability required to make the
changes to Django. Should we have a separate drop down with options to
identify the non-technical (bikeshedding) difficulty of the ticket?
In my experience the "easy pickings" flag is ill-defined and insufficient
for describing the difficulty of a ticket. I don't want to get stuck in
categorizing tickets just for the sake of it, but I think a drop down with
options like the following could be useful in helping co
On Thu, May 9, 2013 at 11:43 PM, Daniele Procida wrote:
> On Mon, Apr 29, 2013, Daniele Procida wrote:
>
> >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 (in
On Mon, Apr 29, 2013, Daniele Procida wrote:
>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).
I've written up the tutorial for
tart with this query:
https://code.djangoproject.com/query?status=assigned&status=new&easy=1&stage=Accepted&desc=1&order=changetime
However, not everything marked "Easy pickings" really is. Also, you
might want to exclude things that already have patches.
Regards,
Luk
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
i think it could
> [15:53] Since 'design decision needed' could be anything
> from a major concern to simply being a matter the triager doesn't want
> to make an executive decision on.
> [15:54] <__machine> yeah... good call... "easy pickings" ;)
&g
cern to simply being a matter the triager doesn't want
to make an executive decision on.
[15:54] <__machine> yeah... good call... "easy pickings" ;)
Would it be worth having a new boolean field in trac for this?
--~--~-~--~~~---~--~~
33 matches
Mail list logo
