Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On Mon, Mar 12, 2012 at 10:49, Petr Bena benap...@gmail.com wrote: It's true, most of the tools were overtaken by another user, can you tell us which tools are still broken? I myself would prefer to move all these tools to wikimedia labs, as soon as it's possible, which would allow us to manage them together without separating it tool per user (eg no ~soxred/files but toolname/files) where all tools would have own git repository and devs could just update them together and push to production. fwiw, the same thing has been possible on the toolserver for quite a while now: Multi-maintainer projects (MMP) maybe they're aren't used enough when making a tool but (I think) you can't blame the roots for that and (I guess/hope) making new MMPs is a relatively cheap/easy process. -Jeremy (Also, this whole thread belongs on toolserver-l I think?) ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
[Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On 12 March 2012 15:49, Hydriz Wikipedia ad...@alphacorp.tk wrote:
Tparis has the full source code of those tools, and looks like he has
already brought them up on his own account. See
https://toolserver.org/~tparis.
Could we (in general) *please* not do this? If someones tools are important
enough to be taken over by someone else, they are most certainly important
enough for a multi-maintainer project. In {one month, one year, five
years}, Tparis' account will also expire and we will have the same problem
all over again.
Best,
Merlijn
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On Mon, Mar 12, 2012 at 6:59 PM, Merlijn van Deen valhall...@arctus.nl wrote:
On 12 March 2012 15:49, Hydriz Wikipedia ad...@alphacorp.tk wrote:
Tparis has the full source code of those tools, and looks like he has
already brought them up on his own account. See
https://toolserver.org/~tparis.
Could we (in general) *please* not do this? If someones tools are important
enough to be taken over by someone else, they are most certainly important
enough for a multi-maintainer project. In {one month, one year, five years},
Tparis' account will also expire and we will have the same problem all over
again.
Best,
Merlijn
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
That's a good point not to do this ever more. But then we are about to
return to the stable toolserver approach, aren't we? :) By the way
there is a sort of bugs in Soxred's tools concerning language code -
project subdomain conversion which I would like to fix or at least
report them (I can remind that I've already done it once in Soxred's
googlecode issue tracker).
--
З павагай,
Павел Селіцкас/Paul Selitskas
Wizardist @ Wikimedia projects
p.selits...@gmail.com, +375257408304
Skype: p.selitskas
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On 12/03/12 17:05, Paul Selitskas wrote: That's a good point not to do this ever more. But then we are about to return to the stable toolserver approach, aren't we? :) By the way there is a sort of bugs in Soxred's tools concerning language code - project subdomain conversion which I would like to fix or at least report them (I can remind that I've already done it once in Soxred's googlecode issue tracker). I also saw some code to be fixed. Maybe there should be a path for converting an inactive user into a MMP, and keeping the urls (if he were active, he could add 301s himself). ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] How to silence qsub/qcronsub?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is it now usual behaviour that qcronsub adds all command-line options to following calls too? qcronsub [some options] script.py [other options] used to call script.py [other options] but now it calls script.py [some options] script.py [other options] is this a bug or a feature? ;)) Thanks anyway and Greetings DrTrigon On 12.03.2012 00:00, Merlissimo wrote: Hi, i have changed qcronsub, so that the long output about successful submit and output about rejection because job already queued is now suppressed. All other output (e.g. warning) is still shown. Using -verbose enables all output as it was before my change. If you are using -terse (maybe used by some script experts) the job number is still returned. On 08.03.2012 23:13, Platonides wrote: BTW, why is qcronsub at /sge62/bin/sol-amd64/qcronsub ? Wouldn't /opt/local/bin/qcronsub (like cronsub) be more appropiate? I do not have access to other folders and using this path is easier for me to update scripts for different platforms. On 08.03.2012 09:32, Simon Kågedal Reimer wrote: Ah, sorry, that didn't work - can't run qsub directly from cronie since we need to set some environment variables etc. You can add needed environment variables by adding -v option to qsub/qcronsub e.g.: qcronsub -v MYARG1=myvalue,MYARG2=myvalue script.sh There are also other possibilities like adding variables to job context (-ac). More information detailed information are available on the qsub manpage (man qsub). Merlissimo ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9eIpEACgkQAXWvBxzBrDBs0QCcDSFxDgsAEZvbZWtGSY1mkD4s 5DsAniMzUZCVU9w2X7T3KB+Wxj6U+KWX =E4er -END PGP SIGNATURE- ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
Hello, At Monday 12 March 2012 17:24:15 DaB. wrote: Maybe there should be a path for converting an inactive user into a MMP, a MMP is not for collecting all stuff from a user, but for 1 project (side- projects may be included). So a MMP Soxred93-old-stuff is not possible, but a MMP gradient would be. The idea behind a MMP is to develop and maintaince a tool (together), and if no member of a MMP are left, anybody can overtake the MMP. Sincerly, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885 signature.asc Description: This is a digitally signed message part. ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
If you are pushing for an MMP, it would be best not to use my code. It's
shoddy, poorly written, broken, and inefficient. Frankly, I'm amazed it lasted
as long as it did.
-X!
On Mar 12, 2012, at 12:05 PM, Paul Selitskas p.selits...@gmail.com wrote:
On Mon, Mar 12, 2012 at 6:59 PM, Merlijn van Deen valhall...@arctus.nl
wrote:
On 12 March 2012 15:49, Hydriz Wikipedia ad...@alphacorp.tk wrote:
Tparis has the full source code of those tools, and looks like he has
already brought them up on his own account. See
https://toolserver.org/~tparis.
Could we (in general) *please* not do this? If someones tools are important
enough to be taken over by someone else, they are most certainly important
enough for a multi-maintainer project. In {one month, one year, five years},
Tparis' account will also expire and we will have the same problem all over
again.
Best,
Merlijn
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
That's a good point not to do this ever more. But then we are about to
return to the stable toolserver approach, aren't we? :) By the way
there is a sort of bugs in Soxred's tools concerning language code -
project subdomain conversion which I would like to fix or at least
report them (I can remind that I've already done it once in Soxred's
googlecode issue tracker).
--
З павагай,
Павел Селіцкас/Paul Selitskas
Wizardist @ Wikimedia projects
p.selits...@gmail.com, +375257408304
Skype: p.selitskas
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On Mon, Mar 12, 2012 at 4:59 PM, Merlijn van Deen valhall...@arctus.nlwrote:
On 12 March 2012 15:49, Hydriz Wikipedia ad...@alphacorp.tk wrote:
Tparis has the full source code of those tools, and looks like he has
already brought them up on his own account. See
https://toolserver.org/~tparis.
Could we (in general) *please* not do this? If someones tools are
important enough to be taken over by someone else, they are most certainly
important enough for a multi-maintainer project. In {one month, one year,
five years}, Tparis' account will also expire and we will have the same
problem all over again.
Best,
Merlijn
I agree. There's also the issue of updating links all over the place. Where
an MMP would have permanent links, regardless of who maintains it.
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On Mon, Mar 12, 2012 at 5:54 PM, Soxred93 soxre...@gmail.com wrote: If you are pushing for an MMP, it would be best not to use my code. It's shoddy, poorly written, broken, and inefficient. Frankly, I'm amazed it lasted as long as it did. -X! Well, it's been working so far. I'd recommend we do the following: * creating a few MMP projects that cover the tools people use most * make your home directory readable for group 'users' via chmod (except for sensitive files) * watch and see people copy your stuff into the SVN repo for the MMP projects and check them out into the MMP account, and see people open stuff in JIRA and get fixed in svn and pushed live :) -- Krinkle ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
On 12/03/12 19:36, Krinkle wrote: On Mon, Mar 12, 2012 at 5:54 PM, Soxred93 wrote: If you are pushing for an MMP, it would be best not to use my code. It's shoddy, poorly written, broken, and inefficient. Frankly, I'm amazed it lasted as long as it did. -X! Well, it's been working so far. I'd recommend we do the following: * creating a few MMP projects that cover the tools people use most * make your home directory readable for group 'users' via chmod (except for sensitive files) * watch and see people copy your stuff into the SVN repo for the MMP projects and check them out into the MMP account, and see people open stuff in JIRA and get fixed in svn and pushed live :) -- Krinkle It's already user-readable. The only prominent non-readable file is public_html/index.php, and I'm not sure if Peachy/Configs has anything of interest. So assuming I think the steps would be: - X! reopens his account. - Determine the tools requiring a MMP and migrate to a repository. - Redirect the old urls to the new one. - Make the best possible code. :) Given that creating a MMP requires root intervention, and a different ACL, it probably makes sense to use a few broad-scope ones, such as article related tools. I'm a bit concerned about the diversity of the tools made by each of us. Almost every user utilises its own library of files for providing a skin, db access... Which make integrating them into something coherent quite hard. These multiple frameworks may also be an effect of the large applications ban. PS: X!, what are your plans of future? Do you intend to continue maintaining your tools? ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
Platonides platoni...@gmail.com wrote: [...] I'm a bit concerned about the diversity of the tools made by each of us. Almost every user utilises its own library of files for providing a skin, db access... Which make integrating them into something coherent quite hard. These multiple frameworks may also be an effect of the large applications ban. [...] I had similar thoughts recently when faced for the n-th time with accessing Wikipedia per MySQL (on the toolserver) or the API (elsewhere) in Perl. It would be nice to have one module with an interface that can be used by Toolserver users and others as well. Skins fall into this category as well: I think most developers could easily adapt their tools to use a centralized skin, but wouldn't bother to implement one by themselves that is accessible and usable. Tim ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] [Wikitech-l] 403: User account expired toolserver.org/~soxred93
Tim Landscheidt wrote: Platonides platoni...@gmail.com wrote: [...] I'm a bit concerned about the diversity of the tools made by each of us. Almost every user utilises its own library of files for providing a skin, db access... Which make integrating them into something coherent quite hard. These multiple frameworks may also be an effect of the large applications ban. [...] I had similar thoughts recently when faced for the n-th time with accessing Wikipedia per MySQL (on the toolserver) or the API (elsewhere) in Perl. It would be nice to have one module with an interface that can be used by Toolserver users and others as well. Skins fall into this category as well: I think most developers could easily adapt their tools to use a centralized skin, but wouldn't bother to implement one by themselves that is accessible and usable. Right. Or if the Toolserver is horribly lagged, switch to the API silently to get the most recent data. I've had similar thoughts. While we all dream of a world in which there's no duplicated coding effort, the reality of these Toolserver tools is that every developer has a programming language preference. You're Perl, I'm Python, others are PHP. So ultimately, I don't know how much integration there can really be. Consistent styling (importing a common CSS file) is easy enough, though. As long as, y'know, it isn't ugly. ;-) MZMcBride ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
