While still hot off the press, questions were received about the Session Council.
The questions have been anonymized out of respect for those who asked them.
Expand the sections below for the questions and answers.
The Session Council is a way to record all issues within an entire session, from the beginning to the end of the session, and then receive the report.
Afterward, the report may be used to assist with creating or contributing to one or more Issue Council reports.
Summarized:
Issue Council: Contribute to or create 1 issue code ticket at a time.
Session Council: Create record of all issues; for use as a companion to Issue Council.
The instructions mention to skip anything that does not apply within any given session.
It is unlikely that the tester would encounter issues with most of the features or content within a single session.
However, the options are available to choose from, should there be a need to record them.
The Session Council provides most, close to all of what may be needed, and includes "encountered other issues" options so that all the bases are covered, so that any issues that are encountered can be recorded and then used later to help with contributing to Issue Council.
Perhaps think about it in a positive way rather than negative. That is not saying that the ask is particularly negative, it's simply a matter of half glass empty versus half full. To clarify, rather than go about it from the perspective of looking for a problem, consider looking at it from the perspective of having a resource that can be used to assist with another resource.
While it is very possible that within one session of Star Citizen someone may repeatedly go back and forth between that and Issue Council to submit reports, that also means that with each report the entire submission process must be started again from the beginning.
The Session Council provides a means to gather all of the issues within a single form, after which, when no longer in Star Citizen (or even while still in the PU or AC, it's up to the user), the Session Council report can be used to assist with Issue Council reports.
Essentially, it may be used to help make life a little bit easier, as when encountering multiple issues within a single session.
With changes announced in February 2024 by CIG pertaining to the nature of a nondisclosure agreement that Evocati Test Flight users adhere to, members of that group will not break their NDA by discussing those builds outside of that group.
Media files of content from those builds, such as images and videos, are still considered by CIG to be under NDA.
No media is shared through the Session Council. The tool does not have any options to upload files.
It is the users' responsibilities to maintain their NDA and remain current with any possible future changes.
Here is the announcement from CIG regarding the NDA changes:
An RSI account may be required to view that post. It has been publicly shared by CIG staff and is available immediately below.
Original post: https://i.imgur.com/3UpTNMX.png
Follow-up clarification: https://i.imgur.com/0YFdVRl.png
The bit.ly short link generator is a popular service, validated as secure for providing encrypted connections via TLS addresses, and is very helpful with using clear, concise, and short links in place of other links that may be very long or consist of randomly generated characters. The main advantage in a bit.ly link, as with short links provided by many similar services, is that it is easy to remember. Investigation into the official CIG short link "play.sc" has also revealed that that domain name is also using the bit.ly service.
It is still understandable if someone does not wish to go to a short link.
For that reason, both the short link and long link have been provided on the Session Council site and form.
The Session Council short link:
The Session Council long link via Google:
https://sites.google.com/view/sessioncouncil
Direct link to the Session Council form:
https://docs.google.com/forms/d/e/1FAIpQLSemVg71Vsi0IdBFxLzm8lXEFH2_bl2pGMYnFklvmcXmTEOGPg/viewform