{"push_id":585004588,"size":2,"distinct_size":2,"ref":"refs/heads/curationDashboard","head":"82ba18608ec243c15ab21c71b5118b3f21cf3a00","before":"f0dd4b17b98998f2f939aecb48ac0131e8cbb48f","commits":[{"sha":"f4a8819e8c69dc77e799ba16813200c51346a7ab","author":{"email":"d0517261e2882c61c16e8636e1d50e350cb7607a@kitware.com","name":"mgrauer"},"message":"Add callback: delete curationfolder on folder delete","distinct":true,"url":"https://api.github.com/repos/midasplatform/curate/commits/f4a8819e8c69dc77e799ba16813200c51346a7ab"},{"sha":"82ba18608ec243c15ab21c71b5118b3f21cf3a00","author":{"email":"d0517261e2882c61c16e8636e1d50e350cb7607a@kitware.com","name":"mgrauer"},"message":"WIP: dashboard operational\n\nAdmin can create a curatedfolder assigned to a community and a user.\nAdmin can approve a curatedfolder approval request from the dashboard.\nUploader user can requests curation approval from the dashboard.\nUploader user gets folderpolicyuser WRITE access to a curated folder once\nthe folder starts being tracked. Once the folder is requested to be\napproved, the all users with folderpolicyuser WRITE get changed to\nREAD.  Upon approval by the Admin, all folderpolicyuser are removed from\nthe folder, and a community members group READ is added.\nNo longer listing curated folders based on group perms, only by\nfolderpolicy user perms.\nNeeds some thinking through about policies and cleanup.","distinct":true,"url":"https://api.github.com/repos/midasplatform/curate/commits/82ba18608ec243c15ab21c71b5118b3f21cf3a00"}]}