Underlying DE for the Workstation product, Desktop -vs- Workstation

[David Tardon]

On Mon, Feb 03, 2014 at 02:52:18PM +0000, "Jóhann B. Guðmundsson" wrote:
> 
> On 02/03/2014 02:32 PM, drago01 wrote:
> >On Mon, Feb 3, 2014 at 3:11 PM, "Jóhann B. Guðmundsson"
> ><johannbg at gmail.com> wrote:
> >>On 02/03/2014 02:08 PM, Josh Boyer wrote:
> >>>I think that's a fair observation, but I would urge the WG to set
> >>>aside marketing for a minute and focus on what they feel is the best
> >>>positioned DE from a technical and resource perspective to build the
> >>>product from.
> >>
> >>When you speak of resource perspective are you referring to downstream
> >>resources  or upstream resources because the former does not matter just the
> >>latter...
> >Both matter.
> 
> I disagree and require further explanation from you since I question
> the current thought of upstream role in downstream distributions
> after exploring the communities surrounding both to better
> understand the eco system of thoughts and the effects of those
> thoughts that residing in both of them.
> 
> The conclusion after that exploration of thought is that the role of
> upstream in downstream distributions should be a role of an
> consultant for upstream application or application stack him or her
> is developing and if time allows become a co-maintainer for a
> completely different application or application stack ( outside
> their "comfort zone" ) then what he or she is developing in the
> community for the distribution he or she uses.

While you conduct thought experiments, the rest of us live in the real
world.

> 
> In other much simpler words upstream maintainers are distracted from
> what they do best which is working on their code by maintaining
> their component in downstream distribution

Citation required.

> and that distraction is
> not helpful to end user, not helpful for those us in QA

The only thing that is dedicedly not helpful for anyone is your
inclination to split contributors into little fiefdoms (upstream,
downstream, subcommunities, etc.) with strictly defined
"responsibilities" and "privileges".

> and does not
> expand those maintainers as individuals.

Huh?

> 
> The more time the maintainer has to focus on his code the better we
> and other downstream distribution are as an result of that.

And who are you to decide what is the best way I spend my time?

D.