Issue Details (XML | Word | Printable)

Key: MDLSITE-350
Type: New Feature New Feature
Status: Open Open
Priority: Minor Minor
Assignee: Mathieu Petit-Clair
Reporter: Anthony Borrow
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Moodle.org Sites

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

Created: 13/Feb/08 12:31 AM   Updated: 02/Apr/08 05:03 PM
Return to search
Component/s: CVS repository

Participants: Anthony Borrow, Martin Dougiamas, Mathieu Petit-Clair and Tim Hunt
Security Level: None


 Description  « Hide
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.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Tim Hunt added a comment - 13/Feb/08 01:28 AM
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.)


Anthony Borrow added a comment - 13/Feb/08 01:48 AM
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

Martin Dougiamas added a comment - 13/Feb/08 10:18 AM
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 ....


Mathieu Petit-Clair added a comment - 01/Apr/08 11:00 AM
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.