{"action":"created","issue":{"url":"https://api.github.com/repos/rosindex/rosindex.github.io/issues/102","labels_url":"https://api.github.com/repos/rosindex/rosindex.github.io/issues/102/labels{/name}","comments_url":"https://api.github.com/repos/rosindex/rosindex.github.io/issues/102/comments","events_url":"https://api.github.com/repos/rosindex/rosindex.github.io/issues/102/events","html_url":"https://github.com/rosindex/rosindex.github.io/issues/102","id":55763814,"number":102,"title":"support ROS-I development status / maturity","user":{"login":"jbohren","id":1253450,"avatar_url":"https://avatars.githubusercontent.com/u/1253450?v=3","gravatar_id":"","url":"https://api.github.com/users/jbohren","html_url":"https://github.com/jbohren","followers_url":"https://api.github.com/users/jbohren/followers","following_url":"https://api.github.com/users/jbohren/following{/other_user}","gists_url":"https://api.github.com/users/jbohren/gists{/gist_id}","starred_url":"https://api.github.com/users/jbohren/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbohren/subscriptions","organizations_url":"https://api.github.com/users/jbohren/orgs","repos_url":"https://api.github.com/users/jbohren/repos","events_url":"https://api.github.com/users/jbohren/events{/privacy}","received_events_url":"https://api.github.com/users/jbohren/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/rosindex/rosindex.github.io/labels/missing-from-wiki","name":"missing-from-wiki","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-28T14:39:55Z","updated_at":"2015-01-30T01:49:10Z","closed_at":null,"body":"@shaun-edwards I noticed that ROS-I packages have this additional software status tag on the wiki\r\n\r\nhttp://wiki.ros.org/Industrial/Software_Status\r\n\r\nDo you think this could be put in an `<export>` tag like:\r\n\r\n```xml\r\n<export>\r\n  <industrial>\r\n    <maturity status=\"experimental\"/>\r\n  </industrial>\r\n</export>\r\n```\r\n\r\nThis has the added benefit of having authorship accountability, since it will be in version-controlled source and not just displayed on a wiki page."},"comment":{"url":"https://api.github.com/repos/rosindex/rosindex.github.io/issues/comments/72140547","html_url":"https://github.com/rosindex/rosindex.github.io/issues/102#issuecomment-72140547","issue_url":"https://api.github.com/repos/rosindex/rosindex.github.io/issues/102","id":72140547,"user":{"login":"jbohren","id":1253450,"avatar_url":"https://avatars.githubusercontent.com/u/1253450?v=3","gravatar_id":"","url":"https://api.github.com/users/jbohren","html_url":"https://github.com/jbohren","followers_url":"https://api.github.com/users/jbohren/followers","following_url":"https://api.github.com/users/jbohren/following{/other_user}","gists_url":"https://api.github.com/users/jbohren/gists{/gist_id}","starred_url":"https://api.github.com/users/jbohren/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbohren/subscriptions","organizations_url":"https://api.github.com/users/jbohren/orgs","repos_url":"https://api.github.com/users/jbohren/repos","events_url":"https://api.github.com/users/jbohren/events{/privacy}","received_events_url":"https://api.github.com/users/jbohren/received_events","type":"User","site_admin":false},"created_at":"2015-01-30T01:49:10Z","updated_at":"2015-01-30T01:49:10Z","body":"> It would be great if every package has such a status. I tried a while back to get \"universal\" ROS adoption, but several important people weren't on board. Other projects have used the software status.\r\n\r\nYeah, there used to be the `review` status, but that went away along with reviews.\r\n\r\n> My one concern would be keeping wiki material and the rosindex material synced. This is probably a general concern inherent in making a switch like this. Probably more appropriate for a different discussion and larger group.\r\n\r\nI'm not really concerned about keeping the material \"synced\" since nothing is actually stored in rosindex. All rosindex does is display what it finds in the repositories. If you move this information to the package.xml, I'm sure you could work with the OSRF guys to get a macro which displays the value extracted from that, too.\r\n\r\n> +1 to the idea itself. I assume the <export> tag would go in the package.xml?\r\n\r\nYeah.\r\n\r\n> I would recommend using xml elements vs. attributes (see here for discussion).\r\n\r\nYeah, I've heard such arguments before. I personally don't care about which convention it uses."}}