User talk:Mstone
welcome!
Welcome to the One Laptop per Child wiki. Please make yourself at home; read through the Table of Contents and FAQ, and take a look around. If you need a general wiki-tutorial, Wikieducator has some excellent ones.
Some possible pages of interest:
Check your preferences and be sure you verify your email address and turn on email notification if you'd like it -- you can find out when your talk page, or any page on your watchlist, is modified. You may want to upload a photo or information about yourself to your userpage (examples: 1, 2).
Some repos details
see Content repository and talk page for starters.
notes on gitweb editing
can you start a gitweb page linked from the git wiki page, describing how one would go about editing documentation for a code project within gitweb? Examples would be most helpful. Sj talk 20:05, 28 August 2007 (EDT)
- I don't know what to write on such a page: since gitweb doesn't provide an editor interface, the appropriate procedure to make a change to the transcluded content is to check out the cited git repo, modify the file, and submit the changes to the owner of the upstream repo by email or by publishing your clone and asking upstream to pull from you. --Ashsong 13:37, 29 August 2007 (EDT)
- Ah. I thought there was a way to add such changes to an automatic untrusted branch... co + local modification + submit-to-someone is much too complicated for small wiki changes, and the cloning would need to take place transparently... Sj talk
- Bernie and I talked about it, and it's not hard, but it requires several hours of work. --Ashsong 16:45, 29 August 2007 (EDT)
- Ah. I thought there was a way to add such changes to an automatic untrusted branch... co + local modification + submit-to-someone is much too complicated for small wiki changes, and the cloning would need to take place transparently... Sj talk
how can we tell what the revision # of the doc being transcluded is, and when it was last edited? that would be most useful to filter up to the wiki page. Sj talk 20:32, 28 August 2007 (EDT)
- This is quite easy to do; we just include a link to the doc's history page. To get to the history page for a doc instead of the raw contents of the doc, change the a=blob_plain; argument of the url to a=history;. For the record, a=commitdiff; also provides an interesting view. --Ashsong 13:37, 29 August 2007 (EDT)
- But programmatic filtering up to the page where it is transcluded? Is there an api call we could make? Sj talk
- Nope. On the other hand, the transclusion currently picks out the most recent version of the page, so (at the moment), it's easy to figure out what you're looking at. --Ashsong 16:45, 29 August 2007 (EDT)
- But programmatic filtering up to the page where it is transcluded? Is there an api call we could make? Sj talk
a mesh of thoughts
Related to our discussions the other night: see User:Sj/U and content network. Still no good conncetions to memebrand, hal, corba or p9 plumbing. --Sj leave me a message 21:23, 8 January 2008 (EST)
- hal and corba came up in discussion of the utility of pyxpcom as general platform, as well :)
thoughts on bundle metadata and required files
see bundle_metadata...
dynamic library use cases and notes
See Dynamic library for a cleaner presentation of use cases for dynamic browsable views. If there are good alternatives to doing this through a local webserver, please mention them... --Sj talk 20:24, 13 February 2008 (EST)
Internship project page model
Take a look at the projects in Category:Summer_of_Content_proposals and see if you can come up with a few dozen of the same for internship project ideas. --Sj talk 22:19, 15 March 2008 (EDT)
Request for getting sponsored for xkeyboard-config
I have applied for xkeyboard-config . Michael Stone/ Dennis please review my request. Thanks --Arjs 12:34, 19 June 2008 (EDT)
US keyboard
I found the whole keyboard situation on the wiki very confusing and I did some work to try to clear it up (even prior to being sysop'ed). Walter was still running things then and he joined in the discussion and approved, so it wasn't just me making things up.
see: Conventions#Keyboard_Layouts_page_naming.2Ftagging_proposal
You just created: OLPC_English_Keyboard. I've just added this cat Category:Keyboard and this template {{Keyboard layouts}} to help it conform.
You deleted:
You edited Template:Keyboard_layouts to repoint to the page you just made, but you did not take care of OLPC_US_International_Keyboard, it still exists (distinct from OLPC_English_Keyboard), and if you are going to delete it too, then you should also clean up the links that would be broken
Leaving those last two steps unfinished could lead to some real confusion. It probably would have been best to just add the text you wanted to OLPC_US_International_Keyboard and then moved it to OLPC_English_Keyboard letting the redirect handle the rest.
Cjl 23:48, 17 July 2008 (UTC)
- I made the edits as I thought best, this gets you to the OLPC English Keyboard page you wanted, but also preserves the edit history from the older OLPC_US_International_Keyboard. I've been watching the SemWiki tests with interest. I may try playing with those features some myself, they look pretty neat. Cjl 01:39, 18 July 2008 (UTC)