SMWCon Fall 2014/Create camp
- 1 What is it about
- 2 Location and Schedule
- 3 Participants
- 4 Ideas
- 5 Challenge 1: Syncing wikis - “Gitify MW”
- 6 Challenge 2: Wishlist for MediaWiki Cooperation. Location: Library
- 7 Challenge 3: Putting extensions into composer
- 8 Challenge 4: Improving SMW Extension Documentation
- 9 Challenge 5: Recovering HaloACL documentation
What is it about
The create camp / hackathon / editathlon / hackay or whatever you want to call ist is a free event (you can attend wheter or not you are registered for the conference. The idea is to get people to gether to do one or more of the following things
- write code
- write documentation
- do testing / bughunting
- configure wikis
- edit articles
- brainstorm for marketing / community ideas
Ideas for the tasks will be collected here (see below) as well as on the SMW Conference. The concrete tasks to be addressed will be discussed at the beginning of the hackday.
Location and Schedule
- 9:30 - 10:00: Arrival, morning coffee, set up
- 10:00 - 10:30: Exchangin ideas for the day: formulating challenges
- 10:30 - 12:30: creating stuff
- 12:30 - 13:00: current status
- 13:00 - 13:30: lunch break (pizza)
- 13:30 - 16:00: creating stuff
- 16:00 - 17:00: round up of achievements
Please feel free to add your name to this list to show your interest. When you register for the conference, you can check if you are intersted in this free event. If you are on Meetup, you can also sign up there: http://www.meetup.com/Semantic-MediaWiki-Austria/events/181484182/
- Bernhard Krabina, KDZ - Centre for Pubic Administration Research
- Joachim King, bsb-muenchen.de
- Dave Brennan, Steria UK Ltd
- Toni Hermoso
- James Montalvo, NASA
- Daren Welsh, NASA
- Ali King
- Robert Ulrich (re3data.org)
- This could be you. :)
20 Participiants of the SMWCon registered for the CreateCamp as well. We also have a Meetup Group: http://www.meetup.com/Semantic-MediaWiki-Austria/events/181484182/
Note: content below auto-generated from Google Doc using wikify.
- SMW Hooks documentation and examples
- Test LUA-support for SMW (works, but is not directly related to SMW)
- Case-insensitivity for SMW queries
- Bidirectional transclusion labels: to aid in reuse of content throughout the wiki, provide labels where content is transcluded from. This makes it easy to see where content is coming from. Also need method to show where content on a page gets transcluded to.
- Provide user icons for Extension:SemanticComments (partly done, but there are some more things left to do)
- document good usable skins on semantic-mediawiki.org
- Use Extension:WatchAnalytics to direct users to articles they may be interested in
- Sync data between SMW websites: See Extension:DSMW.
- MABS (Multi-lateral Asynchronous Bilateral Synchronization): Method to allow people to disconnect from a wiki, but bring a copy into the field and while in the field make edits that can be synced back to the central wiki when they come back from the field.
- Starter kit with templates, exportable, for new users: so many templates/forms on wikipedia and SMW, would be nice to generate start point. Wikipedia is difficult to import from due to the fact that templates have so many dependencies (note: now Wikipedia templates are highly dependent upon Lua/Scribunto).
- Bundling extensions with Composer: Make common extensions Composer-compatible so we could “bundle” extensions together simply by creating composer.json files. https://wikiapiary.com/wiki/Extension:Extensions
- Semantic forms file upload bug: when re-uploading the same file
- Make semantic project management work again: Extension:Semantic Project Management is unmaintained.
- Query (incomplete/parts of) dates: This can be achieved with Parser Functions, but it would be better if it was native to SMW.
- Regain documentation of HaloACL and improve (Test HaloACL, but we don’t have the code yet, but it will be on GitHub here (hopefully) in the future)
- Could it be possible to make HaloACL work without patching? What would it take to modify core to do this simply with hooks?
- Wishlist for MediaWiki Cooperation
- Also, perhaps a repair list - improvement on semantic-mediawiki.org (including votes on business value perceived)
- Test and configure skins (Foreground skin: http://foreground.thingelstad.com/ )
- Sort semantic results by category (confirmed from Jeroen that this is not possible currently)
- Resume Dump HTML (http://www.mediawiki.org/wiki/Extension:DumpHTML): See current discussion on wikitech mailing list: http://www.gossamer-threads.com/lists/wiki/wikitech/512415?page=last
- Conditional formatting in query results, maybe with SemanticCompoundQuery, maybe with Lua templates?
Challenge 1: Syncing wikis - “Gitify MW”
Collaboration on https://github.com/SMWCon-2014-Fall
- Lex, Dave, Daren
Initial Ideas for Functionality
- Clone a wiki to localhost
- CRUD a MW Clone
- Sync from localhost to master
Issues to Consider
- Case: RemotePerson creates page “Strudel” and LocalPerson also creates page “Strudel”, then you have a conflict.
- The program must address the conflict (like git) and request user direction for actual conflicts that can’t be merged.
- Case: RemotePerson creates page “Apple Strudel” and LocalPerson creates page with essentially the same material, but with the different name “Apple Flavored Strudel”.
- How can the program realize these differently named pages are related?
- Human verification of synchronized data
- Consider marking content that has been added/merged/deleted as “auto-merged but not reviewed by human”
- What about https://www.mediawiki.org/wiki/Extension:DSMW - does it fit to your requirements? if yes, it maybe just needs to be updated. https://github.com/momo54/DSMW/wiki
- DSMW was tested with MW 1.16.4 and SMW 1.6.1. Was not easy to setup, somewhat awkward user interface. Does not recognize conflicts, just adds new page versions, though it should have conflict resolution. Unknown if it works with more recent versions.
Challenge 2: Wishlist for MediaWiki Cooperation. Location: Library
- Bernhard, Sabine, Alina
- HaloACL testing, documentation and avoiding patching in future. How to get MediaWiki.org to keep things in core that we need for HaloACL New HaloACL GitRepository : https://github.com/HaloACL/HaloACL1.8
- Extension documentation on mediawiki.org: power it by an SMW instance: show showcase of updated smw.referata.com
- Extension repository: Drupal/Wordpress: browse for plugins/extension, click on “install” or “upgrade”
- precondition: extensions moved to composer? requires detailed analysis
- what about “uninstall” - solved with a)
- deactivate vs. uninstall
- where to put code/documentation: clear guidelines for developers: github used by many) or gerrit (official, with translatewiki support) - mirroring: how to do this, needs to be documented, ask Jeroen). move from gerrit to phabricator?
- directions on how to update existing extensions
Maybe we should also have an SMW powered skinning documentation (analog to the (SMW) extensions
- What’s happening with Athena? https://www.mediawiki.org/wiki/Athena If going on, could broader community benefit?
- See also Winter: https://www.mediawiki.org/wiki/Winter
- Bootstrap extension: http://www.mediawiki.org/wiki/Skin:BootStrapSkin
- See also the skin mentioned at the conference: http://www.mediawiki.org/wiki/Skin:Chameleon
- See also https://github.com/thingles/foreground/
- Other: See the list compiled for SWM+ https://web.archive.org/web/20120814124853/http://www.smwplus.net/index.php/Planned_features_for_SMW%2B/Results_of_survey
- Address companies (MW/SMW) users/integrators
- for funding, you need a legal body (foundation), for an important legal body, you need big players
- address big wikis: https://wikiapiary.com/wiki/Main_Page
Challenge 3: Putting extensions into composer
- Ali, James
Code will be here:
https://github.com/SMWCon-2014-Fall/MediaWiki-Composerify (another ify-ification)
Some extension developers do not want Composer support due to the fact that it makes it difficult/impossible to disable extensions. See discussion here:
Semantic Bundle Extensions:
- Semantic Forms (high priority, perhaps high difficulty)
- Semantic Compound Queries
Semantic Internal Objects(low priority, since SIO is really just a wrapper for Subobjects now)
- Semantic Drilldown
- Semantic Maps
- Semantic Watchlist
- Semantic Forms Inputs
- Semantic Image Input
In Semantic Bundle, not specifically "semantic" though:
- Admin Links (James has completed code changes, have not been accepted into Gerrit yet. See https://gerrit.wikimedia.org/r/#/c/142763/)
Approved Revs(changes pending in Gerrit)
- Data Transfer
- External Data
- Header Tabs
- Page Schemas
- Replace Text
Other popular extensions (from WikiApiary popular extensions list):
- Parser Functions
- Syntax Highlight
- Wiki Editor
- Semantic Comments
- Semantic Glossary
Semantic extensions on WikiApiary:
Note on Packagist.org: you can create “vendor” names other than your own username. Example: James Montalvo maintains the “EnterpriseMediaWiki” username on Packagist, but this user “owns” packages like “mediawiki/talk-right” (see below):
- Talk Right: https://github.com/enterprisemediawiki/TalkRight
- NumerAlpha: https://github.com/jamesmontalvo3/NumerAlpha
- HeaderFooter: https://github.com/enterprisemediawiki/HeaderFooter
- Admin Links: (pending Gerrit patch | unofficial GitHub)
See the minimum required composer.json file at https://github.com/SMWCon-2014-Fall/MediaWiki-Composerify
Challenge 4: Improving SMW Extension Documentation
Improving documentation of existing SMW extensions in semantic-mediawi.org http://semantic-mediawiki.org/wiki/Help:MediaWiki_extensions
- Toni, Nicolas, Joachim
Create a template, form, etc. for extensions. Syncing with MediaWiki?
- https://semantic-mediawiki.org/wiki/Help:Extensions and http://semantic-mediawiki.org/wiki/Category:SMW_extensions so why have bothe a text-only-list and a form/template-system. And why not advertising the form/template-system?
- http://smw.referata.com/wiki/Special:BrowseData/Extensions (seems to be out of date, unique feature: documents sites who use it)
Do main landing pages of developer-docu make (extension) developers aware of Git/Github as current recommended repository? (Stefan)
- http://www.mediawiki.org/wiki/Developer_hub (Source code is managed using the Git)
- http://www.mediawiki.org/wiki/Manual:Developing_extensions (only mentions Example extensions in Git)
- http://en.wikipedia.org/wiki/MediaWiki_extension (also Gerrit is mentioned)
- Question mailing list about relation of semantic-mediawiki.org and smw.referata.com - maybe combine or better integrate? (Bernhard)
- Update Form/Attributes/Templates on Referata for Extension documentation. Look at mediawiki.org documentation of extensions and make it better, semantic! Why not advertise the SMW-powered forms/templates on semantic-mediawiki.org? Should be a use-case for mediawiki.org extension documentation
- Which properties to use additionally, Suggestion (taken from mediawiki.org)
- release status ("stable" ..)
- implementation ("parser function", ...)
- short description (?)
- latest version/ last modified
- dependency mediawiki-version (and “tested with version …”)
- dependency php-version (and sql-versions other server stuff?)
- database-changes (yes/no)
- documentation link
- hooks used
- links codematrix etc. (or direct download counter?)
- rating? (functionality, easy to use 1-5, simple “likes”…?)
- Add to MediaWiki Cooperation todo-list: talk to mediawiki.org about better documentation (Bernhard)
Challenge 5: Recovering HaloACL documentation
- Oliver , Robert
- Challenges to solve
- Where to put the documentation
- Basically there is the question where to put the documentation, that the problem of the halo-wiki doesn’t happen a second time.
- https://www.mediawiki.org/wiki/Extension:HaloACL now points to https://www.mediawiki.org/wiki/Extension:Access_Control_List
- There is a maintained fork of the HaloACL, but is cut down to mediawiki missing the SMW-Stuff. Maybe collaboration with the developer would be a good idea
archive.org is not complete
Some pages are not indexed
The available sites for the HaloACL differ in the version, e.g. there is some documentation for Version 1.4, some for 1.3, 1.7, etc.
Redundancy: Between Documentation of different versions on archive.org and documentation included in sourcecode-zipfile (describes version 1.4, points to docs for 1.3)
- Documentation is protected but available for me (Robert)
- Move page content from the protected wiki
- “Refactor” the documentation and put it online again
- GFDL and CC-BY
- Original information is published under the GFDL. Anyone knows how this is compatible with CC-BY?
- Move from 1.2 to CC seems possible
- Where to put the documentation