Add the various DrupalSouth events (AU/NZ) as options in the d.org field_events_attended profile field (along with the various DrupalCons)

Created on 4 March 2023, about 2 years ago
Updated 23 June 2023, almost 2 years ago

DrupalSouth events are the respective of DrupalCon US and DrupalCon EU, and are attended by people from an entire continent. I find them to be of equal importance, and people should have the option to add them to their d.org user profile similarly to how other Drupal conferences are listed as options.

You can find details about past events in the official site here: https://drupalsouth.org/events

Listing them here for the sake of being helpful:

  • DrupalSouth 2008 - Christchurch, NZ
  • DrupalSouth 2010 - Wellington, NZ
  • Drupal Downunder 2011 - Brisbane, AU
  • Drupal Downunder 2012 - Melbourne, AU
  • DrupalSouth 2014 - Wellington, NZ
  • DrupalSouth 2015 - Melbourne, AU
  • DrupalSouth 2016 - Gold Coast, AU
  • DrupalSouth 2017 - Auckland, NZ
  • DrupalSouth 2018 - Canberra, AU
  • DrupalSouth 2019 - Hobart, AU
  • DrupalSouth 2022 - Brisbane, AU
  • DrupalSouth 2023 - Wellington, NZ
πŸ“Œ Task
Status

Needs work

Component

Other

Created by

πŸ‡¦πŸ‡ΊAustralia klonos 90% Melbourne, Australia - 10% Larissa, Greece

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Issue created by @klonos
  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    Not sure if this `Drupal.org infrastructure` or `Drupal.org content`... maybe it's from a vocabulary?

  • πŸ‡³πŸ‡ΏNew Zealand xurizaemon Ōtepoti, Aotearoa 🏝

    Based on a look at the Drupal.org API (https://www.drupal.org/api-d7/user/{uid}.json, I expect field_events_attended is a "List (text)" field with checkboxes.

      "field_events_attended": [
        "london_2011",
        "sydney_2012"
      ],
    

    vs this term field:

      "field_areas_of_expertise": [
        {
          "uri": "https://www.drupal.org/api-d7/taxonomy_term/151101",
          "id": "151101",
          "resource": "taxonomy_term"
        },
      ],
    

    So I propose adding these values into the field's options:

    drupalsouth_2008|DrupalSouth 2008 - Christchurch, NZ
    drupalsouth_2100|DrupalSouth 2010 - Wellington, NZ
    ddu_2011|Drupal Downunder 2011 - Brisbane, AU
    ddu_2012|Drupal Downunder 2012 - Melbourne, AU
    drupalsouth_2014|DrupalSouth 2014 - Wellington, NZ
    drupalsouth_2015|DrupalSouth 2015 - Melbourne, AU
    drupalsouth_2016|DrupalSouth 2016 - Gold Coast, AU
    drupalsouth_2017|DrupalSouth 2017 - Auckland, NZ
    drupalsouth_2018|DrupalSouth 2018 - Canberra, AU
    drupalsouth_2019|DrupalSouth 2019 - Hobart, AU
    drupalsouth_2022|DrupalSouth 2022 - Brisbane, AU
    drupalsouth_2023|DrupalSouth 2023 - Wellington, NZ
    
Production build 0.71.5 2024