ℹ️ Sibling back-end meta issue: #3450586: [META] Back-end Kanban issue tracker.

Together with the sibling back-end meta issue, this populates the kanban board at https://contribkanban.com/board/experience_builder 📊

See #3454094: Milestone 0.1.0: Experience Builder Demo for the planned next most-important issues.

You can find which front-end issues we're working on by looking at the child issues of this issue.

Comments

jessebaker created an issue. See original summary.

jessebaker’s picture

Issue summary: View changes
wim leers’s picture

Issue summary: View changes
larowlan’s picture

This sounds like a great list
There is prior art for a lot of it in decoupled lb
I think it is worth splitting into separate issues so that people can pick up discrete tasks without duplicating effort

wim leers’s picture

@larowlan Do you mean making each of those <li>s smaller, or do you mean converting them to actual issues?

larowlan’s picture

Sorry I meant converting them to actual issues

jessebaker’s picture

Issue summary: View changes
wim leers’s picture

Issue summary: View changes
wim leers’s picture

Issue summary: View changes
lauriii’s picture

Adding the child issues to the issue summary to make this easier to read.

lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Issue summary: View changes
lauriii’s picture

Component: User interface » Project Management
wim leers’s picture

Title: [META] Early phase front-end work coordination » [META] Front-end Kanban issue tracker
Component: Project Management » Project management
Assigned: jessebaker » Unassigned
Issue summary: View changes

We've failed to keep this meta up-to-date.

We're understaffed on the coordination side and have hence been unable to convey the "next steps" fully tracked in this issue. In practice, this has turned out to be impossible, because there's neither comprehensive designs nor comprehensive technical implementation plans: we've been at best been able to plan a few weeks ahead, and we've constantly had to readjust.
That's why along the way, we've been using #3454094: Milestone 0.1.0: Experience Builder Demo to keep the team laser-focused on the next highest priority per Product Lead @lauriii, who's been keeping that list up-to-date 😊

That's what's been informing what blockers to tackle to keep working towards reducing that list to zero.

Hopefully we'll eventually be able to plan further ahead.

wim leers’s picture

Version: » 0.x-dev
Status: Active » Closed (outdated)