Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

engagement report from first activity #2 #8

Open
govvin opened this issue Mar 1, 2016 · 8 comments
Open

engagement report from first activity #2 #8

govvin opened this issue Mar 1, 2016 · 8 comments

Comments

@govvin
Copy link
Member

govvin commented Mar 1, 2016

Connected to #2 .

PDRF and HSBC is requesting for a summary report from the engagement last September.

@govvin govvin changed the title engagement report from first activity engagement report from first activity #2 Mar 1, 2016
@maning
Copy link
Member

maning commented Mar 1, 2016

I don't think we should do this, it was not part of the initial agreement with PDRF.
Unless you have a diary we can just reference.

@govvin
Copy link
Member Author

govvin commented Mar 1, 2016

What were the agreements @maning ? Wala akong diary entry for that activity eh.

@maning
Copy link
Member

maning commented Mar 1, 2016

We just run the event no commitments on any writeup.

@govvin
Copy link
Member Author

govvin commented Mar 1, 2016

I would've written one, but I just don't have the time right now. :/ Anyway, @ralleon , if you're willing, maybe you could write a one-page brief? You were the designated ringmaster, anyway - top hat, mustache, and megaphone. 😆

@seav
Copy link
Member

seav commented Mar 2, 2016

I think we should do this. We should document our events and partnerships, even if for ourselves anyway. Did PDRF specify any requirements or can we just do a freeform report on our own?

@govvin
Copy link
Member Author

govvin commented Mar 2, 2016

They didn't specify any format, so a free-form document would be just as acceptable.

Off-hand, what I would personally like see in such a brief:

  • basic metrics, before and after (if it was a data mapathon)
  • topics covered
  • significant concerns encountered (by facilitators, by participants), if any
  • participants' profile (hoping to see inclusiveness, diversity)
  • are participants still editing X period after the engagement?
  • feedback from participants

@maning
Copy link
Member

maning commented Mar 2, 2016

Yes, for our own purpose we should write something for every event preferrably as an OSM diary. Its just that for the previous PDRF-HSBC mapathon, we don't have an agreement to do this as part of the engagement. So the burden is not on us nor this is should be a pre-requisite for the next mapping event we are discussing in #2.

👍 on the basic outline ☝️

@govvin
Copy link
Member Author

govvin commented Mar 2, 2016

👍 for the diary entry, then post links to other social media channels.

Clarification: when Rheeza (?) from HSBC inquired for a report, I replied that I don't think we were required to do any, but she asked if it's possible to get some kind of report, and I thought, the after-event diary entry content would suffice. Since @ralleon coordinated closely with HSBC (and PDRF), I thought it best to ping him directly, and made the suggestion to use the previous diary entries a guide.

From my POV, the "report" is beneficial for everyone - us, the OSM community-at-large, and our other collaborators. The only issue right now is finding someone with some time to gather the details, and write a diary/brief/report.

For future events, I agree that we should make them part of the post-event checklist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants