You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the x_contributors meta field is taking off (e.g. see https://metacpan.org/source/DAGOLDEN/HTTP-Tiny-0.029/META.json) and the list of contributors is visible in a distribution's right sidebar (under the author), it would be awesome if an author's contributions were also visible on the author's own page (perhaps above their favourited dists? or as a separate page, or a collapsable iframe?)
This would help encourage newbie authors and contributors, as it's a tangible list to point to and say "I made an impact! I am helping!"
The text was updated successfully, but these errors were encountered:
And by properly I mean that we have to split out the pause ID, email address and put them in separate fields. I wish we would have done that form the beginning (#781 (comment)).
Well, it was not there, and then it was there, and then there was a backlash for it not to be there again. The good thing, though, is that now every single possible implementation of those fields exist in the branch of #781. :-)
On a more serious note, I can understand that on the external-facing need to keep things simple. In that regard, just asking for a name and an email is reasonable. But nothing prevent us, I guess, to do some post-munging of those data in ES...
Now that the x_contributors meta field is taking off (e.g. see https://metacpan.org/source/DAGOLDEN/HTTP-Tiny-0.029/META.json) and the list of contributors is visible in a distribution's right sidebar (under the author), it would be awesome if an author's contributions were also visible on the author's own page (perhaps above their favourited dists? or as a separate page, or a collapsable iframe?)
This would help encourage newbie authors and contributors, as it's a tangible list to point to and say "I made an impact! I am helping!"
The text was updated successfully, but these errors were encountered: