Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Component/s: moodle.org
    • Labels:
      None

      Description

      With core's move away from CVS to git, the script to take care of granting access to CONTRIB projects still in CVS is no longer working. Martin indicates that the goal is to remove the cvsadmin module. One piece of that others may have been using is the access to the dev chat history. As we adjust to git, I just want to make sure we don't unintentionally lose any functionality that cvsadmin was providing. For me it was the ability to manage who had access to particular pieces of contrib. Currently, I have no way of making any modifications so it would be good if we could discuss what the best process for that will be. Peace - Anthony

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            Anthony Borrow added a comment -

            p.s. - I've tagged this as a minor security issue just because it relates to cvs access. I'm not sure if there are any concerns about who should be able to view this issue or particular comments.

            Show
            Anthony Borrow added a comment - p.s. - I've tagged this as a minor security issue just because it relates to cvs access. I'm not sure if there are any concerns about who should be able to view this issue or particular comments.
            Hide
            Helen Foster added a comment -

            Anthony, thanks for creating this issue. I'm not sure who to assign it to so I've added a few VIP watchers and am assigning it to moodle.com initially.

            Show
            Helen Foster added a comment - Anthony, thanks for creating this issue. I'm not sure who to assign it to so I've added a few VIP watchers and am assigning it to moodle.com initially.
            Hide
            Jordan Tomkinson added a comment -

            This is on my to-do list (together with Sam H)

            Show
            Jordan Tomkinson added a comment - This is on my to-do list (together with Sam H)
            Hide
            Anthony Borrow added a comment -

            Thanks Jordan. I would really have no problem seeing it removed or perhaps for now just disabled. Other than the chat history there is no need for it at the moment. Although we do need to remove the Developers link in the Development menu. The only thing holding me back at the moment is being able to manage CVS access for the contrib stuff even if it is just to ssh in and directly modify the avail file. I promise not to grant any moodle access as I understand that could really mess things up with git/cvs integration. Peace - Anthony

            Show
            Anthony Borrow added a comment - Thanks Jordan. I would really have no problem seeing it removed or perhaps for now just disabled. Other than the chat history there is no need for it at the moment. Although we do need to remove the Developers link in the Development menu. The only thing holding me back at the moment is being able to manage CVS access for the contrib stuff even if it is just to ssh in and directly modify the avail file. I promise not to grant any moodle access as I understand that could really mess things up with git/cvs integration. Peace - Anthony
            Hide
            Anthony Borrow added a comment -

            Since we are going to continue using cvsadmin for contrib - at least for now - we can defer the removal of cvsadmin until the new M&P module is implemented. Peace - Anthony

            Show
            Anthony Borrow added a comment - Since we are going to continue using cvsadmin for contrib - at least for now - we can defer the removal of cvsadmin until the new M&P module is implemented. Peace - Anthony
            Hide
            Anthony Borrow added a comment -

            Considering that MDLSITE-1214 (to sync cvsadmin with the cvs server) is not going to happen I think we may want to consider removing or at least hiding the cvsadmin module as it may create confusion. It is OK if folks continue to add entries as it gives me an opportunity to send them a message explaining new practices but ideally I would like to see us close the door so that it does not create confusion. Peace - Anthony

            Show
            Anthony Borrow added a comment - Considering that MDLSITE-1214 (to sync cvsadmin with the cvs server) is not going to happen I think we may want to consider removing or at least hiding the cvsadmin module as it may create confusion. It is OK if folks continue to add entries as it gives me an opportunity to send them a message explaining new practices but ideally I would like to see us close the door so that it does not create confusion. Peace - Anthony
            Hide
            Jordan Tomkinson added a comment - - edited

            Adding some HQ watchers as this was discussed in minimeet today

            Show
            Jordan Tomkinson added a comment - - edited Adding some HQ watchers as this was discussed in minimeet today
            Hide
            Dan Poltawski added a comment -

            After completing the chat module deployment, I disabled the cvsadmin module access. As far as I know, there is no way to access it at the moment.

            The only question is whether the cvs scripts are relying on the database (even if no changes are being made there), which will go of course by the time we fully seal up cvs.

            Show
            Dan Poltawski added a comment - After completing the chat module deployment, I disabled the cvsadmin module access. As far as I know, there is no way to access it at the moment. The only question is whether the cvs scripts are relying on the database (even if no changes are being made there), which will go of course by the time we fully seal up cvs.
            Hide
            Dan Poltawski added a comment -

            Its gone.

            Show
            Dan Poltawski added a comment - Its gone.

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development