all the changes that I made today are not yet visible on the dev page.
So please wait before you fill new bugs :-)

> On 3. May 2017, at 21:12, Michael Tremer <michael.tremer@ipfire.org> wrote:
>
> On Wed, 2017-05-03 at 21:11 +0200, Maurice Gesswein wrote:
>> How can I permanently display closed bugs in bugzilla?
>
> What do you want to do with them?
>
>>
>> On Tue, May 2, 2017 at 7:34 AM, Maurice Gesswein <maurice.gesswein@ip
>> fire.org> wrote:
>>> I meant Ubuntu 500 if this is the medium weight. Sorry for
>>> confusion.
>>>
>>> Am 02.05.2017 7:25 vorm. schrieb "Sven" <sven.hoehn@posteo.de>:
>>> For questions and feedback on the bug, where do I fill that, per
>>> eMail or on bugzilla?
>>>
>>> I see a couple of issues at the buttons I would like to fix. I'll
>>> simply list them down.
>>>
>>> * Touch targets (48px) at 36px buttons are missing. Thats important
>>> for e.g. Smartphone to provide a comfortable touch zone for an
>>> element/button. Let me know if you want to learn more about that.
>>> * The border on filled buttons falsified the left/right paddings.
>>> Please remove the border if the button don't need it
>>> * Please recheck the left/right paddings of ALL buttons and compare
>>> carefully with the Pattern Lib sheet at Zeplin. Paddings are
>>> different if an icon is included.
>>>
>>> Maybe it is easier to rewrite the buttons completely and don’t use
>>> the bootstrap buttons at all. But I will check.
>>>
>>> * It looks like that "Ubuntu-Medium (600)" is not imported:
>>> @import url("
>>> https://fonts.googleapis.com/css?family=Ubuntu:300,400,700
>>> ");
>>> Can you replace 700 with 600 for now please? I guess I'll not use
>>> bold (700) in the designs.
>>>
>>> There is no Ubuntu font from Google with a width of 600. Google
>>> offers only 300 (light), 400 (regular), 500 (medium) and 700
>>> (bold).
>>>
>>>> On 1. May 2017, at 23:26, Maurice Gesswein <maurice.gesswein@ipfi
>>>> re.org> wrote:
>>>>
>>>> Hi. I just created my 1st bug ticket in bugzilla. Is there no
>>>> edit link for the description?!
>>>>
>>>> On Wed, Apr 26, 2017 at 5:23 PM, Sven <sven.hoehn@posteo.de>
>>>> wrote:
>>>>> no problem.
>>>>>
>>>>>
>>>>>> On 26. Apr 2017, at 17:23, Maurice Gesswein <maurice.gesswein
>>>>>> @ipfire.org> wrote:
>>>>>>
>>>>>> Not yet, sorry. I'm pretty busy at the moment :(
>>>>>>
>>>>>> Am 26.04.2017 1:47 nachm. schrieb "Sven" <sven.hoehn@posteo.d
>>>>>> e>:
>>>>>>> Hello.
>>>>>>> Has someone already put a bug into the Redesign category?
>>>>>>> Do I get a notification if someone put something in there?
>>>>>>>
>>>>>>> Greetings,
>>>>>>> Sven
>>>>>>>
>>>>>>>> On 24. Apr 2017, at 12:11, Michael Tremer <michael.tremer
>>>>>>> @ipfire.org> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> On Mon, 2017-04-24 at 12:02 +0200, Maurice Gesswein
>>>>>>> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I'm going to write some bug reports related to
>>>>>>> dev.ipfire.org. As far as I see
>>>>>>>>> there is no component in Bugzilla for dev.ipfire.org.
>>>>>>> There is only a general
>>>>>>>>> "Web Site" component. Should I use that component for my
>>>>>>> reports and refer
>>>>>>>>> to dev.ipfire.org?
>>>>>>>>
>>>>>>>> Yes, please use that one.
>>>>>>>>
>>>>>>>>> I also remember and see the umbrella bug "Big Website
>>>>>>> Relaunch". I assume that
>>>>>>>>> bugs related to dev.ipfire.org should be somehow linked
>>>>>>> to that umbrella bug.
>>>>>>>>> How does it work? I see nothing helpful on the "new bug"
>>>>>>> form. Is there a
>>>>>>>>> hidden mechanism which links a new bug reports to that
>>>>>>> umbrella bug whenever I
>>>>>>>>> refer to that by writing "#11314" (umbrella bug ID) in
>>>>>>> the summary?
>>>>>>>>
>>>>>>>> You can just add the bug ID in the "blocks" field. That
>>>>>>> will automatically
>>>>>>>> connect the two bug reports.
>>>>>>>>
>>>>>>>> Sorry if I have not been clear about this :) Ask me if
>>>>>>> there is anything else I
>>>>>>>> forgot to mention.
>>>>>>>>
>>>>>>>> -Michael
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>> Maurice
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>