Re: Desired translation revision control for Gnome CMS: Can someone point me to a working implementation (in any open source CMS)?
El dt 08 de 08 del 2006 a les 22:33 -0400, en/na Marc Laporte va escriure: Can someone point me to a working implementation of this? If someone could reply to wgo L10n workflow http://mail.gnome.org/archives/marketing-list/2006-July/msg00232.html it would be great. The basic point now is: for the Translation team PO files for content is a must. Well, no CMS we know is able to handle PO files as content. We need either a XML import-export mechanism, a serious hack on a CMS, a negotiation with the translators or a bit of everything For any of these options we need to know about the desired workflow. I haven't been able to deduce it from http://live.gnome.org/GnomeWeb/Localization nor from the i18n section at http://live.gnome.org/GnomeWeb/CmsRequirements We will see if we are able to complete the (currently unassigned) goal wgo translated to some GNOME supported languages by October 4th, or if we drop it to the next release... But we need to go forth now with the goal wgo i18n requirements partially implemented - GnomeWeb/Localization if we want to make the appropriate CMS choice. Christian had done almost all the work at http://live.gnome.org/GnomeWeb/Localization , it would be great if could pick this (yes, unassigned) goal and at least make sure we have all the elements clear to pick the CMS that suits best to our desired L10n workflow. -- Quim Gil /// http://desdeamericaconamor.org | http://guadec.org signature.asc Description: Això és una part d'un missatge, signada digitalment -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Testing the cms candidates
CMS sandboxes update: - Tiki: http://gnome.rclaporte.com/ - eZ: http://wgo.mgdm.net/ - Plone: http://demo.gnome-cn.org/ - A Midgard sandbox is underway - Can someone provide a Drupal fresh installation in a server with direct access (for the admin)? ourproject.org is a gforge-based project and we depend on external and strict security policies that might be an obstacle if wanting to try many things quickly. Still no volunteers to check the CMSs. Perhaps we can try a progressive approach, make a first checking iteration to all the CMS and see if all or just some succeed going for a second round. This second round would be more exhaustive. -- Quim Gil /// http://desdeamericaconamor.org | http://guadec.org signature.asc Description: Això és una part d'un missatge, signada digitalment -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Testing the cms candidates
Quim Gil wrote: - eZ: http://wgo.mgdm.net/ The admin bit for this is http://admin.wgo.mgdm.net. If anyone wants to play with that, give me a shout off-list or on IRC (I'm mgdm in #marketing) and I'll give you the password. -- Cheers, Michael -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Defining products list and pages
GnomeWeb/SoftwareMap is now http://live.gnome.org/GnomeWeb/GnomeProducts I've tried to summarize there the agreements, the planning work needs to concentrate now on the draft sections and the update of deletion of the Needs update section. Hopefully this is something Simon can do without much surprises, following the lines of his last email. El dt 08 de 08 del 2006 a les 18:11 +0200, en/na Simon Rozet va escriure: Which contents on this page ? - To start with see the work done by Claus at http://gnome-apps.berlios.de/ , also what he attached at http://mail.gnome.org/archives/marketing-list/2006-August/msg00046.html Claus, if I'm missing other drafts you have provided about product pages please let us know. - A part with structured informations : website, maintainer, ... This part can be machine-generated. Going into details, select the DOAP properties to be used in the product pages - http://www-128.ibm.com/developerworks/xml/library/x-osproj3/ - A free-part wish feature the application in a cool way with screenshots. Right. I think that even this could be shared with the projects via DOAP / syndication. Think that now most of them have websites in just one language, very few have 2 or 3. We are going to translate the product pages in n supported languages. Imagine they could offer these summary pages in their own website with a marketing approach and in several languages, with no extra effort. Example : http://ploum.frimouvy.org/?2006/03/15/100-why-you-should-try-epiphany-as-your-default-browser-with-gnome-214 Well, too long and detailed. A page like this would be useful in a Epiphany in a nutshell page in the Epiphany project page, I think. Do you agree we go for something like a 20sec ad? - Auto-generated. - URL: http://www.gnome.org/desktop/products http://www.gnome.org/products is better. Specially if we aim to cover the 4 release suites, from which just 1 is desktop. Which apps ? I propose to start with a small list of clear candidates (Like gedit, rhythmbox, epiphany, ...) Let's apply the framework of the GNOME release suites proposed by Jeff. Going into details, define a draft list of product pages. IMO it is better to start with few but very well done. For the selection have in mind http://live.gnome.org/GnomeWeb/UseCases So... whit DOAPs, we can auto-generate (in several languages) Going into details, define how this will work. Marketing, developers and translators will be editing the same DOAP files? Where and how? Simon, thank you for your patience. You are about to reach the start of the implementation. :) -- Quim Gil /// http://desdeamericaconamor.org | http://guadec.org signature.asc Description: Això és una part d'un missatge, signada digitalment -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: gnome app pages (was confusingly Gnome Software Map)
Hi, On Tue, 08 Aug 2006 15:33:38 +0200 Quim Gil [EMAIL PROTECTED] wrote: Pragmatism: it is sensible to say that Evolution needs to be featured somewhere in wgo. And we are going to have a list of featured products. Let's move forward. You're leading. It's your decision. Now that the product pages are in the wgo map, it's time to define their components. Anyone to start with a draft? I think I've sent one already. Might be useful to say what you want instead, or what information you're missing. Don't get me wrong. I think most points of the former proposal are valid and should be kept in the current wgo revamp. See http://live.gnome.org/GnomeWeb/NewWgoStructure , I'm asking for selecting and merging. Why don't you work together with Joachim to get an updated version? No offense meant to Joachim but the differences in his proposal that I find useful can easily be merged back into the old one. Some other points might be worth to be discussed; for example, removing 'Foundation' out of the top navigation -- no idea what other think about it. Some of his points I find, ehm, strange. ;-) Again, no offense meant! However, the main problem is: People need to say what points they find invalid about the old one. They must be prepared to explain why, and maybe to provide an example of their idea (Again: Jeff's proposal about embedded sounds cool but I have no clue about the embeddedd stuff and no time to find out.) Otherwise there's no progress here, just changes. Why better and instead? Case studies are also a 2.16 goal: http://live.gnome.org/GnomeWeb/CaseStudies , still unassigned despite their relevance. *Deployment stories and case studies* instead of *awards* -- because the only awards that GNOME got are number 2 places IIRC. I don't think that will create a good impression. ;-) Agreed. I will insist about this unassigned goal: Make wgo explain clearly what is GNOME, why you want to have it and be part of it Hm, you're not looking at me, are you? ;-) There's no single answer to either of these points. One would probably need at least 4 screenshots to make windows people understand what a desktop environment is, and GNOME's even more! It's useless trying to make people understand an abstract concept: Try to explain what a stone is without showing one! Thus I believe: As soon as people installed Linux and GNOME, they will know what a desktop environment is. Why bother with a single explanation? Again, the tour already features many aspects of GNOME, and we can use different explanations throughout the web site. However, I have a draft about the why; reformulated from existing pages. It's attached. A native English speaker is probably able to refine the basic idea without problems; I just picked the words in the headers because of their, well, rhythm. Cheers, Claus Title: Why Choose GNOME? Why Choose GNOME? A dedicated community of volunteers and years of development have made GNOME a valuable choice for home users, companies, and public authorities: It's easy to learn. And use. GNOME's community of professional and volunteer usability experts have created Free Software's first and only Human Interface Guidelines, and all core GNOME software is adopting these principles. Using GNOME requires minimal training, and is easy to support, administer, and install; cutting IT costs for rollout and maintenance. Easy to use also means easy to support: remote system administration cuts down on time spent pacing hallways and waiting in elevators. In addition, extensive manuals and help systems mean you're never without resources. It's honest. No tricks. GNOME is Free Software and part of the GNU project. Its development is open and transparent. An established peer-review process makes GNOME as secure as possible. No spyware or adware is included in GNOME. GNOME's licensing policy also means that you don't have to pay licensing fees or spend money keeping track of licenses, and you can build in-house software royalty-free, even if you choose not to release the source. It's reliable. Granted. GNOME releases are defined by the GNOME Release Team and are scheduled to occur every six months. Strict policies for the stability of our programming libraries ensure that GNOME software is granted to work after new GNOME releases. As an organized community, with a foundation of several hundred members, with teams for usability, accessibility, and quality assurence, and with an elected board, GNOME is a reliable partner for your desktop and development needs. It's widespread. Globally. GNOME is available in your language. Many large software companies do not produce translations for smaller languages, but GNOME makes it easy for dozens of languages both large and small, including Azerbaijani, Arabic, Chinese, Hebrew, Spanish, and Swedish.
wgo structure
--- Claus Schwarm [EMAIL PROTECTED] wrote: Don't get me wrong. I think most points of the former proposal are valid and should be kept in the current wgo revamp. See http://live.gnome.org/GnomeWeb/NewWgoStructure , I'm asking for selecting and merging. Why don't you work together with Joachim to get an updated version? No offense meant to Joachim but the differences in his proposal that I find useful can easily be merged back into the old one. Some other points might be worth to be discussed; for example, removing 'Foundation' out of the top navigation -- no idea what other think about it. Some of his points I find, ehm, strange. ;-) Again, no offense meant! None taken :) My draft is just that, a draft, and only part of one at that. I'm trying to think in terms of paths through the site. My scenarios are these: * new to GNOME: about, why choose, tour, screenshots * new users: tour, link to library, link to support forum * general users: resources for gnome: links to: art themes, more software, support, etc * potential developers: not sure about this one * current developers: or this one ___ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Why GNOME (was gnome app pages)
--- Claus Schwarm [EMAIL PROTECTED] wrote: However, I have a draft about the why; reformulated from existing pages. It's attached. A native English speaker is probably able to refine the basic idea without problems; I just picked the words in the headers because of their, well, rhythm. At first glance this looks good. I like the way points are laid out. 'It's reliable. Granted.' 'Granted' doesn't mean what you think it does in this context. It sort of means 'I grudgingly concede your point' ;) And 'reliable' is a bit too vague, as we could be talking about reliability in the sense that gnome doesn't crash... This is the sort of thing we should use the wiki for, as it makes it easy for several people to work on documents. ___ Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Defining products list and pages
On Wed, 09 Aug 2006 11:46:02 +0200 Quim Gil [EMAIL PROTECTED] wrote: Claus, if I'm missing other drafts you have provided about product pages please let us know. No, I don't think so. Maybe it's useful to remember that the products.html page was in the 'About' section: The navigation of the product pages needs some serious thought unless we want to go deeper than a 3 level navigation or make 'Products' a top-level item. Theoretically, there could be other ways, too: For example, a feature section that changes content every day? I admit this is similar to the gnomefiles 'App-of-the-week' box but I like it. This may be possible even if the backend remains basically static; it would be sufficient if pages are re-generated every day, using a PHP or Python generator code (web coders are more familiar with templates than makefiles, in general, so this shouldn't be a major problem -- and smarty has full language support IIRC) Additionally, after reading Jeff's suggestion, again, and Joachim's navigation draft, we may need to remember that we probably have a top link for third-party developers and potential contribution coders. It's probably more appropriate to feature technical details about the developement platform (and maybe the embedded stuff) there -- instead of using the 'About GNOME' section which is probably more orienteded towards users and the general public. [snip] Example : http://ploum.frimouvy.org/?2006/03/15/100-why-you-should-try-epiphany-as-your-default-browser-with-gnome-214 If anybody wants to write something like the above (more text, less images, maybe), consider to sent it to the GNOME Journal! :-) Cheers, Claus -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Why GNOME (was gnome app pages)
On Wed, 9 Aug 2006 11:29:39 +0100 (BST) Joachim Noreiko [EMAIL PROTECTED] wrote: At first glance this looks good. I like the way points are laid out. 'It's reliable. Granted.' 'Granted' doesn't mean what you think it does in this context. It sort of means 'I grudgingly concede your point' ;) And 'reliable' is a bit too vague, as we could be talking about reliability in the sense that gnome doesn't crash... This is the sort of thing we should use the wiki for, as it makes it easy for several people to work on documents. I wrote the text over a year ago, together with many other pages of wgo. This was before we were using the wiki this extensively, and I used a CVS checkout. If you like to edit the text in the wiki, move it. Cheers, Claus -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Defining products list and pages
On Wed, 2006-08-09 at 12:58 +0200, Claus Schwarm wrote: Maybe it's useful to remember that the products.html page was in the 'About' section: The navigation of the product pages needs some serious thought unless we want to go deeper than a 3 level navigation or make 'Products' a top-level item. When I was writing my BSc thesis on accessible CMSs, I did some research on navigation. According to [1] the optimal size for a menu is about 5-7 entries, and that they are preferably shallow, so avoid deep hierarchies. A completely filled 3 layer menu with 7 entries each provides for a whopping 343 pages! I'm sure there is also googleable info on this topic. [1] Stephan Lamprecht. Webdesign-Handbuch (2001, Carl Hanser Verlag) -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: wgo structure
On Wed, 9 Aug 2006 11:19:18 +0100 (BST) Joachim Noreiko [EMAIL PROTECTED] wrote: None taken :) Thanks. :-) I'm trying to think in terms of paths through the site. My scenarios are these: * new to GNOME: about, why choose, tour, screenshots * new users: tour, link to library, link to support forum * general users: resources for gnome: links to: art themes, more software, support, etc * potential developers: not sure about this one * current developers: or this one Cool! I also used a path model: 1. New visitors probably want to know more about this thing called GNOME. 'About' has the why, the tour, comments from others, an introduction to products, etc. -- a sales folder for the general public. 2. Then, you may want GNOME: 'Download' has links to the LiveCD, to distributions, release notes, etc. I also thought about calling it 'Install'. 3. Then, you may need help: 'Support' has all the links. 4. Then, you may want to get more active: 'Community' has the links. 5. Then, you may want to contribute or start your own thing: 'Development' introduces live.gnome.org and library.gnome.org, and provides pointers for third-party developers. (I also thought about calling it 'Technology' but Thos rejected it.) 6. Then, you may want to know more about GNOME's legal aspects: 'Foundation' has it. Theoretically, this could be moved elsewhere but there's a lot of content, so moving it would probably break a three-level navigation. 7. In some rare moments, you need to contact GNOME: Click 'contact' and you get a snail mail adress, and some pointers to special interest sections (press, etc.). In other words: The most important sections are first, the less important sections are last. The section names are hopefully concrete enought so visitors will get an initial idea, but not *that* concrete so we're still able to handel additional stuff. For example, you mentioned 'webmaster' in your draft: that could go into 'Contact'. You mentioned 'Certification': that could go into development. A sitemap link as mentioned by Quim could go into the footer -- it's a usual place for sitemap links. I admit 'Support' and 'Community' is a little bit fuzzy but we may point to commerical support companies one day. The navigation is usually just two levels deep, with about 8 pages or sections each. There are just some exceptions like the tour, and the release notes, and some foundation stuff, maybe, that makes a third level necessary. Overall, I think, the layout is sufficient. Cheers, Claus -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Latest Logo
Are we still using the usual logo for the new wgo? Or is there another one we are using... -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Getting GNOME banners created
Hey all, Jorge and I are headed to LWE:SF next week and I discovered that we have no banners. I thus decided to take this into my own hands and get one printed. However, I need feedback on the attached file within 3 hours, in order for them to get it printed by Monday, for me to go. Corey official-desktop-happy-corey.svg Description: image/svg -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
