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
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 20
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 easier to me, so I picked one.
I
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 tickets as "easy pickings"
You should read the comments on the specific tickets opened for long under
specific components first. and if there isn't any activities for long ask
for take over the issue if that suits you.
On Wednesday, September 6, 2017 at 4:44:19 PM UTC+6, Alexander Lyabah wrote:
>
> > look at tests, as you
> look at tests, as you suggest
A quick question around this one.
If someone accept the ticket and working on it, what is the best way to
join and start working on tickets? Should I ask directly on github?
On Tuesday, September 5, 2017 at 5:06:20 PM UTC+3, Daniele Procida wrote:
>
> On Tue, Se
> see if you can collaborate with someone who is already working on
something, so that even if the issue is a larger one, there might be a more
manageable part of it you can tackle.
I like the idea of collaboration with someone, since it give me an
opportunity to learn more. How can I find one
I recommend narrowing down the huge number of tickets using the "Component"
category in Trac. Look at
https://code.djangoproject.com/query?status=assigned&status=new&component=contrib.admin&stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=version&desc=1&order=id
and pick a Co
There are also some other repos in the Django organization on GitHub that
could do with some love: https://github.com/django . For example
localflavor and formtools, which were removed from Django core, still have
some users and you might something to work on there.
On 5 September 2017 at 15:06, D
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 writing tests?
>
>What shou
On Tue, 2007-04-24 at 04:06 +, SmileyChris wrote:
> Following on from an IRC discussion:
> [15:52] SmileyChris: Maybe the ticket DB could use
> another
> level of granularity in triage: "Low hanging fruit"
> [15:53] mattmcc: yea, i think it could
> [15:53] S
13 matches
Mail list logo