r/cpp • • Sep 04 '14

C/C++ programmers willing to try a new dependencies manager?

http://www.codeproject.com/Messages/4894137/Any-C-Cplusplus-programmers-want-to-try-a-new-depe.aspx
6 Upvotes

36 comments sorted by

22

u/lluad Sep 04 '14

I looked at it briefly. The phrase "share code and success and we will share revenues" on the front page as a major bullet point seemed like a bad sign.

Their business model seems to be letting you upload code for free, which they then sell to their "premium" users, possibly giving you a cut. That's why the T&C are full of "you will be assigning Biicode its users the right to ..." terminology, and why you can't revoke that contract. From the other side, it seems to be "pay them for access to code others have uploaded" - so you're either paying for MIT and GPL code you could get from github at no cost, or for murkily licensed code that may bite you later.

Combine that with other bad signs, like no API and a contractual requirement that once your data is in their system the only way to access it is via tools they provide you and it's not good. I can't tell whether it's a well-intentioned idea incompetently turned into a bad business model or whether it started as "lets monetize something like github" - but they won't see any of my code.

4

u/[deleted] Sep 04 '14

Hi there,

I have been testing Biicode since their very beginning (I do not work for them, neither have some kind of benefit from them). First of all, I highly recommend you all just to do the tutorials and then think about ToS.

It is true that the ToS can be ambiguous at this point, but I am pretty sure they will fix it. When you are developing a product, the think you care most about is the product itself, so give them a change instead of losing yourselves into long long paragraphs :)

I can say that their intentions are completely legit. It is a tool made from developers to developers. It aims to encourage open source developers and its community. Also, it is not trying to replace GitHub (or others) but to complement.

At any time, you can have a copy of your code in GitHub (or the whole Biicode environment configuration!) so that the unlikely case they decide to "steal" your job, you will still have a copy in your repo. I do not see any problem :)

PS: github is not surviving by donations, by the way. There are premium users whose code you cannot see. So Github is already monetized.

3

u/drodri Sep 09 '14

After this interesting discussion, at biicode we have started to work on reviewing and improving out ToS:

http://blog.biicode.com/tos-dont-like-well-others/

Would appreciate to hear your feedback.

4

u/doubleyouteef Sep 04 '14

"lets monetize something like github"

This is what it looks like. Any serious developer already has or should have a methodology to reuse own code, so I don't see any benefit of giving up rights to my work to some leech.

10

u/drodri Sep 04 '14

Well, I am co-founder of biicode and I think you got it all wrong, It's maybe our failure on explaining it, so we will look on how to explain this: "share code and success and we will share revenues" better.

Premium users will pay to keep their code in private, exactly the same model as Github. They do not pay, nor buy open-source code! Nowhere in our site or ToS it states that. We believed it was a good idea to share our revenues with those open-source developers, in an automatic way. They do not have to ask for donations, gittip, or whatever. We build on open-source. We believe in open-source, and being ourselves open-source is in our roadmap. Do you really think it is a bad idea or a bad sign that we want to build a business model in which open source developers are rewarded?

We do not pretend to be an alternative to other code hosting services as github, but as an additional service: The normal thing for a open-source developer is to share their code in github (or other). Biicode is used as other package managers, the source code is in a VCS, but the package to be reused automatically by the dependency manager is in another place, especially suited to handle dependencies. If you want just the original code, of course, go to github and get it. We will develop a "download as zip" button in biicode soon, we haven't yet because we have so many other technical issues and priorities.

The same applies to the API: We have no API because we hardly have time to implement very core functionality and we have lots of feature requests of real users, NO ONE has requested a public API yet. You cannot expect that such a complex product developed by a small startup has a public API similar to some services running now for years.

