Replacements that use git data for the blocks at http://drupal.org/cvs:

For phase 2 this should be straightforward, but pending the outcome of #782408: Decide on an approach to recording commit statistics (and thereby, standardize the recommended merge workflow) we may need to mix them back up again.

[Edited by kiamlaluno to fix the link to the image, which was not showing]

Comments

sdboyer’s picture

sdboyer commented
Issue tags: +git phase 2

tagging

mikey_p’s picture

mikey_p commented

It seems that currently these blocks are only used on the global commit view page. If that gets nuked in #782618: Create a global git commit view, then we may not have a place to display there, even though they are probably more interesting than the global commit view itself.

sdboyer’s picture

sdboyer commented

Even if we nuke that commit listing, I don't think the page itself should necessarily go away. In fact, we might consider expanding these blocks to occupy the main page area, and provide slightly more detailed statistics. Or some other kind of global statistics. Whatever we do, I'm +1 on these and -1 on the global commit view...so personally, I'd like to figure out a way to keep them around :)

dww’s picture

dww
we/he/they
commented
Title: Create git analogue to most active projects/developers blocks » Create git analogue to most active developers block

I moved #850146: Create git analogue to most active projects blocks into a separate issue since that's going to be the responsibility of versioncontrol_project, and it's better to keep each issue as self-contained as possible.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Project: Drupal.org infrastructure » Version Control / Project* integration
Version: » 6.x-2.x-dev
Component: Git » Code

Moving to the right project. This may or may not be relevant anymore after project metrics discussion is done.

dww’s picture

dww
we/he/they
commented
Project: Version Control / Project* integration » Version Control API
Component: Code » API module
Status: Active » Postponed

Actually, this doesn't have anything to do with projects, so it really belongs in vcapi itself, not in vc_project. We could probably use a better component for this -- the choices in this queue are a bit narrow. ;)

That said, yeah, it might be dependent on sampler in some way, I'm not sure yet.

If not, it's blocked on #782586: Merge views module into the main versioncontrol module.

So, either way, this is blocked on something else... hence postponed.

marvil07’s picture

marvil07 commented
Status: Postponed » Active

re-opening as start commit of views is about to be committed

marvil07’s picture

marvil07 commented

The base of views integration is committed, but I really do not know how to do group by on views(without depending on another module) nor I reviewed the sampler module, but I have a query to paste here:

SELECT users.name AS users_name, users.uid AS users_uid, COUNT(versioncontrol_operations.vc_op_id) as ranking
FROM versioncontrol_operations versioncontrol_operations 
INNER JOIN users users ON versioncontrol_operations.uid = users.uid
WHERE versioncontrol_operations.uid <> 0
GROUP BY versioncontrol_operations.uid
ORDER BY ranking DESC
marvil07’s picture

marvil07 commented

Since #970256: Introduce additional fields on operations table for capturing user mappings, now we need two queries, one for author_uid and the other for committer_uid. Naturally we can just skip one of them if we only want to show one of those profiles.

sdboyer’s picture

sdboyer commented
Issue tags: -git phase 2 +git phase 3, +git phase 2 leftovers

For the same reasons as in #850146-1: Create git analogue to most active projects blocks, punting out of phase 2.

marvil07’s picture

marvil07 commented
Title: Create git analogue to most active developers block » Create a most active developers block based on versioncontrol data
Category: task » feature

not sure if we still want to define "most active", but changing title and category in this bug triage

marvil07’s picture

marvil07 commented
Status: Active » Closed (won't fix)

This should be focus on event data(not on operations), and based on activity related code(gsoc-activity feature branch), so let's re-think that later.

(changed during triage)