Changes for page Proposal

Last modified by Alina Luchian on 2019/09/11

<
From version < 2.1 >
edited by Clément Aubin
on 2019/09/05
To version < 3.1 >
edited by Alina Luchian
on 2019/09/11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.caubin
1 +XWiki.aluchian
Content
... ... @@ -1,17 +1,25 @@
1 -This year, the XWiki community along with several other open source projects would like to organize a developer room around the theme of collaboration software and collaborative uses of Open Source software.
1 +==Knowledge is power, so it should be shared!==
2 2  
3 +Inspired by this, the XWiki community along with several other Open Source projects would like to organize a developer room to explore the theme of "Collaboration Software and Collaborative Uses of Open Source Software”, at FOSDEM 2020.
4 +Considering last year's devroom success https://archive.fosdem.org/2019/schedule/track/collaborative_information_and_content_management_applications/, with most talks having the room fully packed and never less than half full, we estimate that the session will be well attended and appreciated.
3 3  
4 -This room is backed up by the following projects (in alphabetical order):
6 +===This room is backed up by the following projects (in alphabetical order):===
5 5  
6 -* Cryptpad (represented by Ludovic Dubost)
7 -* Nextcloud (represented by Jos Poortvliet)
8 -* Tiki (represented by Jean-Marc Libs)
9 -* XWiki (represented by Clément Aubin)
8 +* Cryptpad - represented by Ludovic Dubost
9 +* Nextcloud - represented by Jos Poortvliet
10 +* Tiki - represented by Jean-Marc Libs
11 +* XWiki - represented by Clément Aubin
10 10  
11 -== Talks and presentations ==
13 +===Why does it fit FOSDEM?===
12 12  
13 -Talks performed in this room could deal with the specifics of a project in term of ecosystem (plug-ins, extensions, connectors, …), in term of distribution (i.e. : how the application is distributed to be used by most people) or explain how the project responds to use cases related to the theme of the room. Here is a list of potential subjects that could be used :
15 +* Free Software contributors are given an opportunity to understand and participate to collaborative software projects
16 +* The challenges can be explained to a very technical audience able to provide suggestions and ideas
17 +* Projects sharing common goals would get an opportunity to meet and start collaborating
14 14  
19 +
20 +==Talks and presentations==
21 +
22 +Talks performed in this room could deal with the specifics of a project in term of ecosystem (plug-ins, extensions, connectors, …), in term of distribution (i.e.: how the application is distributed to be used by most people) or explain how the project responds to use cases related to the theme of the room. Here is a list of potential subjects that could be used:
15 15  * New projects presentation
16 16  * Self-hosted platforms
17 17  * Secure collaboration
... ... @@ -21,14 +21,18 @@
21 21  * Protocols for collaboration
22 22  * …
23 23  
24 -== CFP process ==
32 +==CFP process==
25 25  
26 26  If this developer room proposal gets accepted, we will be using the following process for our call for participation:
35 +* **Before October 16th**: A page will be created on www.xwiki.org allowing anyone to register to the developer room;
36 +* **December 9th, 23.59 UTC**: End of the call for participation, to leave 5 days to review the calls for participation and prepare the schedule of the room;
37 +* **December 10th to December 15th**: Projects backing up the developer room get to agree on a schedule;
38 +* **December 15th (or before, if time allows)**: the full schedule of the room is published.
27 27  
28 -* Before October 16th : A page will be created on www.xwiki.org allowing anyone to register to the developer room
29 -* The call for participation will end on December 9th; 23.59 UTC to leave 5 days to review the calls for participation and prepare the schedule of the room
30 -* From December 10th to December 15th, projects backing up the developer room get to agree on a schedule
31 -* On December 15th (or before, if time permits), the full schedule of the room is published
32 32  
41 +==Special requirements:==
42 +
43 +Last year devroom (UD2.119) fitted the crowd quite nicely but we had to refuse people because the room was full on multiple occasions. A bigger room would resolve that problem. Even more, due to a high volume of submissions and limited time, we had to turn down talks & presentations. This could be easily solved with more time reserved.
44 +Our preference is for 6 hours or a full day, on Saturday.
45 +
33 33  Please do not hesitate to get back to us if you need more information regarding our application.
34 -Thanking you,

Get Connected