-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TWE: Revise Research: Research Plan Template #533
Comments
@jinyan0425 Would you please update the
Let me know if you have any questions. Thank you! |
Current draft of Research Plan Issue TemplateCurrent draft of Research Plan Issue Template
Dependencies
OverviewWe need to create a Research Plan for [NAME OF RESEARCH PLAN] so that [RESEARCH GOAL(S)]. Action Items
Resources
|
Revised Research Plan Issue Template from the Guides TeamRevised Research Plan Issue Template from the Guides Team
Dependencies
OverviewWe need to create a Research Plan for [NAME OF RESEARCH PLAN] so that [RESEARCH GOAL(S)]. Action Items
Resources
|
Draft of template issue for Creating Research Plan Templatename: Research: Creating Research Plan Instructions for creating this issueThe person who creates this issue should use links in the section "Resources for creating this issue" (i.e., 1.01, 1.02, etc.) to customize this issue.
OverviewWe need to create the RP[Replace 000]’s Research Plan doc using the research plan template so we can keep documentations consistent and up-to-date. During these tasks you will be asked to add link to the Resources/Instructions section, and that section is at the bottom of this issue (go view it now). Customize Resource Links
Create the Research Plan
Resources/InstructionsResources for creating this issue1.01 Wiki: Research Output Overview Resources gathered during the completion of this issue2.01 [Wiki: Research Plan [Replace 000]] |
@pandanista Ying, I created the draft based on the instructions and the format of Two minor questions:
Also please let me know if there is any issue with this draft. Thank you! |
Thank you for working on this issue, @jinyan0425. To answer the two questions above:
|
|
This comment was marked as resolved.
This comment was marked as resolved.
|
|
Hi Ying, Thanks! @pandanista
|
|
These are RPs with both external and internal versions on RP wiki:
|
|
@jinyan0425 I took another look at the template, and I believe the customize the issue setting part is already included. So I am gonna hide that comment. |
Thank you. |
@pandanista See my answers below each of your questions
A: We always include an external research plan for all research plans that involve user interview and surveys
A: YES
A: Because at the time the research plan folders were private (you have to be a member to access) and we don't provide access on a document by document basis, so we put all public facing documents in a folder that is open to the public and that way, any document added is automatically public |
@pandanista Ying, I updated the template based on our discussion. I removed the action items about the external-facing RP and finished the part about updating the WIKI page. Please let me know if you have any questions or suggestions. |
It looks good to me. We will review with product and will let you know if we have any questions. Thank you, @jinyan0425 |
The template has been updated in the repo |
Overview
We need to update the Research Plan issue template so it has the same formatting as the most recent templates we have made.
Action Items
We need to create a template issue for a Research Plan, so that we can create a Research Plan Template, when we are ready and maintain consistency with the org (across projects) and the guides project.
Action Items
Ready for Research Lead
labelResources/Instructions
1.01
TWE Research: Research Plan Issue Template, new issuereplaced by 1.041.02 Issue templates in the code
1.03 TWE Research: Research Plan Issue Template, file
1.04 Issue: Research: Creating Research Plan Template
1.05 New template file for Creating Research plan
The text was updated successfully, but these errors were encountered: