Re: [Bf-committers] Blender developer week notes - 2021.02.15

[Ray Molenkamp via Bf-committers]

>* 2.93 bcon2 on 17 February.

This is listed on developer.blender.org as march 17 
on both the front page [1] and the 2.93 schedule [2]

Did this change, or is it a typo?

--Ray


[1] https://developer.blender.org/
[2] https://developer.blender.org/project/view/125/

On 2021-02-15 11:19 a.m., Dalai Felinto via Bf-committers wrote:

> Hi all,
>
> Here are the compiled notes for this week's development. For the complete
> report with modules and projects updates, links and images read it on:
>
> https://devtalk.blender.org/t/15-february-2021/17475
>
> Announcements
> =
> * Google Summer of Code Ideas page is still mostly with old ideas, deadline
> is February 19th (Friday).
> * Bulidbots will be on maintenance 16 February, Tuesday.
> * 2.92 bcon4 on 17 February.
>   - We will go back to using release_candidate tags.
>   - High frequency tablet input will be removed since it introduced many
> problems for old drivers, but will come back in 2.93.
> * 2.93 bcon2 on 17 February.
> * Python 3.9 support has landed for 2.93 alpha.
>   - This has ended Blender support for Windows 7 and 8.
>   - The new minimum requirement is Windows 8.1.
>
> Have a great week everyone,
> -Dalai-
> 
> Dalai Felinto - da...@blender.org - www.blender.org
> Blender Development Coordinator
> Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender developer week notes - 2021.02.15

[Dalai Felinto via Bf-committers]

Hi all,

Here are the compiled notes for this week's development. For the complete
report with modules and projects updates, links and images read it on:

https://devtalk.blender.org/t/15-february-2021/17475

Announcements
=
* Google Summer of Code Ideas page is still mostly with old ideas, deadline
is February 19th (Friday).
* Bulidbots will be on maintenance 16 February, Tuesday.
* 2.92 bcon4 on 17 February.
  - We will go back to using release_candidate tags.
  - High frequency tablet input will be removed since it introduced many
problems for old drivers, but will come back in 2.93.
* 2.93 bcon2 on 17 February.
* Python 3.9 support has landed for 2.93 alpha.
  - This has ended Blender support for Windows 7 and 8.
  - The new minimum requirement is Windows 8.1.

Have a great week everyone,
-Dalai-

Dalai Felinto - da...@blender.org - www.blender.org
Blender Development Coordinator
Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender buildbot service outage - Tuesday, February 16th @10:00 CET

[James Monteath via Bf-committers]

Hi all,

Blender's buildbot  service will be
down on Tuesday, February 16th @10:00 CET for approximately 6 hours. We are
reorganizing the hardware layout in the room.

The buildbot service should be back up @16:00 CET.

Kind regards,
James.

-- 
James Monteath - ja...@blender.org - www.blender.org
Blender DevOps Engineer
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] No Monday or Tuesday meetings for the time being

[Nathan Vegdahl via Bf-committers]

Thanks, Dalai!

That definitely clears things up for me, at least.  I appreciate you taking the 
time to write that up.

--Nathan


On Monday, February 15th, 2021 at 20:40, Dalai Felinto via Bf-committers 
 wrote:

> Hi Nathan,
>
> First let me say that this was poorly communicated on my end. I will try
> to clarify now.
>
> The meetings were not effective as they used to be a few years ago. One
> of the main purposes of the meetings was to review and agree on
> development and design proposals. This was a good moment to engage in
> real-time with everyone involved in Blender development, especially
> across time-zones. The last meetings have seen very low attendance and
> interaction, making the presence of most attendees felt like a formality.
>
> I see this as a reflection of much Blender has grown recently. Dealing
> with the growth of the Blender project while keeping it welcoming and
> accessible is an important challenge, and active efforts are being
> carried out in that regard.
>
> While for time being the general meeting is put on hold, all the other
> activities carry on as usual. The chat channels, this mailing list, they
> are all open, public and more active than ever. All the contributors are
> encouraged to share their roadmaps. The modules are always open to new
> contributors.
>
> What we expect next is two things: First, module teams are to organize
> themselves more independently. They can decide on how often and how to
> carry their public meetings. This is happening weekly already for the
> animation and other modules. I would like this to be implemented for
> other modules as well.
>
> Another thing is, at some moment (I don't know when yet) I would like we
> to have a regular meeting with all the modules where we can schedule
> release targets, assign bigger projects and find out topics related to
> planning Blender as a general. For this, monthly is probably enough. But
> feedback in the format and frequency is welcome.
> Besides, this week Ton will share a post about modules and roles that
> will help draw a picture of how all the modules related with the
> development of Blender.
>
> And as always, informal communication keeps happening on
>
> #blender-coders. I hope this helps clarifying the situation,
>
> -Dalai-

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] No Monday or Tuesday meetings for the time being

[Dalai Felinto via Bf-committers]

Hi Nathan,

First let me say that this was poorly communicated on my end. I will try 
to clarify now.


The meetings were not effective as they used to be a few years ago. One 
of the main purposes of the meetings was to review and agree on 
development and design proposals. This was a good moment to engage in 
real-time with everyone involved in Blender development, especially 
across time-zones. The last meetings have seen very low attendance and 
interaction, making the presence of most attendees felt like a formality.


I see this as a reflection of much Blender has grown recently. Dealing 
with the growth of the Blender project while keeping it welcoming and 
accessible is an important challenge, and active efforts are being 
carried out in that regard.


While for time being the general meeting is put on hold, all the other 
activities carry on as usual. The chat channels, this mailing list, they 
are all open, public and more active than ever. All the contributors are 
encouraged to share their roadmaps. The modules are always open to new 
contributors.


What we expect next is two things: First, module teams are to organize 
themselves more independently. They can decide on how often and how to 
carry their public meetings. This is happening weekly already for the 
animation and other modules. I would like this to be implemented for 
other modules as well.


Another thing is, at some moment (I don't know when yet) I would like we 
to have a regular meeting with all the modules where we can schedule 
release targets, assign bigger projects and find out topics related to 
planning Blender as a general. For this, monthly is probably enough. But 
feedback in the format and frequency is welcome.


Besides, this week Ton will share a post about modules and roles that 
will help draw a picture of how all the modules related with the 
development of Blender.


And as always, informal communication keeps happening on 
#blender-coders. I hope this helps clarifying the situation,


-Dalai-

Dalai Felinto - da...@blender.org - www.blender.org
Blender Development Coordinator
Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands

On 10-02-2021 23:41, Nathan Vegdahl via Bf-committers wrote:

Hi Dalai,


I talked a bit with Ray over chat to try to clear some things out. The main
issue seemed to be the "how" this change happened/was decided/was
communicated, not so much the change itself. I will keep that in mind for
the next disrupted change.

It's great that you were able to talk to Ray directly.  However, I was also 
confused by the decision, as I suspect were many people who remained silent 
simply because Ray had already expressed their confusion and desire for 
clarification.

Would you mind sending another email to this thread with the rationale/goal of 
this change, so that it is visible to everyone following this thread?

(To clarify: I don't mean this as a challenge to the decision itself.  I trust 
you and the rest of the Blender team.  Just some transparency would be 
appreciated, is all.)

--Nathan

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers