Adding new features to ovirt.org
Hi, Thanks to everyone who helped with the feature categorization effort on the ovirt feature page <https://ovirt.org/develop/release-management/features/>. We've made significant progress, and thanks also to Eldan's UX work, the page is looking much better organized. There are a *few simple things* you can do to help keep the page organized, and to improve it. 1. Adding a new feature to ovirt.org: Please add your feature to a suitable category: - Gluster (The location in the repository is: /develop/release-management/features/gluster) - Infra (Same pattern as above) - Integration - Metrics - Network - Node - SLA - Storage - UX - VDSM - Virt 2. To help us all find which release each feature is associated with, please add a link to your feature under *Features by Release <https://ovirt.org/develop/release-management/features/#features-by-release>. * The folder location in the source repository is under: source/develop/release-management/releases/x.x/feature.html.md x.x = release version 3. We want to continue to list all *existing features* under the correct category and under Features by Release <https://ovirt.org/develop/release-management/features/#features-by-release> . You can help by visiting this spreadsheet and completing the missing feature category and release version info: https://docs.google.com/spreadsheets/d/1c7Di6xz0N0j0rPFRzogBhErJj7rnTCatAZeM... *Legend* Green*: *The feature is listed under the correct category and release *Brown**: *The feature needs to be moved to a different category / link needs to be added to the feature under the relevant release. Let me know if you have any questions. Thanks! John -- John Marks Community Manager & Technical Writer, oVirt redhat Israel Cell: +972 52 8644 491
On 15 November 2017 at 17:47, John Marks <jmarks@redhat.com> wrote:
Hi, Thanks to everyone who helped with the feature categorization effort on the ovirt feature page.
We've made significant progress, and thanks also to Eldan's UX work, the page is looking much better organized.
There are a few simple things you can do to help keep the page organized, and to improve it.
1. Adding a new feature to ovirt.org:
Please add your feature to a suitable category: - Gluster (The location in the repository is: /develop/release-management/features/gluster) - Infra (Same pattern as above) - Integration - Metrics - Network - Node - SLA - Storage - UX - VDSM - Virt
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
And yet we require the user to select a team using the same terms when filing a new bug.. I agree with you, but I think the mandatory field in bugzilla is another candidate for consideration. Martin On Thu, Nov 16, 2017 at 8:21 AM, Barak Korren <bkorren@redhat.com> wrote:
On 15 November 2017 at 17:47, John Marks <jmarks@redhat.com> wrote:
Hi, Thanks to everyone who helped with the feature categorization effort on the ovirt feature page.
We've made significant progress, and thanks also to Eldan's UX work, the page is looking much better organized.
There are a few simple things you can do to help keep the page organized, and to improve it.
1. Adding a new feature to ovirt.org:
Please add your feature to a suitable category: - Gluster (The location in the repository is: /develop/release-management/features/gluster) - Infra (Same pattern as above) - Integration - Metrics - Network - Node - SLA - Storage - UX - VDSM - Virt
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
On 16 November 2017 at 10:30, Martin Sivak <msivak@redhat.com> wrote:
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
And yet we require the user to select a team using the same terms when filing a new bug..
I agree with you, but I think the mandatory field in bugzilla is another candidate for consideration.
I've no disagreement with this statement, then again, I don't know much about the complex reasons behind the selection of fields used in bugzilla. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
On Thu, Nov 16, 2017 at 2:53 PM, Barak Korren <bkorren@redhat.com> wrote:
On 16 November 2017 at 10:30, Martin Sivak <msivak@redhat.com> wrote:
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
And yet we require the user to select a team using the same terms when filing a new bug..
I agree with you, but I think the mandatory field in bugzilla is another candidate for consideration.
I've no disagreement with this statement, then again, I don't know much about the complex reasons behind the selection of fields used in bugzilla.
Nothing complex, to be honest. The bugzilla "oVirt team" fields come to reflect the different teams owning a bug. Those are valuable for the teams, but some also make sense for users (virt/storage/infra/network/dwh/node), while others might be a bit more confusing (ux/integration/SLA). Not sure what VDSM is with regards to the feature pages? maybe for old features? I assume we can merge it into one of the others. And we can send some explanation upstream (or better add one to the website) if that helps.
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Point taken. On Thu, Nov 16, 2017 at 10:30 AM, Martin Sivak <msivak@redhat.com> wrote:
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
And yet we require the user to select a team using the same terms when filing a new bug..
I agree with you, but I think the mandatory field in bugzilla is another candidate for consideration.
Martin
On 15 November 2017 at 17:47, John Marks <jmarks@redhat.com> wrote:
Hi, Thanks to everyone who helped with the feature categorization effort on
On Thu, Nov 16, 2017 at 8:21 AM, Barak Korren <bkorren@redhat.com> wrote: the
ovirt feature page.
We've made significant progress, and thanks also to Eldan's UX work, the page is looking much better organized.
There are a few simple things you can do to help keep the page organized, and to improve it.
1. Adding a new feature to ovirt.org:
Please add your feature to a suitable category: - Gluster (The location in the repository is: /develop/release-management/features/gluster) - Infra (Same pattern as above) - Integration - Metrics - Network - Node - SLA - Storage - UX - VDSM - Virt
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- John Marks Technical Writer, oVirt redhat Israel Cell: +972 52 8644 491
Point taken. On Thu, Nov 16, 2017 at 9:21 AM, Barak Korren <bkorren@redhat.com> wrote:
Hi, Thanks to everyone who helped with the feature categorization effort on
On 15 November 2017 at 17:47, John Marks <jmarks@redhat.com> wrote: the
ovirt feature page.
We've made significant progress, and thanks also to Eldan's UX work, the page is looking much better organized.
There are a few simple things you can do to help keep the page organized, and to improve it.
1. Adding a new feature to ovirt.org:
Please add your feature to a suitable category: - Gluster (The location in the repository is: /develop/release-management/features/gluster) - Infra (Same pattern as above) - Integration - Metrics - Network - Node - SLA - Storage - UX - VDSM - Virt
I wonder where did this category division come from, some of these, like "VDSM" or "Infra" or "SLA" may not be easy for users to understand. We need to be careful about using internal development terms in user facing documentation.
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
-- John Marks Technical Writer, oVirt redhat Israel Cell: +972 52 8644 491
participants (4)
-
Barak Korren -
John Marks -
Martin Sivak -
Oved Ourfali