Currently discussed on-wiki, so scattered across many wiki pages in many languages. That's an issue.

Sure, I can host elsewhere. Does wmf have infrastructure for this? If not, I can host at a random external site with version control.

See:

http://lecturify.net/lbot.zip

wmtran tool

Dialog gadget on en.wn wiki - was not ever attempted to be chucked out of wiki into a repo

Asked42 lead manager script in a .js on-wiki [[User:Asked42/LeadManager]]

https://gryllida.neocities.org/news/writer/v3/

Newsletter wiki extension

Possible fork of PageAssessments extension, customised for news

These are those i wrote or i use, if we get a tag and find some hosting, I'm sure there will be loads more of tools to collaborate on

Mainly, I want wiki users to not have to register for yet another account in order to get involved into software development

In T402150#11093697, @Gryllida wrote:

See:

http://lecturify.net/lbot.zip

wmtran tool

Dialog gadget on en.wn wiki - was not ever attempted to be chucked out of wiki into a repo

Asked42 lead manager script in a .js on-wiki [[User:Asked42/LeadManager]]

https://gryllida.neocities.org/news/writer/v3/

Newsletter wiki extension

Possible fork of PageAssessments extension, customised for news

I don't think that there should be one project tag to mangle all these things together, especially when some already do have an issue tracker (e.g. Newsletter wiki extension).

Please ideally provide links for the toolks in that list (?) above (using list markup is welcome).

Cannot the tags overlap, so some Newsletter tasks get tagged with this tag?

True. See my previous comment, please provide links. I'd like to see broader explicit on-wiki interest in using Phabricator for planning, in order not to create yet another place (Phabricator) where discussions get fragmented even more than it's already the case.
Also, a human-readable name would be welcome - #Wikinews-Developer-Group or such?

Mainly, I want wiki users to not have to register for yet another account in order to get involved into software development

Phabricator is another account (though no separate password) which requires registration.
Same for any Wikimedia code hosting options (GitLab, Gerrit) if you do not already have a Wikimedia Developer Account.

Ok, I will provide links soon.

You can pick a name, I don't mind any name.

Having the same password and it logs me in automatically if I'm logged into wiki is an important advangage. I consider it better than using external sites.

I can upload codes to gitlab, that's fine.

See:

http://lecturify.net/lbot.zip

wmtran tool https://wmtran.toolforge.org/ code entirely on one page

Dialog gadget on en.wn wiki - was not ever attempted to be chucked out of wiki into a repo https://en.wikinews.org/wiki/Help:Dialog

Asked42 lead manager script in a .js on-wiki [[User:Asked42/LeadManager]] https://en.wikinews.org/wiki/User:Asked42/LeadManager https://en.wikinews.org/wiki/User:Asked42/LeadManager.js

https://gryllida.neocities.org/news/writer/v3/ has source in page source as it is all client side

Newsletter wiki extension https://www.mediawiki.org/wiki/Extension:Newsletter https://phabricator.wikimedia.org/diffusion/ENLT/

Possible fork of PageAssessments extension, customised for news https://gerrit.wikimedia.org/g/mediawiki/extensions/PageAssessments

In T402150#11093707, @Aklapper wrote:

I don't think that there should be one project tag to mangle all these things together, especially when some already do have an issue tracker (e.g. Newsletter wiki extension).

Seems like it's fine as long as it's a group tag, right?

The only thing blocking this at the moment is the project description.

• If this is volunteer on-wiki dev for the whole Wikinews project, then a pointer to the discussion where that was decided would be helpful.
  • @Gryllida, on my talk page on MediaWiki you mentioned a Wikinews consultation that was the onus for creating this project, is there a link to that? (glancing through enwikinews proposals I didn't see anything).
• If this group is for developers of a subset of on-wiki projects used by Wikinews folks, then a list of the projects with links is all that's needed.

A good project description saves you all time in future dealing with bugs going to the wrong place. And it'll save users time if they file a task for you only to find it untagged later.

One note on GitLab: if you need code hosting for these projects that'll be hosted on https://gitlab.wikimedia.org.

• You can host each project on gitlab as your user; e.g., gitlab.wikimedia.org/maskaret/wikinews-draft-writer
• But, we can also create a new GitLab group so everyone in the group can collaborate, like we did for this set of projects https://gitlab.wikimedia.org/repos/10nm

For cross-reference, the Wikinews consultation is at https://meta.wikimedia.org/wiki/Public_consultation_about_Wikinews (See primarily the talk page)

I already provided links and a description. "Project tag for volunteers to coordinate development of wiki software, including mediawiki, its extensions, and third party tools, which assist with authoring and revising pages at any language Wikinews, as well as with presenting the output on external social media and content publishing platforms"

Is that specific enough? 70% of it was already written above?.

Please advise what else is needed.

"The only thing blocking this at the moment is the project description." 😢

Thank you @thcipriani 😊

Please could you help with access or point me to some documentation,

Hi, see https://www.mediawiki.org/wiki/Phabricator/Project_management#Boards : "Editing a project and its columns requires membership in Trusted-Contributors."

I realize I should probably just post the usual text after project creation here. :) Let me do that:

Requested public project has been created: https://phabricator.wikimedia.org/project/view/8111/

(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!

Hi @Aklapper I would like to request that you add me to 'Trusted contributors', for purposes of managing the project that was created. If I understood correctly, this is required for me to be able to edit workboard and create subprojects in it. Please let me know if I understood this incorrectly.