dbw9580 commented on a change in pull request #2084:
URL: https://github.com/apache/drill/pull/2084#discussion_r444215763
##########
File path:
contrib/storage-ipfs/src/main/java/org/apache/drill/exec/store/ipfs/IPFSContext.java
##########
@@ -0,0 +1,95 @@
+/*
+ * Copyright (c) 2018-2020 Bowen Ding, Yuedong Xu, Liang Wang
Review comment:
@vvysotskyi We don't intend to keep our names in an contributors list;
we just need a proof that this plugin, at a certain state, was contributed by
us. In fact, we started this as a research project, and I need such a proof to
include in my master's thesis to show these works were really done by me.
I understand that Git history is the best and reliable way to verify
authorship; the problem is Git and Github could be too complicated for someone
who is not familiar with Open Source software development, in contrast to how
people give credits by simply citing literature in research papers.
If possible, I would like to add a commit just before merge, which adds a
authorship statement in `README`, and then another commit to delete it. This
way, I can use that commit as a proof. How does this sound to you?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
