-
Notifications
You must be signed in to change notification settings - Fork 87
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
Attribution/Credits in "Satisfying Real World Use Cases" #53
Comments
Good question. Just for the record, here is a list of people who contributed to the document itself and their previous attribution preference (yes/no) if they gave one:
|
Perhaps a single "authorship" page at the end with a short list like the above with brief information like roles, and a longer list of the workshop attendees and workshop roles/titles? That would arguably represent the most information in context. |
If it helps, in our paper we have author attributions per section, and I'm also thinking we might have an "Authors" or "Acknowledgements" part at the top with all names listed (perhaps including reviewers). Just some ideas we're considering that might be worth thinking about. |
yeah i think this is the right way. and acknowledgements to the "Rebooting On Mon, Nov 9, 2015 at 6:57 PM, Greg Slepak notifications@github.com
|
+1 On Mon, Nov 9, 2015 at 8:46 PM, Juan Benet notifications@github.com wrote:
|
For now I've added a byline, but I like where this conversation is going. Let me know when you settle on something and we can slide it in. |
/cc https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/985eb6010de59303197851173edb82c535d34def/draft-documents/satisfying-real-world-use-cases.md
/re @du5t
How does your team wish to handle attribution? Just "The Participants of the December 2015 #RebootingWebOfTrust Workshop"? A single list of everyone at the workshop? A more narrow list? A list with roles?
Which choice will make the final white paper, edited by @shannona and with graphics from Sonia, more effective to a broader audience?
The text was updated successfully, but these errors were encountered: