Re: [Pywikipedia-l] SVN access

[Dr. Trigon]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25.07.2013 16:46, Jeremy Baron wrote:
> On Jul 25, 2013 4:25 AM, "Dr. Trigon"  > wrote:
>> Is teher already a "PEP 8 bot" out there? *wonder*
> 
> yes, I'm sure we could arrange a Jenkins job to check pep8
> compliance.

+1 (for "checking" compliance but not "stricly enforcing" yet)

> (or run a test suite or do just about anything else that can made
> to give standard Unix exit codes)

+2 (IMHO is checking whether the code crashes more important than pep8)

Greetings
DrTrigon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlH+g3kACgkQAXWvBxzBrDCAOACgxXBhr6kWP3IGZYlBct5ZB4Vc
kygAoJvXGn/XGR2xQzUNJpxfiv9IdgHH
=QfX1
-END PGP SIGNATURE-

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[info]

 


- Original Nachricht 
Von: Merlijn van Deen 
An:  Pywikipedia discussion list 
Datum:   23.07.2013 11:03
Betreff: Re: [Pywikipedia-l] SVN access

> On 23 July 2013 08:02, Bináris  wrote:
> 
> >
> > By this time, trusted committers could commit ("merge") their
> > contributions immediately.
> > How often did we have problems because of this?
> > Is this limitation a solution for a real problem (if so, it's good), or
> > just a new rule to do like MW developers once we are forced to use the
> same
> > infrastructure?
> >
> 
> It would reduce the number of commits that break things (e.g. the patching
> story, unicode output on rewrite that broke some stuff, etc). We are
> already doing post-commit review, but pre-commit review means we can give
> our users a more stable framework.
> 
> Merlijn
> 

+1
xqt

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Merlijn van Deen]

On 25 July 2013 16:58, Bináris  wrote:

> For instance, I don't leave a space after # in an inline comment in order
> to fit in 80 characters. The bot will notice this and put the space,
> therefore 80 chars are exceeded, and the bot will break the comment or put
> it into a separate line, which decreases readability. Or how does it work
> at all?


The 'bot' checks the change (or rather: the code base after applying the
change) by running pep8 [1], using the parameters we choose (so we can say
'ignore line length'). If this raises any errors, it will set Verified -2,
which prevents the patch from being merged.

[1] https://pypi.python.org/pypi/pep8
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Bináris]

Is it always possible to enforce PEP8 with a bot, and no human intervention?
Is it always useful to strictly enforce PEP8?

I already saw cases when e.g. the rule for length of lines was broken on
purpose and this helped the readability.

PEP8 is basically useful, but it's a proposal/recommendation.
For instance, I don't leave a space after # in an inline comment in order
to fit in 80 characters. The bot will notice this and put the space,
therefore 80 chars are exceeded, and the bot will break the comment or put
it into a separate line, which decreases readability. Or how does it work
at all?

-- 
Bináris
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Jeremy Baron]

On Jul 25, 2013 4:25 AM, "Dr. Trigon"  wrote:
> Is teher already a "PEP 8 bot" out there? *wonder*

yes, I'm sure we could arrange a Jenkins job to check pep8 compliance.

(or run a test suite or do just about anything else that can made to give
standard Unix exit codes)

-Jeremy
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Amir Ladsgroup]

someone told about it in here:
http://www.mediawiki.org/wiki/Git/Conversion/pywikipedia#Lower_priority
I'm not sure this bot really exists but It would be very cool If
exists and we use it in gerrit

Best



On 7/25/13, Dr. Trigon  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 23.07.2013 12:29, Amir Ladsgroup wrote:
>> Dear Melijn: I think we both know that pywiki devs don't review
>> theirs' commits you can see tons of "new" commits in code review
>> (current system, SVN) and beside that we can have a automated
>> pre-commit review. like a bot that checks If the code doesn't crash
>> and after that let the patch merges and PEP8 bot sounds good to me
>
> Is teher already a "PEP 8 bot" out there? *wonder*
>
> Greetings
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlHw4PEACgkQAXWvBxzBrDCgwACePbv8XV6L9XB8ZnAGQREO0t4G
> j5oAoMz+L2c3YF9L9ZlBkhCHK7eZ/spB
> =UbqV
> -END PGP SIGNATURE-
>
> ___
> Pywikipedia-l mailing list
> Pywikipedia-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
>


-- 
Amir

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Dr. Trigon]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23.07.2013 12:29, Amir Ladsgroup wrote:
> Dear Melijn: I think we both know that pywiki devs don't review
> theirs' commits you can see tons of "new" commits in code review
> (current system, SVN) and beside that we can have a automated
> pre-commit review. like a bot that checks If the code doesn't crash
> and after that let the patch merges and PEP8 bot sounds good to me

Is teher already a "PEP 8 bot" out there? *wonder*

Greetings
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHw4PEACgkQAXWvBxzBrDCgwACePbv8XV6L9XB8ZnAGQREO0t4G
j5oAoMz+L2c3YF9L9ZlBkhCHK7eZ/spB
=UbqV
-END PGP SIGNATURE-

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Amir Ladsgroup]

Dear Melijn:
I think we both know that pywiki devs don't review theirs' commits you
can see tons of "new" commits in code review (current system, SVN) and
beside that we can have a automated pre-commit review. like a bot that
checks If the code doesn't crash and after that let the patch merges
and PEP8 bot sounds good to me

Best

On 7/23/13, Merlijn van Deen  wrote:
> On 23 July 2013 08:02, Bináris  wrote:
>
>> 2013/7/22 Merlijn van Deen 
>>
>>>
>>> No, if you are member of the +2 group means you can accept and merge any
>>> patches. However, you should *not* merge *your own* patches (unless they
>>> are trivial updates, such as i18n or family files), so that other people
>>> can comment on it before the patch is merged.
>>>
>>
>> By this time, trusted committers could commit ("merge") their
>> contributions immediately.
>> How often did we have problems because of this?
>> Is this limitation a solution for a real problem (if so, it's good), or
>> just a new rule to do like MW developers once we are forced to use the
>> same
>> infrastructure?
>>
>
> It would reduce the number of commits that break things (e.g. the patching
> story, unicode output on rewrite that broke some stuff, etc). We are
> already doing post-commit review, but pre-commit review means we can give
> our users a more stable framework.
>
> Merlijn
>


-- 
Amir

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Merlijn van Deen]

On 23 July 2013 08:02, Bináris  wrote:

> 2013/7/22 Merlijn van Deen 
>
>>
>> No, if you are member of the +2 group means you can accept and merge any
>> patches. However, you should *not* merge *your own* patches (unless they
>> are trivial updates, such as i18n or family files), so that other people
>> can comment on it before the patch is merged.
>>
>
> By this time, trusted committers could commit ("merge") their
> contributions immediately.
> How often did we have problems because of this?
> Is this limitation a solution for a real problem (if so, it's good), or
> just a new rule to do like MW developers once we are forced to use the same
> infrastructure?
>

It would reduce the number of commits that break things (e.g. the patching
story, unicode output on rewrite that broke some stuff, etc). We are
already doing post-commit review, but pre-commit review means we can give
our users a more stable framework.

Merlijn
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Bináris]

2013/7/22 Merlijn van Deen 

>
> No, if you are member of the +2 group means you can accept and merge any
> patches. However, you should *not* merge *your own* patches (unless they
> are trivial updates, such as i18n or family files), so that other people
> can comment on it before the patch is merged.
>

By this time, trusted committers could commit ("merge") their contributions
immediately.
How often did we have problems because of this?
Is this limitation a solution for a real problem (if so, it's good), or
just a new rule to do like MW developers once we are forced to use the same
infrastructure?
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Merlijn van Deen]

On 21 July 2013 23:36, Amir Ladsgroup  wrote:

> If you're a member of +2 group, your patches will be merged
> immediately and you can review others' patches (+1 people) and reject
> or accept them:
>

No, if you are member of the +2 group means you can accept and merge any
patches. However, you should *not* merge *your own* patches (unless they
are trivial updates, such as i18n or family files), so that other people
can comment on it before the patch is merged.

Best,
Merlijn
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Amir Ladsgroup]

If you're a member of +2 group, your patches will be merged
immediately and you can review others' patches (+1 people) and reject
or accept them:
http://www.mediawiki.org/wiki/Gerrit/Tutorial#Who_can_review.3F_Gerrit_project_owners

Best

On 7/21/13, i...@gno.de  wrote:
>
>
>> As a PWB dev I support him (or her?) but we will migrate to gerrit in
>> 6 July and after that (a while after)  we can give +2 access to him or
>> her
>>
> What does this mean: +2 access?
>
> xqt
>


-- 
Amir

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[info]

> As a PWB dev I support him (or her?) but we will migrate to gerrit in
> 6 July and after that (a while after)  we can give +2 access to him or
> her
> 
What does this mean: +2 access?

xqt

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Amir Ladsgroup]

As a PWB dev I support him (or her?) but we will migrate to gerrit in
6 July and after that (a while after)  we can give +2 access to him or
her

Best

On 7/4/13, Dr. Trigon  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Can somebody with admin rights comment on this request?
>
> IF this user has enough experience I would like to support this (but
> honestly I do not know... ;)
>
> Thanks and Greetings
> DrTrigon
>
>
> On 01.06.2013 06:52, Hazard-SJ wrote:
>> Hello, I am again asking if it is possible for me to gain SVN
>> access (I know it probably wouldn't last too long, considering that
>> SVN will be read-only in the (near?) future, but that time is still
>> unknown to us). I frequently use the framework, and I'd like to be
>> able to directly make commits, rather than generating patches to
>> put on the bug tracker, when possible. This would include things
>> such as PEP and typo fixes, as well as improving
>> wikipedia.DataPage. Thanks.
>>
>> Hazard-SJ
>>
>>
>> ___ Pywikipedia-l
>> mailing list Pywikipedia-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
>>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlHVflIACgkQAXWvBxzBrDAc7wCfXrD16TgCQw0wqFYvUJnYzJaG
> QLEAoIbDJppvW2ljNOuRFSFsrYzExprZ
> =5mvW
> -END PGP SIGNATURE-
>
> ___
> Pywikipedia-l mailing list
> Pywikipedia-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
>


-- 
Amir

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access

[Dr. Trigon]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Can somebody with admin rights comment on this request?

IF this user has enough experience I would like to support this (but
honestly I do not know... ;)

Thanks and Greetings
DrTrigon


On 01.06.2013 06:52, Hazard-SJ wrote:
> Hello, I am again asking if it is possible for me to gain SVN
> access (I know it probably wouldn't last too long, considering that
> SVN will be read-only in the (near?) future, but that time is still
> unknown to us). I frequently use the framework, and I'd like to be
> able to directly make commits, rather than generating patches to
> put on the bug tracker, when possible. This would include things
> such as PEP and typo fixes, as well as improving
> wikipedia.DataPage. Thanks.
> 
> Hazard-SJ
> 
> 
> ___ Pywikipedia-l
> mailing list Pywikipedia-l@lists.wikimedia.org 
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHVflIACgkQAXWvBxzBrDAc7wCfXrD16TgCQw0wqFYvUJnYzJaG
QLEAoIbDJppvW2ljNOuRFSFsrYzExprZ
=5mvW
-END PGP SIGNATURE-

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[info]

You may leave it untouched.

Regards
xqt___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Bináris]

2012/1/27 Dr. Trigon 

>
> Concerning the __version__ part of your question; the key part to
> understand is actually the magic keyword $Id$.


When I modify an existing script with line
$Id blahblahblah $
shall I change that back to $Id$ or will SVN recognize this way if I leave
it untouched?

-- 
Bináris
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Bináris]

2012/1/27 Dr. Trigon 

>
> you should AT LEAST READ the license (and understand it mor or less)
> BEFORE writing it into the file... Just to be aware what you allow other
> to do to/with your script... ;)
>
Some day I may do that. :-) By that time I will trust the Pywiki team; what
was good for all the previous contributors, should do for me, too. I am not
a pioneer here. Programming is much more important.


>
> Concerning the __version__ part of your question; the key part to
> understand is actually the magic keyword $Id$. Read more in any svn
> manual, e.g. at [1] about it.
>

Thank you, I will read it after a bit of sleeping!

-- 
Bináris
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Dr. Trigon]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

> it to MIT? How to give an MIT license, I just write it into the
> script? And how to prepare a script for getting a revision number?
> What is the syntax? I suppose, the line __version__ should be
> filled in automatically.

First concernig the licencense the answer is yes (more or less ;) BUT
you should AT LEAST READ the license (and understand it mor or less)
BEFORE writing it into the file... Just to be aware what you allow other
to do to/with your script... ;)

Concerning the __version__ part of your question; the key part to
understand is actually the magic keyword $Id$. Read more in any svn
manual, e.g. at [1] about it.

[1]
http://johnbokma.com/mexit/2008/09/30/subversion-svn-keywords-property.html

Greetings
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8h3UwACgkQAXWvBxzBrDCixgCdGMITma1a3H7UjQWjyeOCKHqK
Q0EAmgLq2Sr57fQAjtIKPazxZbF3pyDR
=B/1l
-END PGP SIGNATURE-

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Bináris]

2011/12/31 Merlijn van Deen 

