5:46 a.m.
Hi,
Dne 16. 07. 22 v 14:34 Dan Čermák napsal(a):
Hi,
On July 15, 2022 9:30:48 PM UTC, Ben Cotton <bcotton(a)redhat.com> wrote:
> https://fedoraproject.org/wiki/Changes/Anaconda_Web_UI_preview_image
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only be implemented if approved
> by the Fedora Engineering Steering Committee.
>
> == Summary ==
> The work on Web UI for the Anaconda installer has advanced enough so
> that it is possible to create and publish self contained preview
> images.
>
> == Owner ==
> * Name: [[User:m4rtink| Martin Kolman]]
> * Email: mkolman(a)redhat.com
>
>
> == Detailed Description ==
> Even though still very simple the new Anaconda Web UI is now far
> enough to support a simple installation workflow from a self-contained
> image while demonstrating all the main aspects of the new UI, such as:
>
> * flexible Wizard layout
> * responsive PatternFly components
> * new style built-in help
> * local and remote access to the Web UI
>
> For this we will create a self-contained boot.iso style image with a
> built-in tar-payload (so that the image can work even without network
> access) based on the latest Anaconda upstream code.
>
> We aim to have the image available for download just after the F37
> release (so that the tar-payload can contain final F37 release
> content) and then updated automatically in regular intervals.
>
> That way the rather active Web UI development of the Web UI will be
> reflected in the up-to-date installation image, as well as any
> feedback and community PRs.
>
>
> == Benefit to Fedora ==
> The Anaconda Web UI will provide modern responsive user interface
> based on a well known
> and widely used toolkit (PatternFly) and backed by proven Cockpit tooling.
>
> The screen layout is based on latest UX design guidelines as well as
> usability testing of the new interface and extensive mockup work.
>
> There are improvements in developer experience as well due to the more
> modern & more mainstream UI technology chosen and powerful Cockpit
> test tooling (rich unit-test as well as pixel-test framework). The
> stateless property of the Web UI allows almost live-coding style of UI
> development. This should make it easier to work on the Anaconda Web UI
> for not only the Anaconda team, addon developer but also for any
> interested contributors.
>
> Remote Web UI access should also provide a much better experience than
> the slow and inefficient VNC based remote GUI installation support
> Anaconda has today. Due to no need for local rendering remotely driven
> GUI installations on a constrained hardware with minimal installation
> images should become possible.
>
>
> == Scope ==
> * Proposal owners:
> The Anaconda team will setup and maintain an automated Web UI preview
> image creation pipeline, with the image being available via a web
> server on the Fedora infrastructure.
>
> It will be a '''preview image only''', not an official
Fedora
> deliverable and it will not influence Fedora release criteria in any
> way.
>
> * Other developers:
> Other developers and Fedora users are welcome to try the image once it
> is released and to provide feedback.
>
> * Release engineering:
> * Policies and guidelines: N/A (not needed for this Change)
> * Trademark approval: N/A (not needed for this Change)
> * Alignment with Objectives:
>
>
> == Upgrade/compatibility impact ==
> (not supplied)
>
>
> == How To Test ==
> Download the Anaconda Web UI preview image and boot it on VM or
> hardware that contains no important data.
>
> Install using the Web UI locally, alternatively try using the Web UI remotely.
>
> The installed OS should be functional but its testing or any issues
> with it are currently out of scope for the Anaconda Web UI preview
> image.
Do you have any plans to integrate this with the Fedora openQA tests? That would
automatically give you some basic coverage for the functionality of the installed system.
That would be definitely valuable but I don't think it's feasible right
now. The current progress is pretty rapid and we are constantly changing
things. Having the OpenQA to reflect that could be too heavy from the
maintenance PoV. Instead of that, we have pixel tests[0] in our upstream
repository to avoid breaking UI, that is much easier to keep updated by us.
When the UI will be more stable than we definitely want to have OpenQA
support.
[0]: https://cockpit-project.org/blog/pixel-testing.html
Best Regards,
Jirka
> To provide feedback use one of the Anaconda team communication channels:
>
> * IRC: [https://web.libera.chat/#anaconda #anaconda] on libera.chat
> * mailing list: anaconda-devel(a)lists.fedoraproject.org -
>
https://lists.fedoraproject.org/archives/list/anaconda-devel@lists.fedora...
> * Github Discussion: https://github.com/rhinstaller/anaconda/discussions
>
>
> == User Experience ==
> Should be improved compared to the current GTK interface.
>
> == Dependencies ==
> (not supplied)
>
>
> == Contingency Plan ==
> * Contingency mechanism: If we hit some blocking technical issues, the
> image will be published later.
> * Contingency deadline: N/A (not a System Wide Change)
> * Blocks release? N/A (not a System Wide Change), Yes/No
>
>
> == Documentation ==
> N/A (not a System Wide Change)
>
>
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure