Last modified: 2014-02-26 12:55:22 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T46937, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44937 - Schema namespace on Meta-Wiki should have a "fork" tab
Schema namespace on Meta-Wiki should have a "fork" tab
Status: RESOLVED DUPLICATE of bug 45878
Product: Analytics
Classification: Unclassified
EventLogging (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-13 08:53 UTC by MZMcBride
Modified: 2014-02-26 12:55 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2013-02-13 08:53:28 UTC
The Schema namespace on Meta-Wiki should have a "fork" tab. This would allow a user to fork (duplicate) a schema more easily, preferably with attribution in the edit summary.

Filing this as an enhancement request against the EventLogging extension and marking the bug as easy.
Comment 1 Ori Livneh 2013-02-13 09:07:33 UTC
I like the idea. OK.
Comment 2 Ori Livneh 2013-02-13 09:07:51 UTC
I like the idea. OK.
Comment 3 Matthew Flaschen 2013-02-13 09:10:08 UTC
See also https://www.mediawiki.org/wiki/Requests_for_comment/Nonlinear_versioning .

Though for now, this would probably have to be implemented as an effective cut and paste with link to the original in the summary.
Comment 4 MZMcBride 2013-02-13 10:50:58 UTC
(In reply to comment #3)
> Though for now, this would probably have to be implemented as an effective
> cut and paste with link to the original in the summary.

Because this is just a silly enhancement request, I was thinking you could probably do this whole feature in client-side JS. Click "fork" tab --> dialog box for forked page title --> opens new browser tab --> pre-fills textarea with wikitext of most recent revision and fills in edit summary with some kind of attribution (internal link to forked page or permalink to the specific revision ID). Or something.
Comment 5 Ori Livneh 2013-04-15 16:55:34 UTC
I've thought about this a bit more.

We don't actually want forking. Forking doesn't resolve the underlying problem of schema re-use. Forking arguably makes things worse by encouraging the proliferation of minor variances. What we want is a way to re-use and compose existing schema, and the way to do that is to implement JSON referencing, which will make it possible for schemas to transclude other schemas by reference.

*** This bug has been marked as a duplicate of bug 45878 ***
Comment 6 MZMcBride 2013-04-16 01:28:38 UTC
(In reply to comment #5)
> I've thought about this a bit more.
> 
> We don't actually want forking. Forking doesn't resolve the underlying
> problem of schema re-use. Forking arguably makes things worse by encouraging
> the proliferation of minor variances.

Fair enough. Thanks for the pointer to bug 45878. I've added myself to its CC list.
Comment 7 MZMcBride 2013-04-16 01:32:05 UTC
(In reply to comment #6)
> I've added myself to its CC list.

Err, rather, you did when you marked this bug as a dupe. Even better. Thanks! :-)
Comment 8 Andre Klapper 2014-02-26 12:55:22 UTC
[moving from MediaWiki extensions to Analytics product - see bug 61946]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links