Django 5.x Technical Board Candidate Registration

[Katie McLaughlin]

With the completion of the Django 4.x major release cycle and in accordance 
with DEP-0010 
,
 
it is now time to collect candidates for the Django Technical Board.

Technical board candidates must demonstrate:

   - A history of technical contributions to Django or the Django 
   ecosystem. This history MUST begin at least 18 months prior to the 
   individual's candidacy for the Technical Board.
   - A history of participation in Django's development outside of 
   contributions merged to the https://github.com/django/django/ 
   repository. This may include, but is not restricted to:
  - Participation in discussions on the django-developers mailing list 
  or Django Forum.
  - Reviewing and offering feedback on pull requests in the Django 
  source-code repository
  - Assisting in triage and management of the Django bug tracker.
   - A history of recent engagement with the direction and development of 
   Django. Such engagement MUST have occurred within a period of no more than 
   two years prior to the individual's candidacy for the Technical Board.


To register your candidacy, we require you to enter your name, email, and a 
bio/evidence of qualifications. The candidacy form has optional fields for 
your GitHub, Twitter, and website which can be useful for evaluating your 
qualifications.

Your email address will only be used by the DSF to contact you related to 
the election and process and will not be shared publicly.

Registration for Candidates will end on April 28th, 2023 AoE.

Please register using this form .

If you have any questions about the election, please see the post on 
djangoproject.com for contact 
details: 
https://www.djangoproject.com/weblog/2023/apr/22/technical-board-candidate-registration/

-- 
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/c91632a5-de61-4547-9c76-01eb8b5d973fn%40googlegroups.com.

Django 5.x Steering Council Candidate Registration

[Katie McLaughlin]

With the completion of the Django 4.x major release cycle and in accordance 
with DEP-0010 

 
and DEP-0012 
,
 
it is now time to collect candidates for the Django Steering Council.

Steering council candidates must demonstrate:

   - A history of substantive contributions to Django or the Django 
   ecosystem. This history must begin at least 18 months prior to the 
   individual's candidacy for the Steering Council, and include substantive 
   contributions in at least two of these bullet points:
  - Code contributions on Django projects or major third-party packages 
  in the Django ecosystem
  - Reviewing pull requests and/or triaging Django project tickets
  - Documentation, tutorials or blog posts
  - Discussions about Django on the django-developers mailing list or 
  the Django Forum
  - Running Django-related events or user groups
   - A history of engagement with the direction and future of Django. This 
   does not need to be recent, but candidates who have not engaged in the past 
   three years must still demonstrate an understanding of Django's changes and 
   direction within those three years.


To register your candidacy, we require you to enter your name, email, and a 
bio/evidence of qualifications. The candidacy form has optional fields for 
your GitHub, Twitter, and website which can be useful for evaluating your 
qualifications.

Your email address will only be used by the DSF to contact you related to 
the election and process and will not be shared publicly.

Registration for Candidates will end on April 30th, 2023 AoE.

Please register using this form .

If you have questions about the election please see the post on 
djangoproject.com for contact 
details: 
https://www.djangoproject.com/weblog/2023/apr/22/steering-council-candidate-registration/

*Please note: A previous version of this post used the term "Technical 
Board" with the candidacy requirements in DEP-0010. It has since been 
updated to reflect the requirements in DEP-0012, which updates DEP-0010. 
Additional time has been added to the candidacy nomination window to 
compensate.*

-- 
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/b2d38401-e527-437d-aed3-c08e7b470a9cn%40googlegroups.com.

Re: Django 5.x Technical Board Candidate Registration

[Katie McLaughlin]

With apologies from the Secretary, the above information is incorrect 
regarding the candidacy requirements for this election. 

The new post with the updated details has been posted 
here: https://groups.google.com/g/django-developers/c/ZjkbmE5bIoE 

Regards, 

Katie McLaughlin
Secretary
Django Software Foundation


On Sunday, 23 April 2023 at 07:57:11 UTC+10 Katie McLaughlin wrote:

> With the completion of the Django 4.x major release cycle and in 
> accordance with DEP-0010 
> ,
>  
> it is now time to collect candidates for the Django Technical Board.
>
> Technical board candidates must demonstrate:
>
>- A history of technical contributions to Django or the Django 
>ecosystem. This history MUST begin at least 18 months prior to the 
>individual's candidacy for the Technical Board.
>- A history of participation in Django's development outside of 
>contributions merged to the https://github.com/django/django/ 
>repository. This may include, but is not restricted to:
>   - Participation in discussions on the django-developers mailing 
>   list or Django Forum.
>   - Reviewing and offering feedback on pull requests in the Django 
>   source-code repository
>   - Assisting in triage and management of the Django bug tracker.
>- A history of recent engagement with the direction and development of 
>Django. Such engagement MUST have occurred within a period of no more than 
>two years prior to the individual's candidacy for the Technical Board.
>
>
> To register your candidacy, we require you to enter your name, email, and 
> a bio/evidence of qualifications. The candidacy form has optional fields 
> for your GitHub, Twitter, and website which can be useful for evaluating 
> your qualifications.
>
> Your email address will only be used by the DSF to contact you related to 
> the election and process and will not be shared publicly.
>
> Registration for Candidates will end on April 28th, 2023 AoE.
>
> Please register using this form .
>
> If you have any questions about the election, please see the post on 
> djangoproject.com for contact details: 
> https://www.djangoproject.com/weblog/2023/apr/22/technical-board-candidate-registration/
>

-- 
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/1877360d-0542-4dbc-a759-55b56d279f3cn%40googlegroups.com.