>
> As far as I am concerned you can have SVN access.
>
Thank you, at least one support.  I thought I would have more.

>
> However, before adding your bot to the repository: it should be MIT
> licensed, and not GPL - at least as long as bots and framework coexist in
> the same directory.
>

As you wish. :-) I am not really interested in licences, so it won't be a
problem for me. Once I uploaded a script to Wikipedia, may I transform it
to MIT? How to give an MIT license, I just write it into the script?
And how to prepare a script for getting a revision number? What is the
syntax? I suppose, the line __version__ should be filled in automatically.


> Please see
> https://www.mediawiki.org/wiki/Commit_access_requests#Requesting_commit_access
> for information on the steps of gaining the actual access.
>

Thank you, that was really helpful!
At the moment, I have a little problem. As far as I remember, I never owned
an SSH  key (or I forgot it :-)). I downloaded PuTTY gen from the given
link, as written on that page, and generated a key pair with SSH1 (RSA)
type, because they write "not SSH2". I saved both keys and the fingerprint.
But my public key does not look like in the given example

> ssh-rsa AAAB3NzaC1yc2EB3FWqgypbL ..
>
> It begins with 2047 37  and ends with rsa-key-20120126. And it has
no letters, rather numerals. Is that a problem? In conversions menu I see
an item called Export OpenSSH Key, but it is quite gray and unaccessable.

-- 
Bináris
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Merlijn van Deen]

Hi Bináris,

On 30 December 2011 21:30, Bináris  wrote:

> Hi folks,
> after a few months of IRL activity which prevented me of finishing this
> work, I am on board again and would like to continue. I need the commit
> acces to publish and maintain the script which I hope to be used widely.
>

As far as I am concerned you can have SVN access.

However, before adding your bot to the repository: it should be MIT
licensed, and not GPL - at least as long as bots and framework coexist in
the same directory.

Please see
https://www.mediawiki.org/wiki/Commit_access_requests#Requesting_commit_access
for information on the steps of gaining the actual access.

Best regards,
Merlijn
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Bináris]

Hi folks,
after a few months of IRL activity which prevented me of finishing this
work, I am on board again and would like to continue. I need the commit
acces to publish and maintain the script which I hope to be used widely.

Please respond to my request and support my access. I think my
contributions here in the past years are worth. I made several
modifications to replace.py and some other scripts, including a major
improvement of replace.py (introducing the -save parameter), some bugfixes,
published
http://hu.wikipedia.org/wiki/Szerkeszt%C5%91:Bin%C3%A1ris/Fixes_and_functions_HOWTO,
had a lot of contributions to Pywiki documentation on Meta, and run a
couple of own scripts on huwiki, some of them are listed at
http://hu.wikipedia.org/wiki/Szerkeszt%C5%91:Itt_BinBot_besz%C3%A9l_a_toolserverr%C5%91l.
Thank you in advance.

2011/9/3 Bináris 

> Hi,
>
> I would like to get an SVN access and some help to start.
>
> I need it mainly for inserting and maintaining TOCbot that is under
> preparation (it has worked in huwiki for several months and is now being
> internationalized).
> Information about TOCbot:
> http://hu.wikipedia.org/wiki/Szerkeszt%C5%91:Bin%C3%A1ris/TOCbot
> Description, user guide and bot owners' guide and a collection of examples
> is ready as well as an auxilary script, while the main script is not yet
> public. It will soon be published for test and may need much care in the
> first time.
> I would also like to take part in maintenance of replace.py for what I
> worked a lot already.
> At the moment I am interested only in trunk version.
>
> My SF page: http://sourceforge.net/users/binbot/ -- I don't know how to
> list all my contributions, here appears a part of them since May 22, but
> there are much more. I have also been active on mailing list in the past
> years. Please support and give me technical help to use the system.
>
> --
> Bináris
>



-- 
Bináris
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Bináris]

2011/9/3 Dr. Trigon 

> I hope you are also aware of my bot [1] which is at least somehow
> related to yours. My bot provides an extension to the standard
> watchlist in order to help users to stay up2date in all discussions
> they participate(d). May be you want to have a look... ;)
> May be we could also work together at some points...?
>

Thank you, I didn't know about this. First I want to release my own srcipt.
The two projects don't seem to be closely related, but your one may be
useful, too.

-- 
Bináris
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access request

[Dr. Trigon]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I hope you are also aware of my bot [1] which is at least somehow
related to yours. My bot provides an extension to the standard
watchlist in order to help users to stay up2date in all discussions
they participate(d). May be you want to have a look... ;)
May be we could also work together at some points...?

