{"action":"created","issue":{"url":"https://api.github.com/repos/canada-ca/devex/issues/79","repository_url":"https://api.github.com/repos/canada-ca/devex","labels_url":"https://api.github.com/repos/canada-ca/devex/issues/79/labels{/name}","comments_url":"https://api.github.com/repos/canada-ca/devex/issues/79/comments","events_url":"https://api.github.com/repos/canada-ca/devex/issues/79/events","html_url":"https://github.com/canada-ca/devex/issues/79","id":320306889,"number":79,"title":"Failed procurement—Now what? // Échec de l’approvisionnement — Que faire maintenant?","user":{"login":"RachelMuston","id":29108013,"avatar_url":"https://avatars0.githubusercontent.com/u/29108013?v=4","gravatar_id":"","url":"https://api.github.com/users/RachelMuston","html_url":"https://github.com/RachelMuston","followers_url":"https://api.github.com/users/RachelMuston/followers","following_url":"https://api.github.com/users/RachelMuston/following{/other_user}","gists_url":"https://api.github.com/users/RachelMuston/gists{/gist_id}","starred_url":"https://api.github.com/users/RachelMuston/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RachelMuston/subscriptions","organizations_url":"https://api.github.com/users/RachelMuston/orgs","repos_url":"https://api.github.com/users/RachelMuston/repos","events_url":"https://api.github.com/users/RachelMuston/events{/privacy}","received_events_url":"https://api.github.com/users/RachelMuston/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-05-04T14:56:03Z","updated_at":"2018-05-05T05:10:24Z","closed_at":null,"author_association":"NONE","body":"The term “failed procurement” describes a procurement process that runs its course, but without a result.   This is what happened with the second opportunity posted on the Government of Canada Developers Exchange (GC DevEx). The opportunity closed on April 23, 2018 and did not receive any proposals. Nor did it generate any discussion or comments on the [Git Hub issue](https://github.com/canada-ca/HC-Technology-and-Business-Innovation_Innovations-Technologiques-et-d-Affaires-SC/issues/1).\r\n \r\nThis raises two questions…. Why?  And now what?\r\n \r\nWas there a problem with the way the opportunity was described or scoped? If so, should Health Canada re-write their opportunity?  Was the problem with the skill set required? If so, should we be using promotions to broaden the depth and breadth of the pool of developers who are signed-up to hear about GC DevEx opportunities?\r\n \r\nOr is the problem with the GC DevEx platform itself?  Do we need to fix any technical issues or processes to make it easier for developers to apply to opportunities?\r\n \r\nPlease share any thoughts you have in the comments section below!\r\n\r\n—\r\n\r\nLe terme « échec de l’approvisionnement » décrit un processus d’approvisionnement mené jusqu’au bout, mais sans résultat. C’est ce qui est arrivé dans le cas de la deuxième possibilité affichée sur le Carrefour des développeurs du gouvernement du Canada (CarrefourProgGC). La possibilité a pris fin le 23 avril 2018 et n’a reçu aucune proposition. Et elle n’a pas non plus généré de discussion ou de commentaire sur la [question Git Hub](https://github.com/canada-ca/HC-Technology-and-Business-Innovation_Innovations-Technologiques-et-d-Affaires-SC/issues/1).\r\n \r\nCela soulève deux questions… Pourquoi? Et que faire maintenant? \r\n \r\nY avait-il un problème dans la manière dont la possibilité était décrite ou dans sa portée? Dans l’affirmative, Santé Canada devrait-elle réécrire la possibilité?  Le problème était-il au niveau de l’ensemble de compétences requis? Le cas échéant, devrions-nous utiliser des promotions pour accroître l’ampleur et la richesse du bassin de développeurs qui se sont abonnés pour être informés des possibilités dans le cadre du CarrefourProgGC?\r\n \r\nOu le problème vient-il de la plateforme du CarrefourProgGC elle-même? Devons-nous corriger des problèmes techniques ou des processus pour faire en sorte qu’il soit plus facile pour les développeurs de présenter leur candidature pour des possibilités?\r\n \r\nVeuillez nous faire part de toute réflexion dans la section réservée aux commentaires que vous trouverez ci-dessous!\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/canada-ca/devex/issues/comments/386780028","html_url":"https://github.com/canada-ca/devex/issues/79#issuecomment-386780028","issue_url":"https://api.github.com/repos/canada-ca/devex/issues/79","id":386780028,"user":{"login":"karfai","id":13842,"avatar_url":"https://avatars3.githubusercontent.com/u/13842?v=4","gravatar_id":"","url":"https://api.github.com/users/karfai","html_url":"https://github.com/karfai","followers_url":"https://api.github.com/users/karfai/followers","following_url":"https://api.github.com/users/karfai/following{/other_user}","gists_url":"https://api.github.com/users/karfai/gists{/gist_id}","starred_url":"https://api.github.com/users/karfai/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/karfai/subscriptions","organizations_url":"https://api.github.com/users/karfai/orgs","repos_url":"https://api.github.com/users/karfai/repos","events_url":"https://api.github.com/users/karfai/events{/privacy}","received_events_url":"https://api.github.com/users/karfai/received_events","type":"User","site_admin":false},"created_at":"2018-05-05T05:10:24Z","updated_at":"2018-05-05T05:10:24Z","author_association":"NONE","body":"I left some comments on the original issue (https://github.com/canada-ca/HC-Technology-and-Business-Innovation_Innovations-Technologiques-et-d-Affaires-SC/issues/1) that summarizes what I see are the problems with the offer. All of the comments here are valid, but they don't explore what would **actually go in to** implementing an application like this one. These comments all assume that the constraints are valid. I don't think they are."}}
{"actor":{"display_login":"karfai"}}