You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Daniel Gruno <hu...@apache.org> on 2017/06/18 08:06:59 UTC
New reporter UI
Hi folks,
I've been working on a new UI for the reporter tool today, and I think
it's coming together nicely. The new UI can be seen at
https://reporter.apache.org/ng.html and should prove to be less
clunky/flashy compared to the old one.
Unless I hear otherwise, I'll change this to be the default UI for the
reporter tool in a few days. Comments, feedback etc is of course very
welcome!
With regards,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by sebb <se...@gmail.com>.
It's looking a lot better now.
However I still think the About link needs to be more prominent.
c.f. projects.a.o which has the About link on the menu line
[I have no idea how to fix it]
Minor nit: Back to top does not quite get to the top.
On 19 June 2017 at 09:33, Daniel Gruno <hu...@apache.org> wrote:
> On 06/19/2017 10:31 AM, Maxim Solodovnik wrote:
>> Hello Daniel,
>>
>> new reported looks nice :)
>> I would add padding-top: 10px; to ngfooter CSS class
>>
>
> Can do! (and did)
>
> With regards,
> Daniel.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/19/2017 10:31 AM, Maxim Solodovnik wrote:
> Hello Daniel,
>
> new reported looks nice :)
> I would add padding-top: 10px; to ngfooter CSS class
>
Can do! (and did)
With regards,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello Daniel,
new reported looks nice :)
I would add padding-top: 10px; to ngfooter CSS class
On Mon, Jun 19, 2017 at 3:22 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 06/19/2017 10:13 AM, Mark Thomas wrote:
> > On 19/06/17 08:31, Daniel Gruno wrote:
> >> On 06/18/2017 11:17 PM, sebb wrote:
> >>> On 18 June 2017 at 17:06, Daniel Gruno <hu...@apache.org> wrote:
> >
> > <snip/>
> >
> >>>> I'm assuming you mean the footer is _not_ always visible now. I don't
> >>>
> >>> Yes.
> >>>
> >>>> think that's a real issue, and I don't think we make use of an 'always
> >>>> visible' footer in many places.
> >>>
> >>> Maybe some of the info could be presented in the header instead.
> >>> e.g. Managed by and About links
> >>> It's important that people can readily find how to report problems.
> >>
> >> I've made the footer sticky now, would this be a reasonable compromise?
> >
> > Personally, I think that is a step backwards as it is giving more
> > prominence to the less frequently needed information. I'd rather see
> > more project report.
> >
> > Something about pleasing all of the people all of the time comes to mind.
> >
> > I suggest you go with whatever you think is best.
>
> I've unstuck it, but made it go to the bottom all the time now (with
> some viewport magic). I'm personally happy with this solution.
>
> In the end, it's not what I think is best, or anyone in comdev for that
> matter, but what the PMC chairs would prefer. Pondering asking them for
> feedback...
>
> With regards,
> Daniel.
>
> >
> > Mark
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
--
WBR
Maxim aka solomax
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/19/2017 10:13 AM, Mark Thomas wrote:
> On 19/06/17 08:31, Daniel Gruno wrote:
>> On 06/18/2017 11:17 PM, sebb wrote:
>>> On 18 June 2017 at 17:06, Daniel Gruno <hu...@apache.org> wrote:
>
> <snip/>
>
>>>> I'm assuming you mean the footer is _not_ always visible now. I don't
>>>
>>> Yes.
>>>
>>>> think that's a real issue, and I don't think we make use of an 'always
>>>> visible' footer in many places.
>>>
>>> Maybe some of the info could be presented in the header instead.
>>> e.g. Managed by and About links
>>> It's important that people can readily find how to report problems.
>>
>> I've made the footer sticky now, would this be a reasonable compromise?
>
> Personally, I think that is a step backwards as it is giving more
> prominence to the less frequently needed information. I'd rather see
> more project report.
>
> Something about pleasing all of the people all of the time comes to mind.
>
> I suggest you go with whatever you think is best.
I've unstuck it, but made it go to the bottom all the time now (with
some viewport magic). I'm personally happy with this solution.
In the end, it's not what I think is best, or anyone in comdev for that
matter, but what the PMC chairs would prefer. Pondering asking them for
feedback...
With regards,
Daniel.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Mark Thomas <ma...@apache.org>.
On 19/06/17 08:31, Daniel Gruno wrote:
> On 06/18/2017 11:17 PM, sebb wrote:
>> On 18 June 2017 at 17:06, Daniel Gruno <hu...@apache.org> wrote:
<snip/>
>>> I'm assuming you mean the footer is _not_ always visible now. I don't
>>
>> Yes.
>>
>>> think that's a real issue, and I don't think we make use of an 'always
>>> visible' footer in many places.
>>
>> Maybe some of the info could be presented in the header instead.
>> e.g. Managed by and About links
>> It's important that people can readily find how to report problems.
>
> I've made the footer sticky now, would this be a reasonable compromise?
Personally, I think that is a step backwards as it is giving more
prominence to the less frequently needed information. I'd rather see
more project report.
Something about pleasing all of the people all of the time comes to mind.
I suggest you go with whatever you think is best.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/18/2017 11:17 PM, sebb wrote:
> On 18 June 2017 at 17:06, Daniel Gruno <hu...@apache.org> wrote:
>> On 06/18/2017 03:15 PM, sebb wrote:
>>> On 18 June 2017 at 09:06, Daniel Gruno <hu...@apache.org> wrote:
>>>> Hi folks,
>>>> I've been working on a new UI for the reporter tool today, and I think
>>>> it's coming together nicely. The new UI can be seen at
>>>> https://reporter.apache.org/ng.html and should prove to be less
>>>> clunky/flashy compared to the old one.
>>>>
>>>> Unless I hear otherwise, I'll change this to be the default UI for the
>>>> reporter tool in a few days. Comments, feedback etc is of course very
>>>> welcome!
>>>
>>> Sorry, but I much prefer the current style.
>>> It seems cleaner to me.
>>>
>>> In comparison with the current style, to my mind the proposed style
>>> has the following disadvantages:
>>> - it's not immediately obvious which tab is selected
>>
>> I'm not sure how to interpret this, but I have changed the text color so
>> it should be more obvious which tab is selected.
>>
>>> - "Add a tab" only works for members and does not actually add a tab
>>> each time it is used.
>>
>> This has now been addressed.
>>
>>> - not as easy to read the tab text as it fills the space
>>
>> I'm sorry but I don't understand the criticism here. Could you
>> elaborate? or maybe your browser displays something I'm not seeing.
>> Perhaps a screenshot would be helpful.
>
> Try adding
>
> httpcomponents
> trafficserver
>
> and you should see what I mean.
> The original tabs allowed space before and after the text.
I've added extra padding in r1799142 to address this issue.
>
>>> - not as easy to read the tab contents as the contrast is reduced
>>
>> Assuming you mean the ToC links, I have made them more visible now. Hope
>> this addresses the concern.
>
> I meant all the text, however the ToC were the worst affected.
>
>>> - tab shapes are not as nice as before
>>
>> I frankly found it too flashy in the end (even though I originally
>> created them that way)...a matter of taste I suppose :)
>>
>>> - the surrounding dark background is distracting
>>
>> The CSS is there for people to change if they can come up with a better
>> color scheme (css/tabs.css) :)
>>
>>> - the back to top links don't take one back to the top
>>
>> I have addressed this issue now, it should link to the very top again.
>>
>>> - the footer contents are always visible (or would be, if an alignment
>>> bug were fixed) so it's always obvious whom to contact
>>
>> I'm assuming you mean the footer is _not_ always visible now. I don't
>
> Yes.
>
>> think that's a real issue, and I don't think we make use of an 'always
>> visible' footer in many places.
>
> Maybe some of the info could be presented in the header instead.
> e.g. Managed by and About links
> It's important that people can readily find how to report problems.
I've made the footer sticky now, would this be a reasonable compromise?
With regards,
Daniel.
>
>>
>> I hope this addresses your concerns.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> The improvements:
>>> - the page footer is not obscured by the scroll box (that should be fixable)
>>> - it's possibly slightly easier to scroll the whole page rather than
>>> scrolling within the box. But this does mean the footer is not always
>>> available.
>>>
>>> I'd much rather see the few minor issues with the current layout fixed.
>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by sebb <se...@gmail.com>.
On 18 June 2017 at 17:06, Daniel Gruno <hu...@apache.org> wrote:
> On 06/18/2017 03:15 PM, sebb wrote:
>> On 18 June 2017 at 09:06, Daniel Gruno <hu...@apache.org> wrote:
>>> Hi folks,
>>> I've been working on a new UI for the reporter tool today, and I think
>>> it's coming together nicely. The new UI can be seen at
>>> https://reporter.apache.org/ng.html and should prove to be less
>>> clunky/flashy compared to the old one.
>>>
>>> Unless I hear otherwise, I'll change this to be the default UI for the
>>> reporter tool in a few days. Comments, feedback etc is of course very
>>> welcome!
>>
>> Sorry, but I much prefer the current style.
>> It seems cleaner to me.
>>
>> In comparison with the current style, to my mind the proposed style
>> has the following disadvantages:
>> - it's not immediately obvious which tab is selected
>
> I'm not sure how to interpret this, but I have changed the text color so
> it should be more obvious which tab is selected.
>
>> - "Add a tab" only works for members and does not actually add a tab
>> each time it is used.
>
> This has now been addressed.
>
>> - not as easy to read the tab text as it fills the space
>
> I'm sorry but I don't understand the criticism here. Could you
> elaborate? or maybe your browser displays something I'm not seeing.
> Perhaps a screenshot would be helpful.
Try adding
httpcomponents
trafficserver
and you should see what I mean.
The original tabs allowed space before and after the text.
>> - not as easy to read the tab contents as the contrast is reduced
>
> Assuming you mean the ToC links, I have made them more visible now. Hope
> this addresses the concern.
I meant all the text, however the ToC were the worst affected.
>> - tab shapes are not as nice as before
>
> I frankly found it too flashy in the end (even though I originally
> created them that way)...a matter of taste I suppose :)
>
>> - the surrounding dark background is distracting
>
> The CSS is there for people to change if they can come up with a better
> color scheme (css/tabs.css) :)
>
>> - the back to top links don't take one back to the top
>
> I have addressed this issue now, it should link to the very top again.
>
>> - the footer contents are always visible (or would be, if an alignment
>> bug were fixed) so it's always obvious whom to contact
>
> I'm assuming you mean the footer is _not_ always visible now. I don't
Yes.
> think that's a real issue, and I don't think we make use of an 'always
> visible' footer in many places.
Maybe some of the info could be presented in the header instead.
e.g. Managed by and About links
It's important that people can readily find how to report problems.
>
> I hope this addresses your concerns.
>
> With regards,
> Daniel.
>
>>
>> The improvements:
>> - the page footer is not obscured by the scroll box (that should be fixable)
>> - it's possibly slightly easier to scroll the whole page rather than
>> scrolling within the box. But this does mean the footer is not always
>> available.
>>
>> I'd much rather see the few minor issues with the current layout fixed.
>>
>>> With regards,
>>> Daniel.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/18/2017 03:15 PM, sebb wrote:
> On 18 June 2017 at 09:06, Daniel Gruno <hu...@apache.org> wrote:
>> Hi folks,
>> I've been working on a new UI for the reporter tool today, and I think
>> it's coming together nicely. The new UI can be seen at
>> https://reporter.apache.org/ng.html and should prove to be less
>> clunky/flashy compared to the old one.
>>
>> Unless I hear otherwise, I'll change this to be the default UI for the
>> reporter tool in a few days. Comments, feedback etc is of course very
>> welcome!
>
> Sorry, but I much prefer the current style.
> It seems cleaner to me.
>
> In comparison with the current style, to my mind the proposed style
> has the following disadvantages:
> - it's not immediately obvious which tab is selected
I'm not sure how to interpret this, but I have changed the text color so
it should be more obvious which tab is selected.
> - "Add a tab" only works for members and does not actually add a tab
> each time it is used.
This has now been addressed.
> - not as easy to read the tab text as it fills the space
I'm sorry but I don't understand the criticism here. Could you
elaborate? or maybe your browser displays something I'm not seeing.
Perhaps a screenshot would be helpful.
> - not as easy to read the tab contents as the contrast is reduced
Assuming you mean the ToC links, I have made them more visible now. Hope
this addresses the concern.
> - tab shapes are not as nice as before
I frankly found it too flashy in the end (even though I originally
created them that way)...a matter of taste I suppose :)
> - the surrounding dark background is distracting
The CSS is there for people to change if they can come up with a better
color scheme (css/tabs.css) :)
> - the back to top links don't take one back to the top
I have addressed this issue now, it should link to the very top again.
> - the footer contents are always visible (or would be, if an alignment
> bug were fixed) so it's always obvious whom to contact
I'm assuming you mean the footer is _not_ always visible now. I don't
think that's a real issue, and I don't think we make use of an 'always
visible' footer in many places.
I hope this addresses your concerns.
With regards,
Daniel.
>
> The improvements:
> - the page footer is not obscured by the scroll box (that should be fixable)
> - it's possibly slightly easier to scroll the whole page rather than
> scrolling within the box. But this does mean the footer is not always
> available.
>
> I'd much rather see the few minor issues with the current layout fixed.
>
>> With regards,
>> Daniel.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by sebb <se...@gmail.com>.
On 18 June 2017 at 09:06, Daniel Gruno <hu...@apache.org> wrote:
> Hi folks,
> I've been working on a new UI for the reporter tool today, and I think
> it's coming together nicely. The new UI can be seen at
> https://reporter.apache.org/ng.html and should prove to be less
> clunky/flashy compared to the old one.
>
> Unless I hear otherwise, I'll change this to be the default UI for the
> reporter tool in a few days. Comments, feedback etc is of course very
> welcome!
Sorry, but I much prefer the current style.
It seems cleaner to me.
In comparison with the current style, to my mind the proposed style
has the following disadvantages:
- it's not immediately obvious which tab is selected
- "Add a tab" only works for members and does not actually add a tab
each time it is used.
- not as easy to read the tab text as it fills the space
- not as easy to read the tab contents as the contrast is reduced
- tab shapes are not as nice as before
- the surrounding dark background is distracting
- the back to top links don't take one back to the top
- the footer contents are always visible (or would be, if an alignment
bug were fixed) so it's always obvious whom to contact
The improvements:
- the page footer is not obscured by the scroll box (that should be fixable)
- it's possibly slightly easier to scroll the whole page rather than
scrolling within the box. But this does mean the footer is not always
available.
I'd much rather see the few minor issues with the current layout fixed.
> With regards,
> Daniel.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/18/2017 02:12 PM, Raphael Bircher wrote:
> Hi Daniel,
>
> Am .06.2017, 10:06 Uhr, schrieb Daniel Gruno <hu...@apache.org>:
>
>> Hi folks,
>> I've been working on a new UI for the reporter tool today, and I think
>> it's coming together nicely. The new UI can be seen at
>> https://reporter.apache.org/ng.html and should prove to be less
>> clunky/flashy compared to the old one.
> I just get "loading page..." how long I have to wait? ;-) I also tryed
> different browsers, It does not help.
Perhaps we need a notice there. You need to be on a PMC (Incubator
excluded) to be able to see results here.
With regards,
Daniel.
>
> Regards, Raphael
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Raphael Bircher <rb...@gmail.com>.
Hi Daniel,
Am .06.2017, 10:06 Uhr, schrieb Daniel Gruno <hu...@apache.org>:
> Hi folks,
> I've been working on a new UI for the reporter tool today, and I think
> it's coming together nicely. The new UI can be seen at
> https://reporter.apache.org/ng.html and should prove to be less
> clunky/flashy compared to the old one.
I just get "loading page..." how long I have to wait? ;-) I also tryed
different browsers, It does not help.
Regards, Raphael
--
My introduction https://youtu.be/Ln4vly5sxYU
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/18/2017 11:07 AM, Pierre Smits wrote:
> Compliance to house styles is something that takes time! And we are working
> with volunteers.
Compliance implies policy. There is no style policy for our web sites.
>
> You're mistaken, Whimsy is not just a PMC only tool.
I did not say that, I said it's an ASF tool :)
>
> The (incubating)t projects have different approaches for their
> (semi-static) project pages is understandable, but they do have mandatory
> elements. And yes, I understood from discussions here and elsewhere that
> discussions were underway to have a more unified approach for ASF sites and
> tooling. So you could say it has already brought forward.
While there are mandatory elements (the apache logo and certain links
and disclaimers), there is no mandatory style for sites.
But, again, if you feel you can enhance the CSS, you are welcome to do so.
With regards,
Daniel.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Sun, Jun 18, 2017 at 10:59 AM, Daniel Gruno <hu...@apache.org> wrote:
>
>> On 06/18/2017 10:52 AM, Pierre Smits wrote:
>>> A House Style is more about branding and overall UX than whether it is
>> for
>>> just static pages (the web site as you call it) or a dynamic web pages
>> with
>>> a tabbed interface (also applied in a web site).
>>>
>>> It is also about colour schemas, imagery, etc. You can take a hint from:
>>>
>>> 1. https://incubator.apache.org/ngtest/
>>> 2. https://whimsy.apache.org
>>
>> Whimsy (an ASF tool) doesn't use the same style as www.apache.org,
>> whereas the incubator site (a public facing page) does. Our main comdev
>> site also doesn't use the same style as www.a.o.
>>
>> This is a PMC-only tool, so I don't see where the branding comes into
>> play. Furthermore, we have no mandatory house style, nor do I believe we
>> should have one. Every project has their own style, and should be
>> allowed to do so.
>>
>> If you feel very strongly about brightening the CSS, feel free to do so.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> ORRTIZ.COM <http://www.orrtiz.com>
>>> OFBiz based solutions & services
>>>
>>> OFBiz Extensions Marketplace
>>> http://oem.ofbizci.net/oci-2/
>>>
>>> On Sun, Jun 18, 2017 at 10:32 AM, Daniel Gruno <hu...@apache.org>
>> wrote:
>>>
>>>> On 06/18/2017 10:29 AM, Pierre Smits wrote:
>>>>> Hi Daniel,
>>>>>
>>>>> Is there no intention to bring it in sync with the house style of the
>>>> ASF?
>>>>
>>>> If you mean www.apache.org, they serve different purposes and the style
>>>> reflects that. I don't see how you would "style" it the same way.
>>>> I've tried to get it closer, color-wise, this time, but it's not gonna
>>>> be a 100% match.
>>>>
>>>> One is a tabbed interface (for a reason), the other is a web site with a
>>>> menu (also for a reason). Using the same menu for the reporter tool
>>>> would arguably make browsing very sluggish.
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Pierre Smits
>>>>>
>>>>> ORRTIZ.COM <http://www.orrtiz.com>
>>>>> OFBiz based solutions & services
>>>>>
>>>>> OFBiz Extensions Marketplace
>>>>> http://oem.ofbizci.net/oci-2/
>>>>>
>>>>> On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org>
>>>> wrote:
>>>>>
>>>>>> Hi folks,
>>>>>> I've been working on a new UI for the reporter tool today, and I think
>>>>>> it's coming together nicely. The new UI can be seen at
>>>>>> https://reporter.apache.org/ng.html and should prove to be less
>>>>>> clunky/flashy compared to the old one.
>>>>>>
>>>>>> Unless I hear otherwise, I'll change this to be the default UI for the
>>>>>> reporter tool in a few days. Comments, feedback etc is of course very
>>>>>> welcome!
>>>>>>
>>>>>> With regards,
>>>>>> Daniel.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Pierre Smits <pi...@gmail.com>.
Compliance to house styles is something that takes time! And we are working
with volunteers.
You're mistaken, Whimsy is not just a PMC only tool.
The (incubating)t projects have different approaches for their
(semi-static) project pages is understandable, but they do have mandatory
elements. And yes, I understood from discussions here and elsewhere that
discussions were underway to have a more unified approach for ASF sites and
tooling. So you could say it has already brought forward.
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Sun, Jun 18, 2017 at 10:59 AM, Daniel Gruno <hu...@apache.org> wrote:
> On 06/18/2017 10:52 AM, Pierre Smits wrote:
> > A House Style is more about branding and overall UX than whether it is
> for
> > just static pages (the web site as you call it) or a dynamic web pages
> with
> > a tabbed interface (also applied in a web site).
> >
> > It is also about colour schemas, imagery, etc. You can take a hint from:
> >
> > 1. https://incubator.apache.org/ngtest/
> > 2. https://whimsy.apache.org
>
> Whimsy (an ASF tool) doesn't use the same style as www.apache.org,
> whereas the incubator site (a public facing page) does. Our main comdev
> site also doesn't use the same style as www.a.o.
>
> This is a PMC-only tool, so I don't see where the branding comes into
> play. Furthermore, we have no mandatory house style, nor do I believe we
> should have one. Every project has their own style, and should be
> allowed to do so.
>
> If you feel very strongly about brightening the CSS, feel free to do so.
>
> With regards,
> Daniel.
>
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM <http://www.orrtiz.com>
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Sun, Jun 18, 2017 at 10:32 AM, Daniel Gruno <hu...@apache.org>
> wrote:
> >
> >> On 06/18/2017 10:29 AM, Pierre Smits wrote:
> >>> Hi Daniel,
> >>>
> >>> Is there no intention to bring it in sync with the house style of the
> >> ASF?
> >>
> >> If you mean www.apache.org, they serve different purposes and the style
> >> reflects that. I don't see how you would "style" it the same way.
> >> I've tried to get it closer, color-wise, this time, but it's not gonna
> >> be a 100% match.
> >>
> >> One is a tabbed interface (for a reason), the other is a web site with a
> >> menu (also for a reason). Using the same menu for the reporter tool
> >> would arguably make browsing very sluggish.
> >>
> >> With regards,
> >> Daniel.
> >>
> >>>
> >>> Best regards,
> >>>
> >>> Pierre Smits
> >>>
> >>> ORRTIZ.COM <http://www.orrtiz.com>
> >>> OFBiz based solutions & services
> >>>
> >>> OFBiz Extensions Marketplace
> >>> http://oem.ofbizci.net/oci-2/
> >>>
> >>> On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org>
> >> wrote:
> >>>
> >>>> Hi folks,
> >>>> I've been working on a new UI for the reporter tool today, and I think
> >>>> it's coming together nicely. The new UI can be seen at
> >>>> https://reporter.apache.org/ng.html and should prove to be less
> >>>> clunky/flashy compared to the old one.
> >>>>
> >>>> Unless I hear otherwise, I'll change this to be the default UI for the
> >>>> reporter tool in a few days. Comments, feedback etc is of course very
> >>>> welcome!
> >>>>
> >>>> With regards,
> >>>> Daniel.
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >>>> For additional commands, e-mail: dev-help@community.apache.org
> >>>>
> >>>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/18/2017 10:52 AM, Pierre Smits wrote:
> A House Style is more about branding and overall UX than whether it is for
> just static pages (the web site as you call it) or a dynamic web pages with
> a tabbed interface (also applied in a web site).
>
> It is also about colour schemas, imagery, etc. You can take a hint from:
>
> 1. https://incubator.apache.org/ngtest/
> 2. https://whimsy.apache.org
Whimsy (an ASF tool) doesn't use the same style as www.apache.org,
whereas the incubator site (a public facing page) does. Our main comdev
site also doesn't use the same style as www.a.o.
This is a PMC-only tool, so I don't see where the branding comes into
play. Furthermore, we have no mandatory house style, nor do I believe we
should have one. Every project has their own style, and should be
allowed to do so.
If you feel very strongly about brightening the CSS, feel free to do so.
With regards,
Daniel.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Sun, Jun 18, 2017 at 10:32 AM, Daniel Gruno <hu...@apache.org> wrote:
>
>> On 06/18/2017 10:29 AM, Pierre Smits wrote:
>>> Hi Daniel,
>>>
>>> Is there no intention to bring it in sync with the house style of the
>> ASF?
>>
>> If you mean www.apache.org, they serve different purposes and the style
>> reflects that. I don't see how you would "style" it the same way.
>> I've tried to get it closer, color-wise, this time, but it's not gonna
>> be a 100% match.
>>
>> One is a tabbed interface (for a reason), the other is a web site with a
>> menu (also for a reason). Using the same menu for the reporter tool
>> would arguably make browsing very sluggish.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> ORRTIZ.COM <http://www.orrtiz.com>
>>> OFBiz based solutions & services
>>>
>>> OFBiz Extensions Marketplace
>>> http://oem.ofbizci.net/oci-2/
>>>
>>> On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org>
>> wrote:
>>>
>>>> Hi folks,
>>>> I've been working on a new UI for the reporter tool today, and I think
>>>> it's coming together nicely. The new UI can be seen at
>>>> https://reporter.apache.org/ng.html and should prove to be less
>>>> clunky/flashy compared to the old one.
>>>>
>>>> Unless I hear otherwise, I'll change this to be the default UI for the
>>>> reporter tool in a few days. Comments, feedback etc is of course very
>>>> welcome!
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Dave Fisher <da...@comcast.net>.
I agree. I want to thank Daniel for his efforts.
Regards,
Dave
Sent from my iPhone
> On Jun 18, 2017, at 6:25 AM, Patricia Shanahan <pa...@acm.org> wrote:
>
> Not a response to this message in particular, but to the whole thread. I
> have an uneasy feeling that "What format should the web page be?" is
> going to be the 21st Century version of "What form should the bike shed
> take?" https://en.wikipedia.org/wiki/Law_of_triviality
>
>> On 6/18/2017 1:52 AM, Pierre Smits wrote:
>> A House Style is more about branding and overall UX than whether it is for
>> just static pages (the web site as you call it) or a dynamic web pages with
>> a tabbed interface (also applied in a web site).
>> It is also about colour schemas, imagery, etc. You can take a hint from:
>> 1. https://incubator.apache.org/ngtest/
>> 2. https://whimsy.apache.org
>> Best regards,
>> Pierre Smits
>> ORRTIZ.COM <http://www.orrtiz.com>
>> OFBiz based solutions & services
>> OFBiz Extensions Marketplace
>> http://oem.ofbizci.net/oci-2/
>>> On Sun, Jun 18, 2017 at 10:32 AM, Daniel Gruno <hu...@apache.org> wrote:
>>>> On 06/18/2017 10:29 AM, Pierre Smits wrote:
>>>> Hi Daniel,
>>>>
>>>> Is there no intention to bring it in sync with the house style of the
>>> ASF?
>>>
>>> If you mean www.apache.org, they serve different purposes and the style
>>> reflects that. I don't see how you would "style" it the same way.
>>> I've tried to get it closer, color-wise, this time, but it's not gonna
>>> be a 100% match.
>>>
>>> One is a tabbed interface (for a reason), the other is a web site with a
>>> menu (also for a reason). Using the same menu for the reporter tool
>>> would arguably make browsing very sluggish.
>>>
>>> With regards,
>>> Daniel.
>>>
>>>>
>>>> Best regards,
>>>>
>>>> Pierre Smits
>>>>
>>>> ORRTIZ.COM <http://www.orrtiz.com>
>>>> OFBiz based solutions & services
>>>>
>>>> OFBiz Extensions Marketplace
>>>> http://oem.ofbizci.net/oci-2/
>>>>
>>>> On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org>
>>> wrote:
>>>>
>>>>> Hi folks,
>>>>> I've been working on a new UI for the reporter tool today, and I think
>>>>> it's coming together nicely. The new UI can be seen at
>>>>> https://reporter.apache.org/ng.html and should prove to be less
>>>>> clunky/flashy compared to the old one.
>>>>>
>>>>> Unless I hear otherwise, I'll change this to be the default UI for the
>>>>> reporter tool in a few days. Comments, feedback etc is of course very
>>>>> welcome!
>>>>>
>>>>> With regards,
>>>>> Daniel.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Patricia Shanahan <pa...@acm.org>.
Not a response to this message in particular, but to the whole thread. I
have an uneasy feeling that "What format should the web page be?" is
going to be the 21st Century version of "What form should the bike shed
take?" https://en.wikipedia.org/wiki/Law_of_triviality
On 6/18/2017 1:52 AM, Pierre Smits wrote:
> A House Style is more about branding and overall UX than whether it is for
> just static pages (the web site as you call it) or a dynamic web pages with
> a tabbed interface (also applied in a web site).
>
> It is also about colour schemas, imagery, etc. You can take a hint from:
>
> 1. https://incubator.apache.org/ngtest/
> 2. https://whimsy.apache.org
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Sun, Jun 18, 2017 at 10:32 AM, Daniel Gruno <hu...@apache.org> wrote:
>
>> On 06/18/2017 10:29 AM, Pierre Smits wrote:
>>> Hi Daniel,
>>>
>>> Is there no intention to bring it in sync with the house style of the
>> ASF?
>>
>> If you mean www.apache.org, they serve different purposes and the style
>> reflects that. I don't see how you would "style" it the same way.
>> I've tried to get it closer, color-wise, this time, but it's not gonna
>> be a 100% match.
>>
>> One is a tabbed interface (for a reason), the other is a web site with a
>> menu (also for a reason). Using the same menu for the reporter tool
>> would arguably make browsing very sluggish.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> ORRTIZ.COM <http://www.orrtiz.com>
>>> OFBiz based solutions & services
>>>
>>> OFBiz Extensions Marketplace
>>> http://oem.ofbizci.net/oci-2/
>>>
>>> On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org>
>> wrote:
>>>
>>>> Hi folks,
>>>> I've been working on a new UI for the reporter tool today, and I think
>>>> it's coming together nicely. The new UI can be seen at
>>>> https://reporter.apache.org/ng.html and should prove to be less
>>>> clunky/flashy compared to the old one.
>>>>
>>>> Unless I hear otherwise, I'll change this to be the default UI for the
>>>> reporter tool in a few days. Comments, feedback etc is of course very
>>>> welcome!
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Rich Bowen <rb...@rcbowen.com>.
On 06/18/2017 10:52 AM, Pierre Smits wrote:
> A House Style is more about branding and overall UX than whether it is for
> just static pages (the web site as you call it) or a dynamic web pages with
> a tabbed interface (also applied in a web site).
>
> It is also about colour schemas, imagery, etc. You can take a hint from:
>
> 1. https://incubator.apache.org/ngtest/
> 2. https://whimsy.apache.org
Pierre, the code is here:
https://svn.apache.org/repos/asf/comdev/reporter.apache.org/
we welcome you (and everyone else!) to dive in and improve the tool,
including bringing it more into line with the house styles. I know that
Sally has been working towards codifying these styles, although I must
admit I don't know where that work is available.
Meanwhile, thanks, Daniel, for your hard work on improving these tools,
and the overall reporting quality of our projects. Those of us reading
the board reports greatly appreciate it.
--
Rich Bowen - rbowen@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon
Re: New reporter UI
Posted by Pierre Smits <pi...@gmail.com>.
A House Style is more about branding and overall UX than whether it is for
just static pages (the web site as you call it) or a dynamic web pages with
a tabbed interface (also applied in a web site).
It is also about colour schemas, imagery, etc. You can take a hint from:
1. https://incubator.apache.org/ngtest/
2. https://whimsy.apache.org
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Sun, Jun 18, 2017 at 10:32 AM, Daniel Gruno <hu...@apache.org> wrote:
> On 06/18/2017 10:29 AM, Pierre Smits wrote:
> > Hi Daniel,
> >
> > Is there no intention to bring it in sync with the house style of the
> ASF?
>
> If you mean www.apache.org, they serve different purposes and the style
> reflects that. I don't see how you would "style" it the same way.
> I've tried to get it closer, color-wise, this time, but it's not gonna
> be a 100% match.
>
> One is a tabbed interface (for a reason), the other is a web site with a
> menu (also for a reason). Using the same menu for the reporter tool
> would arguably make browsing very sluggish.
>
> With regards,
> Daniel.
>
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM <http://www.orrtiz.com>
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org>
> wrote:
> >
> >> Hi folks,
> >> I've been working on a new UI for the reporter tool today, and I think
> >> it's coming together nicely. The new UI can be seen at
> >> https://reporter.apache.org/ng.html and should prove to be less
> >> clunky/flashy compared to the old one.
> >>
> >> Unless I hear otherwise, I'll change this to be the default UI for the
> >> reporter tool in a few days. Comments, feedback etc is of course very
> >> welcome!
> >>
> >> With regards,
> >> Daniel.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: New reporter UI
Posted by Daniel Gruno <hu...@apache.org>.
On 06/18/2017 10:29 AM, Pierre Smits wrote:
> Hi Daniel,
>
> Is there no intention to bring it in sync with the house style of the ASF?
If you mean www.apache.org, they serve different purposes and the style
reflects that. I don't see how you would "style" it the same way.
I've tried to get it closer, color-wise, this time, but it's not gonna
be a 100% match.
One is a tabbed interface (for a reason), the other is a web site with a
menu (also for a reason). Using the same menu for the reporter tool
would arguably make browsing very sluggish.
With regards,
Daniel.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org> wrote:
>
>> Hi folks,
>> I've been working on a new UI for the reporter tool today, and I think
>> it's coming together nicely. The new UI can be seen at
>> https://reporter.apache.org/ng.html and should prove to be less
>> clunky/flashy compared to the old one.
>>
>> Unless I hear otherwise, I'll change this to be the default UI for the
>> reporter tool in a few days. Comments, feedback etc is of course very
>> welcome!
>>
>> With regards,
>> Daniel.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Pierre Smits <pi...@gmail.com>.
Hi Daniel,
Is there no intention to bring it in sync with the house style of the ASF?
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Sun, Jun 18, 2017 at 10:06 AM, Daniel Gruno <hu...@apache.org> wrote:
> Hi folks,
> I've been working on a new UI for the reporter tool today, and I think
> it's coming together nicely. The new UI can be seen at
> https://reporter.apache.org/ng.html and should prove to be less
> clunky/flashy compared to the old one.
>
> Unless I hear otherwise, I'll change this to be the default UI for the
> reporter tool in a few days. Comments, feedback etc is of course very
> welcome!
>
> With regards,
> Daniel.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: New reporter UI
Posted by Mark Thomas <ma...@apache.org>.
On 18/06/17 09:06, Daniel Gruno wrote:
> Hi folks,
> I've been working on a new UI for the reporter tool today, and I think
> it's coming together nicely. The new UI can be seen at
> https://reporter.apache.org/ng.html and should prove to be less
> clunky/flashy compared to the old one.
>
> Unless I hear otherwise, I'll change this to be the default UI for the
> reporter tool in a few days. Comments, feedback etc is of course very
> welcome!
I like it. In particular, a greater % of the screen area is put to a
useful use (i.e. showing me the info I actually want to see).
Thanks for your work on this.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: New reporter UI
Posted by Christopher <ct...@apache.org>.
Looks good.
One suggestion: please fix the time zone translation for the release dates.
The browser is converting the timezone to its local time zone, but these
dates are date/times, they are just dates, and should not be converted
based on time zone. This is annoying because different viewers in time
zones west of UTC will show release dates that are one day earlier than the
actual release date.
This was fixed in the "Manage release versions" page, but it was never
fixed in the "Last release was X.Y.Z, released on ddd MMM DD YYYY" part or
in the "Releases" section of the "Report template". I'm not sure the exact
fix, but it seems like it just needs to always present as UTC (since that's
the zone assumed when the raw date string is parsed), regardless of the
browser's time zone.
The only other place a date appears to be shown is "Next report date", and
it looks like that's correctly not doing any time zone translation.
It's not a serious issue, but it's annoying. :)
On Sun, Jun 18, 2017 at 4:07 AM Daniel Gruno <hu...@apache.org> wrote:
> Hi folks,
> I've been working on a new UI for the reporter tool today, and I think
> it's coming together nicely. The new UI can be seen at
> https://reporter.apache.org/ng.html and should prove to be less
> clunky/flashy compared to the old one.
>
> Unless I hear otherwise, I'll change this to be the default UI for the
> reporter tool in a few days. Comments, feedback etc is of course very
> welcome!
>
> With regards,
> Daniel.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: New reporter UI
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Am 18.06.2017 um 10:06 schrieb Daniel Gruno:
> Hi folks,
> I've been working on a new UI for the reporter tool today, and I think
> it's coming together nicely. The new UI can be seen at
> https://reporter.apache.org/ng.html and should prove to be less
> clunky/flashy compared to the old one.
>
> Unless I hear otherwise, I'll change this to be the default UI for the
> reporter tool in a few days. Comments, feedback etc is of course very
> welcome!Some/all of the mailing lists are shown twice
>
> With regards,
> Daniel.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org