Cool design Lars, nice and simple! IMHO the font color in the top banner should be a bit more readable On 7 March 2017 at 20:50, Ish Sookun wrote:

Hi Lars,

It's simple & sleek while remaining informational. Just what geckos would need to check the status of openSUSE services.

Cheers,

-- Ish Sookun

On 03/07/2017 09:59 PM, Lars Vogdt wrote:

...

Hi @ll

I like to invite you to test our new status page: https://status.opensuse.org/

I wrote some initial information here: https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Statusopensu...

I *hope* that we can use the page "as it is" - but want to get some feedback from you before I write the big announcement...

with kind regards, Lars

-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org

-- Nick Mantas -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org

On Tue, Mar 7, 2017 at 9:59 AM, Lars Vogdt wrote:

Hi @ll

I like to invite you to test our new status page: https://status.opensuse.org/

I wrote some initial information here: https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Statusopensu...

That page returns, "You are not authorized to access this page." after I logon. -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org

On Tue, Mar 7, 2017 at 10:47 PM, Lars Vogdt wrote:

Hi

Am 8. März 2017 02:11:41 MEZ schrieb PatrickD Garvey :

...

...

I wrote some initial information here:

https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Statusopensu...

That page returns, "You are not authorized to access this page." after I logon.

I'm sorry that I created confusion: You are not authorized because the wiki is currently limited to members of the openSUSE heroes team.

As user, you do not miss anything as the wiki page just contains information for admins on how to use status.o.o to inform users.

I will write some additional, public information in the openSUSE wiki once we officially "go live" with the system.

Does that explains it to you?

Yes, that explains the situation, but I don't see why you need to limit the exposure. It's just a status page. I've heard radical openness has benefits, but have yet to see it practiced in the openSUSE project. -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org

On Tue, 7 Mar 2017 21:33:26 +0200 Nick Mantas wrote:

Cool design Lars, nice and simple! IMHO the font color in the top banner should be a bit more readable

Thanks for the feedback! I have to admit that I just did minimal adaptions to the layout, as I rely on our designers for the main homepage. I managed to enforce a bigger font and a white font color now for the top banner links. I hope this is what you wanted? With kind regards, Lars -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org

Hello, Am Donnerstag, 9. März 2017, 17:47:48 CET schrieb Lars Vogdt:

On Tue, 07 Mar 2017 22:51:12 +0100 Christian Boltz wrote:

...

Am Dienstag, 7. März 2017, 18:59:41 CET schrieb Lars Vogdt:

...

I like to invite you to test our new status page: https://status.opensuse.org/

The http variant is broken in a funny way. I first wondered about some strange browser behaviour after typing "status.opensuse.org", and then started an always-working browser which never has any rendering problems - telnet ;-) [1]

Fixed. Thanks for the hint.

;-)

...

Looks like you need more coffee ;-)

Indeed ;-)

This reminds me - wasn't the main reason for using Cachet the coffee machine graph? So, where is it? ;-)

...

It looks mostly good, but it might be a good idea to make the top bar full width - see http://paste.opensuse.org/52599157 for a nice fake screenshot ;-)

Trust me: I tried... But don't ask why the bottom-padding is now that huge. => Patches welcome! :-)

Firebug is quite helpful to answer such questions ;-) - and you can edit the CSS "live" to see what a change does. You'll probably need some CSS changes: .app-banner { background-color: #173f4f; /* !important is superfluous */ } body.status-page .app-banner { margin-bottom: 0; /* instead of 30px */ } Unfortunately the .app-banner class gets applied at two places in the header bar: <div class="app-banner"> <div class="container"> <div class="row app-banner-padding app-banner"> This means the margin-bottom change above fixes the margin inside the header (good) - but also drops the margin after the header (bad). Is it possible to change the CSS classes in the HTML? If yes, please do that. Otherwise we'll have to use slightly more funny CSS: - do not change body.status-page .app-banner { (keep 30px) - add body.status-page .app-banner .app-banner { margin-bottom: 0px; } <ul style="list-style-type:none;float:right;padding:10px;font-weight: 400;font-size: 18px;"> Needless to say that hardcoding CSS in HTML is a bad idea - and while moving it to a CSS class, please change padding to padding-top (and maybe also padding-right) to avoid superfluous bottom padding.

...

Can you please add a (if everything else fails^Wworks, dummy) failure so that we see how the page looks when people really visit it? ;-)

Feel free to do it yourself: I sent invites to most people, so you can hopefully add/delete/update incidents on your own...

Well, yes and no. I created the account, but I can't find any login link on the page. It might be a good idea to add it ;-)

