{"id":3597,"date":"2014-12-07T11:59:46","date_gmt":"2014-12-07T11:59:46","guid":{"rendered":"http:\/\/peerproduction.net\/?page_id=3597"},"modified":"2014-12-08T01:18:10","modified_gmt":"2014-12-08T01:18:10","slug":"reviews","status":"publish","type":"page","link":"http:\/\/peerproduction.net\/editsuite\/issues\/issue-6-disruption-and-the-law\/peer-reviewed-articles\/cultures-of-sharing-in-thingiverse-what-can-we-learn-from-the-licence-choices-of-thingiverse-users\/reviews\/","title":{"rendered":"Reviews"},"content":{"rendered":"
\n

Review A<\/h2>\n
\n

Reviewer:<\/strong><\/p>\n

 <\/p>\n

1) Is the subject matter relevant?<\/strong><\/p>\n

Yes \u2013 very interesting; this article deals with IP controversies and licensing choices in 3D printing \u2013 as the authors rightly note, it\u2019s something that will only grow in importance.<\/p>\n

 <\/p>\n

2) Is the treatment of the subject matter intellectually interesting? Are there citations of bodies of literature you think are essential to which the author has not referred?<\/strong><\/p>\n

The authors present an interesting discussion and a good analysis of the data. It is mostly well situated within the literature. My major suggestion to improve the paper is to better integrate the two substantive parts. The IP controversies in Thingiverse that are presented as case studies do not really frame the data collected and analysed \u2013 the paper seems almost at times like two halves of different papers. The link between these two halves is that Thingiverse does not seem to be as open as the rhetoric that surrounds it \u2013 either from the platform\u2019s side or from the point of view of users, half of whom choose to keep their Things private. I think this is really interesting, but I would like to see it expanded upon. There\u2019s not quite enough given to make a compelling argument or analysis, but there is certainly the potential to do so.<\/p>\n

 <\/p>\n

3) Are there any noticeable problems with the author’s mean of validating assumptions or making judgments?<\/strong><\/p>\n

Because much of the link discussed above rests on the speculation about why many Things are private, I think this needs to be treated in a slightly more in-depth way than it currently is. I would assume, for example, that many people are just experimenting with 3D printing, and don\u2019t necessarily feel the confidence to share their designs with a wide audience \u2013 but I\u2019m not sure that it necessarily follows that Thingiverse does not have an \u2018open\u2019 culture. I\u2019d really like to see the authors tease this out a bit more.<\/p>\n

 <\/p>\n

4) Is the article well written?<\/strong><\/p>\n

Yes. My main suggestion is to make the argument a bit more clear in the introduction to better explain the conclusions to the reader.<\/p>\n

 <\/p>\n

5) Are there portions of the article that you recommend to be shortened, excised or expanded?<\/strong><\/p>\n

As above \u2013 I think the analysis and the link between the parts of the paper could usefully be expanded.<\/p>\n

 <\/p>\n<\/div>\n

Review B<\/h2>\n
\n

Reviewer:<\/strong><\/p>\n

1) Is the subject matter relevant?<\/strong><\/p>\n

Yes. However, the most interesting issues have only been treated superficially. For example,<\/p>\n

 <\/p>\n

2) Is the treatment of the subject matter intellectually interesting? Are there citations of bodies of literature you think are essential to which the author has not referred?<\/strong><\/p>\n

The introductory part is very interesting but the empirical part is a bit weak, and only scratches the surface without going deeper into potential causalities or explanations of the collected and described data.<\/p>\n

 <\/p>\n

3) Are there any noticeable problems with the author’s mean of validating assumptions or making judgements?<\/strong><\/p>\n

\u201cTo make things worse, MakerBot released new 3D printing software to accompany the new printer which also did not comply with open source principles.\u201d <\/i><\/p>\n

This implies judgment of the business strategy, which should be discussed.<\/p>\n

 <\/p>\n

4) Is the article well written?<\/strong><\/p>\n

Yes.<\/p>\n

 <\/p>\n

5) Are there portions of the article that you recommend to be shortened, excised or expanded?<\/strong><\/p>\n

A description of Thingiverse\u2019s business model would be very helpful. The business model and the question regarding the openness of the platform are at the core of the issues discussed in this article. For example, does the site sell advertisement space or are there any fees\/premium memberships? Is Thingiverse predominately a vehicle to promote Makerbots? Clarifications of these issues could help to interpret the behaviours of users and the platform better.<\/p>\n

 <\/p>\n

\u201c<\/i>Our first finding, based on an analysis of metadata from the 68,618 Public Things in our sample\u201d. <\/i><\/p>\n

Here, the authors speak of a \u201csample\u201d. Before, they indicate that the 117,450 Things are the entirety of Things available on Thingiverse between the indicated time frame? If it is a sample, the authors should discuss the sampling technique.<\/p>\n

As the license choice is at the core for the article\u2019s arguments, an elaboration on the process how users chose a license would be insightful. Eg does the site recommend specific licenses? Does the site offer explanations about licenses? Do uploaders have to actively choose a license or is a default license applied?<\/p>\n

Regarding figure 2: It could be made clearer that the text refers to the size of the blobs. Also, a quick explanation about the difference between \u201camount of remixes\u201d and \u201camount of makes\u201d would be helpful. Especially, as the figure indicates that there is a significant difference between the BY and BY-SA Things with regards to \u201camount of makes\u201d but the text does not address this difference.<\/p>\n

\u201c<\/i>In other words, non-sticking licences seem to be preferred when remixing objects\u201c. <\/i><\/p>\n

This conclusion should be discussed a bit more in-depth. Isn\u2019t it trivial that remixers prefer less restrictive licenses provided that all other factors are constant (which has to be assumed if no other information is given)? Why should someone choose a Thing with a more restrictive license if the same Thing is available with a less restrictive license? There might be other factors potentially influencing the decision to remix a Thing such as perceived quality.<\/p>\n

\u201cThis remixing pattern can be compared with how users use the \u201ccollection\u201d function. CC BY (blue) and CC BY-SA (grey) licensed Things are almost equal in terms of how many times they are included in user collections.\u201d [\u2026] \u201cLicence choice does not seem to make a difference in collections\u201d.<\/i><\/p>\n

What is the assumed motivation of users to include Things in collections? Respectively, what is the implication of this observation? Some informed speculations of the authors about the reasons and implications of those findings would be insightful.<\/p>\n

 <\/p>\n

\u201cThe most common tag that users attach to Things is customized (19,206 times). This tag, which refers to Thingiverse users handling Things in a way more close to \u2018remixing\u2019 these designs than \u2018building them from scratch\u2019, reveals the iterative, collaborative kind of production model on which that Thingiverse prides itself.\u201d <\/i><\/p>\n

 <\/p>\n

The numbers should be put into perspective. Of 117,450 Things in total (assuming it is the total population and not a sample, see comment above) 68,618 are public of which 19,206 are customized (16% of total). This is not a majority. Hence, the number does not support strongly the claim that Thingiverse is a collaborative platform. To put it a different way, according to the data, 84% of Things are either private or not customized. Some discussion of this point would be good.<\/p>\n

 <\/p>\n

Things with \u201cprivate\u201d status have been saved as drafts. Interestingly, it seems that over time the share of Private Things among all Things has been growing. <\/i><\/p>\n

 <\/p>\n

The data only provides weak support for this conclusion because the time frame is short (3 month) and the increase is minor (< 2%). It might be just a random fluctuation.<\/p>\n

 <\/p>\n

\u201cIf it is true that closed systems tend toward control, while open ones tend toward innovation, then the enclosure of Thingiverse may suggest that it is losing its innovative character.\u201d <\/i><\/p>\n

 <\/p>\n

It\u2019s not really clear whether the \u201csystem\u201d refers to the openness of Thingiverse.com or the openness of its users. Above, the authors describe Thingiverse as a \u201ccommercial, proprietary platform, owned by a large, global corporation\u201d. I do not understand why there has to be an alignment between the platform\u2019s philosophy regarding openness and the users\u2019 philosophies. In other words, a platform can be closed but provide services for users to share content openly, depending on the business model.<\/p>\n

 <\/p>\n

A few words about a possible link between the quality of Things and chosen licenses would be interesting. Intuitively, I would expect that high quality Things are published under more restrictive licenses (as more time and effort have been invested) than low quality Things.<\/p>\n

 <\/p>\n<\/div>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"

Reviewer:   1) Is the subject matter relevant? Yes \u2013 very interesting; this article deals with IP controversies and licensing choices in 3D printing \u2013 as the authors rightly note, it\u2019s something that will only grow in importance.   2) Is the treatment of the subject matter intellectually interesting? Are<\/p>\n

Read more<\/a><\/p>\n","protected":false},"author":16,"featured_media":0,"parent":3562,"menu_order":2,"comment_status":"open","ping_status":"closed","template":"template_full_width.php","meta":[],"tags":[],"_links":{"self":[{"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/pages\/3597"}],"collection":[{"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/comments?post=3597"}],"version-history":[{"count":7,"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/pages\/3597\/revisions"}],"predecessor-version":[{"id":3718,"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/pages\/3597\/revisions\/3718"}],"up":[{"embeddable":true,"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/pages\/3562"}],"wp:attachment":[{"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/media?parent=3597"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/peerproduction.net\/editsuite\/wp-json\/wp\/v2\/tags?post=3597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}