Code clones are a pervasive source of technical debt in large software systems. Prior work has focused on detecting clones and analyzing their technical impacts, but the social processes behind clone creation and propagation are underexplored. In this study, we take a socio-technical perspective to examine whether code cloning behavior correlates with developer collaboration patterns. We apply method-level clone detection (NiCad) to four mature open-source projects (python, C, C++, Java) and construct developer interaction networks from co-commits, code reviews, and issue discussions. Through statistical analysis, regression modeling, and community detection, we investigate questions such as: are clones more likely to emerge among socially close developers, and do clones introduced by highly central contributors persist longer or spread more widely? We anticipate that our findings will reveal how collaboration structures influence redundant coding and offer broader insights for managing technical debt. These insights have practical impact: they can inform the design of clone-aware LLM assistants, automated review tools, or onboarding support systems that account for social propagation risks.