Hi @Acrion-dev, there is already https://github.com/acrion/zelph/issues and the code is on GitHub. Could you elaborate, for example do you plan to switch off GitHub issues entirely and only link to the Wikimedia Phabricator project, or what is the idea? Thanks! :)

Hi @Aklapper ! Yesterday I presented zelph at the Wikimedia Hackathon in Istanbul (T391618) where I received encouraging feedback from several developers. Mohammed Sadat from Developer Outreach recommended creating a project. I'm open to moving issues or the code repository to Wikimedia's infrastructure if that would better support zelph's goal of becoming a key component for Wikidata quality assurance. What would you recommend as the best approach?

from Developer Outreach

I'm curious where to find out about that Developer Outreach team (but that's off-topic here).

What would you recommend as the best approach?

Unfortunately I don't think I can judge what's the best approach here - there are some advantages of using Wikimedia infrastructure but in the end it is the maintainer(s)' decision. Maybe the Developer Outreach team can provide more guidance?
I can only warn about conversation fragmentation, confusion, and duplication of work by having two issue trackers (GitHub and Phabricator) in parallel.

In T393334#10795158, @Aklapper wrote:

from Developer Outreach

I'm curious where to find out about that Developer Outreach team (but that's off-topic here).

CC @Mohammed_Sadat_WMDE (So this is developer outreach specifically from WMDE / Wikidata / Wikibase

Ah, makes sense (and I guess I could have known myself, sorry!).

@Mohammed_Sadat_WMDE: Could you elaborate on the intention / advantages? The project currently has an issue tracker on GitHub.

Hi @Aklapper and @Mohammed_Sadat_WMDE,

To follow up on the recommendation I received at the Wikimedia Hackathon, I've created a WikiProject page for zelph at https://www.wikidata.org/wiki/Wikidata:WikiProject_zelph.

Regarding the advantages of having a WikiProject on wikidata.org in addition to the GitHub repository:

1. Community Integration: The WikiProject provides a central hub for Wikidata community members interested in data quality to learn about and contribute to zelph without requiring GitHub familiarity.

2. Visibility within Wikidata: Having an official project page increases visibility among Wikidata editors who can benefit from the contradiction detection capabilities.

3. Alignment with Similar Projects: Other tools that enhance Wikidata quality (like constraint violation reports) have dedicated WikiProjects to coordinate their development and usage.

I understand the concern about fragmentation. The GitHub repository currently hosts only the source code and doesn't yet have an active community of contributors or issue discussions. I'm certainly open to potentially migrating the development infrastructure to Wikimedia platforms if that would better integrate zelph with the Wikidata ecosystem. In the meantime, I plan to clearly document on the WikiProject page that all technical development happens in one place to avoid any confusion.

I would appreciate your guidance on whether creating a Phabricator project would still be valuable in this context, or if the WikiProject page is sufficient for coordination at this stage.

That depends on what you have in mind when it comes to "coordination"...
Phabricator is for issue and work tracking - bug reports and feature requests, basically. GitHub's "Issues" serve the same purpose.
However if you consider moving the source code from GitHub to https://gitlab.wikimedia.org/ you'd need a place to track issues and that would be Phabricator.

Having a WikiProject page on wikidata.org is completely independent from anything on Phabricator. :)

In T393334#10831948, @Aklapper wrote:

@Mohammed_Sadat_WMDE: Could you elaborate on the intention / advantages? The project currently has an issue tracker on GitHub.

Sorry I'm late to the party. I think there was a misunderstanding. My advice was to create a project page on Wikidata which I can now see exists, and not here on phabbricator. I don't think a project tag is needed here.

In T393334#10795290, @Addshore wrote:

In T393334#10795158, @Aklapper wrote:

from Developer Outreach

I'm curious where to find out about that Developer Outreach team (but that's off-topic here).

CC @Mohammed_Sadat_WMDE (So this is developer outreach specifically from WMDE / Wikidata / Wikibase

We have @Deepesha_WMDE doing developer advocacy for the Wikibase Suite team. But we don't have a developer advocacy team per se.

@Aklapper @Mohammed_Sadat_WMDE Thanks everyone for clarifying this. Regarding the source code location: While I understand that GitHub Issues serve the same technical purpose as Phabricator and that the WikiProject page is independent, I’m still open to migrating the repository from GitHub to GitLab Wikimedia if that would better integrate zelph with the Wikimedia ecosystem. I believe there could be benefits in terms of project visibility and community perception when tools are hosted within the Wikimedia infrastructure.

Would it be appropriate to move zelph to GitLab Wikimedia and use Phabricator for issue tracking? If so, I noticed my Wikimedia Developer Account shows "Your account is pending approval from your GitLab administrator and hence blocked" when I try to access GitLab Wikimedia. Could you please advise on the next steps if you think this migration would be beneficial?

I noticed my Wikimedia Developer Account shows "Your account is pending approval from your GitLab administrator and hence blocked"

I've approved your Wikimedia GitLab account.

Would it be appropriate to move zelph to GitLab Wikimedia and use Phabricator for issue tracking?

Wikimedia GitLab welcomes hosting. I don't know how to interpret the word "appropriate" though. :)

Is a Phabricator project still wanted? If yes then I'd recommend disabling https://github.com/acrion/zelph/issues.

Thank you for approving my GitLab Wikimedia account and for the clarification!

Yes, a Phabricator project is definitely still wanted. The zelph project has recently received Wikimedia Rapid Grant funding (R-RF-2508-20108), and I'm planning to use Phabricator for issue tracking and project management going forward.

I've already disabled GitHub Issues as recommended and am currently migrating the repository to GitLab Wikimedia using the import functionality. GitLab Wikimedia will serve as the primary repository for development and contributions, while GitHub will remain as a mirror since the repository already has established visibility.

Once the Phabricator project tag is created, I'll update the GitHub project documentation accordingly.

Sorry, this somehow fell through the cracks. :(
Requested public project Zelph has been created: https://phabricator.wikimedia.org/project/view/8564/

(In case you need to edit the project or project workboard itself at some point and lack permissions, please see Trusted-Contributors.)

Interested people are welcome to join the project as members, and to watch the project in order to receive notifications on task updates.

If tasks are created under this new project which are about a specific codebase, please make sure to also add these codebase project tags to the tasks in addition.

Recommended practices for project and workboard management in Phabricator are available.

Feel free to bring up any questions you might have about Phabricator or about best ways to manage projects in Phabricator.

Enjoy!

I've already disabled GitHub Issues as recommended

https://github.com/acrion/zelph/issues is currently enabled.

and am currently migrating the repository to GitLab Wikimedia using the import functionality

What's the URI of the repository? I cannot find a project in Wikimedia GitLab...

@Acrion-dev gentle ping in case you missed @Aklapper's queries in T393334#11677716 :)