Search results

Jump to: navigation, search

Page title matches

Page text matches

  • .... You can help us by either translating them into your native language or reviewing and correcting them.
    15 KB (2,389 words) - 06:30, 14 February 2009
  • == Content Reviewing ==
    4 KB (526 words) - 11:45, 27 March 2012
  • when a user wants it; Jon Corbet is reviewing the patch.
    121 KB (20,194 words) - 12:31, 1 June 2012
  • * Feedback loop for reviewing the user experience -- how is a country's chosen language, keyboard, activi
    23 KB (3,443 words) - 16:31, 25 July 2013
  • join us advocating for, and/or reviewing shortcomings of these proposals:
    30 KB (4,938 words) - 19:05, 8 January 2010
  • join us advocating for, and/or reviewing shortcomings of these proposals: <CanoeBerry> Benji_Smith: great, please introduce us, reviewing your recent progress and where you're going next and this summer.
    22 KB (3,372 words) - 15:07, 23 April 2010
  • ...ibuted community development of Sugar software and content, guidelines for reviewing and creating great material, and identification and assignment of open task
    22 KB (3,547 words) - 09:38, 26 April 2013
  • ...by their individual contributions, and 20% would go to the Data Base, for reviewing costs.
    17 KB (2,791 words) - 07:42, 27 May 2010
  • I spent the fireworks writing reports and reading code and reviewing scholarship apps. Happily, I could see them outside the window; reading ab
    751 bytes (125 words) - 11:44, 20 December 2009
  • ...=5060 opening the kimono] with regard to the Sugar-XO User Interface (UI). Reviewing the UI docs starting to appear in this Wiki makes it manifest that the mesh
    12 KB (2,017 words) - 10:30, 21 December 2008
  • On reviewing the .info structure, I am wondering why we don't have an *interface* versio
    9 KB (1,394 words) - 14:48, 9 April 2008
  • {After reviewing recent much more detailed explanations in [http://wiki.laptop.org/go/Power_
    10 KB (1,856 words) - 21:58, 12 May 2007
  • join us advocating for, and/or reviewing shortcomings of these proposals: * christophd is reviewing atm
    33 KB (4,926 words) - 15:45, 20 August 2010
  • join us advocating for and/or reviewing shortcomings of these proposals:
    23 KB (3,631 words) - 16:59, 28 August 2009
  • ...r Peru jumping in&mdash;[[IRC]] #olpc-peru & #olpc-es). Translation wise, reviewing the [[:Category:Ongoing Translation]]s would be worthwhile (I know there ar
    6 KB (932 words) - 02:21, 17 September 2007
  • ...cking the proliferation of projects, collections, and related efforts, and reviewing new submissions for quality and audience. Coordinators determine what conte
    12 KB (1,562 words) - 19:09, 13 January 2009
  • 18:28 <|sj|> so if the collection of people reviewing and organizing our 18:31 <|sj|> mchua, if we actually start reviewing and organizing those needs
    22 KB (3,405 words) - 08:41, 25 March 2008
  • ...cation here may confuse a designer trying to design for the system without reviewing the image for aspect reference.
    511 bytes (79 words) - 16:16, 10 March 2007
  • * Non-intrusive -- reviewing should require no work on the part of the content provider. ...arrier to entry -- it should be easy for a new group of reviewers to start reviewing works and revising their internal system, without proving something about t
    6 KB (1,032 words) - 18:13, 28 February 2008
  • As discussed on april 1 -- there is some reviewing that will be core; having an official developer program may mean announcing
    10 KB (1,712 words) - 01:47, 30 January 2008

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)