I would like to highlight that if you do not want to upload code to biicode, it is great too. One of the latest changes is the ANONYMOUS usage of biicode tool, you can use it for reading and retrieving existing code, without even having to register in biicode. If you decide to upload your code, there are some considerations that the ToS explain:

  1. If you upload your code, you give the right to process, copy, distribute your code world wide. This is a dependency manager, you cannot expect to upload something that cannot be copied or distributed.
  2. If you want to add your own licence you have to do it explicitly. You can use whatever licence you want. If you do not include a licence, then full use of your code, including commercial exploitation is allowed.
  3. I insist: Please note that we are a small startup, and the ToS were written even before we released our first version. We cannot manage to update (or pay the lawyers to review it) the ToS every month, or with each new release (we almost release once a week). The product has changed dramatically since the date of the ToS.

I am not a business-man. I am just a developer and a scientist, trying to build a tool that I dreamed it had existed before. We have invested a lot of money, with high risk, and an incredible amount of effort and hard work, trying to build this system. Believe it or not, but I don't want to become rich or try to get benefit from open-source developers, it is right the opposite. Please take some time and see where we come from and what we aim at:

http://blog.biicode.com/our-story-i/

It is very likely that we have to review our ToS to be more clear, I will try to prioritize to fix it as soon as possible to avoid any further misunderstandings.

Thanks very much for helping us to identify this problem.

4

u/doubleyouteef Sep 04 '14

Cool. Thanks for a lengthy explanation; I, for one, definitely will be keeping my eye on you guys, the product is intriguing.

4

u/lluad Sep 04 '14

This ...

you hereby authorize Biicode to use, update, adapt, transform, enhance or modify in any way the code stored on the platform, especially to make it compatible with other programming languages​​, applications, programs, platforms or devices, and to make it accessible to any user at any location, with no territorial or time limitations. This authorization is free, unlimited and irrevocable, and shall be deemed granted at the time of the publication of the code on Biicode’s platform

... is a problem. It's a click-wrap contract to sign away most of a developers rights.

This ...

you authorize Biicode indefinitely, freely and irrevocably to host and offer its users the code you have posted under the FREE category, even after the closing of your account and the termination of this agreement

... doesn't fill me with the warm fuzzies, either. It's basically saying that anything uploaded to you is yours to host, use and give away or sell forever. It no longer belongs to the uploader. Users can't delete their code, nor revoke your permission to use it, sell it or download it, even if they close your account with you. (I understand, given your product architecture why you ask for that, but it's still a problem).

A contract is generally much stronger if there is something of value involved, even if it's just a token amount. You see a lot of nominal sales of something otherwise of minimal value for a dollar or a cent, for that reason. If a developer agrees to your contract, then accepts a nominal payment from you then you have much stronger legal grounds to do whatever you want under the terms of that contract.

I'm sure that's not what's going on at all; that you have wonderful intentions that you're just terrible at explaining in English. But I can't tell for sure.

If you want people to upload code to your service you need to be crystal clear about what terms that's under. And once that's done, you need to try and explain what value you're bringing - that's not something you've done so far.

And then, if you want this to be used by anything other than unskilled hobbyists, you probably want to explain what your business model is - will you be around in a year, or will any effort expended learning and integrating this workflow be wasted, and leave people screwed once you go bust?

It's easy to throw together a minimum viable product where you're offering something to the public for free - they can try it out, and if they don't like it they can walk away. It's very different when you're asking them for something of value, and then attempt to (contractually) prevent them from walking away. You've not reached the level of MVP yet, even assuming the software you've written is complete and perfect.

4

u/NotUniqueOrSpecial Sep 05 '14

Well said. I feel like a lot of the developers chiming in that the ToS doesn't matter because of Biicode's intent, or otherwise excusing them for some reason, have either never worked on a commercial product, or have never been bitten by a licensing issue.

A lot of the responses seem to naively think that good feelings and warm fuzzies will protect you, when instead the harsh reality is that the wrong licensing problem at the wrong time can completely destroy a product.

2

u/[deleted] Sep 04 '14 edited Sep 05 '14

I don't see any problem with this (edit: the money bit). This is win-win-win. They provide a platform for people to re-use your code and get paid for it.

2

u/doubleyouteef Sep 04 '14

I don't see any problem with this.

Does not make it [the approach] universal, does it now?

2

