Redesign of bugs.php.net

php.internals

Maciej Sobaczewski

9 years ago
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

Michael Wallner

9 years ago
On 23/01/17 08:22, Maciej Sobaczewski wrote:
> 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 >
Looks good to me, great work, thanks! Just one thing, comments' text look tiny, don't they?
-- Regards, Mike

Maciej Sobaczewski

9 years ago
> Looks good to me, great work, thanks! > Just one thing, comments' text look tiny, don't they? >
Hi Mike, do you judge by the screenshots or an online demo? http://sobak.pl/php-bugs-mockup/bug.html Thank you for the kind words, by the way. Cheers

Michael Wallner

9 years ago
On 23/01/17 09:38, Maciej Sobaczewski wrote:
> > do you judge by the screenshots or an online demo? > http://sobak.pl/php-bugs-mockup/bug.html >
Ah, yeah, thanks. I was looking at the screenshot; it looks definitely better in Firefox.
-- Regards, Mike

Andreas Heigl

9 years ago
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
-- ,,, (o o) +---------------------------------------------------------ooO-(_)-Ooo-+ | Andreas Heigl | | mailto:andreas@heigl.org N 50°22'59.5" E 08°23'58" | | http://andreas.heigl.org http://hei.gl/wiFKy7 | +---------------------------------------------------------------------+ | http://hei.gl/root-ca | +---------------------------------------------------------------------+

Maciej Sobaczewski

9 years ago
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.

Tom Sommer

9 years ago
On 2017-01-23 08:22, Maciej Sobaczewski wrote:
> What are your thoughts? Does it look good? Can I start the branch or > you prefer something entirely different/leaving it as-is?
The "button-links" move the layout when you hover over them, because of the style-change to italic, very annoying for the eye. Would it not make sense to just make these clickable buttons? Or at least underline them to show they are clickable? Not very friendly at the moment. // Tom