The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Just like the projects section at the bottom of: http://drupal.org/user/1 this should be a pretty simple port from cvs.module.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 1010046-user_profile_project_list-6.patch | 2.16 KB | mikey_p |
Comments
Comment #1
marvil07 commentedSince the information is living on {versioncontrol_operations} author_uid and committer_uid, I think it have to be provided by versioncontrol ;-)
But, BTW ¿we need two tabs? (one as author, one as commmitter) and maybe we just want to wait to #879600: Meta: introduce an activity stream separate from commit logs
Comment #2
mikey_p commentedI think this needs to live in VC Project since it's a list of Projects, not repositories.
Comment #3
sdboyer commentedThis is not especially hard, but is a crucial part of achieving feature parity, so let's try to knock it out in sprint 8.
A note - I'd really like this to be separated into two listings: one of projects I've got commits in that I maintain, and others that I don't. That separation is going to become more and more important as time goes on, as we'll talk about at length in #986656: Determine approach to commit statistics in post-CVS drupal world.
Comment #4
sdboyer commentedComment #5
sdboyer commentedComment #6
mikey_p commentedThis is basically a direct port of the functionality from CVS module. We can circle back to splitting this out into maintainers vs. contributors later, this is just feature parity as sdboyer noted in #3.
Probably going to go ahead and commit this so that it makes it into vendor branches and is ready for the demo.
Comment #7
mikey_p commentedCommitted, but leaving open for review.
Comment #8
dwwVisually the patch looks great to me. If it works, I'm happy. ;)