Name: Wiktionary
Description: A wiki-based Open Content dictionary.
Type: Project
Policy: Default
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Aklapper | T75872 Create project: Wiktionary | |||
| Resolved | Aklapper | T802 Phabricator projects for Wikimedia sister projects |
Event Timeline
Comment Actions
Please elaborate how this tag would be used in Phabricator exactly.
I might be against fulfilling this request without having a general plan for T802 in place first.
Comment Actions
Indeed, I'm personally very happy to create projects for sister projects, but we need a plan before starting. @GPHemsley, your feedback in T802 is welcome!
@Aklapper, do you want to take both?
Comment Actions
I'm not really sure how to answer that. It will be used to track tasks related to Wiktionary (e.g. T986 and its dependencies). What other information are you looking for?
I might be against fulfilling this request without having a general plan for T802 in place first.
It's not intended to replace any existing wiki-based discussion mechanisms, necessarily. It's meant to be used as a bug/task tracker, as Bugzilla/Phabricator are intended to be used.
Comment Actions
Basically "where to make the cut", and defining that well.
For example, does that proposed keyword include/exclude cases like "I ran into this bug in the MediaWiki extension XYZ on Wiktionary.org because that extension is installed there. So it also affects Wiktionary (and any other wiki site that has the extension installed) and hence I'm going to set the project tags for all those wiki sites on this task" ?
A use case is also welcome. If such a project exists, how would you use the information that a task in Phabricator has the Wiktionary project tag set? Search for it in some situations? Would it cover both bugs that happen on Wiktionary and also enhancement/functionality requests that would be specific to Wiktionary?
I'd really like to understand that better before making any decisions.
Comment Actions
Sorry, I had replied to @GPHemsley at T802#795889 and forgot to report here, which I'm doing now. I think this discussion is applicable to all Wikimedia project families, therefore I believe it is better to focus the discussion in T802 for now.
Comment Actions
This task was blocked by T802, and I changed the blocking for the more specific case of T78482 based on
@GPHemsley said:
It will be used to track tasks related to Wiktionary
PS: for the added: 1; removed: 1, see T78250.
Comment Actions
Requested project All-and-every-Wiktionary has been created: https://phabricator.wikimedia.org/project/profile/1115/
Please encourage interested people to visit the project and to join the project as members, and to subscribe themselves to the project in order to receive updates!
Generally: Recommended practices for project and workboard management in Phabricator are available.
And if for some reason you ever want to rename the project, please check the guidelines first.
Enjoy!
Comment Actions
The description is a bit confusing to me. It doesn't say that reports added to the project need to have some sort of community demand, so additions like T38881#1098189 are acceptable. However, it doesn't clearly say that being in the project is no indication of community support/need/discussion.
Can the description be clarified either way?
Comment Actions
Seven months ago the Phabricator project All-and-every-Wiktionary was created - it's time to evaluate in T111046.
Those who wanted to see this Phabricator project: How do things work for you? Does the project and its workboard help you keeping an overview and getting things done? What problems do you face? Do people associate the project on tasks in the way that you suppose it? If not, do you have ideas how to improve that? Are you missing something that would make your work easier?
Please provide your input in T111046 (not here!) so we can find out whether to continue this way. And/or what to improve.
Thanks in advance for your feedback!