-
Notifications
You must be signed in to change notification settings - Fork 2
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
😴Create Sub-working Groups - what can we create? #120
Comments
Documentation Sub-working Group is #119.
|
@hfu do you have a suggested method to sign-up volunteers for working groups? Or should we volunteer using the GitHub issues threads? |
@albertkun I do not still have an idea about signing-up volunteers. Yes, use of GitHub would be a default method because we are relatively successful in using GitHub. By the way we have tested Matrix / Element (instead of Discord or Slack) recently, but I was not so successful in facilitating the use of such a chat platform. I am considering what subgroups can we have. I will be back here with my suggestion! |
Sub-working Groups - a suggested listLeadership and StrategyI do not think we do not need it for the time being. We are small, and we can openly work on leadership and strategy issues. We already have a chat group for 'Objective Owners'. This chat group can be considered as a Leadership and Strategy SWG. DocumentationLed by @albertkun. See #119. OperationsWe already have 'UN Operations' and 'GSI Operations' Objectives. Applications / Digital Making / Capacity BuildingCore, UNVT Portable, Smart Campus, etc. Adopt Geodata / Smart Maps Bazaar / Data Specifications & Policy studyThis would be an open data oriented group. My take
|
@hfu Oh! I tried using Matrix/Element last month! I like it! What issues did you run into? I tested video calling on it on both Desktop and Android phone and it worked well! |
@albertkun Thanks for the interest. The issue was lack of active participation there on Matrix. Let's discuss the issue of chat / microblog platform at #130. |
OK, sounds good! |
Let's say we start from Documentation Sub-working Group and leave others as is. |
As suggested in #92.
The text was updated successfully, but these errors were encountered: