{"action":"created","issue":{"url":"https://api.github.com/repos/zackbatist/open-archaeo/issues/1","repository_url":"https://api.github.com/repos/zackbatist/open-archaeo","labels_url":"https://api.github.com/repos/zackbatist/open-archaeo/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/zackbatist/open-archaeo/issues/1/comments","events_url":"https://api.github.com/repos/zackbatist/open-archaeo/issues/1/events","html_url":"https://github.com/zackbatist/open-archaeo/issues/1","id":391503588,"node_id":"MDU6SXNzdWUzOTE1MDM1ODg=","number":1,"title":"Not just \"What do we have?\" but also \"What is missing?\"","user":{"login":"nevrome","id":10789038,"node_id":"MDQ6VXNlcjEwNzg5MDM4","avatar_url":"https://avatars2.githubusercontent.com/u/10789038?v=4","gravatar_id":"","url":"https://api.github.com/users/nevrome","html_url":"https://github.com/nevrome","followers_url":"https://api.github.com/users/nevrome/followers","following_url":"https://api.github.com/users/nevrome/following{/other_user}","gists_url":"https://api.github.com/users/nevrome/gists{/gist_id}","starred_url":"https://api.github.com/users/nevrome/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nevrome/subscriptions","organizations_url":"https://api.github.com/users/nevrome/orgs","repos_url":"https://api.github.com/users/nevrome/repos","events_url":"https://api.github.com/users/nevrome/events{/privacy}","received_events_url":"https://api.github.com/users/nevrome/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2018-12-16T20:48:28Z","updated_at":"2018-12-19T20:42:29Z","closed_at":null,"author_association":"NONE","body":"In a brief exchange with @carlosrellan on twitter a few months ago I had the idea to create a ToDo list for archaeological open source software. This might be a great resource for thesis projects, hackathons, unconferences, summer schools etc. \r\n\r\nOn Friday this idea emerged again in a conversation with @nmueller18 and I remembered this new \"What do we have\" list by you, @zackbatist. Your list could be a starting point for a collection of ToDos. The community of practice for digital archaeology is pretty small, so it could be possible to establish it as a common hub for ideas and feature requests. Or does everybody prefer to protect their good project ideas?\r\n\r\n@carlosrellan was asking for a harris matrix R package, @nmueller18 had several great ideas to reimplement algorithms that already existed in the past but are lost to framework progress and I think there is -- just as an example -- a desperate need for a simple graph/network transformation package in R.\r\n\r\nMaybe @joeroe, @MartinHinz, @florianthiery, @dirkseidensticker or @benmarwick have an opinion or some more ideas?\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/zackbatist/open-archaeo/issues/comments/448736921","html_url":"https://github.com/zackbatist/open-archaeo/issues/1#issuecomment-448736921","issue_url":"https://api.github.com/repos/zackbatist/open-archaeo/issues/1","id":448736921,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0ODczNjkyMQ==","user":{"login":"isaacullah","id":8882548,"node_id":"MDQ6VXNlcjg4ODI1NDg=","avatar_url":"https://avatars3.githubusercontent.com/u/8882548?v=4","gravatar_id":"","url":"https://api.github.com/users/isaacullah","html_url":"https://github.com/isaacullah","followers_url":"https://api.github.com/users/isaacullah/followers","following_url":"https://api.github.com/users/isaacullah/following{/other_user}","gists_url":"https://api.github.com/users/isaacullah/gists{/gist_id}","starred_url":"https://api.github.com/users/isaacullah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/isaacullah/subscriptions","organizations_url":"https://api.github.com/users/isaacullah/orgs","repos_url":"https://api.github.com/users/isaacullah/repos","events_url":"https://api.github.com/users/isaacullah/events{/privacy}","received_events_url":"https://api.github.com/users/isaacullah/received_events","type":"User","site_admin":false},"created_at":"2018-12-19T20:42:29Z","updated_at":"2018-12-19T20:42:29Z","author_association":"NONE","body":"Hi all, sorry I'm a little late to the discussion, and thanks for the nice shout-outs about my blog post. Yes, a lot of non-archaeologists use that list (I frequently get emails), but, reading through the thread here, I'm struck by a couple of things:\r\n1) Do we *actuall* need or even want uniformity? Isn't that sort of against the idea of open source? We should have options (e.g., R v. SciPy, QGIS v. GRASS), so people can choose the interfaces they like the best, and tools should be made to be the best at the thing they do, and not try to do everything. \r\n2) We *should* think more about user interfaces. I am not scared by code, but I have been doing it a long time. A lot of my students are frightened to death by it, however, and it takes a lot to get over that. I personally am a BIG fan of widget-based graphical programming interfaces, such as Orange (https://orange.biolab.si/), KNIME (https://www.knime.com/), Flowgarithm (http://www.flowgorithm.org/), AppInventor (http://appinventor.mit.edu/explore/),AgentSheets (http://www.agentsheets.com/), and GRASS's \"graphical modeler\" (https://grass.osgeo.org/grass77/manuals/wxGUI.gmodeler.html). These are MUCH easier for novices to get into, yet they are fully reproducible workflows that can generate real code. \r\n3) Like it or not, archaeology-specific programs are really niche, and as such the audience is fairly limited. Certain things can be wider reaching, as some analyses are shared by other disciplines (my cumulative viewshed tool in GRASS, for example, is very widely used), whereas say a module to create Harris Matrices wouldn't really be used outside of Archaeology. One thing I think computational and digital archaeologists especially have become really good at is seeing the archaeological applications of softwware and hardware designed for other purposes. Just look at the boom in use of off-the-shelf drones and VRware for 3D mapping and scanning of heritage resources. Archaeologists aren't the main coders or builders, but were are really right up at the forefront of those people figuring out secondary (unintended) use-cases for all of that.\r\n4) To that last point, I really think we need to be sharing *generalizable workflows* in addition to just code snippets or specific case studies. For example, here's one of my own: http://isaacullah.github.io/Digital-Data-Collection-for-Field-Sciences/\r\n\r\nAnyway, just my 2 cents on all this. \r\n\r\nShout out to @mpeeples2008 @benmarwick @carlosrellan @izaromanowska ! Hope to see you all soon!"}}
{"actor":{"display_login":"isaacullah"}}