{"action":"created","comment":{"url":"https://api.github.com/repos/theforeman/theforeman.org/pulls/comments/55671419","id":55671419,"diff_hunk":"@@ -0,0 +1,342 @@\n+---\n+layout: post\n+title: 2016 Foreman Survey Analysis\n+date: 2016-03-07 14:34:44\n+author: Greg Sutcliffe\n+tags:\n+- usage\n+- foreman\n+- events\n+- plugins\n+- community\n+- survey\n+- API\n+- virtualization\n+- cfgmgmtcamp\n+- puppet\n+- devconf\n+- fosdem\n+- chef\n+- use cases\n+---\n+\n+Over the course of Febrary, we again ran the Foreman Community Survey to get\n+feedback on how we're doing and what needs to be addressed. I've now had some\n+time to sit down and look through the data, and share some insights with you\n+all.\n+\n+Firstly - **thank you** to all those who filled out the survey. It was a little\n+bit longer this year, as we looked to get data on how we can grow the\n+contributor community as well as the user community, so thanks for taking the\n+time. It's great to hear all your feedback.\n+\n+<!--more-->\n+\n+## <a name=\"intro\"></a>Contents\n+\n+* [Intro](/2016/03/2016-forman-survey-analysis.html/#intro)\n+* [Community Diversity](/2016/03/2016-forman-survey-analysis.html/#diversity)\n+* [Support and Docs](/2016/03/2016-forman-survey-analysis.html/#support)\n+* [Specific Features](/2016/03/2016-forman-survey-analysis.html/#foreman-features)\n+* [Upcoming Work](/2016/03/2016-forman-survey-analysis.html/#upcoming-work)\n+* [Events](/2016/03/2016-forman-survey-analysis.html/#events)\n+* [Contributor Survey](/2016/03/2016-forman-survey-analysis.html/#contributor-survey)\n+* [Final thoughts](/2016/03/2016-forman-survey-analysis.html/#final-thoughts)\n+\n+Sadly, response were slightly down from last year (**76 responses**) and the\n+smaller sample size makes it difficult to draw strong conculsions. According to\n+other metrics, we have usually 250ish active people in IRC each month, and some\n+2000 people on the mailing list. Suggestions on how to reach more people with\n+the survey are, of course, [welcome][contact]!\n+\n+That said, we can still look at the results and look for trends, especially as\n+compared to last year (which we couldn't do then, it being the first such\n+survey). Lets start with some stats on...\n+\n+## <a name=\"diversity\"></a>Community Diversity\n+\n+![How long using](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/how-long-using.png)\n+\n+This is broadly similar to last year, with some 40% of the community having\n+used Foreman for under a year. We do see a shift in the 3+ years category, with\n+a corresponding drop in 1 and 2 year categories, but it's nice to see that the 3\n+months category remains stable at 13% - we seem to be continuing to attract new\n+people to the community, which is great. Having more \"old hands\" around to\n+answer questions is starting to be noticable on IRC and the mailing lists, too.\n+\n+![What version used](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/what-version-using.png)\n+\n+I was quite surprised by this - Foreman 1.10 was released at Christmas, meaning\n+it had only been out for 4 weeks by the time of the survey. It's great to see\n+people so quick to upgrade something which can be so deeply embedded in the\n+infrastructure. When you add in 1.9 (we still support the last two versions, so\n+this is the total supported userbase) we get 71% which is a bit of a drop on\n+last year (86%). A quarter of responses are running an unsupported version of\n+Foreman - as we said last year, if there's anything holding you back from\n+upgrading, do [get in touch][contact]!\n+\n+![Nodes managed](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/nodes-managed.png)\n+\n+Again similar to last year, we see under 10% of responses coming from large\n+installations (>1k nodes). It is good to see a spread here though, as it shows\n+we're meeting the needs of a wide variety of infrastructure usecases and\n+network topologies.\n+\n+![Number of Users](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/number-users.png)\n+\n+Interestingly, larger numbers of users (>10) shows growth this year, up to\n+nearly 25%. Hopefully this is due to continuing effort in our Roles,\n+Authorization, and Locations/Organisations features. That said, a solid 50%\n+remain in the 1-5 section, so keeping the option to disable or streamline these\n+features is also important. This is relevant due to the discussion around\n+Locations/Orgainisations at the moment.\n+\n+Finally for diversity, lets have a couple of bar charts:\n+\n+![Operatingsystems](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/operatingsystems.png)\n+\n+This year we allowed respondents to select more than one option, as \"most\" is\n+subjective, especially when you put proxies and Foreman itself in the same\n+question.\n+\n+Keeping this in mind, we see that Red Hat family distros remain constant at\n+75%, but there's a marked increase in deb-based distros (up 5%) and in \"Other\"\n+which is up 10%. It would be very interesting [to hear from those users][contact]\n+about what OSs they are using!\n+\n+![Hammer vs API](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/hammer-vs-api.png)\n+\n+Hammer remains stable this year at just under 50%, and it's good to see APIv1\n+declining. The real surprise here, however, is the \"No\" response jumping from\n+just 6% to 32%. I have no data to suggest why this might be, but one conclusion\n+is that the tooling we're providing to the newer users joining the community is\n+now sufficient for their needs. If you've got a story about this,\n+[let us know][contact]!\n+\n+Overall, the community seems diverse in many respects, with different sizes,\n+ages, OSs and usecases. This is good news as we move forward, since it shows we\n+have broad appeal to people just discovering Foreman today.\n+\n+## <a name=\"support\"></a>Support and Docs\n+\n+Moving on then, we have a number of question related to how well we meet\n+support needs of the community:\n+\n+![IRC and Lists](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/irc-and-lists.png)\n+\n+It's not very visible (thanks Google), but the vertical axis is, in order:\n+\n+* I know of the IRC channel, but don't use it\n+* I use the IRC channel\n+* I know of the mailing list, but don't use it\n+* I use the mailing list\n+* I wasn't aware of either\n+\n+The really important number for me here is the last one - 7% not aware of our\n+primary support systems. That's both good (it's *only* 7%) and bad (how do we\n+reach those people). For the others, so long as they know that the IRC channel\n+and mailing lists exist, that's good - they can get help when they need it.\n+\n+To those who said they spend active time on the lists and on IRC - *thank you!*\n+User-to-user support is one of the things that makes community leads go all\n+warm and fuzzy and liable to buy rounds ;)\n+\n+![User Support](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/user-support.png)\n+\n+We have a great reputation for our IRC channel, and that's reflected here in\n+the 5-star rating our IRC support gets in the survey results. Happily the other\n+support routes also do well, getting 4s across the board. This is great to see,\n+but there's always more we can do, as seen below in the free-text comments.\n+\n+![Major and Minor releases](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/major-and-minor.png)\n+\n+I was woried about this one - if, say, frequency had come out as bad, we'd have\n+no data on whether it was too fast or too slow, etc.\n+\n+Thankfully, we seem to do pretty well across the board, with the majority being\n+3+ in every category, which is all the more important since it's largely the\n+same as last year, showing that we have consistency in our releases as well as\n+providing what our users want. Whilst a lot of people work on each release, I\n+think it's worth calling out Dominic for all he does around release engineering\n+- thanks!\n+\n+The final support question was a free text field, and I don't plan to\n+cut'n'paste the entire result set, but we did get some themes. Out of the 17\n+responses to this question:\n+\n+* 11 were generally positive about the support/docs (65%)\n+* 7 requested more diagrams or how-to guides (potentially including screencasts) (41%)\n+* 3 specifically requested improvements to plugin docs (18%)\n+\n+It's good to see two-thirds of the responses are positive, as a lot of effort\n+goes into the manual and support channels. I still plan to produce my\n+\"beginners guide\" screencast series \"soon(tm)\". Plugins, as ever, remain the\n+responsibility of the authors, but the development community tries to help out\n+where we can. Writing docs is also a great way to get [started with\n+contributing][contribute], if you're so inclined!\n+\n+## <a name=\"foreman-features\"></a>Specific Foreman Features\n+\n+Now we move onto the detail in some of Foreman's features:\n+\n+![Compute Resources](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/compute-resources.png)\n+\n+This graph is fascinating for quite a few reasons. Firstly, in a change from\n+last year, we explicitly included \"Physical hardware\" as an option - although\n+the question is about Compute Resources, in reality it should have been \"What\n+do you provision on with Foreman?\". By including this separately from \"None\",\n+we get that nearly two-thirds of the community stil manage physical hardware\n+with Foreman. PXE is not dead yet, it seems!\n+\n+The other interesting figures are in the shifts from last year. EC2 and\n+OpeStack both lose a few percentage points, while VMware and Docker (no\n+surprise there) gain a few. The really big increases, though, are in Libvirt\n+and oVirt, which given the Docker hype this year is really surprising to me.\n+Other is also up substantially, perhaps in a nod to our plugin structure for\n+Compute Resources.\n+\n+Overall, this graph nicely highlights the diversity of infrastructure that\n+we're able to support, and cautions us about getting to narrow-minded with\n+respect to a particular platform. We do well because of our neutrality.\n+\n+![Taxonomies](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/taxonomies.png)\n+\n+One of our more advanced features, Locations / Organisations are a scoping\n+mechanism, useful if you have resources that should only matter to certains\n+places or people (e.g. multi-tenant setups). Whats interesting here is that\n+while the number of users not using Locs/Orgs is constant, many of those who\n+used just one last year now use both (24% -> 33%).\n+\n+We actually asked three questions on this feature, as the developer community\n+wanted to gather usecases for a potential refactoring of the feature, and\n+wanted to be sure we didn't break it for anyone. We'll be able to say more on\n+this once the refactoring is decided on (or not)\n+\n+This next graph is huge. Sorry ;)\n+\n+![Plugin Usage](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/plugin-usage.png)\n+\n+Most of the big usage numbers here are entirely expected. Discovery tops the\n+chart again, but it's good to see Katello move in to second place; closely\n+following are foreman\\_hooks, puppetdb\\_foreman, foreman\\_templates and\n+foreman\\_bootdisk. I'll admit I was surprised to see foreman\\_dhcp\\_browser up at\n+30% - perhaps this indicates a need for more Smart Proxy visibility from within\n+the UI? Happily, such things are in progress!\n+\n+The fast movers are foreman\\_ansible, and foreman\\_openscap, both developed this\n+year - in particular the Ansible plugin is only a few months old, so it's 13%\n+uptake is rapid indeed.\n+\n+As with last year, this shows some of the activity in our plugin ecosystem,\n+which is great to see. We really want to see plugins succeed, and provide a lot\n+of materials to help get started writing them, so graph like these are a reward\n+for that effort.\n+\n+## <a name=\"upcoming-work\"></a>Upcoming work\n+\n+For this, we changed the style this year. Rather than ask for interest ratings\n+on individual features from 1-5 (which can be a problem since not every feature\n+is of interest to all users), we decided to simply ask for your top 3 wishes,\n+in no specific order. This list was drawn from the items still not done from\n+last year, from some things that come up over and over in conversations, and so\n+on.\n+\n+![Future Features](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/future-features.png)\n+\n+Overwhelmingly, Puppet 4 support tops the bill. We knew this would be high on\n+the list, so we took time to meet with Puppetlabs at CfgMgmt Camp, and come up\n+with a plan of action (you can read it [here][puppet4]). This work is\n+*tentatively* scheduled for 1.12, but as ever with open source, there's no\n+promises.\n+\n+Following that, we see better container support coming in strong. We've already\n+got a Docker plugin, Docker registry support via Pulp/Katello, and CoreOS &\n+Atomic provisioning support. There's more we can do though, so do file\n+[feature requests][issues] on this area if you have specific features relating\n+to containers you'd like to see.\n+\n+All the others come in roughly equally, with a very slight edge to networking\n+and IPv6. The developer community will be taking this on board in the coming\n+year, and I really hope that next year (as with this year) we can say that\n+we've delivered on a lot of these items.\n+\n+We also had a free-text field for people to put their #1 wish in. Again, Puppet\n+4 comes out strongly here, but also more Ansible integration, VMware, IPv6 and\n+Katello development were common.\n+\n+## <a name=\"events\"></a>Events\n+\n+We split this up this year. Last year we only asked if you would like to attend\n+events - this time we also asked if you'd be willing to help organise them:\n+\n+![Meetups](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/meetups.png)\n+\n+We see that the US and EMEA are popular, but a sizeable chunk of people would\n+like a local meetup. We're investigating getting involved with other local\n+events such as DevOpsDays and so forth - if there's an event near you that you\n+think we should be at, [let us know][contact]!\n+\n+I'm *really* excited that 22 peaople said they'd be willing to speak about\n+Foreman at conferences, and 16 people would be willing to help set up events -\n+*thanks*! However, this is an anonymous survey! Please, please *email me* with\n+me about this - I'm starting to build a collection of potential speakers (and\n+their areas of travel), and potential event locations to see what we can match\n+up.\n+\n+Again, if you responded to this question - *email me*! Thanks!\n+\n+## <a name=\"contributor-survey\"></a>Contributor survey\n+\n+I'll keep this section brief, but here's two interesting graphs:\n+\n+![Contribute](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/do-you-contribute.png)\n+\n+Clearly, the responses to this question will be strongly skewed in the\n+contributor survey. However, I think it's notable that 20% of people felt\n+strongly enough to fill this out even though they are *not* currently a\n+contributor - it implies there's probably more people in this position. We owe\n+it to ourselves to support new contributors and help them get started.\n+\n+I do have some ideas here, such as more screencasts (how about a \"Let's Play\"\n+of writing a plugin?) and also perhaps a \"where can I help\" workflow on the\n+website, similar to the [Mozilla site](https://www.mozilla.org/en-US/contribute).\n+\n+![Dev Support](/static/images/blog_images/2016-03-07-2016-forman-survey-analysis/dev-support.png)\n+\n+Leading on from that, it seems that while we are consistently good at helping\n+out once we get to reporting and monitoring PRs, the picture for helping those\n+who are stuck (either stuck *in* some code, or stuck just getting started) is a\n+bit more mixed. Work is underway to write a [developer handbook][handbook]\n+which is helping to clarify this, and further work remains to be done on it.\n+This should probably re-emphasize the IRC dev channel as the primary means of\n+support when contributing.\n+\n+## <a name=\"final-thoughts\"></a>Final thoughts\n+\n+It's fascinating reading through all the comments and stats - there's more data\n+in here than I can show without this becoming a book, but I'll be using it\n+myself in my role to assist the community further.\n+\n+Hopefully the above gives you a flavour of where we're at. For myself, I feel\n+that we get good marks for our support - essential for such a complex piece of\n+software - and we do a good job of halding releases, new features, etc as well.\n+\n+I'll leave you with a few of my favourite quotes from the question \"Do you have\n+any additional comments or special requests?\":\n+\n+* Thank you for a great solution!!! Keep up the great work!\n+* When I adopted Foreman I mostly wanted a good DHCP/PXE provisioner with a solid, simple classifyer. You've come to meet and exceed my needs","path":"_posts/2016-03-07-2016-forman-survey-analysis.md","position":328,"original_position":328,"commit_id":"06404d8b75a22dbf2e624f8b76e3eb58f3f82673","original_commit_id":"06404d8b75a22dbf2e624f8b76e3eb58f3f82673","user":{"login":"GregSutcliffe","id":827786,"avatar_url":"https://avatars.githubusercontent.com/u/827786?v=3","gravatar_id":"","url":"https://api.github.com/users/GregSutcliffe","html_url":"https://github.com/GregSutcliffe","followers_url":"https://api.github.com/users/GregSutcliffe/followers","following_url":"https://api.github.com/users/GregSutcliffe/following{/other_user}","gists_url":"https://api.github.com/users/GregSutcliffe/gists{/gist_id}","starred_url":"https://api.github.com/users/GregSutcliffe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GregSutcliffe/subscriptions","organizations_url":"https://api.github.com/users/GregSutcliffe/orgs","repos_url":"https://api.github.com/users/GregSutcliffe/repos","events_url":"https://api.github.com/users/GregSutcliffe/events{/privacy}","received_events_url":"https://api.github.com/users/GregSutcliffe/received_events","type":"User","site_admin":false},"body":"Taken directly from a response. Should we fix their typos?","created_at":"2016-03-10T12:24:42Z","updated_at":"2016-03-10T12:24:42Z","html_url":"https://github.com/theforeman/theforeman.org/pull/563#discussion_r55671419","pull_request_url":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563","_links":{"self":{"href":"https://api.github.com/repos/theforeman/theforeman.org/pulls/comments/55671419"},"html":{"href":"https://github.com/theforeman/theforeman.org/pull/563#discussion_r55671419"},"pull_request":{"href":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563"}}},"pull_request":{"url":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563","id":61950938,"html_url":"https://github.com/theforeman/theforeman.org/pull/563","diff_url":"https://github.com/theforeman/theforeman.org/pull/563.diff","patch_url":"https://github.com/theforeman/theforeman.org/pull/563.patch","issue_url":"https://api.github.com/repos/theforeman/theforeman.org/issues/563","number":563,"state":"open","locked":false,"title":"Add 2016 survey analysis blog post","user":{"login":"GregSutcliffe","id":827786,"avatar_url":"https://avatars.githubusercontent.com/u/827786?v=3","gravatar_id":"","url":"https://api.github.com/users/GregSutcliffe","html_url":"https://github.com/GregSutcliffe","followers_url":"https://api.github.com/users/GregSutcliffe/followers","following_url":"https://api.github.com/users/GregSutcliffe/following{/other_user}","gists_url":"https://api.github.com/users/GregSutcliffe/gists{/gist_id}","starred_url":"https://api.github.com/users/GregSutcliffe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GregSutcliffe/subscriptions","organizations_url":"https://api.github.com/users/GregSutcliffe/orgs","repos_url":"https://api.github.com/users/GregSutcliffe/repos","events_url":"https://api.github.com/users/GregSutcliffe/events{/privacy}","received_events_url":"https://api.github.com/users/GregSutcliffe/received_events","type":"User","site_admin":false},"body":"First draft, it's 300 lines so there's probably errors, especially knowing me - have at it. \r\n\r\nText is pretty much complete. Still to do:\r\n\r\n[x] add some URLs in appropriate places\r\n[ ] possibly redraw/edit the bar graphs so the Y-axis labels are readable (thanks Google...)","created_at":"2016-03-07T17:30:14Z","updated_at":"2016-03-10T12:24:42Z","closed_at":null,"merged_at":null,"merge_commit_sha":"f0d0407ff12a20b881dbe2f7bcc106ba3649a5fa","assignee":null,"milestone":null,"commits_url":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563/commits","review_comments_url":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563/comments","review_comment_url":"https://api.github.com/repos/theforeman/theforeman.org/pulls/comments{/number}","comments_url":"https://api.github.com/repos/theforeman/theforeman.org/issues/563/comments","statuses_url":"https://api.github.com/repos/theforeman/theforeman.org/statuses/06404d8b75a22dbf2e624f8b76e3eb58f3f82673","head":{"label":"GregSutcliffe:survey","ref":"survey","sha":"06404d8b75a22dbf2e624f8b76e3eb58f3f82673","user":{"login":"GregSutcliffe","id":827786,"avatar_url":"https://avatars.githubusercontent.com/u/827786?v=3","gravatar_id":"","url":"https://api.github.com/users/GregSutcliffe","html_url":"https://github.com/GregSutcliffe","followers_url":"https://api.github.com/users/GregSutcliffe/followers","following_url":"https://api.github.com/users/GregSutcliffe/following{/other_user}","gists_url":"https://api.github.com/users/GregSutcliffe/gists{/gist_id}","starred_url":"https://api.github.com/users/GregSutcliffe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GregSutcliffe/subscriptions","organizations_url":"https://api.github.com/users/GregSutcliffe/orgs","repos_url":"https://api.github.com/users/GregSutcliffe/repos","events_url":"https://api.github.com/users/GregSutcliffe/events{/privacy}","received_events_url":"https://api.github.com/users/GregSutcliffe/received_events","type":"User","site_admin":false},"repo":{"id":7629769,"name":"theforeman.org","full_name":"GregSutcliffe/theforeman.org","owner":{"login":"GregSutcliffe","id":827786,"avatar_url":"https://avatars.githubusercontent.com/u/827786?v=3","gravatar_id":"","url":"https://api.github.com/users/GregSutcliffe","html_url":"https://github.com/GregSutcliffe","followers_url":"https://api.github.com/users/GregSutcliffe/followers","following_url":"https://api.github.com/users/GregSutcliffe/following{/other_user}","gists_url":"https://api.github.com/users/GregSutcliffe/gists{/gist_id}","starred_url":"https://api.github.com/users/GregSutcliffe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GregSutcliffe/subscriptions","organizations_url":"https://api.github.com/users/GregSutcliffe/orgs","repos_url":"https://api.github.com/users/GregSutcliffe/repos","events_url":"https://api.github.com/users/GregSutcliffe/events{/privacy}","received_events_url":"https://api.github.com/users/GregSutcliffe/received_events","type":"User","site_admin":false},"private":false,"html_url":"https://github.com/GregSutcliffe/theforeman.org","description":"The new and improved Foreman website.","fork":true,"url":"https://api.github.com/repos/GregSutcliffe/theforeman.org","forks_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/forks","keys_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/keys{/key_id}","collaborators_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/teams","hooks_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/hooks","issue_events_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/issues/events{/number}","events_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/events","assignees_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/assignees{/user}","branches_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/branches{/branch}","tags_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/tags","blobs_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/git/refs{/sha}","trees_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/git/trees{/sha}","statuses_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/statuses/{sha}","languages_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/languages","stargazers_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/stargazers","contributors_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/contributors","subscribers_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/subscribers","subscription_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/subscription","commits_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/commits{/sha}","git_commits_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/git/commits{/sha}","comments_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/comments{/number}","issue_comment_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/issues/comments{/number}","contents_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/contents/{+path}","compare_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/compare/{base}...{head}","merges_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/merges","archive_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/downloads","issues_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/issues{/number}","pulls_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/pulls{/number}","milestones_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/milestones{/number}","notifications_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/labels{/name}","releases_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/releases{/id}","deployments_url":"https://api.github.com/repos/GregSutcliffe/theforeman.org/deployments","created_at":"2013-01-15T17:38:30Z","updated_at":"2015-09-21T14:37:56Z","pushed_at":"2016-03-08T12:46:37Z","git_url":"git://github.com/GregSutcliffe/theforeman.org.git","ssh_url":"git@github.com:GregSutcliffe/theforeman.org.git","clone_url":"https://github.com/GregSutcliffe/theforeman.org.git","svn_url":"https://github.com/GregSutcliffe/theforeman.org","homepage":null,"size":28805,"stargazers_count":0,"watchers_count":0,"language":"HTML","has_issues":false,"has_downloads":true,"has_wiki":true,"has_pages":true,"forks_count":0,"mirror_url":null,"open_issues_count":0,"forks":0,"open_issues":0,"watchers":0,"default_branch":"gh-pages"}},"base":{"label":"theforeman:gh-pages","ref":"gh-pages","sha":"577a21b44834071a1e793e45ac3df18c7de8057b","user":{"login":"theforeman","id":1439844,"avatar_url":"https://avatars.githubusercontent.com/u/1439844?v=3","gravatar_id":"","url":"https://api.github.com/users/theforeman","html_url":"https://github.com/theforeman","followers_url":"https://api.github.com/users/theforeman/followers","following_url":"https://api.github.com/users/theforeman/following{/other_user}","gists_url":"https://api.github.com/users/theforeman/gists{/gist_id}","starred_url":"https://api.github.com/users/theforeman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theforeman/subscriptions","organizations_url":"https://api.github.com/users/theforeman/orgs","repos_url":"https://api.github.com/users/theforeman/repos","events_url":"https://api.github.com/users/theforeman/events{/privacy}","received_events_url":"https://api.github.com/users/theforeman/received_events","type":"Organization","site_admin":false},"repo":{"id":5928690,"name":"theforeman.org","full_name":"theforeman/theforeman.org","owner":{"login":"theforeman","id":1439844,"avatar_url":"https://avatars.githubusercontent.com/u/1439844?v=3","gravatar_id":"","url":"https://api.github.com/users/theforeman","html_url":"https://github.com/theforeman","followers_url":"https://api.github.com/users/theforeman/followers","following_url":"https://api.github.com/users/theforeman/following{/other_user}","gists_url":"https://api.github.com/users/theforeman/gists{/gist_id}","starred_url":"https://api.github.com/users/theforeman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theforeman/subscriptions","organizations_url":"https://api.github.com/users/theforeman/orgs","repos_url":"https://api.github.com/users/theforeman/repos","events_url":"https://api.github.com/users/theforeman/events{/privacy}","received_events_url":"https://api.github.com/users/theforeman/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/theforeman/theforeman.org","description":"The new and improved Foreman website.","fork":false,"url":"https://api.github.com/repos/theforeman/theforeman.org","forks_url":"https://api.github.com/repos/theforeman/theforeman.org/forks","keys_url":"https://api.github.com/repos/theforeman/theforeman.org/keys{/key_id}","collaborators_url":"https://api.github.com/repos/theforeman/theforeman.org/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/theforeman/theforeman.org/teams","hooks_url":"https://api.github.com/repos/theforeman/theforeman.org/hooks","issue_events_url":"https://api.github.com/repos/theforeman/theforeman.org/issues/events{/number}","events_url":"https://api.github.com/repos/theforeman/theforeman.org/events","assignees_url":"https://api.github.com/repos/theforeman/theforeman.org/assignees{/user}","branches_url":"https://api.github.com/repos/theforeman/theforeman.org/branches{/branch}","tags_url":"https://api.github.com/repos/theforeman/theforeman.org/tags","blobs_url":"https://api.github.com/repos/theforeman/theforeman.org/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/theforeman/theforeman.org/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/theforeman/theforeman.org/git/refs{/sha}","trees_url":"https://api.github.com/repos/theforeman/theforeman.org/git/trees{/sha}","statuses_url":"https://api.github.com/repos/theforeman/theforeman.org/statuses/{sha}","languages_url":"https://api.github.com/repos/theforeman/theforeman.org/languages","stargazers_url":"https://api.github.com/repos/theforeman/theforeman.org/stargazers","contributors_url":"https://api.github.com/repos/theforeman/theforeman.org/contributors","subscribers_url":"https://api.github.com/repos/theforeman/theforeman.org/subscribers","subscription_url":"https://api.github.com/repos/theforeman/theforeman.org/subscription","commits_url":"https://api.github.com/repos/theforeman/theforeman.org/commits{/sha}","git_commits_url":"https://api.github.com/repos/theforeman/theforeman.org/git/commits{/sha}","comments_url":"https://api.github.com/repos/theforeman/theforeman.org/comments{/number}","issue_comment_url":"https://api.github.com/repos/theforeman/theforeman.org/issues/comments{/number}","contents_url":"https://api.github.com/repos/theforeman/theforeman.org/contents/{+path}","compare_url":"https://api.github.com/repos/theforeman/theforeman.org/compare/{base}...{head}","merges_url":"https://api.github.com/repos/theforeman/theforeman.org/merges","archive_url":"https://api.github.com/repos/theforeman/theforeman.org/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/theforeman/theforeman.org/downloads","issues_url":"https://api.github.com/repos/theforeman/theforeman.org/issues{/number}","pulls_url":"https://api.github.com/repos/theforeman/theforeman.org/pulls{/number}","milestones_url":"https://api.github.com/repos/theforeman/theforeman.org/milestones{/number}","notifications_url":"https://api.github.com/repos/theforeman/theforeman.org/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/theforeman/theforeman.org/labels{/name}","releases_url":"https://api.github.com/repos/theforeman/theforeman.org/releases{/id}","deployments_url":"https://api.github.com/repos/theforeman/theforeman.org/deployments","created_at":"2012-09-24T02:36:57Z","updated_at":"2016-03-08T01:35:45Z","pushed_at":"2016-03-10T10:57:17Z","git_url":"git://github.com/theforeman/theforeman.org.git","ssh_url":"git@github.com:theforeman/theforeman.org.git","clone_url":"https://github.com/theforeman/theforeman.org.git","svn_url":"https://github.com/theforeman/theforeman.org","homepage":null,"size":30528,"stargazers_count":44,"watchers_count":44,"language":"HTML","has_issues":true,"has_downloads":true,"has_wiki":false,"has_pages":true,"forks_count":125,"mirror_url":null,"open_issues_count":24,"forks":125,"open_issues":24,"watchers":44,"default_branch":"gh-pages"}},"_links":{"self":{"href":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563"},"html":{"href":"https://github.com/theforeman/theforeman.org/pull/563"},"issue":{"href":"https://api.github.com/repos/theforeman/theforeman.org/issues/563"},"comments":{"href":"https://api.github.com/repos/theforeman/theforeman.org/issues/563/comments"},"review_comments":{"href":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563/comments"},"review_comment":{"href":"https://api.github.com/repos/theforeman/theforeman.org/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/theforeman/theforeman.org/pulls/563/commits"},"statuses":{"href":"https://api.github.com/repos/theforeman/theforeman.org/statuses/06404d8b75a22dbf2e624f8b76e3eb58f3f82673"}}}}