Technical board report - 1.8 release cycle

[Aymeric Augustin]

Hello,

It recently occurred to the team that, in the interest of transparency and accountability, the technical board should publish a report on its activity at the end of each term.

As a reminder, the technical board is a group of five people elected among the Django team who holds two prerogatives: making major technical decisions and removing or vetoing a grant of commit access.

Here’s the report from September 7th, 2014 to March 31st, 2015.

Activity was low. This is a good! It means that decisions were made by consensus within the community and the team. No disagreement had to be resolved by a vote of the technical board.

We applied the “no veto to new team members” rule by voting on each proposal. Most of these votes were formalities because the technical board members had already expressed their opinion on the team’s mailing list.

I just looked at the documentation and realized that our organization doesn’t require such positive votes. It merely allows negative votes. Perhaps we could cut down that bureaucracy.

Here’s the detail of the discussions held on the mailing-list.

1. September 12th, 2014: adding Michael Manfre to the team with commit access. Decision: yes.

2. September 14th, 2014: discussion about the unsettings project, both on the process and technical aspects. No decision put to vote.

3. Septembre 19th, 2014: discussion about the name of this list. Decision: change it to "Django Developers (contributions to Django itself)”. 

4. September 24th, 2014: adding Tom Christie to the team without commit access. Decision: yes.

5. October 1st, 2014: adding Collin Anderson to the team without commit access. Decision: yes.

6. October 8th, 2014: adding Curtis Maloney to the team without commit access. Decision: yes.

7. January 8th, 2015: adding Markus Holtermann to the team with commit access. Decision: yes.

8. January 29th, 2015: adding Ola Sitarska and Ola Sendecka to the team without commit access. Decision: yes.

I’ll send a similar email for the 1.9 release cycle when it’s over.

If someone knows a better place than the mailing-list archives to store this information, let me know.

Best regards,

-- 

Aymeric.

[Aymeric Augustin]

Sorry, I missed one discussion:

6bis. December 29th, 2014: accepting DEP 182 (Multiple Template Engines). Decision: yes.

-- 

Aymeric.