@Osnard: T111606#1670917 talks about Sourceforge (SF) being used as the bugtracker for BlueSpice.
Will the SF tracker be closed and links be updated? What will happen to the existing reports in SF?

@Aklapper : No, not yet. We plan to use the Phabricator project mainly for communication/discussion with the MediaWiki develper community. SF.net will remain for our communication with the end users (anonymous access to Phabricator is not possible, AFAIK). At least for a while. There is an internal discussion about whether or not to drop SF.net completely. But I don't think this will happen very soon. Maybe selected topics from SF.net will be moved to Phabricator, but there is no plan to do a full migration.

That means you plan to have two bug trackers? If so how do you plan to keep them in sync?

(Anonymous reporting of issues in Phabricator is not possible as we want to be able to follow up with reporters.)

Well on SF.net we've got quite a number of anonymous contributions. It won't be easy to make them create a Phabricator account right away. But I don't think that this is actually required.

If there are any issues on SF.net that we feel should be on Phabricator, our support will transfer them and close the SF.net ones with a link to Phabricator.

Actually I see the BlueSpice project on Phabricator as a place to discuss various topics with the MediaWiki community (like continuous integration, unit tests, distribution, etc.).

Thanks. Makes sense. Any links that should be part of the Phabricator project description (like project page, or also a link to SF.net only if it makes sense)?
After that we're good to go here. :)

It'd be nice if you could add the following links to the project page

• http://bluespice.com/
• https://help.bluespice.com
• https://sourceforge.net/projects/bluespice/

If there is limited space, just take the first one :)

I added the existing phabricator repos to the project description too.

Thanks a lot!