add gpw etherpad, and a bit of dir structure

README.md

@@ -2,6 +2,25 @@
 
 Another attempt to collect a set of slides suitable to be used in Intro Talks during or before a Perl conference.
 
+## I want to help!
+
+We have set up a few issues, so you can grab one of them and "fix" it (currently this mostly means some research, or even just creating more issues..)
+
+Please feel free to submit new issues.
+
+If you found a nice slidedeck or authored one yourself, either send us a pull request or join to group to get direct access (a commit bit!)
+
+## Repo structure
+
+I prepared a few directories for a bit of structure:
+
+* meta: documents, notes etc about this group and process
+* talks: for regular talks (20 - 45 minutes)
+* tutorials: for 2 - 4h long tutorials on a topic
+* workshops: for interactive workshops with user participation
+
+In each of those dirs, we should set up one directory that corresponds to a particular talk topic; within each of those there are one or more slide decks as well as a README file describing when each slide deck originated and the different times the corresponding talk has been delivered.
+
 ## Background
 
 * https://domm.plix.at/perl/2017_08_how_to_make_perl_conferences_beginner_friendly.html
@@ -15,6 +34,3 @@ Another attempt to collect a set of slides suitable to be used in Intro Talks du
 Until this team agrees to a more specific Code of Conduct, the [Debian Code of Conduct](https://www.debian.org/code_of_conduct) and the [Debian Mailing Lists Code of Conduct](https://www.debian.org/MailingLists/#codeofconduct). We assume you are able to transpile the mailing list specifica to git-based collaboration.
 
 
-
-
-

meta/gpw_etherpad_20200305.md

@@ -0,0 +1,66 @@
+#Meta-Intro:
+
+\url{https://domm.plix.at/perl/2020\_03\_perl\_intro\_curriculum.html}
+\url{https://act.yapc.eu/gpw2020/talk/7707}
+
+#Perl Intro Talks
+
+Do you think this idea even makes sense?
+Consensus: yes, but it’s difficult
+
+Will this help attract newbies?
+Consensus: It will help the newbies but it’s very hard to attract them.
+
+Should an Intro-Block happen on the 0th day of the conference? Or during the proper conference?
+
+
+   * domm: I think 6 talks each 30 minutes would be a good format
+   * or have a workshop on the 0th day: \url{https://twitter.com/stommepoes/status/1235497728370589696}
+Gefahren:
+
+   * "Perl-Kindergarten" evtl. nicht gutes Marketing
+Erfahrungen von früheren/anderen Konferenzen/Fachgebieten:
+
+   * im Bibliothekbereich (ELAG, SWIB) gibt es Pre-Conf-Workshops, praktische WS, WS extra Buchbar (auch ohne Conf)
+   * London Perl Workshop: Beginner-Talks sehr schlecht besucht
+   * Raku-Workshop beim GPW2020: sehr guter Einstieg, aber keine Neulinge davon angezogen
+Offene Fragen:
+
+   * Dauer des Events im Auge behalten.
+   * Zielgruppe / stakeholder, "zertifikat" ?Teilnahmebestätigung?
+   * Gezielt Firmen ansprechen die Perl verwenden – Auf welchem Weg? Welche? Mit welchen Argumenten?
+   * marketing um neulinge auf conf zu bringen
+   * Ziel und Zielgruppe definieren
+Konkrete Ideen:
+
+   * Frühzeitig ankündigen
+   * Hackathon?
+   * alte vorträge durchforsten und recyclen; iterativ
+   * Zertifikat/Urkunde für Workshop-Teilnehmer
+   * Schwerpunktthemen "automatisierung/cloud/KI ... mit Perl"
+   * Andere Konferenzen besuchen und dort Beginner-Talks anbieten (nicht nur Perl, sondern konkretes kleines Projekt)
+
+#Curriculum ideas
+
+What topics should be in a curriclum?
+
+What things would newbies want to know?
+
+What do we as Perl devs want them to kow?
+
+Intro Workshop vs Talks
+
+
+
+
+#Perl and / or Raku
+
+Do we need / want to multiply the efforts for Perl AND Raku?
+
+
+#I want to help:
+(please add your name and some way to contact you)    
+
+
+   * domm@plix.at
+   * Daniel Böhmer <post@daniel-boehmer.de>

talks/README.md

@@ -0,0 +1,4 @@
+# Talks
+
+for regular talks (20 - 45 minutes)
+

tutorials/README.md

@@ -0,0 +1,5 @@
+# Talks
+
+for tutorials (long talks, 1.5h - 4h)
+
+

workshops/README.md

@@ -0,0 +1,4 @@
+# Talks
+
+for interactive workshops
+