Hi,
When browsing through [mediawiki]/trunk [1] I see a lot of things that have piled up over the years. Now that we have /trunk/tools [2] and the separate [wikimedia] repository, perhaps some things should be re-organized.
A few examples:
* /trunk/backup: This is the script for generating data dumps for Wikimedia's public wikis. Perhaps move this to /tools or perhaps to trunk of the [wikimedia] repo.
* /trunk/mwdumper: Tool for extracting sets of pages from an MW dump file If this works for regular mediawiki dumps, probably a good one to be moved to /tools
* /trunk/lucene-search-2: Lucene-search 2.1: search extension for MediaWiki Sounds like something that should be in a /libs/ directory of /trunk/extensions/MWSearch or something
* /trunk/wikiSDK: Attempt at creating a developer friendly SDK for MW Again, perfect for /tools probably
* /trunk/wap: Wap Wikipedia. quick and dirty Hack for wap.es.wikipedia.org Doesn't' appear to be used anymore. But since it's used as a fronted to MediaWiki, perhaps go into /tools, or if wikimedia specific, into [wikimedia]
*/trunk/wmfmailadmin: Simple mail account maintenance script. Fairly obvious. [wikimedia]
etc. take a look at the complete list here: http://svn.wikimedia.org/viewvc/mediawiki/trunk/
Just mentioning here on the mailing list in case there are some special dirs that needs special treatment before I make a bold move.
-- Krinkle
[1] http://svn.wikimedia.org/viewvc/mediawiki/trunk/ [2] http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/ (descriptions copied from the README files and/or the initial commit messages)
On 11-09-18 06:18 PM, Krinkle wrote:
Hi,
When browsing through [mediawiki]/trunk [1] I see a lot of things that have piled up over the years. Now that we have /trunk/tools [2] and the separate [wikimedia] repository, perhaps some things should be re-organized.
A few examples:
- /trunk/backup: This is the script for generating data dumps for
Wikimedia's public wikis. Perhaps move this to /tools or perhaps to trunk of the [wikimedia] repo.
- /trunk/mwdumper: Tool for extracting sets of pages from an MW dump file
If this works for regular mediawiki dumps, probably a good one to be moved to /tools
- /trunk/lucene-search-2: Lucene-search 2.1: search extension for MediaWiki
Sounds like something that should be in a /libs/ directory of /trunk/extensions/MWSearch or something
- /trunk/wikiSDK: Attempt at creating a developer friendly SDK for MW
Again, perfect for /tools probably
- /trunk/wap: Wap Wikipedia. quick and dirty Hack for wap.es.wikipedia.org
Doesn't' appear to be used anymore. But since it's used as a fronted to MediaWiki, perhaps go into /tools, or if wikimedia specific, into [wikimedia]
*/trunk/wmfmailadmin: Simple mail account maintenance script. Fairly obvious. [wikimedia]
etc. take a look at the complete list here: http://svn.wikimedia.org/viewvc/mediawiki/trunk/
Just mentioning here on the mailing list in case there are some special dirs that needs special treatment before I make a bold move.
-- Krinkle
[1] http://svn.wikimedia.org/viewvc/mediawiki/trunk/ [2] http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/ (descriptions copied from the README files and/or the initial commit messages)
wikiSDK can be put wherever we archive the stuff that completely failed and we don't need anymore but is good to stick around for historical reference.
That project is from my early days, ;) it failed harder than TitleRewrite.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
On Sun, Sep 18, 2011 at 10:44 PM, Daniel Friesen lists@nadir-seen-fire.com wrote:
wikiSDK can be put wherever we archive the stuff that completely failed and we don't need anymore but is good to stick around for historical reference.
That project is from my early days, ;) it failed harder than TitleRewrite.
That would be /trunk/ATTIC/ :)
-Chad
On 19/09/11 11:18, Krinkle wrote:
Hi,
When browsing through [mediawiki]/trunk [1] I see a lot of things that have piled up over the years. Now that we have /trunk/tools [2]
Most of these things were created after /trunk/tools.
and the separate [wikimedia] repository, perhaps some things should be re-organized.
[...]
- /trunk/lucene-search-2: Lucene-search 2.1: search extension for MediaWiki
Sounds like something that should be in a /libs/ directory of /trunk/extensions/MWSearch or something
It's not an extension or a library, it's a complete Lucene backend server and index update system. The MediaWiki extension (MWSearch) is a client for it.
-- Tim Starling
Just try to not produce conflicts for people when updating. And keep subversion history, obviously. I'm not sure if moving in two steps would be good (svn mv, but first commit the additions, then the deletes), as it would allow for an intermediate step, where you could move things in that revision.
The are files not-handled by subversion, such as extenals (WikiWord folder will be a problem) or modified ones. For instance, if you moved pngds, I would get an error because folder pngds cannot be deleted (I have the three binaries there, thus it would be non-empty).
Maybe post a plan of the moves before? I'm not sure what to do with some projects. When is a project worth enough to be on trunk and when it needs to go under tools ?
On Mon, Sep 19, 2011 at 7:46 PM, Platonides Platonides@gmail.com wrote:
When is a project worth enough to be on trunk and when it needs to go under tools ?
I would't use the phrase "worth enough".
/mediawiki/trunk/tools is for tools related to MediaWiki but not ran inside MediaWiki. Such as the ruby gateway, a WordPress plugin that connects to a MediaWiki instance, independent shell scripts, irc bots connecting to the API, statistics-related tools that scan a mediawiki database.
I think almost everything is eligible to move down a level into /trunk/tools, /trunk/extensions or /trunk/parsers. And then there's several directories that should probably be in the separate Wikimedia repo entirely (things like php, otrs, ubuntu, wikimania)
Ideally trunk would only contain phase3, extensions, tools, parsers and perhaps one or two more.
– Krinkle
On Mon, Sep 19, 2011 at 10:06 PM, Krinkle krinklemail@gmail.com wrote:
/mediawiki/trunk/tools is for tools related to MediaWiki but not ran inside MediaWiki. Such as the ruby gateway, a WordPress plugin that connects to a MediaWiki instance, independent shell scripts, irc bots connecting to the API, statistics-related tools that scan a mediawiki database.
I think almost everything is eligible to move down a level into /trunk/tools, /trunk/extensions or /trunk/parsers. And then there's several directories that should probably be in the separate Wikimedia repo entirely (things like php, otrs, ubuntu, wikimania)
Ideally trunk would only contain phase3, extensions, tools, parsers and perhaps one or two more.
I really don't think it's worth the effort at all. We're ditching SVN within the year anyway, which would be a point where we split all these things into separate repos anyway.
-Chad
On Sun, Sep 18, 2011 at 6:18 PM, Krinkle krinklemail@gmail.com wrote:
When browsing through [mediawiki]/trunk [1] I see a lot of things that have piled up over the years. Now that we have /trunk/tools [2] and the separate [wikimedia] repository, perhaps some things should be re-organized.
I'd recommend against rearranging directories that someone other than you may be using, particularly since we're expecting to work on some git migrations in the next couple months -- this will likely lead to some big rearrangements anyway.
*Planning* how to rearrange them into git modules probably makes sense to start doing.
Actually moving them in SVN without warning and then having Wikimedia's ops people discover that their checkout and package build scripts no longer work would be less happy. :)
-- brion
On 11-09-19 10:50 AM, Brion Vibber wrote:
On Sun, Sep 18, 2011 at 6:18 PM, Krinkle krinklemail@gmail.com wrote:
When browsing through [mediawiki]/trunk [1] I see a lot of things that have piled up over the years. Now that we have /trunk/tools [2] and the separate [wikimedia] repository, perhaps some things should be re-organized.
I'd recommend against rearranging directories that someone other than you may be using, particularly since we're expecting to work on some git migrations in the next couple months -- this will likely lead to some big rearrangements anyway.
*Planning* how to rearrange them into git modules probably makes sense to start doing.
Actually moving them in SVN without warning and then having Wikimedia's ops people discover that their checkout and package build scripts no longer work would be less happy. :)
-- brion
By planning which do you mean: - Deciding what paths we would turn into repos - Figuring out how we would manage a number of git repos instead of one svn repo - Figuring out what kind of workflow we'll use for community commuting etc...
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
wikitech-l@lists.wikimedia.org