English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

The growing availability of open source projects has facilitated developersto reuse existing software artifacts and leverage them to develop new software.However, it is hard to understand the notion of similarity as it varies fromdeveloper to developer. Some developers might search for repositories withsimilar source code, while some might be in search of repositories with similarrequirements or issues. Existing approaches tend to find similar projects bycomparing similar artifacts such as source-code to source-code, API usage toAPI usage, documentation to documentation, and so on. Even though there is adissimilarity between two similar artifacts, there could be a similaritybetween two dissimilar artifacts. Hence, in this paper, we aim to answer thequestion - Can we find similarity of software repositories through dissimilarartifacts?. To this end, we conduct an experiment to find similarities betweenthree repositories, two similar and one different project comparing similar anddissimilar artifacts (documentation, commits, and source-code). We observedsimilarities between dissimilar artifacts such as Commits, Source Code, andReadme Files in the context of both similar and different repositories.

Apples, Oranges & Fruits -- Understanding Similarity of Software Projects Through The Lens of Dissimilar Artifacts