Moodle Community Sites

Moodle.org - CVS Developers Module - Ability to Remove a Developer

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Component/s: CVS repository
  • Labels:
    None

Description

While a specific case has not yet come up, thinking I ahead I can see it being helpful to be able to delete a developer from the CVS module - especially with CONTRIB code. The immediate workaround would be to simply remove the directories that the person has access for; however, it would be nice to have a remove option somewhere in the administration tab.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tim Hunt added a comment -

Anthony, one question that the CVS module answers is, when I am looking at ancient CVS history, and I wonder "Who was [wierdname] who made this change".

So I don't think people who have ever committed anything to CSV should be removed.

However, people who do not currently have access should not be listed by default. (There should be a "show all" option, or something.)

Show
Tim Hunt added a comment - Anthony, one question that the CVS module answers is, when I am looking at ancient CVS history, and I wonder "Who was [wierdname] who made this change". So I don't think people who have ever committed anything to CSV should be removed. However, people who do not currently have access should not be listed by default. (There should be a "show all" option, or something.)
Hide
Permalink
Anthony Borrow added a comment -

Tim - As I understand it, the CVS module is meant to show the current list of folks with write access. I'm not sure it is meant to be a historical record. Although, I do like the idea of having it function that way whereby the record is not actually deleted but simply marked as inactive/deleted/revoked, etc. Then it would be fairly easy to have a show all, show previous developers, etc. I'm not sure if some type of log is maintained of the changes. That would also be great as we could go back and see that a particular person started working on a theme, then did a module, block, and then was granted access to core. Peace - Anthony

Show
Anthony Borrow added a comment - Tim - As I understand it, the CVS module is meant to show the current list of folks with write access. I'm not sure it is meant to be a historical record. Although, I do like the idea of having it function that way whereby the record is not actually deleted but simply marked as inactive/deleted/revoked, etc. Then it would be fairly easy to have a show all, show previous developers, etc. I'm not sure if some type of log is maintained of the changes. That would also be great as we could go back and see that a particular person started working on a theme, then did a module, block, and then was granted access to core. Peace - Anthony
Hide
Permalink
Martin Dougiamas added a comment -

Yes, a new status of "inactive" would be a good idea, with a new way to list those people separately.

Mat can work on this after 1.9.

Note we're not putting the cvsadmin module itself in contrib for the time being ....

Show
Martin Dougiamas added a comment - Yes, a new status of "inactive" would be a good idea, with a new way to list those people separately. Mat can work on this after 1.9. Note we're not putting the cvsadmin module itself in contrib for the time being ....
Hide
Permalink
Mathieu Petit-Clair added a comment -

We just had a quick discussion about this .. so here's the current plan :

  • add a checkbox 'inactive' that will remove the user from the avail file (this way, no information is actually lost, if the developper comes back)
  • add a tab 'Inactive developpers' to the module, showing ... inactive developpers.
Show
Mathieu Petit-Clair added a comment - We just had a quick discussion about this .. so here's the current plan :
  • add a checkbox 'inactive' that will remove the user from the avail file (this way, no information is actually lost, if the developper comes back)
  • add a tab 'Inactive developpers' to the module, showing ... inactive developpers.
Hide
Permalink
Anthony Borrow added a comment -

I'm going to resolve this as fixed. I can remove the permissions by updating the directories and then if needed mark the entry in the database as being rejected which would keep them from showing up. It's not a big deal so I am not concerned about this. If a specific need arises then we can deal with it then. Peace - Anthony

Show
Anthony Borrow added a comment - I'm going to resolve this as fixed. I can remove the permissions by updating the directories and then if needed mark the entry in the database as being rejected which would keep them from showing up. It's not a big deal so I am not concerned about this. If a specific need arises then we can deal with it then. Peace - Anthony

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.