Newsgroups: php.internals,php.webmaster
Path: news.php.net
Xref: news.php.net php.internals:97931 php.webmaster:25531
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
Sender: Maciej Sobaczewski <msobaczewski@gmail.com>
To: Andreas Heigl <andreas@heigl.org>, php-webmaster@lists.php.net
References: <9b34a688-49ad-ad0c-50e5-8baa0b52045f@php.net>
 <eaa73cd7-fad1-5b14-6fb5-cba12ecb8ece@heigl.org>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <f467f552-76af-78f2-4007-9b714c2a1e06@php.net>
Date: Mon, 23 Jan 2017 09:48:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <eaa73cd7-fad1-5b14-6fb5-cba12ecb8ece@heigl.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-WEBMASTER] Redesign of bugs.php.net
From: sobak@php.net (Maciej Sobaczewski)

W dniu 23.01.2017 o 09:44, Andreas Heigl pisze:
> Am 23.01.17 um 08:22 schrieb Maciej Sobaczewski:
>> Hello,
>>
>> I know it's bringing the same thread again but since my last post[1]
>> I gathered some feedback on /r/php, including a few membmers of PHP.net.
>>
>> https://github.com/Sobak/bugsnet-redesign-mockup this is the repo for
>> my experimental approach on redesigning PHP.net. Short story: I took the
>> design of php.net main website and after some modifications used it for
>> our bugtracker.
>>
>> Long story? All details are in the repo's README file. At the moment,
>> this is just a static mockup but I'm ready to start feature branch on
>> web/bugs as soon as I get your opinions.
>>
>> Make sure to read section on Functional changes[2] I'd like to happen.
>> I know these should be separated from the redesign but I limited myself
>> to suggestions which are strictly connected to the interface/UX.
>>
>> What are your thoughts? Does it look good? Can I start the branch or
>> you prefer something entirely different/leaving it as-is?
>>
>> CC'ed to php.internals to make sure it'll reach most of bugsnet users.
>>
>> [1]: http://news.php.net/php.webmaster/25510
>> [2]: https://github.com/Sobak/bugsnet-redesign-mockup#functional-changes
>>
> Great work! Thanks.
>
> Here are my personal thougts:
>
> 1. Shouldn't we talk about "issues" instead of "bugs"? One of the types
> clearly is "bug" but the tracker should also contain stuff that aren'T
> bugs so "issues" seems more appropriate. And yes, I wouldn't rename the
> whole thing to issues.php.net even though that would better fit in my
> eyes ;)
>
> 2. On creating an issue I'd put the Issue-Title right on top: Bold and
> large. Everything else is then detail…
>
> Apart from that I'd really love a feature to edit multiple issues at
> once. But that's something for a later stage!
>
> I'm definitely looking forward to seeing that going live in the near future!
>
> Cheers
>
> Andreas
>

Hi Andreas,

1) I'd like to handle such changes separately. Diff between eventual
branches to review and merge is going to be quite big anyway.

2) Right, I'll move it to the top. We'll see how would it look bolded,
I consider it only a proposal which is a subject to change.

Thanks,
Maciej.