647
edits
Changes
mLine 1:
Line 1: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Reverted edits by Walter's rectum (Talk) to last revision by Walter
First to type on your user:talk page, what an honor. When it all seems like too much, as I'm sure it must, I've left something [[User:Cjl/Random_musings| here]] that I hope you might find amusing. [[User:Cjl|Cjl]] 20:56, 15 May 2008 (UTC)
== Thought on translations ==
Before you spend a lot of time on translations via the translations template, consider the potential of the ''GoogleTrans-xx'' templates I'm starting to develop/deploy on OLPC wiki. Note, it will require the same plugin/extension magic-dust currently installed on the OLPC wiki to be sprinkled here before they will work.
*''GoogleTrans-en'' for starting from English page [http://wiki.laptop.org/go/The_OLPC_Wiki#Machine_Translations (example)]. Click on Spanish and continue browsing rest of wiki in espanol inside Google frame.
*''GoogleTrans-es'' for starting from Spanish page [http://wiki.laptop.org/go/Lambayeque (example)]. Click English and see that page and any linked lang-es page in English.
* 20-odd other variations possible
The idea is that you want to lower language barrier, but you don't want your most valuable trilingual (1 lang-en, 2 lang-xx, 3 wiki/Python/C/Linux/Sugar/etc.) assets spending a lot of time on keeping up with rapidly evolving edits. By the time a page becomes stable, it's probably too late to get meaningful input from a mono or bi-lingual non-lang-en audience (like teachers, local coders, etc.).
For wiki pages, I think that any translation '''now''' is better than a great translation '''later'''. Allows you to lower language barrier immediately (in a usually good enough manner) and reserve human translation effort for Pootle and tech-phrasing sensitive pages. Try the provided links to OLPC wiki and let me know what you think. [[User:Cjl|Cjl]] 19:39, 20 May 2008 (UTC)
:I was playing with it on the OLPC site earlier today. I agree, it is a decent compromise that is resource-efficient. --[[User:Walter|Walter]] 21:23, 20 May 2008 (UTC)
== Current events date convention ==
Walter, I'm not sure I get the link-naming convention you are using on [[Sugar Labs/Current Events/Archive]]. The text there that says "2008-06-16" links to [[SugarLabs:Current_events/Archive/2006-06-24]]. Is one start of week and the other end of week? You and I have reverted each other on this (maybe even twice), and that just seems like a silly misunderstanding to have. In the spirit of [http://en.wikipedia.org/wiki/Wikipedia:BRD WP:BRD], I may just be missing the convention you are using and I'd like to I understand it. [[User:Cjl|Cjl]] 18:14, 24 June 2008 (UTC)
:I need to move all the pages to the correct date. I accidentally started naming them based on the date I moved them into the archive instead of the date I created them. --[[User:Walter|Walter]] 21:31, 24 June 2008 (UTC)
::I was assuming the date of publication on IAEP was the operative date and I had crossed-checked against the archives there to do the last rename/relinking I did yesterday, which you reverted today. No point in operating at cross-purposes, so much to do to move forward without tripping over each other. [[User:Cjl|Cjl]] 21:36, 24 June 2008 (UTC)
:::I must be tired (I was up all night flying over the Atlantic and in meetings all day today--hence the late posting). I thought I was exposing the publication dates in IAEP even though the pages in the wiki. I defer to you. --[[User:Walter|Walter]] 21:41, 24 June 2008 (UTC)
::I'll take another pass at it, carefully checking against the IAEP archive pages again. I do much of my wiki editing from 22:00 - 03:00 local time, so I'm just as susceptible to error as the next guy :-) [[User:Cjl|Cjl]] 21:49, 24 June 2008 (UTC)
==notes re sfc transactions==
Sugar Labs is a member project of the [http://conservancy.softwarefreedom.org/ Software Freedom Conservancy], "an organization composed of Free and Open Source Software (FOSS) projects. As a fiscal sponsor for FOSS projects, the Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions." While we benefit from the numerous services provided by the conservancy, we are also under an obligation to abide by its mission--promoting FOSS projects--and work within its administrative structure. Below is a set of administrative procedures for routine transactions with the conservancy. If you have any transactions that fall outside of those listed below, please contact [[User:Walter|the Sugar Labs executive director]].
=== Request for payment ===
Some Sugar Labs projects have a budget (e.g., Google Summer of Code). Typically there is a project leader who has put together a budget that has been vetted by the Conservancy (See [[#Project proposal approval]]). If you have incurred a project-related expense, please submit a copy of your receipt to conservancy AT along with a brief explanation of the expense. Please be sure to include reference to the specific project for which the expense applies.
* lead time of two weeks for proposal reviews; 5% overhead
* invoices, requests for payment to c@ email
* license request--answer these questions:
* finances processed around the ides of each month