I am re-posting my reply to a question @frankchen07 asked me here as I think you may be curious to know these details:
From @frankchen07:
heyo, also wanted to get a pulse on what else you were working on - I saw your townsquare post. what's the cadence for check ins too - I don't want to micro-manage, but definitely don't want to let things slip!
My reply -sorry for the length:
No problem. I will probably copy paste what I am about to write later on into Townsquare or under my Grant.
Since I did not expect to be in the current position I am in, I have not yet considered fully how I will handle reporting or check-ins. Ideally, since most everything is already public, I would not need to report much or do check-ins, rather I would simply need to aggregate all the public data as to my progress or status and put into a single place or into a simple representation.
I probably will need to script up a walidmujahid-bot or something the longer I contribute here :-D
I will need to think more on that and get back to you.
However, for now, since I am working from Github Issues and Github is central to the workflow, I will make a point to post weekly status updates under each of the active issues I am working on at least once on minimum.
Active being I either have a draft PR open, a WIP PR, or I am working on getting one or both PR types open. My updates may be more frequent than once, but I just mentioning my minimum.
I will not really bother doing weekly status updates under the issue if the PR is has been waiting for maintainer review for a while or is just taking a while to merged into master for some reason.
I do keep my open PRs waiting to be merged up to date with current upstream HEAD and I already mention under the PRs whether local testing on updates passes or if I need to update my code. Perhaps I should also post those under the relevant issues as well?
Now, I am not sure if this was included in the scope of your question, but I will go into it anyway.
Currently, my open task list includes the following -based on priority. And priority being defined as to the time sensitivity self-imposed it be or not:
- Hackathon Project Page: gitcoinco/web#6211 (this one I am currently working on around this time and can be seen in my current townsquare video call)
- Status Updates Input Form Autocomplete Should Be Able To Be Keyed Up And Down With My Keyboard: https://gitcoin.co/issue/gitcoinco/web/6191/4096 (this is actually the most time-sensitive of my tasks and I will be needing to rework based on feedback by @octavioamu on deprecating jQueryUI in the codebase and I am waiting on some further answers from him to some questions)
- New Comment Email is Busted: gitcoinco/web#6147 (I have not started work on this yet)
- If user cancels metamask transaction, a tip comment is still generated: gitcoinco/web#6005 (This technically was an open PR waiting for review, but I moved it back to WIP PR stage due to recent updates not passing local tests. I suspect some, if not all of the issues stems from my solution to fix another issue -changes in migration files- and @owocki provided feedback on another issue that came up, I actually hope to get this PR open soon)
- Request: on the 'Hackathons' Tab -- I'd love if 'Start Work' included the work plan in the Town Square and 'Submit Work' included the link to the submitted work: https://gitcoin.co/townsquare?tab=activity:156395 (I have not started work on this yet)**
- Simplified user area in Nav Bar: gitcoinco/web#6066 (I have not started work on this yet, and I will probably need to check on the status of the issue before I do start work)
- As a Gitcoin contributor, I have fat fingers, and I comment with typos, and want the ability to edit my townsquare comment: gitcoinco/web#6010 (This issue is technically done on my end. I am just waiting for further maintainer review which is taking quite a while. I suspect it is because it might be on the wrong section in the review board making it seem they are waiting on the contributor, me)
- Town Square - As a user, I want an easy way to turn an interesting post into a GitHub issue: gitcoinco/web#6009 (I have a draft PR open for this and I need to work on this after the first couple or three tasks first mentioned above)