The Experts below are selected from a list of 25977 Experts worldwide ranked by ideXlab platform

Piotr Sliz - One of the best experts on this subject based on the ideXlab platform.

  • A Quick Guide to Software Licensing for the Scientist-Programmer
    PLoS computational biology, 2012
    Co-Authors: Andrew Morin, Jennifer M. Urban, Piotr Sliz
    Abstract:

    Computing is ubiquitous in every domain of scientific research. Software is the means by which scientists harness the power of computers, and much scientific computing relies on Software conceived and developed by other practicing researchers. The task of creating scientific Software, however, does not end with the publication of computed results. Making the developed Software available for inspection and use by other scientists is essential to reproducibility, peer-review, and the ability to build upon others’ work. In fulfilling expectations to distribute and disseminate their Software, scientist-programmers are required to be not only proficient scientists and coders, but also knowledgeable in legal strategies for Licensing their Software. Navigating the often complex legal landscape of Software Licensing can be overwhelming, even for sophisticated programmers. Institutional technology transfer offices (TTOs) exist to help address this need, but due to mismatches in expectations or specific domain knowledge, interactions between scientists and TTO staff can result in suboptimal outcomes. As practitioners in the scientific computing and technology law fields, we have witnessed firsthand the confusion and difficulties associated with Licensing scientifically generated Software. Together, we offer a primer on Software Licensing with a focus on the particular needs of the scientist-Software developer in choosing a Software license and engaging with TTOs.

  • a quick guide to Software Licensing for the scientist programmer
    PLOS Computational Biology, 2012
    Co-Authors: Andrew Morin, Jennifer M. Urban, Piotr Sliz
    Abstract:

    Computing is ubiquitous in every domain of scientific research. Software is the means by which scientists harness the power of computers, and much scientific computing relies on Software conceived and developed by other practicing researchers. The task of creating scientific Software, however, does not end with the publication of computed results. Making the developed Software available for inspection and use by other scientists is essential to reproducibility, peer-review, and the ability to build upon others' work [1], [2]. In fulfilling expectations to distribute and disseminate their Software, scientist-programmers are required to be not only proficient scientists and coders, but also knowledgeable in legal strategies for Licensing their Software. Navigating the often complex legal landscape of Software Licensing can be overwhelming, even for sophisticated programmers. Institutional technology transfer offices (TTOs) exist to help address this need, but due to mismatches in expectations or specific domain knowledge, interactions between scientists and TTO staff can result in suboptimal outcomes. As practitioners in the scientific computing and technology law fields, we have witnessed firsthand the confusion and difficulties associated with Licensing scientifically generated Software. SBGrid.org is a consortium of scientific Software developers and users in hundreds of biomedical research laboratories worldwide. As facilitator and middleman between developers and end-users, we commonly assist in the dissemination and use of scientifically generated Software. Through research and advocacy, the Samuelson Law, Technology and Public Policy Clinic works with Software developers and other creators on Licensing issues, particularly issues related to facilitating “open access” to scientific, technical, or creative materials. Together, we offer a primer on Software Licensing with a focus on the particular needs of the scientist Software developer. The aim of this guide is to help scientists better engage with their institutional TTO when choosing Software licenses.

