Project type: Team
Optional hashtatgs: #hackathon
Project description: Hackathon organization team
Visible To: Public (no login required)
Editable By: All Users
Joinable By: All Users
Project type: Team
As a person who helped with perhaps all Hackathons, I can clearly state, that there is a recurring set of core people participating on the organization.
Discussing generic Hackathon tasks is another relevant thing.
Besides - like any other projects - it's joinable and leavable.
Also, if the "administration" was left out, it can actually be for all Hackathon participants (and that would involve all reasons above too).
As far as I know there will be a Wikimania-Hackathon and a (European) Wikimedia-Hackathon, like last years.
For instance The current one in Jerusalem will have "sister-hackathons" in Amman and Rammalah.
I'm not aware of a Hackathon in Ramallah (there will be a technical workshop though) and I don't see hacking activities listed for WikiArabia. If you have more information / links, please share.
Tasks about those were not marked with Wikimedia-Hackathon-2016-Organization.
That's because they have nothing to do with Wikimedia-Hackathon-2016-Organization, as Ramallah and Amman are different people organizing different things.
I don't see a reason for creating a #Hackathon project as each Hackathon org team is mostly local and not involved in organizing next year's Hackathon in a different place. Currently, people organizing a specific Hackathon or interested in following the tasks for a specific Hackathon can become member / subscribe to the dedicated Phabricator project for that specific Hackathon, and that seems to be sufficient. If it is not, please explain which actual problem and existing use case you would like to solve by creating a generic #Hackathon project.
I don't see a need for a #hackathon project either, at least as we are working today. If one day there is a formal group working on hackathons, then sure. But first the group, then the tag. Tasks that go across hackathons usually end up in Developer-Advocacy and the next hackathon(s) in the calendar.
Regarding that example, it is a task to be fixed once, and then added to https://www.mediawiki.org/wiki/Hackathons/Hackathon_tips_for_organizers so future Hackathon edition organizers are aware.
The organizers of a specific Hackathon are free to use a dedicated Hackathon edition Phabricator project to plan and organize any organizational (and actionable) tasks for the edition (like "Order lanyards in three different colors" for the 2017 Hackathon).
Declining this task for the time being as per last comments, similar to T126954: Create team #Wikimania.
Please feel free to reopen this task once input has been provided which specific existing problems might get solved by such an additional team project, in contrast to existing Hackathon related Phabricator projects in the past. Thanks!