Best status to start to contribute

[Sarah A]

Hi,

I'm a new contributor to Django project. 

I've tried to contribute to a ticket by using the query "easy picking" from 
the documentation but unfortunately I didn't pay attention to the triage 
status which is different to the status. 

Is there a status for easy ticket which are ready, or something ?

I found only assigned tickets or tickets which are not ready. I may miss 
something, I'm happy to get information to be in right direction.

Thanks,
Sarah

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/06b83790-3d75-4238-985e-c4befb164cd9n%40googlegroups.com.

Re: Best status to start to contribute

[Sarah A]

Hi,

Thank you Carlton and Adam, I really appreciate it!
Both answers help, I'll check that.

Kind regards,
Sarah

Le mar. 18 mai 2021 à 15:34, Carlton Gibson  a
écrit :

> Hi Sarah,
>
> Welcome!
>
> Beyond the “easy pickings”, another good approach is to filter by
> component. The framework is so big, no-one can take it all on.
>
> Here a filter for the GeoDjango tickets
> <https://code.djangoproject.com/query?status=assigned&status=new&component=GIS&col=id&col=summary&col=status&col=component&col=owner&col=type&col=version&desc=1&order=id>.
> If you adjust the component at the top, you can see other. Maybe you like
> forms, maybe you like templates, … 37 tickets, in the case of GeoDjango, is
> a lot more addressable than 1000+ if you take them all.
>
> Most tickets require a bit of time to get into them and understand what’s
> going on. (The dual of that is that, pretty much every ticket is “What on
> earth is that about?" to begin.) That’s normal. It’s part of the fun. 😀
>
> Have a browse. If you get stuck do reach out, either here or on the forum
> <https://forum.djangoproject.com> as you prefer.
>
> I hope that helps.
>
> Kind Regards,
>
> Carlton
>
>
> On 14 May 2021, at 11:38, Sarah A  wrote:
>
> Hi,
>
> I'm a new contributor to Django project.
>
> I've tried to contribute to a ticket by using the query "easy picking"
> from the documentation but unfortunately I didn't pay attention to the
> triage status which is different to the status.
>
> Is there a status for easy ticket which are ready, or something ?
>
> I found only assigned tickets or tickets which are not ready. I may miss
> something, I'm happy to get information to be in right direction.
>
> Thanks,
> Sarah
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/06b83790-3d75-4238-985e-c4befb164cd9n%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/06b83790-3d75-4238-985e-c4befb164cd9n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-developers/Cs5GuVHUcrU/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/34BB7D51-AFEC-42C9-8567-EBF574E365A5%40gmail.com
> <https://groups.google.com/d/msgid/django-developers/34BB7D51-AFEC-42C9-8567-EBF574E365A5%40gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
[image: Sarah Abderemane] <https://sarahabd.com/>
SARAH ABDEREMANE

FULLSTACK DEVELOPER+33 6 67 51 46 80 <+33667514680>
sarahabderem...@gmail.com
[image: Twitter] <https://twitter.com/sarichouu> [image: LinkedIn]
<https://fr.linkedin.com/in/SarahAbd>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAOGRSUKqe9EBxy1d-SW7Mj%2BG1jwHi2sHA5uTrQgShGmNN3sM%2Bw%40mail.gmail.com.

Re: Accessibility standards & contribution guidelines for Django

[Sarah A]

Hi folks,

I'm interested in accessibility lately, I discovered a tool that can 
probably be added to the list: pa11y . It was used for 
automated tests.
I don't have enough experience to give my opinion but @Thibaud you might 
have an opinion on it.

I wanted to check the issue on password UX but maybe I can help on others 
things related to this before. Tell me what do you think.

Best regards,

Sarah

Le mardi 15 juin 2021 à 10:44:07 UTC+2, carlton...@gmail.com a écrit :

> Hi Thibaud. 
>
> Thanks for this, and for your efforts here generally! 🥇
>
> > ...a long-overdue follow up...
>
> This is the only bit I can't agree with 😀 — ticking along, 
> slow-and-steady, is realistic/sustainable/desirable/... 🙂
>
> You mention a lot of things, so that'll take a little while to absorb — 
> links to click, things to read. (If you have stronger opinions on "We 
> should do X, using tool Y" then that's worth putting forward.)
>
> The thought that comes up is, what can we do on the documentation front? 
> We have guides/how-tos on security, testing, and so on. Could we add 
> similar for accessibility? 
>
> * These are the standards to follow
> * Here's some of the basics of making sure your Django site is accessible. 
> * Here are some tools you can use to test/ensure that. 
>
> (Lots of this is in your email here.) 
>
> I've read various articles on this over the years, but don't feel 
> confident on it at all. I think a trusted guide in the Django docs would be 
> an awesome resource. (As a Django user I want a guide in the docs so that I 
> can make my site accessible from the start.) 
>
> That doesn't directly address your specific questions. 
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/67e57058-7c97-4e77-876a-513b498703b9n%40googlegroups.com.

Postgresql testing question

[Sarah A]

Hi folks,

I'm future new contributor (I hope so) and I'm facing a problem. 

I add tests for a ticket (#27694 
) which are PostgreSQL tests 
case. I've run all the tests in the postgres_tests file and I got failures 
but it's not linked to my additional tests. I've got same failures without 
them.

I don't know what I'm supposed to do:
Submit my contribution and create a bug ticket ?  Something else? 

Note: I don't understand completely what's happening to fix those tests.

Happy to get the right direction.

Best regards,

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/093da5c5-fc0d-414c-b995-d2755b43036bn%40googlegroups.com.

Re: Postgresql testing question

[Sarah A]

Thanks Carlton ! 
  
Yes, it's not related, it's tests about headline search 
(postgres_tests.test_search.SearchHeadlineTests) 
I'll try to open a PR to see, if it's only on my side and should be my 
configuration or I will open a ticket with all informations related.

Le dimanche 3 octobre 2021 à 19:16:33 UTC+2, carlton...@gmail.com a écrit :

> Hi Sarah. 👋 
>
> If the failures are unrelated, you can ignore them for the purposes of 
> your ticket: if you open a PR the CI will run against all configurations, 
> so an issue should show up there. 
>
> Maybe it’s a local config issue, but if it doesn't look that way, you can 
> open a ticket on Trac (with the exact error and so on) or just as well 
> follow-up with more details here.
>
> In general, it’s not expected that the test suite fails, but without more 
> details I can’t say for sure what’s going on. 
>
> Kind regards, Carlton 
>
>
>
> On Sun, 3 Oct 2021 at 19:07, Sarah A  wrote:
>
>> Hi folks,
>>
>> I'm future new contributor (I hope so) and I'm facing a problem. 
>>
>> I add tests for a ticket (#27694 
>> <https://code.djangoproject.com/ticket/27694>) which are PostgreSQL 
>> tests case. I've run all the tests in the postgres_tests file and I got 
>> failures but it's not linked to my additional tests. I've got same failures 
>> without them.
>>
>> I don't know what I'm supposed to do:
>> Submit my contribution and create a bug ticket ?  Something else? 
>>
>> Note: I don't understand completely what's happening to fix those tests.
>>
>> Happy to get the right direction.
>>
>> Best regards,
>>
>> -- 
>> 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-develop...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/093da5c5-fc0d-414c-b995-d2755b43036bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-developers/093da5c5-fc0d-414c-b995-d2755b43036bn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/2977d53b-0341-4da3-b3e2-cf775e8c282cn%40googlegroups.com.