Can this be brought back/centralised on the appropriate existing channel
(#wikimedia-dev or #wikimedia-office), as it was decided for the metrics
meeting?
Thanks,
Nemo
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On 18/10/12 14:10, Denny Vrandečić wrote:
For now, we have no plans for Wikidata to create articles. This would,
in my opinion, meddle too much with the autonomy of the Wikipedia
language projects.
I don't know if I am so bad at explaining things or if this is such a
complex thing to grasp.
On Mon, Oct 22, 2012 at 2:17 PM, Nikola Smolenski smole...@eunet.rs wrote:
No one has ever suggested for Wikidata to create articles.
OK; then I misunderstood and generate the article on the fly..
Regards,
Ole
--
http://palnatoke.org * @palnatoke * +4522934588
No one has ever suggested for Wikidata to create articles.
OK; then I misunderstood and generate the article on the fly..
So to make sure that I understand this correctly, this is the idea:
* Let's say I search on the lojban Wikipedia for Creagerstown, Maryland
* The article doesn't exist, but
On 22/10/12 14:31, Derric Atzrott wrote:
No one has ever suggested for Wikidata to create articles.
OK; then I misunderstood and generate the article on the fly..
So to make sure that I understand this correctly, this is the idea:
* Let's say I search on the lojban Wikipedia for
Mark, thank you, for preparing the RC.
I've started packaging for openSUSE, but after updating my test-system, I have
recognized, that everything is very slow now. Where it took MW1.19 ~0.3 secs to
render a page, I have now to wait for 12 seconds.
I don't see any issues in the apache-log nor
On Sun, Oct 21, 2012 at 12:43:32PM +0200, John Erling Blad wrote:
In my opinion, parsing .js and .css as wikitext is a borken idea.
Add some kind of pragmas to the page and strip them off in the ResourceLoader.
Going further in that direction, I seem to recall one of the goals of
ContentHandler
That should have said
These are only on github till we can test replication and have pull
request support in gerrit.
--tomasz
On Sat, Oct 20, 2012 at 2:20 PM, Platonides platoni...@gmail.com wrote:
On 18/10/12 18:52, Tomasz Finc wrote:
These are only on gerrit till we can test replication
On 10/19/2012 11:43 AM, Tomasz Finc wrote:
I added a couple of highly visible but missing projects from github.
Thank you!
Question: does anybody have a problem if MediaWiki extensions are listed
as own projects in Ohloh as opposed to be aggregated to the MediaWiki
project?
Hi folks,
To help accelerate code review, we (WMF) have recently made efforts to
expand the +2 merge right on Git/Gerrit, consistent with the idea that
+2 is an expression of trust and confidence in someone's judgment
rather than an indicator of universal technical competence.
For example, you
Rather than expanding +2 I'm a little more concerned about allowing more
people to create repositories.
Currently it can take a half week waiting for a new repo just so you can
contribute a new extension, and there's typically no notification.
We need to make getting multiple new extensions
Am 23.10.2012 01:21, schrieb Daniel Friesen:
Rather than expanding +2 I'm a little more concerned about allowing
more people to create repositories.
Currently it can take a half week waiting for a new repo just so you
can contribute a new extension, and there's typically no notification.
We
Agreed on what Daniel said. I'd much prefer to keep my extensions on
Gerrit, but it becomes slightly frustrating when you have to wait two weeks
for the repository to be created.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com |
Thomas Gries wrote:
Am 23.10.2012 01:21, schrieb Daniel Friesen:
Rather than expanding +2 I'm a little more concerned about allowing
more people to create repositories.
Currently it can take a half week waiting for a new repo just so you
can contribute a new extension, and there's typically
My understanding is that creating new repositories becomes WAY easier
with Gerrit 2.5, which is one of many reasons the upgrade to 2.5 is one
of Chad's priorities. (Also GitBlit support, automatic GitHub repo
creation, etc.) We know creating new repos is pretty sub-optimal right
now and are
On Mon, Oct 22, 2012 at 8:12 PM, Sumana Harihareswara
suma...@wikimedia.org wrote:
My understanding is that creating new repositories becomes WAY easier
with Gerrit 2.5, which is one of many reasons the upgrade to 2.5 is one
of Chad's priorities. (Also GitBlit support, automatic GitHub repo
On Mon, 2012-10-22 at 20:11 -0400, MZMcBride wrote:
Am 23.10.2012 01:21, schrieb Daniel Friesen:
Currently it can take a half week waiting for a new repo
Is there a relevant bug about this? I guess you'd want a general bug about
slowness to create new requested repos (that's the issue,
On Monday, October 22, 2012 at 4:37 PM, Tyler Romeo wrote:
Agreed on what Daniel said. I'd much prefer to keep my extensions on
Gerrit, but it becomes slightly frustrating when you have to wait two weeks
for the repository to be created.
FWIW I happened to request a repository on Saturday
On Monday, October 22, 2012 at 5:46 PM, Ori Livneh wrote:
On Monday, October 22, 2012 at 4:37 PM, Tyler Romeo wrote:
Agreed on what Daniel said. I'd much prefer to keep my extensions on
Gerrit, but it becomes slightly frustrating when you have to wait two weeks
for the repository
Sorry about that. Two weeks is indeed *not* the norm. Most repositories
(from what I can tell) are created pretty quickly. However, if we're
encouraging extension developers to stick to Gerrit, the occasional edge
case might put a bad taste in somebody's mouth (as for me, I'm a patient
man ;) ).
On Mon, 22 Oct 2012 17:46:33 -0700, Ori Livneh o...@wikimedia.org wrote:
On Monday, October 22, 2012 at 4:37 PM, Tyler Romeo wrote:
Agreed on what Daniel said. I'd much prefer to keep my extensions on
Gerrit, but it becomes slightly frustrating when you have to wait two
weeks
for the
Last year we decided not to participate in Google Code-In
https://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page
, an outreach program to help us get more 13-to-17-year-old
contributors. I outlined the reasons here:
I think it's a cool idea, especially considering I'm still kicking myself
for not getting involved in open-source earlier. The real problem is
deciding what to have them work on.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com |
23 matches
Mail list logo
