You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the WG App Development, we are currently working on our first deliverable, but we also continuously run into ideas for future initiatives.
I suggest to create a new GitHub issue here, with a high-level description about the deliverable/project. Using GitHub would give us a nice way to start a conversation around the proposal, refine the requirements and desired outcome, and track the overall status (even though part of the work will be done elsewhere in Zoom calls, GDoc, and Slack).
We can use the "wg-appdev" label to mark all GitHub issues related to our WG. Also, for easy read, we might also include the "[AppDev]" prefix in each issue title as well.
The text was updated successfully, but these errors were encountered:
+100 : Keeping track and follow-up in a structured way via GH issues is imho the perfect approach.
Would be also great to have them in a dedicated GH project which would help us, but also increase visibility to interested parties on what is discussed and what is worked on.
In the WG App Development, we are currently working on our first deliverable, but we also continuously run into ideas for future initiatives.
I suggest to create a new GitHub issue here, with a high-level description about the deliverable/project. Using GitHub would give us a nice way to start a conversation around the proposal, refine the requirements and desired outcome, and track the overall status (even though part of the work will be done elsewhere in Zoom calls, GDoc, and Slack).
We can use the "wg-appdev" label to mark all GitHub issues related to our WG. Also, for easy read, we might also include the "[AppDev]" prefix in each issue title as well.
The text was updated successfully, but these errors were encountered: