-
Notifications
You must be signed in to change notification settings - Fork 59
review of 201806 pay period rewards by guides #809
Comments
@dckc , @deannald d it's my opinion that quarterly reporting may be fine for traditional centralized organizations, but as we move forward at "lightspeed" i think you'll find monthly reporting useful. The more important question, imo, is why will we continue to have label guides at all? The TAC by definition has the role of communicating to our contributor teams what are the goals are of our Cooperative, and equally of reporting to our Cooperative what the accomplishments of our bounty contributors have been. The TAC is functioning as designed. Please don't add a layer of indirection where none is necessary: it's the role of TAC to do these things and TAC is already doing them well. cc @dckc @deannald @patrick727 @lapin7 |
As to why we continue to have label guides:
The three members of the TAC are not performing the roles you note without help from the guides. The guides are necessary. |
In #803 , I have made a China community report in June . I think this will help the core community know the China community. |
@deannald @Jake-Gillberg I'm headed out for the holiday soon; I'd like your help with #789 (comment) |
I asked @allancto to help @deannald and @PatrickM727 get in touch with the guides to wrap this up. |
@deannald would you please certify the guides that you have formed effective working relationships with? The list of people you have certified is empty. @PatrickM727 the certifications you made as @patrick727 have no effect. Please re-do them as @PatrickM727 . (Well, I'd rather you went back to your @patrick727 account, but I can imagine that's infeasible.) |
@dckc I guess the Community report in Africa for June 2018 can serve the purpose of a review for Africa, what's your take on it? |
The report is coming along nicely. My only question here is: are the Africa rewards for 201806 all set? If so, please check the box above. If not, what is left to do? |
@David405 says there's outstanding voting to fix for a meetup issue. |
Also issue #781 is yet to be addressed by either of the marketing, education and discussion guides save event guide@ojimadu. please I think the guides need to visit with urgency and sort it out. Thanks...Frank Nnalue |
The events label is done for 201806. I voted a budget of $1600 being that marketing and translation guide has created an issue for those labels. I think this should do. I claimed a reward based on an estimated 5 hour work. I and @TrenchFloat needs help completing the rewards. |
Rewards for Africa labeled issues is set. |
Need help with reward and budget vote for this issues 773 782 800. Thanks |
At the request of @lapin7 , I rolled over to July:
p.s. see also July 22 snapshot, Q2 numbers |
@dckc TAC is in touch with the label guides using the Label guide discord server, to which you have been invited. Voting for June is complete. There is a blank report and a list of issues that were budgeted in June in the folder below. Label guides should look at the spreadsheet first, fill in ColumnE for issues you guided, and help complete the overall report. Thanks! -@allancto |
Well, voting for June is over in that the due date is passed. But is it complete in that guides from each label area have confirmed that the votes in their area are appropriate? The empty check-boxes above suggest otherwise. Again, from the July 4 notes:
How are the proceedings of the Label guide discord server published? As to regular reports, as noted in the issue description here, @deannald and I aim for quarterly. Your 30 Jun prediction that the TAC will want to do monthly reports has not yet come true. I renamed the folder and its contents as such (and added the earlier report). Filling in column E of that spread sheet is make-work; their votes are already a matter of record. |
@dckc so your purpose in this issue is for someone (the lead guide in each label?) to check that they've reviewed the votes in their label? ColumnE is there to determine which label is responsible for reporting on an issue (where multiple labels exist). IMO that should be in the issue template. Or are you saying that bit of information is simply irrelevant? Thanks! -@allancto |
Yes; that is: a guide from each label. (As we discussed, I have no use for the notion of "lead guide".)
I'm saying it's redundant make-work. If an issue has multiple labels, then guides for all those labels are responsible for it. If something is labelled Development and I don't want to be responsible for it, then I just remove the Development label. This went quite smoothly in May (#759). My attempt to delegate this time evidently didn't work out. @deannald has wisely reserved some time for TAC / guide meetings, which should smooth things out for next month. |
@TrenchFloat thanks for your question. Both @dckc and @deannald of TAC have requested quarterly reports. The title June was changed to Q2, TAC please let us know how you'd like this handled: should a report still be prepared for Q2 (we have already the May retrospective) or we should wait until Q3 (and make that report Sep 30 leaving June hanging, or Aug 31). Request to Label guides: please indicate by check mark in the issue statement above that you have reviewed voting within your label for June (will post this request as well in the discord Label Guides server). Thanks! -@allancto |
@allancto May was not included in the retrospective report. So May, June, July would make 3 months, unless I'm mistaken. |
Some stuff about May got added to the retrospective report. I found it somewhat confusing. May, June, and July would be a quarter, but sort of a skewed one. Q2 is traditionally Apr, May, June. So we could get back on a traditional schedule if we covered June plus whatever seems useful from April and May in our Q2 report. |
I just made an issue for a Q2 report: April, May, June. #850 |
Thanks. |
Much like #759 last time. Guides: let us know when you're done for this pay period.
As to reporting: @deannald and I lean toward quarterly reporting.
Legal
Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.
The text was updated successfully, but these errors were encountered: