Hey PMC. I've connected with the project team to advise them that
this committer has actual visible contributions in the Eclipse S-CORE
project that they should have cited in the nomination statement.
$ git clone
https://github.com/eclipse-score/communication$ cd communication/
$ git shortlog --all --author="Xavier Bonaventura"
Xavier Bonaventura (26):
mw/com: Remove unnecessary string comparison class
mw/com: Cleanup dealing with strings
mw/com: Remove usage of custom string views
mw/com: Keep old API for compatibility
mw/com/rust: Explicitly call std::string_view
aas: Adapt code to v2 version of amp::span
lib/memory: Remove any_string_view
mw/com: Remove usage of custom string views
mw/com: Remove usage of custom string views
mw/com: Adapt code to inotify changes
mw/com: Remove creation of string view
mw/com - config_parser: Add missing include
mw/com: Remove call to .data() and .size()
mw/com: Fix typo
mw/com: Link ticket number to deprecations
mw/com: Remove explicit creaton of string view when it is already one
mw/com: Use string view literals for strings in static storage
mw/com: Remove unused alias
mw/com: Remove unused dependencies
mw/com: Remove deprecated API supporting custom string views
mw/com: Do not access the underlying const char *
lib/json: Use std::string_view in FromFile API
mw/com: Fix string_view in puml files
mw/com: Fix compiler warning due to sign conversion
mw/com: Fix compiler warnings comming from deprecation
tools: Do not explicitly set the Python version
Our
practice has been that adding more information to a mailing list
discussion regarding a committer election is valid. There is no specific
requirement for the election record itself to be updated.
If you feel that this meets with your criteria, I encourage you to approve the election on this basis.
