And here we go unloading my CSCW related tabs in no particular order :
An Interview with Volker Wulf and Myriam Lewkowicz on “The European Tradition of CSCW”
https://link.springer.com/article/10.1007/s12599-018-0525-5
[#]cscw #history
=> More informations about this toot | More toots from aurelien@hci.social
By Aarhus peeps including @heenrik : 'A Farmer, a Place and at least 20 Members': The Development of Artifact Ecologies in Volunteer-based Communities
The community artifact ecology concept is important for CSCW as it enables framing of the relationship between communities and technologies beyond the single artifact and beyond a static view of a dedicated technology.
[#]cscw #community #ecology
=> More informations about this toot | More toots from aurelien@hci.social
Landscapes of Practice: Bricolage as a Method for Situated Design
This paper proposes a `bricolage' approach to designing systems for cooperative work. This involves users, participatory designers and ethnographers in a continuing cycle of design and revised work practice, often in settings where resources are limited and short-term results are required.
https://link.springer.com/article/10.1023/A:1011293210539
[#]cscw #design #participation
=> More informations about this toot | More toots from aurelien@hci.social
Socialization in an Open Source Software Community: A Socio-Technical Analysis
From these analyses it appears that successful participants progressively construct identities as software craftsmen, and that this process is punctuated by specific rites of passage. Successful participants also understand the political nature of software development and progressively enroll a network of human and material allies to support their efforts
https://link.springer.com/article/10.1007/s10606-005-9000-1
ping @eda
[#]cscw #oss #community
=> More informations about this toot | More toots from aurelien@hci.social
A Situated Approach of Roles and Participation in Open Source Software Communities
We propose a methodology—based on situated analyses of a formal design process used in the Python project—to identify the distribution of actual roles (implementation, interactive, group, and design oriented) performed by participants into and between the spaces (defining boundary spaces).
https://www.tandfonline.com/doi/abs/10.1080/07370024.2013.812409
[#]cscw #oss #community #commons
=> More informations about this toot | More toots from aurelien@hci.social
@aurelien thank you :)
=> More informations about this toot | More toots from eda@framapiaf.org
@aurelien is there a way to download the pdf even if I’m not subscribed?
=> More informations about this toot | More toots from amalgam_@mastodon.social
@amalgam_ @aurelien
Here is the full article, vive HAL and Open Science Platforms <3
https://shs.hal.science/halshs-00860554/document
=> More informations about this toot | More toots from eda@framapiaf.org
@amalgam_ @aurelien And the article from Duchenaut (the firts one) is available here : https://www.researchgate.net/profile/Nicolas-Ducheneaut/publication/220168951_Socialization_in_an_Open_Source_Software_Community_A_Socio-Technical_Analysis/links/0deec5201de2ccca57000000/Socialization-in-an-Open-Source-Software-Community-A-Socio-Technical-Analysis.pdf
=> More informations about this toot | More toots from eda@framapiaf.org This content has been proxied by September (3851b).Proxy Information
text/gemini