Problem/Motivation

The wiki namepsace appears to be an unpublished Drupal 4/5 module.

Proposed resolution

I would like to takeover the namespace for a new module that will create a new wiki entity for creating wiki pages within Drupal. A new entity is needed in order to (hopefully) support wikitext.

Remaining tasks

  1. Clone existing project and push it to an archive sandbox.
  2. Publish (or delete?) existing module
  3. Assign ownership to davidwbarratt

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

davidwbarratt created an issue. See original summary.

davidwbarratt’s picture

Issue summary: View changes
avpaderno’s picture

The project has been unpublished; the project owner has been moved to Unsupported Projects, the account used to show the project is unsupported.

When taking over a project for creating a different project, the existing project needs to be cloned in a sandbox project. I am not sure if cloning an unpublished project is possible, or the project needs to first be published.

gisle’s picture

Issue summary: View changes

You can clone the existing project without it being published first. Just use this command locally:

git clone https://git.drupalcode.org/project/wiki.git

 
The cloned project can then be pushed to an archive sandbox.

Added this as a task to the issue summary.

Interesting project. looking at the git log I see that ther repo contains three commits by Dries, and that the project's main developer was moshe weitzman – user #23 here. No indication about why it is unpublished, but development stopped in 2006. Back in those days, it may be that when a project became obsolete, it was unpublished rather than just marked as obsolete as we do now.

davidwbarratt’s picture

Is there anything I need to do?

gisle’s picture

Yes. As stated in the issue summary, you need to clone the existing project repo and push it to an archive sandbox.

davidwbarratt’s picture

davidwbarratt’s picture

Issue summary: View changes
davidwbarratt’s picture

Is it ok to keep using this repo? Might be nice to keep the history in the main namespace (if you don't mind).

gisle’s picture

Assigned: Unassigned » avpaderno

I am assigning this to kiamlaluno. I think he is the only one that monitors this issue queue with sufficient access to publish an unpublished node.

avpaderno’s picture

Status: Active » Fixed

I changed ownership as requested.

davidwbarratt’s picture

kiamlaluno,

Thanks!

I tried to change the name to "Wiki" but I got the error "This project name is already in use." I searched for that name, but nothing came up, any ideas?

davidwbarratt’s picture

Oh it's this sandbox...
https://www.drupal.org/sandbox/themeprofessional/1670942
Should I create a new issue to request the name?

gisle’s picture

I don't think it is the sandbox (if I've understood things right, it does not have a short name, just a number).
The old project/repo still exist (as per your request in comment #9), i.e.: https://www.drupal.org/project/wiki . It is now owned by you. Just set it up as the remote in your local git configuration for your project, and push your project into its repo.

avpaderno’s picture

It happened to me in the past: I wanted to create a project with a specific name, but it was already taken. Then, I discovered it was the name used from a sandbox project.
Project names must be unique between sandbox projects and full projects. I guess it's done to allow a promoted sandbox project to keep its name. It also avoids users can create a sandbox project with the same name a full project already have.

I renamed the sandbox project and renamed the Wiki-NS project to Wiki.

gisle’s picture

Got it. The name collision was the long name (human facing name) - not the short name. Learned something new today.

davidwbarratt’s picture

Thank you so much!

Status: Fixed » Closed (fixed)

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