A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Timestamp | Which code repository should we use for OpenRefine? | Why do you prefer that code repository? | Where should we keep documentation? | Where should we track issues (bugs, feature requests, patches)? | Is it important to provide continuity of issue tracking and transfer open issues? | Is it important to transfer ALL issues (open and closed)? | Where should we perform code reviews (prior to submitting code)? | Where should we host our project mailing list? | Where should we provide technical support? (multiple selection) | Any other thought? | ||||||||||
2 | 10/9/2012 11:49:27 | GitHub | Easy code sharing between ancillary projects. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 1 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
3 | 10/9/2012 11:52:13 | Google Code SVN | I have problems in getting git repository behind proxy network | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 5 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
4 | 10/9/2012 11:53:47 | GitHub | I find it easy to submit contributions because the branching and merging model is easier. It's also the location where I keep all my other code | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 2 | 2 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | To encourage participation it would be useful to identify a list of tasks, even very small ones that people can contribute towards completing. These could be anything from simple bug fixes or feature additions, or creation of documentation, etc. | ||||||||||
5 | 10/9/2012 11:56:13 | GitHub | cleanest | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 3 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | there are a couple of scripts on Github user repositories, a bit quick and dirty tools that exploit google code and Guthub API to transfer issues, they could be taken as starting point to ease the transfer. | ||||||||||
6 | 10/9/2012 11:56:27 | GitHub | It's where a number of my projects already are and it'll be easier to keep tabs on the project there. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | Thanks for all of the wonderful work. | ||||||||||
7 | 10/9/2012 11:56:59 | GitHub | I find that GitHub provides a more advanced set of features and a very intuitive workflow, which makes both development and contributing much easier. I find myself less tempted to contribute to projects which don't use GitHub unless I'm very passionate about them, because it's less convenient. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 2 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel, Issue tracker for chosen repository | |||||||||||
8 | 10/9/2012 11:57:13 | GitHub | Because as a USGS Developer, we already have a signed agreement with Github as an open-source repository. It is way easier to extend code that is hosted on Github than anywhere else. I would en up moving everything that I did to Github anyways. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 1 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | Looking forward to the new OpenRefine | ||||||||||
9 | 10/9/2012 12:06:39 | Default issue tracking system provided by code hosting site | 3 | 2 | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||||||
10 | 10/9/2012 12:09:03 | Google Code Git | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 4 | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||||
11 | 10/9/2012 12:12:30 | GitHub | Nicer UI, nicer tools. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 2 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | IRC is secondary for support unless you get global coverage of active contributors. Whether to do commit-then-review (CTR) or review-then-commit (RTC) depends on the number of active committers. CTR is for smaller projects, RTC for larger ones. RTC with a small pool of active reviewers stifles the project. | ||||||||||
12 | 10/9/2012 12:28:50 | GitHub | It increases peripheral innovation and "collaboration without coordination". Second best would be git on google code. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 1 | Rietveld (https://codereview.appspot.com/) | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
13 | 10/9/2012 12:31:59 | GitHub | Prefer the features available. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 1 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
14 | 10/9/2012 12:45:05 | GitHub | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 2 | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||||
15 | 10/9/2012 12:56:50 | Google Code Git | Social integration | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 4 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | Simple and open is important. | ||||||||||
16 | 10/9/2012 12:58:41 | GitHub | Large number of active users, active development by github, responsive | Default wiki provided by code hosting site | 4 | 3 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | ||||||||||||
17 | 10/9/2012 13:04:47 | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | ||||||||||||||
18 | 10/9/2012 13:28:19 | GitHub | The community seems to prefer this over Google Code. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 3 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
19 | 10/9/2012 14:03:07 | GitHub | 1. Familiarity with Github 2. Online reviews seem to favour Github 3. Learning curve for future contributors could effectively be lowered due to its widespread use | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 5 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
20 | 10/9/2012 14:38:19 | GitHub | Excellent site usability and issue integration | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 2 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
21 | 10/9/2012 14:39:20 | Google Groups (same as this current mailing list, but renamed to openrefine) | Pretty open to most of these issues - I'm not a developer, really an end user. | ||||||||||||||||||
22 | 10/9/2012 14:53:23 | GitHub | More active, individual devs on Github. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | ||||||||||||||||
23 | 10/9/2012 14:55:09 | GitHub | Best basis for broad open source collaboration. Based on my experience coordinating projecthydra & traching hydracamp. | Default wiki provided by code hosting site | Redmine | 2 | 2 | Tightly enforce standards of quality through social means while allowing committers to self-police & opt into reviews when needed | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel, Encourage people to list themselves as vendors on wiki; encorage user meetups | Glad this is happening! If you want to pick brains of people who have done this, contact hydra-tech@googlegroups.com or hydra-steering@googlegroups.com Or email me matt@curationexperts.com. Cheers! | ||||||||||
24 | 10/9/2012 15:00:13 | GitHub | Everyone is there. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 3 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
25 | 10/9/2012 23:48:00 | GitHub | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 4 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | ||||||||||||
26 | 10/10/2012 0:20:16 | GitHub | Ease of use, popular | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 2 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
27 | 10/10/2012 0:39:14 | GitHub | Easy to use, built into existing workflows | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 2 | Sorry, not sure | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
28 | 10/10/2012 1:20:33 | GitHub | What most people are using, so better for building community. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 1 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||
29 | 10/10/2012 2:59:15 | GitHub | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 4 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | ||||||||||||
30 | 10/10/2012 3:23:47 | GitHub | Most reach | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | As the maintainers of RDF Refine [1] we're utterly supportive and find this a great step. I'm personally willing to throw considerable resources at it, from a couple of projects in form of people for code contributions, documentation, and outreach (which I'll do myself). Cheers, Michael Hausenblas http://mhausenblas.info/ [1] http://refine.deri.ie/ | |||||||||||
31 | 10/10/2012 4:24:43 | GitHub | Robustness and independence | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
32 | 10/10/2012 4:36:29 | Google Code Git | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 5 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | ||||||||||||
33 | 10/10/2012 6:45:10 | GitHub | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 5 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | ||||||||||||
34 | 10/10/2012 7:51:23 | GitHub | As I understand this is the most known repository for current Google Refine developers. We should set up the most friendly environment to keep them engaged. | mediawiki | Default issue tracking system provided by code hosting site | 4 | 3 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | IRC channel, to be discussed. | Here is my position: Development oriented tool (repository, tracking ...): github Code review should grow with the community. No need to add extra burden so far. On the documentation and user support side, a new set of tool less tech / dev. oriented need to be set, so user can easily: (1) find what he is looking for (2) engage with the community (3) participate. The mailing list is really convenient but offer a poor display and search experience. Should we support other languages? | ||||||||||
35 | 10/10/2012 8:08:59 | GitHub | I use github a lot already. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 3 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
36 | 10/10/2012 14:11:50 | GitHub | Easier to access, already have account (and presence) there. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 1 | 1 | We don't do code reviews prior to submitting. | Google Groups (new mailing list) | On project mailing list (as we have been doing), IRC channel | A list of (current) FAQs would be nice to have. | ||||||||||
37 | 10/10/2012 19:46:16 | GitHub | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 1 | 1 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | ||||||||||||
38 | 10/11/2012 0:54:45 | GitHub | I know it yet. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 3 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
39 | 10/11/2012 10:21:17 | Google Code Git | Default issue tracking system provided by code hosting site | 4 | 5 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing), IRC channel | |||||||||||||
40 | 10/11/2012 10:31:15 | GitHub | Google Groups (same as this current mailing list, but renamed to openrefine) | ||||||||||||||||||
41 | 10/11/2012 12:31:27 | GitHub | The Github for Windows tool takes away the pain of Git on windows. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 5 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
42 | 10/11/2012 17:12:04 | GitHub | Simply because I am already using it. | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 1 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | |||||||||||
43 | 10/11/2012 23:40:20 | GitHub | Easy forking (google code supports it too but seems that there is no pull request system). | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 5 | 2 | Default code review system provided by code hosting site | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | There are tools to copy issues from google code to github https://github.com/arthur-debert/google-code-issues-migrator, https://github.com/alexrudnick/migrate-googlecode-issues (not tried it) | ||||||||||
44 | 10/13/2012 4:17:19 | GitHub | Default wiki provided by code hosting site | Default issue tracking system provided by code hosting site | 4 | 1 | We don't do code reviews prior to submitting. | Google Groups (same as this current mailing list, but renamed to openrefine) | On project mailing list (as we have been doing) | ||||||||||||
45 | |||||||||||||||||||||
46 | |||||||||||||||||||||
47 | |||||||||||||||||||||
48 | |||||||||||||||||||||
49 | |||||||||||||||||||||
50 | |||||||||||||||||||||
51 | |||||||||||||||||||||
52 | |||||||||||||||||||||
53 | |||||||||||||||||||||
54 | |||||||||||||||||||||
55 | |||||||||||||||||||||
56 | |||||||||||||||||||||
57 | |||||||||||||||||||||
58 | |||||||||||||||||||||
59 | |||||||||||||||||||||
60 | |||||||||||||||||||||
61 | |||||||||||||||||||||
62 | |||||||||||||||||||||
63 | |||||||||||||||||||||
64 | |||||||||||||||||||||
65 | |||||||||||||||||||||
66 | |||||||||||||||||||||
67 | |||||||||||||||||||||
68 | |||||||||||||||||||||
69 | |||||||||||||||||||||
70 | |||||||||||||||||||||
71 | |||||||||||||||||||||
72 | |||||||||||||||||||||
73 | |||||||||||||||||||||
74 | |||||||||||||||||||||
75 | |||||||||||||||||||||
76 | |||||||||||||||||||||
77 | |||||||||||||||||||||
78 | |||||||||||||||||||||
79 | |||||||||||||||||||||
80 | |||||||||||||||||||||
81 | |||||||||||||||||||||
82 | |||||||||||||||||||||
83 | |||||||||||||||||||||
84 | |||||||||||||||||||||
85 | |||||||||||||||||||||
86 | |||||||||||||||||||||
87 | |||||||||||||||||||||
88 | |||||||||||||||||||||
89 | |||||||||||||||||||||
90 | |||||||||||||||||||||
91 | |||||||||||||||||||||
92 | |||||||||||||||||||||
93 | |||||||||||||||||||||
94 | |||||||||||||||||||||
95 | |||||||||||||||||||||
96 | |||||||||||||||||||||
97 | |||||||||||||||||||||
98 | |||||||||||||||||||||
99 | |||||||||||||||||||||
100 |