Come up with strategy for follow-up

[Daniel-Mietchen]

Follow-up in terms of

• projects that were worked on at this event
• people who attended the event
• other events where some of the work from this event could be continued
• potential contributions to Open Data Day 2018

[npscience]

What about resources for people to take projects forward?

e.g. https://aws.amazon.com/grants/ is a quarterly grant scheme that gives credits to people that want to use cloud services, including for educating researchers in open data type cloud tools.

[npscience]

Can we recognise contributors using a hatrack? See https://github.com/LABHR/hatrack

[Daniel-Mietchen]

@npscience can you turn this into an idea issue and give a pitch on it?

[npscience]

This is now issue #49 - I can pitch it tomorrow.

[C21Beancounter]

Daniel. Didnt know where else to put this. Following the discussion about providing academics/researchers with a simple way (e.g. infographic) of knowing which mechanisms (e.g. platforms, apps) might be in line with their Open Access (or other!) principles.

Here is an example of a project trying to provide such assistance (with apps, and not specifically for academia): http://redecentralize.org/radar/ and the report from which it was inspired https://assets.thoughtworks.com/assets/technology-radar-nov-2016-en.pdf.

This is slightly different to the issue of signposting changes in ownership of widely used free platforms, but still, this was the best I could do to answer my own question!

[JosephMcArthur]

• Look at additional milestone

• send email

• let folks know that if they're going to do more work leave a note in the follow up email !

[goodwingibbins]

For the people who attended to stay connected with each other and other people with similar interests, don't forget about the Open Research London Community Meet-up @OpenResLDN and similar perhaps to follow. There's nothing like bumping into someone face to face again and being able to catch up on and suggest developments to something you worked on once in the distant past ;)

[Daniel-Mietchen]

@JosephMcArthur add to the follow-up email a question like "What would you change in future events of this kind?"

[JosephMcArthur]

I think we could follow up on project's status's by just responding to tickets

[Daniel-Mietchen]

One follow-up not mentioned here yet is the
https://github.com/sparcopen/do-a-doathon
repo that came out of #47, which is now serving as the basis for a new event currently being set up at https://github.com/UVA-DSI/2017-doathon .

[JosephMcArthur]

Hey Daniel, That's ace! This site: https://github.com/sparcopen/doathon-dev which is going to be formally launched soon (not quite yet done), may be very helpful! We've done a lot of developing on the concept there, and the site is planned as a potential template & approach for others moving forwards (post-OpenCon 2017). J

On Fri, 20 Oct 2017 at 15:00 Daniel Mietchen ***@***.***> wrote: One follow-up not mentioned here yet is the https://github.com/sparcopen/do-a-doathon repo that came out of #47 <#47>, which is now serving as the basis for a new event currently being set up at https://github.com/UVA-DSI/2017-doathon . — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEuWZ1xVLwjG06HHqYAo9HPH-xV8GcBRks5suKdCgaJpZM4L_j50> .

-- Joseph McArthur Assistant Director: Right to Research Coalition <http://righttoresearch.org/> Co-Lead/Founder: Open Access Button <http://openaccessbutton.org/> Twitter: @Mcarthur_Joe <https://twitter.com/Mcarthur_Joe> Skype: joseph_mcarthur

[Daniel-Mietchen]

OK, looks great except for the licensing, on which I just opened a ticket. Our event will be a few days post-OpenCon, so lots of potential for interaction. I'll also try to attend your doathon remotely.