@grnsft/if 0.1.0 → 0.1.2

package/.github/ISSUE_TEMPLATE/agenda.md

@@ -1,17 +1,18 @@
 ---
 name: Agenda
-about: The standard agenda template for carbon ql
+about: The standard agenda template for Impact Framework
 title: "GSF IEF Meeting Agenda yyyy-mm-dd"
 labels: agenda
 assignees: ''
 
 ---
 
-Time 11:30am (GMT) / 4:00pm (IST) - See the time in your [timezone](https://everytimezone.com/s/e7e219dd)
+Time 10:30am (GMT) / 4:00pm (IST) - See the time in your [timezone](https://everytimezone.com/s/e7e219dd)
 
 - Lead – @srini1978 (Microsoft)
 - Co-Lead @navveenb (Accenture)
-- PM – @jawache (GSF)
+- Co-Lead – @jawache (GSF)
+- PM - @jmcook1186 (GSF)
 
 ## Antitrust Policy
 Joint Development Foundation meetings may involve participation by industry competitors, and it is the intention of the Joint Development Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

package/.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,32 @@
+Issue tracker is **ONLY** used for reporting bugs.
+
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- Tell us what should happen -->
+
+## Actual Behavior
+<!--- Tell us what happens instead of the expected behavior -->
+
+## Ideas for Solution
+<!--- Not required, but suggest a fix/reason for the bug if possible -->
+
+## Steps to Reproduce
+<!--- Provide a link to a live example, or a set of specific instructions to -->
+<!--- reproduce the bug. Include code, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context (Environment)
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Detailed Description
+<!--- Provide a detailed description of the change or addition you are proposing -->
+
+## Possible Implementation
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->

package/.github/ISSUE_TEMPLATE/dev-ticket.md

@@ -0,0 +1,44 @@
+---
+name: Dev-ticket
+about: General developer ticket 
+title: "Dev ticket - "
+labels: dev-ticket
+assignees: ''
+---
+
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Story
+<!--- Describe the benefits of this change, ideally in the following format: -->
+<!--- As a < type of user >, I want < some goal > so that < some reason >. -->
+
+## Rationale
+<!--- Provide the relevant background information to udnerstand why this change is needed -->
+<!--- This is where you can provide more details thathelp the reader understand why you want to make this change -->
+
+## Implementation details
+<!--- Explain the steps you will take to implement this change. If you do not have specific steps yet, write your implementation ideas or outline general approach -->
+
+## Priority
+<!--- How urgent is this issue, and why? -->
+<!--- Explain in writing or give a numerical value from 1 (nice-to-have) to 5 (critical) -->
+
+## Scope
+<!--- Which parts of the project/codebase does this affect? -->
+<!--- What are the possibel downstream impacts or side-effects of this change?? -->
+
+## Size
+<!--- How long do you expect this to take? -->
+<!--- How many people/person-hours are required? -->
+
+## What does "done" look like?
+<!--- Explain what needs to happen in order for this to be considered complete -->
+
+## Does this require updaes to documentation or other materials??
+<!--- Are there documentation, website or other media changes required after this change is implemented?. -->
+
+## What testing is required?
+<!--- Describe what tests are required to ensure this change has been delivered as expected -->
+
+## Is this a known/expected update?
+<!--- Has this been discussed with the core team or in a discussion forum? Provide links if possible. -->

package/.github/ISSUE_TEMPLATE/sprint-planning.md

@@ -0,0 +1,39 @@
+---
+name: Sprint planning
+about: The standard template for IF sprint planning
+title: "GSF IEF Sprint planning yyyy-mm-dd"
+labels: sprint planning
+assignees: ''
+
+---
+
+Time 11:00am - 12:00pm (GMT) every other Monday
+
+## Roll Call
+- [ ] 
+Please add 'Attended' to this issue during the meeting to denote attendance.
+
+## Backlog audit
+- [ ] 
+What tickets are on the backlog, blocked or still in progress?
+
+## Prioritization
+- [ ] 
+What are the most urgent tickets that should be worked on this sprint, and why?
+
+## Readiness check
+- [ ] 
+Are the issues `READY`? Do the tickets conform to our dev-ticket template, and do they contain sufficient information to get started?
+Are the issues sized? How much person-power do we have available in the coming sprint?
+Is there a clear and specific definition of done for each issue?
+
+## Assignment
+- [ ] 
+Who will work on which issue? What are the deadlines? 
+
+## Support
+- [ ] 
+What opportunities are there to raise concerns, resize, course correct, ask for support during the coming sprint?
+
+### Discussions and AOB
+- [ ] 

package/.github/ISSUE_TEMPLATE/sprint-retro.md

@@ -0,0 +1,41 @@
+
+---
+name: Sprint retro
+about: The standard template for IF sprint retrospectives
+title: "GSF IEF Sprint retro yyyy-mm-dd"
+labels: sprint retro
+assignees: ''
+
+---
+
+Time 11:00am - 12:00pm (GMT) every other Friday
+
+## Roll Call
+- [ ] 
+Please add 'Attended' to this issue during the meeting to denote attendance.
+
+## What went well?
+- [ ] 
+What did we ship, what progress did we make, what are we proud of?
+
+## What unexpected issues arose?
+- [ ] 
+What issues, delays or otherwise unexpected events did we encounter this week that caused us to diverge from our plan?
+
+## What can be improved?
+- [ ] 
+What did we identify as areas for improvement? Any process changes required? Any reflections that can inform how we operate in the next sprint?
+
+## Board
+- [ ] 
+Check the board to see what tickets can be closed out or moved to a new column. Any details need adding to tickets?
+
+## Support
+- [ ] 
+Any concerns, resizing or course correcting required? Any other support needed arising from the recent sprint?
+
+### Discussions and AOB
+- [ ] 
+
+### Actions
+- [ ]