Re: GUADEC leaflets
Hi Murray, On Tue, 2006-10-24 at 17:17 +0200, Murray Cumming wrote: But as usual with our GUADEC stuff, it doesn't make the GNOME name and GNOME logo clear enough. When someone looks at this, he should see immediately see that it's all about GNOME. We keep neglecting our brand. I agree this was a problem in the past, but I think we improved this a lot in Vilanova 2006. If you found the GNOME brand was also neglected in last GUADEC please provide examples so the Birmingham team can learn from recent mistakes. -- Quim Gil /// http://desdeamericaconamor.org | http://pinguino.tv signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GUADEC leaflets
On Wed, 2006-10-25 at 09:11 +0200, Quim Gil wrote: Hi Murray, On Tue, 2006-10-24 at 17:17 +0200, Murray Cumming wrote: But as usual with our GUADEC stuff, it doesn't make the GNOME name and GNOME logo clear enough. When someone looks at this, he should see immediately see that it's all about GNOME. We keep neglecting our brand. I agree this was a problem in the past, but I think we improved this a lot in Vilanova 2006. If you found the GNOME brand was also neglected in last GUADEC please provide examples so the Birmingham team can learn from recent mistakes. Yes, GUADEC 2006 was the best yet and an example for Birmingham. It was only the logo that I didn't like, but I can't complain about everything. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
marketing-list tiny reorg
Do you think it makes sense to - move back to gnome-web-list all the web development discussion - create [EMAIL PROTECTED] and move there all the related topics This way this list will have more focus on the hardcore marketing topics. The marketing team needed to take the lead of the wgo revamp and moving the discussion to this was appropriate. Now we have a wgo plan made with a marketing view, and all the implementation process can be discussed in gnome-web-list. I fear keeping the web development threads here will make some marketing lovers stop reading marketing-list, while many web brains in gnome-web-list won't notice discussion that could interest them. We can keep discussing here web related topics if they have to do with marketing: wgo strategy, content, and so on. About the events, this is a topic we need to discuss more and better. I feel there is more people interested on this, but 'event people' don't always match with 'marketing people' and they might be get bored with other topics discussed here. And viceversa. Do you also think there is enough meat to feed an autonomous events list? -- Quim Gil /// http://desdeamericaconamor.org signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
The wgo CMS can't wait more
Gergerly is missing, I wish he is doing well and everything. We need to choose a CMS with or without him, otherwise the timeline gets compromised. Greg had made a perfect plan we haven't followed. I'm going to be the bad boy and suggest a non-perfect-at-all plan with the aim of getting to a conclusion soon. Sorry, I think this is all we can do at this stage. Now we know that the wgo site itself is not big deal from a content management perspective. - The only tough bone is the localization, a big bone though. It seems that XML import/export is the bottom line to find a workflow compatible with the i18n needs. The L10n features and performance of the CMS are crucial. - We have a lookfeel approach we can test against: CMSs not able to generate pages looking as we want can be discarded. - An enjoyable learning curve, good documentation for admins and editors and responsive support is also needed so new contributors can start helping without learning an obscure bible. - Proved security and a good upgrade policy. Unsecure and outdated CMSs are a plague and we need to fight it. - A robust user management with fine grained permissions and the possibility to integrate users with other platforms is something to be considered as well. Not essential now, but something for the future. But all the previous is useless if we don't have anyone willing to setup and custom the beast, so I will add to the list: - Experienced contributors willing to install, custom and assist the 2.18 release, from now until the end in March. Names and surnames, and probably also a server to mount the beta system that will be moved to the GNOME servers once tested (unless the sysadmins have a different plan). Have your say about this plan. Based on these criteria we will discarding CMS candidates one by one in the following days. -- Quim Gil /// http://desdeamericaconamor.org signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
Drupal it is ! ;-) Sorry, I'm a sucker for it as its the easiest to custom-theme. Thoughts ? -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
2006/10/25, Andy Fitzsimon [EMAIL PROTECTED]: Drupal it is ! ;-) Sorry, I'm a sucker for it as its the easiest to custom-theme. Thoughts ? I like Drupal, too. I find it quiet handy and easy because everything makes sense. My other experiences with CMS are mainly XOOPS (which i think is much worse), TikiWiki (too big), Zope (argh...), Mambo (never worked on my installations) and WordPad (which is a blog, not CMS). What I like most is the ability to work with many subdomains. I like Python but Zope was always a bit messy in my view, maybe this is different with Plone, which i have not tested, yet. Thilo -- Blog: http://vinci.wordpress.com Linked In: http://www.linkedin.com/in/tpfennig -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
On Wed, 2006-10-25 at 11:36 +0200, Thilo Pfennig wrote: 2006/10/25, Andy Fitzsimon [EMAIL PROTECTED]: Drupal it is ! ;-) We have been already into this game of I prefer this, That is cool. If you want to be helpful selecting the CMS at this stage do the following: a) Suggest improvements to the criteria of my previous mail at http://mail.gnome.org/archives/marketing-list/2006-October/msg00078.html b) Based on these criteria, tell which candidate you find to be the less appropriate for wgo from the 5 listed at http://live.gnome.org/GnomeWeb/CmsRequirements and why. Anything out of this risk to fall into the categories of deja-vu, noise or yet more insightful thoughts not that useful to make a good CMS selection. Sorry for setting such strict rules for this game, but it has taken too long and we need to find a common agreement on something. -- Quim Gil /// http://desdeamericaconamor.org signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: marketing-list tiny reorg
Hi, Jeff Waugh wrote: quote who=Quim Gil Do you think it makes sense to - move back to gnome-web-list all the web development discussion Yes please! But please bring it back here when we start talking about content rather than form. - create [EMAIL PROTECTED] and move there all the related topics Naw, I think that's definitely worth keeping here. More mailing lists is usually a bad idea. Events need to be a big part of our marketing effort. Complete agreement. Cheers, Dave. -- David Neary [EMAIL PROTECTED] -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
Hi! On Wed, October 25, 2006 12:04 pm, Quim Gil wrote: Greg had made a perfect plan we haven't followed. I'm going to be the bad boy and suggest a non-perfect-at-all plan with the aim of getting to a conclusion soon. Sorry, I think this is all we can do at this stage. Understandable. The selection process has been stalling the whole autumn. In light of this, let me answer the requirements you listed with how Midgard CMS supports them. - The only tough bone is the localization, a big bone though. It seems that XML import/export is the bottom line to find a workflow compatible with the i18n needs. The L10n features and performance of the CMS are crucial. Midgard has a system called MultiLang which allows content to be stored with multiple translation. A language has to be selected to be the default language (lang0) on top of which the other translations are made. Content import/export can be done in XML format (currently a custom format but we're considering XLIFF as well). - We have a lookfeel approach we can test against: CMSs not able to generate pages looking as we want can be discarded. Midgard does not impose any limitations on the templates used, so this is completely up to you guys being able to translate your lookfeel wishes into XHTML and CSS. - An enjoyable learning curve, good documentation for admins and editors and responsive support is also needed so new contributors can start helping without learning an obscure bible. The Midgard Documentation wiki (http://www.midgard-project.org/documentation/) and the IRC channel (#midgard in freenode) are good places to start. It has to be noted though that most active Midgard community members are located in the European time zones. - Proved security and a good upgrade policy. Unsecure and outdated CMSs are a plague and we need to fight it. Midgard should be on quite good grounds here. - A robust user management with fine grained permissions and the possibility to integrate users with other platforms is something to be considered as well. Not essential now, but something for the future. Midgard has comprehensive Access Control Lists support, and is able to do authentication against external sources like PAM and Kerberos. - Experienced contributors willing to install, custom and assist the 2.18 release, from now until the end in March. I would like to offer the services of my company, Nemein for this on pro bono basis. We're currently doing a Midgard deployment also for the Maemo community: https://garage.maemo.org/pipermail/maemo2midgard-discussion/2006-October/00.html Quim Gil /// http://desdeamericaconamor.org /Henri -- Henri Bergius Consultant Partner, Nemein [EMAIL PROTECTED] Midgard CMS www.midgard-project.org -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
GNOME Screenshot Idea
Inspired from Dave's latest blog post about it's important to be free, not only being feature perfect of FX, an idea poped up into my mind, but my artistic skills (if any) don't let me to do it. Therefore I thought some gfx artist might be interested in it, so I wanted to share it in here. Think about a regular GNOME desktop composed of text (sources) with a slogan like It's open enough.. There used to be famous penguin imaged created by linux kernel sources with ascii I remember. Maybe we can create such an image as well. There must be some tools to do this with ascii but it is not needed to be an ascii. Would it be possible to fit most of the panel sources in panel area, and other GNOME sources into desktop by using very small font sizes? I know this is not very bright idea but it would be at least a good meme to put open source, which is actually not equivalent to free software but still something, into a visual perspective. Sharing it in here so that some artist having insomnia to find something to in their spare time. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: community.gnome.org (was Re: [Fwd: GnomeWeb 2.18 goals])
--- Quim Gil [EMAIL PROTECTED] wrote: On Mon, 2006-10-23 at 09:34 +1000, Jeff Waugh wrote: What on earth is community.gnome.org? As for today it is a launcher from the general nav bar to the GNOME is People subsites: * Planet GNOME * GUADEC and other event subsites if appropriate i.e. Foro Brazil * The GNOME Foundation * ... and all the official regional sites. I believe there is potential content to justify such subdomain, although I haven't got the time to extract yet the related use cases. However, it is clear that we are going late and short of resources on this 2.18 release, so maybe we could do something a bit more straightforward by now: - Take out Community from the General nav bar and add Planet and Foundation. - Link GUADEC and other event subsites from news.gnome.org (News in the General nav bar) - Create a page in wgo under About or Get Involved listing the regional subsites. The General nav bar would be then: (GNOME logo) | News | Planet | Projects | Art | Support | Development | Foundation Foundation being on the General nav bar is probably a good thing. Other than that, it's getting long and messy. Put Planet in with News. Shame about the regional sites getting hidden. As some of them carry news, maybe link them from News also. Send instant messages to your online friends http://uk.messenger.yahoo.com -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
GNOME Logo Branding Guidelines Concerns
Hi, So for a while now I've been working at establishing a set of guidelines for the GNOME brand, including the GNOME logo. An issue has come up and I wanted to ask you all for your thoughts on it: The GNOME 'sublogo' guidelines [1] may be of concern with respect to the defensibility of the GNOME foot's trademark. (See discussion at [2]). One thing that's been done with Fedora's logo is establish at set of lean strict guidelines [3], and request that all folks wanting to use the logo email [EMAIL PROTECTED], a ticket system by which people tell us how they plan to use the logo and send mockups/sketches if required (this has happened in the past for magazine cover designs for example.) If approved, we send them the SVG files and a license agreement for usage of the logo. If not approved, we work with them to help them meet the license agreement usage guidelines. I think that a model like Fedora's might be a bit overkill for GNOME's full brand - but it may be useful for the sublogos specifically. I do think that having guidelines for creative sublogos that relate to the project's mission/goals is a real benefit. My rationale is: (1) Folks are probably going to create them anyway, so we may as well provide guidelines for them to do so in a consistent manner that extends rather than clashes with the brand. (2) The alternatives are not as nice: (a) having rather bland logos that all look the same besides the small sublogo text, or (b) having logos for subprojects that have nothing to do with GNOME's brand and thus we lose an opportunity to make our brand more visible and we lose an association with a project. We could set up a sublogo approval email address, and we could state in the guidelines that folks must submit their sublogo designs to that address for final approval before they may use them. I would be willing to handle these approvals - I do so for Fedora's logo now, so I have some experience with this sort of thing. The reason I bring this up now is just because the guidelines are out there on the wiki now. I marked the sublogo guidelines in particular with the caveat that they have not been officially approved by the board and any designs should be run by the board. So my questions for you folks are: (1) Are there any objections to the proposed sublogo guidelines? Do you think they are too restrictive or too permissive? (2) Do you think the 'creative' sublogos approach is entirely more risk than it is worth? Should we just not allow for sublogos, or only allow for sublogos that use the 'stock' GNOME foot logomark? (3) Do you think having an approval system for sublogos would be an acceptable requirement? Should we contact a lawyer to get some advice? Discuss! :) Thanks, ~m [1] http://live.gnome.org/BrandGuidelines?action=show#head-fd7481407393ff9e54fae8ed1d9f8323547ea88b [2] http://mihmo.livejournal.com/31832.html [3] http://fedoraproject.org/wiki/Logo/UsageGuidelines -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Logo Branding Guidelines Concerns
On Wed, 2006-10-25 at 10:50 -0400, Máirín Duffy wrote: [snip] (2) Do you think the 'creative' sublogos approach is entirely more risk than it is worth? Should we just not allow for sublogos, or only allow for sublogos that use the 'stock' GNOME foot logomark? [snip] Máirín is asking this partly because I think that some of the existing sub-logos on that page break our own rules about how to use the logo. For instance, not using complex pattern fills (instead of a solid color), and not letting other elements (the cup or the brush) overlap or collide with the logo. I think these rules are important - to keep the brand visually distinct and - because I think the lawyers told the board that it was necessary. Thanks Máirín. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Logo Branding Guidelines Concerns
Hi Murray, Murray Cumming wrote: Máirín is asking this partly because I think that some of the existing sub-logos on that page break our own rules about how to use the logo. We make the rules. Trademarks are about quality control and corporate image. So we can approve logos which are stylish and which clearly stay GNOMEy if we want. I think these rules are important - to keep the brand visually distinct and - because I think the lawyers told the board that it was necessary. The feedback we got from the lawyers (through Tim) was that the plain foot is easier to trademark, and thus easier to protect. At least, that's my recollection. As it happens, the plain foot is not registered - the old rock-foot is. That's why we still use TM rather than R with the plain black foot. (note: we can use R with the GNOME name, and we probably should start getting into the habit). I disagree with you that we need to have plain black to protect the brand - I think there's more value in allowing good variations of the foot to develop. Cheers, Dave. -- David Neary [EMAIL PROTECTED] -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Logo Branding Guidelines Concerns
quote who=Máirín Duffy (1) Are there any objections to the proposed sublogo guidelines? Do you think they are too restrictive or too permissive? (3) Do you think having an approval system for sublogos would be an acceptable requirement? Should we contact a lawyer to get some advice? An approvals process is entirely reasonable. (2) Do you think the 'creative' sublogos approach is entirely more risk than it is worth? Should we just not allow for sublogos, or only allow for sublogos that use the 'stock' GNOME foot logomark? Something for us to take to the lawyers. There are some certification marks that I would like to develop, based on the GNOME logo. They're sufficiently important that they can't be confused with other sublogo designs. I'll chat to you about this off-list, so we can get something designed and published in the brand guidelines, and so no one makes conflicting sublogo designs. - Jeff -- linux.conf.au 2007: Sydney, Australia http://lca2007.linux.org.au/ Broken hearts rarely come with Some Assembly Required stickers. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Logo Branding Guidelines Concerns
On Wed, 2006-10-25 at 18:04 +0200, Dave Neary wrote: [snip] I disagree with you that we need to have plain black to protect the brand - I think there's more value in allowing good variations of the foot to develop. I'm not saying it needs to be black. I am saying that having a globe or flag as a fill for the foot is probably distorting it too much. Other colors are definitely OK - though we probably want to recommend our brand colors. I suspect a gradient is probably OK too. But I'm not a lawyer or designer, so I'm happy as long as we do whatever we do with open eyes, and as long as our guidelines are clear. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Logo Branding Guidelines Concerns
On 10/25/06, Luis Villa [EMAIL PROTECTED] wrote: On 10/25/06, Murray Cumming [EMAIL PROTECTED] wrote: On Wed, 2006-10-25 at 18:04 +0200, Dave Neary wrote: [snip] I disagree with you that we need to have plain black to protect the brand - I think there's more value in allowing good variations of the foot to develop. I'm not saying it needs to be black. I am saying that having a globe or flag as a fill for the foot is probably distorting it too much. Other colors are definitely OK - though we probably want to recommend our brand colors. I suspect a gradient is probably OK too. But I'm not a lawyer or designer, so I'm happy as long as we do whatever we do with open eyes, and as long as our guidelines are clear. (IANALY) On variety/colors: The legal key is that the design be clearly related to the Foot; that's really all that matters, once we've established the existence of the basic mark, and assuming we continue to use something very close to it for the 'primary' logo in the software and the web page. (We wouldn't want to make a habit of using a variation of it as 'the' primary logo in the about box, or in the header of the web page, for example, but irregularly using something like the old pumpkin foot would not likely be a problem.) We could of course decide as a matter of branding/marketing policy that we don't want variations, but I'd scream bloody fucking murder about that as a policy choice, for reasons Dave has already made fairly clear. :) And of course we'd need approval; not to restrict their style/design/nature, but to restrict what they are applied to. Luis (still wanting to abandon the mark registration, but that is tangential to Mairin's excellent work) -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
CMS Url's
I cant seem to Access the following CMS Test Url's:- Midgard CMS evaluation - http://devel-xen-stable.nemein.net/ and Plone - http://demo.gnome-cn.org/ Regards L. Tambiah -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
2006/10/25, Quim Gil [EMAIL PROTECTED]: As a matter of fact I think we can get a decent wgo with the 5 tools, in an ideal world with no time constraints and a good team of savvy CMS hackers. But we need to end up with one tool, the one that brings the best results with the minimum headaches for the type of website we want. Agreed. I suggest using the GoodEnough pattern ( http://c2.com/cgi/wiki?GoodEnough). About Tiki: I think Tiki is a very bad choice. I have not so much experience but I know that it is not very secure and has bad code quality. It does not scale well. I know of a case where somebody had given up to use TikiWiki because it could not deal with large amounts of data. TikiWiki gives you all you want, but not the quality or security About Midgard: I have the feeling that it is similar from the goals (security, stability) as Drupal. So I also would say one of the two (Drupal, Midgard) should be chosen. BTW: KDE had also chosen Drupal for spreadkde.org. Why is here: http://www.spreadkde.org/about/faq#newsite I think the whole process to decide which CMS to use was too complicated (too many goals, too many requirements. I know this was done with the best intentions, but I also see it this way: Drupal or Midgard- one of them might even be better today - but is it tomorrow? So only real interesting question are: * Does it a good enough job? and: * Does the development go in the right direction? Are errors fixed or are the implementing features soon that we might want to use I think to look in future decisions sometimes it is better to act and trust in the spontaneous community feedback instead of going through intensive testing that takes YEARS and in the end the results reflect tests that have been made before some bugs where fixed. I Don' t think detailled testing makes sense. I think every month that GNOME lives without a choice is a lost month. Again: I think the intentions where very good, but I think it was a bit overkill. Thilo -- Blog: http://vinci.wordpress.com Linked In: http://www.linkedin.com/in/tpfennig -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
On Wed, 2006-10-25 at 21:42 +0200, Thilo Pfennig wrote: Agreed. I suggest using the GoodEnough pattern ( http://c2.com/cgi/wiki?GoodEnough). Yeah, but the problem is when you get more than one option good enough. You need to evaluate then what is more good enough. I think the whole process to decide which CMS to use was too complicated (too many goals, too many requirements. Well, yes, but Gergerly (and others) seemed to enjoy elaborating such process. We are all volunteering here and we shouldn't stop anybody doing more than enough, if she enjoys doing it. This works if there are results on time. We haven't got them, then we need a plan B. I know this was done with the best intentions, but I also see it this way: Drupal or Midgard- one of them might even be better today - but is it tomorrow? Then comes i.e. Ramon and says that Plone is the best and he volunteers to do all the job, sowing you URLs of Plone installations he has made. What do you tell him? So only real interesting question are: * Does it a good enough job? and: * Does the development go in the right direction? Are errors fixed or are the implementing features soon that we might want to use The answers for i.e. eZ would be also affirmative in both cases. I think to look in future decisions sometimes it is better to act and trust in the spontaneous community feedback The spontaneous community came up with these 5 candidates plus at least 3 more. Things shouldn't be complicated, but they are not simple either. -- Quim Gil /// http://desdeamericaconamor.org signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
Could you (plural) explain why Drupal is going to handle a multilingual wgo and a translation workflow friendly with the i18n Team better than Plone and eZ? Henrius has explained the i18n feature of Midgard, but a closer comparison with the other candidates would be appreciated. As said, to me this is a (THE?) critical point. On Wed, 2006-10-25 at 21:51 +0100, Lee Tambiah wrote: Lets cut down the amount of testing in regards to functionality and just go for the really important points 'the really important points' are the ones mentioned in the email that started this thread. 5+1. Only in case of a draw we need to go into more details. -- Quim Gil /// http://desdeamericaconamor.org signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Logo Branding Guidelines Concerns
On Wed, 2006-10-25 at 12:25 -0400, Luis Villa wrote: Dave, I'd prefer we stay away from the (R) and (TM) Oh yes please! A clean foot smells much nicer. -- Quim Gil /// http://desdeamericaconamor.org signature.asc Description: This is a digitally signed message part -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: The wgo CMS can't wait more
On Wed, 2006-10-25 at 13:45 +0300, Henri Bergius wrote: Midgard has a system called MultiLang which allows content to be stored with multiple translation. A language has to be selected to be the default language (lang0) on top of which the other translations are made. This sounds interesting. I know that for my vision of GNOME Journal I wanted to have translated articles so that we aren't just stuck with a single language. We are currently using TextPattern which does the job, but not what I've envisioned. However, I have not been able to find an alternative short of a xslt/xmlpo/makefile system that makes it hard for other people to learn. - An enjoyable learning curve, good documentation for admins and editors and responsive support is also needed so new contributors can start helping without learning an obscure bible. The Midgard Documentation wiki (http://www.midgard-project.org/documentation/) and the IRC channel (#midgard in freenode) are good places to start. I'll browse that. Thanks. - Experienced contributors willing to install, custom and assist the 2.18 release, from now until the end in March. I would like to offer the services of my company, Nemein for this on pro bono basis. An intriguing offer that I hope Quim and others takes you up on. I know for about two years or so you've been doing some GNOME integration with Midgard. What kind of stuff have you been doing? I find that part very interesting, especially if we can manage our web pages using desktop technology. sri -- Sri Ramkrishna [EMAIL PROTECTED] -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
