{"action":"created","issue":{"url":"https://api.github.com/repos/PyAbel/PyAbel/issues/73","repository_url":"https://api.github.com/repos/PyAbel/PyAbel","labels_url":"https://api.github.com/repos/PyAbel/PyAbel/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/PyAbel/PyAbel/issues/73/comments","events_url":"https://api.github.com/repos/PyAbel/PyAbel/issues/73/events","html_url":"https://github.com/PyAbel/PyAbel/issues/73","id":130990294,"number":73,"title":"Issue triage meeting for Pyabel v1.0 in February","user":{"login":"rth","id":630936,"avatar_url":"https://avatars.githubusercontent.com/u/630936?v=3","gravatar_id":"","url":"https://api.github.com/users/rth","html_url":"https://github.com/rth","followers_url":"https://api.github.com/users/rth/followers","following_url":"https://api.github.com/users/rth/following{/other_user}","gists_url":"https://api.github.com/users/rth/gists{/gist_id}","starred_url":"https://api.github.com/users/rth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rth/subscriptions","organizations_url":"https://api.github.com/users/rth/orgs","repos_url":"https://api.github.com/users/rth/repos","events_url":"https://api.github.com/users/rth/events{/privacy}","received_events_url":"https://api.github.com/users/rth/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/PyAbel/PyAbel/labels/discussion","name":"discussion","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/PyAbel/PyAbel/milestones/2","html_url":"https://github.com/PyAbel/PyAbel/milestones/Version%200.7","labels_url":"https://api.github.com/repos/PyAbel/PyAbel/milestones/2/labels","id":1423032,"number":2,"title":"Version 0.7","description":"Adding a few other inverse Abel implementations. Converge to a consistent user interface.","creator":{"login":"rth","id":630936,"avatar_url":"https://avatars.githubusercontent.com/u/630936?v=3","gravatar_id":"","url":"https://api.github.com/users/rth","html_url":"https://github.com/rth","followers_url":"https://api.github.com/users/rth/followers","following_url":"https://api.github.com/users/rth/following{/other_user}","gists_url":"https://api.github.com/users/rth/gists{/gist_id}","starred_url":"https://api.github.com/users/rth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rth/subscriptions","organizations_url":"https://api.github.com/users/rth/orgs","repos_url":"https://api.github.com/users/rth/repos","events_url":"https://api.github.com/users/rth/events{/privacy}","received_events_url":"https://api.github.com/users/rth/received_events","type":"User","site_admin":false},"open_issues":10,"closed_issues":28,"state":"open","created_at":"2015-11-21T11:17:04Z","updated_at":"2016-02-03T10:56:39Z","due_on":null,"closed_at":null},"comments":2,"created_at":"2016-02-03T10:56:31Z","updated_at":"2016-02-03T22:56:41Z","closed_at":null,"body":"*Actually for clarity copying my previous message in a new issue here.*\r\n\r\n@DanHickstein  Congratulations on your new job! Myself I'm also in a bit of a job transition at the moment (leaving the academia), so I will probably not be able to contribute to PyAbel much in the  future beyond some light maintenance. Still, I completely agree that we should  make the final push to get to v1.0 for PyAbel, and there are a number of points I should finish myself  :)\r\n> we should make a final push to get the code documented, cleaned up, and ready for public consumption.  [...] we should get the documentation in working order and make the package look professional. Basically, the 1.0 release. \r\n\r\n@DanHickstein @stggh @DhrubajyotiDas I was thinking that it might be useful to make a short meeting (say 30 min) to go through the open issue together, decide what needs to be done for v1.0 and what each us is willing to work on given his availability. As email (or github messaging) conversation tend to linger, it would it probably be more efficient to just make decisions in a viso-conference (I was thinking Google Hangouts).  \r\n\r\nBecause of the time difference this could be [a bit tricky](https://www.timeanddate.com/worldclock/meetingtime.html?iso=20160210&p1=195&p2=57&p3=179&p4=75), but essentially something like,\r\n   -  9 AM Canberra time (day after), 3PM Denver CO time, 5PM Eastern Standard Time (EST) and 11PM Paris time could work for all of us, I think.\r\n\r\n*Note:* @DanHickstein I can't find the message where you mention the location of your new post-doc, I think it was not far from Texas, right? so in EST time, isn't it? @DhrubajyotiDas I'm not certain if you are in the EST time zone? @stggh Note, that there is a +1 day difference in the date for Australia. \r\n\r\nHere is a poll to decide on the date: http://doodle.com/poll/xahg84847swz252x\r\nEven if 3 out 4 of us can make it, that would already be great.  I will send the Google Hangouts link shortly before (it requires to have a gmail account).   What do you think?"},"comment":{"url":"https://api.github.com/repos/PyAbel/PyAbel/issues/comments/179517441","html_url":"https://github.com/PyAbel/PyAbel/issues/73#issuecomment-179517441","issue_url":"https://api.github.com/repos/PyAbel/PyAbel/issues/73","id":179517441,"user":{"login":"stggh","id":10932229,"avatar_url":"https://avatars.githubusercontent.com/u/10932229?v=3","gravatar_id":"","url":"https://api.github.com/users/stggh","html_url":"https://github.com/stggh","followers_url":"https://api.github.com/users/stggh/followers","following_url":"https://api.github.com/users/stggh/following{/other_user}","gists_url":"https://api.github.com/users/stggh/gists{/gist_id}","starred_url":"https://api.github.com/users/stggh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stggh/subscriptions","organizations_url":"https://api.github.com/users/stggh/orgs","repos_url":"https://api.github.com/users/stggh/repos","events_url":"https://api.github.com/users/stggh/events{/privacy}","received_events_url":"https://api.github.com/users/stggh/received_events","type":"User","site_admin":false},"created_at":"2016-02-03T22:56:41Z","updated_at":"2016-02-03T22:56:41Z","body":"Hmm, such a meeting is doubly tricky for me:\r\n\r\n  (1) Hardware\r\n          At work (ANU) I use Linux workstations that have no video capabilities.  I do have a Macbook Pro at my home, which I could bring into the ANU (on my bicycle), but the wifi network is really slow, so I would need to apply for an IP address to gain access to the ANU wired network.\r\n\r\n   (2) Software\r\n         I eschew anything Microsoft, simply because I love Linux. I once had a skype account (under the old software/owners) but let it lapse due to lack of use.  I will need to renew/reapply for a skype account.\r\n\r\nI would be quite happy to connect while I am at home, so 7am-9am, Wednesday or Thursday (Canberra time) would work, and perhaps, be more convenient for all others. I am also available during the weekend, which may open up @rth's google hangouts.\r\n"}}