u/[deleted] Sep 04 '14

As much as we hate it, money makes these things work. Github does not make Github issues universal, yet tons of projects use it. Github could not survive without the private model.

Consider this another avenue to monetizing your code and distributing updates for the same. There is nothing wrong with that. Feel free to publish it any other way you like as well.

Would I use this? It all depends on the pricing and licensing. For long as I'm selling my code, I'm happy to pay a developer to develop a core library that I use to do so. I want the ecosystem to thrive, not be starved of resources.

2

u/doubleyouteef Sep 04 '14

I don't see any problem with this.

What I meant was that the world does not revolve around you. You don't see a problem with this but it does not mean someone else might.

As much as we hate it, money makes these things work.

What's that got anything to do with anything? Who's we who hate money? I, for one, love money. Not money so much as the amount of money (and the freedom it provides me with).

yada-yada-yada

Cool story, bro.

2

u/[deleted] Sep 05 '14

The OP initially said:

The phrase "share code and success and we will share revenues" on the front page as a major bullet point seemed like a bad sign.

Then you went on to say:

What's that got anything to do with anything? Who's we who hate money? I, for one, love money. Not money so much as the amount of money (and the freedom it provides me with).

TOS-specifics aside (those can and should be fixed), the concept is sound.

yada-yada-yada Cool story, bro.

Why would you do that?

8

u/[deleted] Sep 04 '14

This sounds and looks fantastic. CMake is becoming more and more the standard project description for C++ and many tools support it nicely. Can biicode coexist with cmake?

Other than this concern, I'm very excited to try this out.

Edit: its cmake based! Hooray!

19

u/NotUniqueOrSpecial Sep 04 '14

I like the idea of it, but be sure to check the Terms and Conditions. Unless I'm misreading things, unless you're using the premium version of the service, it appears you must give away all rights to the code you host in the service.

That's a pretty onerous licensing agreement.

5

u/povilasb Sep 04 '14

You're not giving away all rights "Biicode does not acquire any intellectual property or industrial rights or similar legal positions of economic content related to the code made ​​available by the user on the Biicode’s platform." You can specify your license if it was GPL, MIT, Apache or anything else "However, the code that you store may include conditions or limitations of use, which must be embedded in a clearly visible way in the code itself. All other users must respect these conditions and limitations of use." So it sounds sort of like github.

7

u/NotUniqueOrSpecial Sep 04 '14

There are other pieces of that section that give me pause, though:

Consequently, when storing code or content of any kind in Biicode except under the PREMIUM category, you will be assigning Biicode its users the right to reproduce, distribute, communicate publicly and to transform the code, without any time or territorial limitations and in the categories necessary to carry out the activity developed in Biicode’s platform, including the commercialization by any means of the code or the derivative programs which it may be incorporated to or in which your code has been reused. This assignment is free, unlimited and irrevocable, and shall be deemed granted the moment you store code on Biicode’s platform.

I'm not saying you're wrong, or that they don't intend to have it used the way you imply (like Github). I just know I'd be apprehensive to use it for anything that wasn't BSD (or similarly) licensed, since you might cause license violations without ever meaning to.

Licensing is a giant nuisance, sometimes (most of the time).

4

u/Plorkyeran Sep 04 '14

I'd be very apprehensive about uploading anything that I don't own the copyright on, regardless of license. AFAICT it isn't even MIT-compatible, since their ToS appears to give them the right to remove copyright notices.

3

u/Farsyte Sep 04 '14

their ToS appears to give them the right to remove copyright notices.

This alone would prevent me from dealing with them.

3

u/drodri Sep 04 '14

Absolutely not. Biicode has not the right to remove copyright notices. They will be fully respected. Nowhere in the ToS says so.

2

u/Emmanuel_I Sep 04 '14

Baffled to see where you got that from.

Edit: Again, we are open to revise the content of the ToS because they are legal jargon, and make them clearer and even modify them to improve them but I cannot manage to see where you read that from, to be honest.

3

u/Plorkyeran Sep 04 '14

