Yay!!
John Vandenberg.
sent from Galaxy Note
---------- Forwarded message ----------
From: "MZMcBride" <z(a)mzmcbride.com>
Date: Apr 23, 2013 12:28 PM
Subject: [Wikitech-l] Bug 189: "Add a music wikimodule" resolved/fixed
To: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org>
Cc:
Hi.
https://bugzilla.wikimedia.org/show_bug.cgi?id=189
Congrats to all involved in getting bug 189 resolved! :-)
Bug 189 was one of the oldest unresolved and one of the better known bugs
in Bugzilla involving a request to add a music module to Wikimedia wikis.
Quick stats about the bug:
* Opened: 2004-08-22
* Votes: 48
* Comments: 123
The bug filer is still around and left a nice note on the bug
(<https://bugzilla.wikimedia.org/show_bug.cgi?id=189#c123>):
---
Congratulations to all !
It makes my dream comes true today !
Thanks million times!
---
<https://en.wikipedia.org/wiki/Note> seemed like an easy target for
demoing the newly deployed Score extension
(<https://www.mediawiki.org/wiki/Extension:Score>) on a production site,
if anyone's interested. I tried looking around for a point and click
lilypond or ABC code generation tool (preferably Web-based), but a lot of
these tools quickly went over my head.
MZMcBride
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello Wikisourcerers!
See below for the announcement I just sent to the wikitech-ambassadors
list about the new Score extension available to you all.
It's already been announced on the Scriptorium, as many of you probably
know:
https://en.wikisource.org/wiki/Wikisource:Scriptorium#Score_extension_.28a_…
I just wanted to cover all the bases.
All the best,
Greg
----- Forwarded message from Greg Grossmeier <greg(a)wikimedia.org> -----
> Date: Tue, 23 Apr 2013 08:40:53 -0700
> From: Greg Grossmeier <greg(a)wikimedia.org>
> To: Wikitech Ambassadors <wikitech-ambassadors(a)lists.wikimedia.org>
> Subject: New Extension: Score - Music Markup!
>
> Hello Ambassadors!
>
> I wanted to give you a heads up that there is a new extension available
> for use on Wikimedia project wikis; Score!
>
> http://www.mediawiki.org/wiki/Extension:Score
>
> It was enabled yesterday during the regularly scheduled MediaWiki
> deployment window.
>
> See what it can do at this English Wikipedia Help page:
> https://en.wikipedia.org/wiki/Help:Wiki_markup#Musical_notation
>
> This is a long time request, first reported in August of 2004:
> https://bugzilla.wikimedia.org/show_bug.cgi?id=189
>
> We'll announce this in a more wider fashion in a few days, but I wanted
> to give you all a heads up.
>
> Thanks, and as always, please do let me know if you have any questions.
>
> Greg
>
>
> Some bonus relevant links:
>
> You can learn more about Lilypond, the software that the Score extension
> uses, at:
> http://www.lilypond.org/introduction.html
>
> Their manuals:
> http://www.lilypond.org/manuals.html
>
>
> --
> | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
> | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
----- End forwarded message -----
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
The following was posted at English Wikipedia. I reproduce it here due to
the wider implementation and approach that the community can have
https://en.wikisource.org/wiki/Wikisource:Scriptorium#Implementing_Easier_a…
Implementing Easier and More Efficient Metadata Tags on Wikisource
Disclosure: I am contracted by Creative Commons LRMI Project.
I would like to propose adopting the use of a by-default-disabled
Mediawiki metadata feature that would greatly improve the organization and
search engine visibility of the content of Wikisource. These metadata tags
are part of Schema.org which was developed by Google, Bing, Yahoo, and
Yandex, and can be viewed here. The benefit of these tags is that when used
within educational content such as on Wikisource, the information contained
on the page is made into a way that is easily intelligible to machines by
changing just one line with the Mediawiki configuration. An example of
MediaWiki using Schema can be seen by using Google's testing tool. These
metatags were originally developed by LRMI but their recent adoption of
Schema.org is a huge milestone that has great potential to improve the
efficiency of the way we are able to search educational resources and
content on places like Wikisource. Maximilian.Klein.LRMI (talk) 21:29, 22
April 2013 (UTC)
I have let a light response with the post, however, there are many with
more knowledge of this than I, and as mentioned a interlanguage WS
community response seems better.
Regards, Billinghurst
Apologies if this unwelcome on the Wikisource list -- I know from
speaking with the conference organizer that they are very interested
in hearing from community projects like Wikisource.
----
Call for Proposals
Proposals are invited for the Social, Digital, Scholarly Editing
conference, to be held in Saskatoon, Saskatchewan, Canada, from 11-13
July 2013. This conference comes at a critical inflection point in
the transformation of scholarly editing caused by the two massive
shifts of the digital revolution: the movement of all data into
digital form and the creation of new modes of collaboration. For the
first: the creation of massive amounts of data in digital form has
already transformed the basic materials of scholarly editing, while
digital tools offer new methods for exploration and publication. For
the second: where scholarly editing in the past has been typically the
work of a single dedicated scholar, the development of social media
opens up the possibilities of collaborative work across whole
communities. These changes affect every aspect of scholarly editing.
This conference will explore the theoretical, practical, and social
implications of these changes.
Proposers accepted from this open call will join some thirty invited
conference participants, drawn from scholarly editing, digital
humanities, and the 'citizen scholar' movement. Confirmed
participants are Barbara Bordalejo, Susan Brown, Ben Brumfield,
Gabriel Egan, Paul Eggert, Paul Flemons, Alex Gil, James Ginther,
Tuomas Heikkilä, Fotis Jannidis, Laura Mandell, Murray McGillivray,
Brent Nelson, Catherine Nygren, Dan O'Donnell, Roger Osbourne, Wendy
Phillips-Rodriguez, Elena Pierazzo, Ken Price, Peter Robinson,
Geoffrey Rockwell, Peter Shillingsburg, Ray Siemens, Michael
Eberle-Sinatra, Joshua Sosin, Melissa Terras, Edward Vanhoutte, and
Joris van Zundert (to be confirmed: Hans Gabler and Jerome McGann).
The conference will be preceded by a one-day workshop, focussing on
collaborative editing systems.
Proposals should focus on some aspect of contemporary digital
scholarly editing. We welcome descriptions of current projects,
theoretical or speculative discussions, bibliographic work, or any
aspect of scholarly digital editing. Papers considering scholarly
editing in a communal, collaborative context are particularly
encouraged. Proposals will be accepted under two strands: one for
students of graduate and doctoral programs, one for all others. We
particularly welcome proposals from the GO::DH (Global
Outlook::Digital Humanities) community, addressing digital scholarly
editing in a global context. We will able to offer financial support
for accepted proposals, if needed, in the form of bursaries and/or
funding for all travel and other costs, and will give preference in
allocating funding to proposers from circumstances where support is
rarely available (if at all). As well as a 500 word abstract,
proposers should submit a cover letter explaining their interest in
the conference theme, why they want to attend and indicate what level
of support (if any) they might need to come to the conference.
Proposal submission will close on 26 April; successful proposers will
be notified by 10 May 2013.
For more information, see the website at
https://ocs.usask.ca/conf/index.php/sdse/sdse13
Ben Brumfield
http://manuscripttranscription.blogspot.com/
---------- Forwarded message ----------
From: David Gerard <dgerard(a)gmail.com>
Date: Thu, Apr 11, 2013 at 4:27 AM
Subject: [Wikimedia-l] Distributed Proofreaders hits 25, 000 books
scanned and proofread
To: Wikimedia Foundation Mailing List <wikimedia-l(a)lists.wikimedia.org>
This is pretty awesome.
http://www.pgdp.net/phpBB2/viewtopic.php?t=53404
- d.
_______________________________________________
Wikimedia-l mailing list
Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
--
John Vandenberg
Hi!
Thanks for your quick answer!
I've opened some bugs for the most important tasks:
https://bugzilla.wikimedia.org/show_bug.cgi?id=46578https://bugzilla.wikimedia.org/show_bug.cgi?id=46580
I've also added the proposal to the list with a copy/past of the message. Feel free to improve it if needed. https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Extens…
The community is, I think, very happy with this request as this proposal is related to "back office" changes that will allows to add new features and support of the Visual Editor that is a feature waited for a long time.
Thanks for your support!
Thomas
> Date: Mon, 25 Mar 2013 15:04:38 -0700
> From: qgil(a)wikimedia.org
> To: thomaspt(a)hotmail.fr; zanni.andrea84(a)gmail.com; wikisource-l(a)lists.wikimedia.org; dacuetu(a)gmail.com; sumanah(a)wikimedia.org
> Subject: Re: [Wikisource-l] Missing project ideas for GSOC
>
> Good to hear from the Wikisource community!
>
> On 03/25/2013 02:12 PM, Thomas PT wrote:
> > Hi!
> > Yes, I think that a GSOC project related to Proofread Page is a very
> > good idea. The things to do would be:
>
> After going through a lot of possible projects, this is the approach I
> find more efficient:
>
> 1. File an enhancement request in Bugzilla.
>
> 2. List the proposal at
> http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects
>
> If you need already proposals written somewhere you can simply link to
> them, no need to duplicate.
>
> If the community is happy with the request, it sounds feasible and there
> is at least a mentor supporting it, then we can add it to GSOC 2013. If
> not, then we can keep polishing in Bugzilla and wait for the next
> program, if nobody decides to take it before.
>
> Looking forward to hearing from you. Soon. :)
>
> PS: personal anecdote: my first significant contributions to Wikimedia
> were done at ca:wikisource some years ago...
>
> --
> Quim Gil
> Technical Contributor Coordinator @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
It was suggested to me that the Wikisources should be paying attention to
the opportunity available through WMF's participation in Google Summer of
Code.
I have started a discussion at
https://wikisource.org/wiki/Wikisource:Scriptorium#Wikisources_asked_for_id…
Regards, Billinghurst
-------- Original Message --------
Subject: [Wikitech-l] Missing project ideas for GSOC
Date: Wed, 20 Mar 2013 16:43:23 -0700
From: Quim Gil <qgil(a)wikimedia.org>
Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Organization: Wikimedia Foundation
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
It's time to start defining what we want our Google Summer of Code to be
all about. Let's look at the ideas we are proposing to potential students:
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects
Many of the ideas listed there are too generic ("Write an extension"),
improvements of existing features ("Improve Extension:CSS") or
work-in-progress tasks ("Fix Parsoid bugs"). Many others are not
directly related with development, and therefore not suitable either for
GSOC.
After this filtering, we seem to be left with:
* Article evolution playback tool idea
* An easy way to share wiki content on social media services
* Write an extension to support XML Sitemaps without using command line
* Extension:OEmbedProvider
* Add support for x3d 3D files to MediaWiki
* Allow smoother and easier Wikimedia Commons pictures discovery
* Build an interwiki notifications framework and implement it for
InstantCommons
* Automatic category redirects
(If you think your project should also be considered here please speak
up!)
Most of these projects seem to be extension (and PHP?) centric. Can we
have more diversity? Maybe gadgets and templates are too simple for a
GSOC project? What about the mobile front? Do we have skin development
projects that could make it here? Anything in the DevOps area? Anything
the MediaWiki core maintainers would like to see happening?
It would be also nice to have more candidates benefiting specific
Wikimedia projects. Beyond Wikipedia, we have several proposals related
to Commons. Wikidata seems to be joining soon. What else? Could this be
a chance to help Wiktionary, Wikibooks or any other project with
specific needs craving for tech attention?
Also to the many students that have already showed their interest: feel
free pushing your project ideas now!
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi Denny,
as Nemo pointed out, that grant is for Wikisource :-)
http://meta.wikimedia.org/**wiki/Grants:IEG/Elaborate_**
Wikisource_strategic_vision<http://meta.wikimedia.org/wiki/Grants:IEG/Elaborate_Wikisource_strategic_vi…>
We spoke about that briefly in the Office hours:
one of the main thing Wikidata could do, I think,
is to centralize cross-wiki links, the very same way it centralized
interlinks.
I don't know how difficult could it be, but I sense this would be a
breakthrough for all sister projects.
We could review the Sister template, and make cross-wiki navigation much
more easy and useful.
Aubrey
On Mon, Mar 11, 2013 at 3:16 PM, Federico Leva (Nemo) <nemowiki(a)gmail.com>wrote:
> Denny Vrandečić, 11/03/2013 14:52:
>
> There is currently a number of things going on re the future of
>> Wiktionary.
>>
>> There is, for example, the suggestion to adopt OmegaWiki, which could
>> potentially complicate a Wikibase-Solution in the future (but then again,
>> structured data is often rather easy to transform):
>> <http://meta.wikimedia.org/**wiki/Requests_for_comment/**Adopt_OmegaWiki<http://meta.wikimedia.org/wiki/Requests_for_comment/Adopt_OmegaWiki>
>> >
>>
>> There is this grant proposal for elaborating the future of Wiktionary,
>> which I consider a potentially smarter first step:
>>
>> <
>> http://meta.wikimedia.org/**wiki/Grants:IEG/Elaborate_**
>> Wikisource_strategic_vision<http://meta.wikimedia.org/wiki/Grants:IEG/Elaborate_Wikisource_strategic_vi…>
>>
>>>
>>>
> That's Wikisource. :)
>
>
>
>> There's this discussion on Wikdiata itself:
>>
>> <https://www.wikidata.org/**wiki/Wikidata:Wiktionary<https://www.wikidata.org/wiki/Wikidata:Wiktionary>
>> >
>>
>> And I know that Daniel K. is very interested in working into this
>> direction.
>>
>> Personally, I regard Wiktionary as the third priority, following Wikipedia
>> and Commons. A lot of the other projects -- like Wikivoyage or Wikisource
>> -- can be served with only small changes to Wikidata as it is, but both
>> Commons and Wiktionary would require a bit of thought (and here again,
>> Commons much less than Wiktionary).
>>
>
> Actually Wikiquote and Wikivoyage use interwikis exactly like Wikipedia;
> Commons in the same way except it's interproject; Wiktionary in the same
> way except it's case-sensitive and not about concepts (opr about a stricter
> definition of concept); Wikisource in a completely different way;
> Wikibooks, Wikinews and Wikiversity I'm not sure.
> As for phase II, it's another story. Wikisource and Commons would benefit
> a lot from it; for Wiktionary it could be a revolution; for Wikispecies
> idem but with less effort (?); Wikiquote would become
>
>
> I would appreciate a discussion with
>> the Wiktionary-Communities, and also to make them more aware of the
>> OmegaWiki proposal, the potential of Wikidata for Wiktionary, etc. Just to
>> give a comparison: it took a few months to write the original Wikidata
>> proposal, and it was up for discussion for several months before it was
>> decided and acted upon. I would strongly advise to again choose slow and
>> careful planning over hastened decisions.
>>
>
> It's impossible to plan or discuss anything without knowing what matters.
>
> Nemo
>
>
> ______________________________**_________________
> Wikimedia-l mailing list
> Wikimedia-l(a)lists.wikimedia.**org <Wikimedia-l(a)lists.wikimedia.org>
> Unsubscribe: https://lists.wikimedia.org/**mailman/listinfo/wikimedia-l<https://lists.wikimedia.org/mailman/listinfo/wikimedia-l>
>