#232 Creation of a Template for Mindshare Event Reports
Closed: Duplicate 3 years ago by riecatnor. Opened 3 years ago by nasirhm.

It was brought up in a Mindshare meeting on 2020-18-19 by @hhlp , that we currently have 14 open tickets in the Mindshare ticket tracker marked as needs event report.

As defined in Mindshare's event report policy, which applies to every mindshare-funded event that we need an event report for reimbursements and has certain consequences if the report is not available depending on the timeline.

It is suggested to create an Event report template for the organizers to fill in their information and images about the event and get it published to make the process more simpler and efficient.


@nasirhm
how is this different than https://pagure.io/mindshare/issue/15?
if it's similar, we can just move it there and close this ticket

It was brought up in a Mindshare meeting on 2020-18-19 by @hhlp , that we currently have 14 open tickets in the Mindshare ticket tracker marked as needs event report.

As defined in Mindshare's event report policy, which applies to every mindshare-funded event that we need an event report for reimbursements and has certain consequences if the report is not available depending on the timeline.

It is suggested to create an Event report template for the organizers to fill in their information and images about the event and get it published to make the process more simpler and efficient.

@nasirhm Yes, this has always been under discussion. The ticket filed by @bex #15 is actually the source and we should take inspiration from that, if we are trying to create one.

Ah @sumantrom & @siddharthvipul1 thank you for pointing that out. We asked @nasirhm to open a ticket in the meeting without looking through aging tickets. I will close this one and we can work on ticket #15

Metadata Update from @riecatnor:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

3 years ago

Metadata Update from @riecatnor:
- Issue status updated to: Open (was: Closed)

3 years ago

Metadata Update from @riecatnor:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata