{"action":"created","issue":{"url":"https://api.github.com/repos/voxpupuli/puppet-jenkins/issues/857","repository_url":"https://api.github.com/repos/voxpupuli/puppet-jenkins","labels_url":"https://api.github.com/repos/voxpupuli/puppet-jenkins/issues/857/labels{/name}","comments_url":"https://api.github.com/repos/voxpupuli/puppet-jenkins/issues/857/comments","events_url":"https://api.github.com/repos/voxpupuli/puppet-jenkins/issues/857/events","html_url":"https://github.com/voxpupuli/puppet-jenkins/issues/857","id":298349848,"number":857,"title":"semi-regular triage/use case discussions?","user":{"login":"jhoblitt","id":948901,"avatar_url":"https://avatars3.githubusercontent.com/u/948901?v=4","gravatar_id":"","url":"https://api.github.com/users/jhoblitt","html_url":"https://github.com/jhoblitt","followers_url":"https://api.github.com/users/jhoblitt/followers","following_url":"https://api.github.com/users/jhoblitt/following{/other_user}","gists_url":"https://api.github.com/users/jhoblitt/gists{/gist_id}","starred_url":"https://api.github.com/users/jhoblitt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhoblitt/subscriptions","organizations_url":"https://api.github.com/users/jhoblitt/orgs","repos_url":"https://api.github.com/users/jhoblitt/repos","events_url":"https://api.github.com/users/jhoblitt/events{/privacy}","received_events_url":"https://api.github.com/users/jhoblitt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-02-19T17:16:58Z","updated_at":"2018-02-20T19:57:15Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Would folks be interested in holding semi-regular triage/use case discussions?  The primary agenda would be to beat down the issue/PR backlog and discussion of the primary use cases going forward and how this module should evolve."},"comment":{"url":"https://api.github.com/repos/voxpupuli/puppet-jenkins/issues/comments/367099960","html_url":"https://github.com/voxpupuli/puppet-jenkins/issues/857#issuecomment-367099960","issue_url":"https://api.github.com/repos/voxpupuli/puppet-jenkins/issues/857","id":367099960,"user":{"login":"esalberg","id":9370354,"avatar_url":"https://avatars2.githubusercontent.com/u/9370354?v=4","gravatar_id":"","url":"https://api.github.com/users/esalberg","html_url":"https://github.com/esalberg","followers_url":"https://api.github.com/users/esalberg/followers","following_url":"https://api.github.com/users/esalberg/following{/other_user}","gists_url":"https://api.github.com/users/esalberg/gists{/gist_id}","starred_url":"https://api.github.com/users/esalberg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/esalberg/subscriptions","organizations_url":"https://api.github.com/users/esalberg/orgs","repos_url":"https://api.github.com/users/esalberg/repos","events_url":"https://api.github.com/users/esalberg/events{/privacy}","received_events_url":"https://api.github.com/users/esalberg/received_events","type":"User","site_admin":false},"created_at":"2018-02-20T19:57:15Z","updated_at":"2018-02-20T19:57:15Z","author_association":"NONE","body":"I ran through the open PRs for triage.  I'd really like to get the automatic Travis checks in place again, though, before pushing any of these through.\r\n\r\n(Review PR standards - e.g. squash to one commit, doc update, either specify or validate type for variables, spec tests, etc. - also see issues #393, #394, #397, #718  )\r\n\r\nTop design issues:\r\n1) Stop accepting new non-native type changes (e.g. PAM auth, LDAP auth, user changes) - require those to be implemented as the native types and providers only?\r\n\r\n2) Management of init.groovy.d scripts - how do we want to do that?  Should be flexible to allow users to add their own scripts via template / hiera / etc.  What about running groovy scripts not at initialization time?  Should init.groovy.d script changes call a (safe) restart of Jenkins?\r\n - also issue #230 to abstract groovy helper scripts, issue #368, #534  for safe restart\r\n\r\n3) Plugin management\r\nIssues: #10 #12 #192 #309 #521 #677 #731 #839 #841 \r\n\r\n4) CLI / remoting / bootstrap access issues, e.g. issue #684 (unclear if this is mainly the Debian issue), issues #749 #808 #814 #854 (discussion of reverting remoting cli changes)\r\n work with elconas to get those changes reviewed / implemented\r\n\r\n4) Other: Issues related to the native types/providers probably should be prioritized if they're not going to be considered experimental (e.g. #730).  \r\n - Also need better documentation / examples of the native types / providers (especially bootstrap / security related), config_hash, etc.\r\n\r\n----------------------\r\n\r\nThe following look like they are pretty easy changes after review / rebase / squash to one commit / add tests. However, not sure what the etiquette is related to taking other people's PRs and resubmitting them.\r\n#432 #436 #439 #555 #593 #725 #811 \r\n\r\nThese are more complex but look close to being complete:\r\nconfig.xml (#508) and plugin templates (#592)\r\n - see also issue #381 \r\n\r\n------------------------\r\nNative type/provider enhancements:\r\nLDAP auth (#339 #606, issue #332 ) - implement with native types/providers; need to be able to encrypt password if applicable\r\nPAM auth (#809) - implement with native types/providers\r\nNew jenkins_exec (script/groovy) type #791 \r\n\r\nUser management issues (idempotency #504), (password update #524), (bootstrapping secure users #761 #824)\r\n - requires init.groovy.d discussion; implement with native types/providers; discuss if #524 is a bug fix\r\n\r\njava args / sysconfig fixes: #723 \r\n- issue #217 #448 may also be related; issue #634 \r\n\r\nOS issues - each needs someone using the specific OS to take it on:\r\nOpenBSD support (PR #304 #658 #743); also issue #105 for FreeBSD\r\nWindows support (PR #466 #816)\r\nMacOS script (PR #780)\r\nDebian - Related to issue #462?\r\n\r\n----------------\r\n\r\nPossibly should be closed:\r\n#456 (fact no longer exists?); #472 (comments state that the functionality already existed?)\r\n - there are a number of issues that look like they are ready to be closed, although some should be documented first\r\n\r\nCurrently active PRs (updated within the last 2 weeks):\r\n#844 (spec tests; waiting rebase)\r\n#484 \r\n\r\n\r\n"}}
{"actor":{"display_login":"esalberg"}}