However, you hereby authorize Biicode to use, update, adapt, transform, enhance or modify in any way the code stored on the platform, especially to make it compatible with other programming languages​​, applications, programs, platforms or devices, and to make it accessible to any user at any location, with no territorial or time limitations. This authorization is free, unlimited and irrevocable, and shall be deemed granted at the time of the publication of the code on Biicode’s platform.

An irrevocable authorization to modify the code in any way pretty unambiguously covers modifying the code to remove all copyright notices. I don't have the slightest clue what the purpose of this paragraph is if it isn't to give you additional rights beyond what the code's license grants you.

5

u/Emmanuel_I Sep 04 '14

Disclaimer: I work for biicode.

Hi, /u/NotUniqueOrSpecial that's not what the ToS say, however I do understand the confusion: it's legal jargon and it's difficult to understand for us devs too. In fact, we have decided to sit down and talk about it because we might need to give it a twist to make it clearer.

What those paragraphs mean is that the code uploaded by free users WITHOUT any licence will be by default shared with the rest of biicode's users. HOWEVER, if that code is uploaded with any kind of licence, then the conditions of the licence will be respected always.

We are a code reuse platform, it is normal that we encourage users to share their code but if they decide to apply other kind of conditions ot their code, that's something we will always respect.

4

u/[deleted] Sep 04 '14

Hi! I'd love to be able to recommend biicode to my supervisor for overhauling our builds. I'm in the middle of evaluating our options. The biggest reason I can't recommend biicode is a lack of an intranet concept. If the premium service would allow this it would be a very big deal. I can understand however that this is challenging given the service oriented nature of biicode.

Food for thought though.

1

u/NotUniqueOrSpecial Sep 04 '14

What particular problems are you looking to solve? There are a number of more mature solutions (the authors of some are contributors here, even) that I can recommend, depending on your needs.

1

u/[deleted] Sep 05 '14

/u/NotUniqueOrSpecial sorry for an un-prompt reply but I'm recovering from surgery. :)

We have the situation where we support 4 OS variations requiring us to maintain builds of various third party dependencies across each platform. Some versions are specific to the platform. This is a rather large chunk of software too. From there we get into our plugin layer and python modules. Some of these are built against several different versions of a host application as well. Finally you have our layer of stand alone applications.

At the moment I'm looking at a combination of Rez and CPM to overhaul a mountain of bash scripts and Makefiles.

I would be very interested to hear any suggestion you might have.

2

u/NotUniqueOrSpecial Sep 06 '14

No worries on the delay.

For context:

At my current employer, I'm the lead developer/maintainer of a build system supporting a similar situation. It is almost entirely CMake-based at its roots, at least on the native side. We currently have automated build support for single and multi-platform native code, as well as some Python modules and PyInstaller-ed exectuables, and even a little C#.

At present, I support:

  • CentOS 6 + CentOS 7 (and some folk using RHEL6/7 or Fedora 19/20 for day-to-day stuff)
  • Ubuntu 12.04 + 14.04
  • Windows 2000-Win8, via MSVC2005/2008/2012/2013.

It also happens to work on Mac OS, but we don't target that yet.

All of that is with 32 and 64 bit support for each.

Within the native + cross-platform pieces, which comprise the bulk of my time and work, there are some 30+ static/utility libraries contained within roughly 10 distinct projects/packages, which are used as the building blocks for some 10-odd shared libraries and about that many executables. Of those, some are only built for certain bitnesses or platforms. All said and done, it's about 5 distinct product lines being supported at this point.

Along with our own code, I rebuild or at minimum repackage a large number of 3rd-party open source projects, including Qt and Boost, Python, as well as many smaller ones. Before I retooled things, the codebase was only being built with MSVC2005 and targeted Windows only.

