Re: [Bf-committers] Blender 2.8x - support and core development goals

[Julian Eisel]

Hi all,

reviving this topic since I'm also a full time employed dev since this
month :) There also haven't been any objections to my plans, so I
guess I should share them here.
Due to my studies we limited my contract to 4 months for now.

I proposed the following plans to some admins and Ton, seems they are
fine with it.
Being the only full-time UI dev, there are lots of tasks I could take
responsibility for. But there's also the XR (VR + MR + AR + ...)
topic, which I find important. So my efforts will be split between
general UI work and XR.

More concretely, over the 4-6 months, I plan to focus on the following:
* Address open 2.8 UI tasks, AKA polishing the rough edges of 2.8 (see
https://developer.blender.org/T63726)
* Help designing and implement the UI side of the asset manager(s)
* Help ensure XR design development is done on solid foundations (i.e.
define "the big picture")
* Lead XR core development to create a basis for others to implement
rich experiences

It's worth mentioning that I also live in Amsterdam and work in the
Blender offices now, which should be tremendously helpful in my role.
One of my goals is to make the design process more user centered, e.g.
by involving the artists here and their contexts in the process, or by
making XR development based on concrete use-cases.

Lots of work ahead, looking forward!

Cheers,
- Julian -



On Tue, Aug 6, 2019 at 1:36 PM  wrote:
>
> I intend to focus on improvements in the selection area (peformanse and 
> usability) for possible use in the snapping code and thus initiate the goals 
> indicated on https://developer.blender.org/T66337
>
> Germano
>
> On 26. Jul 2019, at 08:00, Dalai Felinto  wrote:
>
> Dear developers,
>
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
>
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
>
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
>
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
>
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules (https://wiki.blender.org/wiki/Modules) 
> /
> https://developer.blender.org/T63725 (https://developer.blender.org/T63725)
>
> Best regards,
> Dalai
> ___
> Bf-committers mailing list
> Bf-committers@blender.org (mailto:Bf-committers@blender.org)
> https://lists.blender.org/mailman/listinfo/bf-committers 
> (https://lists.blender.org/mailman/listinfo/bf-committers)
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org (mailto:Bf-committers@blender.org)
> https://lists.blender.org/mailman/listinfo/bf-committers 
> (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 mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.8x - support and core development goals

[germano . costa]

I intend to focus on improvements in the selection area (peformanse and 
usability) for possible use in the snapping code and thus initiate the goals 
indicated on https://developer.blender.org/T66337

Germano

On 26. Jul 2019, at 08:00, Dalai Felinto  wrote:

Dear developers,

Which areas would you like to focus on in the next few months? Which
code improvements, performance, stability, new features in those areas
would you work on first [1]?

Finally which bigger new features are you confident would make it in
the 2.81 release, and which are the ones that might happen? These are
particularly important so we can allocate more time for code review
early in the release cycle and work together to assess their
feasibility.

That should empower us to set priorities and keep our ongoing
development on track. The original goal of a more strict 2-3 month
release cycle is still on the table, and it is up to us to set dates
the deliverables. As long as we are working in the right priorities,
and strive for quality, which specific features land in 2.81 are
secondary.

I'm away for Siggraph (28-1) so there is no need to rush to reply to this.

[1] - Please update the module page to reflect this -
https://wiki.blender.org/wiki/Modules (https://wiki.blender.org/wiki/Modules) /
https://developer.blender.org/T63725 (https://developer.blender.org/T63725)

Best regards,
Dalai
___
Bf-committers mailing list
Bf-committers@blender.org (mailto:Bf-committers@blender.org)
https://lists.blender.org/mailman/listinfo/bf-committers 
(https://lists.blender.org/mailman/listinfo/bf-committers)

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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Stefan Werner]

I have a bunch of patches in and outside the tracker that I’d like to prepare 
for inclusion, such as:

* OpenImageDenoise compositor node
* Adaptive Sampling for Cycles
* Tiled Texture Cache for Cycles
* Various sampling improvements for Cycles

I hope to also get a few half-finished features ready for prime time:
* light BVH (GSOC 2018)
* OpenVDB import

If time permits, I would also like to dive deeper into the volume rendering 
code in Cycles, there is lots of room for improvement in my opinion. Sparse 
voxel representations (another GSCO 2018 project that hasn’t gotten merged) and 
tracking based integrators look promising.

-Stefan

> On 26. Jul 2019, at 08:00, Dalai Felinto  wrote:
> 
> Dear developers,
> 
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
> 
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
> 
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
> 
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
> 
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules /
> https://developer.blender.org/T63725
> 
> Best regards,
> Dalai
> ___
> 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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Jeroen Bakker]

Hi all,

The upcoming year I would like to focus around the next areas:
- Image/UV Editor
- Texture Painting
- LookDev
- OpenCL
- AMD/Intel GPU support
- Compositor

It is not clear how much time I can spend in the short term because of
holidays, trainings and the actual schedule of Blender 2.81. I will be
working on preparing bigger designs and refactoring for next releases. Of
course if there are small improvements that come from these designs it can
be added to 2.81.
*Designs*
- Image/UV Editor
- Texture Painting
- Current LookDev/Rendered draw type modes
*Refactorings*
- camera background image: there are many issues related to the compositing
of the background images in the viewport (alpha/depth compositing,
transformation matrices)
- Preparing the image/uv editor to be drawn by the draw manager/GPU modules.
- Force workbench for Vertex/Weight painting (we already do this for
texture painting https://developer.blender.org/D5190 )
*Features*
- Adding similar options we have for LookDev to cycles like the world HDRI
chooser. For 2.81 I would like to start small as there are many ideas, but
need to be designed and agreed upon.
- Multilayered MatCap drawing (https://developer.blender.org/D5335). This
will need a call for content as the current matcaps don't use this feature,
but would benefit from it if they do.

Greetings,
Jeroen

On Sat, Aug 3, 2019 at 9:54 AM William Reynish  wrote:

> On the UI front, here are my thoughts and priorities:
>
> First, I feel like we have some things that are unfinished, which should
> be high priority to get done ASAP:
>
> Mainly things like:
>
>   - Dragging on a selected item should move all selected items (
> https://developer.blender.org/T57918)
> Currently we only support the Node Editor for this. Being able to
> drag your selected elements around is such a basic thing which we left
> unfinished, that I think we should try and do this asap
>
>   - Tools & gizmos
> ‘Simple’ gizmos for more tools (
> https://developer.blender.org/T66304)
> Interactive Create Object tools (Pablo Dobarro started on this.
> https://developer.blender.org/T57210)
> Inside-the-camera gizmo (https://developer.blender.org/T57234)
>
>   - Themes
> We never included additional themes for 2.80. Not super important
> but we promised to do it. I will assist picking them and testing them
> again.
>
>
>
> Additionally, I expect we will do some of these UI-related merges:
>   - Outliner GSOC (https://developer.blender.org/D5388)
>   - File Browser UI (https://developer.blender.org/T62971)
>   - Text Editor UI (https://developer.blender.org/D5028)
>
> Also many other patches related to the Sequencer UI etc.
>
> I also expect to assist with UI layout and feedback for things like LANPR
> and other new features.
>
>
>
> Other things I really hope we could do for this release:
>   - Multi-Object Properties Editing (https://developer.blender.org/D4948)
>   - Checkbox Aligmnet tweaks (https://developer.blender.org/T65965)
>   - Toolbar for the Sequencer (patch already done by Campbell)
>   - Toolbar for the Clip Editor (https://developer.blender.org/T57846)
>   - Convert NLA sidebar to Python, so we can start to make this
> 2.8-compliant.
>
>
>
> Bigger design-tasks & projects:
>
>   - Asset Browser (https://developer.blender.org/T54642)
> Since this will be a key core part of Blender’s UI and workflow,
> we should really get started with this, so this project doesn’t keep
> slipping forever. At the very least we should have a plan for how to proceed
>   - Everything Nodes. I expect to continue working on the Everything Nodes
> design task, with input mainly from Brecht and Jacques Lucke, and others (
> https://developer.blender.org/T67088)
>   - Drag & drop support for UI elements (
> https://developer.blender.org/T67893)
>
>
>
>
>
>
>
> > On 26 Jul 2019, at 08.00, Dalai Felinto  wrote:
> >
> > Dear developers,
> >
> > Which areas would you like to focus on in the next few months? Which
> > code improvements, performance, stability, new features in those areas
> > would you work on first [1]?
> >
> > Finally which bigger new features are you confident would make it in
> > the 2.81 release, and which are the ones that might happen? These are
> > particularly important so we can allocate more time for code review
> > early in the release cycle and work together to assess their
> > feasibility.
> >
> > That should empower us to set priorities and keep our ongoing
> > development on track. The original goal of a more strict 2-3 month
> > release cycle is still on the table, and it is up to us to set dates
> > the deliverables. As long as we are working in the right priorities,
> > and strive for quality, which specific features land in 2.81 are
> > secondary.
> >
> > I'm away for Siggraph (28-1) so there is no need to rush to reply to
> this.
> >
> > [1] - Please update the module page to reflect this -
> > https://wiki.blender.org/wiki/Modules /
> > https://deve

Re: [Bf-committers] Blender 2.8x - support and core development goals

[William Reynish]

On the UI front, here are my thoughts and priorities:

First, I feel like we have some things that are unfinished, which should be 
high priority to get done ASAP:

Mainly things like:

  - Dragging on a selected item should move all selected items 
(https://developer.blender.org/T57918)
Currently we only support the Node Editor for this. Being able to drag 
your selected elements around is such a basic thing which we left unfinished, 
that I think we should try and do this asap

  - Tools & gizmos
‘Simple’ gizmos for more tools (https://developer.blender.org/T66304)
Interactive Create Object tools (Pablo Dobarro started on this. 
https://developer.blender.org/T57210)
Inside-the-camera gizmo (https://developer.blender.org/T57234)

  - Themes
We never included additional themes for 2.80. Not super important but 
we promised to do it. I will assist picking them and testing them again. 



Additionally, I expect we will do some of these UI-related merges:
  - Outliner GSOC (https://developer.blender.org/D5388)
  - File Browser UI (https://developer.blender.org/T62971)
  - Text Editor UI (https://developer.blender.org/D5028)

Also many other patches related to the Sequencer UI etc.

I also expect to assist with UI layout and feedback for things like LANPR and 
other new features.



Other things I really hope we could do for this release:
  - Multi-Object Properties Editing (https://developer.blender.org/D4948)
  - Checkbox Aligmnet tweaks (https://developer.blender.org/T65965)
  - Toolbar for the Sequencer (patch already done by Campbell)
  - Toolbar for the Clip Editor (https://developer.blender.org/T57846)
  - Convert NLA sidebar to Python, so we can start to make this 2.8-compliant.



Bigger design-tasks & projects:

  - Asset Browser (https://developer.blender.org/T54642)
Since this will be a key core part of Blender’s UI and workflow, we 
should really get started with this, so this project doesn’t keep slipping 
forever. At the very least we should have a plan for how to proceed
  - Everything Nodes. I expect to continue working on the Everything Nodes 
design task, with input mainly from Brecht and Jacques Lucke, and others 
(https://developer.blender.org/T67088)
  - Drag & drop support for UI elements (https://developer.blender.org/T67893)







> On 26 Jul 2019, at 08.00, Dalai Felinto  wrote:
> 
> Dear developers,
> 
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
> 
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
> 
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
> 
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
> 
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules /
> https://developer.blender.org/T63725
> 
> Best regards,
> Dalai
> ___
> 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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Harley Acheson]

Dalai,

I realize that this thread was intended for core developers, but I couldn’t
resist chiming in.

I will probably continue to work on polish and finish, mostly very small
(and largely unnoticeable) things with widgets, layout issues, and scaling
problems. I have been working lately on refreshing the mouse cursors and
related code. I have some plans for dialogs and alerts, and things I want
to do in File Manager. One day soon I’ll get back to more work I have
planned for area splitting and joining. And if I ever get past all that I
have some interest in working on some Internationalization issues, locale
stuff, fonts maybe.

But I can’t really estimate what things might be done when. I will mostly
remain known as the annoying guy who butts into all UI discussions with odd
ideas and unworkable solutions. But that is okay, everyone needs a hobby.
LOL.

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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Richard Antalík]

Hi,

My plan for VSE in 2.81 is to implement:
https://developer.blender.org/D5386
https://developer.blender.org/T65432
https://developer.blender.org/P1027

Then depending on available time focus on usability issues like
https://developer.blender.org/D2506
or https://developer.blender.org/T45221

And do review to submitted patches(and write some) in context of
https://developer.blender.org/T65724 and new tool system. Side quest is to
audit operators code to fix obvious insanities/hacks.

Finally, fix bugs. All of them. (which isn't actually impossible but
it's still a joke)

št 1. 8. 2019 o 16:57 Pablo Dobarro  napísal(a):

> Hi!
>
> I'm currently making the final patches of all the features in the sculpt
> branch for master. I will focus first on features that don't rely on the
> sculpting system (remeshers, view navigation, mask extraction...)and then I
> will continue with all the code directly related to sculpt mode (cursor,
> filters, automasking...). As most of these features are independent of each
> other, I will try to include as many as possible for 2.81.
>
> If code review goes well and we have a defined plan for the UI and
> integration, maybe I can start looking at the vertex paint features. Doing
> this after having the sculpting tools in master should be easier.
>
> I also have the patch for the blueprint tool. It still needs some work and
> I'm not sure how to make the integration with the tools system. A basic
> version of this tool can also be ready for 2.81. Booleans and more advanced
> drawing modes can come later.
>
> El vie., 26 jul. 2019 a las 8:01, Dalai Felinto ()
> escribió:
>
> > Dear developers,
> >
> > Which areas would you like to focus on in the next few months? Which
> > code improvements, performance, stability, new features in those areas
> > would you work on first [1]?
> >
> > Finally which bigger new features are you confident would make it in
> > the 2.81 release, and which are the ones that might happen? These are
> > particularly important so we can allocate more time for code review
> > early in the release cycle and work together to assess their
> > feasibility.
> >
> > That should empower us to set priorities and keep our ongoing
> > development on track. The original goal of a more strict 2-3 month
> > release cycle is still on the table, and it is up to us to set dates
> > the deliverables. As long as we are working in the right priorities,
> > and strive for quality, which specific features land in 2.81 are
> > secondary.
> >
> > I'm away for Siggraph (28-1) so there is no need to rush to reply to
> this.
> >
> > [1] - Please update the module page to reflect this -
> > https://wiki.blender.org/wiki/Modules /
> > https://developer.blender.org/T63725
> >
> > Best regards,
> > Dalai
> > ___
> > 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 mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Pablo Dobarro]

Hi!

I'm currently making the final patches of all the features in the sculpt
branch for master. I will focus first on features that don't rely on the
sculpting system (remeshers, view navigation, mask extraction...)and then I
will continue with all the code directly related to sculpt mode (cursor,
filters, automasking...). As most of these features are independent of each
other, I will try to include as many as possible for 2.81.

If code review goes well and we have a defined plan for the UI and
integration, maybe I can start looking at the vertex paint features. Doing
this after having the sculpting tools in master should be easier.

I also have the patch for the blueprint tool. It still needs some work and
I'm not sure how to make the integration with the tools system. A basic
version of this tool can also be ready for 2.81. Booleans and more advanced
drawing modes can come later.

El vie., 26 jul. 2019 a las 8:01, Dalai Felinto ()
escribió:

> Dear developers,
>
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
>
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
>
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
>
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
>
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules /
> https://developer.blender.org/T63725
>
> Best regards,
> Dalai
> ___
> 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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Julien Duroure]

Hello,

My plan is to continue working on glTF 2.0 import / export. There is still
some issues, mainly in rigging / animation but not only.
And then this addon need some perf enhancements.

Julien

On Thu, Aug 1, 2019 at 7:12 PM antonioya blend  wrote:

> Hi all,
>
> My plans for Grease Pencil are the following:
>
> 1) Help Clément in fixing all problems with Draw Engine, mainly Blend
> modes, Z-depth issues and Antialiasing. Also, try to improve speed in any
> possible areas.
> 2) Move the modifiers evaluation from Draw Manager to depsgraph. The
> grease pencil modifiers were done before depsgraph was ready and the code
> need to be adapted.
> 3) Work in the SVG import workflow. This include two subjects, improve SVG
> import add-on and work in the conversion from Curve to Grease Pencil
> strokes.
>
> Also, I’m working in doing  a review of some operators and review edit
> menus to get a better integration with the general design, because now
> there are some points that are not clear enough.
>
> Finally, I will work with Wu Yiming in the integration between LANPR and
> Grease Pencil.
>
> I think this is enough for one release.
>
> Cheers,
> Antonio Vazquez
>
> De: Wu Yiming
> Enviado: jueves, 1 de agosto de 2019 19:01
> Para: bf-blender developers
> Asunto: Re: [Bf-committers] Blender 2.8x - support and core development
> goals
>
> Hi Blender developers!
>
> If we are talking about 2~3 months for the 2.81 release, I believe LANPR
> could be ready to be merged into master as well.
>
> I'll see how GSoC part goes and plan for the next stage.
>
> YimingWu
>
> ___
> 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 mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.8x - support and core development goals

[antonioya blend]

Hi all,

My plans for Grease Pencil are the following:

1) Help Clément in fixing all problems with Draw Engine, mainly Blend modes, 
Z-depth issues and Antialiasing. Also, try to improve speed in any possible 
areas.
2) Move the modifiers evaluation from Draw Manager to depsgraph. The grease 
pencil modifiers were done before depsgraph was ready and the code need to be 
adapted.
3) Work in the SVG import workflow. This include two subjects, improve SVG 
import add-on and work in the conversion from Curve to Grease Pencil strokes.

Also, I’m working in doing  a review of some operators and review edit menus to 
get a better integration with the general design, because now there are some 
points that are not clear enough.

Finally, I will work with Wu Yiming in the integration between LANPR and Grease 
Pencil.

I think this is enough for one release.

Cheers,
Antonio Vazquez

De: Wu Yiming
Enviado: jueves, 1 de agosto de 2019 19:01
Para: bf-blender developers
Asunto: Re: [Bf-committers] Blender 2.8x - support and core development goals

Hi Blender developers!

If we are talking about 2~3 months for the 2.81 release, I believe LANPR could 
be ready to be merged into master as well.

I'll see how GSoC part goes and plan for the next stage.

YimingWu

___
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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Wu Yiming]

Hi Blender developers!

If we are talking about 2~3 months for the 2.81 release, I believe LANPR could 
be ready to be merged into master as well.

I'll see how GSoC part goes and plan for the next stage.

YimingWu

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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[darkdefende]

For me, it seems like Ton has planned that I should work on new
animation features like better motion paths:
https://www.youtube.com/watch?v=P1zBbOowyTE
Or Implicit skinning:
https://www.youtube.com/watch?v=RHySGIqEgyk

However, I feel like it would be nice if I took a bit of time and
implemented small QoL improvements that the animation studio want to
have in blender before I start working on the new big features.

To be able to do this, I can't work full time on triaging bug reports
anymore (and I really don't want to work on the tracker either).
However, I feel that at the rate the bug tracker has been going, we will
need at least 3 full time people just working on triaging new reports to
keep it under control and not burn out the people working on it.

In addition to this we need to setup unit tests. This should be a
coordinated effort to get good coverage of the various features Blender
has. Otherwise I feel this will simply not be done.

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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Howard Trickey]

There's been a lot of complaining about edit mode performance in 2.8, and
some
amount of complaints (but not as much) about edit mode memory footprint.
Some of the complaints seem specifically about what happens with modifiers,
especially subdivision, but some seem to feel it is not just limited to
that.

I wonder if it should be a goal to profile and then come up with and
implement ideas
for edit mode performance improvements?  There are an awful lot of
algorithms
inside the edit tools and modifiers that go over every element (vertex,
edge, face)
of a mesh, often multiple times. E.g., looking for selected elements. I
have a
suspicion that that might be some of the problem. Or maybe I'm completely
wrong
and the whole problem is incrementally updating the display code with only
those
things that have been changed by the edit operation that just happened.

I might be willing to work on this kind of investigation instead of the
Boolean
stuff; though it might make more sense for a full-time developer...


On Thu, Aug 1, 2019 at 10:26 AM Clément FOUCAULT 
wrote:

> For the next release I would like to:
> - Merge my refactor of Mesh Batch Cache for quicker mesh update.
> - Merge my refactor of the DRWManager for better instancing.
> - Help refactor GPencil drawing pipeline (with antonioya). (fix many issues
> for GPencil)
> - Help refactor Selection drawing (with manowii). (faster and more reliable
> selection for edit mode)
> - Merge Object/Edit/Wireframe and all others overlay engines together to
> reduce compositing complexity.
> I think it is good to do this cleanup now before adding more features.
>
> I would like to also start looking into making EEVEE faster and a bit more
> simpler to use notably:
> - Volumetrics: Using some opengl extension I should be able to speedup
> their evaluation. Should be rather simple.
> - Shadows: Defaults are not good and the system does not support dupli
> lights. Refactoring this to use a "screenspace" approach would make it
> possible to have raytraced shadows in the future.
>
> I think this is enough for 2.81.
>
> Of course there is more to do for EEVEE but I try to keep it realistic.
> I'll update the TODO's on phabricator.
>
> Le lun. 29 juil. 2019 à 18:28, Jacques Lucke  a écrit :
>
> >
> >
> > I intend to continue to work on the new particle system in the next
> > couple of months. It is unlikely that we can release this in Blender
> > 2.81, mainly due to missing features. Releasing it in Blender 2.82 might
> > be possible. It should be stable and usable by then, but it will
> > probably still lack many features. Maybe other developers are interested
> > in contributing to it as well. I happily help them to get started with
> > this project.
> >
> > It would be good if we could merge some of the
> > particle-system-independent code from the functions branch already. That
> > mainly includes some c++ data structures I developed in the process. I
> > already prepared D4966, but need to update it again. Other encapsulated
> > code of the functions branch could be merged as well, but it makes more
> > sense to wait until it is actually used by e.g. the particle system.
> >
> > Besides that I want to continue designing what I like to call
> > "simulations as first class citizens" in Blender. I already wrote some
> > documents [1] on the topic, but there are still to many unknowns.
> >
> > Finally, I will also help reviewing the code written for the procedural
> > shading GSOC project.
> >
> > [1] https://wiki.blender.org/wiki/Source/Nodes
> >
> > Am 2019-07-26 08:00, schrieb Dalai Felinto:
> >
> > > Dear developers,
> > >
> > > Which areas would you like to focus on in the next few months? Which
> > > code improvements, performance, stability, new features in those areas
> > > would you work on first [1]?
> > >
> > > Finally which bigger new features are you confident would make it in
> > > the 2.81 release, and which are the ones that might happen? These are
> > > particularly important so we can allocate more time for code review
> > > early in the release cycle and work together to assess their
> > > feasibility.
> > >
> > > That should empower us to set priorities and keep our ongoing
> > > development on track. The original goal of a more strict 2-3 month
> > > release cycle is still on the table, and it is up to us to set dates
> > > the deliverables. As long as we are working in the right priorities,
> > > and strive for quality, which specific features land in 2.81 are
> > > secondary.
> > >
> > > I'm away for Siggraph (28-1) so there is no need to rush to reply to
> > this.
> > >
> > > [1] - Please update the module page to reflect this -
> > > https://wiki.blender.org/wiki/Modules /
> > > https://developer.blender.org/T63725
> > >
> > > Best regards,
> > > Dalai
> > > ___
> > > Bf-committers mailing list
> > > Bf-committers@blender.org
> > > https://lists.blender.org/mailman/listinfo/bf-committers
> >
> >
> > _

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Clément FOUCAULT]

For the next release I would like to:
- Merge my refactor of Mesh Batch Cache for quicker mesh update.
- Merge my refactor of the DRWManager for better instancing.
- Help refactor GPencil drawing pipeline (with antonioya). (fix many issues
for GPencil)
- Help refactor Selection drawing (with manowii). (faster and more reliable
selection for edit mode)
- Merge Object/Edit/Wireframe and all others overlay engines together to
reduce compositing complexity.
I think it is good to do this cleanup now before adding more features.

I would like to also start looking into making EEVEE faster and a bit more
simpler to use notably:
- Volumetrics: Using some opengl extension I should be able to speedup
their evaluation. Should be rather simple.
- Shadows: Defaults are not good and the system does not support dupli
lights. Refactoring this to use a "screenspace" approach would make it
possible to have raytraced shadows in the future.

I think this is enough for 2.81.

Of course there is more to do for EEVEE but I try to keep it realistic.
I'll update the TODO's on phabricator.

Le lun. 29 juil. 2019 à 18:28, Jacques Lucke  a écrit :

>
>
> I intend to continue to work on the new particle system in the next
> couple of months. It is unlikely that we can release this in Blender
> 2.81, mainly due to missing features. Releasing it in Blender 2.82 might
> be possible. It should be stable and usable by then, but it will
> probably still lack many features. Maybe other developers are interested
> in contributing to it as well. I happily help them to get started with
> this project.
>
> It would be good if we could merge some of the
> particle-system-independent code from the functions branch already. That
> mainly includes some c++ data structures I developed in the process. I
> already prepared D4966, but need to update it again. Other encapsulated
> code of the functions branch could be merged as well, but it makes more
> sense to wait until it is actually used by e.g. the particle system.
>
> Besides that I want to continue designing what I like to call
> "simulations as first class citizens" in Blender. I already wrote some
> documents [1] on the topic, but there are still to many unknowns.
>
> Finally, I will also help reviewing the code written for the procedural
> shading GSOC project.
>
> [1] https://wiki.blender.org/wiki/Source/Nodes
>
> Am 2019-07-26 08:00, schrieb Dalai Felinto:
>
> > Dear developers,
> >
> > Which areas would you like to focus on in the next few months? Which
> > code improvements, performance, stability, new features in those areas
> > would you work on first [1]?
> >
> > Finally which bigger new features are you confident would make it in
> > the 2.81 release, and which are the ones that might happen? These are
> > particularly important so we can allocate more time for code review
> > early in the release cycle and work together to assess their
> > feasibility.
> >
> > That should empower us to set priorities and keep our ongoing
> > development on track. The original goal of a more strict 2-3 month
> > release cycle is still on the table, and it is up to us to set dates
> > the deliverables. As long as we are working in the right priorities,
> > and strive for quality, which specific features land in 2.81 are
> > secondary.
> >
> > I'm away for Siggraph (28-1) so there is no need to rush to reply to
> this.
> >
> > [1] - Please update the module page to reflect this -
> > https://wiki.blender.org/wiki/Modules /
> > https://developer.blender.org/T63725
> >
> > Best regards,
> > Dalai
> > ___
> > 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 mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Jacques Lucke]

 

I intend to continue to work on the new particle system in the next
couple of months. It is unlikely that we can release this in Blender
2.81, mainly due to missing features. Releasing it in Blender 2.82 might
be possible. It should be stable and usable by then, but it will
probably still lack many features. Maybe other developers are interested
in contributing to it as well. I happily help them to get started with
this project. 

It would be good if we could merge some of the
particle-system-independent code from the functions branch already. That
mainly includes some c++ data structures I developed in the process. I
already prepared D4966, but need to update it again. Other encapsulated
code of the functions branch could be merged as well, but it makes more
sense to wait until it is actually used by e.g. the particle system. 

Besides that I want to continue designing what I like to call
"simulations as first class citizens" in Blender. I already wrote some
documents [1] on the topic, but there are still to many unknowns. 

Finally, I will also help reviewing the code written for the procedural
shading GSOC project. 

[1] https://wiki.blender.org/wiki/Source/Nodes 

Am 2019-07-26 08:00, schrieb Dalai Felinto: 

> Dear developers,
> 
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
> 
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
> 
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
> 
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
> 
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules /
> https://developer.blender.org/T63725
> 
> Best regards,
> Dalai
> ___
> 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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Campbell Barton]

On Fri, Jul 26, 2019 at 4:01 PM Dalai Felinto  wrote:
>
> Dear developers,
>
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?

My plans for the following months:

- Improve existing tools & gizmos based on design docs from the code-quest,
  see tools section T55438.
- Undo system improvements / fixes, especially texture painting.
- Bug fixing & code review.


Would also like to spend time on...

- Tool-system & gizmo access for add-ons (including docs).
- User interface improvements.
- Keymaps & event handling.
- Multi-object editing.


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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Ray Molenkamp]

Being a windows platform dev this could pretty much be a list called
'things nobody will get exited about' but here's my plans/wish-list
regardless

If I get nothing else, I hope it's this one (2.81):

I think the most important one for stability is having working automated
crash reporting, being able to see the top 10 reasons why people lose work
and proactively fix them should go a long way in improving the end-user
experience.

I Have the client side code for win/linux is in a workable state,
arto will have to take another look at the mac side since I'm pretty
sure I broke that when I merged it from 2.7 to master. Nathan is
looking into the server side of things. (D3576)

Nice to haves (not attached to a release target):

1) I'd like to see the unit tests run nightly on BF infrastructure
(I currently run them nightly on azure, but we cannot run the opengl based
tests on there) but this is something the people at the institute need to work 
on.
(Already on the list in T66306)

2) Cycles unit tests:
Currently the cycles unit tests only test the kernel most appropriate for the
host it runs on, small differences errors between architectures have been
slipping though our test suite. All render tests should run on all kernels
we build. If nobody picks this up I'll have stab at it.
(not yet on the list in T66306, but probably should be there)

Developer experience (not attached to a release target)

1) I'm planning some small tweaks to the build helper scripts on windows
to give developers some features that have been asking for like being
able to specify an absolute path for the build folder. I'm open for
other suggestions/improvements here.

2) Enable JMC for compilers that support it

JMC [1] drastically cuts down the time you spend stepping though boiler plate 
C++
code in the debugger, once master gets unfrozen I'll enable this for debug 
builds
on VS2019.

3) Developer profile.

Not my work, but i'd like to see brechts D5149 land sooner than later, just to 
get
rid of some of the annoyances like buildinfo being on for developers by default
leading to constant rebuilds which leads to less productive developers. (D5149)

4) Rewrite the build instructions for windows.

The wiki could use a refresher, some things can be clarified better, other 
things
can be skipped all together since the build scripts take care of it now-days.

I have been dragging my heels on this.

Libs 2.81:

I'm mostly following here, If you want/need a dep update for your module speak 
up!

1) Python, I heard talk about a python version bump a while ago (but never saw 
the
official request to bump it), also I have to repackage python on windows so
`make format` can use it and we longer have to rely on a system python being
installed, so these things will probably go together.
(not yet on any list I'm aware of)

2) USD will need to be scripted and packaged if sybren wants to get USD into 
2.81, I have
this partially done already, but USD on windows is having an 'unhappy time', 
officially the
windows support is experimental so our success may vary on this. The code 
builds and links
but doesn't work due some plugin registration issues inside USD. I haven't 
found  the time
to debug this yet. (not yet on any list I'm aware of)

3) Removal of 32 bit support.

Finally! (T67184)

Libs Longer term:

I've heard from multiple devs that dealing with deps is a pain, they just 
randomly sprinkle
includes and linker commands until the errors go way, that's a great use of 
their time.

While moving all of blender to a modern target based cmake style may be out of 
reach,
I think we can do this for the deps integration without causing too much 
trouble.
(not yet on any list i'm aware of)

--Ray


[1] 
https://devblogs.microsoft.com/cppblog/announcing-jmc-stepping-in-visual-studio/

On 2019-07-26 12:00 a.m., Dalai Felinto wrote:
> Dear developers,
>
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
>
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
>
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
>
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
>
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules /
> https://developer.blender.org/T63725
>
> Best regards,
> Dalai
> ___
> B

Re: [Bf-committers] Blender 2.8x - support and core development goals

[dr . Sybren A . Stüvel]

On 26-07-19 08:00, Dalai Felinto wrote:
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?

The USD branch I'm working on now is getting a lot of attention, not
only from private individuals but also from companies like AMD, Apple,
Digital Negative, and RodeoFX. I think it might be possible to merge my
branch to master for 2.81. Even though the initial goal was to have
something working before SIGGRAPH (hack or no hack, just get it
working), I'm quite happy with the result. The basis for the exporter is
an output format agnostic class that can iterate over the depsgraph and
call upon other classes to perform the actual serialisation into USD.
I'd like to convert the Alembic exporter to use the same approach, which
I think will help resolve some bugs currently in the tracker as well as
provide cleaner code.

For 2.81 I also have some fixes for Alembic-related and FFmpeg-related
bugs & features that can probably go in as soon as master is open again.

I've just emailed a proposal to the animators at the Blender Animation
Studio to work through the list of animation topics. This will serve as
a kickoff for filling out the animation module design task
.

One of the often-requested features for the Alembic importer, but also
for various other mesh-generating code (think MantaFlow, flip fluids,
fracture modifier, etc.), is to be able to import/generate motion
vectors. Currently our fluid simulation explicitly exposes the vertex
velocities, but there is no custom data layer in Mesh to store this
information in a generic way. I wouldn't mind working on this as well,
as the subject is bound to come up for USD as well.


-- 
Sybren A. Stüvel

https://stuvelfoto.nl/
https://stuvel.eu/

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

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Howard Trickey]

I intend to keep working on a Boolean redesign, for which I just made a
design task,
https://developer.blender.org/T67744 and added it to the Modeling Module
list,
 https://developer.blender.org/T63731

(Hope that's OK; haven't had a chance to discuss this with other Modeling
Module owners yet.)

I also will merge the GSoC custom bevel profile code into master and polish
it if need be.
(Will add a task for that soon too.)

And continue with any bug fixes, small enhancements requested by users for
Bevel.

Longer term, after Boolean, my next intended big project will be to make
Bevel and perhaps Inset behave properly when they bump into/flow over
existing geometry.

I am open to doing other modeling tasks has higher priority than these, if
the group here (and especially Modeling Module members) decide on different
priority orider.


On Fri, Jul 26, 2019 at 5:08 AM Brecht Van Lommel 
wrote:

> I'd like to review and finish various Cycles patches, listed on the
> module page here. The ones I've marked as most important are UDIM,
> OpenImageDenoise and procedural texture summer of code. I'm quite
> confident these could be in 2.81, since they're not that far from
> finished. Hopefully we can get more patches done, I should have time
> to review but addressing comments and bug fixing would depend on other
> developers.
> https://developer.blender.org/T66305
>
> Further there is design, code review and assistance for other
> projects, which I expect to take up easily half my time.
>
> There are two other things I'd like to help organize, though probably
> I would not have time to implement them myself:
> * Upgrade our buildbot to run automated tests and make release builds
> * Start a project for Blender performance improvements (make tasks,
> setup measurements, think of algorithms/designs)
>
>
>
> On Fri, Jul 26, 2019 at 8:01 AM Dalai Felinto  wrote:
> >
> > Dear developers,
> >
> > Which areas would you like to focus on in the next few months? Which
> > code improvements, performance, stability, new features in those areas
> > would you work on first [1]?
> >
> > Finally which bigger new features are you confident would make it in
> > the 2.81 release, and which are the ones that might happen? These are
> > particularly important so we can allocate more time for code review
> > early in the release cycle and work together to assess their
> > feasibility.
> >
> > That should empower us to set priorities and keep our ongoing
> > development on track. The original goal of a more strict 2-3 month
> > release cycle is still on the table, and it is up to us to set dates
> > the deliverables. As long as we are working in the right priorities,
> > and strive for quality, which specific features land in 2.81 are
> > secondary.
> >
> > I'm away for Siggraph (28-1) so there is no need to rush to reply to
> this.
> >
> > [1] - Please update the module page to reflect this -
> > https://wiki.blender.org/wiki/Modules /
> > https://developer.blender.org/T63725
> >
> > Best regards,
> > Dalai
> > ___
> > 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 mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.8x - support and core development goals

[Brecht Van Lommel]

I'd like to review and finish various Cycles patches, listed on the
module page here. The ones I've marked as most important are UDIM,
OpenImageDenoise and procedural texture summer of code. I'm quite
confident these could be in 2.81, since they're not that far from
finished. Hopefully we can get more patches done, I should have time
to review but addressing comments and bug fixing would depend on other
developers.
https://developer.blender.org/T66305

Further there is design, code review and assistance for other
projects, which I expect to take up easily half my time.

There are two other things I'd like to help organize, though probably
I would not have time to implement them myself:
* Upgrade our buildbot to run automated tests and make release builds
* Start a project for Blender performance improvements (make tasks,
setup measurements, think of algorithms/designs)



On Fri, Jul 26, 2019 at 8:01 AM Dalai Felinto  wrote:
>
> Dear developers,
>
> Which areas would you like to focus on in the next few months? Which
> code improvements, performance, stability, new features in those areas
> would you work on first [1]?
>
> Finally which bigger new features are you confident would make it in
> the 2.81 release, and which are the ones that might happen? These are
> particularly important so we can allocate more time for code review
> early in the release cycle and work together to assess their
> feasibility.
>
> That should empower us to set priorities and keep our ongoing
> development on track. The original goal of a more strict 2-3 month
> release cycle is still on the table, and it is up to us to set dates
> the deliverables. As long as we are working in the right priorities,
> and strive for quality, which specific features land in 2.81 are
> secondary.
>
> I'm away for Siggraph (28-1) so there is no need to rush to reply to this.
>
> [1] - Please update the module page to reflect this -
> https://wiki.blender.org/wiki/Modules /
> https://developer.blender.org/T63725
>
> Best regards,
> Dalai
> ___
> 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