Drupal Pune Regular Activities

We discussed strategies on what would be the best ways to do regular meetups and help community members actively participate in meetups and events. Here’s a summary:

  • Active Marketing
    • Regular posts and promotions
    • Drupal Pune Newsletter:
      • Proposal to create a Drupal Pune Newsletter and include Drupal openings in India.
      • Need further discussion.
      • Rahul will do research on this with Sushil’s help and present their findings in next meetup.
    • We’ll be exploring marketing automation tools like:
      • Open source: Mautic
      • Paid: Hootsuite, etc.
      • Dipak will research on this and set up something
    • Designs:
      • We often need design assets for social marketing and posts
      • We need to prepare the list of posts/topics we need designs
      • Nikita will prepare the list
    • Misc:
      • Mails from drupalpune12 [at] gmail.com often go to spam. 
        • Dipak: Find a way so that emails don’t go to spam
  • Community communication & collaboration:
    • The current use of DIA Slack for community communication was discussed.
    • Concerns were raised regarding the loss of message history due to using a free instance.
    • It was proposed to transition community communication to the #pune channel in the Drupal Official Slack workspace to preserve message history and facilitate better collaboration.
    • Action items:
      • Announcement to be made to all community members regarding the transition and instructions for joining the new channel to be disseminated by Dipak.
      • Nikita to support marketing.
    • We also decided that it’s team lead's responsibility to post their team’s MOM in respective channels
  • Splash awards:
    • We want to host a Pune version of Splash Awards.
    • Aastha will research the best way to do this and present it in the next meetup.
  • Re-launching Drupal Campus Ambassador Program and Mentorship for GSOC
    • We had a discussion where Aastha volunteered to lead the re-launching Drupal CAP
    • Others showed interest in helping with this:
      • Ruturaj, Vighnesh, Rahul
    • Anyone else interested, please reach out to us in #pune channel in Drupal Official slack
  • Consideration for Drupal Pune Mascot
    • The need for a mascot for Drupal Pune was discussed. Further brainstorming and decision-making are required.

Drupal Camp 2024

We also discussed the plan and strategy for hosting DrupalCamp Pune 2024.

Here’s the summary of the discussion:

  • Tentative date and venue for Drupal Camp Pune 2024:
    • It was agreed upon to schedule DrupalCamp on 19th—20th Oct tentatively. Further deliberation is needed to finalize the location
  • Attendees ROI:
    • Networking opportunities
    • Job prospects
    • The value of obtaining Acquia certifications was emphasized to empower attendees with in-demand skills and credentials.
  • Sponsorship ROI:
    • Get in touch with previous sponsors to understand the expectations.
  • Paid or Free Camp:
    • Attendees debated whether sponsorship for the event should be paid or free.
    • Consensus was reached to opt for a pay-for-value approach
    • Discussed the idea of bringing participants from outside India to enhance the diversity and richness of the event.
  • Drupal Camp finance retrospective
    • Rahul Shinde to explore the options for Drupal Pune to manage finances for camps efficiently.
    • Research around creating a non-profit entity for Drupal Pune.
  • Collaboration:
    • The possibility of collaborating with other communities was explored. 
    • Explore the possibility of collaborating with DrupalCons. Proposal for free tickets for DrupalCon. Need to get in touch with the Drupal Association to discuss the same.
  • We created teams for DrupalCamp. We invite everyone to reach out to us in #pune channel if you want to join any team:
    • Marketing:
      • Lead: Nikita
      • Reviewers: Ajit and Dipak
      • Team: Asmita, Vighnesh, Ruturaj, Ishita
    • Website Team:
      • Lead: Sushil
      • Team: Abhisek, Asmita, Pankaj
      • Sushil: To arrange a meeting to discuss web development strategy
    • Design team
      • Lead: Aastha (Tentative)
      • Aastha will reach out to various designers for collaboration.
    • Sponsorship
      • Lead: Dipak (Tentative)
      • Team: Nikita
      • Dipak will set up a meeting to discuss strategy on how to reach out to sponsors
    • Speaker coordination
      • Lead: Ajit
    • Networking Event
      • Lead: Abhisek
    • Logistics:
      • Lead: Asmita
    • Bi-weekly meetings
      • Lead: Vighnesh
      • Action item:
        • Create a different calendar, so everyone can subscribe
      • Make a decision on splash awards.
      • Team leads must join to connect and discuss the progress/action items.

Plan for next Meetup:

  1. Date for meetup:
    1. 27th April
  2. Agenda:
    1. Guidance for attendees for Acquia Certifications (Every meetup should have a discussion)
    2. BOF on Career opportunities/path (Every meetup should have a BOF for this)
    3. Tech sessions to be decided
    4. What’s new you’ve worked with in Drupal.
    5. First contribution: getting started
    6. Splash awards strategy update: Aastha
    7. Drupal Pune Newsletter update: Rahul
    8. Decide on agenda for next month
  3. Location for next meetup:
    1. Abhisek volunteered to look for a place with Asmita’s help
    2. Location preference: Near Shivaji Nagar.
    3. A place with AC and good seating and accessibility

Comments

nikitaaswani created an issue. See original summary.

dipakmdhrm’s picture

Issue summary: View changes
rahul.shinde’s picture

Issue summary: View changes

Updated.

ajits’s picture

Issue summary: View changes
dipakmdhrm’s picture

Issue summary: View changes
ajits’s picture

Issue summary: View changes
rahul.shinde’s picture

Issue summary: View changes
rahul.shinde’s picture

Updating attribution.

rahul.shinde’s picture

rahul.shinde’s picture

Status: Active » Reviewed & tested by the community
ajits’s picture

dipakmdhrm’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.