Trying to come up with a response to that has made me feel like a sleaze ball for asking. :/ Basically, there are a few Twitter management services that have team features that we need. The problem is they're all expensive as crap. We're pretty much at a stalemate with ourselves on handling the Twitter account, and I'm trying to find a way forward.
I realized I'm essentially asking for handouts, which is pretty gross.
@svincent: When you're back: io.js isn't technically a non-profit, and hasn't filed a 501c3. Also, everybody's stretched thin with payments from their pockets for io.js as-is that even $25 is a lot, especially per month.
Yes, but since the first day I found io.js, he's been very concerned about events that had already happened that had reflected negatively on the io.js account. He's been very clear that he wants a team management tool where there won't be any toe stepping or mistakes.
I'm having a hard time writing and not sounding like an ass right now.
Hootsuite seems to be a better choice, if we're looking at pricing. They also have a non-profit setup, but they, as would be expected, also define non-profit as a 503c3 organizations (that's a tax form).
iojs/io.js#1060 1.5 will be out in a couple of days, Buffer#indexOf is the major one in there, we'll have to make sure to mention why Colin has removed himself from the TC too because that might set off alarm bells for people
@rvagg I read in one of the iojs/io.js discussion issues that it would be harder to reconcile with Node.js once we bumped major. Does this have credence in reality, or is it just someone blowing smoke?
Indirectly perhaps, a major version bump means there's a breaking functionality change and that's the part that impacts on reconciliation -- but in reality I don't think that's any more of a concern than a lot of the other technical decisions being taken in io.js. So no, I don't buy that a major version bump in itself has any impact on this.