Modules and projects organization #68701

New Issue

Dalai Felinto · 2019-08-15T18:08:35+02:00

Dalai Felinto commented

2019-08-15 18:08:35 +02:00

Modules and projects organization

This proposal tries to unify the [wiki modules page ]] with the [ https:*developer.blender.org | Phabricator project tags.

Workboards

New columns for workboard: Backlog | Bugs | Tasks | Curated
Clean up outdated tasks

Link to workboard from module page

Code Quest

Re-tag open tasks into existent projects
Close project

Modules organization
See below.

Bug / Tags / Projects
Go over the bugs and tag them to the their projects

Modules TODO

Cleanup remaining bugs
Move bugs assignment from developers to module

Paper Cuts

Modules Organization

Subprojects
The ideal solution would be to use subprojects for sub-modules - or even the modules as subprojects of #bf_blender :

Move existent modules around (doable via script ).
Patch Phabricator so workboards of parent projects aggregate subprojects tasks as well.
When tagging with subprojects we should see the parents full path (e.g., Blender→VFX & Video→Compositing)
Patch phabricator to change that OR; Manually rename tags to include their fullpath in their names;

Note: A task can only be tagged with the parent or subproject, not both at the same time.

Need a landing page

VFX & Video

Need to be demoted to subproject/module
Can still be on #63725 indented under parent.

Text Editor
Video Sequence Editor (VSE) - also remove from developer.blender.org/index.html

Need a top-level generic tag

Need to rename tags to match project

#mesh_modeling → Modeling
#sculpting_and_painting → Sculpt, Paint, Texture

Need cleanup (nitpicking)

Video Sequence Editor (VSE) Module
Should be named "Video Sequencer" consistently, ok to mention it is short version, but in the task title we should follow the [wiki ]] (or rename it in the [ https:*wiki.blender.org/wiki/Modules | wiki ) Suggestion is to use "Video Sequence", and refer to it as VSE in the body (as we do in the User Interface / UI module).

Modules and projects organization **** This proposal tries to unify the [wiki modules page ]] with the [[ https:*developer.blender.org | Phabricator ](https:*wiki.blender.org/wiki/Modules) project tags. **Workboards** - New columns for workboard: Backlog | Bugs | Tasks | Curated - Clean up outdated tasks # Link to workboard from module page **Code Quest** - Re-tag open tasks into existent projects - Close project **Modules organization** *See below.* **Bug / Tags / Projects** Go over the bugs and tag them to the their projects **Modules TODO** - Cleanup remaining bugs - Move bugs assignment from developers to module # Paper Cuts ### Modules Organization **Subprojects** The ideal solution would be to use subprojects for sub-modules - or even the modules as subprojects of #bf_blender : * Move existent modules around ([doable via script ](https://secure.phabricator.com/T10350)). * Patch Phabricator so workboards of parent projects aggregate subprojects tasks as well. * When tagging with subprojects we should see the parents full path (e.g., *Blender→VFX & Video→Compositing*) **Patch phabricator to change that OR;** Manually rename tags to include their fullpath in their names; *Note: A task can only be tagged with the parent or subproject, not both at the same time.* **Need a landing page** * VFX & Video **Need to be demoted to subproject/module** *Can still be on #63725 indented under parent*. * [Text Editor ](https://developer.blender.org/T68061) * [Video Sequence Editor (VSE) ](https://developer.blender.org/T64682) - also remove from developer.blender.org/index.html **Need a top-level generic tag** * VFX & Video * [EEVEE & Viewport ](https://developer.blender.org/T64282) * [Data, Assets & I/O ](https://developer.blender.org/T63728) * [Nodes & Physics ](https://developer.blender.org/T66307) * [Platforms, Builds & Tests ](https://developer.blender.org/T66306) * [Render & Cycles ](https://developer.blender.org/T66305) * [Python & Add-ons ](https://developer.blender.org/T63733) **Need to rename tags to match project** * #mesh_modeling → [Modeling ](https://developer.blender.org/T63731) * #sculpting_and_painting → [Sculpt, Paint, Texture ](https://developer.blender.org/T63745) **Need cleanup (nitpicking)** * [Video Sequence Editor (VSE) Module ](https://developer.blender.org/T64682) **Should be named "Video Sequencer" consistently, ok to mention it is short version, but in the task title we should follow the [wiki ]] (or rename it in the [[ https:*wiki.blender.org/wiki/Modules | wiki ](https:*wiki.blender.org/wiki/Modules))** Suggestion is to use "Video Sequence", and refer to it as VSE in the body (as we do in the User Interface / UI module).

Dalai Felinto commented

2019-08-15 18:08:35 +02:00

Added subscribers: @dfelinto, @brecht, @jesterking, @lichtwerk

ChristopherAnderssarian commented

2019-08-15 19:40:57 +02:00

Added subscriber: @ChristopherAnderssarian

ChristopherAnderssarian commented

2019-08-15 20:05:59 +02:00

I wonder if the #phabricator can be un-archived...

Brecht Van Lommel commented

2019-08-16 11:35:04 +02:00

When tagging with subprojects we should see the parents full path (e.g., Blender→VFX & Video→Compositing)
Patch phabricator to change that OR;
Manually rename tags to include their fullpath in their names;

This should be trivial to do in the code, it already does something like that for milestones:
https://developer.blender.org/diffusion/P/browse/blender-tweaks/src/applications/project/storage/PhabricatorProject.php$574

> When tagging with subprojects we should see the parents full path (e.g., Blender→VFX & Video→Compositing) > Patch phabricator to change that OR; > Manually rename tags to include their fullpath in their names; This should be trivial to do in the code, it already does something like that for milestones: https://developer.blender.org/diffusion/P/browse/blender-tweaks/src/applications/project/storage/PhabricatorProject.php$574

Brecht Van Lommel commented

2019-08-16 14:07:45 +02:00

In #68701#753921, @ChristopherAnderssarian wrote:
I wonder if the #phabricator can be un-archived...

We could have a project for development infrastructure as a whole, so that all the plans of @dfelinto and @jesterking in this area are listed somewhere and can be prioritized. Or extend #66306 (Platforms, Builds & Tests Module) to include this kind of thing. Not sure a dedicated phabricator project is needed.

> In #68701#753921, @ChristopherAnderssarian wrote: > I wonder if the #phabricator can be un-archived... We could have a project for development infrastructure as a whole, so that all the plans of @dfelinto and @jesterking in this area are listed somewhere and can be prioritized. Or extend #66306 (Platforms, Builds & Tests Module) to include this kind of thing. Not sure a dedicated phabricator project is needed.

ChristopherAnderssarian commented

2019-08-16 16:01:36 +02:00

In #68701#754363, @brecht wrote:
We could have a project for development infrastructure as a whole, so that all the plans of @dfelinto and @jesterking in this area are listed somewhere and can be prioritized.

That was the thought. That way there can be a (dedicated, probably with sub-projects) project with a Workboard laying out all the designs and todos...

In #68701, @dfelinto wrote:

New columns for workboard: Backlog | Bugs | Tasks | Curated

(Unless I'm misunderstanding this) It feels like the same status is duplicated. We already have the "Task Type", seemingly for this, wouldn't it be a waste of parameters.
Shouldn't columns be sections/parts of the project? Take the #video_sequencer for example...

Columns would consist of, say:

General
Proxy
Cache/Prefetching
Strips/Effects
Pipeline

This way bugs, design and todo tasks can be placed in their appropriate column,
and I'm sure tweeks can be made to show the task type on the Workboard and the ability to sort by them...

> In #68701#754363, @brecht wrote: > We could have a project for development infrastructure as a whole, so that all the plans of @dfelinto and @jesterking in this area are listed somewhere and can be prioritized. That was the thought. That way there can be a (dedicated, probably with sub-projects) project with a Workboard laying out all the designs and todos... ___ > In #68701, @dfelinto wrote: > # New columns for workboard: Backlog | Bugs | Tasks | Curated (Unless I'm misunderstanding this) It feels like the same status is duplicated. We already have the "Task Type", seemingly for this, wouldn't it be a waste of parameters. Shouldn't columns be sections/parts of the project? Take the #video_sequencer for example... Columns would consist of, say: - General - Proxy - Cache/Prefetching - Strips/Effects - Pipeline This way bugs, design and todo tasks can be placed in their appropriate column, and I'm sure tweeks can be made to show the task type on the Workboard and the ability to sort by them...

Dalai Felinto commented

2019-08-26 23:41:10 +02:00

Update:

Need a top-level generic tag (VFX & Video, EEVEE & Viewport, Data, Assets & I/O, Nodes & Physics, Platforms, Builds & Tests, Render & Cycles, Python & Add-ons.
Need a landing page (VFX & Video)
Need to rename tags to match project (Mesh Modeling, Sculpting and Painting).

Update: - [x] Need a top-level generic tag (VFX & Video, EEVEE & Viewport, Data, Assets & I/O, Nodes & Physics, Platforms, Builds & Tests, Render & Cycles, Python & Add-ons. - [x] Need a landing page (VFX & Video) - [x] Need to rename tags to match project (Mesh Modeling, Sculpting and Painting).

Dalai Felinto self-assigned this 2019-08-29 16:21:39 +02:00

Dalai Felinto commented

2019-10-02 20:58:16 +02:00

For the records, regarding the moving/nesting projects around:

Projects that need to be nested under (2, 'PROJ', 'PHID-PROJ-hclk7tvd6pmpjmqastjl', 'BF Blender'):

[
(12, 'PROJ', 'PHID-PROJ-bn2o3b77deft3sds2w3g', 'User Interface'), 
(14, 'PROJ', 'PHID-PROJ-kqw5cptccmoasg4jrzcu', 'Modeling'),
(27, 'PROJ', 'PHID-PROJ-ohc6hawtth6bxwqa2qim', 'Sculpt, Paint, Texture'),
(5, 'PROJ', 'PHID-PROJ-h4kgxzla4f2qqror2y3a', 'Animation'),
(62, 'PROJ', 'PHID-PROJ-6yd2vwyynrha33cnhigh', 'Grease Pencil'),
(96, 'PROJ', 'PHID-PROJ-4537ew3ewzg6bs3numzk', 'EEVEE & Viewport'),
(99, 'PROJ', 'PHID-PROJ-u7bdto4blwb3bulv4al7', 'Render & Cycles'),
(97, 'PROJ', 'PHID-PROJ-ccmtlgbelt2abwreerd2', 'Data, Assets & I/O'),
(98, 'PROJ', 'PHID-PROJ-qqpq7phzkcwzdu7s6fsh', 'Python & Add-ons'),
(95, 'PROJ', 'PHID-PROJ-bhgd7227zax6bmimh667', 'VFX & Video'),
(101, 'PROJ', 'PHID-PROJ-v53pbsbznpcnnoi7rsob', 'Nodes & Physics'),
(100, 'PROJ', 'PHID-PROJ-6i7z4qtnswaj7epemlno', 'Platforms, Builds & Tests'),
(102, 'PROJ', 'PHID-PROJ-wr7riw2hq6dfmaphrj7h', 'Development Management'),
]

Sub-Projects that need to be nested under (98, 'PROJ', 'PHID-PROJ-qqpq7phzkcwzdu7s6fsh', 'Python & Add-ons'):

[
(29, 'PROJ', 'PHID-PROJ-apehvwdfdipa4y2mchvo', 'Text Editor'),
]

Sub-Projects that need to be nested under (95, 'PROJ', 'PHID-PROJ-bhgd7227zax6bmimh667', 'VFX & Video'):

[
(28, 'PROJ', 'PHID-PROJ-hqdzj7oesaxe4mm7o5ld', 'Video Sequencer'),
(16, 'PROJ', 'PHID-PROJ-mvb4tyj4xz2wqghi3jcw', 'Motion Tracking'),
]

For the records, regarding the moving/nesting projects around: Projects that need to be nested under `(2, 'PROJ', 'PHID-PROJ-hclk7tvd6pmpjmqastjl', 'BF Blender')`: ``` [ (12, 'PROJ', 'PHID-PROJ-bn2o3b77deft3sds2w3g', 'User Interface'), (14, 'PROJ', 'PHID-PROJ-kqw5cptccmoasg4jrzcu', 'Modeling'), (27, 'PROJ', 'PHID-PROJ-ohc6hawtth6bxwqa2qim', 'Sculpt, Paint, Texture'), (5, 'PROJ', 'PHID-PROJ-h4kgxzla4f2qqror2y3a', 'Animation'), (62, 'PROJ', 'PHID-PROJ-6yd2vwyynrha33cnhigh', 'Grease Pencil'), (96, 'PROJ', 'PHID-PROJ-4537ew3ewzg6bs3numzk', 'EEVEE & Viewport'), (99, 'PROJ', 'PHID-PROJ-u7bdto4blwb3bulv4al7', 'Render & Cycles'), (97, 'PROJ', 'PHID-PROJ-ccmtlgbelt2abwreerd2', 'Data, Assets & I/O'), (98, 'PROJ', 'PHID-PROJ-qqpq7phzkcwzdu7s6fsh', 'Python & Add-ons'), (95, 'PROJ', 'PHID-PROJ-bhgd7227zax6bmimh667', 'VFX & Video'), (101, 'PROJ', 'PHID-PROJ-v53pbsbznpcnnoi7rsob', 'Nodes & Physics'), (100, 'PROJ', 'PHID-PROJ-6i7z4qtnswaj7epemlno', 'Platforms, Builds & Tests'), (102, 'PROJ', 'PHID-PROJ-wr7riw2hq6dfmaphrj7h', 'Development Management'), ] ``` Sub-Projects that need to be nested under `(98, 'PROJ', 'PHID-PROJ-qqpq7phzkcwzdu7s6fsh', 'Python & Add-ons')`: ``` [ (29, 'PROJ', 'PHID-PROJ-apehvwdfdipa4y2mchvo', 'Text Editor'), ] ``` Sub-Projects that need to be nested under `(95, 'PROJ', 'PHID-PROJ-bhgd7227zax6bmimh667', 'VFX & Video')`: ``` [ (28, 'PROJ', 'PHID-PROJ-hqdzj7oesaxe4mm7o5ld', 'Video Sequencer'), (16, 'PROJ', 'PHID-PROJ-mvb4tyj4xz2wqghi3jcw', 'Motion Tracking'), ] ```

Dalai Felinto commented

2019-10-08 01:38:37 +02:00

For the records, there are other tags we can (and may want to) nest, but there are not the first priority. Such as nesting EEVEE under "EEVEE & Viewport".

Dalai Felinto commented

2020-06-24 11:13:04 +02:00

Closing this for now since most of it was done. The missing part is only the idea of having the subprojects nested under the top-projects.

Dalai Felinto commented

2020-06-24 11:13:13 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Dalai Felinto closed this issue

2020-06-24 11:13:13 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Modules and projects organization #68701

Link to workboard from module page

Paper Cuts

Modules Organization

New columns for workboard: Backlog | Bugs | Tasks | Curated