[fedora-budget] Issue #25 `Work with FAmSCo to get the storyteller role working again`

[Pagure]

bex reported a new issue against the project: `fedora-budget` that you are following:
``
See https://pagure.io/Fedora-Council/tickets/issue/66
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-budget/issue/25

[Pagure]

bex added a new comment to an issue you are following:
``
@jflory7 
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-budget/issue/25

[Pagure]

robyduck added a new comment to an issue you are following:
``
We started a discussion, or more a brainstorming, about the storyteller role during [today's FAmSCo meeting](https://meetbot.fedoraproject.org/fedora-meeting-2/2017-02-01/famsco.2017-02...). The actual definition about his job is just:
The Storytelling Delegate will be accountable for Regional Reports. They don't necessarily have to write all the original content, they just need to be accountable for ensuring content makes it out onto our channels.
Some thoughts we have put on the plate were:
* Should the storyteller to FAmSCo/FOSCo or directly to the FCAIC?
* Define main points every event owner should provide when making his report to the storyteller
* What about non-measurable data? Sometimes an event might have any "good number", but it could be successful anyway if we look to the future of this event (let's call it an investment for the next years)

``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-budget/issue/25

[Brian Exelbierd (bex)]

bex added a new comment to an issue you are following:
``
> We started a discussion, or more a brainstorming, about the storyteller role during today's FAmSCo meeting. The actual definition about his job is just:
> The Storytelling Delegate will be accountable for Regional Reports. They don't necessarily have to write all the original content, they just need to be accountable for ensuring content makes it out onto our channels.
> Some thoughts we have put on the plate were:
> Should the storyteller to FAmSCo/FOSCo or directly to the FCAIC?

My initial thoughts are that the storyteller should be with the "budget unit" not the overall budget.  The thinking being that we need to have consumers of budget able to explain what happened with their usage and why it was good, bad, etc.  I would prefer to see the overall budget org serve a more mechanical/administrative role.
> Define main points every event owner should provide when making his report to the storyteller
> What about non-measurable data? Sometimes an event might have any "good number", but it could be successful anyway if we look to the future of this event (let's call it an investment for the next years)

These are fairly ambassador specific points that I think could be adapted for other uses and would be a great contribution for ambassadors to make to the larger project.

I am trying to get some clarity on the RH side to see if their are other concerns, however I would really like to hear people chime in with their thoughts.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-budget/issue/25