Problem/Motivation

The projects drupal/drupal and drupal/core are not under the control of Drupal nor Dries on Packagist. Because of this, the projects could be pointed to urls with bad / malicious repositories.

Proposed resolution

Request that Packagist transfer ownership drupal/drupal and drupal/core to Drupal and/or Dries.

Remaining tasks

  1. Create an official Drupal packagist account (if one doesn't already exist)
  2. Request that Packagist transfer ownership to official account

Comments

davidwbarratt’s picture

Title: Add drupal/drupal an drupal/core to packagist » Add drupal/drupal and drupal/core to packagist
davidwbarratt’s picture

Title: Add drupal/drupal and drupal/core to packagist » [no patch] Submit drupal/drupal and drupal/core to Packagist
Priority: Normal » Major
Issue summary: View changes
davidwbarratt’s picture

Issue summary: View changes
davidwbarratt’s picture

Title: [no patch] Submit drupal/drupal and drupal/core to Packagist » [no patch] Take over ownership of drupal/drupal and drupal/core on Packagist
Issue summary: View changes
davidwbarratt’s picture

Issue summary: View changes
davidwbarratt’s picture

Issue summary: View changes
tstoeckler’s picture

I maintain drupal/core on Github currently.

Just posting here to confirm that I will of course hand over that namespace as soon as the ownership/responsibility has been worked out here.

tstoeckler’s picture

Status: Postponed » Active

So https://packagist.org/users/Dries/ now owns drupal/drupal and drupal/core. So in terms of the issue title this is now fixed.

We should still discuss what to actually do with those. I can hardly imagine Dries wants to maintain the subtree split from his MacBook ;-)

tstoeckler’s picture

Status: Active » Fixed

The drupal/drupal package is being updated via a Git hook on drupal.org now. The drupal/core is being updated from my subtree split on Github. So we can mark this fixed. Once we have a subtree split on Drupal.org we can add a Git hook to that as well and retire my Github repo. But this issue is fixed, AFAICT.

Status: Fixed » Closed (fixed)

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