Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Radar 31 #389

Closed
chadwhitacre opened this issue Nov 3, 2015 · 32 comments
Closed

Radar 31 #389

chadwhitacre opened this issue Nov 3, 2015 · 32 comments

Comments

@chadwhitacre
Copy link
Contributor

What are you working on this week and why?

last week

@chadwhitacre
Copy link
Contributor Author

Roadmap (what?)

Short Term

Embarrassments:

Long Term

roadmap

@chadwhitacre
Copy link
Contributor Author

L2 Support 0, Vendors, etc. 0.

@techtonik
Copy link
Contributor

I am joining the land of JavaScript and trying to switch grtp.co to Gulp (which is funded through Gratipay)

@techtonik
Copy link
Contributor

@whit537 I need someone to help with upgrading grtp.co to Ubuntu 14.04 - gratipay/grtp.co#106 - because I don't have access to Digital Ocean, I can not see if I can prepare a new node like dev.grtp.co and test that it serves traffic as expected.

@chadwhitacre
Copy link
Contributor Author

@kaguillera and I are thinking through #319. We're hoping to look at Team editing and closing the books for October today as well.

@kzisme
Copy link

kzisme commented Nov 4, 2015

@whit537 @mattbk here is a user sending an image with undefined receiving(?) amount. He didn't offer anymore information have we come across anything like that before?

@mattbk
Copy link
Contributor

mattbk commented Nov 4, 2015

gratipay/grtp.co#103

You can add that to embarrassments: It's embarrassing that such a front-facing aspect of the platform is broken.

@chadwhitacre
Copy link
Contributor Author

@mattbk Agreed. Also embarrassing for me is that we don't have our escrow precisely accounted for.

@kzisme
Copy link

kzisme commented Nov 5, 2015

At least we are aware of these things and working to improve them rather than being oblivious - one step at a time 🚶

@chadwhitacre
Copy link
Contributor Author

@kzisme Indeed! 🐢

Also embarrassing for me: the fact that we are at Security 9. We should be running at 0! 😞

@techtonik
Copy link
Contributor

And the reason for that is because Balanced Shutdown + Gratipay 2.0 Model + Gratipay 2.0 Redesign all were happening at the same time in a hurry. Gratipay 1.0 was killed too fast. =)

I also found that I can not receive money in Belarus, so we are trying to work with our offline legal advisers fixing issues with access to actual laws (which appeared to be paid for citizens of my country).

I also added my opinion on #319. Maybe it doesn't propose a consolidated point of view, but Internet was never a place of single voice.

@mattbk
Copy link
Contributor

mattbk commented Nov 5, 2015

Support momentarily 0.

@clone1018
Copy link
Contributor

I'm working on the planning for the Gratipay Retreat :)

@mattbk
Copy link
Contributor

mattbk commented Nov 5, 2015

Just got an email from Wikipedia asking for donations. Wouldn't it be cool to have them as a Team? 😍
Then I considered that they wouldn't be eligible, because they would choose not to use payroll. Just some thoughts for the morning. Gratipay seems to be focusing on the long tail of teams that are marginally viable but have not established internal financial structures. Is this a problem, or just wherw we want to be?

@chadwhitacre
Copy link
Contributor Author

Over on AspenWeb/pando.py#526, @pjz and I are considering winding down the Aspen project, salvaging the best parts, and relaunching as Simplates. The upshot for Gratipay is that we would need to migrate to Flask (with Simplates as a plugin).

@mattbk
Copy link
Contributor

mattbk commented Nov 5, 2015

Team Review 16

@chadwhitacre
Copy link
Contributor Author

Lunch 0. Coffee 0.5. L2 0, Vendors 0. Inbox 6, GitHub 15.

@kaguillera is working on #390. I'm gonna clear out my GitHub queue and then run payday: #394.

@chadwhitacre
Copy link
Contributor Author

Wouldn't it be cool to have [Wikipedia] as a Team?

Yes! 💃

Gratipay seems to be focusing on the long tail of teams that are marginally viable but have not established internal financial structures. Is this a problem, or just wherw we want to be?

I would add that we're betting on a few of those long-tail teams turning out to be the next Wikipedias.

@chadwhitacre
Copy link
Contributor Author

And the reason for that is because Balanced Shutdown + Gratipay 2.0 Model + Gratipay 2.0 Redesign all were happening at the same time in a hurry. Gratipay 1.0 was killed too fast. =)

Tell me about it! Serious case of the bends. O.o

Maybe it doesn't propose a consolidated point of view, but Internet was never a place of single voice.

@techtonik True, true. Whether or not we end up publishing something "official" out of #319, I think multiple voices on that ticket are highly welcome. :-)

@chadwhitacre
Copy link
Contributor Author

I'm working on the planning for the Gratipay Retreat :)

!m @clone1018 💃

@chadwhitacre
Copy link
Contributor Author

Blip: I set an alert at Digital Ocean (new feature of theirs I just noticed) when our usage goes over $10.

@chadwhitacre
Copy link
Contributor Author

Okay! @kaguillera and I are dialing back out of books cleanup (#390) and diving into payday (#394).

@mattbk
Copy link
Contributor

mattbk commented Nov 5, 2015

Wouldn't it be cool to have [Wikipedia] as a Team?

Yes! 💃

Am I right in determining that they wouldn't qualify as a team because they wouldn't be in a position to use Payroll? Don't mean to keep anyone from other things, but this is interesting to me. I suppose that they could use Payroll to pay anyone and everyone who contributes as editors, but that wouldn't really help them sustain the site (that is, they have 300 staff to pay). Maybe I need to take another look at the different Payroll models that have been talked about since 2.0 and see if I can figure this out.

@chadwhitacre
Copy link
Contributor Author

Payday 0, GitHub 0, Inbox 6.

@chadwhitacre
Copy link
Contributor Author

Am I right in determining that they wouldn't qualify as a team because they wouldn't be in a position to use Payroll?

Yeah, probably. :-(

@techtonik
Copy link
Contributor

And the reason for that is because Balanced Shutdown + Gratipay 2.0 Model + Gratipay 2.0 Redesign all were happening at the same time in a hurry. Gratipay 1.0 was killed too fast. =)

Tell me about it! Serious case of the bends. O.o

I mean that after new design popped up I no longer can see to who I am donating and graphs. It is all new and clean, but there is no values visible anymore - I'd still prefer to access the same information I had before but in some PAUSED state. Now everything is hidden or malfunctioning, so on the outside it looks polished, but once I login I don't understand anything.

@mattbk
Copy link
Contributor

mattbk commented Nov 6, 2015

Gratipay has processed about $999,000 over 3+ years.

Is next week the week? $1,000,000 processed?

@chadwhitacre
Copy link
Contributor Author

For the second time! :-)

https://twitter.com/Gratipay/status/576005036926492672

We were somehow counting money differently back then. Overinflating, I guess.

@techtonik
Copy link
Contributor

I'd like Gulp gratipay/grtp.co#108 to be reviewed before going further with migration from Grunt.

This was referenced Jul 10, 2016
This was referenced Aug 7, 2016
This was referenced Sep 18, 2016
This was referenced Oct 9, 2016
This was referenced Oct 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants