[kde-community] Community vision and product vision

[Alexander Neundorf]

On Monday, February 15, 2016 22:22:53 Thomas Pfeiffer wrote:
> On Montag, 15. Februar 2016 22:02:18 CET Alexander Neundorf wrote:
> > On Monday, February 15, 2016 18:41:14 Thomas Pfeiffer wrote:
> > > My suggestion, therefore, is: Why don't those who are looking for a
> > > common
> > > product direction band together and create one, which however is not
> > > "mandatory" for all of KDE. Instead, any project that adheres to this
> > > common product vision could publicly commit to it, and the suite made up
> > > of all of these products could even create their own _product brand_
> > > (within KDE as the community brand) to reflect that. That way, we can
> > > have a collective product brand with a collective product vision without
> > > having to exclude any project which follows the same _community vision_
> > > out of KDE.
> > > 
> > > To me, this sounds like a win/win situation for all of us. What do you
> > > think?
> > 
> > just a thought: if we go this way, I suggest we try whether we can get
> > that
> > done at once, and announce both together/at the same time.
> 
> Sure, why not?
> The only potential problem I see with this is that finding a good common
> product vision might take a little more time, and I'd neither want to rush
> the product vision nor delay the publishing of the community vision too
> long.
> 
> Therefore, if we all decide to go this route, I'd suggest to start the
> product vision creation process right away and see how it goes. If that
> process goes well and it looks like the product vision can be finished
> soon, then I see no downside in publishing them at the same time (maybe in
> the same article, we could decide that later).
> 
> If, however, those working on the product vision decide that they would like
> to give themselves more time, it might be better to publish the generally
> agreed upon community vision with a remark that an overarching product
> vision is in the works and will be published soon.

my impression is that the term "product vision" which you use, and the 
"mission", which other people use, refer to basically the same kind of 
document. Is that so or are they something very different ?

Alex