-
Notifications
You must be signed in to change notification settings - Fork 38
Radar 31 #389
Comments
Roadmap (what?)Short Term
Long Term |
L2 Support 0, Vendors, etc. 0. |
I am joining the land of JavaScript and trying to switch grtp.co to Gulp (which is funded through Gratipay) |
@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. |
@kaguillera and I are thinking through #319. We're hoping to look at Team editing and closing the books for October today as well. |
You can add that to embarrassments: It's embarrassing that such a front-facing aspect of the platform is broken. |
@mattbk Agreed. Also embarrassing for me is that we don't have our escrow precisely accounted for. |
At least we are aware of these things and working to improve them rather than being oblivious - one step at a time 🚶 |
@kzisme Indeed! 🐢 Also embarrassing for me: the fact that we are at Security 9. We should be running at 0! 😞 |
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. |
Support momentarily 0. |
I'm working on the planning for the Gratipay Retreat :) |
Just got an email from Wikipedia asking for donations. Wouldn't it be cool to have them as a Team? 😍 |
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). |
Team Review 16 |
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. |
Yes! 💃
I would add that we're betting on a few of those long-tail teams turning out to be the next Wikipedias. |
Tell me about it! Serious case of the bends. O.o
@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. :-) |
!m @clone1018 💃 |
Blip: I set an alert at Digital Ocean (new feature of theirs I just noticed) when our usage goes over $10. |
Okay! @kaguillera and I are dialing back out of books cleanup (#390) and diving into payday (#394). |
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. |
Payday 0, GitHub 0, Inbox 6. |
Yeah, probably. :-( |
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. |
Is next week the week? $1,000,000 processed? |
For the second time! :-) https://twitter.com/Gratipay/status/576005036926492672 We were somehow counting money differently back then. Overinflating, I guess. |
I'd like Gulp gratipay/grtp.co#108 to be reviewed before going further with migration from Grunt. |
What are you working on this week and why?
last week
The text was updated successfully, but these errors were encountered: