[ https://issues.apache.org/jira/browse/MPIR-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928866#comment-17928866 ]
ASF GitHub Bot commented on MPIR-478: ------------------------------------- slawekjaranowski commented on code in PR #97: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/97#discussion_r1964024075 ########## src/main/java/org/apache/maven/report/projectinfo/TeamReport.java: ########## @@ -226,10 +276,7 @@ private void renderTeamMember(Contributor member, Map<String, Boolean> headersMa Properties properties = member.getProperties(); String picUrl = properties.getProperty("picUrl"); if (picUrl == null || picUrl.isEmpty()) { - picUrl = getGravatarUrl(member.getEmail()); - } - if (picUrl == null || picUrl.isEmpty()) { - picUrl = getSpacerGravatarUrl(); + picUrl = getExternalAvatarUrl(member.getEmail()); Review Comment: I know that I can catch and skip exception, and use default images - but I don't want. As you know one step of release new component is publishing new documentation ... I don't want to add next manual task to verify team page during release. Maybe you have another experience with releasing new components ... Some context of change - look at our team pages: https://maven.apache.org/team.html the same are on many other ASF projects. > describe use of gravatar.com for profiles in team report > -------------------------------------------------------- > > Key: MPIR-478 > URL: https://issues.apache.org/jira/browse/MPIR-478 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: team > Affects Versions: 3.8.0 > Reporter: Herve Boutemy > Assignee: Slawomir Jaranowski > Priority: Major > Fix For: 3.9.0 > > > like MARTIFACT-83, to clarify privacy implications > see > https://github.com/apache/maven-project-info-reports-plugin/blob/master/src/main/java/org/apache/maven/report/projectinfo/TeamReport.java -- This message was sent by Atlassian Jira (v8.20.10#820010)