This module allows the import of an existing PHPBB3 installation into D7's relevant core modules. It also includes other modules which import data into Drupal contrib modules.

More specifically, it imports forums, and containers, into core Forum. It creates users from all the phpbb users, while maintaining working password. It imports all forum topics and posts, although in phpbb there is no distinction.

This is a replacement for the ageing http://drupal.org/project/phpbb2drupal

I have done some work on phpbb2drupal but felt that the code base had got unwieldy. I suggested changing some of the code to use the Migrate framework but when I started looking into it, I found that it was really an all or nothing approach so I started a rewrite of phpbb2drupal. Under discussion with the maintainer of that project it was felt that my module does a better job, with cleaner code and that going forward, this is the better way to handle things. He is now pointing D7 users to my sandbox project and I, in turn, am directing users of older versions of Drupal to phpbb2drupal.

The sandbox page can be found here http://drupal.org/sandbox/darksnow/1353038

The git repo can be found here http://drupalcode.org/sandbox/darksnow/1353038.git

Comments

michelle’s picture

I would suggest calling it simply "PHPBB Migration" or something similar. Otherwise a new project is needed when PHPBB 4 comes out and so on. With a more generic name, you could simply branch the module for each new version rather than having separate projects.

Michelle

patrickd’s picture

Status: Needs review » Needs work

welcome

why not putting this rewrite into phpbb2drupal eg 7.x-2.x ?
It would be nicer to have it all in one place.

It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Go and review some other project applications, so we can get back to yours sooner.

darksnow’s picture

Thanks for the suggestions, and the quick replies.

I've contacted the current maintainer of phpbb2drupal and he's made me a maintainer. It does seem to be the best way to go.

I have a quick question, and I realise that this is probably not the best place for it.

I created a 7.x-2.x branch of the code locally, then renamed a few files for consistency, updated some others with my code from this sandbox and added the remaining files. Essentially, I went thought a refactored some stuff so this sandbox project is now called phpbb2drupal throughout the code. Anyway, that isn't really relevant, suffice to say, the code from this sandbox is now in a branch of ppbb2drupal.

My issues is that this code cannot be seen anywhere. I'm not listed as a maintainer on the project page and the VCS viewer doesn't show my code, or my branch at all. A git checkout does get my branch if requested though, so I'm fairly sure it's there.

This is my first commit to D.org, all other small submissions have been patches submitted by others. So my question is simple enough, what's going on?

Again, I'm sure this isn't the right place to ask, but I don't know who else to ask.

Cheers.

patrickd’s picture

If you go to the project page and click on Repository viewer you'll see all branches (HEADS) at the bottom, then click on 7.x-2.x and your commits will be shown.
http://drupalcode.org/project/phpbb2drupal.git/shortlog/refs/heads/7.x-2.x
Your name at the commits is "DarkSnow" so I think the problem is that you did not authentificate right with git.

Try this

git config user.email "your@mail"

To show code on the project page you have to create a release (at the bottom of the project page there are "Administer releases" and "Add release" links for this). But you got to have the permission of the main-maintainer to do this.

misc’s picture

@darksnow has been contacted to ask if the application is abandoned.

After ten weeks with a status of needs work: the applicant may be contacted by a reviewer to determine whether the application was indeed abandoned. The action taken by the reviewer should be documented in the project application issue.

http://drupal.org/node/894256

darksnow’s picture

Status: Needs work » Closed (won't fix)

Thanks for the message MiSc.

This sandbox project was abandoned following the suggestions above. The maintainer of phpbb2drupal contacted me during this application process and made me the maintainer of phpbb2drupal.

I then replaced the existing code base with the code in this sandbox and work continued in there.

I updated the sandbox project page to reflect all that but was unaware that I should have put something in here.

Do I need to mark this project as abandoned in some official way?

Cheers.

Martin...

patrickd’s picture

Your sandbox has a link to the existing module and is marked as abandoned, that's perfect!

thanks for your collaboration