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
1- Collaboration with PHUSE (in response to Greg's mail): Jeremy and Jim will get back to Greg. PHUSE and ISG might have different strategies so far, but ISG is open for information sharing and is open for future collaboration if we share the same goal.
2- Patent question (in response to Scott's question): based on Jeremy's conversations with multiple lawyers and Mengchun's consultation with another lawyer, it seems like there is no major concern so far. People can still put what we have developed into commercial product, but the working group will still able to use the open source deliverables that we have developed, and will be able to continue to work on this. Since there is no major concerns from the ISG team, Mengchun will get back to scott as a standalone Q&A
3- People management and retention. The core team talked about ways to motivate team members and to reflect how we can do better along the way. One area that we can do better is to provide timely feedback to team members of their work, or having a senior person paired with a junior person, or even just peer-peer pair so there is an active mechanism for providing feedback. Core team member will think about how we can do better and how to provide feedback as a standing item.
4- Liaison between ISG and BRATS: It is not clear at this point what is needed by BRATS team, a co-lead who understand ISG/technical aspects but also to drive BRATS, or just a liaison person making sure ISG and BRATS are well aligned? Jim and Mengchun will clarify with Leadership council, also to figure out " Does BRATS have any technical contributors?" " What is their roadmap?" At the meanwhile, Xiao will figure out what is the role of Tony Rossini in BRATS. If he is already there, he might be a perfect person to serve this role (by inviting him to ISG). Core team members agreed that having Xiao as the liaison person might stretch Xiao too thin, which is essentially not good for ISG nor the entire working group.
5- Do we need a launch readiness team for ISG? For many aspects as described in a potential launch readiness team, it seems those are falling into the communication category (for example, YouTube Channel, LinkedIn, etc.). Team can ask members if anyone is good at launch readiness and wanted to be a member of this effort; also team can check with OCT if they are willing to be involved. Jim and Mengchun will bring this topic up at the leadership council as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@jwildfire @xni7 @JimBuchanan @mli1
1- Collaboration with PHUSE (in response to Greg's mail): Jeremy and Jim will get back to Greg. PHUSE and ISG might have different strategies so far, but ISG is open for information sharing and is open for future collaboration if we share the same goal.
2- Patent question (in response to Scott's question): based on Jeremy's conversations with multiple lawyers and Mengchun's consultation with another lawyer, it seems like there is no major concern so far. People can still put what we have developed into commercial product, but the working group will still able to use the open source deliverables that we have developed, and will be able to continue to work on this. Since there is no major concerns from the ISG team, Mengchun will get back to scott as a standalone Q&A
3- People management and retention. The core team talked about ways to motivate team members and to reflect how we can do better along the way. One area that we can do better is to provide timely feedback to team members of their work, or having a senior person paired with a junior person, or even just peer-peer pair so there is an active mechanism for providing feedback. Core team member will think about how we can do better and how to provide feedback as a standing item.
4- Liaison between ISG and BRATS: It is not clear at this point what is needed by BRATS team, a co-lead who understand ISG/technical aspects but also to drive BRATS, or just a liaison person making sure ISG and BRATS are well aligned? Jim and Mengchun will clarify with Leadership council, also to figure out " Does BRATS have any technical contributors?" " What is their roadmap?" At the meanwhile, Xiao will figure out what is the role of Tony Rossini in BRATS. If he is already there, he might be a perfect person to serve this role (by inviting him to ISG). Core team members agreed that having Xiao as the liaison person might stretch Xiao too thin, which is essentially not good for ISG nor the entire working group.
5- Do we need a launch readiness team for ISG? For many aspects as described in a potential launch readiness team, it seems those are falling into the communication category (for example, YouTube Channel, LinkedIn, etc.). Team can ask members if anyone is good at launch readiness and wanted to be a member of this effort; also team can check with OCT if they are willing to be involved. Jim and Mengchun will bring this topic up at the leadership council as well.
Beta Was this translation helpful? Give feedback.
All reactions