Questions
Is the content writer section referring to the wiki? cwhii
- Yes, I saw this section yesterday and I'm fairly certain that was the intent. You'll notice that the associated teams are the Doc, Wiki, and Marketing teams. Ridderman 16:55, 7 December 2008 (UTC)
Then what about content that is to be included in the product rather than promotional and support content? User:cwhii 2-Feb-2009
- Sorry to have been so long in answering this question... I only just stumbled across it. Content can be bundled for download into Sugar by packaging it in the .xol format (essentially a “zip” file with a .xol suffix). There is some work planned on unifying the format with .xo, the one used for applications (See Features/Sugar_Bundles), and to simplify the process (See Features/Content_support). --Walter 13:09, 10 March 2010 (UTC)
Suggestions
Gary -- this is some really nice work but there are a couple of things which would make it substantially better:
- Clicking on the images should take me to a nice description of the roles, not to the Image pages themselves.
- Oh man, tell me about it. Wikis are designed for copyright reasons to make this as tough as possible on image content. The wiki needs extra plug-ins or custom hacks to make this work properly. I did get one working case after about 3hrs of testing, but it meant images would be hard linked (so the page would need to be manually updated if any get changed), and generate nasty 3 line URL mouse overs (on my browser at least). Best case I can think of is to convince someone to install the custom Image Map plug-in, which has a fair chance of working without breaking the table alignment. I notice fedora made a separate page on their regular web-site [1] just to get this behaviour. --Garycmartin 21:28, 21 January 2009 (UTC)
- Say I want to meet some people from role X. How do I do that?
- Thanks, good idea, each team should list its members. Perhaps the semantic wiki plug-in is worth installing for this (Mel backed off asking for it re: test case content/results). Members should at least make a User wiki page for themselves, a little semantic wiki could then auto generate lists for each team where ever needed. --Garycmartin 21:28, 21 January 2009 (UTC)
--Michael Stone 19:18, 21 January 2009 (UTC)
Countering systemic bias
I'd like to see a project dedicated to identifying systemic bias in the community, and doing specific things to resolve gaps. +sj + 21:09, 17 May 2009 (UTC)
Page Resources
Here's the list of pdf files for those who want to use/modify resolution independent vector version of the artwork, they also include a couple of additional icons not used in the final page design --Garycmartin 12:10, 10 March 2010 (UTC)
- File:Web Developer.pdf
- File:Web Developer BW.pdf
- File:Translator2.pdf
- File:Translator2 BW.pdf
- File:Translator.pdf
- File:Translator BW.pdf
- File:People Person.pdf
- File:People Person BW.pdf
- File:Educator.pdf
- File:Educator BW.pdf
- File:Developer3.pdf
- File:Developer3 BW.pdf
- File:Designer.pdf
- File:Designer BW.pdf
- File:Content Writer.pdf
- File:Content Writer BW.pdf
Do you think there are some easy projects with which I can help Sugar Labs and at the same time gain some practical experience programming?
- We'd love to get you involved. (FYI, there is a group of students working with Sugar/OLPC in a local school. I can introduce you if you are interested.)
- Re: where to get started, there are number of different options. Perhaps the easiest route is to simply take a Sugar Activity that you find interesting and make a modification of some sort. This will get you engaged with the Sugar codebase in a give you a toe hold into getting more involved. Or you could try writing a Sugar activity from scratch (really not so difficult and reasonably well documented these days: http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction). Keep it simple to begin with and well aligned with some personal interest.
- There is a running list of open tickets (bug reports and feature requests) here: http://bugs.sugarlabs.org/. This interface is optimized for the seasoned developer, not newbies, but if you have the fortitude, you will find lots of introductory challenges.
- There is also a Feature request section of our wiki. Many of these project need a champion and again, some are relatively easy to approach as someone new to Python (Features).
- Finally, there is no penalty for trying and not succeeding in any of these tasks. You learn through doing, so jump in.
- regards. --Walter, 10 March 2010 (UTC)