{"action":"created","issue":{"url":"https://api.github.com/repos/OpenConsent/openconsentgroup/issues/14","labels_url":"https://api.github.com/repos/OpenConsent/openconsentgroup/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/OpenConsent/openconsentgroup/issues/14/comments","events_url":"https://api.github.com/repos/OpenConsent/openconsentgroup/issues/14/events","html_url":"https://github.com/OpenConsent/openconsentgroup/issues/14","id":120874196,"number":14,"title":"Scheduling Mid-Project Review","user":{"login":"dazzaji","id":2357755,"avatar_url":"https://avatars.githubusercontent.com/u/2357755?v=3","gravatar_id":"","url":"https://api.github.com/users/dazzaji","html_url":"https://github.com/dazzaji","followers_url":"https://api.github.com/users/dazzaji/followers","following_url":"https://api.github.com/users/dazzaji/following{/other_user}","gists_url":"https://api.github.com/users/dazzaji/gists{/gist_id}","starred_url":"https://api.github.com/users/dazzaji/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dazzaji/subscriptions","organizations_url":"https://api.github.com/users/dazzaji/orgs","repos_url":"https://api.github.com/users/dazzaji/repos","events_url":"https://api.github.com/users/dazzaji/events{/privacy}","received_events_url":"https://api.github.com/users/dazzaji/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-07T21:41:00Z","updated_at":"2015-12-08T06:03:06Z","closed_at":null,"body":"## Please Use Comments to Suggest and Agree Mid-Project Review Day and Time\r\n\r\nAll - it appears we are ready to at least schedule the mid-project review.  Please use the comments to this issue to communicate potential day-time blocks for this review session and to close the issue when a day-time is set. \r\n\r\n## Status: Things are on track\r\n\r\nThe current artifacts are located here: https://github.com/MassachusettsLegalHackers/orgsetup and the documentation is hosted on Wiki pages here: https://github.com/MassachusettsLegalHackers/orgsetup/wiki and it is pointed to from \"openconsent.net\" here: http://openconsent.net \r\n\r\nThe requirement for the mid-project review is that each item exist at a URL and each item does.  Better yet, the most difficult aspect has been done, which is independent install, configuration, deployment and testing of the API.  This step has been documented such that any person with no prior knowledge of this project should be able to achieve the same results.  \r\n\r\nAlso, this project is being developed in a way that will ensure all resources exist within a single, version controlled environment and no resources that are needed as an essential part of the project exist \"out of band\" at external sites that may be changed or deleted at any time.  This common project management and documentation risk is being handled by keeping all resources available within GitHub repositories that can be forked at any time while ensuring downstream developers that fork the project have all essential resources needed to understand and see working examples and re-deploy the project themselves.  \r\n\r\n## What remains to be completed\r\n\r\nAt a high level what remains is to duplicate the working externalize \"button\" (form) an example of which is currently operating at Kantara.  The plan is to take the same form as exists on the API page and ensure it is possible to deploy and operate it from an external third party site and to document the steps needed for that.  There are open issue items seeking assistance getting all relevant code by which the example externalized form and submit button have been implemented at the Kantara site.  This will assist in working with the code and making the best possible deliverable for this item. \r\n\r\n## Why is this work happening outside OpenConsent GitHub org?\r\n\r\nThis is a forked repo from the OpenConsent GitHub organization, which was a necessary step due to lack of rights in OpenConsent organization and the repo OpenConsentGroup or the repo OrgSetUp.  The repo OpenConsentGroup, which was originally intended to be the dev repo, has apparently been used for other purposes and the links have been disrupted based on actions by the project owner.  This is fine, given the repo name \"group\" suggests that repo may be used for purposes of an organization and subject to these types of unplanned and unannounced changes in setup.  However, to ensure a stable development environment, this is not compatible or workable in the short time frames alloted for this project.  Therefore, the repo \"OrgSetup\" is being used for dev work and as the example setup that organizations would use to adopt and deploy consent receipt API and/or the \"button\".  And due to lack of rights in the OpenConsent org or the OrgSetup repo in the OpenConsent org, that repo has been forked and the development work for this project is being done at the forked version which, again, is here: https://github.com/MassachusettsLegalHackers/orgsetup\r\n\r\n## Immediate Next Steps:\r\n\r\n(1) Communicate potential day-time slots for Mid-Project review in comments below\r\n\r\n(2) Project owner should provide sufficient rights to the contractor(s) and project guarantor for read-wright-admin to at least the OrgSetup repo in the OpenConsentGroup GitHub organization.  If this is done, then this project will go smoother and better. \r\n\r\n(3) Review all remaining open issues and close those that no longer need to be open, make progress on those that remain open, and be prepared to discuss and close all open items or have a good quick plan to close all open items before the Mid-Project review meeting starts.\r\n\r\nI apologize if I have misrepresented or incorrectly stated any fact or factor in the above.  If I have, please include any corrections or improvements in the comments to this GitHub Issue.  \r\n"},"comment":{"url":"https://api.github.com/repos/OpenConsent/openconsentgroup/issues/comments/162778950","html_url":"https://github.com/OpenConsent/openconsentgroup/issues/14#issuecomment-162778950","issue_url":"https://api.github.com/repos/OpenConsent/openconsentgroup/issues/14","id":162778950,"user":{"login":"prhana","id":8837791,"avatar_url":"https://avatars.githubusercontent.com/u/8837791?v=3","gravatar_id":"","url":"https://api.github.com/users/prhana","html_url":"https://github.com/prhana","followers_url":"https://api.github.com/users/prhana/followers","following_url":"https://api.github.com/users/prhana/following{/other_user}","gists_url":"https://api.github.com/users/prhana/gists{/gist_id}","starred_url":"https://api.github.com/users/prhana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prhana/subscriptions","organizations_url":"https://api.github.com/users/prhana/orgs","repos_url":"https://api.github.com/users/prhana/repos","events_url":"https://api.github.com/users/prhana/events{/privacy}","received_events_url":"https://api.github.com/users/prhana/received_events","type":"User","site_admin":false},"created_at":"2015-12-08T06:03:06Z","updated_at":"2015-12-08T06:03:06Z","body":"Can we schedule for Wednesday or Thursday between 9am-1:30pm? Tomorrow during the day will not work since Didar and I have opposite schedules. We are also available tomorrow night after 10pm. "}}