diff --git a/.markdownlint-cli2.jsonc b/.markdownlint-cli2.jsonc index 197a7a2077..355e1f5b67 100644 --- a/.markdownlint-cli2.jsonc +++ b/.markdownlint-cli2.jsonc @@ -2,7 +2,7 @@ "config": { "default": true, "MD013": false, - "MD033": { "allowed_elements": ["input"] }, // only allowing input elements within md tables + "MD033": { "allowed_elements": ["li", "ul"] }, // only allowing ul, li elements for checkboxes within md tables "MD024": false, "search-replace": { "rules": [ diff --git a/community/hackathons/checklist.md b/community/hackathons/checklist.md index 7543d93a79..36e86cfedc 100644 --- a/community/hackathons/checklist.md +++ b/community/hackathons/checklist.md @@ -5,43 +5,43 @@ to the situation. ## Checklist 6 months before Hackathon -| | Date | Task | -|----------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| | | Clarify sponsorship | -| | | Clarify who is responsible for planning. Contact persons of the companies involved. These should then also be present at the hackathon. | -| | | Set a specific date. | -| | | Clarify responsibilities. | -| | | First advertising in form of advertising in meetings, LinkedIn post, mailing list or similar. | -| | | Clarify which advertising measures are required (see checklist advertising). | -| | | Determine venue. | -| | | Set the theme for the hackathon and apply it to the design. | +| | Date | Task | +| ------------------------ | ---- | --------------------------------------------------------------------------------------------------------------------------------------- | +| | | Clarify sponsorship | +| | | Clarify who is responsible for planning. Contact persons of the companies involved. These should then also be present at the hackathon. | +| | | Set a specific date. | +| | | Clarify responsibilities. | +| | | First advertising in form of advertising in meetings, LinkedIn post, mailing list or similar. | +| | | Clarify which advertising measures are required (see checklist advertising). | +| | | Determine venue. | +| | | Set the theme for the hackathon and apply it to the design. | ## Checklist advertising -| | Topic | Task | -|----------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------| -| | Social Media | Create content plan. | -| | | Which accounts/people/companies have to be mentioned as well. | -| | | Which persons must agree to a publication. | -| | | Should hashtags be used, if yes which ones. | -| | Newsletter | Create content plan with possible content and frequency. | -| | Website | Content plan: Blogposts. | -| | | Info landing page. | -| | | Registration page. | -| | | Special newsletter or just regular. | -| | Other placements | Spread the word in meetings or at other events. | -| | Media | Should be changeable, specify target audience, language, sources. | -| | Media suggestions | Video, images, PDF, texts, merch, graphics. Everything should be planned in advance precisely date, type, releases, scope, size, etc. | -| | Graphics | Set design motto. | -| | Key metrics | Should the success be tracked by key metrics, if so which ones. | +| | Topic | Task | +| ------------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------- | +| | Social Media | Create content plan. | +| | | Which accounts/people/companies have to be mentioned as well. | +| | | Which persons must agree to a publication. | +| | | Should hashtags be used, if yes which ones. | +| | Newsletter | Create content plan with possible content and frequency. | +| | Website | Content plan: Blogposts. | +| | | Info landing page. | +| | | Registration page. | +| | | Special newsletter or just regular. | +| | Other placements | Spread the word in meetings or at other events. | +| | Media | Should be changeable, specify target audience, language, sources. | +| | Media suggestions | Video, images, PDF, texts, merch, graphics. Everything should be planned in advance precisely date, type, releases, scope, size, etc. | +| | Graphics | Set design motto. | +| | Key metrics | Should the success be tracked by key metrics, if so which ones. | ## Checklist 5 months before Hackathon -| | Date | Task | -|----------------------------------------|------------|---------------------------------------------------------------------------------| -| | | Clarify if extra merch is desired and start looking for vendors. Order samples. | -| | | Discuss concrete advertising measures. | -| | | Check hotels (see checklist hotel). | +| | Date | Task | +| ------------------------ | ---- | ------------------------------------------------------------------------------- | +| | | Clarify if extra merch is desired and start looking for vendors. Order samples. | +| | | Discuss concrete advertising measures. | +| | | Check hotels (see checklist hotel). | ## Checklist hotel @@ -63,17 +63,17 @@ to the situation. ## Checklist 4 months before Hackathon -| | Date | Task | -|----------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------| -| | | Determine hotel final and make recommendation. Possibly reserve contingent if the hotel offers it. | -| | | Find the location for the evening before (see checklist for evening before location). | -| | | Start organizing venue. (See checklist rooms 1). | -| | | Roughly plan evening event (consider volume level and space available). | -| | | Promotional drumbeat. Social media, website, meetings, newsletter. | -| | | Order special merch. | -| | | Organize merch in general (see merch checklist). | -| | | Start collecting statements that need to be sent around. (Privacy statements, photo statements, data center statements, security statements). | -| | | Rough sequence of events to be able to plan more precisely at a later date. | +| | Date | Task | +| ------------------------ | ---- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| | | Determine hotel final and make recommendation. Possibly reserve contingent if the hotel offers it. | +| | | Find the location for the evening before (see checklist for evening before location). | +| | | Start organizing venue. (See checklist rooms 1). | +| | | Roughly plan evening event (consider volume level and space available). | +| | | Promotional drumbeat. Social media, website, meetings, newsletter. | +| | | Order special merch. | +| | | Organize merch in general (see merch checklist). | +| | | Start collecting statements that need to be sent around. (Privacy statements, photo statements, data center statements, security statements). | +| | | Rough sequence of events to be able to plan more precisely at a later date. | ## Checklist for evening before location @@ -110,22 +110,22 @@ to the situation. ## Checklist 3 months before Hackathon -| | Date | Task | -|----------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------| -| | | Required declarations (photo/video usage rights, data center, premises, etc.) are available as a form. Have a look if you can have | -| | | them confirmed with the registration. Otherwise as a circular email to all who register with the registration confirmation. Well | -| | | visible. For the photo/video declaration: Give the option of refusing and explain the variant with the no-photo dot. | -| | | Promote again: Website, social media, newsletter, meetings, circular email, etc.... | -| | | Make reservations for pre-evening event. | -| | | Plan evening event and reserve location / tables (see checklist evening event). | -| | | Create a provisional schedule. | -| | | Eventually invite people separately. (Special guests). | -| | | Schedule start time and arrival time. Allow enough time for everyone to arrive. | -| | | Set presentation time and end time. | -| | | Define arrival time evening event. Leave enough time to change, but also do not define too long. | -| | | Schedule a fixed cleanup time. | -| | | Plan break time. | -| | | Activate login page. | +| | Date | Task | +| ------------------------ | ---- | ---------------------------------------------------------------------------------------------------------------------------------- | +| | | Required declarations (photo/video usage rights, data center, premises, etc.) are available as a form. Have a look if you can have | +| | | them confirmed with the registration. Otherwise as a circular email to all who register with the registration confirmation. Well | +| | | visible. For the photo/video declaration: Give the option of refusing and explain the variant with the no-photo dot. | +| | | Promote again: Website, social media, newsletter, meetings, circular email, etc.... | +| | | Make reservations for pre-evening event. | +| | | Plan evening event and reserve location / tables (see checklist evening event). | +| | | Create a provisional schedule. | +| | | Eventually invite people separately. (Special guests). | +| | | Schedule start time and arrival time. Allow enough time for everyone to arrive. | +| | | Set presentation time and end time. | +| | | Define arrival time evening event. Leave enough time to change, but also do not define too long. | +| | | Schedule a fixed cleanup time. | +| | | Plan break time. | +| | | Activate login page. | ## Checklist evening event @@ -140,16 +140,16 @@ to the situation. ## Checklist 2 months before Hackathon -| | Date | Task | -|----------------------------------------|------------|-------------------------------------------------------------------------------------------------| -| | | Start collecting goals and topics. | -| | | Work out goals and topics yourself. | -| | | Check results from the checklist rooms 1 again. | -| | | Go through checklist rooms 2. | -| | | Advertising (social media, mailing list, website, blog post, newsletter, room plan video, etc). | -| | | Go through checklists again in general, was anything forgotten? | -| | | Plan food for the break. | -| | | Plan snacks / breakfast (See snacks checklist). | +| | Date | Task | +| ------------------------ | ---- | ----------------------------------------------------------------------------------------------- | +| | | Start collecting goals and topics. | +| | | Work out goals and topics yourself. | +| | | Check results from the checklist rooms 1 again. | +| | | Go through checklist rooms 2. | +| | | Advertising (social media, mailing list, website, blog post, newsletter, room plan video, etc). | +| | | Go through checklists again in general, was anything forgotten? | +| | | Plan food for the break. | +| | | Plan snacks / breakfast (See snacks checklist). | ## Snacks checklist @@ -193,71 +193,71 @@ to the situation. ## Checklist 1 month before Hackathon -| | Date | Task | -|----------------------------------------|------------|--------------------------------------------------------------------------------------------| -| | | Fix and publish the agenda. | -| | | Check the declarations once again, has every declaration been send, have any answered yet? | -| | | Check reservations, expand if necessary. | -| | | Check whether all possible special features have been observed (location etc). | -| | | Pre-order food for in-between meals and for the lunch break. | -| | | Plan drinks, type and quantity (don't forget coffee, tea, milk, sugar). | +| | Date | Task | +| ------------------------ | ---- | ------------------------------------------------------------------------------------------ | +| | | Fix and publish the agenda. | +| | | Check the declarations once again, has every declaration been send, have any answered yet? | +| | | Check reservations, expand if necessary. | +| | | Check whether all possible special features have been observed (location etc). | +| | | Pre-order food for in-between meals and for the lunch break. | +| | | Plan drinks, type and quantity (don't forget coffee, tea, milk, sugar). | ## Checklist 1 week before Hackathon -| | Date | Task | -|----------------------------------------|------------|-------------------------------------------------------------------------------------------------| -| | | Print statements and forms. | -| | | Advertise again. | -| | | Make a list for the snacks (See for inspiration checklist snacks). | -| | | Pre-order the food, if necessary, check whether the quantity still fits with the registrations. | -| | | Depending on expand. Firmly plan transport / pickup / delivery. | -| | | Create a room plan with the topics, where, when, what takes place. | -| | | Organize drinks. | -| | | Determine the time when the helpers / organizers meet. | -| | | If necessary create / organize lists and visitor cards. | +| | Date | Task | +| ------------------------ | ---- | ----------------------------------------------------------------------------------------------- | +| | | Print statements and forms. | +| | | Advertise again. | +| | | Make a list for the snacks (See for inspiration checklist snacks). | +| | | Pre-order the food, if necessary, check whether the quantity still fits with the registrations. | +| | | Depending on expand. Firmly plan transport / pickup / delivery. | +| | | Create a room plan with the topics, where, when, what takes place. | +| | | Organize drinks. | +| | | Determine the time when the helpers / organizers meet. | +| | | If necessary create / organize lists and visitor cards. | ## Checklist one day before Hackathon -| | Date | Task | -|----------------------------------------|------------|---------------------------------------------------------------| -| | | Buy snacks. | -| | | Contact food supplier again if the delivery date is suitable. | -| | | Check technology for functionality. | -| | | Send around the room plan with the topics by email. | -| | | Prepare rooms if necessary / possible. | -| | | Put drinks in the refrigerator. | -| | | Provide coffee machine. | -| | | Provide dishes. | -| | | Label rooms. | -| | | Check visitor cards and lists for completeness. | +| | Date | Task | +| ------------------------ | ---- | ------------------------------------------------------------- | +| | | Buy snacks. | +| | | Contact food supplier again if the delivery date is suitable. | +| | | Check technology for functionality. | +| | | Send around the room plan with the topics by email. | +| | | Prepare rooms if necessary / possible. | +| | | Put drinks in the refrigerator. | +| | | Provide coffee machine. | +| | | Provide dishes. | +| | | Label rooms. | +| | | Check visitor cards and lists for completeness. | ## Checklist Hackathon Day X -| | Time | Task | -|----------------------------------------|------------|-------------------------------------------------------| -| | | Place snacks on the tables in small bowls or similar. | -| | | Distribute merchandise. | -| | | Have declarations and forms ready for late deciders. | -| | | Have lists and visitor cards ready if necessary. | -| | | Check drinks in an interval. | -| | | Make coffee if necessary. | -| | | Provide tea, coffee, milk, sugar. | -| | | Provide breakfast / snacks. | -| | | Pick up lunch. | -| | | Lunch "build up" | -| | | Cleanup | -| | | Keep an eye on the process (keep times a little bit). | -| | | See if everyone feels picked up, no one is bored. | -| | | Makes Photos. | +| | Time | Task | +| ------------------------ | ---- | ----------------------------------------------------- | +| | | Place snacks on the tables in small bowls or similar. | +| | | Distribute merchandise. | +| | | Have declarations and forms ready for late deciders. | +| | | Have lists and visitor cards ready if necessary. | +| | | Check drinks in an interval. | +| | | Make coffee if necessary. | +| | | Provide tea, coffee, milk, sugar. | +| | | Provide breakfast / snacks. | +| | | Pick up lunch. | +| | | Lunch "build up" | +| | | Cleanup | +| | | Keep an eye on the process (keep times a little bit). | +| | | See if everyone feels picked up, no one is bored. | +| | | Makes Photos. | ## Checklist after Hackathon -| | Date | Task | -|----------------------------------------|------------|--------------------------------------------------------------------| -| | | Collect photos and provide them in a link for review and approval. | -| | | Create and send feedback sheet. | -| | | Create Blog Post Article. | -| | | Eventually create retro video. | -| | | Create social media posts. (After all approvals). | -| | | Prepare debriefing. | -| | | Summarize and process feedback. | +| | Date | Task | +| ------------------------ | ---- | ------------------------------------------------------------------ | +| | | Collect photos and provide them in a link for review and approval. | +| | | Create and send feedback sheet. | +| | | Create Blog Post Article. | +| | | Eventually create retro video. | +| | | Create social media posts. (After all approvals). | +| | | Prepare debriefing. | +| | | Summarize and process feedback. |