-
Notifications
You must be signed in to change notification settings - Fork 38
Radar 20 #312
Comments
Roadmap (what?) |
Queues (what?)
|
For me, just finishing up my last week of my internship...Time flew by for me! Was camping all weekend, so that was fun 😸 |
(I just moved three tickets to L2 Support, based on #290 (comment).) |
My goal for the week is to make significant progress on the Pivot. Recall our timetable:
We've got this week and next week to clean up Gratipay 2.0 as much as we can before driving traffic, and that's what the Pivot milestone is about. |
Inbox 1, GitHub 20, L2 Support 3. |
Inbox 1, GitHub 0, L2 Support 3. |
Inbox 1, GitHub 0, L2 Support 0. |
Okay! What to work on? :-) |
I'm diving in on gratipay/gratipay.com#3399, using that ticket to steer the Pivot. |
I am inordinately happy looking at the revised about page: https://gratipay.com/about/. :-) |
@whit537 I really like the revised about page and it answers many questions that were not addressed previously 🎯 |
Thanks @kzisme! Working on more "About" updates in gratipay/gratipay.com#3687 ... |
I am in the process of searching for a full time job to get out of debts. But I hope to finish my notes about setting up development with LXC. It requires Linux, but is much faster. |
I am trying to stay out of everyone's way. Incidentally, I was just walking down the hall recasting my office's shared coffee economy into Gratipay terms: Team Coffee is a group who purchase and redistribute coffee grounds and push buttons on the machine, without expectation of compensation. People (who may not be on Team Coffee) benefit from these actions. It's easy to join Team Coffee--instructions are posted in our #coffee Slack channel, and nobody has to ask to use the shared coffeemaker resource. All that's missing is other ~users who wish to subscribe to Team Coffee, thereby providing the team with revenue to distribute. (Unfortunately, this example broke down when I realized that only people at my place of work are allowed to join Team Coffee, so it's not truly open.) |
Hah! 💃 !m @mattbk |
☕ ← There it is. :-) |
I just resolved an error! :-) gratipay/gratipay.com#3674 Errors 110. 💃 |
/me climbs out of gratipay/gratipay.com#3399 for the evening. Off tomorrow, be back Wednesday! :-) !m * |
Another version of "open work" to which Gratipay could be applied: Science!. The "product" being paid for might need to be more explicit, but I think even covering costs to publish in an Open Access (OA) journal would count as producing a product. |
Heck yeah! We're friends with the Center for Open Science (their Gratipay). We should figure out a partnership once 2.0 is further along. |
P.S., Tugboat (local Pittsburgh print shop) is totally killing it with their latest project. |
@whit537 I'm definitely stopping in there this weekend...I've been quite fond of Dave DiCello's photography work - I bought one of his photos recently :) |
Nice! TIL. :-) |
Alright, Bountysource is competing with us. Head to head. Toe to toe. Moving in on our turf. Edging us out. Kicking us while we're down. Going for the jugular. Moving in for the kill. No two ways about it. There, I said it. :-) Who's ready to find out what "open competition" looks like? #316 💃 |
I used to search Twitter for https://github.com/search?q=gratipay+-user%3Agratipay&type=Issues&utf8=%E2%9C%93 |
So much for that. :-( |
Alright! Revised team application (gratipay/gratipay.com#3694) is live! We still have a 💩-ton of work to do on the Pivot. Next week is a big week. And then the month after that. 🎼 |
It's a valid question, especially regarding the vagueness of Terms 4.iii:
|
You'll also note that he followed up to ask what he could work on. |
Moreover, it's not one we're going to escape if we want to keep serving the open-source community—which, of course, we do. Especially if we're going to compete with Bountysource (#316), we're going to have to start becoming more visible again (cf. #297, etc.), and people are bound to continue asking for our "stance" on the Gittip Crisis. We need to have some response other than fleeing in terror. Here's the problem: I can't in good conscience tell my side of the Gittip Crisis story (and I can't in good conscience explain why I can't in good conscience tell my side of the story; this recurses, with no base case). By extension, therefore, I don't see that there can be an "actual stance Gratipay has on the whole controversy that Gittip went through[,]" because for Gratipay to have a "stance" would be tantamount to me telling my side of the story. I think that's the most honest thing we can say about it. cc: @seanstrom |
Apart from that, I think we're starting to get clear on what the next six weeks look like for us:
@seanstrom If you do decide to get involved, these Radar tickets are where we coordinate work each week. |
Thanks for going more indepth with your response. I appreciate your honesty on the matter. I think what I should have asked was: Before the controversy, and before I knew of the controversy, I wouldn't think much about the possibility of something like that happening. But now that something has happen, people (like me) may be more cautious around the whole matter. That all said, I don't want to make anyone tell me their personal information to clear my own conscience. I just want to know where Gratipay ultimately stands and what this organization would do if presented with that circumstance. If this line of questioning still conflicts then I'll understand, but I agree with you, Gratipay should have response to the issue. I'm definitely willing to help with that as well. |
also thanks @mattbk for speaking about this more, and also on my behalf. 🍰 😄 |
I just see the issue as a conflation of "Gratipay" and "@whit537". If these are separate entities, @seanstrom's question is easier to answer. Even at an open company, though, the buck has to stop somewhere, and to outsiders it's unclear where. |
@seanstrom @mattbk I've reticketed formulating a response to questions about the Gittip Crisis as #319. |
Email (what?) |
What are you working on this week and why?
last week
The text was updated successfully, but these errors were encountered: