Hi Wayne, I think that is what I am trying
to ask. If we remove Sign-off by, how am I supposed to
correlate the commit to the email. For example, take this PR:
https://github.com/eclipse/eclipse-collections/pull/1058
In the commit, the only way for me to know
the email is by the sign-off. If I go by the user name, I
don’t have the email address available.
When we create our Eclipse accounts, we
have to put in our GitHub user name. Is it possible to have a
ECA Validation Tool where we can check it against the GitHub
user names as well?
Thanks,
Nikhil.
The ECA Validation Tool still exists and
is unchanged. If you can obtain the email address from the
commit, you can determine whether or not we have a signed
ECA associated with that email address.
Hi
Wayne,
This
is great news and I am sure the entire contributor
community will appreciate it!
Just
one question, in case the webhook fails we had a way
previously to verify the ECA using the ECA tool. Will
we have a similar way of doing it in the new workflow?
I
am asking this because as a committer, I will not know
easily the email address associated with the ECA for
the user and how do I validate that I am not accepting
contributions incorrectly.
Thanks,
Nikhil.
Greetings
Eclipse Committers.
We're
making a change to the contribution process.
As
you are aware, when you receive contributions from
developers who are not project committers, we
require those contributors to have signed the
Eclipse Contributor Agreement (ECA) and for
their contributions to to include
a "Signed-off-by" footer with credentials that
match those specified in the "Author" field in
their commit comments. This combination serves an
indication that the contributor understands and
accepts the terms of the
Developer Certificate of Origin (DCO) that
is embedded in the ECA.
Effective
March 30 at 1200h EDT, we are removing the
"Signed-off-by" requirement. Instead, we believe
that the combination of an author's email address
in the "Author" field of a commit and having a
valid ECA (or equivalent committer agreement) on
file fulfill the DCO's "sign-off" requirement.
That is, contributors must still sign the ECA, and
must use the credentials associated with their
Eclipse Foundation account in the "Author" field
of all Git commits, but are no longer required to
include a "Signed-off-by" footer in their commit
comments. Note that it is not wrong for commits to
include "Signed-off-by", it is just no longer
required to meet our IP management goals.
The
Eclipse Webmaster is rolling out updates to the
repository hooks that had previously enforced this
requirement and we are updating related
documentation, including the
Eclipse Foundation Project Handbook.
While
I have your attention, a team of researchers would
like your input.
I,
together with a team of researchers, am trying
to help improve software documentation and
maintainability of open-source projects by
providing automatic support of source code
comments based on code review discussions as a
final goal. We believe that code review tools
store important discussions, and possible
decisions, which can be useful for the project
documentation. Thus, as a starting point, we
would like to learn identifying relevant
information from code review discussions such
that tooling can be developed to improve
software documentation and maintainability of
open-source projects. If you are interested in
talking about your experiences as an
open-source reviewer then please schedule a
meeting with us using YouCanBook.me here: https://tue-interview.youcanbook.me.
Kind regards and
thanks in advance,
Nicole
Novielli, University of Bari,
Fernando
Castor, Federal University of Pernambuco,
Christoph
Treude, University of Adelaide,
Alexander
Serebrenik, Eindhoven University of
Technology,
Felipe
Ebert, Eindhoven University of Technology
--
Wayne
Beaton
Director
of Open Source Projects |
Eclipse
Foundation
The information contained in this e-mail, and any
attachment, is confidential and is intended solely for
the use of the intended recipient. Access, copying or
re-use of the e-mail or any attachment, or any
information contained therein, by any other person is
not authorized. If you are not the intended recipient
please return the e-mail to the sender and delete it
from your computer. Although we attempt to sweep e-mail
and attachments for viruses, we do not guarantee that
either are virus-free and accept no liability for any
damage sustained as a result of viruses.
Please refer to
https://disclaimer.bnymellon.com/eu.htm for
certain disclosures relating to European legal entities.
We take our data protection and privacy responsibilities
seriously and our privacy notice explains how we
collect, use and share personal information in the
course of our business activities. It can be accessed at
the privacy section of
www.bnymellon.com.
_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse.org-committers
--
Wayne
Beaton
Director
of Open Source Projects |
Eclipse
Foundation
