[Development] "Examples and demos" component in Jira (QTBUG project)

Kai Köhne Kai.Koehne at qt.io
Fri Sep 11 16:46:16 CEST 2020

> -----Ursprüngliche Nachricht-----
> Von: Development <development-bounces at qt-project.org> Im Auftrag von
> Santtu Ahonen
> Betreff: Re: [Development] "Examples and demos" component in Jira (QTBUG
> project)
> Retiring the component would be a massive loss of data and alignment
> between projects. This before retirement proposal we should have a plan on
> how to manage this area properly. Granted, this is a messy area without clear
> ownership thus we can argue on what team / who should be the owner of the
> component.
> In fact the component combines two different use cases (Examples and
> Demos) and it is not helping that different Qt projects have differently named
> components for the same overall use case.

Well, then I'm wondering what the loss of alignment is 😊

> In Product Management we use quite a lot of these Demo components to
> track demos we need to create for specific customer verticals or events,
> marketing needs etc. Our master board is here:
> https://bugreports.qt.io/secure/RapidBoard.jspa?rapidView=83

The filter query for this very board is: 

component in (Demo, Demos, "Demo Design (internal)", "Demo Implementation (internal)", DemosAndPresentations, "Examples and Demos", Examples) OR labels in (example, examples, Examples)

So the fix for QTBUG is easy: Tag the JIRA issues you're interested in in QTBUG with 'example' label. Or even better, extend the query and use a more descriptive label like 'pm_demo'. Because I actually doubt that the various bugs we have currently reported against the 'Examples and Demos' component are really regularly reviewed by PM.

> If we touch this area I'd be welcoming on splitting the Examples and Demos in
> to two separate use cases but this is not an issue for just QTBUG project, this
> goes across the board and over several projects. 

If we ever get properly maintained demos into QTBUG back (with clear responsibility) then I'm certainly not against it.



More information about the Development mailing list