Hello Fedora friends!
I would like to follow up and collect your input on Application Streams and modularity after all of the discussions over the past month. We have been listening and brainstorming on how to proceed with both the tooling, user experience, and communicating better upstream for this process.
The team working on modularity in Fedora posted some revisions to the Fedora modularity documentation. Additionally, I described the end user experience expectations in this thread, essentially describing why fully automated stream switching cannot occur for a sane distro environment- at least at our current level of understanding and tooling. While my description was certainly focused on the RHEL user perspective, as a long time Fedora user I will say this is equally true for many Fedora users.
That said, I am hoping you could share your collective wisdom and provide us feedback on the following:
1. Have we better communicated the current features and goals of Application Streams and modularity, primarily focused on end users?
I would like to follow up and collect your input on Application Streams and modularity after all of the discussions over the past month. We have been listening and brainstorming on how to proceed with both the tooling, user experience, and communicating better upstream for this process.
The team working on modularity in Fedora posted some revisions to the Fedora modularity documentation. Additionally, I described the end user experience expectations in this thread, essentially describing why fully automated stream switching cannot occur for a sane distro environment- at least at our current level of understanding and tooling. While my description was certainly focused on the RHEL user perspective, as a long time Fedora user I will say this is equally true for many Fedora users.
That said, I am hoping you could share your collective wisdom and provide us feedback on the following:
1. Have we better communicated the current features and goals of Application Streams and modularity, primarily focused on end users?
2. Does this help developers better understand the current limiting state and challenges for both stream and other tooling limitations?
3. What can you share from commercial ISV and/or community developer perspectives, and with respect to the user experience and stable distro goals previously described for Application Streams, do you have recommendations or requests for specific behaviors or tooling needed to benefit the Fedora and RHEL ecosystems? Such as but not limited :
a. How to provide the ability to switch streams without breaking a user's choice or need for a different AppStream in the dependency chain.
3. What can you share from commercial ISV and/or community developer perspectives, and with respect to the user experience and stable distro goals previously described for Application Streams, do you have recommendations or requests for specific behaviors or tooling needed to benefit the Fedora and RHEL ecosystems? Such as but not limited :
a. How to provide the ability to switch streams without breaking a user's choice or need for a different AppStream in the dependency chain.
b. What feature or tooling gaps still exist for creating community or commercial products for RHEL & Fedora?
c. Anything I did not think to ask?
Thank you for your feedback!
c. Anything I did not think to ask?
Thank you for your feedback!
---
Terry Bowling
Sr. Technical Product Manager - RHEL Systems Mgmt
Red Hat, Inc.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