Andrew Morin - One of the best experts on this subject based on the ideXlab platform.

  • A Quick Guide to Software Licensing for the Scientist-Programmer
    PLoS computational biology, 2012
    Co-Authors: Andrew Morin, Jennifer M. Urban, Piotr Sliz
    Abstract:

    Computing is ubiquitous in every domain of scientific research. Software is the means by which scientists harness the power of computers, and much scientific computing relies on Software conceived and developed by other practicing researchers. The task of creating scientific Software, however, does not end with the publication of computed results. Making the developed Software available for inspection and use by other scientists is essential to reproducibility, peer-review, and the ability to build upon others’ work. In fulfilling expectations to distribute and disseminate their Software, scientist-programmers are required to be not only proficient scientists and coders, but also knowledgeable in legal strategies for Licensing their Software. Navigating the often complex legal landscape of Software Licensing can be overwhelming, even for sophisticated programmers. Institutional technology transfer offices (TTOs) exist to help address this need, but due to mismatches in expectations or specific domain knowledge, interactions between scientists and TTO staff can result in suboptimal outcomes. As practitioners in the scientific computing and technology law fields, we have witnessed firsthand the confusion and difficulties associated with Licensing scientifically generated Software. Together, we offer a primer on Software Licensing with a focus on the particular needs of the scientist-Software developer in choosing a Software license and engaging with TTOs.

  • a quick guide to Software Licensing for the scientist programmer
    PLOS Computational Biology, 2012
    Co-Authors: Andrew Morin, Jennifer M. Urban, Piotr Sliz
    Abstract:

    Computing is ubiquitous in every domain of scientific research. Software is the means by which scientists harness the power of computers, and much scientific computing relies on Software conceived and developed by other practicing researchers. The task of creating scientific Software, however, does not end with the publication of computed results. Making the developed Software available for inspection and use by other scientists is essential to reproducibility, peer-review, and the ability to build upon others' work [1], [2]. In fulfilling expectations to distribute and disseminate their Software, scientist-programmers are required to be not only proficient scientists and coders, but also knowledgeable in legal strategies for Licensing their Software. Navigating the often complex legal landscape of Software Licensing can be overwhelming, even for sophisticated programmers. Institutional technology transfer offices (TTOs) exist to help address this need, but due to mismatches in expectations or specific domain knowledge, interactions between scientists and TTO staff can result in suboptimal outcomes. As practitioners in the scientific computing and technology law fields, we have witnessed firsthand the confusion and difficulties associated with Licensing scientifically generated Software. SBGrid.org is a consortium of scientific Software developers and users in hundreds of biomedical research laboratories worldwide. As facilitator and middleman between developers and end-users, we commonly assist in the dissemination and use of scientifically generated Software. Through research and advocacy, the Samuelson Law, Technology and Public Policy Clinic works with Software developers and other creators on Licensing issues, particularly issues related to facilitating “open access” to scientific, technical, or creative materials. Together, we offer a primer on Software Licensing with a focus on the particular needs of the scientist Software developer. The aim of this guide is to help scientists better engage with their institutional TTO when choosing Software licenses.

R Manimegalai - One of the best experts on this subject based on the ideXlab platform.

  • SSCC - SPIC - SRAM PUF Intergrated Chip Based Software Licensing Model.
    Communications in Computer and Information Science, 2019
    Co-Authors: Vyshak Suresh, R Manimegalai
    Abstract:

    A Software license key or a product key is a Software based key that is used during the installation of a Software. This key authorizes a genuine purchase of the Software product by the user and verifies the authenticity of the Software installation copy. Hackers have made successful attempts in thwarting the Software license key checking and hence cracked copies of the original versions are released. They not only cause losses for the companies but also render the hard work and dedication of the Software development team useless. To counter such hacks, companies have resorted to various checks and countermeasures but all have been beaten in one way or another. In this paper, a Software Licensing model which generates a key from SRAM PUF source is proposed.

  • spic sram puf intergrated chip based Software Licensing model
    International Symposium on Security in Computing and Communication, 2018
    Co-Authors: Vyshak Suresh, R Manimegalai
    Abstract:

    A Software license key or a product key is a Software based key that is used during the installation of a Software. This key authorizes a genuine purchase of the Software product by the user and verifies the authenticity of the Software installation copy. Hackers have made successful attempts in thwarting the Software license key checking and hence cracked copies of the original versions are released. They not only cause losses for the companies but also render the hard work and dedication of the Software development team useless. To counter such hacks, companies have resorted to various checks and countermeasures but all have been beaten in one way or another. In this paper, a Software Licensing model which generates a key from SRAM PUF source is proposed.

