On Tue, Aug 23, 2016 at 05:06:56PM -0400, Paul W. Frields wrote:
On Tue, Aug 23, 2016 at 03:28:33AM -0400, Olivier Fourdan wrote:
> Hi Paul
> > > Thanks for the warning. We do want Wayland to be the default in the
> > > alpha release, so no action is required. If we decide to switch back to
> > > X11, we'll probably do it sometime between alpha release and beta
> > > freeze.
> > Yes to all this. Olivier, could we get you to update the wiki page
> > please? <https://fedoraproject.org/wiki/Changes/WaylandByDefault>
> I tried to update this page to the best of my knowledge, but there is some overlap
so I also linked to that page
> Please let me know if that's what you had in mind,
That's helpful, thank you. I think it would also be helpful -- not
just for me, really for FESCo, storytellers, and the community at
large -- to know how the features fall into categories:
* Must be finished (modulo expected bugs) for F25
* Expected to finish for F26
* Nice-to-have but not a set time/release to finish
If there are some clear trends in things users ask for that aren't
planned (anti-features?), we should collect those in the same place to
set proper expectations. I suspect these may be spelled out in one or
more design docs somewhere but need to be collated somehow.
Sorry to respond to myself, I realized a wrinkle I didn't call out.
We should make sure that completion measures are clear. Take for
example this Wayland feature:
What does 100% mean here? How is that related to e.g. WebKit
consumers/users? Again, a matter of setting expectations for what
"done" means so it's not a moving goal post.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
- - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com