----- Original Message -----
On Tue 05 Jun 2012 03:33:11 PM MDT, Kyle Baker wrote:
>
>
> ----- Original Message -----
>> Attached screenshot of proposed new menu navigation.
>>
>> 1. There isn't a landing menu item for Subscriptions under
>> Subscriptions, just Activation Keys and Import History. While I
>> understand that clicking the second level navigation,
>> Subscriptions,
>> brings you to the default landing page, shouldn't that default
>> still
>> be in the third level nav?
>
> Yeah good catch. We could have the Third level label be
> 'Subscriptions List'.
>
>>
>> 2. Currently we have Content Providers with sub nav of Red Hat and
>> Custom; is Subscriptions meant to incorporate both?
>
> No, In 1.0 you will find a list of subscriptions under
> Organizations and under Red Hat Provider. Breaking Subscriptions
> out is meant to eliminate the ambiguity and redundancy. Under
> Repositories you now have 'Custom Repos' and 'Red Hat Repos' which
> is the same content as providers with the exception of 'Red Hat
> Repos' which should no longer have a list of subs or an import
> history tab. These now have the label of repos because that is
> what they contain. We are sill mirroring content we are just doing
> it in multiple places and are more specific with nav labels. Users
> now have one place to see all Subs available in that environment
> which is under 'Subscriptions' in a nice new tu-payne.
>
>>
>> 3. The current flow for Custom Provider is to create the provider,
>> create products, and then finally add repos; what is the suggested
>> new flow?
>
> For the current 'Custom Provider' everything is done exactly the
> same just the label changed and its position in the nav. For 'Red
> Hat Provider' we have now eliminated the subscriptions from this
> page and condensed it into one list under subscriptions. The
> process is still the same here is well except you now import from
> the subscription page. This is why the nav is reorganized this why
> to imply the workflow you outlined.
>
> 1- Import Subs
> 2- Enable Repos(Could add gpgs here or filter packages)
> 3- Sync down content
> 4- Content Search (Browser) - Find Content, Add to Sys
> template/Changeset
> 5- Manage Sys template/Add to change set
> 6- Manage Changeset/Promote to next environment
> _______________________________________________
> katello mailing list
> katello(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/katello
It is my understanding that we are trying not to abbreviate the words
"Repositories" down to "Repos"
Yeah, it should say repositories even if just for consistency sake.
-J
--
Jason E. Rist
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.754.4048
Freenode: jrist