review fixed cost #928
Comments
|
@nobodxbodon What's your goal, to spend as little as possible? :-) |
|
Saving cost would be a side effect of this reviewing, IMO. It's mainly to check (hopefully periodically) whether we make the most out of each cost, by checking the current usage and exploring alternatives. These costs are recuring and can be more easily overlooked overtime. Besides, we may also consider @kaguillera suggestion of using OS service providers and tip them. Additionally, it would also save managing cost if any of the service is no longer needed, or if we can use one provider instead of two similar ones. |
|
Cool. I just want to make sure that we're on the same page in terms of the principle of paying for what we use. Gratipay exists to solve the free rider problem in open source, and it is important to me that we model non-free-riding with our own vendors. That puts us at odds with traditional ways of thinking about accounting ... but that's what we're about! :-) The reasons you mention are valid. I think we should focus on:
Once we have real data and a common way to look at it, then we can circle back here to have the real discussion, about specific financial decisions. Does that sound right to you? |
|
I wonder what you think of questions below:
Besides, I don't quite see dependency on the accounting system or reporting app. Those may have higher priority but this will have immediate influence on the cash flow. |
Fair enough. Looking over the list, the ones that jump out at me as providing low value are Pipedrive (#917), Librato (gratipay/gratipay.com#4203), and possibly Papertrail (though I think @rohitpaulk will disagree on that one). |
|
I didn't comment on Pipedrive as marketing is one of our weakness and I hoped the tool would help out. If you think it doesn't quite help with the marketing stategry/methods, +1 with removing it. Still the items above together is about half of Travis's cost. Now I feel that I must have missed something about Travis. Are we using some features that the commercial version provides, but the free version doesn't? Or is there some special reason that doesn't qualify us from using the free version? |
|
@nobodxbodon We depend heavily on Travis. We need to give back somehow. If we don't give back monetarily, we need to find another way. What would you propose? |
|
As I mentioned above, here are just some ways I can think of. I'm sure there are many other ways.
|
|
Those are abstract possibilities, yes. Do you have a concrete proposal for what to replace our monetary payment with? Are you volunteering to do any of the things you mention? :-) |
|
For No.1, how about something like below: |
|
I don't think that's equivalent to $69/mo. Do you? |
|
I'm all for paying for what we use, but this must be value driven. I don't think $69/mo for Travis is justified at all in the first place - shouldn't it be along the lines of $25 (how much we pay Github)? Heroku is the one item I definitely wouldn't move - $95/month is definitely worth it. We get database backups, monitoring, easy rollbacks + a reliable service overall. Trying to replicate that on another provider (like AWS) is likely going to cost us as much or more (including man hours). |
IMO it's potentially worth more if compared to ads.
I agree though there are alternatives to Heroku, I haven't seen any has overall better score, considering feature, cost, maturaity, etc. |
|
I think that paying Travis $70/month is better than dedicating man hours to it that should be dedicated here but I also think that Travis deliberately offers free accounts to open source projects because they have the same value system as we do and that (much like our technical debt discussion) it is useful to have a base goal before you prioritize idealism over bottom line. #imho |
|
FYI, another service we may consider using is Netlify, if necessary, as they also are free specially for OS projects: |
Say more? What I'm seeing is that we have a PWYW pricing model (with a floor), and Travis has a freemium model. I'm not comfortable being on the "free" side of a freemium business model. Somehow it's related to my even greater discomfort being on the "free" side of an adware business model. I don't know how best to articulate my discomfort right now (I've tried several times today and want to work on other things :). I mean, we've talked about this in years past, so there's almost certainly a record in the old IRC archives if not GitHub. That doesn't mean we don't need to hash it out again with a new Gratipay generation. :-) Something blah blah, "If you are not paying for it, you're not the customer; you're the product being sold." Blah blah something. But.
I'd be totally fine switching (paid) CI vendors. The next step there would be a comparison with one or more alternatives. Note that we do use a private project as part of our security workflow. |
|
Redhat offers Resource Grants Program for OS projects to run on their Openshift docker platform. Quoting below:
What's more, they use Jenkins CI |
Not really, OpenShift v3, the new version based on Docker, isn't actually launched yet, it's still in developer preview (temporary accounts, can't host real projects on it). |
@whit537 is that a close source project or just a repository to postpone open sourcing the security fixes after they are fixed? If latter it should be still considered OS project I suppose?
@Changaco thanks I overlooked that. Still the migration from v2 app to v3 seems pretty straightforward, and it can take a while to sign up for the Resource Grants Program. So maybe worthwhile to consider starting the process and putting some part of Gratipay on it. |
The latter. The question isn't whether we could get free service from Travis, GitHub, etc. We almost certainly could. The question is whether we should as a matter of policy. |
|
@JessaWitzel pretty much captured my thoughts. |
|
What I mean by same value system is that they obviously want to encourage open source work. We are trying to allow people to get paid for open source work and they are trying to support people who are doing open source work by offering them value for free. "Travis CI is, and always will be, free for open source projects." I don't see an ethical dilemma in taking advantage of the value that they want to offer us until we are bootstrapped (am I using that word right?). I do, however, see why you would want to follow the "you should contribute in some way to the open source code that you use" mantra and set a good example. I just think that Travis has intentionally set this pricing structure up because they want us to be able to take advantage of it, which makes it a little different? << The question mark is there because maybe it's not different. |
Alright, so what's our deadline for paying Travis? If we stop paying them now, will we ever start paying them again? When? How will we know? |
I suppose you mean we'll take the free services for granted and forget about them while using them. If we review services we use periodically (how about twice a year?), that will give good opportunity to decide whether we are in good position to start paying for certain free services.
I don't see any other way than to decide case by case. Similarly, it's hard to tell how much is proper to give to a certain free service to show gratitude. |
|
What would we use $69/mo (~$17/wk) for, if it wasn't going to Travis? Would it be added to https://gratipay.com/Gratipay/distributing/? Would it be used for some other vendor? Would it be saved up for conferences/other travel to drum up business? I think that question needs to be answered in order to determine whether money spent on Travis is worth more than money spent elsewhere. Would Travis be willing to open a project on Gratipay so open-source projects (like ours) can give them an affordable amount, even though it isn't necessary per Travis' open-source-is-free rule? PWYW for the free part of a Freemium model? |
If we're going to accept free services from Travis, it'll be because we're willing to accept free services in general, which means that our cost for GitHub, Sentry, and possibly others (Heroku? Transifex? Librato?) would go away as well.
No. I've actually talked to rkh about it, most recently at #534. They're off and running and it would be more hassle than it'd be worth to accept money PWYW. |
... unless there's a reason why we would keep paying some vendors that offer free services and not others? I suppose it could be because of case-by-case considerations: this vendors needs it more than this other. I think the way we know whether a vendor needs it is that they stop offering free services, or clearly communicate that they are PWYW. In fact, Read the Docs is a vendor that falls into this latter category. We should probably start paying them!
|
+1 Besides, is the option of listing all free services on bottom of homepage on the table? Something like:
|
@mattbk IMO it should be part of budget planning, which I don't think there's a formal one for now? Like what we have, how much is spending, how much to spend and how & when, etc. Anyways, as I mentioned IMO there are many possibilities to spend that in a more direct way to help Gratipay grow. |
|
Good news from Travis!
💃 My response:
|
... and Sticker Mule. ;-) Anyone else I'm forgetting? |
|
Speaking of which, do you think #950 would be a more persistent way to show the acknowledgement from these vendors? |
|
Is #333 still relevent? |
|
Yes, more persistent, but we're unresolved there due to the question of also acknowledging the people that give money to Gratipay and in some cases have done so for years. Since Travis offered a blog post that seemed the easiest way forward. |
Yes, we still use Icomoon. Good catch. |
I've added them to the budget (btw, once gratipay/finances#12 is done, budget changes will be by PR in the finances repo, and will be much more auditable). Apart from settling with Travis, I believe our last task here is to decide on how much we're paying the donation-based services we depend on, and then we can write up a blog post and close this ticket. Does that sound right to you, @nobodxbodon et al.? |
This makes me happy. |
|
From Travis:
|
|
As there's discussion in slack about using mockup service, here's another option: https://balsamiq.com/free/ under category "I contribute to a big Open Source project" |
|
Applied for free mybalsamiq license:
|
|
@whit537 mybalsamiq has agreed to provide Open Source free forever setting for the site (place to create mockup projects) I created. Could you give an email so that I can invite you as staff and then transfer the site to you? |
|
Let's use [email protected]. Thanks, @nobodxbodon! |
|
@whit537 invitation sent. Could you check please? |
|
Got it! Any chance we can change from https://gratipay-ux.mybalsamiq.com/ to just https://gratipay.mybalsamiq.com/? |
|
Owner transferred. As I recall I saw in config a place to change the site name, as far as it's not taken I guess. |
|
Awesome, changed! !m @nobodxbodon |
|
I've added Balsamiq to the spreadsheet. |
|
$20/mo to Read the Docs! |
Our budget for StartSSL had been $119.80/yr, sooooo ... $10/mo to Let's Encrypt! |
|
Upon further inspection, IcoMoon is actually a freemium model, not a pwyw model. We're fine at the free level there, I think. |
|
Report URI ... figure $5/mo, ya? No easy recurring, soooo ... $60 to Report URI! |
Okay! Pwyw services are topped up! Let's use #950 for the blog post. Closing! 💃 🌻 !m @nobodxbodon |
Reticket from #878. Below is based on budget spreadsheet, #73 (comment), http://inside.gratipay.com/appendices/tools. Please list other missing in it.
As I'm not familiar with many services below, or the past related decisions, any input is more than welcome.
The text was updated successfully, but these errors were encountered: