Description
Related Objects
Event Timeline
My question was: How will it be effectively used and for what and why? A counter-question is not an answer. :)
In general I do not want to create lots of tags/projects for the sake of having lots of tags/projects. And tagging creates costs (triage time).
If a software has no clear license, either its maintainers need to do their homework, or if things are more complicated WMF-Legal needs to get involved.
For example when a software's license is not clear, or when it needs to be changed to a more permissive one.
In general I do not want to create lots of tags/projects for the sake of having lots of tags/projects. And tagging creates costs (triage time).
It wouldn't be a real project, more like a tag as good first task or Epic.
You describe a categorization, but you still don't describe why and how having that categorization would be useful for anybody.
I am conducting a lazy but extensive review of software licensing on Wikimedia. I presume I'll find more and more problems as I advance.
While creating projects is cheap in Phabricator, associating new tasks properly to projects has a cost (someone needs to triage incoming tickets) and gets harder the more projects there are. Hence I ask all these questions...
Sorry but I still don't feel like my question has been answered how that project will effectively be used. You're doing a review. That's very welcome. But how does a project help with that? So far it sounds like you'd like to create a list of items for yourself. What comes after that, and how will the existence of that project help make someone (like you) do anything about the tasks in that project?
That is up to the authors and maintainers of the software, and to you of course ;-)
I cannot and will not set a priority on tasks whose projects I don't maintain. I can only report them and suggest a possible solution.
Sorry but I still don't feel like my question has been answered how that project will effectively be used. You're doing a review. That's very welcome. But how does a project help with that? So far it sounds like you'd like to create a list of items for yourself. What comes after that, and how will the existence of that project help make someone (like you) do anything about the tasks in that project?
Identifying license issues at a glance, organizing what needs to be done in a workboard, etc.
Identifying license issues at a glance, organizing what needs to be done in a workboard, etc.
Are those theoretical needs or actual needs? Do you plan to organize software license issues on a workboard? How? :)
By the way, the new project can be a child of WMF-Legal.
They already have plenty of tasks about software licenses.
(Technically speaking there are no subprojects in Phabricator.)
I'm happy to see this created if WMF-Legal is also interested in its existence
Requested project Software-Licensing has been created: https://phabricator.wikimedia.org/project/profile/1443/
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!
Recommended practices for project and workboard management in Phabricator are available.
Enjoy!