...

Another detail: the subscribe page should contain a sentence that explains what it does. I'd *guess* that I can enter my mail address - but a) already that is just a guess based on "input field near a subscribe button" and b) it does not explain when I'll get mailed (if a status note is added? if a service fails? ...?)

hm: something I need to figure out. At the moment it looks to me like the source does not allow to put additional information there.

If everything else fails, you can still change the HTML ;-) Regards, Christian Boltz -- Außerdem - welcher Spammer wird den Provider wegen Nichtzustellung verklagen? ;-) [Werner Flamme in postfixbuch-users] -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org

Hello, Am Donnerstag, 9. März 2017, 20:57:18 CET schrieb Lars Vogdt:

Am 9. März 2017 20:12:47 MEZ schrieb Christian Boltz:

...

This reminds me - wasn't the main reason for using Cachet the coffee machine graph? So, where is it? ;-)

As your machine does not send notifications, the graph is not there, yet. Permission request to NSA is out... ;-)

;-) I'm afraid my coffee machine won't create impressive numbers, so the coffee machine in the SUSE office might be a more interesting target ;-)

To be honest: I'm unsure what we should show as graph. Ideas?

At the risk of everybody hating me - what about the number of open admin tickets?

...

...

Trust me: I tried... But don't ask why the bottom-padding is now that huge. => Patches welcome! :-)

Firebug is quite helpful to answer such questions ;-) - and you can edit the CSS "live" to see what a change does.

Yes, but the css "hides" in the cachet app and I don't want to maintain patches when they are not really needed...

Luckily it's possible to define a custom CSS sniplet that gets applied on top of the default CSS :-)

...

Unfortunately the .app-banner class gets applied at two places in the header bar:

<div class="app-banner">

<div class="container">

<div class="row app-banner-padding app-banner">

This means the margin-bottom change above fixes the margin inside the header (good) - but also drops the margin after the header (bad). Is it possible to change the CSS classes in the HTML? If yes, please do The container is done by me, so we should be able to insert anything we need there.

Actually _removing_ something helped - I removed the "app-banner" class in the inner <div> to avoid the 30px margin. I also moved the menu styles to the CSS and adjusted the padding. Another detail I noticed is that https://status.opensuse.org/incidents/4 had another header above "our" menu bar. I added .navbar {display:none} to hide it (and hope it doesn't hide something else ;-)

As I'm not so good in that CSS/ HTML stuff, would you mind checking the "Settings" -> "Customization" stuff? I bet you get faster results than me :-)

Might be ;-) - does it look better now? Please remind me to give you a quick firebug introduction at oSC ;-) Once you understand how it works, it's really easy.

...

Well, yes and no. I created the account, but I can't find any login link on the page. It might be a good idea to add it ;-)

If you would read the progress wiki (link from my first mail), you would know it already :-)

I already read that page when you created it , but somehow I didn't remember that it has a pointer to the login page. Maybe because I didn't have an account back then. That said - even if I don't hope we have to do it often, updating the status because a service broke is a valid usecase. I'm not sure if we really want to search for the login when already in emergency mode ;-) therefore having a login link somewhere might be a good idea.

...

...

hm: something I need to figure out. At the moment it looks to me like the source does not allow to put additional information there.

If everything else fails, you can still change the HTML ;-)

You mean the PHP... It's like editing the mediawiki code, to give you an idea. Just have a look at the github page of cachet to get the idea ;-)

The subscribe page is probably resources/views/subscribe/subscribe.blade.php and not too hard to edit (basically HTML with some PHP to include translated texts). I agree that patching the code isn't nice, but it's doable and manageable without too much pain when building a RPM and applying the patch on top of the upstream tarball. I just tested the subscribe page. After entering my mail address and clicking the subscribe button, I get a page where I can manage the notifications (which means a checkbox for each item on the status page). Nice :-) Not-so-nice: - The notification mails come with an unsubscribe link (which seems to cancel all subscriptions), but no "edit subscriptions" link. - I also don't see a way to manage subscriptions or unsubscribe *without* having a status update mail at hand. And a final question - I found where I can add and edit incidents, and it's also possible to add an update there. But - where can I edit or delete existing updates? Regards, Christian Boltz --

In Yast2-System-Editor /etc/sysconfig-Dateien in System-Kernel-MODULES_LOADED_ON_BOOT ide-scsi eintragen. *JAUUUUUUUULLLLL* *ARRRGGHHHH* Man reiche mir eine Klinik-Jahrespackung von $SCHMERZMITTEL!!! [> Heinz Dittmar und David Haller in suse-linux]

-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org