{"action":"opened","issue":{"url":"https://api.github.com/repos/baritonehands/jenkinsnuget/issues/2","repository_url":"https://api.github.com/repos/baritonehands/jenkinsnuget","labels_url":"https://api.github.com/repos/baritonehands/jenkinsnuget/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/baritonehands/jenkinsnuget/issues/2/comments","events_url":"https://api.github.com/repos/baritonehands/jenkinsnuget/issues/2/events","html_url":"https://github.com/baritonehands/jenkinsnuget/issues/2","id":146245049,"number":2,"title":"Need for clarification on the status of this plugin ","user":{"login":"Greybird","id":8553578,"avatar_url":"https://avatars.githubusercontent.com/u/8553578?v=3","gravatar_id":"","url":"https://api.github.com/users/Greybird","html_url":"https://github.com/Greybird","followers_url":"https://api.github.com/users/Greybird/followers","following_url":"https://api.github.com/users/Greybird/following{/other_user}","gists_url":"https://api.github.com/users/Greybird/gists{/gist_id}","starred_url":"https://api.github.com/users/Greybird/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Greybird/subscriptions","organizations_url":"https://api.github.com/users/Greybird/orgs","repos_url":"https://api.github.com/users/Greybird/repos","events_url":"https://api.github.com/users/Greybird/events{/privacy}","received_events_url":"https://api.github.com/users/Greybird/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-06T09:11:55Z","updated_at":"2016-04-06T09:11:55Z","closed_at":null,"body":"Hi,\r\n\r\nI’m currently working on a plugin to allow publishing packages to nuget servers.\r\nFrom googling the need, it appeared that the recommended way is to store api key in environement variables, but this does not fit with security needs of my organization as these variables can then be extracted very easily.\r\nThe idea is mainly to allow configuration of api keys in the global configuration, and to provide a post build task pushing to nuget using one of the api keys configured at system level.\r\n\r\nI then discovered your nuget plugin, which is providing a trigger based on nuget.\r\nI then found that repos on jenkinsci and your repo are not in sync,\r\nJenkins plugin page references jenkinsci repo, but the releases history seems to ft more with yours.\r\nI also see an open pull request on the jenkinsci fork.\r\n\r\nCould you please tell me if:\r\n* you still maintain this plugin?\r\n* there is an issue with the wiki page/the jenkinsci repo?\r\n* you are open to a contribution regarding publication to nuget servers or if I should go with a separate plugin?\r\n\r\nThanks!\r\n\r\nArnaud\r\n"}}