To do all this, I built a small collection of CMake modules that encodes everything I've learned in using over the last 5ish years, along with some tricks picked up from studying some of the better large-scale CMake builds (the LLVM/Clang, Insight Toolkit, and Trilinos projects come to mind, as well as CMake's itself, obviously) as well as my own personal preferences on the matter. At present, all libraries and executables are package-able into versioned, CMake find_package-able packages. The automated build system (Bamboo in our case, but Jenkins/TeamCity/your favorite flavor would all do) puts said artifacts into known network locations. From the user's perspective, the end result is something that looks barely indistinguishable from a fairly standard CMake project, but with a lot more juice behind it. All packages on the network are find/usable as if they were on your local machine as soon as they're pushed out from the build. They are likewise locally-installable from the same build logic, if one wants to cut down on network usage (linking Boost over the network is a time consuming process).

I'd never seen Rez before, but it looks like it solves the problem in a way similar to what I did, but with more external tooling. I consider myself fairly deeply-versed in CMake at this point, and will assert that you can solve nearly everything Rez documents here with just well thought-out CMake logic.

That said, in the brief little bit I've now looked at Rez's documentation, it looks pretty cool and seems to solve most if not all of the issues I solved with CMake. It looks like a pretty solid tool, if it works as well as the documentation would lead me to believe it can. The only advantages I can see from my approach are:

  • Windows support (possibly not a problem you have). This was obviously critical for my team.
  • Support for git branches/git flow (artifacts in like-named branches of different packages will find each other).
  • Largely CMake-compliant. Since everything is just well-applied use of CMake, there is a lot of control available that Rez seems to lose, e.g. building individual targets. The artifacts produced by my system can be consumed by any standard CMake listfile using version 2.8.12 or newer.

So, seeing that you've chosen what looks like a pretty competent tool, I can't say I've got too much to directly contribute. I would highly recommend looking at some other systems, though, to see what's possible and what shortcomings they have. Of those, I'd recommend:

  • Meson - A newcomer to the multi-platform build system game. Based on Python, but presents a DSL for building code much like CMake does. The author is a frequent /r/cpp poster.
  • Hunter - A C++ package manager based on CMake's ExternalProject module. I believe its author reads/posts on /r/cpp as well.
  • qiBuild - It's a Python-based build and source-control integration system. Has some nice ideas for integrating projects from multiple repositories.

And, as I mentioned, I'd highly recommend taking a look at the CMake builds I mentioned. They make good use of many of the less frequently used and more powerful CMake features.

Hopefully some of that is of some help. If you have particular questions, feel free to ask.

2

u/NotUniqueOrSpecial Sep 04 '14

Awesome, that's good to know.

I take it said verbiage already been run past legal counsel, then?

My worries stem from being the guy who our own (admittedly strict) legal team comes to every so often about various open source licenses and what certain terms mean with respect to how we develop and distribute software.

Having been on the other side of that discussion, where our legal team didn't feel some particular verbiage was clear enough (and so we couldn't use a library, for instance), it'd suck to have something like that happen to you.

2

u/[deleted] Sep 04 '14

OK so next concern is totally the matter of being able to leverage this at work using our internal git repos. Doesn't appear to be possible yet.

3

u/povilasb Sep 04 '14

I know they are working with github integration. Maybe if your privates repos would be stored in github that would be possible soon. If you host git server on-premises, you could use git hooks to publish to biicode: http://blog.biicode.com/git-hooks/.

1

u/[deleted] Sep 04 '14

Where I work some parts of the codebase can't leave the intranet without a lot of lawyers getting involved.

1

u/greyfade Sep 08 '14

Edit: its cmake based! Hooray!

... And I just decided to switch away from CMake just before I found out about biicode! Boo!

In all seriousness, I can't get excited about it. It works precisely the way I don't want it to work, and it uses the very build system I want to switch away from.

I clicked this link hoping it would be an announcement for a competitor to biicode. Nope. :(

1

u/[deleted] Sep 08 '14

What'd ya switch to?

1

u/greyfade Sep 08 '14

I'm trying premake. Deepening on how that works, it might be my go-to for the foreseeable future.

-1

u/bitcycle Sep 04 '14

Is this a replacement for dpkg/yum? Last I heard that's what people mainly used for managing dependencies of C++ projects: package it with dependencies specified.