But I have to admit that I do not have commit access and this is
why may bot is placed in [2]... It is using the trunk only (also).

Greetings
DrTrigon

[1] http://de.wikipedia.org/wiki/Benutzer:DrTrigonBot
[2] https://fisheye.toolserver.org/changelog/drtrigon

Am 03.09.2011 20:09, schrieb Bináris:
> Hi,
> 
> I would like to get an SVN access and some help to start.
> 
> I need it mainly for inserting and maintaining TOCbot that is
> under preparation (it has worked in huwiki for several months and
> is now being internationalized). Information about TOCbot: 
> http://hu.wikipedia.org/wiki/Szerkeszt%C5%91:Bin%C3%A1ris/TOCbot 
> Description, user guide and bot owners' guide and a collection of 
> examples is ready as well as an auxilary script, while the main
> script is not yet public. It will soon be published for test and
> may need much care in the first time. I would also like to take
> part in maintenance of replace.py for what I worked a lot already. 
> At the moment I am interested only in trunk version.
> 
> My SF page: http://sourceforge.net/users/binbot/ -- I don't know
> how to list all my contributions, here appears a part of them since
> May 22, but there are much more. I have also been active on mailing
> list in the past years. Please support and give me technical help
> to use the system.
> 
> -- Bináris
> 
> 
> ___ Pywikipedia-l
> mailing list Pywikipedia-l@lists.wikimedia.org 
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5ijCkACgkQAXWvBxzBrDChIgCeLvofiWAW4PspmwWwaRspwhsk
eQEAoIOJfWbTzEb22dNw/rttkzAaQbAJ
=tNCT
-END PGP SIGNATURE-

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

[Dr. Trigon]

Thanks a lot for the support!!


Am 28.02.2011 03:10, schrieb Tim Starling:
> Done.
> 
> -- Tim Starling
> 
> On 22/02/11 23:19, i...@gno.de wrote:
>> I support his request. He submitted a lot of usefull patches, see
>> r8989, 8985, 8984, 8946, 8652, 8609, 8562, 8527 (I am sure I
>> forgotten some) and he could complete the developer team very
>> well.
>>
>> Greetings xqt
>>
>>
>> - Original Nachricht  Von: "Dr. Trigon"
>>  An:  pywikipedia-l@lists.wikimedia.org 
>> Datum:   22.01.2011 19:07 Betreff: Re: [Pywikipedia-l] SVN access
>> for Lewis Cawte (Lcawte)
>>
>>> Hello all!
>>>
>>> What do I have to do in order to get SVN commit access?
>>>
>>> I already asked a few times... :)
>>>
>>> Thanks and Greetings Dr. Trigon
>>>
>>>
> 
> 
> 
> ___
> Pywikipedia-l mailing list
> Pywikipedia-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
> 


___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

[Tim Starling]

Done.

-- Tim Starling

On 22/02/11 23:19, i...@gno.de wrote:
> I support his request. He submitted a lot of usefull patches, see
> r8989, 8985, 8984, 8946, 8652, 8609, 8562, 8527 (I am sure I
> forgotten some) and he could complete the developer team very
> well.
> 
> Greetings xqt
> 
> 
> - Original Nachricht  Von: "Dr. Trigon"
>  An:  pywikipedia-l@lists.wikimedia.org 
> Datum:   22.01.2011 19:07 Betreff: Re: [Pywikipedia-l] SVN access
> for Lewis Cawte (Lcawte)
> 
>> Hello all!
>> 
>> What do I have to do in order to get SVN commit access?
>> 
>> I already asked a few times... :)
>> 
>> Thanks and Greetings Dr. Trigon
>> 
>> 



___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

[info]

I support his request. He submitted a lot of usefull patches, see r8989, 8985, 
8984, 8946, 8652, 8609, 8562, 8527 (I am sure I forgotten some) and he could 
complete the developer team very well.

Greetings
xqt


- Original Nachricht 
Von: "Dr. Trigon" 
An:  pywikipedia-l@lists.wikimedia.org
Datum:   22.01.2011 19:07
Betreff: Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

> Hello all!
> 
> What do I have to do in order to get SVN commit access?
> 
> I already asked a few times... :)
> 
> Thanks and Greetings
> Dr. Trigon
> 
> 

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

[Lewis Cawte]

