<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">This may complicate things a bit and isn't something that would need to be done in the first pass; however, I'll throw it out there anyway. :) Would it be worthwhile to extend the information on this page also facilitate using an activation key to register a system? In other words, a user can register a system using this method currently listed; however, they could alternatively use an activation key. This would allow them to do some initial setup of the system during registration, such as assignment of environment, content view, subscriptions, system groups...etc. To support this, might involve something as simple as splitting #2 in to: - 2a - registering the system without an activation key (i.e. current #2) - 2b - registering the system with an activation key, providing a cross-link to allow the user to quickly get to the activation keys page to view/create them thanks, Brad On 06/06/2013 10:53 AM, Kyle Baker wrote: </div> <blockquote cite="mid:1269831702.12475927.1370530433979.JavaMail.root@redhat.com" type="cite"> <pre wrap="">Attached a wireframe for this model. This wireframe eliminates the 'New System' area which is not useful based on discussions between Eng and PM. This basic design at some point should allow the user to register systems from the UI. This also should have a link to a help doc when it exists. Kyle ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">i like ditching new system for register too the right pane could have multiple tabs too, similar to 'new' import manifest, if its decided we want to keep the current new system form Sent from my iPhone On May 31, 2013, at 8:09 PM, Justin Sherrill <a class="moz-txt-link-rfc2396E" href="mailto:jsherril@redhat.com"><jsherril@redhat.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">On 05/31/2013 02:42 PM, Tom McKay wrote: </pre> <blockquote type="cite"> <pre wrap="">Suggestions: 1. Organization page 2. About page 3. On right side of page when no systems selected (going away w/ nu-tupane) 5. Nu-tupane perhaps has a place for this as an action? 4. menu Systems > Certificates (directs to link with instructions) </pre> </blockquote> <pre wrap="">I think we should probably ask ourselves: a) Why would a user want to find this? b) What would a user look for to find this? 3) would be my vote from that list simply because its with systems, although thats going away. I'm not sure that anyone would think to go to Systems -> Certificates to find it though. My vote would be (as my other email suggests), either have a Systems -> Register System tab, or somehow alter "New system" to either: a) replace "new system" with "register system" and provide instructions for registering a system with the link b) Change it to "register system" and provide both instructions or the "new system" form. -Justin </pre> <blockquote type="cite"> <pre wrap=""> ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">From: "Adam Price" <a class="moz-txt-link-rfc2396E" href="mailto:adprice@redhat.com"><adprice@redhat.com></a> To: "katello-devel" <a class="moz-txt-link-rfc2396E" href="mailto:katello-devel@redhat.com"><katello-devel@redhat.com></a> Sent: Friday, May 31, 2013 2:24:45 PM Subject: [katello-devel] candlepin-ca-certs hey folks, i have this story to do for this sprint "As a user, I'd like a link to the candlepin-certs rpm from UI." I'd like to get some suggestions on where folks think this should go. DISCUSS! -- Adam Price Software Engineer Red Hat Inc., Raleigh adprice at redhat dot com <a class="moz-txt-link-freetext" href="http://github.com/komidore64">http://github.com/komidore64</a> <a class="moz-txt-link-freetext" href="http://www.ohloh.net/accounts/komidore64">http://www.ohloh.net/accounts/komidore64</a> _______________________________________________ katello-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a> </pre> </blockquote> <pre wrap="">_______________________________________________ katello-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a> </pre> </blockquote> <pre wrap=""> _______________________________________________ katello-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a> </pre> </blockquote> <pre wrap=""> _______________________________________________ katello-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a> </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ katello-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a></pre> </blockquote> </blockquote> </body> </html>