On 2019-08-01 11:06, Daniel Gruno wrote:
> On 8/1/19 2:19 PM, Patricia Shanahan wrote:
>> I've tried out the tool. I can see it being useful for some projects,
>> and should be available as a choice.
>>
>> However, I would not use it as it is, and hope the existing reporter
>> gets upgraded, not replaced by the wizard. I much prefer to view the
>> whole report as a unit, not just as a series of separate pieces.
>>
>> If it is to become the main way of editing reports it really needs an
>> option to view and edit a draft with one or two clicks, not clicking
>> through all the windows.
>>
>> It would be better to present the help text for each window in a
>> separate text area, so that it can remain visible after there is
>> actual content.
>
> I can definitely see your arguments/frustrations, and a unified option
> would be a great addition - it will be tricky to cram all that
> information into a single text box though, and will likely require a lot
> of logic to figure out where in the report you are, and what assistance
> you need, so as to not display everything all at once and overwhelm the
> layout (and the user). So I opted for the steps as a good starting
> point. That is not to say the unified editing can't be done, but it
> would take a while to figure out how to go about setting it all up,
> graphically and logically.
>
> I have some ideas on the drawing board myself for this, but if anyone
> has any concrete ideas on how to solve this, I'd be happy to hear from
> you :)
As I said on board@ I agree with Patricia here :)
I've seen wizards that would present all the info on a single page, but
collapse each section as it loses focus / scroll is done / "next" button
is pressed. Users could manually expand each section, or press a "Expand
all sections" button to keep everything visible at once?
>> On 7/31/2019 9:06 PM, Daniel Gruno wrote:
>>> On 8/1/19 2:54 AM, Christopher wrote:
>>>> Pretty neat.
>>>>
>>>> Could add a send draft to list feature (private@ or dev@ for
>>>> community review).
>>>> Does it support editing by multiple people? Can one person resume a
>>>> draft saved by another?
>>>
>>> It's being worked on, though there are some considerations to
>>> consider first (so we don't end up with a too-many-chefs issue).
>>>
>>>> Would be nice to have questions from the previous board feedback
>>>> auto-populated to be answered in the current report.
>>>
>>> Also in the works, we just have to figure out some permission issues
>>> here, as we'd be pulling the data from whimsy.
>>>
>>>>
>>>> On Wed, Jul 31, 2019 at 3:34 PM Daniel Gruno <humbed...@apache.org>
>>>> wrote:
>>>>>
>>>>> Hi folks,
>>>>> I've been working on a new board report tool to help address some
>>>>> of the
>>>>> most common issues with the current tool (mainly that it favors
>>>>> auto-inserted metrics over the story and doesn't guide people very
>>>>> well)
>>>>> and have thus far come up with this new wizard:
>>>>>
>>>>> https://reporter.apache.org/wizard/
>>>>>
>>>>> It's open to all committers to review, though easiest if you're on
>>>>> a PMC
>>>>> of some sort. There are some ideas being brewed, and some features
>>>>> that
>>>>> aren't complete (such as the draft/publish buttons and additional
>>>>> helper
>>>>> text).
>>>>>
>>>>> I'd like people to take a look, and provide some feedback. I am
>>>>> stringly
>>>>> contemplating either replacing the existing reporter tool with this
>>>>> (but
>>>>> keeping the getjson.py which powers both), or a link from the old
>>>>> to the
>>>>> new.
>>>>>
>>>>> Anyway, feedback is most welcome!
>>>>> Things will probably change as we go along and feedback comes in.
>>>>>
>>>>> With regards,
>>>>> Daniel.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
