-
Notifications
You must be signed in to change notification settings - Fork 6
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
Joint publication about results of the hackathon #9
Comments
+1 Question-based format that could be used for this hackathon
|
This is a great suggestion. I like the template provided by @ljgarcia . We will publish a hackathon report for sure. |
Just for clarification (and conclude this issue), you will take care of sending the form to project leaders and stuff around @TomMiksa? |
I have created this document: https://docs.google.com/document/d/1oMyArI3xTALO6fi3xYdMmO9LoHqJE9LFKqWYTn3K5XY/edit?usp=sharing I will contact the team leaders to get the contributions. I would appreciate any help in polishing the report, selecting a place for publishing, and in general pulling it over the finish line. |
Hi Thomas,
I was able to watch 2/3 of the wrap-up today! Very very useful. Thanks again for pointing me to your hackathon.
Enjoy the weekend. Here in Norway, we have blue skies. 🙂
Best
VJ
…________________________________
From: TomMiksa <[email protected]>
Sent: Friday, May 29, 2020 6:22 PM
To: RDA-DMP-Common/hackathon-2020 <[email protected]>
Cc: Subscribed <[email protected]>
Subject: Re: [RDA-DMP-Common/hackathon-2020] Joint publication about results of the hackathon (#9)
I have created this document: https://docs.google.com/document/d/1oMyArI3xTALO6fi3xYdMmO9LoHqJE9LFKqWYTn3K5XY/edit?usp=sharing
I will contact the team leaders to get the contributions. I would appreciate any help in polishing the report, selecting a place for publishing, and in general pulling it over the finish line.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#9 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APTK5MGNGSIUJPT3XB33R2DRT7ON7ANCNFSM4MXDS3MA>.
|
What would you say about publishing the hackathon report here? https://riojournal.com |
Hi,
The RIO Journal looks like a good venue for the hackathon report. Please
let me know whether you want an extra pair of eyes to help harmonizing the
different projects and/or go through the whole document
Regards,
…On Mon, Jun 15, 2020 at 5:40 PM TomMiksa ***@***.***> wrote:
What would you say about publishing the hackathon report here?
https://riojournal.com
Seems to be a good fit. Any other ideas?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJNANBDJTAEIW4PG5OBVXLRWY6HNANCNFSM4MXDS3MA>
.
|
Yes, your help @ljgarcia would be very valuable! |
Hi,
I do not mind latex or GDocs. What is required/supported by the RIO Journal?
Indeed, the contents are what is provided by the project leads. It is more
about harmonization.
How do you want to proceed?
Cheers,
…On Tue, Jun 16, 2020 at 10:30 AM TomMiksa ***@***.***> wrote:
Yes, your help @ljgarcia <https://github.com/ljgarcia> would be very
valuable!
I think we should make the text coherent. I wouldn't not interfere much
with the contents. Do you think we should use a latex template?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJNANHCAQMCWCOB6BBYDGDRW4UT3ANCNFSM4MXDS3MA>
.
|
It looks that we would have to pay to publish in RIO. Maybe CODATA is a better option then (RDA Europe could cover the costs potentially)? Let's harmonize the report first and then we will look for a place to publish. Maybe some other ideas will come? |
It would be great if we can write a publication together to present our results for sharing and referencing...
The text was updated successfully, but these errors were encountered: