Re: [Wikitech-l] Mailman archives broken?

Hi, On Thu, Aug 16, 2012 at 7:07 PM, Daniel Zahn wrote: > > the last time we had to rebuild archives was about 2 weeks ago. > Unfortunately this is a major drawback of removing messages from > archives as you pointed out and we are aware of it. We had a thread > there though that contained privat

Re: [Wikitech-l] Can we make an acceptable behavior policy? (was: Re: Mailman archives broken?)

This is (hopefully) a community. When somebody fucks something up, they own up to it and somebody fixes it (sometimes the person who did it fixes it, sometimes somebody else). The proper way to phrase it would have been "So how can we go about fixing this?". By saying that you're not putting one pe

Re: [Wikitech-l] Can we make an acceptable behavior policy? (was: Re: Mailman archives broken?)

On Aug 16, 2012, at 7:18 PM, MZMcBride wrote: > Ryan Lane wrote: >>> What is your plan to clean up the mess you made? >> >> I need to call you out on this MZ. This is an incredibly rude way to >> phrase this. >> >> I get that our community tends to accept this kind of behavior, but I >> think

Re: [Wikitech-l] Can we make an acceptable behavior policy? (was: Re: Mailman archives broken?)

Ryan Lane wrote: >> What is your plan to clean up the mess you made? > > I need to call you out on this MZ. This is an incredibly rude way to > phrase this. > > I get that our community tends to accept this kind of behavior, but I > think we should really put effort into coming up with some metho

[Wikitech-l] Can we make an acceptable behavior policy? (was: Re: Mailman archives broken?)

> What is your plan to clean up the mess you made? > I need to call you out on this MZ. This is an incredibly rude way to phrase this. I get that our community tends to accept this kind of behavior, but I think we should really put effort into coming up with some method of discouraging people fro

Re: [Wikitech-l] Mailman archives broken?

Daniel Zahn wrote: > On Thu, Aug 16, 2012 at 1:49 PM, Federico Leva (Nemo) > wrote: >> Thanks Daniel. I don't understand, how can a message need to be removed >> completely? > > In this case the request was for a complete thread to be removed. > Since many people reply with full quotes it usually

Re: [Wikitech-l] Smart machine-learning based anti-spam system (I wish!)

On 17/08/12 04:16, Daniel Friesen wrote: > Of course. While I have the whole idea for the ui, backend stuff, how > to handle the service, etc... I haven't done the actual > machine-learning stuff before. I would think that the actual machine learning stuff would be the hard part. I stopped using T

Re: [Wikitech-l] Smart machine-learning based anti-spam system (I wish!)

Hi Daniel, A lot of your ideas are covered by http://en.wikipedia.org/wiki/Wikipedia:STiki. Andrew has done a lot of great research, if you haven't read his papers yet that might be a good intro to the type of machine learning approaches that have been used. That being said, I would love to have

Re: [Wikitech-l] EtherEditor testing, round 3: Minor stress test

So I'm here to ask for some volunteers to help me test EtherEditor tomorrow, between 20:00 and 22:00 UTC. I'll be in #ethereditor on Freenode with a list of things to try out, and really, some number of people helping me stress test the connections to the backend would be immensely useful. All r

Re: [Wikitech-l] Mailman archives broken?

On Thu, Aug 16, 2012 at 1:49 PM, Federico Leva (Nemo) wrote: > Thanks Daniel. I don't understand, how can a message need to be removed > completely? In this case the request was for a complete thread to be removed. Since many people reply with full quotes it usually repeats the information in alm

Re: [Wikitech-l] Mailman archives broken?

Thanks Daniel. I don't understand, how can a message need to be removed completely? I can't imagine anything which couldn't just be redacted by leaving at least the message's "skeleton" as demanded by Nemo _

Re: [Wikitech-l] OAuth Implementation

Hi Tyler, I've been slowly trying to organize getting an implementation done. OAuth does have it's issues, but about once a week I have other developers here at WMF who want to do a project that would be much easier and more secure if we had OAuth. We started a list of stories here http://www.med

[Wikitech-l] EtherEditor stress test about to start

A brief note, we're about to start a stress test of EtherEditor, an extension for real-time collaborative editing, at 20:00 UTC. If you'd like to help out, or if you'd like to watch, do please join us in #ethereditor on Freenode. If you don't have IRC for whatever reason, but still would like t

Re: [Wikitech-l] OAuth Implementation

I indeed meant the OAuth extension for PHP (the PECL one). *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Thu, Aug 16, 2012 at 3:41 PM, Derric Atzrott < datzr...@alizeepathology.com> wrote: > >Read both

Re: [Wikitech-l] OAuth Implementation

Mhm, sounds good. *sigh* Going to be a long journey. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Thu, Aug 16, 2012 at 3:23 PM, Daniel Friesen wrote: > Read both OAuth 2 (and it's Bearer and MAC specs

Re: [Wikitech-l] OAuth Implementation

>Read both OAuth 2 (and it's Bearer and MAC specs) and the OAuth 1 RFC. > >I would probably avoid reading the PHP code for it. I have a feeling that >it's going to do nothing but give you some wrong ideas about how OAuth >should be implemented. I think he meant the OAuth extension for PHP [0] rath

Re: [Wikitech-l] OAuth Implementation

Read both OAuth 2 (and it's Bearer and MAC specs) and the OAuth 1 RFC. I would probably avoid reading the PHP code for it. I have a feeling that it's going to do nothing but give you some wrong ideas about how OAuth should be implemented. -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http:

Re: [Wikitech-l] OAuth Implementation

Yeah I've noticed. I decided to start with reading the OAuth IETF document first so I'm totally familiarized with the protocol. Then I'm going to look at the PHP extension (although in the long run I don't want to have it as a dependency), and finally I'm going to look through the mailing list and

Re: [Wikitech-l] OAuth Implementation

On Thu, 16 Aug 2012 11:39:54 -0700, Tyler Romeo wrote: Is anybody working on OAuth for MediaWiki? Because if not I might put something together (i.e., start putting together design documents based on http://www.mediawiki.org/wiki/OAuth). *--* *Tyler Romeo* Stevens Institute of Technology,

[Wikitech-l] OAuth Implementation

Is anybody working on OAuth for MediaWiki? Because if not I might put something together (i.e., start putting together design documents based on http://www.mediawiki.org/wiki/OAuth). *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com |

[Wikitech-l] organize a bug triage

> Hello, > > We didn't have a bug triage since May. I suggest organizing one in a few > weeks (say 2?) > > I agree to take care of this if it is widely supported. > How about focusing on patch triage? > > I mean reviewing bugs with patches attached but not in gerrit. > > Any other subject would be

Re: [Wikitech-l] organize a bug triage

Thanks Chad and Andre for your responses. I am new to the community and did not know that RESOLVED bugs were considered CLOSED. Thanks for the update. Al Snow > Date: Thu, 16 Aug 2012 14:01:33 -0400 > From: innocentkil...@gmail.com > To: wikitech-l@lists.wikimedia.org > Subject: Re: [Wikitech-l

[Wikitech-l] Smart machine-learning based anti-spam system (I wish!)

I've had a good idea for an anti-spam system for awhile. Blocks, Captchas, and local filters, all the tricks we've been using end up not working well enough to easily deal with the spam on a lot of wikis. I know this because I've been continually dealing with the spam on a small dead wiki. S

Re: [Wikitech-l] organize a bug triage

Triaging already closed bugs seems like a huge waste of time when there's so many open bugs that need love. -Chad On Aug 16, 2012 1:53 PM, "Andre Klapper" wrote: > Hi Al, > > [Expectations, workflows and manpower among FOSS projects differ so > please take my comments with a grain of salt as I d

Re: [Wikitech-l] organize a bug triage

Hi Al, [Expectations, workflows and manpower among FOSS projects differ so please take my comments with a grain of salt as I don't follow the Wikimedia project that closely.] On Thu, 2012-08-16 at 13:31 -0400, Al Snow wrote: > > > c. Accept non-fix resolution > > > * Accepting all non-fixed resol

Re: [Wikitech-l] organize a bug triage

Andre, > > c. Accept non-fix resolution > > * Accepting all non-fixed resolution. > > * STATUS is RESOLVED; RESOLUTION is not "FIXED" (I count at least 5 > > non-"FIXED" RESOLUTION values) > Sorry but I don't know what you mean by "accepting" here. :/ When I look at the non-"FIXED" RESOLUTIONs t

Re: [Wikitech-l] organize a bug triage

Hi Al, On Thu, 2012-08-16 at 11:02 -0400, Al Snow wrote: > I see 3 types of bug triages: Thanks. These could be added to https://www.mediawiki.org/wiki/Project:WikiProject_Bug_Squad/Activities Some more ideas could be to concentrate on a single module (e.g. extensions) or to update/try to reprod

Re: [Wikitech-l] Mailman archives broken?

On Thu, Aug 16, 2012 at 2:00 AM, Guillaume Paumier wrote: > I was told yesterday that the mailman/pipermail archives were broken, > in that permalinks were no longer linking to the messages they used to > link to (therefore not being "permalinks" at all).\ Hi Guillaume, the last time we had to

Re: [Wikitech-l] organize a bug triage

I see 3 types of bug triages: a. Up-front * Confirming bugs and assigning them to developers. * STATUS is "UNCONFIRMED", "NEW", "REOPENED"; RESOLUTION is N/A b. Verify fix * Verifying fixes (STATUS is "RESOLVED"; RESOLUTION is "FIXED") c. Accept non-fix resolution * Accepting all n

[Wikitech-l] Wikidata weekly blocker mail

Hi all, no new blockers. The two current blockers are still open, and the discussion is ongoing. In both cases the ball in our court right now: * The Wikidata branch (https://bugzilla.wikimedia.org/show_bug.cgi?id=38622): the latest comment by Tim

[Wikitech-l] organize a bug triage

Hello, We didn't have a bug triage since May. I suggest organizing one in a few weeks (say 2?) I agree to take care of this if it is widely supported. How about focusing on patch triage? I mean reviewing bugs with patches attached but not in gerrit. Any other subject would be good as well. opi

Re: [Wikitech-l] Notification bubble system

I didn't like jsMessage's behaviour of mw.util.jsMessage( 'Foo' ); treating 'Foo' as html, so any string you pass will be treated as plaintext. But it does accept arbitrary DOM nodes and jQuery objects just like jsMessage did. And as a bonus it will also accept a mw.message instance and automatical

Re: [Wikitech-l] Notification bubble system

This looks like it would work brilliantly for Echo real time notifications. Does it accept arbitrary HTML as a payload? On Mon, Aug 13, 2012 at 6:18 PM, Daniel Friesen wrote: > A little while ago Trevor Parscal changed our jsMessage setup to be a > floating auto-hiding notification bubble. > http

[Wikitech-l] Mailman archives broken?

Hi, I was told yesterday that the mailman/pipermail archives were broken, in that permalinks were no longer linking to the messages they used to link to (therefore not being "permalinks" at all). I know this happened at least once in the past, when the archives were rebuilt. Retroactively fixing

Re: [Wikitech-l] Gerrit evaluation: where we stand

>That said there are known negatives; the Java+Google Web Toolkit >front-end is intimidating to people who might want to help improve >the UI; even Gerrit devs don't love it. :) >Improvements to the UI and to the git-review CLI tool are welcome... Intimidating to PHP+JS only devs - but Java+Googl