If I understand what you're saying, we made an open source offering based on our current model: http://codemill.io/for-open-source is that what you're after?
I believe that if you can define your task in as much details, and break it to the most micro level, then it works. If on the other hand, you're issue is something like "there's a bug when sometimes an invoice is inserted with a negative amount", so yeah, this is something more comprehensive, and maybe related to god knows what in the codebase....
I guess it's something in the parallax the theme uses then. I'll need to have a look. What puzzles me is that I don't really feel any problem myself...
You know, the original name we came up with was GigHub. We also found the owner of the domain gighub.io and agreed to buy it. But then I thought we're a GitHub app and the names are too similar and maybe github won't like that, so I asked them, and yes, they said it'll violate their trademark policy and we better find another name...
hehe sorry for that. You know I used a ready made theme, and it works fine on my chrome/mac and I didn't really tested it on many other OS/browsers. What you're using?
I here what you're saying. All of these are also tasks that need to be done. however I believe that in most scenarios, those tasks would have to be held at the organisation level. I'm also not sure the github platform integration would be useful to accomplish that, and the coding itself is the basis for the dev process, we thought we can help with that.
This is something worth thinking about. Of course time, and experience, will tell. We wanted to keep it as simple as possible, and as disruptive as possible to the current employment/contracting process that goes "offline", so we decided to start the way we did. We're not shutting our ears though for ideas.
The idea here, since we don't want to make it a competition or something where only one wins the jackpot, that if a lazy dev takes the job, and he's behind schedule, or provides a low quality deliverance, then the client can unassign. I here your concerns but I hope it won't grow into a backdoor for stealing code.
It's true, a client can do what you describe but then we won't keep them as clients for long ;-) I assume in the future we can add a mechanism to ensure payment in case of such a code "theft", and I admit this isn't handled now. That said, we're talking rather small tasks, not complete projects here, and what you describe is not something that doesn't happen in real life, i.e. contractors that don't get paid. I assume that a developer that works on this system, saves a lot of time on marketing and clients relation and even if 1/100 tasks he is not paid for, it still be worthwhile than the alternatives.
This is true also outside of the platform and in any business whatsoever. The payee is always at risk of not being paid. That said I believe this system will overall prove to reduce risk for developers and increase overall collecting ratio. The tasks that are being dealt here are meant to be small and specific. Not full scale projects. And once a merge happens, the payment is immediate. Also, a developer that uses this system heavily will have a never ending pipeline of work and won't be required to do marketing and customer care anymore, so all in all, their monthly income will increase.
If by accident you've opened the issue before applying CodeMill to the repo, or added the codemill$price tag in an edit action (github doesn't fire webhooks on edit issues) then please simply add a new comment to the issue with the codemill$price tag and it will work
Yes, there is this point at time between the pull request and the merge. We didn't build any engine to support a possible negligence by the client who sponsors the work. However we do believe that clients won't just "submit" work orders and then ignore them.
You need to install it globally and it needs to be able to copy files into /usr. I reckoned this is how its down with global npm installations. Do you have any other solution?
This algorithm is more relevant to shops where the products on sale aren't that widely distributed all over. It's more for the Shopify, BigCommerce etc speciality shops. It will never compete with Amazon (as long as amazon works on fixed prices)
If you play with it enough, you'll see that it won't go down to the minimum in all cases. The algorithm will insist on what it analyzes the user will pay, and will prefer to lose the sale on account of saving its credibility for the long run.
Also, this is just the beginning. It will get much wiser as we go.
To be honest I really didn't spend much time debugging the add-to-cart button for this demo. I hope ppl understand that and focus on the bargain experience.
Considering the % of abandoned shopping carts these days, I doubt if there's any lower place to go :) however of course you have a point. This things needs testing.
yes but i wanted to keep the language natural. and if you naturally want to address dropbox on twitter, then you "@dropbox" them, and not "DM @ctrltwit do something with dropbox".
moreover i realized best usecases are replies to tweets (like liking an instagram photo, subscribing to a youtube channel, saving to pocket), and those wouldn't have been possible with DMs
However - I always thought of twitter more as a communication protocol rather then a content app. I think twitter today is indeed already full of noise, and anyway there's no way to use it for content without curation tools.
I didn't consult with a lawyer or something... each company and their "branding" rules for API users and most allow to use the logo under certain restrictions that to my best understanding I don't break. Dropbox for instance had to approve the app before I could use the API and I bet they had a look at the website beforehand.