Return-Path: X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AB5929248 for ; Wed, 26 Sep 2012 20:23:24 +0000 (UTC) Received: (qmail 28425 invoked by uid 500); 26 Sep 2012 20:23:24 -0000 Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org Received: (qmail 28390 invoked by uid 500); 26 Sep 2012 20:23:24 -0000 Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-commits@incubator.apache.org Received: (qmail 28381 invoked by uid 99); 26 Sep 2012 20:23:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 20:23:24 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 20:23:21 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id q8QKN0vn013032 for ; Wed, 26 Sep 2012 20:23:00 GMT Date: Wed, 26 Sep 2012 16:23:00 -0400 (EDT) From: confluence@apache.org To: ooo-commits@incubator.apache.org Message-ID: <6879876.1308.1348690980019.JavaMail.confluence@thor> Subject: [CONF] Apache OpenOffice Community > Draft -- Apache OpenOffice Consultants Directory MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Auto-Submitted: auto-generated Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS) Page: Draft -- Apache OpenOffice Consultants Directory (https://cwiki.apache.org/confluence/display/OOOUSERS/Draft+--+Apache+OpenOffice+Consultants+Directory) Added by Rob Weir: --------------------------------------------------------------------- Proposed disclaimer on page: {quote} \\ Although most individual users are able to download and use Apache OpenOffice without any help, or with the assistance of volunteers on our Forums and mailing lists, some users, especially corporate users, may have more complex requirements that require commercial services in order to optimize their deployments.  The following individuals and firms offer services that may be of interest.   The information provided here was provided by the entities named here, and is not verified or endorsed by the Apache OpenOffice project.  We offers this listing as a service to the ecosystem. Consultants who wish to add their listing here should follow the instructions provided on this page: XXXX {quote} The listing would then be HTML, machine generated by an XLST transform on a XML file we store in SVN.  For example, the XML could look like this: {code} Joe Bloggs, LLC jbloggs.jpg Deployment Migration Joe Bloggs, LLC provides custom deployment and migration servives for small and medium business moving to OpenOffice. We work with the client from initial evaluation and piloting, through deployment and beyond. References and whitepaper are available on our website. http://www/jbloggsllc.com/openoffice.html joe@jbloggsllc.com 123-456-7890 {code} Consults could submit or edit their entries via a CMS patch, a Bugzilla issue or via the mailing list. The HTML that is generated could take advantage of the XSLT capabilities to sort and categorize the data in several ways, e.g., alphabetically by name, categorized by specialty, etc.  We could evolve this over time, and as needed, based on the number of entries we receive.  For example, at some point, if we have a lot of entries, it might make sense to javascript-enhanced tables, to allow interactive sorting and filtering.  The key thing is to have a clean separation of the data from the presentation, so we are free to update the website as our needs grow.  Initially it would probably be a separate build step, i.e., modifying the XML would require a build, via XALAN, to generate the HTML.  But a further refinement would be to then integrate that with the CMS so it happens automatically.  That should be the goal, but we don't need to get there in one step. >From a policy perspective, we need to be fair in who we list.  We should submissions from the broader ecosystem of consultants providing services related to Apache OpenOffice.  A proposed list of technical and other requirements is: # Consultant must submit valid/well-formed description in our defined XML format, or equivalent information in text form.  # In order to have a good looking website we would have specific logo requirements, perhaps a common size, formats, no animated GIF's. # Description text would have a maximum length.  We want to avoid someone putting in page-length descriptions.  Description is plain unformatted text, no images, no hyperlinks.  In general, from a security perspective we don't want the possibility of any user-submitted active content being promoted to the website. # The listing must not misuse ASF trademarks or be likely to cause confusion with ASF trademarks.  This would apply to the entity name, the email address, website domain, website contents, description, etc.  This would be our main non-technical filter on submissions Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action