On 22/01/11 15:46, Merlijn van Deen wrote:
> As you'll see in the logs below, I'm basicly interested at this point
>
> in time in maintaining the non-WMF family files in the SVN,
>
> This would be nice. However, I'd like to see a cleanup of unnecessary
> family files - now we have got generate_family_file.py, I think a lot
> of files are no longer necessary.
>
I'm happy to help with this, as I know what we're looking to keep (per
our discussion on IRC). :)

- Lewis Cawte
___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

[Dr. Trigon]

Hello all!

What do I have to do in order to get SVN commit access?

I already asked a few times... :)

Thanks and Greetings
Dr. Trigon


Am 22.01.2011 16:46, schrieb Merlijn van Deen:
> Hi again,
> 
> For Lewis, I'll give the +1. Just one comment, though:
> 
> -- Forwarded message --
> From: Lewis Cawte  >
> Date: Tue, Jan 4, 2011 at 10:36 AM
> Subject: Re: [Pywikipedia-l] Commit access requests
> To: Pywikipedia discussion list  >
> My Request
> 
> As you'll see in the logs below, I'm basicly interested at this point
> in time in maintaining the non-WMF family files in the SVN,
> 
> This would be nice. However, I'd like to see a cleanup of unnecessary
> family files - now we have got generate_family_file.py, I think a lot of
> files are no longer necessary.
> 
> and
> working on the i18n translation that I hear you guys are planning to
> work on rather soon. As a member of the translatewiki.net
>  staff, and
> an active user of pywikipediabot, I think it'd be nice to help out
> there.
> 
> Of course siebrand and roberthl already are contacts, but more help is
> always welcome :-)
> 
> 
> Now, as a last comment:
> 
> On 30/12/10 23:57, Rob Lanphier wrote:
>  2.  The access request is from this person:
> http://www.mediawiki.org/wiki/User:Ebraminio
> Any objections to granting access for this person?
> 
> https://sourceforge.net/users/ebraminio
> The translation patches are OK, but this one most certainly is not: this
> patch
> 
>  changes
> the license from GPL to MIT (!) without checking with the original
> author(s). Besides, there is no comment on what this actual change does
> ('hi, this a patch for providing support of links contains unicode
> character.I am used it and working well for me.') only decribes the end
> effect, not the reason it works. Especially when working with
> Unicode<->utf-8 translations, this is important - the current code looks
> like "We'll sprinkle some encode and decodes around and problems will
> magically be solved".
> 
> I haven't seen Ebraminio on the mailing list or IRC either - so no +1
> for Ebraminio from me - at least: not yet.
> 
> Thanks,
> Merlijn
>  
> 
> 
> 
> ___
> Pywikipedia-l mailing list
> Pywikipedia-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l


___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Re: [Pywikipedia-l] SVN access for Lewis Cawte (Lcawte)

[Merlijn van Deen]

Hi again,

For Lewis, I'll give the +1. Just one comment, though:

-- Forwarded message --
> From: Lewis Cawte 
> Date: Tue, Jan 4, 2011 at 10:36 AM
> Subject: Re: [Pywikipedia-l] Commit access requests
> To: Pywikipedia discussion list 
> My Request
>
> As you'll see in the logs below, I'm basicly interested at this point
> in time in maintaining the non-WMF family files in the SVN,

This would be nice. However, I'd like to see a cleanup of unnecessary family
files - now we have got generate_family_file.py, I think a lot of files are
no longer necessary.

and
> working on the i18n translation that I hear you guys are planning to
> work on rather soon. As a member of the translatewiki.net staff, and
> an active user of pywikipediabot, I think it'd be nice to help out
> there.
>
Of course siebrand and roberthl already are contacts, but more help is
always welcome :-)


Now, as a last comment:

> On 30/12/10 23:57, Rob Lanphier wrote:
>  2.  The access request is from this person:
> http://www.mediawiki.org/wiki/User:Ebraminio
> Any objections to granting access for this person?
>
> https://sourceforge.net/users/ebraminio
The translation patches are OK, but this one most certainly is not: this
patch
changes
the license from GPL to MIT (!) without checking with the original
author(s). Besides, there is no comment on what this actual change does ('hi,
this a patch for providing support of links contains unicode character.I am
used it and working well for me.') only decribes the end effect, not the
reason it works. Especially when working with Unicode<->utf-8 translations,
this is important - the current code looks like "We'll sprinkle some encode
and decodes around and problems will magically be solved".

I haven't seen Ebraminio on the mailing list or IRC either - so no +1 for
Ebraminio from me - at least: not yet.

Thanks,
Merlijn

___
Pywikipedia-l mailing list
Pywikipedia-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l