-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Based on the format used for OSEP and LFSCS Signed-off-by: Paul Albertella <[email protected]>
- Loading branch information
1 parent
fc88501
commit 157918d
Showing
1 changed file
with
39 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# New working group proposal template | ||
|
||
New working groups should be proposed on the ELISA Technical Community | ||
[mailing list](https://lists.elisa.tech/g/devel) using the following template: | ||
|
||
Proposed working group name | ||
--------------------------- | ||
|
||
*Name of proposed working group* | ||
|
||
Proposed WG chair | ||
----------------- | ||
|
||
*Name of proposed chair* | ||
|
||
Proposed meeting schedule | ||
------------------------- | ||
|
||
*When and how often will the working group meet? Can be planned day of the week | ||
and time of call if known, or frequency (e.g. weekly, bi-weekly, monthly)* | ||
|
||
Proposed mission statement | ||
-------------------------- | ||
|
||
*What is the proposed scope of the workgroup? Will it focus on a specific aspect | ||
of the ELISA mission statement, or a specific industry sector or type of safety | ||
use case for Linux?* | ||
|
||
Planned activities | ||
------------------ | ||
|
||
*What type of activities will the working group undertake? What are the expected | ||
results of these activities and how will these be shared and managed?* | ||
|
||
Collaboration | ||
------------- | ||
|
||
*What is the expected relationship with other working groups? How will the new | ||
WG collaborate with the existing WGs, and how will this be managed?* |