Date: Fri, 29 Mar 2024 15:14:27 +0000 (UTC)
Message-ID: <1113128244.1433.1711725267087@65012a6a44dd>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_1432_602299937.1711725267087"
------=_Part_1432_602299937.1711725267087
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
LF Energy maintains a number of tools to enable collaboration amon=
gst community participants. To help navigate these tools, this document pro=
vides a brief outline of how to use them and best practices.
LF Energy hosts a Slack organization, which can be joined using th=
e Slack Invite Link. Slack serves as the=
main communication platform for the LF Energy community outside of the mai=
ling lists. It=E2=80=99s important that conversations stays on topic in eac=
h channel, and that everyone abides by the Code of Conduct. There are thousands of members=
who should all expect to have a positive experience.
Chat is searchable and public. Do not make comments that you would=
not say on a video recording or in another public space. Please be courteo=
us to others.
Slack also maintains some best =
practice etiquette, which has some great basic usage tips =
and other recommendations to best collaborate and communicate with others.<=
/span>
Please do not engage in proprietary company specific conversations=
in the LF Energy Slack instance. This workspace is meant for conversations=
related to LF Energy topics and community. Proprietary conversations shoul=
d occur in your company Slack and/or communication platforms. As with all c=
ommunication, please be mindful of appropriateness, professionalism, and ap=
plicability to the LF Energy community.
Some channels have specific rules or guidelines. If they do, they =
will be listed in the purpose or pinned docs of that channel.
If you encounter an issue using the LF Energy Slack, please contac=
t the LF Energy Program Manager.
To add a channel, please submit a request.
Some general guidelines on new channels...
- Channels should be dedicated to sub-projects, community topics, o=
r related LF Energy programs/projects.
- Linking to resources will speed in the validation and processing =
of the channel creation request.
- Channels are NOT:
- Company specific
- Private channels with the exception of: code of conduct matters, =
mentoring, security/vulnerabilities, github management, or steering committ=
ee.
- Special accommodations will be made where necessary.
LF Energy maintains a number of mailing lists for the foundation i=
tself, it's members, and the community at large. These mailing lists are ho=
sted at groups.io and managed by the Linux Fou=
ndation staff and LF Energy community leadership.
The primary mailing list for all technical community discussion is=
tac@lists.lfenergy.org. Each hosted =
project and working group has it's own mailing list as well.
By default, TAC voting members serve as the moderator for discussi=
ons in tac@lists.lfenergy.org, and ea=
ch hosted project's TSC will serve as moderator for it's mailing lists. Mod=
eration privileges can be extended to others upon a vote by the TAC or resp=
ective TSC as applicable.
Being a moderator is as much a privilege as it is a duty. As part =
of volunteering to become a moderator you are now a representative of the L=
F Energy community, and it is your responsibility to remain aware of your c=
ontributions in this space. These responsibilities apply to all official LF=
Energy channels.
Moderators MUST:
- Take action as specified by these Moderator Guidelines.
- You are empowered to take immediate action when there is a violat=
ion. You do not need to wait for review or approval if an egregious violati=
on has occurred. Make a judgement call based on our Code of Conduct and Val=
ues (see below).
- Removing a bad actor or content from the medium is required, do N=
OT let it sit there.
- Abide by the documented tasks and actions required of moderators.=
- Ensure that the Code o=
f Conduct is in effect on all official LF Energy channels.=
- Make yourself generally available during working hours in your ti=
me zone for moderation. This can be handled as a group so that there is eno=
ugh coverage of people to allow for absences/travel.
- Take care of spam as soon as possible, which may mean taking acti=
on by removing a member from that resource.
- Foster a safe and productive environment by being aware of potent=
ial multiple cultural differences between community members.
- Understand that you might be contacted by moderators, community m=
anagers, and other users via private email or a direct message.
- Keep up with software/platform changes on the property they are r=
esponsible for. This might include new UI changes, new features, or other s=
oftware changes. Moderators are encouraged to meet regularly to train thems=
elves how to be proficient with the platform.
- Report violations of the Code of Conduct to operations@lfe=
nergy.org.
Moderators SHOULD:
- Exercise compassion and empathy when communicating and collaborat=
ing with other community members.
- Understand the difference between a user abusing the resource or =
just having difficulty expressing comments and questions in English.=
- Be an example and role model to others in the community. In many =
cases, moderators are some of the first people new contributors will intera=
ct with.
- Remember to check and recognize if you need take a break when you=
become frustrated or find yourself in a heated debate.
- Help your colleagues if you recognize them in one of the stages o=
f burnout.
- Be helpful and have fun!
- Review your mailing list subscriptions regularly, and either chan=
ge the delivery mechanism ( such as switching from individual emails to dai=
ly digests ) as it makes sense to keep the signal-to-noise level reasonable=
for you.
- Keep your comments and conversation on topic
- Recognize with a global community and other obligations, replies =
aren't instantaneous.
- Refrain from cross-posting as a way to get a larger audience to y=
our post.
- Be sure to contact the list moderators if there are any Code of Conduct concerns=
.
You can stay subscribed to the meetings of the projects and commit=
tees of LF Energy by subscribing to the coordinating mailing list. Each mai=
ling list has a calendar which you can subscribe to with your calendar clie=
nt of choice.
By default, the following permissions apply to calendars:=
p>
- Voting TAC members can manage the LF Energy-tac calendar.
- TSC project chairpersons can manage their respective project cale=
ndars.
- LF Staff can manage any calendar event
If you are running into an issue with calendar events, please submit a request and the LF Staff can =
help.
By default, any TSC or TAC chairperson has the ability to schedule=
community meetings on the LF Energy-tac c=
alendar or a project specific calendar, respectively.
- Visit the calendar of the needed mailing list
- Scroll to the bottom of the group calendar, select Add Event.
- Fill in the fields for:
- Event Name, enter descriptive name for your meeting.
- Start and End Times, enter the details noting the Timezone, selec=
ting All Day if applicable.
- Event Repeats, select if applicable, and enter the additional det=
ails.
- Location
- Organizer Email, this will be the sub-group mail list
- Organizer Phone, is optional.
- Event Color is optional
- Description, this will be the relevant meeting details. It is rec=
ommend to enter the following:
- Summary of the meeting purpose
- Meeting lead name
- Wiki page for reference
- Full Zoom details
- Request RSVP, select this item to ensure that guests can provide =
a response to your meeting (Will Attend, Will Not Attend, and Not Sure). Th=
is will also allow you to see the responses within the meeting invite.
- Max Number of Attendees, can be left at 0, which means unlimited.=
- Additional Information Requested From Attendees, is optional (suc=
h as in person attendance vs via Zoom), this will be asked on the RSVP page=
.
- Note To Send Attendees, is optional (such as a thank you for the =
RSVP and a pointer to a wiki page for more information).
- Reminders, set this up for automatic email reminders to be sent t=
o the applicable mail list regarding the meetings.
- A 1 day before and 10 minutes before reminder is suggested as a s=
tandard, leave as Send As Normal Message.
- Notifications, you must select Send Invite To Group in order for =
the invite to be sent to the applicable sub-group.
- Leave Send Notice To Group When Event Happens unchecked as it is =
not a necessary notification in most cases.
- View How-to Video
- Visit the calendar of the needed mailing list
- Click on the event you are updating and select Edit Event and mak=
e the applicable changes.
- Select Update Event to save the changes and ensure you choose the=
update to reflect on Only This Event or All Meetings as applicable.=
The meeting update will be reflected in the meeting subscription w=
ith the next automatic update.
- Visit the calendar of the needed mailing list
- Click on the event you are updating and select Edit Event, scroll=
to the bottom of the Event and click on Delete Event.
- You'll need to select either Only This Event or All Meetings as a=
pplicable here as well.
The meeting update will be reflected in the meeting subscription w=
ith the next automatic update.
To help individuals to not be inundated with calendar overload, tr=
y to follow these guidelines:
- The LF Energy-tac calendar should only be used for TAC meetings, meetings or events for th=
e full LF Energy community, and kickoff meetings of new projects.
- Specific project meetings should be on your project's calendar. A=
ll meeting should be on the primary discussion, dev, or user calendar unles=
s it's a specific closed meeting to discuss a sensitive topic.
- Avoid making any meeting invite changes ( including cancellations=
or reschedulings ) less that 24 hours in advance, as many calendaring clie=
nts do not update immediately. It's also best practice to email that calend=
ar's respective mailing list to inform the group of the cancellation.
- If you are rescheduling a meeting, cancel the previous one and is=
sue a new meeting instead of doing a reschedule. Some calendaring clients d=
on't do well with meeting invite changes.
Instructions for subscribing to an iCal calendar for popular calen=
daring tools:
- Do ensure that any meeting invites have clearly identified web co=
nference or location details.
- Unless the meeting is only in person, always provide a web confer=
ence for those who can't attend in person
- Be sure the description of the meeting has an agenda or a link to=
the agenda of the meeting.
- Since calendaring clients can not always be good at managing chan=
ges...
- If a meeting is to be rescheduled, delete the original meeting in=
vite and add a new one with a title denoting it being rescheduled.=
li>
- Avoid cancelling meetings within 24 hours of the meeting=
li>
- For changes/cancellations, email the invitees as well to inform t=
hem of the cancellation
- When provisioning a new series of recurring meetings, instruct in=
vites to remove old entries manually.
- Courtesy Email, as a meeting lead it is a best practice to email =
the applicable sub-group with a note about any new meetings available, any =
meeting changes, or meeting cancellations.
------=_Part_1432_602299937.1711725267087--