18
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − <noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }} − {{TOCright}}</noinclude> − ==Finding answers to help== − For general help on Sugar or about Sugar Labs, please see also − − '''→''' '''[[Getting Started | Getting started]]''' − − '''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs − − '''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''') − − '''→''' '''[[:Category:Help]]''' - pages tagged as 'Help' − − '''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo' − − '''→''' '''http://getsatisfaction.com/sugarlabs''' - our community-powered support site − − '''→''' '''http://launchpad.net/soas''' - our Sugar on a Stick project support site − − '''→''' '''[[Sugar_Labs/Contacts#Forums|Community Forums]]''' - on-line forums with lots of topics − − ===The Sugar Learners' manual=== − {| class="wikitable" − |- − |<span class="plainlinks"> [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]</span> − |available as: <span class="plainlinks">[http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).</span> − |} − ===Sugar [[Glossary|glossary]]=== − : There is a [[Glossary|glossary with commonly used acronyms available here]]. − − {{:Tutorials}} − − ===[[The Undiscoverable]]=== − − : We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it. − − ---- − − ===OLPC Project Help and Information=== − : For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]: − : [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order). − ---- − ===[[Request_New_Features| Request new features]]=== − : Please use our [[Request_New_Features|Request New Features page]]. − : If you can't find your answer, please request one or ''supply one!'' below: − − == Help Requests:== − :Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page. − − :There are also links for new questions on the [[:Category:FAQ]] pages. − ===on Usage === − :First, see the help links above. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − ===on [[Wiki_Team/Resources | the Wiki]] === − :First, see the [[Wiki Team/Resources]] page. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − ===on Submitting a bug=== − :Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − ===on Releases=== − :First, see this page, [[{{Upcoming Stable Release}}/Roadmap]]. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − ===on Distributions=== − :First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − * Live CD in Spanish − *:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. <br> Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public. − *::Contact: yamaplos at bolinux.org − − === on Sugar hardware ports=== − :First, see the '''[[Supported systems]]''' page. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − === on Sugar activities=== − :First, see the [[Activity Team]] pages. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − === on Sugar deployments=== − :First, see the [[Deployment Team]] pages. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − === on Sugar Labs=== − : See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support. − − :Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help. − − * <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem. LEAVE the leading asterisk in the first column AND a blank line before and after your question. Use the [Show preview] button, below the edit window, to check the formatting. Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results. (You may click the {Cancel} link to back out with no changes.) Be bold, we will fix up any mistakes or problems that may occur. --> − − [[Category:General public]] − [[Category:Help]]
Blanked the page