public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will • Git public repository: The recipe needs to be hosted in a public Git repository that allows collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will • Git public repository: The recipe needs to be hosted in a public Git repository that allows collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will • Git public repository: The recipe needs to be hosted in a public Git repository that allows collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will • Git public repository: The recipe needs to be hosted in a public Git repository that allows collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will Git public repository: The recipe needs to be hosted in a public Git repository that supports collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will Git public repository: The recipe needs to be hosted in a public Git repository that supports collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will Git public repository: The recipe needs to be hosted in a public Git repository that supports collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will Git public repository: The recipe needs to be hosted in a public Git repository that supports collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will Git public repository: The recipe needs to be hosted in a public Git repository that supports collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If

public, and anyone can use them by simply adding your repository to their Conan remotes. To allow collaboration on open source projects, you can also create Organizations in Bintray and add members who will Git public repository: The recipe needs to be hosted in a public Git repository that supports collaboration. • Recipe fields: description, license and url are required. The license field refers to the lib, that you just develop the packaging code. Such code is also subject to change, often via collaboration, so it should be stored in a VCS like git, and probably put on GitHub or a similar service. If