With the recent conversion of Bugzilla to Phabricator, I requested the
conversion of our tracking bug to be a project, with the basic
premise that a [tag = project], and we are a community working across
multiple languages, and that some of our individual efforts spread
outside of Wikisource, and sometimes the outer efforts flow inside.
Anyway part of the discussion comes to the point that we are not
unique among the sisters with that request/idea, and there is a
thought about nomenclature, for which the following post points to
Being a person of simple thoughts, I would be happy for our project to
be called (wait for it) ... Wikisource, though that doesn't allow for
any future aspects, and others will have valuable input. So I point
you to the general nomenclature discussion  and my specific request
 that is lacking a name in the request.
PS. Apologies for the noise for those who are already cc'd the phabricator post.
---------- Forwarded message ----------
From: Qgil <no-reply(a)phabricator.wikimedia.org>
Date: Mon, Dec 15, 2014 at 9:35 PM
Subject: [Maniphest] [Changed CC] T78482: XXXX-Radar projects for
Wikimedia family projects and languages + MediaWiki Stakeholders
Qgil added subscribers: Rillke, Steinsplitter, Billinghurst, Praveenp.
Qgil added a comment.
In https://phabricator.wikimedia.org/T78482#846850, @Nemo_bis wrote:
> I have no idea what "radar" means here.
A "Wiktionary" project in phabricator could also be a project used by
the Wiktionary community to organize their work. This is why I'm
proposing "-Radar" to identify tags used to collect tasks //on the
radar// of a community. Could be another word, or could be no word if
you think it's not needed.
> Tags aren't inherently "more elegant" than tracking bugs. For instance, https://phabricator.wikimedia.org/T43492 used to be an on-wiki page, which I converted to a tracking bug, which worked well because cc'ing yourself is equivalent to watchlisting a page. Watching a project, instead, brings you a ton of notifications for all tasks past and future: yes, there side ways but they're not as easy.
> So, if the aim is to *replace* on-wiki lists, let's make this the summary.
Fair point. A notification like "Send me an email when a task is
assigned to projects X, Y, Z" is possible with Herald
(https://phabricator.wikimedia.org/T630), and I expect most advanced
users to set one for themselves to fill the current gap of
notifications between joining (almost no notification) and watching
(all notifications) a project.
In any case, you are right that the main change is to move on-wiki
lists of tasks to Phabricator. I have edited the description to make
this more clear.
I think nowadays an own tag project is a better solution for a new
list, but tracking tasks also do the work, and they are indeed easier
to subscribe to. Maybe the difference is whether you want to organize
the tasks tracked in a workboard or not.
> Then ask one by one what their requirements are for such a replacement. Adding *additional* lists, instead, is out of question.
The maintainers of these lists are CCed here, please help if I have
I guess you mean that i.e. it is out of question to create a
Commons-Radar project paralel to
https://commons.wikimedia.org/wiki/Commons:Bugs still exists?
Absolutely. New lists could be started by communities that have none,
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or
Cc: Aklapper, Qgil, Tpt, Micru, Ricordisamoa, Rdicerb, He7d3r, Carlb,
Quiddity, Krenair, Glaisher, Reedy, Nemo_bis, MZMcBride,
MarkAHershberger, Vriullop, Toniher, Arnaugir, GPHemsley, jayvdb,
Darkdadaah, Raymond, Gryllida, scfc, Krinkle, marcoil, Rillke,
Steinsplitter, Billinghurst, Praveenp, Jdforrester-WMF, Rfarrand,
The International Conference on Semantic Web Business and Innovation
The University of Applied Sciences and Arts Western Switzerland (HES-SO
October 7-9, 2015
All registered papers will be included in SDIWC Digital Library
The proposed conference on the above theme will be held at he University
of Applied Sciences and Arts Western Switzerland (HES-SO Valais-Wallis)
on October 7-9, 2015 which aims to enable researchers build connections
between different digital applications.
The conference welcomes papers on the following (but not limited to)
*Semantic Web and Linked Data
- Database, IR, NLP and AI technologies for the Semantic Web
- Geospatial Semantic Web
- Information Extraction from unstructured data
- Information visualization of Semantic Web data and Linked Data
- Internet of things
- Languages, tools, and methodologies for representing and managing
Semantic Web data
- Linked open data
- Management of Semantic Web data and Linked Data
- Ontology engineering and ontology patterns for the Semantic Web
- Ontology modularity, mapping, merging, and alignment
- Ontology-based data access
- Privacy and Security
- Query and inference over data streams
- Search, query, integration, and analysis on the Semantic Web
- Semantic business process management
- Semantic Sensor networks
- Semantic technologies for mobile platforms
- Semantic Web and Linked Data for Cloud Environments
- Semantic Web, Ontologies
- Social networks and processes on the Semantic Web
- Supporting multi-linguality in the Semantic Web
- User Interfaces and interacting with Semantic Web data and Linked Data
*Business and Innovation in Semantic Web
- Business Model Innovation
- Business Models and E-Commerce
- Business Technology Intelligence
- Challenges for change in semantic services
- Collaborative improvement and innovation
- E-Business Applications and Software
- E-commerce Technology Adoption
- E-commerce, E-Business Strategies
- E-tailing and Multi-Channel selling
- Evolution of Business model for Semantic Web Applications
- High-tech marketing
- Implementation strategies for responsible innovation
- Innovation for E-Business
- Innovative methods and tools for products and services
- Practices and Cases in E-Commerce
- Production of Knowledge Economy
- Technology and Business Transformation
- Technology strategies
- The Latest Trends in Linked Data
- Web Advertising and Web Publishing
- Web and Mobile Applications
Researchers are encouraged to submit their work electronically. All
papers will be fully refereed by a minimum of two specialized referees.
Before final acceptance, all referees comments must be considered.
Submission Date: Open from now until Sept. 1, 2015
Notification of Acceptance: 6 weeks from the submission date
Camera Ready Submission: September 14, 2015
Registration Deadline: September 14, 2015
Conference Dates: October 7-9, 2015
Dear Wikitech (cc'd Wikisource)
A recent discussion in English Wikisource's Scriptorium was querying
why commercial book companies, etc. were getting higher search hits,
especially where they may just have summary information, rather than
full text. In that discussion someone pointed to some of the webmaster
information at Google, eg. , which (ultimately) talks about their
microformat (preferred) or JSON-LD as a means to put in more
particular metadata as explained at schema.org (for creative works
I went to play, and ultimately failed, and was pointed to the
inability to <script> for security reasons, and the inability to add
micodata (<cite user="bawolff">microdata attributes are implemented in
MediaWiki, but currently disabled via
So my naive questions to those that know these things are
1) How do we look to improve external search engine hits for the
sister sites where they are particularly pertinent to a search
[wikipedia already gets Google special treatment]
2) if the schema.org metadata is a preferred means to progress, what
is the recommended means to progress such an issue
3) presumably some of this fits into the discussion about Structured
Data discussion, and what means is there to include this into that
Thanks for the guidance.
Anyone know of a tool or a ready means that can check for works (that
are proofread) for the amount/percentage transcluded? I am wondering
how many works may be out there that have plenty of work done on them
but sitting there needing transcluding.
It seems that a tool that can do that sort of analysis, or that could
project that data to an Index: page would be useful.
To note that MZM did create the checker tool on toollabs to manually
run a check on an index page, however, that level of reaction is only
useful for a detailed analysis of a work.
While I am mumbling about wishes, I would still love to have the
ability to project the transcription status of a work (the ribbon)
onto a page rather than having to poke [[Special:IndexPages]]