Michael Hoye - One of the best experts on this subject based on the ideXlab platform.

  • Investigating whether and how Software developers understand open source Software Licensing
    Empirical Software Engineering, 2019
    Co-Authors: Daniel A. Almeida, Greg Wilson, Gail C. Murphy, Michael Hoye
    Abstract:

    Software provided under open source licenses is widely used, from forming high-profile stand-alone applications (e.g., Mozilla Firefox) to being embedded in commercial offerings (e.g., network routers). Despite the high frequency of use of open source licenses, there has been little work about whether Software developers understand the open source licenses that they use. To help understand whether or not developers understand the open source licenses they use, we conducted a survey that posed development scenarios involving three popular open source licenses (GNU GPL 3.0, GNU LGPL 3.0 and MPL 2.0) both alone and in combination. The 375 respondents to the survey, who were largely developers, gave answers consistent with those of a legal expert’s opinion in 62% of 42 cases. Although developers clearly understood cases involving one license, they struggled when multiple licenses were involved. To understand the context in which Licensing issues arise in practice, we analyzed real-world questions posed by developers about the three licenses considered in the survey on online question-and-answer communities. We also interviewed practicing developers about license interaction problems they have faced. Among several lessons, we learnt that Licensing issues can constrain Software evolution and that developers are cautious of more restrictive licenses. Our results indicate a need for tool support to help guide developers in understanding the structure of the code and the technical details of a project while taking into account the exact requirements imposed by the licenses involved.

Jennifer M. Urban - One of the best experts on this subject based on the ideXlab platform.

  • A Quick Guide to Software Licensing for the Scientist-Programmer
    PLoS computational biology, 2012
    Co-Authors: Andrew Morin, Jennifer M. Urban, Piotr Sliz
    Abstract:

    Computing is ubiquitous in every domain of scientific research. Software is the means by which scientists harness the power of computers, and much scientific computing relies on Software conceived and developed by other practicing researchers. The task of creating scientific Software, however, does not end with the publication of computed results. Making the developed Software available for inspection and use by other scientists is essential to reproducibility, peer-review, and the ability to build upon others’ work. In fulfilling expectations to distribute and disseminate their Software, scientist-programmers are required to be not only proficient scientists and coders, but also knowledgeable in legal strategies for Licensing their Software. Navigating the often complex legal landscape of Software Licensing can be overwhelming, even for sophisticated programmers. Institutional technology transfer offices (TTOs) exist to help address this need, but due to mismatches in expectations or specific domain knowledge, interactions between scientists and TTO staff can result in suboptimal outcomes. As practitioners in the scientific computing and technology law fields, we have witnessed firsthand the confusion and difficulties associated with Licensing scientifically generated Software. Together, we offer a primer on Software Licensing with a focus on the particular needs of the scientist-Software developer in choosing a Software license and engaging with TTOs.

  • a quick guide to Software Licensing for the scientist programmer
    PLOS Computational Biology, 2012
    Co-Authors: Andrew Morin, Jennifer M. Urban, Piotr Sliz
    Abstract:

    Computing is ubiquitous in every domain of scientific research. Software is the means by which scientists harness the power of computers, and much scientific computing relies on Software conceived and developed by other practicing researchers. The task of creating scientific Software, however, does not end with the publication of computed results. Making the developed Software available for inspection and use by other scientists is essential to reproducibility, peer-review, and the ability to build upon others' work [1], [2]. In fulfilling expectations to distribute and disseminate their Software, scientist-programmers are required to be not only proficient scientists and coders, but also knowledgeable in legal strategies for Licensing their Software. Navigating the often complex legal landscape of Software Licensing can be overwhelming, even for sophisticated programmers. Institutional technology transfer offices (TTOs) exist to help address this need, but due to mismatches in expectations or specific domain knowledge, interactions between scientists and TTO staff can result in suboptimal outcomes. As practitioners in the scientific computing and technology law fields, we have witnessed firsthand the confusion and difficulties associated with Licensing scientifically generated Software. SBGrid.org is a consortium of scientific Software developers and users in hundreds of biomedical research laboratories worldwide. As facilitator and middleman between developers and end-users, we commonly assist in the dissemination and use of scientifically generated Software. Through research and advocacy, the Samuelson Law, Technology and Public Policy Clinic works with Software developers and other creators on Licensing issues, particularly issues related to facilitating “open access” to scientific, technical, or creative materials. Together, we offer a primer on Software Licensing with a focus on the particular needs of the scientist Software developer. The aim of this guide is to help scientists better engage with their institutional TTO when choosing Software licenses.