From kwade at redhat.com Sat Mar 1 00:24:51 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Fri, 29 Feb 2008 16:24:51 -0800 Subject: About http://search.fedoraproject.org/ In-Reply-To: References: <200802271224.08141.lgautrot@redhat.com> Message-ID: <1204331091.8319.72.camel@calliope.phig.org> On Wed, 2008-02-27 at 08:08 -0600, Mike McGrath wrote: > Indeed it is, we don't actually run search.fedoraproject.org. I'm going > to send a follow up and find out what the deal is there and if we're going > to start using it. gdk owns this project internally now and is working with the Board on what we want to happen there. Greg is your best point of contact, things should be happening on it Real Soon Now (TM). - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From pfrields at redhat.com Mon Mar 3 14:41:52 2008 From: pfrields at redhat.com (Paul W. Frields) Date: Mon, 03 Mar 2008 09:41:52 -0500 Subject: RHM widget on fedoraproject.org In-Reply-To: <47CB5081.3080306@redhat.com> References: <47CB5081.3080306@redhat.com> Message-ID: <1204555312.16292.3.camel@localhost.localdomain> On Sun, 2008-03-02 at 20:12 -0500, Jessica Gerber wrote: > Hi Paul and Max, > > I hope you both had restful weekends. > > Attached is a design mock-up of what we'd like uploaded to > fedoraproject.org (or possibly start.fedoraproject.org). We will have a > DevFu, RHM, and TH widget that will switch every time the site is > refreshed. > > What process should I follow to make this happen? Do I need to work with > traffic? > > Many thanks for the opportunity to put this widget on your site! Hi Jess, For something like this, you would want to work with the Websites group. I'm going to Cc: the fedora-websites-list so someone there can get in touch with you. Obviously there's a huge crossover audience between Fedora and DevFu/RHM/TH, and the actual mechanics of making the banner work, I recall, are pretty trivial. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From fedora-websites-list at redhat.com Mon Mar 3 17:49:47 2008 From: fedora-websites-list at redhat.com (Paul W. Frields (pfrields)) Date: Mon, 3 Mar 2008 17:49:47 GMT Subject: web/html/docs/translation-quick-start-guide/en_US generated-index.php, 1.5, 1.6 index.php, 1.9, 1.10 legalnotice-opl.php, 1.3, 1.4 rv-revhistory.php, 1.9, 1.10 sn_accounts.php, 1.9, 1.10 sn_translating_docs.php, 1.9, 1.10 sn_translating_software.php, 1.9, 1.10 Message-ID: <200803031749.m23Hnlnj002166@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2100 Modified Files: generated-index.php index.php legalnotice-opl.php rv-revhistory.php sn_accounts.php sn_translating_docs.php sn_translating_software.php Log Message: Publish new TQSG 0.4 en_US Index: generated-index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/generated-index.php,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- generated-index.php 23 Dec 2007 16:30:30 -0000 1.5 +++ generated-index.php 3 Mar 2008 17:49:17 -0000 1.6 @@ -1,3 +1,14 @@ + + + +Index + + + + + + + -
Index
Prev??????

Index

Prev??????
4.??Translating Documentation??Home??
+ +
+ + + + + + + +
Index
+Prev??????
+
+
+
+

Index

+
+
+
+
+ + + + + + + + + + + +
+Prev??????
4.??Translating Documentation??Home??
+
+ displayFooter('$Date$'); ?> + Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/index.php,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- index.php 23 Dec 2007 16:30:30 -0000 1.9 +++ index.php 3 Mar 2008 17:49:17 -0000 1.10 @@ -1,3 +1,13 @@ + + + +Translation Quick Start Guide + + + + + + -
Translation Quick Start Guide
??????Next

Translation Quick Start Guide

Manuel Ospina

Edited by

Paul W. Frields

Edited by

Noriko Mizumoto

Hugo Cisneiros

Francesco Tombolini

Andrew Martynov

Jos?? Pires

Bart Courveur

Dimitris Glezos

Damien Durand

Guillermo Gomez

Diego B??rigo Zacar??o

Version 0.3.9.1 (2007-12-23)

Copyright ?? 2005, 2006, 2007 Red Hat, Inc. and others

1. Introduction
2. Accounts and Subscriptions
2.1. Subscribing to the Mailing List
2.2. Makin! g a SSH Key
2.3. Making a GPG Key
2.4. Applying for an Account
2.5. Signing the CLA
2.6. Joining the cvsl10n Group
2.7. Testing Your Access
2.8. Creating a Wiki Account
2.9. Introducing Yourself
2.10. Create a Bugzilla account
2.11. Checklist
3. Translating Software
3.1. File Structure
3.2. Obtaining and Translating Modules
3.3. Committing Modules
3.4. Adding New .po file
3.5. Proofreading
4. Translating Documentation
4.1. Getting Started
4.2. Creating Common Files
4.3. Using Translation Applications
4.4. What to Translate
Index

1.??Introduction

+ +

+ + + + + + + +
Translation Quick Start Guide
??????Next +
+
+
+
+
+
+

Translation Quick Start Guide

+
+

+Manuel Ospina +

+
+

Edited by

+

+Paul W. Frields +

+
+
+

Edited by

+

+Noriko Mizumoto +

+
+
+

Edited by

+

+Dimitris Glezos +

+
+
+

+Hugo Cisneiros +

+

+Francesco Tombolini +

+

+Andrew Martynov +

+

+Jos?? Pires +

+

+Bart Courveur +

+

+Damien Durand +

+

+Guillermo Gomez +

+

+Diego B??rigo Zacar??o +

+

Version 0.4 (2008-03-03)

+

Copyright ?? 2005, 2006, 2007 Red Hat, Inc. and others

+ + +
+
+
+
+
1. Introduction
+
2. Accounts and Subscriptions
+
+
2.1. Subscribing to the Mailing List
+
2.2. Making a SSH Key
+
2.3. Making a GPG Key
+
2.4. Applying for an Account
+
2.5. Signing the CLA
+
2.6. Joining the cvsl10n Group
+
2.7. Testing Your Access
+
2.8. Creating a Wiki Account
+
2.9. Introducing Yourself
+
2.10. Create a Bugzilla account
+
2.11. Checklist
+
+
3. Translating Software
+
+
3.1. File Structure
+
3.2. Obtaining and Translating Modules
+
3.3. Committing Modules
+
3.4. Adding New .po file
+
3.5. Proofreading
+
+
4. Translating Documentation
+
+
4.1. Getting Started
+
4.2. Creating Common Files
+
4.3. Using Translation Applications
+
4.4. What to Translate
+
+
Index
+
+
+

1.??Introduction

+

This guide is a fast, simple, step-by-step set of instructions for translating Fedora Project software and documents. If you are interested in better understanding the translation process involved, refer to the Translation guide or the manual of the specific translation tool. -

??????Next
??????2.??Accounts and Subscriptions
+

+
+
+
+
+ + + + + + + + + + + +
??????Next +
??????2.??Accounts and Subscriptions
+
+ displayFooter('$Date$'); ?> + Index: legalnotice-opl.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/legalnotice-opl.php,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- legalnotice-opl.php 23 Dec 2007 16:30:30 -0000 1.3 +++ legalnotice-opl.php 3 Mar 2008 17:49:17 -0000 1.4 @@ -1,3 +1,10 @@ + + + +Legal Notice + + + -

+

+

Permission is granted to copy, distribute, and/or modify this document under the terms of the Open Publication Licence, Version 1.0, or any later version. The terms of the OPL are set out below. -

  1. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED - VERSIONS

    +

    +
    +
      +
    1. +

      +REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED + VERSIONS

      +

      Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction. -

      +

      +

      Proper form for an incorporation by reference is as follows: -

      +

      +

      Copyright (c) <year> by <author's name or designee>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at http://www.opencontent.org/openpub/). -

      +

      +

      The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see section VI). Commercial redistribution of Open @@ -37,100 +54,149 @@ surfaces of the book the original publisher's name shall be as large as the title of the work and cited as possessive with respect to the title. -

    2. COPYRIGHT

      +

      +
      3. +
    3. +

      +COPYRIGHT

      +

      The copyright to each Open Publication is owned by its author(s) or designee. -

    4. SCOPE OF LICENSE

      +

      +
      5. +
    5. +

      +SCOPE OF LICENSE

      +

      The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document. -

      +

      +

      Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice. -

      +

      +

      SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force. -

      +

      +

      NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement. -

    6. REQUIREMENTS ON MODIFIED WORKS

      +

      +
      7. +
    7. +

      +REQUIREMENTS ON MODIFIED WORKS

      +

      All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements: -

      1. +

        +
          +

        1. The modified version must be labeled as such. -

        2. +

          3. +

        3. The person making the modifications must be identified and the modifications dated. -

        4. +

          5. +

        5. Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices. -

        6. +

          7. +

        7. The location of the original unmodified document must be identified. -

        8. +

          9. +

        9. The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. -

      2. GOOD-PRACTICE RECOMMENDATIONS

        +

        3. +
      +
      8. +
    8. +

      +GOOD-PRACTICE RECOMMENDATIONS

      +

      In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that: -

      1. +

        +
          +

        1. If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document. -

        2. +

          3. +

        3. All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document. -

        4. +

          5. +

        5. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). -

      2. LICENSE OPTIONS

        +

        3. +
      +
      9. +
    9. +

      +LICENSE OPTIONS

      +

      The author(s) and/or publisher of an Open Publication-licensed document may elect certain options by appending language to the reference to or copy of the license. These options are considered part of the license instance and must be included with the license (or its incorporation by reference) in derived works. -

      +

      +

      A. To prohibit distribution of substantively modified versions without the explicit permission of the author(s). "Substantive modification" is defined as a change to the semantic content of the document, and excludes mere changes in format or typographical corrections. -

      +

      +

      To accomplish this, add the phrase 'Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.' to the license reference or copy. -

      +

      +

      B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. -

      +

      +

      To accomplish this, add the phrase 'Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder.' to the license reference or copy. -

+

+ + +
+
displayFooter('$Date$'); ?> + Index: rv-revhistory.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/rv-revhistory.php,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- rv-revhistory.php 23 Dec 2007 16:30:30 -0000 1.9 +++ rv-revhistory.php 3 Mar 2008 17:49:17 -0000 1.10 @@ -1,3 +1,10 @@ + + + +Revision History + + + -
+
Revision History
Revision 0.3.9.12007-12-23PWF
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Revision History
Revision 0.42008-03-03DG
+

+ Removed references to i18n.redhat.com (elvis) +

+
Revision 0.3.9.22008-02-18PWF
+

+ Fix GPG key URL +

+
Revision 0.3.9.12007-12-23PWF

Fix links to Transifex system

-
Revision 0.3.92007-11-14PWF
+
Revision 0.3.92007-11-14PWF

Editing for style, grammar, and clarity

-
Revision 0.3.8.22007-09-28NM
+
Revision 0.3.8.22007-09-28NM

Modified and updated all chapters to reflect latest information including usage of transifex, moved repository etc.

-
Revision 0.3.8.12007-09-04DZ
+
Revision 0.3.8.12007-09-04DZ

Add information on using an existing SSH key

-
Revision 0.3.82007-08-23NM
+
Revision 0.3.82007-08-23NM

Brokeup main file into multiple files based on chapters

-
Revision 0.3.7.52007-07-29PWF
+
Revision 0.3.7.52007-07-29PWF

Add information about LINGUAS and remove unnecessary admonitions

-
Revision 0.3.7.42007-07-28PWF
+
Revision 0.3.7.42007-07-28PWF

Add information on branch modules and testing changes

-
Revision 0.3.7.32007-07-06PWF
+
Revision 0.3.7.32007-07-06PWF

Make admonition against manual POT changes

-
Revision 0.3.7.22007-05-29MO
+
Revision 0.3.7.22007-05-29MO

Fix CVS group membership details; shorten copyright holders list

-
Revision 0.3.7.12007-04-03PWF
+
Revision 0.3.7.12007-04-03PWF

Generate new POT and PO keeping general entities

-
Revision 0.3.72006-10-14PWF
+
Revision 0.3.72006-10-14PWF

Fix erroneous URL (#209900)

-
Revision 0.3.62006-09-20MO
+
Revision 0.3.62006-09-20MO

Bug fixes (#198726, #204266, #205167)

-
Revision 0.3.52006-08-14PWF
+
Revision 0.3.52006-08-14PWF

Editorial pass, revising procedure to match proper ordering

-
Revision 0.3.42006-08-10MO
+
Revision 0.3.42006-08-10MO

Additional information about joining the Docs Project and GPG.

-
Revision 0.3.32006-08-06PWF
+
Revision 0.3.32006-08-06PWF

Remove step for translating rpm-info since this is now part of document POT

-
Revision 0.3.22006-07-03PWF
+
Revision 0.3.22006-07-03PWF

Fix doc translation procedure to include other common files translations

-
Revision 0.3.12006-05-28PWF
+
Revision 0.3.12006-05-28PWF

Add information on common entities and admonition for disabled locales

-
Revision 0.32006-05-27PWF
+
Revision 0.32006-05-27PWF

Fix procedural guide and include document-specific entities

-
Revision 0.2.2.22006-02-13PWF
+
Revision 0.2.2.22006-02-13PWF

Move to DocBook XML 4.4 and use XInclude

-
Revision 0.2.2.12006-02-02PWF
+
Revision 0.2.2.12006-02-02PWF

Fix spelling (#179717)

-
Revision 0.2.22006-02-01PWF
+
Revision 0.2.22006-02-01PWF

Add entity for bug reporting

-
Revision 0.2.12006-01-30PWF
+
Revision 0.2.12006-01-30PWF

Fix hostname error

-
Revision 0.22006-01-25PWF
+
Revision 0.22006-01-25PWF

Additional style editing, division of procedures into more readable sections

-
Revision 0.1Fri Jan 20 2006PWF
+
Revision 0.1Fri Jan 20 2006PWF

First round of editing.

-
Revision 0.0.1Wed Jan 18 2006MO
+
Revision 0.0.1Wed Jan 18 2006MO

First draft

-
+
displayFooter('$Date$'); ?> + Index: sn_accounts.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_accounts.php,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- sn_accounts.php 23 Dec 2007 16:30:30 -0000 1.9 +++ sn_accounts.php 3 Mar 2008 17:49:17 -0000 1.10 @@ -1,3 +1,15 @@ + + + +2.??Accounts and Subscriptions + + + + + + + + -
2.??Accounts and Subscriptions
Prev??????Next

2.??Accounts and Subscriptions

+ +

+ + + + + + + +
2.??Accounts and Subscriptions
+Prev??????Next +
+
+
+
+

2.??Accounts and Subscriptions

+

To become a Fedora Translator, you must sign up for accounts and subscriptions as described in this chapter. If you have questions, post them on the fedora-trans-list, or ask for help via Internet Relay Chat, or IRC, at irc.freenode.org on channel #fedora-l10n. -

2.1.??Subscribing to the Mailing List

  1. +

    +
    +

    2.1.??Subscribing to the Mailing List

    +
      +

    1. Visit https://listman.redhat.com/mailman/listinfo/fedora-trans-list/ and subscribe to the main translation mailing list. -

    2. +

      3. +

    3. Wait for the confirmation email which contains a link to confirm your subscription. Click the link to confirm your subscription. -

    4. +

      5. +

    5. Check http://fedoraproject.org/wiki/L10N/Teams/ to see if there is a special mailing list for your language. If so, subscribe to that list too. -

    2.2.??Making a SSH Key

    +

    2. +
+
+
+

2.2.??Making a SSH Key

+

If you already have an existing SSH key, you can use it for Fedora work. In that case, proceed to Step 2 in the following procedure. If you do not have a SSH key yet, start with the first step below: -

  1. +

    +
      +
    1. +

      Enter the following command: - 

      ssh-keygen -t dsa

      +

      +
      ssh-keygen -t dsa
      +

      Accept the default location (~/.ssh/id_dsa) and enter a passphrase. -

      +
      [Caution]Remember Your Passphrase

      +

      +
      + + + + +
      [Caution]Remember Your Passphrase

      You must have your passphrase to access to the CVS repository. It cannot be recovered if you forget it. -

    2. +

      3. +
      3. +
    3. +

      Change permissions to your key and .ssh directory: - 

      chmod 700 ~/.ssh
+	
      
+
      chmod 700 ~/.ssh
 chmod 600 ~/.ssh/id_dsa
-chmod 644 ~/.ssh/id_dsa.pub

    4. +chmod 644 ~/.ssh/id_dsa.pub +

      5. +

    5. Copy and paste the SSH key in the space provided in order to complete the account application. -

2.3.??Making a GPG Key

  1. +

    2. +
+
+
+

2.3.??Making a GPG Key

+
    +
  1. +

    Generate a key by typing in a command line: - 

    gpg --gen-key

    +

    +
    gpg --gen-key
    +

    A series of prompts guides you through the process. The default values suffice in almost all cases. Remember to choose a good password. -

    [Tip]Choosing a Good Password

    A good password:

    • consists of uppercase and lowercase letters, - numbers, punctuation, and other characters

    • does not include any words or names, with or without - substitutions

    • is not the same as any other password used for other - systems

  2. +

    +
    + + + + + +
    [Tip]Choosing a Good Password
    +

    A good password:

    +
      +

    • consists of uppercase and lowercase letters, + numbers, punctuation, and other characters

      • +

    • does not include any words or names, with or without + substitutions

      • +

    • is not the same as any other password used for other + systems

      • +
    +
    +
    3. +

  3. In the resulting text, find your key ID in the statement that resembles "pub 1024D/1B2AFA1C". Your key ID is the 8 character "word" after the slash (/). In the previous example, the GPG Key ID is 1B2AFA1C. Write down your key ID. -

  4. +

    5. +
  5. +

    Export your public key to a public server so that others can find it with the following command, substituting your key ID: - 

    gpg --keyserver pgp.mit.edu --send-keys GPGKEYID

2.4.??Applying for an Account

  1. +

    +
    gpg --keyserver subkeys.pgp.net --send-keys GPGKEYID
    +
    2. +
+
+
+

2.4.??Applying for an Account

+
    +

  1. To sign up for a Fedora account, first visit https://admin.fedoraproject.org/accounts/ and select Apply for a new account. -

  2. +

    3. +

  3. Fill in the form and choose a password for your Fedora account. Enter information for your GPG key ID and SSH key in the form. In the Comments field, write the languages you plan to work on. -

2.5.??Signing the CLA

+

+
+
+
+

2.5.??Signing the CLA

+

You must complete the Contributors License Agreement, or CLA. -

  1. Visit https://admin.fedoraproject.org/accounts/send-cla.cgi. +

    +
      +

    1. Visit https://admin.fedoraproject.org/accounts/send-cla.cgi. Authenticate using your username and password from the previous process. -

    2. Wait for receipt of an email with an attachment. The +

      3. +

    3. Wait for receipt of an email with an attachment. The attachment is an agreement you can sign and return. Save the attachment to your Desktop. -

    4. Double-click the file on your Desktop to open it with an +

      5. +

    5. Double-click the file on your Desktop to open it with an editor. Add the phrase "I agree" and your full name. -

    6. +

      7. +
    7. +

      Digitally sign the text file using your GPG key with the following command, providing your password when prompted: - 

       gpg -a --sign fedora-icla-{username}.txt

      There is now a new file on your Desktop that ends with +

      +
       gpg -a --sign fedora-icla-{username}.txt
      +

      There is now a new file on your Desktop that ends with .asc. This file is the signed version of the CLA. -

    8. +

      +
      9. +

    9. Open your email client again and reply to the CLA email. Attach the signed file which ends with .asc, and send the email. -

2.6.??Joining the cvsl10n Group

  1. +

    2. +
+
+
+

2.6.??Joining the cvsl10n Group

+
    +

  1. Visit https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1. Select Add new membership at the bottom of the page. In the field Groupname, enter cvsl10n and select Add. -

  2. +

    3. +

  3. An administrator is notified of your application, and offers to sponsor you. This may take between an hour and a few days. -

+
[Caution]Caution

+

+ +
+ + + + +
[Caution]Caution

The rest of the steps help you test your access and grant you privileges to all the Fedora infrastructure you might need in the near future. Language maintainers and people starting new languages should follow them. Although they are optional for translations, everyone is encouraged to follow them. -

[Important]Important

- Some of the Fedora modules are still hosted on the i18n.redhat.com system, - which is not enabled to work with the - cvsl10n group. To translate modules - hosted there, please visit http://i18n.redhat.com/cgi-bin/i18n-signup. This - warning may be deprecated soon. -

2.7.??Testing Your Access

  1. +

+
+
+

2.7.??Testing Your Access

+
    +
  1. +

    Install the cvs package, if it is not already installed, with the following command: - 

    su -c 'yum install cvs'

  2. +

    +
    su -c 'yum install cvs'
    +
    3. +
  3. +

    Checkout some PO files with the following command, substituting your username and providing your SSH key passphrase when prompted: - 

    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/l10n
+	
    
+
    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/l10n
 cvs co web
-ls web/flpweb/po

2.8.??Creating a Wiki Account

  1. +ls web/flpweb/po +

    2. +
+
+
+

2.8.??Creating a Wiki Account

+
    +

  1. Visit http://fedoraproject.org/wiki/UserPreferences/. For your username, choose a name like 'FirstnameLastname' and select Create Profile. -

  2. +

    3. +

  3. A current wiki user can now give you Edit access on the wiki. Contact someone from the Edit Group at http://fedoraproject.org/wiki/EditGroup/, or add your name to the EditGroupQueue at http://fedoraproject.org/wiki/EditGroupQueue/, and someone will add you shortly. -

  4. +

    5. +

  5. If you are starting a new language, or want to become the maintainer of one, add your information on the L10N/Teams page at http://fedoraproject.org/wiki/L10N/Teams/. -

2.9.??Introducing Yourself

  1. +

    2. +
+
+
+

2.9.??Introducing Yourself

+
    +

  1. Once you have edit access on the wiki, create a personal page. at a URL like this: http://fedoraproject.org/wiki/FirstnameLastname/. This is very useful for Fedora contributors to get to know and contact each other. -

  2. +

    3. +

  3. Post a short self introduction http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/ to the fedora-trans-list mailing list and to the list of your local team. -

2.10.??Create a Bugzilla account

+

+
+
+
+

2.10.??Create a Bugzilla account

+

Visit https://bugzilla.redhat.com/bugzilla/createaccount.cgi/ to create a Bugzilla account. -

2.11.??Checklist

+

+
+
+

2.11.??Checklist

+

You should now have the following: -

  • Subscription to fedora-trans-list mailing list +

    +
      +

    • Subscription to fedora-trans-list mailing list and your locale-specific mailing list, if there is - one

    • A SSH key

    • A GPG key

    • A Fedora account

    • Membership in the cvsl10n - group

    • A wiki account

    • Your language and translation team appear on - http://fedoraproject.org/wiki/L10N/Teams/

    • A Bugzilla account

    • A personal homepage on the wiki

    • A self-introduction sent to the mailing - list

    + one

    • +

  • A SSH key

    • +

  • A GPG key

    • +

  • A Fedora account

    • +

  • Membership in the cvsl10n + group

    • +

  • A wiki account

    • +

  • Your language and translation team appear on + http://fedoraproject.org/wiki/L10N/Teams/

    • +

  • A Bugzilla account

    • +

  • A personal homepage on the wiki

    • +

  • A self-introduction sent to the mailing + list

    • +
+

Sit back and enjoy your achievement. You are now a fully recognized member of the Fedora community, capable of digitally signing documents and emails, submitting contributions to our CVS, publishing content on the wiki, submitting bugs, following the discussions of our groups and joining other Fedora teams. -

Prev??????Next
Translation Quick Start Guide??Home??3.??Translating Software
+

+
+
+
+
+ + + + + + + + + + + +
+Prev??????Next +
Translation Quick Start Guide??Home??3.??Translating Software
+
+ displayFooter('$Date$'); ?> + Index: sn_translating_docs.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_translating_docs.php,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- sn_translating_docs.php 23 Dec 2007 16:30:30 -0000 1.9 +++ sn_translating_docs.php 3 Mar 2008 17:49:17 -0000 1.10 @@ -1,3 +1,15 @@ + + + +4.??Translating Documentation + + + + + + + + -
4.??Translating Documentation
Prev??????Next

4.??Translating Documentation

+ +

+ + + + + + + +
4.??Translating Documentation
+Prev??????Next +
+
+
+
+

4.??Translating Documentation

+

To translate Fedora documentation, become a member of the cvsl10n group. For more information on account and subscriptions, refer to Section??2, ???Accounts and Subscriptions???. -

+

+

To translate documentation, you need a Fedora 5 or later system with the following packages installed: -

  • gnome-doc-utils

  • xmlto

  • make

The gnome-doc-utils package provides the +

+
    +

  • gnome-doc-utils

    • +

  • xmlto

    • +

  • make

    • +
+

The gnome-doc-utils package provides the xml2po command, and does not require you to install the GNOME desktop environment. The xmlto and make packages contain tools necessary for - testing document builds and translations.

+ testing document builds and translations.

+

To install these packages, use the following command: - 

su -c 'yum install gnome-doc-utils xmlto make'

4.1.??Getting Started

+

+
su -c 'yum install gnome-doc-utils xmlto make'
+
+

4.1.??Getting Started

+

The Fedora documentation is stored in a CVS repository under the directory docs/. To list the available modules, run the following commands: - 

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
-cvs co -c

+

+
export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
+cvs co -c
+

To download a module to translate, list the current modules in the repository and then check out that module. You must also check out the docs-common module to work with some modules. - 

+    

+
       cvs co release-notes/
-    

+
+

Some modules are release specific, meaning that they have a branch, or subdirectory, for each release of Fedora: - 

ls release-notes/
-CVS  F-7  FC-5  FC-6  FC3  FC4  devel

+

+
ls release-notes/
+CVS  F-7  FC-5  FC-6  FC3  FC4  devel
+

The devel/ branch is used for the upcoming release of Fedora. Often translators work on this branch, and port changes back to previous branches as required. -

4.2.??Creating Common Files

+

+
+
+

4.2.??Creating Common Files

+

If you are creating the first-ever translation for a locale, you must first translate some common files used in all documents for your locale. The common files are located in docs-common/common/. -

+
[Note]Example Locale is pt_BR

The following examples use the locale code +

+
+ + + + +
[Note]Example Locale is pt_BR +

The following examples use the locale code pt_BR. Substitute your locale code - in these commands as necessary.

  1. + in these commands as necessary.

+
    +

  1. Read the README.txt file in the docs-common/common/entities and follow the directions to create new entities. -

  2. +

    3. +
  3. +

    Once you have created common entities for your locale and committed the results to CVS, create locale files for the legal notices: - 

    cd docs-common/common/
+	  
    
+
    cd docs-common/common/
 cp legalnotice-opl-en_US.xml legalnotice-opl-pt_BR.xml
 cp legalnotice-relnotes-en_US.xml legalnotice-relnotes-pt_BR.xml	
-
    
+
    [Important]Do Not Translate Legal Notice
    
+
+
    
+
+
+
+
+
    [Important]Do Not Translate Legal Notice
    
 	      To ensure it is legally equivalent in all locales, do not
 	      translate the OPL.
-	    
  4. 
+	    
    5. 
+
    5. +
  5. +

    Then commit those file to CVS also: - 

    cvs add legalnotice-*-pt_BR.xml
-cvs ci -m 'Added legal notices for pt_BR' legalnotice-*-pt_BR.xml

  6. +

    +
    cvs add legalnotice-*-pt_BR.xml
+cvs ci -m 'Added legal notices for pt_BR' legalnotice-*-pt_BR.xml
    +
    7. +
  7. +

    Next, build the draft watermark for your locale in the docs-common/images/ folder: - 

    cd docs-common/images/
-cp watermark-en_US.svg watermark-pt_BR.svg

    +

    +
    cd docs-common/images/
+cp watermark-en_US.svg watermark-pt_BR.svg
    +

    Translate the text elements in the SVG. Then add your locale's SVG file to the Makefile, produce the PNG and commit the results: - 

    make watermark-pt_BR.png
+	  
    
+
    make watermark-pt_BR.png
 cvs add watermark-pt_BR*
-cvs ci -m 'Added pt_BR images' Makefile watermark-pt_BR*
+
[Important]Build Errors

+cvs ci -m 'Added pt_BR images' Makefile watermark-pt_BR* + + +

+ + + + +
[Important]Build Errors

If you do not create these common entities, building your document may fail. -

4.3.??Using Translation Applications

The po/ directory +

+
+
+

4.3.??Using Translation Applications

+

The po/ directory contains the .po files used to translate content. It also contains a .pot file, or PO template, which is used to create new .po - files when necessary.

+ files when necessary.

+

If the po/ directory does not exist, you can create it and the translation template file with the following commands: - 

mkdir po
+      

+
mkdir po
 cvs add po/
 make pot
-

+
[Caution]Do Not Make Manual POT Changes
Authors and editors generate the POT file from the source
+
+

+
+
+
+
+
[Caution]Do Not Make Manual POT Changes
Authors and editors generate the POT file from the source
 	XML files, which overwrite any manual changes to a POT file.  If
 	you find a problem in the original messages of a POT file, visit
-	Bugzilla at https://bugzilla.redhat.com to file a bug against the document.

+	Bugzilla at https://bugzilla.redhat.com to file a bug against the document.

+

 	To work with a .po editor
 	like KBabel or
 	gtranslator, follow these
 	steps.
-      

+
[Note]Example Locale is pt_BR
The following examples use the locale code
+      

+

+
+
+
+
+
[Note]Example Locale is pt_BR
+
The following examples use the locale code
 	pt_BR.  Substitute your locale code
-      in these commands as necessary.
  1. Change Directory
    
+      in these commands as necessary.

+
    
+
  1. 
+
    Change Directory
    
+
    
 	    In a terminal, go to the directory of the document you want
 	    to translate:
-	  
    cd ~/docs/example-tutorial
  2. Add Locale to List
    To add your locale, you must locate and change the
+	  
    
+
    cd ~/docs/example-tutorial
    
+
    3. 
+
  3. 
+
    Add Locale to List
    
+
    To add your locale, you must locate and change the
 	    appropriate locale list.  Some documents are using the
 	    po/LINGUAS file, as standardized in the
 	    GNOME project, to track locales.  Some documents have not
 	    been updated to this standard yet.  If you find the module
 	    you are translating has not been updated, notify the Fedora Documentation Project
-	    or file a bug using Bugzilla.
    Add your translation language code to the list in the
+	    or file a bug using Bugzilla.
    
+
    Add your translation language code to the list in the
 	  po/LINGUAS file.  Keep the list
-	    in alphabetical order.
  4. Create PO File
    
+	    in alphabetical order.
    
+
    5. 
+
  5. 
+
    Create PO File
    
+
    
 	    Make a new .po file
 	    for your locale:
-	  
    make po/pt_BR.po
  6. Translate Strings
    
+	  
    
+
    make po/pt_BR.po
    
+
    7. 
+
  7. 
+
    Translate Strings
    
+
    
 	  To translate the file, use the same application used to
 	  translate software:
-	  
    kbabel po/pt_BR.po
  8. Check Integrity
    
+	  
    
+
    kbabel po/pt_BR.po
    
+
    9. 
+
  9. 
+
    Check Integrity
    
+
    
 	  Before committing your changes, check the integrity of the XML
 	  with the following command.  This ensures a sane build for all
 	  users.
-     
    make html-pt_BR
    You can read the resulting HTML files with a Web
-	  browser.
    
+
    [Important]Always Test Your Translation
    
+     
    
+
    make html-pt_BR
    
+
    You can read the resulting HTML files with a Web
+	  browser.
    
+
    
+
+
+
+
+
    [Important]Always Test Your Translation
    
 	    Do not go to the next step or commit changes until you test
 	    your work in this step. Erroneous changes can break
 	    documents for other users, editors, and automated
-	    applications.
  10. Commit Work
    
+	    applications.
    11. 
+
    11. 
+
  11. 
+
    Commit Work
    
+
    
 	    When you have finished your translation, commit the .po file. You may note the percent complete or some other useful message at commit time.
-	  
    cvs ci -m 'Translating... 400/10/126' po/pt_BR.po

4.4.??What to Translate

+

+
cvs ci -m 'Translating... 400/10/126' po/pt_BR.po
+ +
+
+
+

4.4.??What to Translate

+

The most important docs modules/directories for each release are the following: -

  • docs-common/common/entities

  • release-notes/devel

  • homepage/devel

  • install-guide/devel

  • about-fedora/devel

  • readme/devel

  • readme-burning-isos/devel

  • readme-live-image/devel

+

+
    +

  • docs-common/common/entities

    • +

  • release-notes/devel

    • +

  • homepage/devel

    • +

  • install-guide/devel

    • +

  • about-fedora/devel

    • +

  • readme/devel

    • +

  • readme-burning-isos/devel

    • +

  • readme-live-image/devel

    • +
+

To see all documents available in the documentation repository, run: - 

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
-cvs co -c
Prev??????Next
3.??Translating Software??Home??Index
+

+
export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
+cvs co -c
+
+ +
+
+ + + + + + + + + + + +
+Prev??????Next +
3.??Translating Software??Home??Index
+
+ displayFooter('$Date$'); ?> + Index: sn_translating_software.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_translating_software.php,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- sn_translating_software.php 23 Dec 2007 16:30:30 -0000 1.9 +++ sn_translating_software.php 3 Mar 2008 17:49:17 -0000 1.10 @@ -1,3 +1,15 @@ + + + +3.??Translating Software + + + + + + + + -
3.??Translating Software
Prev??????Next

3.??Translating Software

+ +

+ + + + + + + +
3.??Translating Software
+Prev??????Next +
+
+
+
+

3.??Translating Software

+

The translatable part of a software package is available in one or more po files. These files may be maintained in any of a number of version control systems (VCSs) depending on the project, such as CVS, Subversion, Mercurial, - and git. They may be hosted on either fedoraproject.org or the - i18n.redhat.com - server. The i18n.redhat.com system is not - enabled to work with the cvsl10n group. To - sign up for an account on i18n.redhat.com, please visit - http://i18n.redhat.com/cgi-bin/i18n-signup/. This - warning will probably be deprecated soon. -

+ and git. They may be hosted on either fedoraproject.org or other + systems. +

+

This chapter explains how to translate the modules hosted on fedoraproject.org. Translators work on two interfaces, one for obtaining modules and another for committing modules. Before you start, you must first prepare the directories which hold your po files. -

3.1.??File Structure

+

+
+

3.1.??File Structure

+

To find which modules are translatable, visit the Module List at https://translate.fedoraproject.org/submit/module/. -

+

+

Before you download any files, prepare the structure holding those files. The described structure below is an example, and your structure can be formed differently. For example, if you want to download the comps module for translation, make the following directories: - 

mkdir -p ~/myproject/comps/

+

+
mkdir -p ~/myproject/comps/
+

To work on another module later, make a directory with the module name under the parent directory such as myproject. -

3.2.??Obtaining and Translating Modules

+

+
+
+

3.2.??Obtaining and Translating Modules

+

Now that you have prepared a directory structure, you can download a file to translate. -

  1. +

    +
      +

    1. Visit http://translate.fedoraproject.org/submit/module/ and select a target module. The interface will redirect you to a page for that module, such as http://translate.fedoraproject.org/submit/module/comps/. -

    2. +

      3. +

    3. Scroll down the page to find the table of all po files available. The pot file appears at the top of the listing. Use the green download icon next to each language to download the file to the directory you created in the previous section. -

    4. +

      5. +
    5. +

      Since the file name to commit follows the name convention of lang.po, change the name of the downloaded file. The following example uses the Japanese locale for the po file: - 

      ls ~/myproject/comps/
+	
      
+
      ls ~/myproject/comps/
 comps.HEAD.ja.po
 mv ~/myproject/comps/comps.HEAD.ja.po ja.po 
 ls ~/myproject/comps/
-ja.po

    6. +ja.po +

      7. +

    7. Now the file is ready for translation. Translate the po file for your language in a po editor such as KBabel or gtranslator. -

    8. +

      9. +
    9. +

      Check the integrity of your file before you commit it. - 

      msgfmt -cvo /dev/null ja.po
    +
    [Important]Important

    +

    +
    msgfmt -cvo /dev/null ja.po
    + + +
    + + + + +
    [Important]Important

    If any error message appears, correct it before commit. -

    3.3.??Committing Modules

    +

    +
+
+

3.3.??Committing Modules

+

Once you finish translation work, commit the file using a separate interface called Transifex. You can find detailed information about this web tool at https://translate.fedoraproject.org/submit. -

  1. +

    +
      +

    1. Visit https://translate.fedoraproject.org/submit and click the link Jump to Modules! to go to the Modules and repositories page. This page displays all modules to which you can commit changes. Find the module to commit from the list and select it to visit the Submit page for that module. -

    2. Login

      +

      3. +
    3. +

      Login

      +

      At the bottom of the Submit page, select Authenticate as a translator to visit the Login page. Authenticate with your Fedora Account System username and password. Upon successful login, the Submit page appears. -

    4. Submit

      +

      +
      5. +
    5. +

      Submit

      +

      In the section labeled Local file, click the browse button to locate your translated file. -

      +

      +

      In the section labeled Destination file, click the dropdown menu labeled Overwrite an existing file: to select your language. -

      +

      +

      In the section labeled Commit message, enter a comment to describe your work. -

      +

      +

      Select the Preview button to proceed to the Preview submission page. Check the Differences section to verify your changes and select the Submit button. -

      +

      +

      The Submit page appears and displays the message Your submission was committed successfully. If you receive an error or some other success message, please post it to the Fedora Translation Project mailing list so it can be addressed. -

3.4.??Adding New .po file

+

+ +
+
+
+

3.4.??Adding New .po file

+

If there is no po file for your language, add it. -

  1. +

    +
      +
    1. +

      Download the pot file and copy it as your own language's po file. - 

      cp ~/myproject/comps/comps.HEAD.pot ja.po
+	
      
+
      cp ~/myproject/comps/comps.HEAD.pot ja.po
 kbabel ja.po
-msgfmt -cvo /dev/null ja.po

    2. +msgfmt -cvo /dev/null ja.po +

      3. +

    3. Once you finish the translation, follow the same steps for verifying and committing your translation described in previous section. -

    4. +

      5. +
    5. +

      In the section labeled Destination file, type your new filename in the field marked Type the name for a new one:, replacing the filename with your locale: - 

      po/ja.po

3.5.??Proofreading

+

+
po/ja.po
+ +
+
+
+

3.5.??Proofreading

+

To proofread your translation as part of the software, follow these steps: -

  1. +

    +
      +
    1. +

      Change directory to the package you want to proofread: - 

      cd ~/myproject/package_name

    2. +

      +
      cd ~/myproject/package_name
      +
      3. +
    3. +

      Convert the .po file to a .mo file with msgfmt: - 

      msgfmt lang.po

    4. +

      +
      msgfmt lang.po
      +
      5. +
    5. +

      Overwrite the existing .mo file in /usr/share/locale/lang/LC_MESSAGES/. First, back up the existing file: - 

      cp /usr/share/locale/lang/LC_MESSAGES/package_name.mo package_name.mo-backup
-mv package_name.mo /usr/share/locale/lang/LC_MESSAGES/

    6. +

      +
      cp /usr/share/locale/lang/LC_MESSAGES/package_name.mo package_name.mo-backup
+mv package_name.mo /usr/share/locale/lang/LC_MESSAGES/
      +
      7. +
    7. +

      Proofread the package with the translated strings as part of the application: - 

      LANG=lang package_command

    +

    +
    LANG=lang package_command
    +
    2. +
+

The application related to the translated package runs with the translated strings. -

Prev??????Next
2.??Accounts and Subscriptions??Home??4.??Translating Documentation
+

+
+
+
+
+ + + + + + + + + + + +
+Prev??????Next +
2.??Accounts and Subscriptions??Home??4.??Translating Documentation
+
+ displayFooter('$Date$'); ?> + From fedora-websites-list at redhat.com Mon Mar 3 17:52:36 2008 From: fedora-websites-list at redhat.com (Paul W. Frields (pfrields)) Date: Mon, 3 Mar 2008 17:52:36 GMT Subject: web/html/docs/translation-quick-start-guide/it generated-index.php, 1.4, 1.5 index.php, 1.13, 1.14 legalnotice-opl.php, 1.2, 1.3 rv-revhistory.php, 1.13, 1.14 sn_accounts.php, 1.13, 1.14 sn_translating_docs.php, 1.13, 1.14 sn_translating_software.php, 1.13, 1.14 Message-ID: <200803031752.m23HqarT002265@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/fedora/web/html/docs/translation-quick-start-guide/it In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2221 Modified Files: generated-index.php index.php legalnotice-opl.php rv-revhistory.php sn_accounts.php sn_translating_docs.php sn_translating_software.php Log Message: Publish updated TQSG 0.4 it Index: generated-index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/generated-index.php,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- generated-index.php 27 Dec 2007 02:06:59 -0000 1.4 +++ generated-index.php 3 Mar 2008 17:52:06 -0000 1.5 @@ -1,3 +1,14 @@ + + + +Indice + + + + + + + -
Indice
Indietro   

Indice

+ +
+
Indietro   
4. Tradurre la documentazione Partenza 
+ + + + + + +
Indice
+Indietro   
+
+
+
+

Indice

+
+
+
+
+ + + + + + + + + + + +
+Indietro   
4. Tradurre la documentazione Partenza 
+
+ displayFooter('$Date$'); ?> + Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/index.php,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- index.php 27 Dec 2007 02:06:59 -0000 1.13 +++ index.php 3 Mar 2008 17:52:06 -0000 1.14 @@ -1,3 +1,13 @@ + + + +Guida rapida alle traduzioni + + + + + + -
Guida rapida alle traduzioni
   Avanti

Guida rapida alle traduzioni

Manuel Ospina

A cura di

Paul W. Frields

A cura di

Noriko Mizumoto

Hugo Cisneiros

Francesco Tombolini

Andrew Martynov

José Pires

Bart Courveur

Dimitris Glezos

Damien Durand

Guillermo Gomez

Diego Búrigo Zacarão

Version 0.3.9.1 (2007-12-23)

Copyright © 2005, 2006, 2007 Red Hat, Inc. ed altri

1. Introduzione
2. Accounts e sottoscrizioni
2.1. Sottoscrivere la mailing list
2.2. Creazione di una chiave SSH
2.3. Creazione di una chiave GPG
2.4. Richiedere un account
2.5. Firmare la CLA
2.6. Unirsi al gruppo cvsl10n
2.7. Verifica dell'accesso
2.8. Creare un account wiki
2.9. Presentarsi
2.10. Creare un account Bugzilla
2.11. Chec! klist
3. Tradurre il software
3.1. Struttura dei files
3.2. Ottenere e tradurre i moduli
3.3. Invio dei moduli
3.4. Aggiungere un nuovo file .po
3.5. Correggere le bozze
4. Tradurre la documentazione
4.1. Cominciamo!
4.2. Creare i files comuni
4.3. Usare le applicazioni per la traduzione
4.4. Cosa tradurre
Indice

1. Introduzione

Questa guida è un veloce, semplice, insieme di istruzioni passo-passo per tradurre software e documenti del Fedora Project. Se si è interessati nel comprendere meglio il processo di traduzione impiegato, si faccia riferimento alla guida per la traduzione o al manuale dello specifico strumento di traduzione.

   Avanti
   2. Accounts e sottoscrizioni
+ +
+ + + + + + + +
Guida rapida alle traduzioni
   Avanti +
+
+
+
+
+
+

Guida rapida alle traduzioni

+
+

+Manuel Ospina +

+
+

A cura di

+

+Paul W. Frields +

+
+
+

A cura di

+

+Noriko Mizumoto +

+
+
+

A cura di

+

+Dimitris Glezos +

+
+
+

+Hugo Cisneiros +

+

+Francesco Tombolini +

+

+Andrew Martynov +

+

+José Pires +

+

+Bart Courveur +

+

+Damien Durand +

+

+Guillermo Gomez +

+

+Diego Búrigo Zacarão +

+

Version 0.4 (2008-03-03)

+

Copyright © 2005, 2006, 2007 Red Hat, Inc. ed altri

+ + +
+
+
+
+
1. Introduzione
+
2. Accounts e sottoscrizioni
+
+
2.1. Sottoscrivere la mailing list
+
2.2. Creazione di una chiave SSH
+
2.3. Creazione di una chiave GPG
+
2.4. Richiedere un account
+
2.5. Firmare la CLA
+
2.6. Unirsi al gruppo cvsl10n
+
2.7. Verifica dell'accesso
+
2.8. Creare un account wiki
+
2.9. Presentarsi
+
2.10. Creare un account Bugzilla
+
2.11. Checklist
+
+
3. Tradurre il software
+
+
3.1. Struttura dei files
+
3.2. Ottenere e tradurre i moduli
+
3.3. Invio dei moduli
+
3.4. Aggiungere un nuovo file .po
+
3.5. Correggere le bozze
+
+
4. Tradurre la documentazione
+
+
4.1. Cominciamo
+
4.2. Creare i files comuni
+
4.3. Usare le applicazioni per la traduzione
+
4.4. Cosa tradurre
+
+
Indice
+
+
+

1. Introduzione

+

Questa guida è un veloce, semplice, insieme di istruzioni passo-passo per tradurre software e documenti del Fedora Project. Se si è interessati nel comprendere meglio il processo di traduzione impiegato, si faccia riferimento alla guida per la traduzione o al manuale dello specifico strumento di traduzione.

+
+
+
+
+ + + + + + + + + + + +
   Avanti +
   2. Accounts e sottoscrizioni
+
+ displayFooter('$Date$'); ?> + Index: legalnotice-opl.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/legalnotice-opl.php,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- legalnotice-opl.php 27 Dec 2007 02:06:59 -0000 1.2 +++ legalnotice-opl.php 3 Mar 2008 17:52:06 -0000 1.3 @@ -1,3 +1,10 @@ + + + +Note Legali + + + -

+

+

Permission is granted to copy, distribute, and/or modify this document under the terms of the Open Publication Licence, Version 1.0, or any later version. The terms of the OPL are set out below. -

  1. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED - VERSIONS

    +

    +
    +
      +
    1. +

      +REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED + VERSIONS

      +

      Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction. -

      +

      +

      Proper form for an incorporation by reference is as follows: -

      +

      +

      Copyright (c) <year> by <author's name or designee>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at http://www.opencontent.org/openpub/). -

      +

      +

      The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see section VI). Commercial redistribution of Open @@ -37,100 +54,149 @@ surfaces of the book the original publisher's name shall be as large as the title of the work and cited as possessive with respect to the title. -

    2. COPYRIGHT

      +

      +
      3. +
    3. +

      +COPYRIGHT

      +

      The copyright to each Open Publication is owned by its author(s) or designee. -

    4. SCOPE OF LICENSE

      +

      +
      5. +
    5. +

      +SCOPE OF LICENSE

      +

      The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document. -

      +

      +

      Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice. -

      +

      +

      SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force. -

      +

      +

      NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement. -

    6. REQUIREMENTS ON MODIFIED WORKS

      +

      +
      7. +
    7. +

      +REQUIREMENTS ON MODIFIED WORKS

      +

      All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements: -

      1. +

        +
          +

        1. The modified version must be labeled as such. -

        2. +

          3. +

        3. The person making the modifications must be identified and the modifications dated. -

        4. +

          5. +

        5. Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices. -

        6. +

          7. +

        7. The location of the original unmodified document must be identified. -

        8. +

          9. +

        9. The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. -

      2. GOOD-PRACTICE RECOMMENDATIONS

        +

        3. +
      +
      8. +
    8. +

      +GOOD-PRACTICE RECOMMENDATIONS

      +

      In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that: -

      1. +

        +
          +

        1. If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document. -

        2. +

          3. +

        3. All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document. -

        4. +

          5. +

        5. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). -

      2. LICENSE OPTIONS

        +

        3. +
      +
      9. +
    9. +

      +LICENSE OPTIONS

      +

      The author(s) and/or publisher of an Open Publication-licensed document may elect certain options by appending language to the reference to or copy of the license. These options are considered part of the license instance and must be included with the license (or its incorporation by reference) in derived works. -

      +

      +

      A. To prohibit distribution of substantively modified versions without the explicit permission of the author(s). "Substantive modification" is defined as a change to the semantic content of the document, and excludes mere changes in format or typographical corrections. -

      +

      +

      To accomplish this, add the phrase 'Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.' to the license reference or copy. -

      +

      +

      B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. -

      +

      +

      To accomplish this, add the phrase 'Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder.' to the license reference or copy. -

+

+ + +
+
displayFooter('$Date$'); ?> + Index: rv-revhistory.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/rv-revhistory.php,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- rv-revhistory.php 27 Dec 2007 02:06:59 -0000 1.13 +++ rv-revhistory.php 3 Mar 2008 17:52:06 -0000 1.14 @@ -1,3 +1,10 @@ + + + +Diario delle Revisioni + + + -
+
Diario delle Revisioni
Revisione 0.3.9.12007-12-23PWF
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Diario delle Revisioni
Revisione 0.42008-03-03DG
+

+ Rimossi riferimenti a i18n.redhat.com (elvis) +

+
Revisione 0.3.9.22008-02-18PWF
+

+ Aggiornato l'URL alla chiave GPG +

+
Revisione 0.3.9.12007-12-23PWF

Correzione links per il sistema Transifex

-
Revisione 0.3.92007-11-14PWF
+
Revisione 0.3.92007-11-14PWF

Modifiche per stile, grammatica, e chiarezza

-
Revisione 0.3.8.22007-09-28NM
+
Revisione 0.3.8.22007-09-28NM

Modificati ed aggiornati tutti i capitoli per riflettere le ultime informazioni incluso l'uso di transifex, i repositori spostati, etc.

-
Revisione 0.3.8.12007-09-04DZ
+
Revisione 0.3.8.12007-09-04DZ

Aggiunte informazioni sull'uso di una chiave SSH esistente

-
Revisione 0.3.82007-08-23NM
+
Revisione 0.3.82007-08-23NM

Spezzato il file principale in files multipli basati sui capitoli

-
Revisione 0.3.7.52007-07-29PWF
+
Revisione 0.3.7.52007-07-29PWF

Aggiunte le informazioni su LINGUAS e rimozione delle ammonizioni non necessarie

-
Revisione 0.3.7.42007-07-28PWF
+
Revisione 0.3.7.42007-07-28PWF

Aggiunte le informazioni sui moduli branch e cambiamenti testing

-
Revisione 0.3.7.32007-07-06PWF
+
Revisione 0.3.7.32007-07-06PWF

Fatta l'ammonizione sui cambiamenti manuali ai POT

-
Revisione 0.3.7.22007-05-29MO
+
Revisione 0.3.7.22007-05-29MO

Risolti dettagli sull'appartenenza al gruppo CVS; abbreviato elenco proprietari copyright

-
Revisione 0.3.7.12007-04-03PWF
+
Revisione 0.3.7.12007-04-03PWF

Generato nuovo POT e PO mantenendo le entità generali

-
Revisione 0.3.72006-10-14PWF
+
Revisione 0.3.72006-10-14PWF

Corretto URL erroneo (#209900)

-
Revisione 0.3.62006-09-20MO
+
Revisione 0.3.62006-09-20MO

Risoluzione errori (#198726, #204266, #205167)

-
Revisione 0.3.52006-08-14PWF
+
Revisione 0.3.52006-08-14PWF

Controllo editore, procedura di revisione per conformarsi all'appropriato ordinamento

-
Revisione 0.3.42006-08-10MO
+
Revisione 0.3.42006-08-10MO

Informazioni aggiuntive su come partecipare al Progetto di Documentazione e GPG.

-
Revisione 0.3.32006-08-06PWF
+
Revisione 0.3.32006-08-06PWF

Rimosso il passo per la traduzione dell'rpm-info poiché è ora parte del documento POT

-
Revisione 0.3.22006-07-03PWF
+
Revisione 0.3.22006-07-03PWF

Migliorata la procedura di traduzione dei documenti per includere le traduzioni dei files comuni

-
Revisione 0.3.12006-05-28PWF
+
Revisione 0.3.12006-05-28PWF

Aggiunte informazioni sulle common entities e le ammonizioni per le localizzazioni disabilitate

-
Revisione 0.32006-05-27PWF
+
Revisione 0.32006-05-27PWF

Risolta guida procedurale ed incluse entità specifiche per il documento

-
Revisione 0.2.2.22006-02-13PWF
+
Revisione 0.2.2.22006-02-13PWF

Aggiornato a DocBook XML 4.4 ed utilizzato XInclude

-
Revisione 0.2.2.12006-02-02PWF
+
Revisione 0.2.2.12006-02-02PWF

Risolto errore di battitura (#179717)

-
Revisione 0.2.22006-02-01PWF
+
Revisione 0.2.22006-02-01PWF

Aggiunta entità per le segnalazioni d'errore

-
Revisione 0.2.12006-01-30PWF
+
Revisione 0.2.12006-01-30PWF

Risolto errore hostname

-
Revisione 0.22006-01-25PWF
+
Revisione 0.22006-01-25PWF

Ulteriori aggiunte di stile, divisione delle procedure in sezioni più leggibili

-
Revisione 0.1Fri Jan 20 2006PWF
+
Revisione 0.1Fri Jan 20 2006PWF

Primo round di editing.

-
Revisione 0.0.1Wed Jan 18 2006MO
+
Revisione 0.0.1Wed Jan 18 2006MO

Prima bozza

-
+
displayFooter('$Date$'); ?> + Index: sn_accounts.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/sn_accounts.php,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- sn_accounts.php 27 Dec 2007 02:06:59 -0000 1.13 +++ sn_accounts.php 3 Mar 2008 17:52:06 -0000 1.14 @@ -1,3 +1,15 @@ + + + +2. Accounts e sottoscrizioni + + + + + + + + -
2. Accounts e sottoscrizioni
Indietro   Avanti

2. Accounts e sottoscrizioni

Per diventare un Traduttore Fedora, si deve aderire ad accounts e sottoscrizioni come descritto in questo capitolo. Se si hanno domande, postarle sulla fedora-trans-list, o chiedere aiuto via Internet Relay Chat, oIRC, su irc.freenode.org sul canale #fedora-l10n.

2.1. Sottoscrivere la mailing list

  1. Visitare https://listman.redhat.com/mailman/listinfo/fedora-trans-list/ e sottoscrivere la mailing list principale delle traduzioni.

  2. Attendere l'email di conferma che contiene un link per confermare la sottoscrizione. Cliccare il link per confermare la sottoscrizione.

  3. Controllare http://fedoraproject.org/wiki/L10N/Teams/ per vedere se ci sono speciali mailing list per il proprio linguaggio. Se si, sottoscrivere anche quelle liste.

2.2. Creazione di una chiave SSH

Se si possiede già una chiave SSH, è! ; possib ile utilizzarla per lavorare in Fedora. In quel caso, come nella seguente procedura, si proceda a Passo 2. Se non si ha ancora una chiave SSH, si cominci con il primo passo qui sotto:

  1. Inserire il seguente comando:

    ssh-keygen -t dsa

    Accettare la locazione predefinita (~/.ssh/id_dsa) ed immettere una passphrase.

    [Attenzione]Ricordare la passphrase

    Si avrà bisogno della passphrase per accedere al repositorio CVS. Non potrà essere recuperata se diment! icata.

  2. Cambiare i permessi alla chiave ed alla directory .ssh:

    chmod 700 ~/.ssh chmod 600 ~/.ssh/id_dsa chmod 644 ~/.ssh/id_dsa.pub

  3. Copiare ed incollare la chiave SSH nello spazio fornito per poter completare la sottoscrizione all'account.

2.3. Creazione di una chiave GPG

  1. Generare una chiave scrivendo in un terminale:

    gpg --gen-key

    Si verrà guidati attraverso il processo da una serie di prompts. I valori predefiniti sono sufficienti per la maggior parte dei casi. Ricordarsi di scegliere una buona password.

    [Suggerimento]Scegliere una buona password

    Una buona password:

    • consiste di lettere maiuscole e minuscole, numeri, segni di punteggiatura, ed altri caratteri

    • non include alcuna parola o nome, con o senza sostituzioni

    • non è la stessa password utilizzata su altri sistemi

  2. Nel testo risultante, si troverà l'ID chiave nella riga che somiglia a "pub 1024D/1B2AFA1C". L'ID chiave è la "parola" di 8 caratteri dopo lo slash (/). Nell'esempio precedente l'ID chiave GPG è 1B2AFA1C. Scriversi il proprio ID chiave.

  3. Esportare la propria chiave pubblica su un server pubblico affi! nchè anche altri possano trovarla, con il seguente comando, sostituire il proprio ID chiave:

    gpg --keyserver pgp.mit.edu --send-keys GPGKEYID

2.4. Richiedere un account

  1. Per richiedere un account Fedora, visitare https://admin.fedoraproject.org/accounts/ e selezionare Apply for a new account.

  2. Riempire il form e scegliere una password per l'account Fedora. Immettere le informazioni sull'ID chiave GPG e la chiave SSH. Nel campo Comments, scrivere la lingua su cui si è pianificato di lavor! are.

2.5. Firmare la CLA

Si deve completare la Contributors License Agreement, o CLA.

  1. Visitare https://admin.fedoraproject.org/accounts/send-cla.cgi. Autenticarsi usando il proprio username e password dal processo precedente.

  2. Attendere la ricezione di un email con un allegato. L'allegato è un accordo che si deve firmare e restituire. Salvare l'allegato sul Desktop.

  3. Doppio-cliccare il file sul Desktop per aprirlo con un editor. Aggiungere la frase "I agree" ed il proprio nome completo.

  4. Firmare digitalmente il file di testo usando la propria chiave GPG con il seguente comando, fornendo la password quando richiestta:

    gpg -a --si!
 gn fedora-icla-{username}.txt

    In quel momento comparirà un nuovo file sul desktop che termina per .asc. Questo file è la versione firmata della CLA.

  5. Aprire il client email e rispondere alla lettera della CLA. Allegare il file firmato che termina con .asc, e spedire l'email.

2.6. Unirsi al gruppo cvsl10n

  1. Visitare https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1. Selezionare Add new membership alla fine della pagina. Nel campo Groupname, inserire ! cvsl10n e sele! zionare Add.

  2. Un amministratore verrà notificato della tua partecipazione, e ti offrirà di sponsorizzarti. Per questo passaggio potrebbero volerci da un ora a un po di giorni.

[Attenzione]Attenzione

I restanti passi aiuteranno nella verifica dell'accesso e delle grant dei privilegi a tutte le infrastrutture Fedora di cui si potrà aver necessità in futuro. I manutentori dei linguaggi e le persone che iniziano nuovi linguaggi dovranno seguirli. Nonostante essi siano opzionali per i traduttori, ogniuno è incoraggiato a seguirli.

[Importante]Importante

Alcuni dei moduli Fedora sono ancora ospitati sul sistema i18n.redhat.com, che non è abilitato a lavorare con il gruppo cvsl10n. Per tradurre i moduli ospitati qui, visitare http://i18n.redhat.com/cgi-bin/i18n-signup. Questo avviso sarà presto deprecato.

2.7. Verifica dell'accesso

  1. Installare il pacchetto cvs, se non è già! installato, con i seguenti comandi:

    su -c 'yum install cvs'

  2. Eseguire il checkout di alcuni files PO con il seguente comando, sostituire l'username e fornire la propria passphrase della chiave SSH quando richiesto:

    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/l10n cvs co web ls web/flpweb/po

2.8. Creare un account wiki

  1. Visitare http://fedoraproject.org/wiki/UserPreferences/. Per username, scegliere un nome tipo 'NomeCognome' e selezionare Create Profile.

  2. Un utente wiki corrente può dare a sua volta l'accesso per editare ! la wiki. Contattare qualcuno dell'Edit Group su http://fedoraproject.org/wiki/EditGroup/, o aggiungere il proprio nome alla EditGroupQueue su http://fedoraproject.org/wiki/EditGroupQueue/, e qualcuno in breve tempo fornirà l'accesso desiderato.

  3. Se si comincia un nuovo linguaggio, o si vuole diventare il manutentore di uno, aggiungere le proprie informazioni alla pagina L10N/Teams su http://fedoraproject.org/wiki/L10N/Teams/.

2.9. Presentarsi

  1. Una volta ottenuto accesso per editare la wiki, creare una pagina p! ersonale su un URL tipo questo: http://fedoraproject.org/wiki/FirstnameLastname/. Ciò è utilissimo per i contributori Fedora per conoscersi e contattarsi.

  2. Inviare una breve presentazione di se http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/ alla mailing list fedora-trans-list ed alla lista del team del proprio linguaggio.

2.10. Creare un account Bugzilla

Visitare https://bugzilla.redhat.com/bugzilla/createaccount.cgi/ per creare un account Bugzilla.

2.11. Checklist

Si dovrà essere in possesso di quanto segue:

  • Sottoscrizione alle mailing list fedora-trans-list ed a quella specifica per il proprio linguaggio, se ce n'è una.

  • Una chiave SSH

  • Una chiave GPG

  • Un account fedora

  • Appartenenza al gruppo cvsl10n

  • Un account wiki

  • Il proprio linguaggio ed il team appariranno su http://fedoraproject.org/wiki/L10N/Teams/

  • Un account Bugzilla

  • Un homeapge personale sulla wiki

  • Una presentazione di se spedita alla mailing list

A questo punto ci si potrà sedere per godersi quanto ottenuto. Ora si è pienamente riconosciuti come membri della comunità! ; Fedora, capaci di firmare digitalmente documenti ed emails, ! inviare contributi ai nostri CVS, publicare contenuti sulla wiki, segnalare errori, seguire le discussioni dei nostri gruppi e partecipare agli altri teams Fedora.

Indietro   Avanti
Guida rapida alle traduzioni Partenza 3. Tradurre il software
+ +
+ + + + + + + +
2. Accounts e sottoscrizioni
+Indietro   Avanti +
+
+
+
+

2. Accounts e sottoscrizioni

+

Per diventare un Traduttore Fedora, si deve aderire ad accounts e sottoscrizioni come descritto in questo capitolo. Se si hanno domande, postarle sulla fedora-trans-list, o chiedere aiuto via Internet Relay Chat, oIRC, su irc.freenode.org sul canale #fedora-l10n.

+
+

2.1. Sottoscrivere la mailing list

+
    +

  1. Visitare https://listman.redhat.com/mailman/listinfo/fedora-trans-list/ e sottoscrivere la mailing list principale delle traduzioni.

    2. +

  2. Attendere l'email di conferma che contiene un link per confermare la sottoscrizione. Cliccare il link per confermare la sottoscrizione.

    3. +

  3. Controllare http://fedoraproject.org/wiki/L10N/Teams/ per vedere se ci sono speciali mailing list per il proprio linguaggio. Se si, sottoscrivere anche quelle liste.

    4. +
+
+
+

2.2. Creazione di una chiave SSH

+

Se si possiede già una chiave SSH, è possibile utilizzarla per lavorare in Fedora. In quel caso, come nella seguente procedura, si proceda a Passo 2. Se non si ha ancora una chiave SSH, si cominci con il primo passo qui sotto:

+
    +
  1. +

    Inserire il seguente comando:

    +
    ssh-keygen -t dsa
    +

    Accettare la locazione predefinita (~/.ssh/id_dsa) ed immettere una passphrase.

    +
    + + + + + +
    [Attenzione]Ricordare la passphrase

    Si avrà bisogno della passphrase per accedere al repositorio CVS. Non potrà essere recuperata se dimenticata.

    +
    2. +
  2. +

    Cambiare i permessi alla chiave ed alla directory .ssh:

    +
    chmod 700 ~/.ssh chmod 600 ~/.ssh/id_dsa chmod 644 ~/.ssh/id_dsa.pub
    +
    3. +

  3. Copiare ed incollare la chiave SSH nello spazio fornito per poter completare la sottoscrizione all'account.

    4. +
+
+
+

2.3. Creazione di una chiave GPG

+
    +
  1. +

    Generare una chiave scrivendo in un terminale:

    +
    gpg --gen-key
    +

    Si verrà guidati attraverso il processo da una serie di prompts. I valori predefiniti sono sufficienti per la maggior parte dei casi. Ricordarsi di scegliere una buona password.

    +
    + + + + + +
    [Suggerimento]Scegliere una buona password
    +

    Una buona password:

    +
      +

    • consiste di lettere maiuscole e minuscole, numeri, segni di punteggiatura, ed altri caratteri

      • +

    • non include alcuna parola o nome, con o senza sostituzioni

      • +

    • non è la stessa password utilizzata su altri sistemi

      • +
    +
    +
    2. +

  2. Nel testo risultante, si troverà l'ID chiave nella riga che somiglia a "pub 1024D/1B2AFA1C". L'ID chiave è la "parola" di 8 caratteri dopo lo slash (/). Nell'esempio precedente l'ID chiave GPG è 1B2AFA1C. Scriversi il proprio ID chiave.

    3. +
  3. +

    Esportare la propria chiave pubblica su un server pubblico affinchè anche altri possano trovarla, con il seguente comando, sostituire il proprio ID chiave:

    +
    gpg --keyserver subkeys.pgp.net --send-keys GPGKEYID
    +
    4. +
+
+
+

2.4. Richiedere un account

+
    +

  1. Per richiedere un account Fedora, visitare https://admin.fedoraproject.org/accounts/ e selezionare Apply for a new account.

    2. +

  2. Riempire il form e scegliere una password per l'account Fedora. Immettere le informazioni sull'ID chiave GPG e la chiave SSH. Nel campo Comments, scrivere la lingua su cui si è pianificato di lavorare.

    3. +
+
+
+

2.5. Firmare la CLA

+

Si deve completare la Contributors License Agreement, o CLA.

+
    +

  1. Visitare https://admin.fedoraproject.org/accounts/send-cla.cgi. Autenticarsi usando il proprio username e password dal processo precedente.

    2. +

  2. Attendere la ricezione di un email con un allegato. L'allegato è un accordo che si deve firmare e restituire. Salvare l'allegato sul Desktop.

    3. +

  3. Doppio-cliccare il file sul Desktop per aprirlo con un editor. Aggiungere la frase "I agree" ed il proprio nome completo.

    4. +
  4. +

    Firmare digitalmente il file di testo usando la propria chiave GPG con il seguente comando, fornendo la password quando richiestta:

    +
    gpg -a --sign fedora-icla-{username}.txt
    +

    In quel momento comparirà un nuovo file sul desktop che termina per .asc. Questo file è la versione firmata della CLA.

    +
    5. +

  5. Aprire il client email e rispondere alla lettera della CLA. Allegare il file firmato che termina con .asc, e spedire l'email.

    6. +
+
+
+

2.6. Unirsi al gruppo cvsl10n +

+
    +

  1. Visitare https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1. Selezionare Add new membership alla fine della pagina. Nel campo Groupname, inserire cvsl10n e selezionare Add.

    2. +

  2. Un amministratore verrà notificato della tua partecipazione, e ti offrirà di sponsorizzarti. Per questo passaggio potrebbero volerci da un ora a un po di giorni.

    3. +
+
+ + + + + +
[Attenzione]Attenzione

I restanti passi aiuteranno nella verifica dell'accesso e delle grant dei privilegi a tutte le infrastrutture Fedora di cui si potrà aver necessità in futuro. I manutentori dei linguaggi e le persone che iniziano nuovi linguaggi dovranno seguirli. Nonostante essi siano opzionali per i traduttori, ogniuno è incoraggiato a seguirli.

+
+
+

2.7. Verifica dell'accesso

+
    +
  1. +

    Installare il pacchetto cvs, se non è già installato, con i seguenti comandi:

    +
    su -c 'yum install cvs'
    +
    2. +
  2. +

    Eseguire il checkout di alcuni files PO con il seguente comando, sostituire l'username e fornire la propria passphrase della chiave SSH quando richiesto:

    +
    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/l10n cvs co web ls web/flpweb/po
    +
    3. +
+
+
+

2.8. Creare un account wiki

+
    +

  1. Visitare http://fedoraproject.org/wiki/UserPreferences/. Per username, scegliere un nome tipo 'NomeCognome' e selezionare Create Profile.

    2. +

  2. Un utente wiki corrente può dare a sua volta l'accesso per editare la wiki. Contattare qualcuno dell'Edit Group su http://fedoraproject.org/wiki/EditGroup/, o aggiungere il proprio nome alla EditGroupQueue su http://fedoraproject.org/wiki/EditGroupQueue/, e qualcuno in breve tempo fornirà l'accesso desiderato.

    3. +

  3. Se si comincia un nuovo linguaggio, o si vuole diventare il manutentore di uno, aggiungere le proprie informazioni alla pagina L10N/Teams su http://fedoraproject.org/wiki/L10N/Teams/.

    4. +
+
+
+

2.9. Presentarsi

+
    +

  1. Una volta ottenuto accesso per editare la wiki, creare una pagina personale su un URL tipo questo: http://fedoraproject.org/wiki/FirstnameLastname/. Ciò è utilissimo per i contributori Fedora per conoscersi e contattarsi.

    2. +

  2. Inviare una breve presentazione di se http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/ alla mailing list fedora-trans-list ed alla lista del team del proprio linguaggio.

    3. +
+
+
+

2.10. Creare un account Bugzilla

+

Visitare https://bugzilla.redhat.com/bugzilla/createaccount.cgi/ per creare un account Bugzilla.

+
+
+

2.11. Checklist

+

Si dovrà essere in possesso di quanto segue:

+
    +

  • Sottoscrizione alle mailing list fedora-trans-list ed a quella specifica per il proprio linguaggio, se ce n'è una.

    • +

  • Una chiave SSH

    • +

  • Una chiave GPG

    • +

  • Un account fedora

    • +

  • Appartenenza al gruppo cvsl10n

    • +

  • Un account wiki

    • +

  • Il proprio linguaggio ed il team appariranno su http://fedoraproject.org/wiki/L10N/Teams/

    • +

  • Un account Bugzilla

    • +

  • Un homeapge personale sulla wiki

    • +

  • Una presentazione di se spedita alla mailing list

    • +
+

A questo punto ci si potrà sedere per godersi quanto ottenuto. Ora si è pienamente riconosciuti come membri della comunità Fedora, capaci di firmare digitalmente documenti ed emails, inviare contributi ai nostri CVS, publicare contenuti sulla wiki, segnalare errori, seguire le discussioni dei nostri gruppi e partecipare agli altri teams Fedora.

+
+
+
+
+ + + + + + + + + + + +
+Indietro   Avanti +
Guida rapida alle traduzioni Partenza 3. Tradurre il software
+
+ displayFooter('$Date$'); ?> + Index: sn_translating_docs.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/sn_translating_docs.php,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- sn_translating_docs.php 27 Dec 2007 02:06:59 -0000 1.13 +++ sn_translating_docs.php 3 Mar 2008 17:52:06 -0000 1.14 @@ -1,3 +1,15 @@ + + + +4. Tradurre la documentazione + + + + + + + + -
4. Tradurre la documentazione
Indietro   Avanti

4. Tradurre la documentazione

Per tradurre la documentazione Fedora, si deve diventare un membro del gruppo cvsl10n. Per maggiori informazioni sugli account e le sottoscrizioni, fare riferimento a Sezione 2, «Accounts e sottoscrizioni».

Per tradurre la documentazione, si dov! rà avere un sistema Fedora 5 o superiore con i seguenti pacchetti installati:

  • gnome-doc-utils

  • xmlto

  • make

Il pacchetto gnome-doc-utils fornisce il comando xml2po, e non richiede l'installazione dell'ambiente desktop GNOME. I pacchetti xmlto e make contengono strumenti necessari alla verifica della compilazione e delle traduzioni.

Per installare questi pacchetti, usare il seguente comando:

su -c 'yum install gnome-doc-utils xmlto make'

4.1. Cominciamo

La documentazione Fedora &#! 232; conservata in un repositorio CVS sotto la directory docs/. Per elencare i moduli disponibili, eseguire i seguenti comandi:

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
-cvs co -c

Per scaricare un modulo da tradurre, elencare i moduli correnti nel repositorio quindi eseguire il check out di quel modulo. Si deve anche eseguire il check out del modulo docs-common per lavorare con alcuni moduli.

+
+

+
+
+
+
+
+
+
+
4. Tradurre la documentazione

+Indietro   Avanti
+

+

+

+

+
4. Tradurre la documentazione

+
Per tradurre la documentazione Fedora, si deve diventare un membro del gruppo cvsl10n. Per maggiori informazioni sugli account e le sottoscrizioni, fare riferimento a Sezione 2, «Accounts e sottoscrizioni».

+
Per tradurre la documentazione, si dovrà avere un sistema Fedora 5 o superiore con i seguenti pacchetti installati:

+
    
+
  • gnome-doc-utils
    • 
+
  • xmlto
    • 
+
  • make
    • 
+

+
Il pacchetto gnome-doc-utils fornisce il comando xml2po, e non richiede l'installazione dell'ambiente desktop GNOME. I pacchetti xmlto e make contengono strumenti necessari alla verifica della compilazione e delle traduzioni.

+
Per installare questi pacchetti, usare il seguente comando:

+
su -c 'yum install gnome-doc-utils xmlto make'

+

+
4.1. Cominciamo

+
La documentazione Fedora è conservata in un repositorio CVS sotto la directory docs/. Per elencare i moduli disponibili, eseguire i seguenti comandi:

+
export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
+cvs co -c

+
Per scaricare un modulo da tradurre, elencare i moduli correnti nel repositorio quindi eseguire il check out di quel modulo. Si deve anche eseguire il check out del modulo docs-common per lavorare con alcuni moduli.

+
       cvs co release-notes/
-    
Alcuni moduli sono specifici della versione, vuol dire che hanno una branch, o sottodirectory, per ciascuna versione di Fedora:
ls release-notes/
-CVS  F-7  FC-5  FC-6  FC3  FC4  devel
La branca devel/ è utilizzata per le imminenti versioni di Fedora. Spesso i traduttori lavorano su questa branca, e portano i cambiamenti sulle branche precedenti se necessario.
4.2. Creare i files comuni
Se si sta creando la primissima traduzione per una lingua, si dovrà prima tradurre alcuni files comuni usati in tutti i documenti della lingua. I files comuni si trovano in docs-common/common/.
[Nota]Esempio per la lingua pt_BR
I seguenti esempi usano il codice della lingua pt_BR. Si sostituisca il codice della lingua locale in questi comandi come necessario.
  1. Leggere il file README.txt in docs-common/common/entities e seguire le indicazioni per creare le nuove entità.
  2. Una volta create le entità comuni per la lingua ed eseguito il commit dei files al CVS, creare i files di lingua per le note legali:
    cd docs-common/common/
+    
    
+
    Alcuni moduli sono specifici della versione, vuol dire che hanno una branch, o sottodirectory, per ciascuna versione di Fedora:
    
+
    ls release-notes/
+CVS  F-7  FC-5  FC-6  FC3  FC4  devel
    
+
    La branca devel/ è utilizzata per le imminenti versioni di Fedora. Spesso i traduttori lavorano su questa branca, e portano i cambiamenti sulle branche precedenti se necessario.
    
+

+

+
4.2. Creare i files comuni

+
Se si sta creando la primissima traduzione per una lingua, si dovrà prima tradurre alcuni files comuni usati in tutti i documenti della lingua. I files comuni si trovano in docs-common/common/.

+

+
+
+
+
+
+
[Nota]Esempio per la lingua pt_BR
+
I seguenti esempi usano il codice della lingua pt_BR. Si sostituisca il codice della lingua locale in questi comandi come necessario.

+
    
+
  1. Leggere il file README.txt in docs-common/common/entities e seguire le indicazioni per creare le nuove entità.
    2. 
+
  2. 
+
    Una volta create le entità comuni per la lingua ed eseguito il commit dei files al CVS, creare i files di lingua per le note legali:
    
+
    cd docs-common/common/
 cp legalnotice-opl-en_US.xml legalnotice-opl-pt_BR.xml
 cp legalnotice-relnotes-en_US.xml legalnotice-relnotes-pt_BR.xml	
-
    [Importante]Non tradurre le note legali
    Per assicurare che sia legalmente equivalente in tutte le lingue, non tradurre la OPL.
  3. Quindi eseguire il commit al CVS anche di quei files:
    cvs add legalnotice-*-pt_BR.xml
-cvs ci -m 'Added legal notices for pt_BR' legalnotice-*-pt_BR.xml
  4. Successivamente, creare la filigrana di bozza per la lingua nella cartella docs-common/images/:
    cd docs-common/images/
-cp watermark-en_US.svg watermark-pt_BR.svg
    Tradurre gli elementi di testo nell'SVG. Quindi aggiungere il file SVG tradotto al Makefile, produrre il PNG ed eseguire il commit dei risultati:
    make watermark-pt_BR.png
+
    
+
    
+
+
+
+
+
+
    [Importante]Non tradurre le note legali
    Per assicurare che sia legalmente equivalente in tutte le lingue, non tradurre la OPL.
    
+
    5. 
+
  5. 
+
    Quindi eseguire il commit al CVS anche di quei files:
    
+
    cvs add legalnotice-*-pt_BR.xml
+cvs ci -m 'Added legal notices for pt_BR' legalnotice-*-pt_BR.xml
    
+
    6. 
+
  6. 
+
    Successivamente, creare la filigrana di bozza per la lingua nella cartella docs-common/images/:
    
+
    cd docs-common/images/
+cp watermark-en_US.svg watermark-pt_BR.svg
    
+
    Tradurre gli elementi di testo nell'SVG. Quindi aggiungere il file SVG tradotto al Makefile, produrre il PNG ed eseguire il commit dei risultati:
    
+
    make watermark-pt_BR.png
 cvs add watermark-pt_BR*
-cvs ci -m 'Added pt_BR images' Makefile watermark-pt_BR*
[Importante]Errori di compilazione
Se non si creano queste entità comuni, la compilazione del documento potrebbe fallire.
4.3. Usare le applicazioni per la traduzione
La directory po/ contiene i files .po usati per tradurre i contenuti. Contien!
 e anche un file .pot, o PO template, che è utilizzato per creare nuovi files .po se necessario.
Se la directory po/ non esiste, è possibile crearla assieme al file template per la traduzione con i seguenti comandi:
mkdir po
+cvs ci -m 'Added pt_BR images' Makefile watermark-pt_BR*

+
+

+

+
+
+
+
+
+
[Importante]Errori di compilazione
Se non si creano queste entità comuni, la compilazione del documento potrebbe fallire.

+

+

+
4.3. Usare le applicazioni per la traduzione

+
La directory po/ contiene i files .po usati per tradurre i contenuti. Contiene anche un file .pot, o PO template, che è utilizzato per creare nuovi files .po se necessario.

+
Se la directory po/ non esiste, è possibile crearla assieme al file template per la traduzione con i seguenti comandi:

+
mkdir po
 cvs add po/
 make pot
-
[Attenzione]Non fare cambiamenti manuali ai POT
Gli autori e gli editori generano il file POT dai file sorgenti XML, che sovrascrivono qualunque cambiamento manuale al file POT. Se si individua un problema nei messaggi originali di un file POT, visitare Bugzilla su https://bugzilla.redhat.com inviare una segnalazione d'errore verso il documento.
Per lavorare con un  .po editor come KBabel o gtranslator, seguire i seguenti passi.!
 
[Nota]Esempio per la lingua pt_BR
I seguenti esempi usano il codice della lingua pt_BR. Si sostituisca il codice della lingua locale in questi comandi come necessario.
  1. Cambiare la directory
    In un terminale, entrare nella directory del documento che si vuole tradurre:
    cd ~/docs/example-tutorial
  2. Aggiunta della lingua all'elenco
    Per aggiungere la propria localizzazione, si dovrà trovare e cambiare l!
 'appropriato elenco di località. Alcuni documenti stanno !
 usando i
l file po/LINGUAS, come standardizzato nel progetto GNOME, per tracciare le localizzazioni. Alcuni documenti non sono ancora stati aggiornati a questo standard. Se si trova che il modulo che si sta traducendo non è stato aggiornato, si notifichi il Fedora Documentation Project o si invii una segnalazione d'errore usando Bugzilla.
    Nel file po/LINGUAS, aggiungere il codice della lingua tradotta all'elenco. Mantenere la lista in ordine alfabetico.
  3. Creare il file PO
    Creare un nuovo file .po per la lingua:
    make po/pt_BR.po
  4. Tradurre le stringhe
    Per tradurre il file, usare la stessa applicazione usata per tradurre il software:
    kbabel po/pt_BR.po
  5. Controllare l'integrità
    Prima di inviare i cambiamenti, controllare l'integrità dell'XML con il seguente comando. Questo assicura una corretta compilazione a tutti gli utenti.
    make html-pt_BR
    E' possibile leggere i files HTML risultanti con un navigatore Web.
    [Importante]Provare sempre la traduzione
    Non passare al passo successivo o eseguire il commit dei cambiamenti finchè non si è verificato il proprio lavoro. Cambiamenti !
 errati possono rompere documenti per altri utenti, editori, e !
 applicaz
ioni automatizzate.
  6. Eseguire il commit del lavoro
    Quando si è terminata la traduzione, eseguire il commit del file .po. Si noterà la percentuale di completamento od alcuni altri utili messaggi durante il commit.
    cvs ci -m 'Translating... 400/10/126' po/pt_BR.po
4.4. Cosa tradurre
I più importanti moduli/directory di documentazione per ogni versione sono le seguenti:
  • docs-common/common/entities
  • release-notes/devel
  • homepage/devel
  • install-guide/devel
  • about-fedora/devel
  • readme/devel
  • readme-burning-isos/devel
  • readme-live-image/devel
Per vedere tutti i documenti disponibili nel repositorio della documentazione, eseguire:
export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
-cvs co -c
Indietro   Avanti
3. Tradurre il software Partenza Indice

+
+
+ + + + + +
[Attenzione]Non fare cambiamenti manuali ai POT

Gli autori e gli editori generano il file POT dai file sorgenti XML, che sovrascrivono qualunque cambiamento manuale al file POT. Se si individua un problema nei messaggi originali di un file POT, visitare Bugzilla su https://bugzilla.redhat.com inviare una segnalazione d'errore verso il documento.

+

Per lavorare con un .po editor come KBabel o gtranslator, seguire i seguenti passi.

+
+ + + + + +
[Nota]Esempio per la lingua pt_BR +

I seguenti esempi usano il codice della lingua pt_BR. Si sostituisca il codice della lingua locale in questi comandi come necessario.

+
    +
  1. +

    Cambiare la directory

    +

    In un terminale, entrare nella directory del documento che si vuole tradurre:

    +
    cd ~/docs/example-tutorial
    +
    2. +
  2. +

    Aggiunta della lingua all'elenco

    +

    Per aggiungere la propria localizzazione, si dovrà trovare e cambiare l'appropriato elenco di località. Alcuni documenti stanno usando il file po/LINGUAS, come standardizzato nel progetto GNOME, per tracciare le localizzazioni. Alcuni documenti non sono ancora stati aggiornati a questo standard. Se si trova che il modulo che si sta traducendo non è stato aggiornato, si notifichi il Fedora Documentation Project o si invii una segnalazione d'errore usando Bugzilla.

    +

    Nel file po/LINGUAS, aggiungere il codice della lingua tradotta all'elenco. Mantenere la lista in ordine alfabetico.

    +
    3. +
  3. +

    Creare il file PO

    +

    Creare un nuovo file .po per la lingua:

    +
    make po/pt_BR.po
    +
    4. +
  4. +

    Tradurre le stringhe

    +

    Per tradurre il file, usare la stessa applicazione usata per tradurre il software:

    +
    kbabel po/pt_BR.po
    +
    5. +
  5. +

    Controllare l'integrità

    +

    Prima di inviare i cambiamenti, controllare l'integrità dell'XML con il seguente comando. Questo assicura una corretta compilazione a tutti gli utenti.

    +
    make html-pt_BR
    +

    E' possibile leggere i files HTML risultanti con un navigatore Web.

    +
    + + + + + +
    [Importante]Provare sempre la traduzione

    Non passare al passo successivo o eseguire il commit dei cambiamenti finchè non si è verificato il proprio lavoro. Cambiamenti errati possono rompere documenti per altri utenti, editori, e applicazioni automatizzate.

    +
    6. +
  6. +

    Eseguire il commit del lavoro

    +

    Quando si è terminata la traduzione, eseguire il commit del file .po. Si noterà la percentuale di completamento od alcuni altri utili messaggi durante il commit.

    +
    cvs ci -m 'Translating... 400/10/126' po/pt_BR.po
    +
    7. +
+
+
+

4.4. Cosa tradurre

+

I più importanti moduli/directory di documentazione per ogni versione sono le seguenti:

+
    +

  • docs-common/common/entities

    • +

  • release-notes/devel

    • +

  • homepage/devel

    • +

  • install-guide/devel

    • +

  • about-fedora/devel

    • +

  • readme/devel

    • +

  • readme-burning-isos/devel

    • +

  • readme-live-image/devel

    • +
+

Per vedere tutti i documenti disponibili nel repositorio della documentazione, eseguire:

+
export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
+cvs co -c
+
+
+
+
+ + + + + + + + + + + +
+Indietro   Avanti +
3. Tradurre il software Partenza Indice
+
+ displayFooter('$Date$'); ?> + Index: sn_translating_software.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/it/sn_translating_software.php,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- sn_translating_software.php 27 Dec 2007 02:07:00 -0000 1.13 +++ sn_translating_software.php 3 Mar 2008 17:52:06 -0000 1.14 @@ -1,3 +1,15 @@ + + + +3. Tradurre il software + + + + + + + + -
3. Tradurre il software
Indietro   Avanti

3. Tradurre il software

La parte traducibile di un pacchetto software è disponibile in uno o più file po. Questi files sono mantenuti in uno dei numerosi Version Control System (VCSs) dipendenti dal progetto, come CVS, Subversion, Mercurial e git. Questi potrebbero essere ospitati sul server fedoraproject.org o i18n.redhat.c! om. Il i18n.redhat.com non è abilitato a lavorare con il gruppo cvsl10n. Per sottoscrivere un account su i18n.redhat.com, si prega di visitare http://i18n.redhat.com/cgi-bin/i18n-signup/. Questo avviso sarà probabilmente presto deprecato.

Questo capitolo spiega come tradurre i moduli ospitati su fedoraproject.org. I traduttori dovranno lavorare su due interfacce, una per ottenere i moduli e l'altra per eseguire il commit dei moduli. Prima di cominciare, si dovranno preparare le directory che dovranno contenere i files po.

3.1. Struttura dei files

Per sapere quali moduli sono t! raducibili, si visiti l'elenco dei moduli su https://translate.fedoraproject.org/submit/module/.

Prima di scaricare qualsiasi file, si prepari la struttura necessaria a contenerli. La struttura descritta più avanti è solo un esempio, ed è possibile formarne una differente. Per esempio, se si vuole scaricare il modulo comps per la traduzione, creare le seguenti directory.

mkdir -p ~/myproject/comps/

Successivamente per lavorare su un altro modulo, creare una directory con il nome del modulo sotto la directory genitore tipo la myproject.

3.2. Ottenere e tradurre i moduli

Ora che si è preparata la struttura della directory, è possibile scaricare un file ! da tradurre.

  1. Visitare http://translate.fedoraproject.org/submit/module/ e selezionare il modulo prescelto. L'interfaccia ci redirezionerà alla pagina di quel modulo, tipo http://translate.fedoraproject.org/submit/module/comps/.

  2. Scorrendo la pagina, si vedrà una tabella con tutti i files po disponibili. All'inizio dell'elenco apparirà il file pot. Usare l'icona verde di download vicina ad ogni linguaggio per scaricare il file nella directory creata nella sezione precedente.

  3. Poiché il nome del file con cui eseguire il commit deve seguire il nome convenzionale di lang.po, cambiare il nome del file scaricato.! Il seguente esempio usa il linguaggio giapponese per il file ! po:

    ls ~/myproject/comps/
+
+
    
+
+
+
+
+
+
+
+
    3. Tradurre il software
    
+Indietro   Avanti
+
    
+
    
+
    
+
    
+
    3. Tradurre il software
    
+
    La parte traducibile di un pacchetto software è disponibile in uno o più file po. Questi files sono mantenuti in uno dei numerosi Version Control System (VCSs) dipendenti dal progetto, come CVS, Subversion, Mercurial e git. Questi potrebbero essere ospitati sul server fedoraproject.org o altri sistemi.
    
+
    Questo capitolo spiega come tradurre i moduli ospitati su fedoraproject.org. I traduttori dovranno lavorare su due interfacce, una per ottenere i moduli e l'altra per eseguire il commit dei moduli. Prima di cominciare, si dovranno preparare le directory che dovranno contenere i files po.
    
+
    
+
    3.1. Struttura dei files
    
+
    Per sapere quali moduli sono traducibili, si visiti l'elenco dei moduli su https://translate.fedoraproject.org/submit/module/.
    
+
    Prima di scaricare qualsiasi file, si prepari la struttura necessaria a contenerli. La struttura descritta più avanti è solo un esempio, ed è possibile formarne una differente. Per esempio, se si vuole scaricare il modulo comps per la traduzione, creare le seguenti directory.
    
+
    mkdir -p ~/myproject/comps/
    
+
    Successivamente per lavorare su un altro modulo, creare una directory con il nome del modulo sotto la directory genitore tipo la myproject.
    
+
    
+
    
+
    3.2. Ottenere e tradurre i moduli
    
+
    Ora che si è preparata la struttura della directory, è possibile scaricare un file da tradurre.
    
+
      
+
    1. Visitare http://translate.fedoraproject.org/submit/module/ e selezionare il modulo prescelto. L'interfaccia ci redirezionerà alla pagina di quel modulo, tipo http://translate.fedoraproject.org/submit/module/comps/.
      2. 
+
    2. Scorrendo la pagina, si vedrà una tabella con tutti i files po disponibili. All'inizio dell'elenco apparirà il file pot. Usare l'icona verde di download vicina ad ogni linguaggio per scaricare il file nella directory creata nella sezione precedente.
      3. 
+
    3. 
+
      Poiché il nome del file con cui eseguire il commit deve seguire il nome convenzionale di lang.po, cambiare il nome del file scaricato. Il seguente esempio usa il linguaggio giapponese per il file po:
      
+
      ls ~/myproject/comps/
 comps.HEAD.ja.po
 mv ~/myproject/comps/comps.HEAD.ja.po ja.po 
 ls ~/myproject/comps/
-ja.po
    4. Ora il file è pronto per la traduzione. Traducete il file po per il vostro linguaggio in un po Editor come KBabel o gtranslator.
    5. Controllare l'integrità del file prima di inviarlo.
      msgfmt -cvo /dev/null ja.po
    [Importante]Importante
    Se appare un qualsiasi messaggio d'errore, si corregga il file prima di inviarlo.
    3.3. Invio dei moduli
    Una volta terminato il lavoro di traduzione, il file può essere inviato da un interfaccia separata chiamata Transifex. E' possibile trovare informazioni dettagliate su questo strumento web su https://translate.fedoraproject.org/submit..
    1. Visitare https://translate.fedoraproject.org/submit e cliccare il link Jump to Modules! per andare alla pagina dei Modules and repositories. Questa pagina mostra i moduli dei quali è possibile inviare le modifiche. Trovare il modulo da inviare nell'elenco e c!
 liccarlo per visitare la pagina di Subm
it per quel modulo.
    2. Login
      In fondo alla pagina di Submit, selezionare Authenticate as a translator per visitare la pagina di Login. Autenticarsi con l'username e la password del Fedora Account System. Si verrà quindi riportati alla pagina di Submit dopo un login riuscito.
    3. Invio
      Nella sezione denominata Local file, cliccare il bottone browse per localizzare il file tradotto.
      Nella sezione denominata Destination file, cliccare il campo del menu a tendina Overwrite an existing file: per selezionare il linguaggio.
      Nella sezione denominata Commit message, immettere un commento a testo libero per descrivere il lavoro svolto.
      Selezionando il bottone Preview, si arriverà alla pagina Preview submission. Controllare la sezione Differences per verificare i cambiamenti e cliccare il bottone Submit.
      La pagina Submit apparirà e mostrerà il messaggio Your submission was committed successfully. Se si riceverà un messaggio d'errore o un qualsiasi messaggio diverso da questo, lo si invii alla mailing list del Fedora Translation Project affinché possa esserne rintracciata la causa.
    3.4. Aggiung!
 ere un n
uovo file .po
    Se non c'è alcun file po per la lingua desiderata, aggiungerlo.
    1. Scaricare il file pot e copiarlo come proprio file di linguaggio po.
      cp ~/myproject/comps/comps.HEAD.pot ja.po
+ja.po
      
+
      2. 
+
    2. Ora il file è pronto per la traduzione. Traducete il file po per il vostro linguaggio in un po Editor come KBabel o gtranslator.
      3. 
+
    3. 
+
      Controllare l'integrità del file prima di inviarlo.
      
+
      msgfmt -cvo /dev/null ja.po
      
+
      4. 
+
    
+
    
+
+
+
+
+
+
    [Importante]Importante
    Se appare un qualsiasi messaggio d'errore, si corregga il file prima di inviarlo.
    
+
+
+

3.3. Invio dei moduli

+

Una volta terminato il lavoro di traduzione, il file può essere inviato da un interfaccia separata chiamata Transifex. E' possibile trovare informazioni dettagliate su questo strumento web su https://translate.fedoraproject.org/submit..

+
    +

  1. Visitare https://translate.fedoraproject.org/submit e cliccare il link Jump to Modules! per andare alla pagina dei Modules and repositories. Questa pagina mostra i moduli dei quali è possibile inviare le modifiche. Trovare il modulo da inviare nell'elenco e cliccarlo per visitare la pagina di Submit per quel modulo.

    2. +
  2. +

    Login

    +

    In fondo alla pagina di Submit, selezionare Authenticate as a translator per visitare la pagina di Login. Autenticarsi con l'username e la password del Fedora Account System. Si verrà quindi riportati alla pagina di Submit dopo un login riuscito.

    +
    3. +
  3. +

    Invio

    +

    Nella sezione denominata Local file, cliccare il bottone browse per localizzare il file tradotto.

    +

    Nella sezione denominata Destination file, cliccare il campo del menu a tendina Overwrite an existing file: per selezionare il linguaggio.

    +

    Nella sezione denominata Commit message, immettere un commento a testo libero per descrivere il lavoro svolto.

    +

    Selezionando il bottone Preview, si arriverà alla pagina Preview submission. Controllare la sezione Differences per verificare i cambiamenti e cliccare il bottone Submit.

    +

    La pagina Submit apparirà e mostrerà il messaggio Your submission was committed successfully. Se si riceverà un messaggio d'errore o un qualsiasi messaggio diverso da questo, lo si invii alla mailing list del Fedora Translation Project affinché possa esserne rintracciata la causa.

    +
    4. +
+
+
+

3.4. Aggiungere un nuovo file .po

+

Se non c'è alcun file po per la lingua desiderata, aggiungerlo.

+
    +
  1. +

    Scaricare il file pot e copiarlo come proprio file di linguaggio po.

    +
    cp ~/myproject/comps/comps.HEAD.pot ja.po
 kbabel ja.po
-msgfmt -cvo /dev/null ja.po

  2. Una volta terminata la traduzione, seguire gli stessi passi per la verifica e l'invio della traduzione descritti nella sezione precedente.

  3. Nella sezione denominata Destination file, scrivere il nuovo nome del file nel campo Type the name for a new one:, sostituendo il nome del file con quello della propria lingua:

    po/ja.po

3.5. Correggere le bozze

Se si vuole verificare la traduzione nel software, seguire i seguenti passi:

  1. Entrare nella directory del pacchetto che si vuole verificare:

    cd ~/myproject/!
 package_name

  2. Convertire il file .po in file .mo con msgfmt:

    msgfmt lang.po

  3. Sovrascrivere il file .mo esistente in /usr/share/locale/lang/LC_MESSAGES/. Ma prima, fare un back up del file esistente:

    cp /usr/share/locale/lang/LC_MESSAGES/package_name.mo package_name.mo-backup
-mv package_name.mo /usr/share/locale/lang/LC_MESSAGES/

  4. Analizzare il pacchetto con le stringhe tradotte come parte dell'applicazione:

    LANG=langpackage_command

L'applicazione relativa al pacchetto tradotto verrà eseguita con le stringhe tradotte.

Indietro   Avanti
2. Accounts e sottoscrizioni Partenza 4. Tradurre la documentazione
+msgfmt -cvo /dev/null ja.po + +

  • Una volta terminata la traduzione, seguire gli stessi passi per la verifica e l'invio della traduzione descritti nella sezione precedente.

    • +
  • +

    Nella sezione denominata Destination file, scrivere il nuovo nome del file nel campo Type the name for a new one:, sostituendo il nome del file con quello della propria lingua:

    +
    po/ja.po
    +
    • +
    + +
    +

    3.5. Correggere le bozze

    +

    Se si vuole verificare la traduzione nel software, seguire i seguenti passi:

    +
      +
    1. +

      Entrare nella directory del pacchetto che si vuole verificare:

      +
      cd ~/myproject/package_name
      +
      2. +
    2. +

      Convertire il file .po in file .mo con msgfmt:

      +
      msgfmt lang.po
      +
      3. +
    3. +

      Sovrascrivere il file .mo esistente in /usr/share/locale/lang/LC_MESSAGES/. Ma prima, fare un back up del file esistente:

      +
      cp /usr/share/locale/lang/LC_MESSAGES/package_name.mo package_name.mo-backup
+mv package_name.mo /usr/share/locale/lang/LC_MESSAGES/
      +
      4. +
    4. +

      Analizzare il pacchetto con le stringhe tradotte come parte dell'applicazione:

      +
      LANG=langpackage_command
      +
      5. +
    +

    L'applicazione relativa al pacchetto tradotto verrà eseguita con le stringhe tradotte.

    +
    + +
    +
    + + + + + + + + + + + +
    +Indietro   Avanti +
    2. Accounts e sottoscrizioni Partenza 4. Tradurre la documentazione
    +
    + displayFooter('$Date$'); ?> + From fedora-websites-list at redhat.com Mon Mar 3 17:55:28 2008 From: fedora-websites-list at redhat.com (Paul W. Frields (pfrields)) Date: Mon, 3 Mar 2008 17:55:28 GMT Subject: web/html/docs/translation-quick-start-guide index.php,1.17,1.18 Message-ID: <200803031755.m23HtSZE002335@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/fedora/web/html/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2306 Modified Files: index.php Log Message: Remove nonsensical redirections, and instead just remove unfinished translations from the list until they are updated by the translators. Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/index.php,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- index.php 18 Feb 2008 15:38:39 -0000 1.17 +++ index.php 3 Mar 2008 17:54:58 -0000 1.18 @@ -15,9 +15,9 @@ Some of these are redirected to en_US until they are updated by the L10n teams in question. -->

    US English | -???????????????? | -Espa??ol | -fran??ais | + + + italiano | ????????? | Nederlands | @@ -25,12 +25,13 @@ polski | portugu??s | portugu??s brasileiro | -?????????????? | -???????????? | -svenska | -????????????

    + + + + +

    -

    Some of these languages are redirected to the US English (canonical) version until they are updated by the translation teams. This document is maintained in the "translation-quick-start-guide" module in Docs CVS, or you can translate it using the Transifex system. For more information, read the US English version of this guide.

    +

    This document is maintained in the "translation-quick-start-guide" module in Docs CVS, or you can translate it using the Transifex system. For more information, read the US English version of this guide.

    Author: pfrields Update of /cvs/fedora/web/html/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2410 Modified Files: index.php Log Message: Correct directory links for when these are actually updated. Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/index.php,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- index.php 3 Mar 2008 17:54:58 -0000 1.18 +++ index.php 3 Mar 2008 17:56:21 -0000 1.19 @@ -15,9 +15,9 @@ Some of these are redirected to en_US until they are updated by the L10n teams in question. -->

    US English | - - - + + + italiano | ????????? | Nederlands | @@ -25,10 +25,10 @@ polski | portugu??s | portugu??s brasileiro | - - - - + + + +

    This document is maintained in the "translation-quick-start-guide" module in Docs CVS, or you can translate it using the Transifex system. For more information, read the US English version of this guide.

    From fedora-websites-list at redhat.com Mon Mar 3 18:17:06 2008 From: fedora-websites-list at redhat.com (Paul W. Frields (pfrields)) Date: Mon, 3 Mar 2008 18:17:06 GMT Subject: web/html/docs index.php,1.46,1.47 Message-ID: <200803031817.m23IH6kf010505@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/fedora/web/html/docs In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10429 Modified Files: index.php Log Message: Fix link to point to current docs Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/index.php,v retrieving revision 1.46 retrieving revision 1.47 diff -u -r1.46 -r1.47 --- index.php 15 Dec 2007 21:13:32 -0000 1.46 +++ index.php 3 Mar 2008 18:16:36 -0000 1.47 @@ -51,7 +51,7 @@ FAQ (Frequently Asked Questions)
    -Virtualization in Fedora 7 +Virtualization in Fedora 7
    Live CD How-to
    From stickster at gmail.com Mon Mar 3 18:24:15 2008 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 03 Mar 2008 13:24:15 -0500 Subject: RHM widget on fedoraproject.org In-Reply-To: <1204555312.16292.3.camel@localhost.localdomain> References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> Message-ID: <1204568655.19210.4.camel@localhost.localdomain> On Mon, 2008-03-03 at 09:41 -0500, Paul W. Frields wrote: > On Sun, 2008-03-02 at 20:12 -0500, Jessica Gerber wrote: > > Hi Paul and Max, > > > > I hope you both had restful weekends. > > > > Attached is a design mock-up of what we'd like uploaded to > > fedoraproject.org (or possibly start.fedoraproject.org). We will have a > > DevFu, RHM, and TH widget that will switch every time the site is > > refreshed. > > > > What process should I follow to make this happen? Do I need to work with > > traffic? > > > > Many thanks for the opportunity to put this widget on your site! > > Hi Jess, > > For something like this, you would want to work with the Websites group. > I'm going to Cc: the fedora-websites-list so someone there can get in > touch with you. Obviously there's a huge crossover audience between > Fedora and DevFu/RHM/TH, and the actual mechanics of making the banner > work, I recall, are pretty trivial. The mockup is available at: http://fedoraproject.org/wiki/PaulWFrields/Drafts -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mostafa at daneshvar.org.uk Mon Mar 3 21:11:33 2008 From: mostafa at daneshvar.org.uk (Mostafa Daneshvar) Date: Tue, 4 Mar 2008 00:41:33 +0330 Subject: Introduce Mostafa Daneshvar Message-ID: <200803040041.33760.mostafa@daneshvar.org.uk> I'm Mostafa Daneshvar from Iran. I'm using Fedora 8 as OS. My field of interest is PHP programming and translating. As a linguist I want to contribute in translation of Fedora in different languages that I know. I know following languages : Persian,English,Arabic,Balochi and French a little. Here You can find some information about me. From mmcgrath at redhat.com Tue Mar 4 04:03:20 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 3 Mar 2008 22:03:20 -0600 (CST) Subject: Just a heads up (jigdo) Message-ID: I've heard rumors that we're going to be offering a jigdo release this time around. I directed them to post to this list so watch for it. -Mike From mmcgrath at redhat.com Tue Mar 4 04:10:00 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 3 Mar 2008 22:10:00 -0600 (CST) Subject: RHM widget on fedoraproject.org In-Reply-To: <1204568655.19210.4.camel@localhost.localdomain> References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> <1204568655.19210.4.camel@localhost.localdomain> Message-ID: On Mon, 3 Mar 2008, Paul W. Frields wrote: > On Mon, 2008-03-03 at 09:41 -0500, Paul W. Frields wrote: > > On Sun, 2008-03-02 at 20:12 -0500, Jessica Gerber wrote: > > Hi Jess, > > > > For something like this, you would want to work with the Websites group. > > I'm going to Cc: the fedora-websites-list so someone there can get in > > touch with you. Obviously there's a huge crossover audience between > > Fedora and DevFu/RHM/TH, and the actual mechanics of making the banner > > work, I recall, are pretty trivial. > > The mockup is available at: > http://fedoraproject.org/wiki/PaulWFrields/Drafts > I'm calling should vs could on this, we could do it but shouldn't. It's a slippery slope and one that I'm always worried about because our website doesn't really have a vision, but lots of different visions. Lots is good, but it'll look bad quickly. /me notes: http://farm3.static.flickr.com/2038/2304064020_11310fdfe3_b.jpg and http://www.debian.com/ We have a banner system already, I say lets use it. -Mike From duffy at fedoraproject.org Tue Mar 4 04:20:38 2008 From: duffy at fedoraproject.org (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Mon, 03 Mar 2008 23:20:38 -0500 Subject: RHM widget on fedoraproject.org In-Reply-To: References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> <1204568655.19210.4.camel@localhost.localdomain> Message-ID: <47CCCE16.6080003@fedoraproject.org> Mike McGrath wrote: > I'm calling should vs could on this, we could do it but shouldn't. It's a > slippery slope and one that I'm always worried about because our website > doesn't really have a vision, but lots of different visions. Lots is > good, but it'll look bad quickly. > > /me notes: > > http://farm3.static.flickr.com/2038/2304064020_11310fdfe3_b.jpg > > and > > http://www.debian.com/ > > We have a banner system already, I say lets use it. +1 If it's going to be that size, it should just go into banner rotation. Having two banners on the left side like that makes the left heavier than it was ever meant to be. Like Mike said, I think there are a lot of different visions for the site. So here's mine. :) I had always intended for there to be a larger main banner area in the middle, for promotion of Fedora-only things (much like the gnome.org main banner.) We didn't actually use such a design yet because of bandwidth restrictions at release times but we now do have the bandwidth to do this so I'm hoping we'll have banners of a larger size to promote Fedora-related content there soon. (example, mockup: http://i61.photobucket.com/albums/h58/mairinduffy/bigfedorabanner.png) I think the smaller banner space that we currently use now would likely be more appropriate for the RHM banner. ?m From mmcgrath at redhat.com Tue Mar 4 04:26:02 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 3 Mar 2008 22:26:02 -0600 (CST) Subject: RHM widget on fedoraproject.org In-Reply-To: <47CCCE16.6080003@fedoraproject.org> References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> <1204568655.19210.4.camel@localhost.localdomain> <47CCCE16.6080003@fedoraproject.org> Message-ID: On Mon, 3 Mar 2008, M?ir?n Duffy wrote: > Mike McGrath wrote: > > We have a banner system already, I say lets use it. > > +1 > > If it's going to be that size, it should just go into banner rotation. Having > two banners on the left side like that makes the left heavier than it was ever > meant to be. > > Like Mike said, I think there are a lot of different visions for the site. So > here's mine. :) I had always intended for there to be a larger main banner > area in the middle, for promotion of Fedora-only things (much like the > gnome.org main banner.) We didn't actually use such a design yet because of > bandwidth restrictions at release times but we now do have the bandwidth to do > this so I'm hoping we'll have banners of a larger size to promote > Fedora-related content there soon. (example, mockup: > http://i61.photobucket.com/albums/h58/mairinduffy/bigfedorabanner.png) > > I think the smaller banner space that we currently use now would likely be > more appropriate for the RHM banner. > Yeah, we've got a few different sites. I think that all of our 'sub' project sites should have the smaller banner system while the fedora-main site should be different or... I don't know, more grand but still simple? I'm not sure how else to say it. The current fp.o/ site was initially designed to be simple and light on the network, thats no longer the case so the fedoraproject.org/ site is ripe for a re-design or re-visioning. Just going to take someone with the time, guts and skill to do it. Its probably too late for the F9 release as the string freeze is tomorrow :) But we can certainly re-think it shortly after and get it in shape for F10. -Mike From mmcgrath at redhat.com Tue Mar 4 04:29:07 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 3 Mar 2008 22:29:07 -0600 (CST) Subject: Introduce Mostafa Daneshvar In-Reply-To: <200803040041.33760.mostafa@daneshvar.org.uk> References: <200803040041.33760.mostafa@daneshvar.org.uk> Message-ID: On Tue, 4 Mar 2008, Mostafa Daneshvar wrote: > I'm Mostafa Daneshvar from Iran. I'm using Fedora 8 as OS. My field of > interest is PHP programming and translating. > As a linguist I want to contribute in translation of Fedora in different > languages that I know. > I know following languages : Persian,English,Arabic,Balochi and French a > little. > > Here You can find some information about me. > Welcome to the list Mostafa. Are you also in contact with the translations team? The website is just one small portion of what we translate. -Mike From jkeating at redhat.com Tue Mar 4 14:48:02 2008 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 04 Mar 2008 09:48:02 -0500 Subject: Just a heads up (jigdo) In-Reply-To: References: Message-ID: <1204642082.3963.2.camel@localhost.localdomain> On Mon, 2008-03-03 at 22:03 -0600, Mike McGrath wrote: > I've heard rumors that we're going to be offering a jigdo release this > time around. I directed them to post to this list so watch for it. > > -Mike Thanks for the prompt Mike (: We will be trying Jigdo out. Jidgo has .jigdo files and .template files for downloading the isos. Due to client compatibility we will be offering one .jigdo file for every iso (minus the netinst.iso). These will show up in a jigdo/ directory along side iso/ and os/. The Fedora Unity folks have a lot of experience in dealing with these, I'll leave it up to them to help direct the website folks in how to offer these for download. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From 493920156 at mail.fju.edu.tw Tue Mar 4 06:56:42 2008 From: 493920156 at mail.fju.edu.tw (493920156) Date: Tue, 04 Mar 2008 14:56:42 +0800 (CST) Subject: question about Linux Message-ID: <1204613802.28717.493920156@mail.fju.edu.tw> Hi I?m studying at FU JEN CATHOLIC UNIVERSITY. And I have a school project to try out Linux and Open Office in PC. But, before doing that, I have three questions would need your advice. 1. Does your company offer free update service? (Like ?Windows Update??) 2. Does your company offer Version Upgrade? If yes, what will be the impact to existing version user? Or your company will only offer release upgrade and I don?t have to do anything but just download the new release from your web side? 3. About two questions, will they be any cost to me? From sundaram at fedoraproject.org Tue Mar 4 15:28:22 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 04 Mar 2008 20:58:22 +0530 Subject: question about Linux In-Reply-To: <1204613802.28717.493920156@mail.fju.edu.tw> References: <1204613802.28717.493920156@mail.fju.edu.tw> Message-ID: <47CD6A96.1080405@fedoraproject.org> 493920156 wrote: > Hi > I?m studying at FU JEN CATHOLIC UNIVERSITY. And I have a school project to try out Linux and Open Office in PC. But, before doing that, I have three questions would need your advice. > 1. Does your company offer free update service? (Like ?Windows Update??) > 2. Does your company offer Version Upgrade? If yes, what will be the impact to existing version user? Or your company will only offer release upgrade and I don?t have to do anything but just download the new release from your web side? > 3. About two questions, will they be any cost to me? [This webmaster id is only for questions or feedback regarding the website. In the future, head to fedora-list or use the Ask Fedora column in Fedora Weekly News for your questions] Fedora as a distribution is completely free including all updates and upgrades. There is no cost for any of the software that we provide. Note that Fedora is build within a community and while Red Hat and other organizations participate in it, it is not solely a company that is providing you the software. If you want to learn more, refer http://fedoraproject.org/wiki/Overview Rahul From mmcgrath at redhat.com Tue Mar 4 17:36:39 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Tue, 4 Mar 2008 11:36:39 -0600 (CST) Subject: Wiki changes Message-ID: I'm making some more wiki tweaks today, if you're a regular wiki user please stop by #fedora-admin and let me know how its going. Basically I'm allowing more processes to run but for a shorter amount of time. This will cause the longer running threads to be killed much sooner and should free up resources for the normal day-to-day stuff that has been suffering over the last couple of weeks. I'm looking into why we've had more timeouts recently though I suspect its because the release is close, more people are editing and using the wiki. Please let me know what your experiences are with the wiki over the next couple of days. -Mike From Robert.Papesch at hp.com Tue Mar 4 22:50:29 2008 From: Robert.Papesch at hp.com (Papesch, Robert) Date: Tue, 4 Mar 2008 22:50:29 +0000 Subject: feedback on http://fedoraproject.org/en/get-fedora Message-ID: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> hi, On the "Get Fedora" page I found the numerous options confusing. Why not add a link to this forum article? http://www.linuxforums.org/forum/linux-newbie/28214-rpm-differences-i386-i586-i686-x86_64-ppc-etc-etc.html regards Robert Papesch | Software Test Analyst | Technology Solutions Group | Hewlett-Packard New Zealand phone: +64 3 962 5634 | email: robert.papesch at hp.com [cid:070264722 at 04032008-3494] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: tsg_email_signature_static.gif Type: image/gif Size: 5843 bytes Desc: tsg_email_signature_static.gif URL: From mmcgrath at redhat.com Wed Mar 5 03:25:48 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Tue, 4 Mar 2008 21:25:48 -0600 (CST) Subject: feedback on http://fedoraproject.org/en/get-fedora In-Reply-To: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> References: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> Message-ID: On Tue, 4 Mar 2008, Papesch, Robert wrote: > hi, > On the "Get Fedora" page I found the numerous options confusing. Why not add a link to this forum article? > > http://www.linuxforums.org/forum/linux-newbie/28214-rpm-differences-i386-i586-i686-x86_64-ppc-etc-etc.html > Ugh, this does bring up a good point, we had planned on re-designing this page but it looks like we missed the string freeze? Anyone interested in doing it like _right now_ and asking the translations team politely to translate it? -Mike From juankprada at gmail.com Wed Mar 5 03:56:48 2008 From: juankprada at gmail.com (Juan Camilo Prada) Date: Tue, 04 Mar 2008 22:56:48 -0500 Subject: feedback on http://fedoraproject.org/en/get-fedora In-Reply-To: References: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> Message-ID: <1204689408.8418.1.camel@juanky-laptop> On Tue, 2008-03-04 at 21:25 -0600, Mike McGrath wrote: > On Tue, 4 Mar 2008, Papesch, Robert wrote: > > > hi, > > On the "Get Fedora" page I found the numerous options confusing. Why not add a link to this forum article? > > > > http://www.linuxforums.org/forum/linux-newbie/28214-rpm-differences-i386-i586-i686-x86_64-ppc-etc-etc.html > > > > Ugh, this does bring up a good point, we had planned on re-designing this > page but it looks like we missed the string freeze? Anyone interested in > doing it like _right now_ and asking the translations team politely to > translate it? > > -Mike > If you want i could work on in tomorrow, although i would like to know what you people have planned for the re design so i can get as clos as possible to the desired design From kwade at redhat.com Wed Mar 5 06:06:46 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 04 Mar 2008 22:06:46 -0800 Subject: feedback on http://fedoraproject.org/en/get-fedora In-Reply-To: <1204689408.8418.1.camel@juanky-laptop> References: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> <1204689408.8418.1.camel@juanky-laptop> Message-ID: <1204697206.4141.81.camel@calliope.phig.org> On Tue, 2008-03-04 at 22:56 -0500, Juan Camilo Prada wrote: > On Tue, 2008-03-04 at 21:25 -0600, Mike McGrath wrote: > > On Tue, 4 Mar 2008, Papesch, Robert wrote: > > > > > hi, > > > On the "Get Fedora" page I found the numerous options confusing. Why not add a link to this forum article? > > > > > > http://www.linuxforums.org/forum/linux-newbie/28214-rpm-differences-i386-i586-i686-x86_64-ppc-etc-etc.html > > > > > > > Ugh, this does bring up a good point, we had planned on re-designing this > > page but it looks like we missed the string freeze? Anyone interested in > > doing it like _right now_ and asking the translations team politely to > > translate it? Docs has it's own string freeze schedule. The website is the same; we can do it more up to the last minute unlike translations of packages. Even giving 2 weeks for translation, we'd have up to mid-April to redesign the page. Right? - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Wed Mar 5 09:00:09 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 05 Mar 2008 14:30:09 +0530 Subject: feedback on http://fedoraproject.org/en/get-fedora In-Reply-To: <1204689408.8418.1.camel@juanky-laptop> References: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> <1204689408.8418.1.camel@juanky-laptop> Message-ID: <47CE6119.8080004@fedoraproject.org> Juan Camilo Prada wrote: >> > If you want i could work on in tomorrow, although i would like to know > what you people have planned for the re design so i can get as clos as > possible to the desired design Refer http://fedoraproject.org/wiki/PaulWFrields/NewGetFedora Rahul From jonathan.roberts.uk at googlemail.com Wed Mar 5 12:19:39 2008 From: jonathan.roberts.uk at googlemail.com (Jonathan Roberts) Date: Wed, 5 Mar 2008 12:19:39 +0000 Subject: Static Release Notes? Message-ID: <3263b11b0803050419k61d49150u7f410c18c71868c7@mail.gmail.com> Hi, With the alpha release we had trouble with availability of the wiki during the release, and it was said that people would prefer it if we could make the content static for release, so what's the process that we need to go through? Best wishes, Jon From mmcgrath at redhat.com Wed Mar 5 15:03:01 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Wed, 5 Mar 2008 09:03:01 -0600 (CST) Subject: feedback on http://fedoraproject.org/en/get-fedora In-Reply-To: <1204697206.4141.81.camel@calliope.phig.org> References: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> <1204689408.8418.1.camel@juanky-laptop> <1204697206.4141.81.camel@calliope.phig.org> Message-ID: On Tue, 4 Mar 2008, Karsten 'quaid' Wade wrote: > > On Tue, 2008-03-04 at 22:56 -0500, Juan Camilo Prada wrote: > > On Tue, 2008-03-04 at 21:25 -0600, Mike McGrath wrote: > > > On Tue, 4 Mar 2008, Papesch, Robert wrote: > > > > > > > hi, > > > > On the "Get Fedora" page I found the numerous options confusing. Why not add a link to this forum article? > > > > > > > > http://www.linuxforums.org/forum/linux-newbie/28214-rpm-differences-i386-i586-i686-x86_64-ppc-etc-etc.html > > > > > > > > > > Ugh, this does bring up a good point, we had planned on re-designing this > > > page but it looks like we missed the string freeze? Anyone interested in > > > doing it like _right now_ and asking the translations team politely to > > > translate it? > > Docs has it's own string freeze schedule. The website is the same; we > can do it more up to the last minute unlike translations of packages. > Even giving 2 weeks for translation, we'd have up to mid-April to > redesign the page. Right? > I didn't know that, this is the first time we've ever really kept our eyes on the string freeze with the website. Still, it'd probably be good to make sure we have a plan in mind. Anyone interested in heading this up? -Mike From stickster at gmail.com Wed Mar 5 15:29:30 2008 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 05 Mar 2008 10:29:30 -0500 Subject: RHM widget on fedoraproject.org In-Reply-To: References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> <1204568655.19210.4.camel@localhost.localdomain> <47CCCE16.6080003@fedoraproject.org> Message-ID: <1204730970.1552.72.camel@localhost.localdomain> Summary at bottom, keep reading -- On Mon, 2008-03-03 at 22:26 -0600, Mike McGrath wrote: > On Mon, 3 Mar 2008, M?ir?n Duffy wrote: > > Mike McGrath wrote: > > > We have a banner system already, I say lets use it. > > > > +1 > > > > If it's going to be that size, it should just go into banner rotation. Having > > two banners on the left side like that makes the left heavier than it was ever > > meant to be. > > > > Like Mike said, I think there are a lot of different visions for the site. So > > here's mine. :) I had always intended for there to be a larger main banner > > area in the middle, for promotion of Fedora-only things (much like the > > gnome.org main banner.) We didn't actually use such a design yet because of > > bandwidth restrictions at release times but we now do have the bandwidth to do > > this so I'm hoping we'll have banners of a larger size to promote > > Fedora-related content there soon. (example, mockup: > > http://i61.photobucket.com/albums/h58/mairinduffy/bigfedorabanner.png) > > > > I think the smaller banner space that we currently use now would likely be > > more appropriate for the RHM banner. > > > > Yeah, we've got a few different sites. I think that all of our 'sub' > project sites should have the smaller banner system while the fedora-main > site should be different or... I don't know, more grand but still simple? > I'm not sure how else to say it. > > The current fp.o/ site was initially designed to be simple and light on > the network, thats no longer the case so the fedoraproject.org/ site is > ripe for a re-design or re-visioning. Just going to take someone with the > time, guts and skill to do it. Its probably too late for the F9 release > as the string freeze is tomorrow :) But we can certainly re-think it > shortly after and get it in shape for F10. Jessica Gerber isn't on this mailing list, so I'm putting her on Cc: to keep her in the loop. Jess, it sounds like people will be happy to put your banners in rotation at the top of the page in the same bucket as the other ones. To whom can Jess send her banners for inclusion? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mmcgrath at redhat.com Wed Mar 5 15:30:53 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Wed, 5 Mar 2008 09:30:53 -0600 (CST) Subject: Announcing FAS2 Tests! Message-ID: Well, we've been working on it for a long time and even with a last minute core technology change FAS2 is ready for testing and almost ready for deployment. What is FAS2 you ask? Its the second iteration of the Fedora Accounts System. It's based off of TurboGears and has so many standards and future expandability I won't even go into that here. What I will say is that we'd like everyone to come test it before we deploy it in the next week or two. The test site is at: https://publictest10.fedoraproject.org/accounts/ This system is completely separate from the current running system so feel free to come in, setup a test account, or 2 or 10, and groups. If you'd like admin or sponsor access to a group just stop by #fedora-admin and ask for it and someone will set you up. What are features to look forward to in FAS2? * Online help system * Translations (the systems there but without translations currently) * JSON Interface * More comprehensive client for shell access * Easier to sign the CLA * OpenID interface (work in progress) * Much less developer-centeric interface To get your own local install going just run: yum install git-core git clone git://git.fedorahosted.org/git/fedora-infrastructure.git/ cd fedora-infrastructure.git/fas vi README If you have any bugs to report please send them to: https://fedorahosted.org/fas2/ We're also taking feature requests though they will likely not make it into the initial deployment. Happy hacking! From mzotyoka at gmail.com Wed Mar 5 15:48:01 2008 From: mzotyoka at gmail.com (=?UTF-8?Q?Magyar_Zolt=C3=A1n?=) Date: Wed, 5 Mar 2008 16:48:01 +0100 Subject: Announcing FAS2 Tests! In-Reply-To: References: Message-ID: <307f12af0803050748r7e409889hcb1581069e851b60@mail.gmail.com> Hi! After creating a new user and logging in, I get a 404 error page, with the following url: http://publictest10.fedoraproject.org/accounts/accounts/ 404 Not Found The path '/accounts/' was not found. Page handler: "The path '/accounts/' was not found." Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/cherrypy/_cphttptools.py", line 121, in _run self.main() File "/usr/lib/python2.4/site-packages/cherrypy/_cphttptools.py", line 256, in main page_handler, object_path, virtual_path = self.mapPathToObject(path) File "/usr/lib/python2.4/site-packages/cherrypy/_cphttptools.py", line 326, in mapPathToObject raise cherrypy.NotFound(objectpath) NotFound: 404 Looks like the second 'accounts/' is not needed, after deleting, it works fine, I'm logged in. Regards, Zoltan 2008/3/5, Mike McGrath : > > Well, we've been working on it for a long time and even with a last minute > core technology change FAS2 is ready for testing and almost ready for > deployment. What is FAS2 you ask? Its the second iteration of the Fedora > Accounts System. It's based off of TurboGears and has so many standards > and future expandability I won't even go into that here. What I will say > is that we'd like everyone to come test it before we deploy it in the next > week or two. > > The test site is at: https://publictest10.fedoraproject.org/accounts/ > > This system is completely separate from the current running system so feel > free to come in, setup a test account, or 2 or 10, and groups. If you'd > like admin or sponsor access to a group just stop by #fedora-admin and ask > for it and someone will set you up. What are features to look forward to > in FAS2? > > * Online help system > * Translations (the systems there but without translations currently) > * JSON Interface > * More comprehensive client for shell access > * Easier to sign the CLA > * OpenID interface (work in progress) > * Much less developer-centeric interface > > > To get your own local install going just run: > > yum install git-core > git clone git://git.fedorahosted.org/git/fedora-infrastructure.git/ > cd fedora-infrastructure.git/fas > vi README > > If you have any bugs to report please send them to: > https://fedorahosted.org/fas2/ > > We're also taking feature requests though they will likely not make it > into the initial deployment. Happy hacking! > > > -- > Fedora-websites-list mailing list > Fedora-websites-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-websites-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmcgrath at redhat.com Wed Mar 5 23:56:57 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Wed, 5 Mar 2008 17:56:57 -0600 (CST) Subject: RHM widget on fedoraproject.org In-Reply-To: <1204730970.1552.72.camel@localhost.localdomain> References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> <1204568655.19210.4.camel@localhost.localdomain> <47CCCE16.6080003@fedoraproject.org> <1204730970.1552.72.camel@localhost.localdomain> Message-ID: On Wed, 5 Mar 2008, Paul W. Frields wrote: > Summary at bottom, keep reading -- > > On Mon, 2008-03-03 at 22:26 -0600, Mike McGrath wrote: > > On Mon, 3 Mar 2008, M?ir?n Duffy wrote: > > > Mike McGrath wrote: > > > > We have a banner system already, I say lets use it. > > > > > > +1 > > > > > > If it's going to be that size, it should just go into banner rotation. Having > > > two banners on the left side like that makes the left heavier than it was ever > > > meant to be. > > > > > > Like Mike said, I think there are a lot of different visions for the site. So > > > here's mine. :) I had always intended for there to be a larger main banner > > > area in the middle, for promotion of Fedora-only things (much like the > > > gnome.org main banner.) We didn't actually use such a design yet because of > > > bandwidth restrictions at release times but we now do have the bandwidth to do > > > this so I'm hoping we'll have banners of a larger size to promote > > > Fedora-related content there soon. (example, mockup: > > > http://i61.photobucket.com/albums/h58/mairinduffy/bigfedorabanner.png) > > > > > > I think the smaller banner space that we currently use now would likely be > > > more appropriate for the RHM banner. > > > > > > > Yeah, we've got a few different sites. I think that all of our 'sub' > > project sites should have the smaller banner system while the fedora-main > > site should be different or... I don't know, more grand but still simple? > > I'm not sure how else to say it. > > > > The current fp.o/ site was initially designed to be simple and light on > > the network, thats no longer the case so the fedoraproject.org/ site is > > ripe for a re-design or re-visioning. Just going to take someone with the > > time, guts and skill to do it. Its probably too late for the F9 release > > as the string freeze is tomorrow :) But we can certainly re-think it > > shortly after and get it in shape for F10. > > Jessica Gerber isn't on this mailing list, so I'm putting her on Cc: to > keep her in the loop. Jess, it sounds like people will be happy to put > your banners in rotation at the top of the page in the same bucket as > the other ones. To whom can Jess send her banners for inclusion? she can send them to this list or webmaster at fedoraproject.org -Mike From mmcgrath at redhat.com Wed Mar 5 23:58:13 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Wed, 5 Mar 2008 17:58:13 -0600 (CST) Subject: Static Release Notes? In-Reply-To: <3263b11b0803050419k61d49150u7f410c18c71868c7@mail.gmail.com> References: <3263b11b0803050419k61d49150u7f410c18c71868c7@mail.gmail.com> Message-ID: On Wed, 5 Mar 2008, Jonathan Roberts wrote: > Hi, > > With the alpha release we had trouble with availability of the wiki > during the release, and it was said that people would prefer it if we > could make the content static for release, so what's the process that > we need to go through? > Basically just let someone in sysadmin-web know (or in #fedora-admin) know when its ok to static-fy the notes and we'll get them prepared. With some of the changes I've been making ot the wiki it'd be nice to have the static notes ready but stick with the wiki until we see problems. -Mike From stickster at gmail.com Fri Mar 7 13:35:42 2008 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 07 Mar 2008 13:35:42 +0000 Subject: CLA on Wiki Message-ID: <1204896942.4663.47.camel@localhost.localdomain> Assume that we have been given the blessing to use a one-click agreement to the CLA. No GPG required, no cumbersome signing process. Fill in your personal info and click to indicate you've read and agree to the CLA, and create a Fedora account. Now consider our wiki Edit screen. Assume that Legal really wants us to have CLA agreement for anyone editing the wiki. We want that process to be as low-drag as possible. So imagine this: If the user hits Submit, and is not logged in, request the login, along with a "Create an Account (30 seconds)" link. The link either goes to a new page, or pops up a little JavaScripty, Web2.0-y box that collects the minimum info needed for FAS2. A link is included to the CLA and an agreement button. The agreement and link appear *above* the button: "I have read and agree to the terms of the [Fedora Contributor License Agreement]. [I agree]" Upon creation of the account, the user is returned to their edit without losing his work, and can then submit it: "By pressing 'Submit', you agree to the terms of the [WikiLicense]. [Submit] [Cancel]" Seeing as how basically everyone does it -- how hard is this in Moin? In MediaWiki? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Fri Mar 7 14:02:29 2008 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 07 Mar 2008 14:02:29 +0000 Subject: feedback on http://fedoraproject.org/en/get-fedora In-Reply-To: <47CE6119.8080004@fedoraproject.org> References: <29F4A5FA1B21DB43837FAD15C795A01AB86AE3BFEE@G1W0480.americas.hpqcorp.net> <1204689408.8418.1.camel@juanky-laptop> <47CE6119.8080004@fedoraproject.org> Message-ID: <1204898549.4663.66.camel@localhost.localdomain> On Wed, 2008-03-05 at 14:30 +0530, Rahul Sundaram wrote: > Juan Camilo Prada wrote: > > >> > > If you want i could work on in tomorrow, although i would like to know > > what you people have planned for the re design so i can get as clos as > > possible to the desired design > > Refer > > http://fedoraproject.org/wiki/PaulWFrields/NewGetFedora Right, I started working on that shortly after FUDCon IIRC but got sidetracked (go figure). It may need a few more decision points and answers without getting too bogged down. (For instance, someone who's running an IBM zSeries probably knows their architecture... do we really need to include that on the list?) The general idea, as I explained to Toshio and some others at FUDCon, is to make the design follow these constraints: 0. Allow experts to bail into a typical technobabble list of choices. Don't bog them down. 1. For everyone else, follow a "choose your own adventure" workflow. 2. Avoid all jargon and present questions anyone can answer. 3. The choices should continue to use the same screen real estate. Do not link to new pages if possible, just use JavaScript or something similar to reuse the same part of the page for additional questions. 4. Help on BitTorrent should include links for Windows, Mac, and Linux to the simplest effective BT software in a way that doesn't navigate users away from the Get Fedora site. 5. Ask for a user's spin preference. The top choice is "I'm not sure, choose for me," which results in the default Desktop Live or Install image. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Hood.Stephen at orbital.com Thu Mar 6 15:01:22 2008 From: Hood.Stephen at orbital.com (Stephen Hood) Date: Thu, 6 Mar 2008 10:01:22 -0500 Subject: phishing Message-ID: http://mail.vejthani.com/.cgi-bin/update/security/security/update/www.bankofamerica.us.com/ ----------------------------------------- Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged and exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. This communication may also contain data subject to U.S. export laws. If so, that data subject to the International Traffic in Arms Regulation cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, absent the express prior approval of the U.S. Department of State. If you have received this communication in error, please notify the sender by reply e-mail and destroy the e-mail message and any physical copies made of the communication. Thank you. From hvg at etk.pte.hu Fri Mar 7 09:12:17 2008 From: hvg at etk.pte.hu (HvG) Date: Fri, 07 Mar 2008 10:12:17 +0100 Subject: Problem_with_Fedora_setup_please_help! Message-ID: <47D106F1.4090807@etk.pte.hu> Dear Sir, excuse me for bothering you, but I haven't found another E-Mail address for help me. I've downloaded the BitTorrent file for Fedora install DVD from this URL: http://fedoraproject.org/en/get-fedora followed by downloading of install ISO files. After that I've made setup DVD using Nero. The boot from the DVD is OK and the setup program starts normally. After few installation step (choosing language: English, keyboard: hu101) the setup program aborted with this error message: The Fedora disc was not found in any of your CDROM drives. Please insert the Fedora disc and press OK to retry. and the DVD-reader ejects the disc. It is peculiar because in my opinion the disc is OK (after the writing Nero has verified the result) - and I've made another copy of disc and with this second disc the result is same. The parameters of computer: CPU: Intel Celeron 2.40 GHz RAM: 256 MB VGA: Intel 82845G, integrated DVD: _NEC DVD_RW ND-4571A HDD: HDS722580VLAT20 (approx. 80 GB) Please help me and say what was wrong! Thank you for your help! Yours sincerely, Gabor Horvath From gospo at redhat.com Fri Mar 7 20:39:01 2008 From: gospo at redhat.com (Andy Gospodarek) Date: Fri, 7 Mar 2008 15:39:01 -0500 Subject: start.fedoraproject.org search results Message-ID: <20080307203901.GM24495@gospo.usersys.redhat.com> Is fedora getting paid by google for any advertisements they click after searching from start.fedoraproject.org? If not, I'm willing to look into getting that setup. Thanks, -andy From ricky at fedoraproject.org Fri Mar 7 21:00:58 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 7 Mar 2008 16:00:58 -0500 Subject: phishing In-Reply-To: References: Message-ID: <20080307210058.GT16254@Max.nyc1.dsl.speakeasy.net> On 2008-03-06 10:01:22 AM, Stephen Hood wrote: > http://mail.vejthani.com/.cgi-bin/update/security/security/update/www.bankofamerica.us.com/ I assume that you're referring to the page at http://mail.vejthani.com/. That is a test page included with our operating system; we don't actually control the site in question. For more information, please refer to http://fedoraproject.org/wiki/ServerTestPage Try contacting the owner of the site. You should be able to find contact information by doing a WHOIS lookup. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ricky at fedoraproject.org Fri Mar 7 21:02:08 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 7 Mar 2008 16:02:08 -0500 Subject: Problem_with_Fedora_setup_please_help! In-Reply-To: <47D106F1.4090807@etk.pte.hu> References: <47D106F1.4090807@etk.pte.hu> Message-ID: <20080307210208.GU16254@Max.nyc1.dsl.speakeasy.net> On 2008-03-07 10:12:17 AM, HvG wrote: > I've downloaded the BitTorrent file for Fedora install DVD from this URL: > > http://fedoraproject.org/en/get-fedora > > followed by downloading of install ISO files. After that I've made setup > DVD using Nero. The boot from the DVD is OK and the setup program starts > normally. After few installation step (choosing language: English, > keyboard: hu101) the setup program aborted with this error message: > > The Fedora disc was not found in any of your CDROM drives. Please insert > the Fedora disc and press OK to retry. > > and the DVD-reader ejects the disc. > > It is peculiar because in my opinion the disc is OK (after the writing > Nero has verified the result) - and I've made another copy of disc and > with this second disc the result is same. > > The parameters of computer: > CPU: Intel Celeron 2.40 GHz > RAM: 256 MB > VGA: Intel 82845G, integrated > DVD: _NEC DVD_RW ND-4571A > HDD: HDS722580VLAT20 (approx. 80 GB) > > Please help me and say what was wrong! > Thank you for your help! The webmaster at fedoraproject.org address is only for issues related to Fedora's websites. For general Fedora support, please refer to the help resources described at http://fedoraproject.org/wiki/Communicate. Specifically, fedora-list (http://www.redhat.com/mailman/listinfo/fedora-list) might be a good place to ask. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mmcgrath at redhat.com Fri Mar 7 21:06:40 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Fri, 7 Mar 2008 15:06:40 -0600 (CST) Subject: start.fedoraproject.org search results In-Reply-To: <20080307203901.GM24495@gospo.usersys.redhat.com> References: <20080307203901.GM24495@gospo.usersys.redhat.com> Message-ID: On Fri, 7 Mar 2008, Andy Gospodarek wrote: > > Is fedora getting paid by google for any advertisements they click after > searching from start.fedoraproject.org? If not, I'm willing to look > into getting that setup. > We aren't currently though I believe there may be some voodoo in the mix and that GDK knows the latest. -Mike From gospo at redhat.com Fri Mar 7 21:17:52 2008 From: gospo at redhat.com (Andy Gospodarek) Date: Fri, 7 Mar 2008 16:17:52 -0500 Subject: start.fedoraproject.org search results In-Reply-To: References: <20080307203901.GM24495@gospo.usersys.redhat.com> Message-ID: <20080307211752.GN24495@gospo.usersys.redhat.com> On Fri, Mar 07, 2008 at 03:06:40PM -0600, Mike McGrath wrote: > On Fri, 7 Mar 2008, Andy Gospodarek wrote: > > > > > Is fedora getting paid by google for any advertisements they click after > > searching from start.fedoraproject.org? If not, I'm willing to look > > into getting that setup. > > > > We aren't currently though I believe there may be some voodoo in the mix > and that GDK knows the latest. > > -Mike Sweet. Greg, if that's not the case let me know and I can try and follow up with Google (though I know you've got some contacts over there so you might know better where to start). From kwade at redhat.com Fri Mar 7 21:36:45 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Fri, 07 Mar 2008 13:36:45 -0800 Subject: start.fedoraproject.org search results In-Reply-To: <20080307211752.GN24495@gospo.usersys.redhat.com> References: <20080307203901.GM24495@gospo.usersys.redhat.com> <20080307211752.GN24495@gospo.usersys.redhat.com> Message-ID: <1204925805.18757.8.camel@calliope.phig.org> On Fri, 2008-03-07 at 16:17 -0500, Andy Gospodarek wrote: > On Fri, Mar 07, 2008 at 03:06:40PM -0600, Mike McGrath wrote: > > On Fri, 7 Mar 2008, Andy Gospodarek wrote: > > > > > > > > Is fedora getting paid by google for any advertisements they click after > > > searching from start.fedoraproject.org? If not, I'm willing to look > > > into getting that setup. > > > > > > > We aren't currently though I believe there may be some voodoo in the mix > > and that GDK knows the latest. > > > > -Mike > > Sweet. Greg, if that's not the case let me know and I can try and > follow up with Google (though I know you've got some contacts over there > so you might know better where to start). Greg is definitely pretty deep into this situation. It's still in the research-and-Board-decision stage, and when it comes out from there you'll see some sort of change, maybe an announcement. Greg -- if you need another soldja to help the cause, you know where to find Andy. - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mostafa at daneshvar.org.uk Sat Mar 8 17:07:27 2008 From: mostafa at daneshvar.org.uk (Mostafa Daneshvar) Date: Sat, 8 Mar 2008 20:37:27 +0330 Subject: Problem in TX Message-ID: <200803082037.27976.mostafa@daneshvar.org.uk> I have some problem in using Tx interface. I always deal with proxy Error(502) problem. Do you have any idea to solve the problem? -- Mostafa Daneshvar From stickster at gmail.com Sat Mar 8 19:29:14 2008 From: stickster at gmail.com (Paul W. Frields) Date: Sat, 08 Mar 2008 19:29:14 +0000 Subject: CLA on Wiki In-Reply-To: <1204896942.4663.47.camel@localhost.localdomain> References: <1204896942.4663.47.camel@localhost.localdomain> Message-ID: <1205004554.30874.13.camel@localhost.localdomain> On Fri, 2008-03-07 at 13:35 +0000, Paul W. Frields wrote: > Assume that we have been given the blessing to use a one-click agreement > to the CLA. No GPG required, no cumbersome signing process. Fill in > your personal info and click to indicate you've read and agree to the > CLA, and create a Fedora account. > > Now consider our wiki Edit screen. Assume that Legal really wants us to > have CLA agreement for anyone editing the wiki. We want that process to > be as low-drag as possible. So imagine this: > > If the user hits Submit, and is not logged in, request the login, along > with a "Create an Account (30 seconds)" link. > > The link either goes to a new page, or pops up a little JavaScripty, > Web2.0-y box that collects the minimum info needed for FAS2. A link is > included to the CLA and an agreement button. The agreement and link > appear *above* the button: > > "I have read and agree to the terms of the > [Fedora Contributor License Agreement]. > [I agree]" > > Upon creation of the account, the user is returned to their edit without > losing his work, and can then submit it: > > "By pressing 'Submit', you agree to the > terms of the [WikiLicense]. > [Submit] [Cancel]" > > Seeing as how basically everyone does it -- how hard is this in Moin? > In MediaWiki? I'm going to put this in as a ticket, if that's preferable. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mmcgrath at redhat.com Sat Mar 8 20:52:01 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Sat, 8 Mar 2008 14:52:01 -0600 (CST) Subject: Problem in TX In-Reply-To: <200803082037.27976.mostafa@daneshvar.org.uk> References: <200803082037.27976.mostafa@daneshvar.org.uk> Message-ID: On Sat, 8 Mar 2008, Mostafa Daneshvar wrote: > I have some problem in using Tx interface. I always deal with proxy Error(502) > problem. Do you have any idea to solve the problem? > See if this is working now, if it is not please by #fedora-admin on irc.freenode.net and help me troubleshoot it. -Mike From mmcgrath at redhat.com Sat Mar 8 21:00:23 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Sat, 8 Mar 2008 15:00:23 -0600 (CST) Subject: CLA on Wiki In-Reply-To: <1205004554.30874.13.camel@localhost.localdomain> References: <1204896942.4663.47.camel@localhost.localdomain> <1205004554.30874.13.camel@localhost.localdomain> Message-ID: On Sat, 8 Mar 2008, Paul W. Frields wrote: > On Fri, 2008-03-07 at 13:35 +0000, Paul W. Frields wrote: > > Assume that we have been given the blessing to use a one-click agreement > > to the CLA. No GPG required, no cumbersome signing process. Fill in > > your personal info and click to indicate you've read and agree to the > > CLA, and create a Fedora account. > > > > Now consider our wiki Edit screen. Assume that Legal really wants us to > > have CLA agreement for anyone editing the wiki. We want that process to > > be as low-drag as possible. So imagine this: > > > > If the user hits Submit, and is not logged in, request the login, along > > with a "Create an Account (30 seconds)" link. > > > > The link either goes to a new page, or pops up a little JavaScripty, > > Web2.0-y box that collects the minimum info needed for FAS2. A link is > > included to the CLA and an agreement button. The agreement and link > > appear *above* the button: > > > > "I have read and agree to the terms of the > > [Fedora Contributor License Agreement]. > > [I agree]" > > > > Upon creation of the account, the user is returned to their edit without > > losing his work, and can then submit it: > > > > "By pressing 'Submit', you agree to the > > terms of the [WikiLicense]. > > [Submit] [Cancel]" > > > > Seeing as how basically everyone does it -- how hard is this in Moin? > > In MediaWiki? > > I'm going to put this in as a ticket, if that's preferable. > Thats probably not a bad idea, it'd allow us to track it better. I don't think the above is too difficult to do at all actually, especially since I suspect a huge push for the new wiki in the next month or two. -Mike From kwade at redhat.com Mon Mar 10 18:16:10 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 10 Mar 2008 11:16:10 -0700 Subject: string freeze for web sites (was Re: RHM widget on fedoraproject.org) In-Reply-To: References: <47CB5081.3080306@redhat.com> <1204555312.16292.3.camel@localhost.localdomain> <1204568655.19210.4.camel@localhost.localdomain> <47CCCE16.6080003@fedoraproject.org> Message-ID: <1205172970.1101.105.camel@calliope.phig.org> On Mon, 2008-03-03 at 22:26 -0600, Mike McGrath wrote: > Its probably too late for the F9 release > as the string freeze is tomorrow :) Just wanted to note that the websites do not (nor should not) follow the code development freeze. At a minimum, I'd recommend something like the Fedora Docs schedule[1], which has the Preview Release string freeze effectively 17 March, 07 April for l10n that goes into the ISO, and 17 April for final that appears on the web/zero-day updates. Because web pages are instant publishing, our main blockers are: * Giving l10n enough time * Trying not to jam too much into the schedule at the same time For example, when everyone is busy finishing the software for the ISO, that is the time to hold off on pushing out POT updates for web-based content. Based on that, maybe something in between 07 and 17 April, such as 11 April would be a good string freeze for *all* websites, giving nearly three weeks for translation, QA, etc.? Another option is to go as late as possible, with 21 April being the absolute latest. The rule of thumb we've got from L10n in the past is, "10 days minimum, 14 days is best." - Karsten [1] http://fedoraproject.org/wiki/DocsProject/Schedule/9 -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Mon Mar 10 18:29:46 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 10 Mar 2008 11:29:46 -0700 Subject: Omniture & Fedora In-Reply-To: <47C89B81.1070309@gmail.com> References: <47C7213C.40407@redhat.com> <20080229095711.54ebd4c8@j2solutions.net> <47C82FD1.1070801@redhat.com> <47C8415C.7050002@redhat.com> <47C89B81.1070309@gmail.com> Message-ID: <1205173786.1101.115.camel@calliope.phig.org> On Fri, 2008-02-29 at 15:55 -0800, Toshio Kuratomi wrote: > Do the pieces of software (the javascript on the > client in this case) have an open source license? Sorry to arrive late to this discussion. The Omniture JS code used to be on fedora.redhat.com, and it was docs.fedoraproject.org for a while. Mike McGrath (iirc) and I were discussing its existence one day when we noticed docs.fp.o was loading slowly due to the Omniture calls. So, that was one mark against the service in general -- it presented another point of failure on release days, which are ironically the days we'd want the most traffic analysis for. The reason I decided to yank the code is clear -- it is not-FLOSS and we have no rights to use or distribute it as part of Fedora Project web properties. Here is a sample of the Omniture JS from redhatmagazine.com:
    The code only has a copyright notice and no FLOSS license. As Toshio states later in this email, that is the #1 blocker. I consider the "added point of failure" #2, because of historical problems with Omniture that I'm not convinced are just history. So Jesse -- if you can find out if Omniture can or will license that code under an OSI approved license, then we'll actually have something to discuss. Otherwise, it is a ForbiddenItem. - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jeversol at redhat.com Tue Mar 11 12:29:01 2008 From: jeversol at redhat.com (Jesse Eversole Jr) Date: Tue, 11 Mar 2008 08:29:01 -0400 Subject: Omniture & Fedora In-Reply-To: <1205173786.1101.115.camel@calliope.phig.org> References: <47C7213C.40407@redhat.com> <20080229095711.54ebd4c8@j2solutions.net> <47C82FD1.1070801@redhat.com> <47C8415C.7050002@redhat.com> <47C89B81.1070309@gmail.com> <1205173786.1101.115.camel@calliope.phig.org> Message-ID: <47D67B0D.7070205@redhat.com> Karsten, This is new territory for me and reminds me of the days when I used to deal with "fair use" in the digital capture and copying of material submitted by faculty to the library reserve desk. My approach on issues like this is to just put the question to Omniture and see what they say. I do know that they have a rather large piece of javascript embedded in a function call that does all the heavy lifting of logic when it comes to marking up the image call to their backend servers. I have no idea what it means to have a FLOSS license on a piece of javascript that sends marked up query strings to an opaque service handler. Even if the javascript were released under a FLOSS license it would not be usable without a contract with Omniture to enable a network service to talk with it. Right now I don't see compatibility. You might want to mention something to the awstats community about adding client side tracking to the software might be something of interest to the community. Karsten 'quaid' Wade wrote: > On Fri, 2008-02-29 at 15:55 -0800, Toshio Kuratomi wrote: > > >> Do the pieces of software (the javascript on the >> client in this case) have an open source license? >> > > Sorry to arrive late to this discussion. > > The Omniture JS code used to be on fedora.redhat.com, and it was > docs.fedoraproject.org for a while. Mike McGrath (iirc) and I were > discussing its existence one day when we noticed docs.fp.o was loading > slowly due to the Omniture calls. So, that was one mark against the > service in general -- it presented another point of failure on release > days, which are ironically the days we'd want the most traffic analysis > for. > > The reason I decided to yank the code is clear -- it is not-FLOSS and we > have no rights to use or distribute it as part of Fedora Project web > properties. > > Here is a sample of the Omniture JS from redhatmagazine.com: > > >
    > > > > >
    > > > The code only has a copyright notice and no FLOSS license. > > As Toshio states later in this email, that is the #1 blocker. I > consider the "added point of failure" #2, because of historical problems > with Omniture that I'm not convinced are just history. > > So Jesse -- if you can find out if Omniture can or will license that > code under an OSI approved license, then we'll actually have something > to discuss. Otherwise, it is a ForbiddenItem. > > - Karsten > From kwade at redhat.com Tue Mar 11 16:25:19 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 11 Mar 2008 09:25:19 -0700 Subject: Omniture & Fedora In-Reply-To: <47D67B0D.7070205@redhat.com> References: <47C7213C.40407@redhat.com> <20080229095711.54ebd4c8@j2solutions.net> <47C82FD1.1070801@redhat.com> <47C8415C.7050002@redhat.com> <47C89B81.1070309@gmail.com> <1205173786.1101.115.camel@calliope.phig.org> <47D67B0D.7070205@redhat.com> Message-ID: <1205252719.1101.207.camel@calliope.phig.org> On Tue, 2008-03-11 at 08:29 -0400, Jesse Eversole Jr wrote: > Karsten, > > This is new territory for me and reminds me of the days when I used to > deal with "fair use" in the digital capture and copying of material > submitted by faculty to the library reserve desk. My approach on issues > like this is to just put the question to Omniture and see what they > say. Exactly, that would clear things up. > I do know that they have a rather large piece of javascript > embedded in a function call that does all the heavy lifting of logic > when it comes to marking up the image call to their backend servers. I > have no idea what it means to have a FLOSS license on a piece of > javascript that sends marked up query strings to an opaque service > handler. I think it's analogous to the GPL'd kernel modules that talk with not-in-the-kernel binary-only drivers. There are other examples. It's not anyone's favorite way of doing things, but it is at least technically legal, if not entirely ethical. > Even if the javascript were released under a FLOSS license it > would not be usable without a contract with Omniture to enable a network > service to talk with it. Right, it would be a licensing to allow compatibility of use, not really to create a community around it. They can dual-license it, btw, being the sole owner of the copyright, and have a wide range of licenses to choose from. One catch may be where the JS is actually subtly different for each client of Omniture. Bottom line -- I seriously doubt Omniture will consider this idea just for Red Hat, unless they have other clients who are asking for it. But if you do ask and they say yes, we'll be glad to seriously consider the idea. > Right now I don't see compatibility. You > might want to mention something to the awstats community about adding > client side tracking to the software might be something of interest > to > the community. Any chance that Red Hat is interested in furthering the quality of free and open stats tracking? Maybe help grow a solution that is better than the for-pay, non-free options? - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mrector at verizon.net Wed Mar 12 16:29:25 2008 From: mrector at verizon.net (Mike Rector) Date: Wed, 12 Mar 2008 08:29:25 -0800 Subject: Spam Message-ID: Why am I getting spam from your IP address? 128.168.121.45 How can we stop these people? Mike Rector From ricky at fedoraproject.org Wed Mar 12 15:43:35 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Wed, 12 Mar 2008 11:43:35 -0400 Subject: Spam In-Reply-To: References: Message-ID: <20080312154335.GD5429@Max.nyc1.dsl.speakeasy.net> On 2008-03-12 08:29:25 AM, Mike Rector wrote: > Why am I getting spam from your IP address? > > 128.168.121.45 That is a test page included with our operating system; we don't actually control the site in question. Please refer to http://fedoraproject.org/wiki/ServerTestPage To bring this to the right people, you might want to do a WHOIS lookup on the IP address and contact the ISP's abuse address. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Thu Mar 13 19:34:26 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 13 Mar 2008 12:34:26 -0700 Subject: feeds mock-up for front page Message-ID: <1205436866.31045.173.camel@calliope.phig.org> Recently I took the task of getting a few feeds hosted on the front page of fedoraproject.org. To do that I opened a ticket[1], learned that the code is available to do this, and here are mock-ups of what that could look like: http://quaid.fedorapeople.org/websites/front-page-feed-mock-up/mock-up-fp.o-with-feeds.png http://quaid.fedorapeople.org/websites/front-page-feed-mock-up/fedoraproject.org.html ^-- (actual updated content and CSS in use above) The design is a bit of a strawman, in that it is there for you to spring other ideas from and don't worry about tearing it down; I see problems with it but I'm not going to tweak it any further at this point. I was originally thinking of stacking the feeds in a side bar, but I figured we could sneak it in and lose 60% of the 120 pixels of whitespace from the bottom of the #content area and not squeeze the page horizontally. Any objection to the idea of putting some feeds that are specifically useful to Fedorans on the fedoraproject.org front page? What do you think about adding these to start.fedoraproject.org? Any ideas about how to address this for translations? In the ticket[1] I suggest: > My only concern would be how that will work with non-English > translations. That's a good question. I know Red Hat Magazine experimented with the Google auto-translation links Wordpress plugin, and it didn't go over so well. Having this content in English on translated pages ... is that rude? Or better than nothing? What I'd like to try is this: 1. Come up with a stacked design so we can have separate feeds reading in rather than jamming them all into one 2. Put up the RSS feed pull code and start displaying the feeds as-is Thanks - Karsten [1] https://fedorahosted.org/fedora-infrastructure/ticket/357 -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From juankprada at gmail.com Thu Mar 13 21:39:15 2008 From: juankprada at gmail.com (Juan Camilo Prada Ojeda) Date: Thu, 13 Mar 2008 16:39:15 -0500 Subject: feeds mock-up for front page In-Reply-To: <1205436866.31045.173.camel@calliope.phig.org> References: <1205436866.31045.173.camel@calliope.phig.org> Message-ID: 2008/3/13, Karsten 'quaid' Wade : > > Recently I took the task of getting a few feeds hosted on the front page > of fedoraproject.org. To do that I opened a ticket[1], learned that the > code is available to do this, and here are mock-ups of what that could > look like: > > > http://quaid.fedorapeople.org/websites/front-page-feed-mock-up/mock-up-fp.o-with-feeds.png > > http://quaid.fedorapeople.org/websites/front-page-feed-mock-up/fedoraproject.org.html > ^-- (actual updated content and CSS in use above) > > The design is a bit of a strawman, in that it is there for you to spring > other ideas from and don't worry about tearing it down; I see problems > with it but I'm not going to tweak it any further at this point. I was > originally thinking of stacking the feeds in a side bar, but I figured > we could sneak it in and lose 60% of the 120 pixels of whitespace from > the bottom of the #content area and not squeeze the page horizontally. > > Any objection to the idea of putting some feeds that are specifically > useful to Fedorans on the fedoraproject.org front page? > > What do you think about adding these to start.fedoraproject.org? > I like the design and it would fit perfectly with the probably new ideas for fp.o. Also i did a mockup some time ago with only one single column having all the feed news. If you are interested you can check the code (i uploaded the whole website but havent built it so you should download it and build it yourself, sorry about that) -> http://jprada.fedorapeople.org/fedora-web/fedoraproject.org/ this is how it looks -> http://farm3.static.flickr.com/2357/2251189805_ae158b7fd0_o.png the script is functional and parses the latest news from the given feeds and it order them by its parse time BTW, i think we had discussed this things a few times with ricky, and we agreed that changes to the site would be better to do them after having a meeting to get the team know about changes and having people involved in the process, although ive never heard of the meeting and im still waiting -------------- next part -------------- An HTML attachment was scrubbed... URL: From kwade at redhat.com Thu Mar 13 23:44:17 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 13 Mar 2008 16:44:17 -0700 Subject: feeds mock-up for front page In-Reply-To: References: <1205436866.31045.173.camel@calliope.phig.org> Message-ID: <1205451857.13919.20.camel@calliope.phig.org> On Thu, 2008-03-13 at 16:39 -0500, Juan Camilo Prada Ojeda wrote: > > > I like the design and it would fit perfectly with the probably new > ideas for fp.o. > > Also i did a mockup some time ago with only one single column having > all the feed news. If you are interested you can check the code (i > uploaded the whole website but havent built it so you should download > it and build it yourself, sorry about that) -> > http://jprada.fedorapeople.org/fedora-web/fedoraproject.org/ > > this is how it looks -> > http://farm3.static.flickr.com/2357/2251189805_ae158b7fd0_o.png Right! That's the other way I was thinking, breaking out a third column. I'm not entirely done thinking about it, but I think I prefer the two-column with the feeds down the page a bit. I know it doesn't highlight them the same way, though. Maybe we can try out some variations on how the third column is done, such as pushing it down so the first item is on the same level as About Fedora? I'll see if I can get some time. I would be inclined to watch click-through statistics on that page for a while, see what people are interested in, and focus on making that part easiest to get to. Not sure if we can track that though, so it becomes our best guess choice. How about we give ourselves ~7 days to discuss and iterate on some designs and then put up the best one? > the script is functional and parses the latest news from the given > feeds and it order them by its parse time Also not sure about this, but I wanted to find a way to identify the source of the feed. Maybe an icon on the side instead of breaking them out into separate little columns like I did? The feed would look a bit like a Mugshot stacker that way: http://phig.members.sonic.net/screenshots/mugshot-stacker-example.png I could probably make that work in your copy; is that updated against the current content in the websites repository? > BTW, i think we had discussed this things a few times with ricky, and > we agreed that changes to the site would be better to do them after > having a meeting to get the team know about changes and having people > involved in the process, although ive never heard of the meeting and > im still waiting I think we can work these things out on list. But I'm not exactly sure which pieces you both mean. Change management? Process for approving and implementing ideas? Maybe we want to continue with the lightest possible process for now, then move toward what Infrastructure does? Are we worried about chaos? There is a risk that we'll end up with sites designed by committees, but that risk is always there. :) Meanwhile, we can surely identify some of our top priorities and make them happen. Since this one is a priority for me, I'm making it happen as I can. :) - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From juankprada at gmail.com Fri Mar 14 01:45:35 2008 From: juankprada at gmail.com (Juan Camilo Prada Ojeda) Date: Thu, 13 Mar 2008 20:45:35 -0500 Subject: feeds mock-up for front page In-Reply-To: <1205451857.13919.20.camel@calliope.phig.org> References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> Message-ID: 2008/3/13, Karsten 'quaid' Wade : > > > On Thu, 2008-03-13 at 16:39 -0500, Juan Camilo Prada Ojeda wrote: > > > > > > > I like the design and it would fit perfectly with the probably new > > ideas for fp.o. > > > > Also i did a mockup some time ago with only one single column having > > all the feed news. If you are interested you can check the code (i > > uploaded the whole website but havent built it so you should download > > it and build it yourself, sorry about that) -> > > http://jprada.fedorapeople.org/fedora-web/fedoraproject.org/ > > > > this is how it looks -> > > http://farm3.static.flickr.com/2357/2251189805_ae158b7fd0_o.png > > > Right! That's the other way I was thinking, breaking out a third > column. I'm not entirely done thinking about it, but I think I prefer > the two-column with the feeds down the page a bit. I know it doesn't > highlight them the same way, though. Maybe we can try out some > variations on how the third column is done, such as pushing it down so > the first item is on the same level as About Fedora? I'll see if I can > get some time. > > I would be inclined to watch click-through statistics on that page for a > while, see what people are interested in, and focus on making that part > easiest to get to. Not sure if we can track that though, so it becomes > our best guess choice. > > How about we give ourselves ~7 days to discuss and iterate on some > designs and then put up the best one? > > > > the script is functional and parses the latest news from the given > > feeds and it order them by its parse time > > > Also not sure about this, but I wanted to find a way to identify the > source of the feed. Maybe an icon on the side instead of breaking them > out into separate little columns like I did? The feed would look a bit > like a Mugshot stacker that way: > > http://phig.members.sonic.net/screenshots/mugshot-stacker-example.png > > I could probably make that work in your copy; is that updated against > the current content in the websites repository? > > > > BTW, i think we had discussed this things a few times with ricky, and > > we agreed that changes to the site would be better to do them after > > having a meeting to get the team know about changes and having people > > involved in the process, although ive never heard of the meeting and > > im still waiting > > > I think we can work these things out on list. But I'm not exactly sure > which pieces you both mean. Change management? Process for approving > and implementing ideas? > > Maybe we want to continue with the lightest possible process for now, > then move toward what Infrastructure does? > > Are we worried about chaos? There is a risk that we'll end up with > sites designed by committees, but that risk is always there. :) > > Meanwhile, we can surely identify some of our top priorities and make > them happen. Since this one is a priority for me, I'm making it happen > as I can. :) > > > - Karsten There is also this thing that keeps bugging me, and its the fact that there are so many official fedora related websites and all of them have a completly different design, it was already discussed tho but nothing have been done... so... a few days ago FAS2 was released with a completely new design. I would suggest starting to make new changes to the websites (not just fp.o) that matches the same design style that FAS2 has although i understand things cant look the same... at least it would be good that the look and feel of all related to fedora seems to be done by A comunity instead of independent random groups -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricky at fedoraproject.org Fri Mar 14 01:53:04 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 13 Mar 2008 21:53:04 -0400 Subject: feeds mock-up for front page In-Reply-To: References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> Message-ID: <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> On 2008-03-13 08:45:35 PM, Juan Camilo Prada Ojeda wrote: > There is also this thing that keeps bugging me, and its the fact that there > are so many > official fedora related websites and all of them have a completly different > design, it was already discussed tho > but nothing have been done... so... a few days ago FAS2 was released with a > completely new design. > I would suggest starting to make new changes to the websites (not just fp.o) > that matches the same design style that > FAS2 has although i understand things cant look the same... at least it > would be good that the look and feel of all related > to fedora seems to be done by A comunity instead of independent random > groups This one is probably my fault (and I agree completely)- the FAS2 design predates the fp.o design by a bit, if I remember correctly, and we never got a good chance to update the design before launching. We'll definitely be taking a much closer look at FAS2's UI/design once we get a few other issues worked out. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From duffy at fedoraproject.org Fri Mar 14 02:00:47 2008 From: duffy at fedoraproject.org (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Thu, 13 Mar 2008 22:00:47 -0400 Subject: feeds mock-up for front page In-Reply-To: <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> Message-ID: <47D9DC4F.7070309@fedoraproject.org> Ricky Zhou wrote: > On 2008-03-13 08:45:35 PM, Juan Camilo Prada Ojeda wrote: >> There is also this thing that keeps bugging me, and its the fact that there >> are so many >> official fedora related websites and all of them have a completly different >> design, it was already discussed tho >> but nothing have been done... so... a few days ago FAS2 was released with a >> completely new design. >> I would suggest starting to make new changes to the websites (not just fp.o) >> that matches the same design style that >> FAS2 has although i understand things cant look the same... at least it >> would be good that the look and feel of all related >> to fedora seems to be done by A comunity instead of independent random >> groups > This one is probably my fault (and I agree completely)- the FAS2 design > predates the fp.o design by a bit, if I remember correctly, and we never > got a good chance to update the design before launching. Yeh, that's pretty much what happened. The mockups for FAS2 were done before the FPO ones. I think the FPO template is really what we want to start moving forward on across sites. ~m From mmcgrath at redhat.com Fri Mar 14 03:06:45 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Thu, 13 Mar 2008 22:06:45 -0500 (CDT) Subject: feeds mock-up for front page In-Reply-To: <47D9DC4F.7070309@fedoraproject.org> References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> Message-ID: On Thu, 13 Mar 2008, M?ir?n Duffy wrote: > Ricky Zhou wrote: > > On 2008-03-13 08:45:35 PM, Juan Camilo Prada Ojeda wrote: > > > would be good that the look and feel of all related > > > to fedora seems to be done by A comunity instead of independent random > > > groups > > This one is probably my fault (and I agree completely)- the FAS2 design > > predates the fp.o design by a bit, if I remember correctly, and we never > > got a good chance to update the design before launching. > > Yeh, that's pretty much what happened. The mockups for FAS2 were done before > the FPO ones. I think the FPO template is really what we want to start moving > forward on across sites. > Just to make something clear to those on the lists. We all want a unified look and design. We've talked about it for quite some time. But finding individuals with the talent and time has proved next to impossible to find. If you happen to be an individual who thinks they have the time to come up with a unified please do speak up! We sure could use some help. -Mike From brendan_hart at hotmail.com Fri Mar 14 03:14:40 2008 From: brendan_hart at hotmail.com (brendan hart) Date: Fri, 14 Mar 2008 13:44:40 +1030 Subject: FW: feeds mock-up for front page In-Reply-To: References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> Message-ID: I am a web designer, but at the moment I dont have a working computer :( I broke my laptop and the monitor broke on my Desktop, now I feel depressed that my pride and joy has to sit there like a chump. > Date: Thu, 13 Mar 2008 22:06:45 -0500> From: mmcgrath at redhat.com> To: duffy at fedoraproject.org> CC: fedora-websites-list at redhat.com> Subject: Re: feeds mock-up for front page> > On Thu, 13 Mar 2008, M?ir?n Duffy wrote:> > Ricky Zhou wrote:> > > On 2008-03-13 08:45:35 PM, Juan Camilo Prada Ojeda wrote:> > > > would be good that the look and feel of all related> > > > to fedora seems to be done by A comunity instead of independent random> > > > groups> > > This one is probably my fault (and I agree completely)- the FAS2 design> > > predates the fp.o design by a bit, if I remember correctly, and we never> > > got a good chance to update the design before launching.> >> > Yeh, that's pretty much what happened. The mockups for FAS2 were done before> > the FPO ones. I think the FPO template is really what we want to start moving> > forward on across sites.> >> > Just to make something clear to those on the lists. We all want a unified> look and design. We've talked about it for quite some time. But finding> individuals with the talent and time has proved next to impossible to> find. If you happen to be an individual who thinks they have the time to> come up with a unified please do speak up! We sure could use some help.> > -Mike _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&referral=hotmailtaglineOct07&URL=http://music.ninemsn.com.au/roguetraders -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001 URL: From juankprada at gmail.com Fri Mar 14 03:40:12 2008 From: juankprada at gmail.com (Juan Camilo Prada) Date: Thu, 13 Mar 2008 22:40:12 -0500 Subject: feeds mock-up for front page In-Reply-To: References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> Message-ID: <1205466012.11635.2.camel@localhost.localdomain> On Thu, 2008-03-13 at 22:06 -0500, Mike McGrath wrote: > On Thu, 13 Mar 2008, M?ir?n Duffy wrote: > > Ricky Zhou wrote: > > > On 2008-03-13 08:45:35 PM, Juan Camilo Prada Ojeda wrote: > > > > would be good that the look and feel of all related > > > > to fedora seems to be done by A comunity instead of independent random > > > > groups > > > This one is probably my fault (and I agree completely)- the FAS2 design > > > predates the fp.o design by a bit, if I remember correctly, and we never > > > got a good chance to update the design before launching. > > > > Yeh, that's pretty much what happened. The mockups for FAS2 were done before > > the FPO ones. I think the FPO template is really what we want to start moving > > forward on across sites. > > > > Just to make something clear to those on the lists. We all want a unified > look and design. We've talked about it for quite some time. But finding > individuals with the talent and time has proved next to impossible to > find. If you happen to be an individual who thinks they have the time to > come up with a unified please do speak up! We sure could use some help. > > -Mike Well im not really a designer (im most in the coding field) but i think i know some basics about web design and i could help. But i think that its not just people what we need but to settle things about the look and feel, and thats something we havent done yet. I mean, yes we have discussed such things, but never get a conclusion to start from. -- Juan Camilo Prada From kwade at redhat.com Fri Mar 14 04:47:41 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 13 Mar 2008 21:47:41 -0700 Subject: feeds mock-up for front page In-Reply-To: <1205466012.11635.2.camel@localhost.localdomain> References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> Message-ID: <1205470061.13919.43.camel@calliope.phig.org> On Thu, 2008-03-13 at 22:40 -0500, Juan Camilo Prada wrote: > But i think that its not just people what we need but to settle things > about the look and feel, and thats something we havent done yet. I > mean, > yes we have discussed such things, but never get a conclusion to start > from. We could just consider the design in place on fedoraproject.org pages as the new style and make everything else match. One thing that is important is to find a way to make it easy to re-theme the websites. This means using the same CSS elements in the same way across all websites. Then it is easier to redesign the sites by updating a single CSS, right? - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From duffy at fedoraproject.org Fri Mar 14 05:02:28 2008 From: duffy at fedoraproject.org (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Fri, 14 Mar 2008 01:02:28 -0400 Subject: feeds mock-up for front page In-Reply-To: <1205470061.13919.43.camel@calliope.phig.org> References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> Message-ID: <47DA06E4.9000009@fedoraproject.org> Karsten 'quaid' Wade wrote: > On Thu, 2008-03-13 at 22:40 -0500, Juan Camilo Prada wrote: > >> But i think that its not just people what we need but to settle things >> about the look and feel, and thats something we havent done yet. I >> mean, >> yes we have discussed such things, but never get a conclusion to start >> from. > > We could just consider the design in place on fedoraproject.org pages as > the new style and make everything else match. > > One thing that is important is to find a way to make it easy to re-theme > the websites. This means using the same CSS elements in the same way > across all websites. Then it is easier to redesign the sites by > updating a single CSS, right? Yeh, this is how I did the CSS for the test mediawiki instance. It draws from the main FPO style sheet so for the two sites it's one CSS. ~m From brendan_hart at hotmail.com Fri Mar 14 05:58:58 2008 From: brendan_hart at hotmail.com (brendan hart) Date: Fri, 14 Mar 2008 16:28:58 +1030 Subject: FW: feeds mock-up for front page In-Reply-To: <1205470061.13919.43.camel@calliope.phig.org> References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> Message-ID: Your exactly right about the css, But it will be hard to come up with a good css, alot of people have their own ways of implenting CSS styles and it is very debated, then if we add new software to the site design we will need to add more css then update each of the pages. Its a good idea though :P > From: kwade at redhat.com> To: fedora-websites-list at redhat.com> Date: Thu, 13 Mar 2008 21:47:41 -0700> Subject: Re: feeds mock-up for front page> > > On Thu, 2008-03-13 at 22:40 -0500, Juan Camilo Prada wrote:> > > But i think that its not just people what we need but to settle things> > about the look and feel, and thats something we havent done yet. I> > mean,> > yes we have discussed such things, but never get a conclusion to start> > from.> > We could just consider the design in place on fedoraproject.org pages as> the new style and make everything else match.> > One thing that is important is to find a way to make it easy to re-theme> the websites. This means using the same CSS elements in the same way> across all websites. Then it is easier to redesign the sites by> updating a single CSS, right?> > - Karsten> -- > Karsten Wade, Developer Community Mgr.> Dev Fu : http://developer.redhatmagazine.com> Fedora : http://quaid.fedorapeople.org> gpg key : AD0E0C41 _________________________________________________________________ What are you waiting for? Join Lavalife FREE http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30288&_t=764581033&_r=email_taglines_Join_free_OCT07&_m=EXT -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001 URL: From stickster at gmail.com Fri Mar 14 13:47:02 2008 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 14 Mar 2008 13:47:02 +0000 Subject: CLA process Message-ID: <1205502422.18167.60.camel@localhost.localdomain> Legal confirmed for the Board that: * We no longer need to require GPG signatures for our CLA signing process. This means that the FAS2 can be modified to greatly speed up this process. Refer to: https://hosted.fedoraproject.org/fedora-infrastructure/ticket/438 * We still need CLA for wiki writers, but now that we don't need the GPG, this can be a fully click-through process if the Websites team can make it so. In other words, if I want to save my contribution, I still have to agree to the CLA. That means the wiki needs to be tied to FAS2 somehow to check my account. In a way, I guess this is "good news + bad news" because it might mean some work to accomplish the second task. Is this possible to do? If so, who on Websites can own the task? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From pribyl at lowlevel.cz Fri Mar 14 15:23:49 2008 From: pribyl at lowlevel.cz (Adam Pribyl) Date: Fri, 14 Mar 2008 16:23:49 +0100 (CET) Subject: feeds mock-up for front page In-Reply-To: References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> Message-ID: FAS2 looks slightly different, but I do not feel this to be a big problem. BTW: This thread was about feeds at front page. I like what Juan Camilo Prada Ojeda did. The design Karsten 'quaid' Wade did is bit too raw now - e.g. I would not recommend to use different dashing type, just use the one that is already used on the page, also the dashed/dotted line should be split as the collums are. Font type is strange etc. What was not meantioned is - the frontpage was made that simple as it is because of high load on this page at time of new releases. Is including again any dynamic content something the servers can stand at this time? Adam Pribyl From juankprada at gmail.com Fri Mar 14 22:20:33 2008 From: juankprada at gmail.com (Juan Camilo Prada Ojeda) Date: Fri, 14 Mar 2008 22:20:33 +0000 Subject: CLA process In-Reply-To: <1205502422.18167.60.camel@localhost.localdomain> References: <1205502422.18167.60.camel@localhost.localdomain> Message-ID: 2008/3/14, Paul W. Frields : > > Legal confirmed for the Board that: > > * We no longer need to require GPG signatures for our CLA signing > process. This means that the FAS2 can be modified to greatly speed up > this process. Refer to: > > https://hosted.fedoraproject.org/fedora-infrastructure/ticket/438 > > * We still need CLA for wiki writers, but now that we don't need the > GPG, this can be a fully click-through process if the Websites team can > make it so. In other words, if I want to save my contribution, I still > have to agree to the CLA. That means the wiki needs to be tied to FAS2 > somehow to check my account. > > In a way, I guess this is "good news + bad news" because it might mean > some work to accomplish the second task. Is this possible to do? If > so, who on Websites can own the task? Wasnt there a ticket to change wiki engine?, wouldnt it be better to do those changes after migrating to the new wiki engine? so we wont have to do things twice -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeanb5415 at frontiernet.net Fri Mar 14 23:53:19 2008 From: jeanb5415 at frontiernet.net (Jean Bonnett) Date: Fri, 14 Mar 2008 19:53:19 -0400 Subject: My website Message-ID: <000601c8862e$95523730$03fea8c0@D1GHYM41> You are messing up my website. Please get out. jean at jeanbonnetart.com \ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricky at fedoraproject.org Sat Mar 15 01:46:09 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 14 Mar 2008 21:46:09 -0400 Subject: [edsall@iastate.edu: CLA not being accepted] Message-ID: <20080315014609.GB5626@Max.nyc1.dsl.speakeasy.net> ----- Forwarded message from Dave Edsall - JETSETer ----- From: "Dave Edsall - JETSETer" To: webmaster at fedoraproject.org Date: Thu, 13 Mar 2008 12:38:13 -0500 Subject: CLA not being accepted I have tried several times to sign and submit the CLA via your web interface and am getting You could not be added to the 'cla_fedora' group. Any clues? I typed in my name and "I agree" as asked in the form. Thanks for your help, Dave ----- End forwarded message ----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rseguel at mariscope.cl Thu Mar 13 11:40:47 2008 From: rseguel at mariscope.cl (Romanet Seguel) Date: Thu, 13 Mar 2008 08:40:47 -0300 Subject: Question or request Message-ID: Hello: I?m try to find Fedora core 6 from torrent, and is very hard to find. You now some link or something, I really needs to run some open source software named SEADAS. Thanks a lot ._._._._._._._._._._._._._._._._ Romanet Seguel Depto. Oceanograf?a Mariscope Chilena Ega?a 425 Puerto Montt (+56)65-434324 ._._._._._._._._._._._._._._._._ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricky at fedoraproject.org Sat Mar 15 01:52:46 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 14 Mar 2008 21:52:46 -0400 Subject: [edsall@iastate.edu: CLA not being accepted] In-Reply-To: <20080315014609.GB5626@Max.nyc1.dsl.speakeasy.net> References: <20080315014609.GB5626@Max.nyc1.dsl.speakeasy.net> Message-ID: <20080315015246.GC5626@Max.nyc1.dsl.speakeasy.net> On 2008-03-14 09:46:09 PM, Ricky Zhou wrote: > ----- Forwarded message from Dave Edsall - JETSETer ----- > > From: "Dave Edsall - JETSETer" > To: webmaster at fedoraproject.org > Date: Thu, 13 Mar 2008 12:38:13 -0500 > Subject: CLA not being accepted > > > > I have tried several times to sign and submit the CLA via your web > interface and am getting > > You could not be added to the 'cla_fedora' group. > > > Any clues? I typed in my name and "I agree" as asked in the form. > > > Thanks for your help, > > > Dave Hi! We just recently updated the Fedora Account System a few days ago, so we've been seeing a few problems with CLA signing. We're currently pushing a update with (hopefully) a fix to this problem, so please let us know (and tell us your Fedora Account username) if you're still getting this problem. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ricky at fedoraproject.org Sat Mar 15 01:55:18 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 14 Mar 2008 21:55:18 -0400 Subject: My website In-Reply-To: <000601c8862e$95523730$03fea8c0@D1GHYM41> References: <000601c8862e$95523730$03fea8c0@D1GHYM41> Message-ID: <20080315015518.GD5626@Max.nyc1.dsl.speakeasy.net> On 2008-03-14 07:53:19 PM, Jean Bonnett wrote: > You are messing up my website. > > Please get out. > > jean at jeanbonnetart.com I assume that you're referring to a "Fedora Test Page" somewhere. That is a test page included with our operating system; we don't actually control the site in question. For more information, please refer to http://fedoraproject.org/wiki/ServerTestPage. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ricky at fedoraproject.org Sat Mar 15 01:59:28 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 14 Mar 2008 21:59:28 -0400 Subject: Question or request In-Reply-To: References: Message-ID: <20080315015928.GE5626@Max.nyc1.dsl.speakeasy.net> On 2008-03-13 08:40:47 AM, Romanet Seguel wrote: > Hello: > > > > I?m try to find Fedora core 6 from torrent, and is very hard to find. > > > > You now some link or something, I really needs to run some open source > software named SEADAS. Fedora Core 6 is no longer supported, so it is no longer on our torrent tracker. Try and see if you can install or build your software on Fedora 8 (the current version). For more help with this, try looking at some of the help resources described at http://fedoraproject.org/wiki/Communicate (webmaster at fedoraproject.org only deals with issues related to Fedora's websites). Good luck, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ricky at fedoraproject.org Sat Mar 15 02:31:37 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 14 Mar 2008 22:31:37 -0400 Subject: Updating CLA Documentation Message-ID: <20080315023137.GF5626@Max.nyc1.dsl.speakeasy.net> After Paul's CLA announcement today (https://www.redhat.com/archives/fedora-websites-list/2008-March/msg00062.html), we have pushed a FAS2 update that no longer requires a GPG-signed CLA. This is a huge win in terms of making it easier for new contributors to get started---now, we need to go through and update all of the FAS and CLA documentation (mostly on the wiki) for the new process. Here are just a few of the wiki pages that we should start updating: * http://fedoraproject.org/wiki/Infrastructure/AccountSystem * http://fedoraproject.org/wiki/WikiEditing * http://fedoraproject.org/wiki/PackageMaintainers/Join#head-a601c13b0950a89568deafa65f505b4b58ee869b * http://fedoraproject.org/wiki/L10N/Join If you want to get a better feel for how account creation and CLA signing works in FAS2, feel free to try it out with a test account at http://publictest10.fedoraproject.org/accounts/. Thanks a lot, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Sat Mar 15 04:23:07 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Fri, 14 Mar 2008 21:23:07 -0700 Subject: feeds mock-up for front page In-Reply-To: References: <1205436866.31045.173.camel@calliope.phig.org> <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> Message-ID: <1205554988.13919.136.camel@calliope.phig.org> On Fri, 2008-03-14 at 16:23 +0100, Adam Pribyl wrote: > FAS2 looks slightly different, but I do not feel this to be a big problem. > BTW: This thread was about feeds at front page. I like what Juan Camilo > Prada Ojeda did. The design Karsten 'quaid' Wade did is bit too raw now - > e.g. I would not recommend to use different dashing type, just use the one > that is already used on the page, also the dashed/dotted line should be > split as the collums are. Font type is strange etc. Sure, it was just a straw man and full of flaws. Unanswered question -- do we want the three-column or the two column with the feeds in the main #content area? > What was not meantioned is - the frontpage was made that simple as it is > because of high load on this page at time of new releases. Is including > again any dynamic content something the servers can stand at this time? Good point. There is benefit to having dynamic content during release time, but it does carry a risk. Maybe we can do something different for the few days after release, such as: * Comment out the code entirely (sub-optimal) * Have the code run as a cronjob every N minutes (15 min.?) then write out a static bit of HTML for the page to publish * Manually write out the content and leave it is a static "feed" that is updated by hand ever N hours (N = 12? N = 24?) - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Sat Mar 15 04:28:18 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Fri, 14 Mar 2008 21:28:18 -0700 Subject: CLA process In-Reply-To: References: <1205502422.18167.60.camel@localhost.localdomain> Message-ID: <1205555298.13919.140.camel@calliope.phig.org> On Fri, 2008-03-14 at 22:20 +0000, Juan Camilo Prada Ojeda wrote: > > Wasnt there a ticket to change wiki engine?, wouldnt it be better to > do those changes after > migrating to the new wiki engine? so we wont have to do things twice While that is true ... we've been waiting a long time for this capability and it would be *great* if we had a wiki that many more people can contribute to when Fedora 9 is released. AIUI, Moin 1.6 has this capability to do a one-time show of the CLA when an account is created. Paulo Santos was working on this last, but there should be a patch or configuration for it somewhere. - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From ricky at fedoraproject.org Sat Mar 15 04:34:37 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Sat, 15 Mar 2008 00:34:37 -0400 Subject: feeds mock-up for front page In-Reply-To: <1205554988.13919.136.camel@calliope.phig.org> References: <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> <1205554988.13919.136.camel@calliope.phig.org> Message-ID: <20080315043437.GG5626@Max.nyc1.dsl.speakeasy.net> On 2008-03-14 09:23:07 PM, Karsten 'quaid' Wade wrote: > > On Fri, 2008-03-14 at 16:23 +0100, Adam Pribyl wrote: > > What was not meantioned is - the frontpage was made that simple as it is > > because of high load on this page at time of new releases. Is including > > again any dynamic content something the servers can stand at this time? > > Good point. There is benefit to having dynamic content during release > time, but it does carry a risk. Maybe we can do something different for > the few days after release, such as: > > * Comment out the code entirely (sub-optimal) > * Have the code run as a cronjob every N minutes (15 min.?) then write > out a static bit of HTML for the page to publish > * Manually write out the content and leave it is a static "feed" that is > updated by hand ever N hours (N = 12? N = 24?) Right now, the website is generated every hour - would this be an acceptable delay for RSS updates? The RSS support that I mentioned on the ticket is just downloading/parsing the feed during the website build (and displaying the top few entries). Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Sat Mar 15 06:30:51 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Fri, 14 Mar 2008 23:30:51 -0700 Subject: feeds mock-up for front page In-Reply-To: <20080315043437.GG5626@Max.nyc1.dsl.speakeasy.net> References: <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> <1205554988.13919.136.camel@calliope.phig.org> <20080315043437.GG5626@Max.nyc1.dsl.speakeasy.net> Message-ID: <1205562651.13919.170.camel@calliope.phig.org> On Sat, 2008-03-15 at 00:34 -0400, Ricky Zhou wrote: > On 2008-03-14 09:23:07 PM, Karsten 'quaid' Wade wrote: > > > > On Fri, 2008-03-14 at 16:23 +0100, Adam Pribyl wrote: > > > What was not meantioned is - the frontpage was made that simple as it is > > > because of high load on this page at time of new releases. Is including > > > again any dynamic content something the servers can stand at this time? > > > > Good point. There is benefit to having dynamic content during release > > time, but it does carry a risk. Maybe we can do something different for > > the few days after release, such as: > > > > * Comment out the code entirely (sub-optimal) > > * Have the code run as a cronjob every N minutes (15 min.?) then write > > out a static bit of HTML for the page to publish > > * Manually write out the content and leave it is a static "feed" that is > > updated by hand ever N hours (N = 12? N = 24?) > Right now, the website is generated every hour - would this be an > acceptable delay for RSS updates? The RSS support that I mentioned on > the ticket is just downloading/parsing the feed during the website > build (and displaying the top few entries). +1 In practice, I often notice long delays between posting and something coming out of Feedburner, which supplies feeds for *.redhatmagazine.com and Fedora Weekly News. I doubt the hourly build would ever make it feel longer than it is already. :D I displayed the top three items in my mock-up, but I'm a bit partial to five items. I'll leave that decision up to proper designers and UI experts. Looking around a bit more, here are the three groupings I like. OTOH, another option is to pull them into one scrolling column. The main reason I don't like that is steady-state content such as FWN should go up and stay up for the week, with the past few weeks visible. If we combined it into one scrolling column, it would scroll off in under two hours. --- "Fedora Weekly News" http://fedora-tchung.blogspot.com/feeds/posts/default ---- "Red Hat Magazine/Dev Fu/Truth Happens" or "Red Hat Magazine" http://www.redhatmagazine.com/category/fedora/feed http://developer.redhatmagazine.com/category/fedora/feed http://truthhappens.redhatmagazine.com/feed --- "Fedora Announcements" rss://fedora-announce-list at redhat.com (?) http://news.fedoraproject.org/feed --- - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From paulej at packetizer.com Sun Mar 16 07:06:33 2008 From: paulej at packetizer.com (Paul E. Jones) Date: Sun, 16 Mar 2008 03:06:33 -0400 Subject: Language selection logic is incorrect Message-ID: <02fc01c88734$449e8df0$cddba9d0$@com> Fedora Web Team, When I visit fedoraproject.org with a browser set to advertise acceptance of two languages, my preferred language (English) is not presented. Rather, my less preferred language (Chinese) is presented by default. I captured what was sent to the server and the HTTP request contains: Accept-Language: en-US,zh-CN;q=0.5 So, English should be displayed first, since it has a higher "q" value and is listed first. At least I would think ;-) Cheers! Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From kwade at redhat.com Sun Mar 16 22:55:14 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Sun, 16 Mar 2008 15:55:14 -0700 Subject: one fedora.css Message-ID: <1205708114.13919.226.camel@calliope.phig.org> Do we have one fedora.css? Can we get one together? How do we want to manage growing it? For example, I want to use it for docs.fp.org, but that requires additional styles for the DocBook styling. Would we just call e.g. fedora-docs.css? I'd like to start redesigning docs.fp.o with a modern, all-one fedora.css. Which style is The Style? ;-P thx - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From ivazqueznet at gmail.com Sun Mar 16 23:35:18 2008 From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams) Date: Sun, 16 Mar 2008 19:35:18 -0400 Subject: one fedora.css In-Reply-To: <1205708114.13919.226.camel@calliope.phig.org> References: <1205708114.13919.226.camel@calliope.phig.org> Message-ID: <1205710518.14871.8.camel@localhost.localdomain> On Sun, 2008-03-16 at 15:55 -0700, Karsten 'quaid' Wade wrote: > Do we have one fedora.css? > > Can we get one together? > > How do we want to manage growing it? > > For example, I want to use it for docs.fp.org, but that requires > additional styles for the DocBook styling. Would we just call e.g. > fedora-docs.css? > > I'd like to start redesigning docs.fp.o with a modern, all-one > fedora.css. > > Which style is The Style? ;-P That would be great goal. A single fedora.css for all sites, and a customized foo.css per site as well (just as fedorahosted.org has, nudge nudge wink wink). -- Ignacio Vazquez-Abrams From brendan_hart at hotmail.com Mon Mar 17 02:20:13 2008 From: brendan_hart at hotmail.com (brendan hart) Date: Mon, 17 Mar 2008 12:50:13 +1030 Subject: FW: one fedora.css In-Reply-To: <1205710518.14871.8.camel@localhost.localdomain> References: <1205708114.13919.226.camel@calliope.phig.org> <1205710518.14871.8.camel@localhost.localdomain> Message-ID: Hey guys, Would you like me to work on a css/xhtml site, I wont put any designs I'll just show how it can be modified easily etc. > From: ivazqueznet at gmail.com> To: fedora-websites-list at redhat.com> Date: Sun, 16 Mar 2008 19:35:18 -0400> Subject: Re: one fedora.css> > On Sun, 2008-03-16 at 15:55 -0700, Karsten 'quaid' Wade wrote: > > Do we have one fedora.css?> > > > Can we get one together?> > > > How do we want to manage growing it?> > > > For example, I want to use it for docs.fp.org, but that requires> > additional styles for the DocBook styling. Would we just call e.g.> > fedora-docs.css?> > > > I'd like to start redesigning docs.fp.o with a modern, all-one> > fedora.css.> > > > Which style is The Style? ;-P> > That would be great goal. A single fedora.css for all sites, and a> customized foo.css per site as well (just as fedorahosted.org has, nudge> nudge wink wink).> > -- > Ignacio Vazquez-Abrams > > -- > Fedora-websites-list mailing list> Fedora-websites-list at redhat.com> https://www.redhat.com/mailman/listinfo/fedora-websites-list _________________________________________________________________ What are you waiting for? Join Lavalife FREE http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30288&_t=764581033&_r=email_taglines_Join_free_OCT07&_m=EXT -------------- next part -------------- An HTML attachment was scrubbed... URL: From fedora-websites-list at redhat.com Mon Mar 17 00:18:28 2008 From: fedora-websites-list at redhat.com (Karsten Wade (kwade)) Date: Mon, 17 Mar 2008 00:18:28 GMT Subject: web/html/docs/encryption-privacy-guide - New directory Message-ID: <200803170018.m2H0ISFI031800@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/fedora/web/html/docs/encryption-privacy-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31796/encryption-privacy-guide Log Message: Directory /cvs/fedora/web/html/docs/encryption-privacy-guide added to the repository From duffy at fedoraproject.org Mon Mar 17 13:40:42 2008 From: duffy at fedoraproject.org (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Mon, 17 Mar 2008 09:40:42 -0400 Subject: one fedora.css In-Reply-To: <1205708114.13919.226.camel@calliope.phig.org> References: <1205708114.13919.226.camel@calliope.phig.org> Message-ID: <47DE74DA.2080509@fedoraproject.org> Karsten 'quaid' Wade wrote: > Do we have one fedora.css? > > Can we get one together? > > How do we want to manage growing it? > > For example, I want to use it for docs.fp.org, but that requires > additional styles for the DocBook styling. Would we just call e.g. > fedora-docs.css? > > I'd like to start redesigning docs.fp.o with a modern, all-one > fedora.css. > > Which style is The Style? ;-P Use this: http://fedoraproject.org/en/static/css/fedora.css List it first in your css imports. After it, list any styles specific to the pages you're working with to cover areas not covered by the main stylesheet or to cover things that are semantically unique to your new usage. For example, look at: https://publictest1.fedoraproject.org/wiki/FedoraMain The main stylesheet it uses is the one above, and then media-wiki specific styles and tweaks are in the stylesheets below it. ~m From mmcgrath at redhat.com Mon Mar 17 14:01:05 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 17 Mar 2008 09:01:05 -0500 (CDT) Subject: CLA process In-Reply-To: <1205555298.13919.140.camel@calliope.phig.org> References: <1205502422.18167.60.camel@localhost.localdomain> <1205555298.13919.140.camel@calliope.phig.org> Message-ID: On Fri, 14 Mar 2008, Karsten 'quaid' Wade wrote: > > On Fri, 2008-03-14 at 22:20 +0000, Juan Camilo Prada Ojeda wrote: > > > > > Wasnt there a ticket to change wiki engine?, wouldnt it be better to > > do those changes after > > migrating to the new wiki engine? so we wont have to do things twice > > While that is true ... we've been waiting a long time for this > capability and it would be *great* if we had a wiki that many more > people can contribute to when Fedora 9 is released. > > AIUI, Moin 1.6 has this capability to do a one-time show of the CLA when > an account is created. Paulo Santos was working on this last, but there > should be a patch or configuration for it somewhere. > I've looked at getting Moin integrated into FAS2. Its actually very easy if we _require_ fas2 everywhere :) but trying to get anon + fas2 is a bit more work. So for now having the cla on the wiki in addition to FAS2 I think is a good way to go. Does the "wiki license" link not work? I know Paulo has been busy with $DAYJOB stuff so I'd suspect we might be better implementing this ourselves. Karsten, was there a thread or ticket you two were working on? Perhaps someone else can take off where it was left off? There's no problem getting this implemented AFAIK, just needs people hours to do it. -Mike From mmcgrath at redhat.com Mon Mar 17 14:02:33 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 17 Mar 2008 09:02:33 -0500 (CDT) Subject: one fedora.css In-Reply-To: <47DE74DA.2080509@fedoraproject.org> References: <1205708114.13919.226.camel@calliope.phig.org> <47DE74DA.2080509@fedoraproject.org> Message-ID: On Mon, 17 Mar 2008, M?ir?n Duffy wrote: > Karsten 'quaid' Wade wrote: > > Do we have one fedora.css? > > > > Can we get one together? > > > > How do we want to manage growing it? > > > > For example, I want to use it for docs.fp.org, but that requires > > additional styles for the DocBook styling. Would we just call e.g. > > fedora-docs.css? > > > > I'd like to start redesigning docs.fp.o with a modern, all-one > > fedora.css. > > > > Which style is The Style? ;-P > > Use this: > > http://fedoraproject.org/en/static/css/fedora.css > > List it first in your css imports. After it, list any styles specific to the > pages you're working with to cover areas not covered by the main stylesheet or > to cover things that are semantically unique to your new usage. > > For example, look at: > > https://publictest1.fedoraproject.org/wiki/FedoraMain > > The main stylesheet it uses is the one above, and then media-wiki specific > styles and tweaks are in the stylesheets below it. > Sounds good to me, anyone on the list wanting to get involved? Start making some mockups!!! -Mike From fedora-websites-list at redhat.com Mon Mar 17 15:19:50 2008 From: fedora-websites-list at redhat.com (Karsten Wade (kwade)) Date: Mon, 17 Mar 2008 15:19:50 GMT Subject: web/html/docs/encryption-privacy-guide index.php,NONE,1.1 Message-ID: <200803171519.m2HFJoKX014244@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/fedora/web/html/docs/encryption-privacy-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14239/encryption-privacy-guide Added Files: index.php Log Message: need a landing location to point at from the relnotes; this gives us until final release or thereabouts to get the crypto-guide worked up. ***** Error reading new file: [Errno 2] No such file or directory: 'index.php' From juankprada at gmail.com Mon Mar 17 17:18:50 2008 From: juankprada at gmail.com (Juan Camilo Prada Ojeda) Date: Mon, 17 Mar 2008 13:18:50 -0400 Subject: how is this website related to the project? Message-ID: well i was just searching for some tips/tutorials/guides on the internet and i found this site-> http://www.fedoramd.org/ It happens to have almost the same content of fp.o site but doest seem to be a official website, my concern is that if it is not official it doesnt specify, and due to it being so like fp.o it could have content that might damage the ideas of fedora project -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon at questionsplease.org Mon Mar 17 17:15:15 2008 From: jon at questionsplease.org (Jonathan Roberts) Date: Mon, 17 Mar 2008 11:15:15 -0600 Subject: Beta Release Notes Message-ID: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> Hi all, I wondered if somebody could help me out and create a static version of the Beta release notes at http://fedoraproject.org/wiki/Releases/9/Beta/ReleaseNotes ? Hopefully we'll be able to avoid the problems this caused with the Alpha release :) Many thanks, Jon From tchung at fedoraproject.org Mon Mar 17 18:24:09 2008 From: tchung at fedoraproject.org (Thomas Chung) Date: Mon, 17 Mar 2008 11:24:09 -0700 Subject: how is this website related to the project? In-Reply-To: References: Message-ID: <369bce3b0803171124u37614a07h4f47d5cf34e35233@mail.gmail.com> 2008/3/17 Juan Camilo Prada Ojeda : > well i was just searching for some tips/tutorials/guides on the internet and > i found this site-> http://www.fedoramd.org/ > > It happens to have almost the same content of fp.o site but doest seem to be > a official website, my concern is that if it is not > official it doesnt specify, and due to it being so like fp.o it could have > content that might damage the ideas of fedora project I'm not sure it'll damage fedora project but he[1] is one of our mirrors[2] in Moldova[3]. [1] http://fedoraproject.org/wiki/VasileChelban [2] http://mirrors.fedoraproject.org/publiclist (County Code MD) [3] http://en.wikipedia.org/wiki/Moldova Regards, -- Thomas Chung http://fedoraproject.org/wiki/ThomasChung From paulo.banon at googlemail.com Tue Mar 18 09:05:04 2008 From: paulo.banon at googlemail.com (Paulo Santos) Date: Tue, 18 Mar 2008 10:05:04 +0100 Subject: CLA process In-Reply-To: References: <1205502422.18167.60.camel@localhost.localdomain> <1205555298.13919.140.camel@calliope.phig.org> Message-ID: <7a41c4bc0803180205l628fcecbp56cca1dc3ef6cd8b@mail.gmail.com> Hi all, First of all, i'm really sorry for my absense, but i guess that until the end of July i wont have that much free time. Regarding the process we had, it was mainly a patch that Moin upstream had against Moin-1.6, the thing is that we (Infrastructure Team) is looking into migrating from Moin to Mediawiki. I'm currently not aware of the timelines, but unless someone codes something similar to Moin 1.5.x we wont go anywhere with this. The patch was mainly to modify the UserPreferences page, so that when you would register your account, you would first have the CLA, then a line stating something like "If you create an account, you hereby agree with the CLA", then the Username/Password fields. Please let me know if this answer all (or at least some :P ) of your questions :) Paulo On Mon, Mar 17, 2008 at 3:01 PM, Mike McGrath wrote: > On Fri, 14 Mar 2008, Karsten 'quaid' Wade wrote: > > > > > On Fri, 2008-03-14 at 22:20 +0000, Juan Camilo Prada Ojeda wrote: > > > > > > > > Wasnt there a ticket to change wiki engine?, wouldnt it be better to > > > do those changes after > > > migrating to the new wiki engine? so we wont have to do things twice > > > > While that is true ... we've been waiting a long time for this > > capability and it would be *great* if we had a wiki that many more > > people can contribute to when Fedora 9 is released. > > > > AIUI, Moin 1.6 has this capability to do a one-time show of the CLA when > > an account is created. Paulo Santos was working on this last, but there > > should be a patch or configuration for it somewhere. > > > > I've looked at getting Moin integrated into FAS2. Its actually very easy > if we _require_ fas2 everywhere :) but trying to get anon + fas2 is a bit > more work. So for now having the cla on the wiki in addition to FAS2 I > think is a good way to go. > > Does the "wiki license" link not work? I know Paulo has been busy with > $DAYJOB stuff so I'd suspect we might be better implementing this > ourselves. > > Karsten, was there a thread or ticket you two were working on? Perhaps > someone else can take off where it was left off? There's no problem > getting this implemented AFAIK, just needs people hours to do it. > > -Mike > > -- > Fedora-websites-list mailing list > Fedora-websites-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-websites-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stickster at gmail.com Tue Mar 18 13:36:29 2008 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 18 Mar 2008 09:36:29 -0400 Subject: Beta Release Notes In-Reply-To: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> References: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> Message-ID: <1205847389.25162.77.camel@localhost.localdomain> On Mon, 2008-03-17 at 11:15 -0600, Jonathan Roberts wrote: > Hi all, > > I wondered if somebody could help me out and create a static version of the > Beta release notes at > http://fedoraproject.org/wiki/Releases/9/Beta/ReleaseNotes ? > > Hopefully we'll be able to avoid the problems this caused with the Alpha > release :) Great point. We should also give thought to where we provide links to these notes too, and direct them to the static page. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From AnyongXia at viatech.com.cn Tue Mar 18 06:15:38 2008 From: AnyongXia at viatech.com.cn (AnyongXia at viatech.com.cn) Date: Tue, 18 Mar 2008 14:15:38 +0800 Subject: request for mirror Message-ID: HI, I have builded a server with fedora 7, and I want to make a mirror of your websites, please recommend the tool for this. Thank you! Best Wishes! 2008.3.18 -------------- next part -------------- An HTML attachment was scrubbed... URL: From reed4freedom at bellsouth.net Tue Mar 18 13:06:18 2008 From: reed4freedom at bellsouth.net (reed4freedom at bellsouth.net) Date: Tue, 18 Mar 2008 09:06:18 -0400 (Eastern Daylight Time) Subject: HELP Message-ID: <47DFBE4A.000005.03752@BILL-2TQ5JYNTCZ> I've been visiting a web site forum for several years now but the other day I entered the URL of www.homesteadingtoday.com into my browser and I get nothing but a Fedora Test page. I've done everything I know of to correct this on my end, clearing cookies, cache browser etc but I'm still getting this test page. I'm using mozilla foxfire. I know the home steading forum is active, I can access it with another PC... Can you help shed some light on this for me please? Sincerely, Bill Reed -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imstp_pets_cat1_en.gif Type: image/gif Size: 36179 bytes Desc: not available URL: From bicycle.nutz at gmail.com Tue Mar 18 14:41:58 2008 From: bicycle.nutz at gmail.com (Craig Thomas) Date: Tue, 18 Mar 2008 10:41:58 -0400 Subject: HELP In-Reply-To: <47DFBE4A.000005.03752@BILL-2TQ5JYNTCZ> References: <47DFBE4A.000005.03752@BILL-2TQ5JYNTCZ> Message-ID: 2008/3/18 reed4freedom at bellsouth.net : > I've been visiting a web site forum for several years now but the other day > I entered the URL of www.homesteadingtoday.com into my browser and I get > nothing but a Fedora Test page. > I've done everything I know of to correct this on my end, clearing cookies, > cache browser etc but I'm still getting this test page. I'm using mozilla > foxfire. > I know the home steading forum is active, I can access it with another PC... > Can you help shed some light on this for me please? > Sincerely, > Bill Reed Hello Bill, That is a test page included with our operating system; we don't actually control the site in question. Please refer to http://fedoraproject.org/wiki/ServerTestPage For what it is worth, I can get to the forum at the url you've posted. I suspect the owners of that site are using Fedora as their operating system and have been doing some sort of maintenance on their servers. If your problems persist, try contacting the site owner, who's information you can find using a 'whois' lookup [1]. Cheers, -- Craig Thomas [1] [cwt at localhost ~]$ whois homesteadingtoday.com [Querying whois.verisign-grs.com] [Redirected to whois.godaddy.com] [Querying whois.godaddy.com] [whois.godaddy.com] The data contained in GoDaddy.com, Inc.'s WhoIs database, while believed by the company to be reliable, is provided "as is" with no guarantee or warranties regarding its accuracy. This information is provided for the sole purpose of assisting you in obtaining information about domain name registration records. Any use of this data for any other purpose is expressly forbidden without the prior written permission of GoDaddy.com, Inc. By submitting an inquiry, you agree to these terms of usage and limitations of warranty. In particular, you agree not to use this data to allow, enable, or otherwise make possible, dissemination or collection of this data, in part or in its entirety, for any purpose, such as the transmission of unsolicited advertising and and solicitations of any kind, including spam. You further agree not to use this data to enable high volume, automated or robotic electronic processes designed to collect or compile this data for any purpose, including mining this data for your own personal or commercial purposes. Please note: the registrant of the domain name is specified in the "registrant" field. In most cases, GoDaddy.com, Inc. is not the registrant of domain names listed in this database. Registrant: Homesteading Forum 13236 Executive Park Ter Germantown, Maryland 20874 United States Registered through: GoDaddy.com, Inc. (http://www.godaddy.com) Domain Name: HOMESTEADINGTODAY.COM Created on: 27-Feb-02 Expires on: 27-Feb-12 Last Updated on: 17-Feb-08 Administrative Contact: Holton, Charles reply at mission4me.com Homesteading Forum 13236 Executive Park Ter Germantown, Maryland 20874 United States 301-540-5596 Fax -- Technical Contact: Holton, Charles reply at mission4me.com Homesteading Forum 13236 Executive Park Ter Germantown, Maryland 20874 United States 301-540-5596 Fax -- Domain servers in listed order: NS57.1AND1.COM NS58.1AND1.COM [cwt at localhost ~]$ From bicycle.nutz at gmail.com Tue Mar 18 15:03:06 2008 From: bicycle.nutz at gmail.com (Craig Thomas) Date: Tue, 18 Mar 2008 11:03:06 -0400 Subject: request for mirror In-Reply-To: References: Message-ID: 2008/3/18 : > HI, > > I have builded a server with fedora 7, and I want to make a mirror of your > websites, please recommend the tool for this. Thank you! > > Best Wishes! > > > 2008.3.18 Hi, Do you mean you wan to mirror the .iso files? For that, you would need to get in contact with the Infrastructure team: http://fedoraproject.org/wiki/Infrastructure/ The best way is IRC on the freenode network #fedora-admin or send an e-mail to fedora-infrastructure-list at redhat.com (you will need to subscribe). -- Craig Thomas From kwade at redhat.com Tue Mar 18 16:47:45 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 18 Mar 2008 09:47:45 -0700 Subject: Beta Release Notes In-Reply-To: <1205847389.25162.77.camel@localhost.localdomain> References: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> <1205847389.25162.77.camel@localhost.localdomain> Message-ID: <1205858865.13919.361.camel@calliope.phig.org> On Tue, 2008-03-18 at 09:36 -0400, Paul W. Frields wrote: > On Mon, 2008-03-17 at 11:15 -0600, Jonathan Roberts wrote: > > Hi all, > > > > I wondered if somebody could help me out and create a static version of the > > Beta release notes at > > http://fedoraproject.org/wiki/Releases/9/Beta/ReleaseNotes ? > > > > Hopefully we'll be able to avoid the problems this caused with the Alpha > > release :) > > Great point. We should also give thought to where we provide links to > these notes too, and direct them to the static page. IIRC, the actual wiki page is turned 'immutable' and actually served as static from that URL. - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Mar 18 17:02:17 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 18 Mar 2008 10:02:17 -0700 Subject: CLA process In-Reply-To: <7a41c4bc0803180205l628fcecbp56cca1dc3ef6cd8b@mail.gmail.com> References: <1205502422.18167.60.camel@localhost.localdomain> <1205555298.13919.140.camel@calliope.phig.org> <7a41c4bc0803180205l628fcecbp56cca1dc3ef6cd8b@mail.gmail.com> Message-ID: <1205859737.13919.365.camel@calliope.phig.org> On Tue, 2008-03-18 at 10:05 +0100, Paulo Santos wrote: > Regarding the process we had, it was mainly a patch that Moin upstream > had against Moin-1.6, the thing is that we (Infrastructure Team) is > looking into migrating from Moin to Mediawiki. I'm currently not aware > of the timelines, but unless someone codes something similar to Moin > 1.5.x we wont go anywhere with this. Sorry, I thought we had upgrade our Moin Moin instance to 1.6. If we are still running 1.5.x without an available patch, then it's likely we'll be done with a MediaWiki changeover before having the patch (?). If we do have the patch available (or easily ported), that's what I recommend -- we do a short-term solution to get a click-through CLA so people can sign-up and begin editing the wiki without requiring another three humans to intervene first. - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Wed Mar 19 13:17:15 2008 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 19 Mar 2008 13:17:15 +0000 Subject: Beta Release Notes In-Reply-To: <1205858865.13919.361.camel@calliope.phig.org> References: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> <1205847389.25162.77.camel@localhost.localdomain> <1205858865.13919.361.camel@calliope.phig.org> Message-ID: <1205932635.12292.27.camel@localhost.localdomain> On Tue, 2008-03-18 at 09:47 -0700, Karsten 'quaid' Wade wrote: > On Tue, 2008-03-18 at 09:36 -0400, Paul W. Frields wrote: > > On Mon, 2008-03-17 at 11:15 -0600, Jonathan Roberts wrote: > > > Hi all, > > > > > > I wondered if somebody could help me out and create a static version of the > > > Beta release notes at > > > http://fedoraproject.org/wiki/Releases/9/Beta/ReleaseNotes ? > > > > > > Hopefully we'll be able to avoid the problems this caused with the Alpha > > > release :) > > > > Great point. We should also give thought to where we provide links to > > these notes too, and direct them to the static page. > > IIRC, the actual wiki page is turned 'immutable' and actually served as > static from that URL. If there's not a significant load from calling Moin and having it assemble everything to display the page, then that sounds fine. Did that work OK, performance-wise, in the past? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Wed Mar 19 14:09:07 2008 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 19 Mar 2008 14:09:07 +0000 Subject: CLA process In-Reply-To: <1205859737.13919.365.camel@calliope.phig.org> References: <1205502422.18167.60.camel@localhost.localdomain> <1205555298.13919.140.camel@calliope.phig.org> <7a41c4bc0803180205l628fcecbp56cca1dc3ef6cd8b@mail.gmail.com> <1205859737.13919.365.camel@calliope.phig.org> Message-ID: <1205935747.12292.37.camel@localhost.localdomain> On Tue, 2008-03-18 at 10:02 -0700, Karsten 'quaid' Wade wrote: > On Tue, 2008-03-18 at 10:05 +0100, Paulo Santos wrote: > > > Regarding the process we had, it was mainly a patch that Moin upstream > > had against Moin-1.6, the thing is that we (Infrastructure Team) is > > looking into migrating from Moin to Mediawiki. I'm currently not aware > > of the timelines, but unless someone codes something similar to Moin > > 1.5.x we wont go anywhere with this. > > Sorry, I thought we had upgrade our Moin Moin instance to 1.6. If we > are still running 1.5.x without an available patch, then it's likely > we'll be done with a MediaWiki changeover before having the patch (?). > > If we do have the patch available (or easily ported), that's what I > recommend -- we do a short-term solution to get a click-through CLA so > people can sign-up and begin editing the wiki without requiring another > three humans to intervene first. I think most of the focus right now is on getting MediaWiki up to speed. Mike and Ricky told me that MW is going to be much easier to hook to FAS2. If we have a clear owner for fixing Moin in the meantime that doesn't impact the MW work, it's probably worthwhile. If it's not there already, learn from my goof and file a ticket! ;-) -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From fedora-websites-list at redhat.com Wed Mar 19 13:45:26 2008 From: fedora-websites-list at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 19 Mar 2008 13:45:26 GMT Subject: web/html/docs/translation-quick-start-guide/en_US generated-index.php, 1.6, 1.7 index.php, 1.10, 1.11 legalnotice-opl.php, 1.4, 1.5 rv-revhistory.php, 1.10, 1.11 sn_accounts.php, 1.10, 1.11 sn_translating_docs.php, 1.10, 1.11 sn_translating_software.php, 1.10, 1.11 Message-ID: <200803191345.m2JDjQjK018602@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18557/en_US Modified Files: generated-index.php index.php legalnotice-opl.php rv-revhistory.php sn_accounts.php sn_translating_docs.php sn_translating_software.php Log Message: Publish TQSG 0.4.1 en_US Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/index.php,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- index.php 3 Mar 2008 17:49:17 -0000 1.10 +++ index.php 19 Mar 2008 13:44:56 -0000 1.11 @@ -81,7 +81,7 @@

    Diego B??rigo Zacar??o

    -

    Version 0.4 (2008-03-03)

    +

    Version 0.4.1 (2008-03-19)

    Copyright ?? 2005, 2006, 2007 Red Hat, Inc. and others

    Index: legalnotice-opl.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/legalnotice-opl.php,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- legalnotice-opl.php 3 Mar 2008 17:49:17 -0000 1.4 +++ legalnotice-opl.php 19 Mar 2008 13:44:56 -0000 1.5 @@ -24,7 +24,7 @@

    1. -REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED +REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS

      Open Publication works may be reproduced and distributed in @@ -58,7 +58,7 @@

    2. -COPYRIGHT

      +COPYRIGHT

      The copyright to each Open Publication is owned by its author(s) or designee. @@ -66,7 +66,7 @@

    3. -SCOPE OF LICENSE

      +SCOPE OF LICENSE

      The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document. @@ -94,7 +94,7 @@

    4. -REQUIREMENTS ON MODIFIED WORKS

      +REQUIREMENTS ON MODIFIED WORKS

      All modified versions of documents covered by this license, including translations, anthologies, compilations and partial @@ -126,7 +126,7 @@

    5. -GOOD-PRACTICE RECOMMENDATIONS

      +GOOD-PRACTICE RECOMMENDATIONS

      In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that: @@ -155,7 +155,7 @@

    6. -LICENSE OPTIONS

      +LICENSE OPTIONS

      The author(s) and/or publisher of an Open Publication-licensed document may elect certain options by appending language to the Index: rv-revhistory.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/rv-revhistory.php,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- rv-revhistory.php 3 Mar 2008 17:49:17 -0000 1.10 +++ rv-revhistory.php 19 Mar 2008 13:44:56 -0000 1.11 @@ -17,6 +17,16 @@

      + + + + + + Index: sn_translating_software.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_translating_software.php,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- sn_translating_software.php 3 Mar 2008 17:49:17 -0000 1.10 +++ sn_translating_software.php 19 Mar 2008 13:44:56 -0000 1.11 @@ -77,16 +77,10 @@

      1. - Visit http://translate.fedoraproject.org/submit/module/ - and select a target module. The interface will redirect you to - a page for that module, such as http://translate.fedoraproject.org/submit/module/comps/. + Visit your language page such as http://translate.fedoraproject.org/languages/ja/, and select a target release. The interface will redirect you to a page for that release, such as http://translate.fedoraproject.org/languages/ja/fedora-9/.

      2. - Scroll down the page to find the table of all po files - available. The pot file - appears at the top of the listing. Use the green download - icon next to each language to download the file to the - directory you created in the previous section. + Scroll down the page to find the table of all modules available for that release. Use the green download icon next to each module to download the po file to the directory you created in the previous section.

      3. From fedora-websites-list at redhat.com Wed Mar 19 13:46:08 2008 From: fedora-websites-list at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 19 Mar 2008 13:46:08 GMT Subject: web/html/docs/translation-quick-start-guide/pt_BR generated-index.php, 1.4, 1.5 index.php, 1.17, 1.18 legalnotice-opl.php, 1.1, 1.2 rv-revhistory.php, 1.17, 1.18 sn_accounts.php, 1.17, 1.18 sn_translating_docs.php, 1.17, 1.18 sn_translating_software.php, 1.17, 1.18 Message-ID: <200803191346.m2JDk8DP018645@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18610/pt_BR Modified Files: generated-index.php index.php legalnotice-opl.php rv-revhistory.php sn_accounts.php sn_translating_docs.php sn_translating_software.php Log Message: Publish TQSG 0.4.1 pt_BR Index: generated-index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/generated-index.php,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- generated-index.php 29 Nov 2007 01:47:32 -0000 1.4 +++ generated-index.php 19 Mar 2008 13:45:38 -0000 1.5 @@ -1,3 +1,14 @@ + + + +??ndice Remissivo + + + + + + + -

      Revision History
      Revision 0.4.12008-03-19NM
      +

      + Replaced the links in the section 3.2. +

      +
      Revision 0.4 2008-03-03 DG
      ??ndice Remissivo
      Anterior??????

      ??ndice Remissivo

      Anterior??????
      4. Traduzindo Documenta????o??Principal??
      + +
      + + + + + + + +
      ??ndice Remissivo
      +Anterior??????
      +
      +
      +
      +

      ??ndice Remissivo

      +
      +
      +
      +
      + + + + + + + + + + + +
      +Anterior??????
      4. Traduzindo Documenta????o??Principal??
      +
      + displayFooter('$Date$'); ?> + Index: index.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/index.php,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- index.php 29 Nov 2007 01:47:32 -0000 1.17 +++ index.php 19 Mar 2008 13:45:38 -0000 1.18 @@ -1,3 +1,13 @@ + + + +Guia R??pido de Tradu????o + + + + + + -
      Guia R??pido de Tradu????o
      ??????Pr??xima

      Guia R??pido de Tradu????o

      Manuel Ospina

      Editado por

      Paul W. Frields

      Editado por

      Noriko Mizumoto

      Hugo Cisneiros

      Francesco Tombolini

      Andrew Martynov

      Jos?? Pires

      Bart Courveur

      Dimitris Glezos

      Damien Durand

      Guillermo Gomez

      Diego B??rigo Zacar??o

      Version 0.3.9 (2007-11-14)

      Copyright ?? 2005, 2006, 2007 Red Hat, Inc. e outros

      1. Introdu????o
      2. Contas e Inscri????es
      2.1. Subscrevendo na Lista de Discuss??o
      2.2. Cr! iando uma chave SSH
      2.3. Criando uma chave GPG
      2.4. Aplicando para uma Conta
      2.5. Assinando o CLA
      2.6. Entre no Grupo cvsl10n
      2.7. Testando Seu Acesso
      2.8. Criando uma Conta na Wiki
      2.9. Apresenta????o
      2.10. Crie uma conta no Bugzilla
      2.11. Checklist
      < span class="section">3. Traduzindo Programas
      3.1. Estrutura de Arquivos
      3.2. Obtendo e Traduzindo M??dulos
      3.3. Enviando M??dulos
      3.4. Adicionando um Novo Arquivo .po
      3.5. Verifica????o Ortogr??fica
      4. Traduzindo Documenta????o
      4.1. Iniciando
      4.2. Criando Arquivos Comuns
      4.3. Usando Aplica????es de Tradu????o
      4.4. O que Traduzir?
      ??ndice Remissivo

      1. Introdu????o

      Esse guia fornece instru????es r??pidas, simples e passo a passo para traduzir programas e documentos do Projeto Fedora. Se voc?? est?? interessado em entender melhor o processo de tradu????o, veja o Guia de Tradu????o ou o manual da ferramenta espec??fica de tradu????o.

      ??????Pr??xima
      ??????2. Contas e Inscri????es
      + +
      + + + + + + + +
      Guia R??pido de Tradu????o
      ??????Pr??xima +
      +
      +
      +
      +
      +
      +

      Guia R??pido de Tradu????o

      +
      +

      +Manuel Ospina +

      +
      +

      Editado por

      +

      +Paul W. Frields +

      +
      +
      +

      Editado por

      +

      +Noriko Mizumoto +

      +
      +
      +

      Editado por

      +

      +Dimitris Glezos +

      +
      +
      +

      +Hugo Cisneiros +

      +

      +Francesco Tombolini +

      +

      +Andrew Martynov +

      +

      +Jos?? Pires +

      +

      +Bart Courveur +

      +

      +Damien Durand +

      +

      +Guillermo Gomez +

      +

      +Diego B??rigo Zacar??o +

      +

      Version 0.4.1 (2008-03-19)

      +

      Copyright ?? 2005, 2006, 2007 Red Hat, Inc. e outros

      + + +
      +
      +
      +
      +
      1. Introdu????o
      +
      2. Contas e Inscri????es
      +
      +
      2.1. Subscrevendo na Lista de Discuss??o
      +
      2.2. Criando uma chave SSH
      +
      2.3. Criando uma chave GPG
      +
      2.4. Aplicando para uma Conta
      +
      2.5. Assinando o CLA
      +
      2.6. Entre no Grupo cvsl10n
      +
      2.7. Testando Seu Acesso
      +
      2.8. Criando uma Conta na Wiki
      +
      2.9. Apresenta????o
      +
      2.10. Crie uma conta no Bugzilla
      +
      2.11. Checklist
      +
      +
      3. Traduzindo Programas
      +
      +
      3.1. Estrutura de Arquivos
      +
      3.2. Obtendo e Traduzindo M??dulos
      +
      3.3. Enviando M??dulos
      +
      3.4. Adicionando um Novo Arquivo .po
      +
      3.5. Verifica????o Ortogr??fica
      +
      +
      4. Traduzindo Documenta????o
      +
      +
      4.1. Iniciando
      +
      4.2. Criando Arquivos Comuns
      +
      4.3. Usando Aplica????es de Tradu????o
      +
      4.4. O que Traduzir?
      +
      +
      ??ndice Remissivo
      +
      +
      +

      1. Introdu????o

      +

      Esse guia fornece instru????es r??pidas, simples e passo a passo para traduzir programas e documentos do Projeto Fedora. Se voc?? est?? interessado em entender melhor o processo de tradu????o, veja o Guia de Tradu????o ou o manual da ferramenta espec??fica de tradu????o.

      +
      +
      +
      +
      + + + + + + + + + + + +
      ??????Pr??xima +
      ??????2. Contas e Inscri????es
      +
      + displayFooter('$Date$'); ?> + Index: legalnotice-opl.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/legalnotice-opl.php,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- legalnotice-opl.php 29 Nov 2007 01:47:32 -0000 1.1 +++ legalnotice-opl.php 19 Mar 2008 13:45:38 -0000 1.2 @@ -1,3 +1,10 @@ + + + +Nota Legal + + + -

      +

      +

      Permission is granted to copy, distribute, and/or modify this document under the terms of the Open Publication Licence, Version 1.0, or any later version. The terms of the OPL are set out below. -

      1. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED - VERSIONS

        +

        +
        +
          +
        1. +

          +REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED + VERSIONS

          +

          Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction. -

          +

          +

          Proper form for an incorporation by reference is as follows: -

          +

          +

          Copyright (c) <year> by <author's name or designee>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at http://www.opencontent.org/openpub/). -

          +

          +

          The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see section VI). Commercial redistribution of Open @@ -37,100 +54,149 @@ surfaces of the book the original publisher's name shall be as large as the title of the work and cited as possessive with respect to the title. -

        2. COPYRIGHT

          +

          +
          3. +
        3. +

          +COPYRIGHT

          +

          The copyright to each Open Publication is owned by its author(s) or designee. -

        4. SCOPE OF LICENSE

          +

          +
          5. +
        5. +

          +SCOPE OF LICENSE

          +

          The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document. -

          +

          +

          Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice. -

          +

          +

          SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force. -

          +

          +

          NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement. -

        6. REQUIREMENTS ON MODIFIED WORKS

          +

          +
          7. +
        7. +

          +REQUIREMENTS ON MODIFIED WORKS

          +

          All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements: -

          1. +

            +
              +

            1. The modified version must be labeled as such. -

            2. +

              3. +

            3. The person making the modifications must be identified and the modifications dated. -

            4. +

              5. +

            5. Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices. -

            6. +

              7. +

            7. The location of the original unmodified document must be identified. -

            8. +

              9. +

            9. The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. -

          2. GOOD-PRACTICE RECOMMENDATIONS

            +

            3. +
          +
          8. +
        8. +

          +GOOD-PRACTICE RECOMMENDATIONS

          +

          In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that: -

          1. +

            +
              +

            1. If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document. -

            2. +

              3. +

            3. All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document. -

            4. +

              5. +

            5. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). -

          2. LICENSE OPTIONS

            +

            3. +
          +
          9. +
        9. +

          +LICENSE OPTIONS

          +

          The author(s) and/or publisher of an Open Publication-licensed document may elect certain options by appending language to the reference to or copy of the license. These options are considered part of the license instance and must be included with the license (or its incorporation by reference) in derived works. -

          +

          +

          A. To prohibit distribution of substantively modified versions without the explicit permission of the author(s). "Substantive modification" is defined as a change to the semantic content of the document, and excludes mere changes in format or typographical corrections. -

          +

          +

          To accomplish this, add the phrase 'Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.' to the license reference or copy. -

          +

          +

          B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. -

          +

          +

          To accomplish this, add the phrase 'Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder.' to the license reference or copy. -

      +

      +
      7. +
    + + displayFooter('$Date$'); ?> + Index: rv-revhistory.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/rv-revhistory.php,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- rv-revhistory.php 29 Nov 2007 01:47:32 -0000 1.17 +++ rv-revhistory.php 19 Mar 2008 13:45:38 -0000 1.18 @@ -1,3 +1,10 @@ + + + +Hist??rico de Revis??es + + + -
    +
    Hist??rico de Revis??es
    Revis??o 0.3.92007-11-14PWF
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Hist??rico de Revis??es
    Revis??o 0.4.12008-03-19NM
    +

    + Foram substitu??dos os links na se????o 3.2 +

    +
    Revis??o 0.42008-03-03DG
    +

    + Foram removidas as referencias para i18n.redhat.com (elvis) +

    +
    Revis??o 0.3.9.22008-02-18PWF
    +

    + Consertado a URL de chave GPG +

    +
    Revis??o 0.3.9.12007-12-23PWF
    +

    + Reparar links para o sistema Transifex +

    +
    Revis??o 0.3.92007-11-14PWF

    Edi????o para mudan??as de estilo, gram??tica e esclarecimentos

    -
    Revis??o 0.3.8.22007-09-28NM
    +
    Revis??o 0.3.8.22007-09-28NM

    Todos os cap??tulos modificados e atualizados para refletir as informa????es mais recentes incluindo uso de transifex, movido reposit??rio etc.

    -
    Revis??o 0.3.8.12007-09-04DZ
    +
    Revis??o 0.3.8.12007-09-04DZ

    Adi????o de informa????es sobre uso de uma chave SSH existente

    -
    Revis??o 0.3.82007-08-23NM
    +
    Revis??o 0.3.82007-08-23NM

    Arquivo principal quebrado em m??ltiplos arquivos baseados nos cap??tulos

    -
    Revis??o 0.3.7.52007-07-29PWF
    +
    Revis??o 0.3.7.52007-07-29PWF

    Adi????o de informa????o sobre LINGUAS a remo????o de avisos desnecess??rios

    -
    Revis??o 0.3.7.42007-07-28PWF
    +
    Revis??o 0.3.7.42007-07-28PWF

    Adi????o de informa????es sobre as ??rvores de diret??rios dos m??dulos e mudan??as de teste

    -
    Revis??o 0.3.7.32007-07-06PWF
    +
    Revis??o 0.3.7.32007-07-06PWF

    Criando aviso para mudan??as manuais em arquivos POT

    -
    Revis??o 0.3.7.22007-05-29MO
    +
    Revis??o 0.3.7.22007-05-29MO

    Corre????o de detalhes de membros do grupo CVS; encurtar lista de copyright

    -
    Revis??o 0.3.7.12007-04-03PWF
    +
    Revis??o 0.3.7.12007-04-03PWF

    Gerara????o de novo POT e PO mantendo entidades gerais

    -
    Revis??o 0.3.72006-10-14PWF
    +
    Revis??o 0.3.72006-10-14PWF

    Corre????o de URL errada (#209900)

    -
    Revis??o 0.3.62006-09-20MO
    +
    Revis??o 0.3.62006-09-20MO

    Bugs corrigidos (#198726, #204266, #205167)

    -
    Revis??o 0.3.52006-08-14PWF
    +
    Revis??o 0.3.52006-08-14PWF

    Passo editorial, revis??o para corresponder a uma ordem apropriada.

    -
    Revis??o 0.3.42006-08-10MO
    +
    Revis??o 0.3.42006-08-10MO

    Informa????es adicionais sobre inscri????o no Projeto Docs e GPG.

    -
    Revis??o 0.3.32006-08-06PWF
    +
    Revis??o 0.3.32006-08-06PWF

    Passo de remo????o da tradu????o do rpm-info, dado que este agora faz parte do POT do documento

    -
    Revis??o 0.3.22006-07-03PWF
    +
    Revis??o 0.3.22006-07-03PWF

    Corre????o do procedimento de tradu????o do documento para incluir as tradu????es de outros arquivos comuns

    -
    Revis??o 0.3.12006-05-28PWF
    +
    Revis??o 0.3.12006-05-28PWF

    Adi????o de informa????es sobre as entidades comuns e adivert??ncia para locais desativados

    -
    Revis??o 0.32006-05-27PWF
    +
    Revis??o 0.32006-05-27PWF

    Corre????o do guia de procedimentos e inclus??o das entidades espec??ficas do documento (document-specific)

    -
    Revis??o 0.2.2.22006-02-13PWF
    +
    Revis??o 0.2.2.22006-02-13PWF

    Mudan??a para o DocBook XML 4.4 e uso do XInclude

    -
    Revis??o 0.2.2.12006-02-02PWF
    +
    Revis??o 0.2.2.12006-02-02PWF

    Corre????o ortogr??fica (#179717)

    -
    Revis??o 0.2.22006-02-01PWF
    +
    Revis??o 0.2.22006-02-01PWF

    Adi????o da entidade para reportar de erros

    -
    Revis??o 0.2.12006-01-30PWF
    +
    Revis??o 0.2.12006-01-30PWF

    Corre????o de hostname errado

    -
    Revis??o 0.22006-01-25PWF
    +
    Revis??o 0.22006-01-25PWF

    Edi????o adicional do estilo, divis??o dos procedimentos em se????es mais leg??veis

    -
    Revis??o 0.1Fri Jan 20 2006PWF
    +
    Revis??o 0.1Fri Jan 20 2006PWF

    Primeira ronda de edi????o.

    -
    Revis??o 0.0.1Wed Jan 18 2006MO
    +
    Revis??o 0.0.1Wed Jan 18 2006MO

    Primeiro rascunho

    -
    +
    displayFooter('$Date$'); ?> + Index: sn_accounts.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/sn_accounts.php,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- sn_accounts.php 29 Nov 2007 01:47:32 -0000 1.17 +++ sn_accounts.php 19 Mar 2008 13:45:38 -0000 1.18 @@ -1,3 +1,15 @@ + + + +2. Contas e Inscri????es + + + + + + + + -
    2. Contas e Inscri????es
    Anterior??????Pr??xima

    2. Contas e Inscri????es

    Para se tornar um Tradutor do Fedora, voc?? deve criar contas e subscrever-se como descrito neste cap??tulo. Se voc?? tem d??vidas, poste as mesmas em fedora-trans-list, ou pe??a ajuda via Internet Relay Chat, ou IRC em irc.freenode.org no canal #fedora-l10n.

    2.1. Subscrevendo na Lista de Discuss??o

    1. Visite https://listman.redhat.com/mailman/listinfo/fedora-trans-list/ e subscreva-se na principal lista de discuss??o sobre tradu????o.

    2. Espere pelo e-mail de confirma????o que cont??m um link para confirmar sua subscri????o. Clique no link para confirm??-la.

    3. Verifique em http://fedoraproject.org/wiki/L10N/Teams/ se existe uma lista de discuss??o especial para seu idioma. Se existir, subscreva-se nesta lista tamb??m.

    2.2. Criando uma chave SSH

    Se voc?? j?? possui uma chave! SSH, voc?? pode us??-la para trabalhos no Fedora. Neste caso,! prossig a no Passo 2 no procedimento seguinte. Se voc?? n??o tem uma chave SSH ainda, inicie na primeira etapa abaixo:

    1. Digite o seguinte comando:

      ssh-keygen -t dsa

      Aceite a localiza????o padr??o (~/.ssh/id_dsa) e entre com um frase senha.

      [Cuidado]Lembre-se de sua Frase Senha!

      Voc?? ir?? precisar de sua frase senha para acessar o reposit??rio CVS. Ela n??o pode ser recuperada se voc?? esquec??-la.

    2. Altere as permiss??es da sua chave e diret??rio .ssh:

      chmod 700 ~/.ssh
+
+
      
+
+
+
+
+
+
+
+
      2. Contas e Inscri????es
      
+Anterior??????Pr??xima
+
      
+
      
+
      
+
      
+
      2. Contas e Inscri????es
      
+
      Para se tornar um Tradutor do Fedora, voc?? deve criar contas e subscrever-se como descrito neste cap??tulo. Se voc?? tem d??vidas, poste as mesmas em fedora-trans-list, ou pe??a ajuda via Internet Relay Chat, ou IRC em  irc.freenode.org no canal #fedora-l10n.
      
+
      
+
      2.1. Subscrevendo na Lista de Discuss??o 
      
+
        
+
      1. Visite https://listman.redhat.com/mailman/listinfo/fedora-trans-list/ e subscreva-se na principal lista de discuss??o sobre tradu????o.
        2. 
+
      2. Espere pelo e-mail de confirma????o que cont??m um link para confirmar sua subscri????o. Clique no link para confirm??-la.
        3. 
+
      3. Verifique em http://fedoraproject.org/wiki/L10N/Teams/ se existe uma lista de discuss??o especial para seu idioma. Se existir, subscreva-se nesta lista tamb??m.
        4. 
+
      
+
      
+
      
+
      2.2. Criando uma chave SSH
      
+
      Se voc?? j?? possui uma chave SSH, voc?? pode us??-la para trabalhos no Fedora. Neste caso, prossiga no Passo 2 no procedimento seguinte. Se voc?? n??o tem uma chave SSH ainda, inicie na primeira etapa abaixo:
      
+
        
+
      1. 
+
        Digite o seguinte comando:
        
+
        ssh-keygen -t dsa
        
+
        Aceite a localiza????o padr??o (~/.ssh/id_dsa) e entre com um frase senha.
        
+
        
+
+
+
+
+
+
        [Cuidado]Lembre-se de sua Frase Senha!
        Voc?? ir?? precisar de sua frase senha para acessar o reposit??rio CVS. Ela n??o pode ser recuperada se voc?? esquec??-la.
        
+
        2. 
+
      2. 
+
        Altere as permiss??es da sua chave e diret??rio .ssh:
        
+
        chmod 700 ~/.ssh
 chmod 600 ~/.ssh/id_dsa
-chmod 644 ~/.ssh/id_dsa.pub
      3. Copie e cole a chave SSH no espa??o fornecido para completar a aplica????o da conta.
      2.3. Criando uma chave GPG
      1. Gere uma chave digitando em uma linha de comando:
        gpg --gen-key
        Uma s??rie de ??tens ir??o gui??-lo por todo o processo. Os valores padr??es devem sersuficientes na maioria dos casos. Lembre-se de escolher uma boa senha.
        [Dica]Escolhendo uma Boa Senha
        Uma boa senha:
        • consiste de letras mai??sculas e min??sculas, n??meros, pontua????es e outros caracteres
        • n??o inclui quaisquer palavras ou nomes, com ou sem substitui????es
        • n??o ?? a mesma senha utilizada em outros sistemas
      2. No texto resultante, encontre sua ID da chave que se assemelha com "pub 1024D/1B2AFA1C". Sua ID ?? uma palavra de 8 caracteres depois da barra (/). No exemplo anterior, a ID da chave GPG ?? 1B2AFA1C. Anote sua ID da chave.
      3. Exporte sua chave p??blica para um servidor p??blico, a fim de que outros possam encontr??- la, com o seguinte comando, substituindo sua ID da chave:
        gpg --keyserver pgp.mit.edu --send-keys GPGKEYID
      2.4. Aplicando para uma Conta
      1. Para obter uma conta do Fedora, visite primeiro  https://admin.fedoraproject.org/accounts/ e selecione a op????o Apply for a new account (Pedir uma nova conta). 
      2. Preencha o formul??rio e escolha uma senha para sua conta Fedora. Entre com as informa????es de sua ID da chave GPG e chave SSH no formul??rio. No campo Comments (Coment??rios), escreva a l??ngua em que voc?? planeja trabalhar.
      2.5. Assinando o CLA
      Voc?? deve completar o "Contributors License Agreement", ou CLA.
      1. Visite https://admin.fedoraproject.org/accounts/send-cla.cgi. Autentique usando seu nome de usu??rio e senha do procedimento anterior.
      2. Espere at?? receber um e-mail com um anexo. O anexo ?? um acordo que voc?? pode assinar ou devolver. Salve o anexo na sua ??rea de Trabalho.
      3. Clique duas vezes no arquivo em sua ??rea de Trabalho para abri-lo em um editor de texto. Adicione a frase "I agree" e seu nome completo.
      4. Assine digitalmente o arquivo de texto usando a sua chave GPG com o seguinte comando, fornecendo a sua senha quando solicitado:
        gpg -a --sign fedora-icla-{username}.txt
        Agora existe um novo arquivo na sua ??rea de Trabalho com a extens??o .asc. Este arquivo ?? a vers??o assinada do CLA.
      5. Abra seu cliente de e-mail n!
 ovamente e responda o e-mail do CLA. Anexe o arquivo assinado,!
  que ter
mina com .asc e envie o e-mail.
      2.6. Entre no Grupo cvsl10n
      1. Visite https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1. Selecione a op????o Add new membership (Adicionar novo membro) no bot??o da p??gina. No campo Groupname, digite cvsl10n e selecione Add (Adicionar). 
      2. Um administrador ?? notificado da sua requisi????o e se oferece para patrocinar/coordenar voc??. Isto pode levar uma hora ou apena alguns minutos!
 .
      [Cuidado]Cuidado
      Os passos restantes ajudam voc?? a testar seu acesso e lhe concedem privil??gios em toda a Infra-estrutura do Fedora que voc?? poder?? precisar num futuro pr??ximo. Mandedores e pessoas que iniciam a tradu????o para um novo idioma deveriam segui-los. Embora eles sejam opcionais para os tradutores, todos s??o incentivados a segui-los.
      [Importante]Importante
      Alguns m??dulos do Fedora ainda est??o hospedados no s!
 istema <
code class="systemitem">i18n.redhat.com, que n??o ?? habilitado a trabalhar com o grupo cvsl10n. Para traduzir m??dulos hospedados l??, por favor visite http://i18n.redhat.com/cgi-bin/i18n-signup. Est?? advert??ncia pode se tornar obsoleta em breve.
      2.7. Testando Seu Acesso
      1. Instale o pacote cvs, caso ainda n??o esteja instalado, com o seguinte comando:
        su -c 'yum install cvs'
      2. Baixe alguns arquivos PO com o seguinte comando, substituindo seu nome de usu??rio e fornecendo sua frase senha da chave SSH quando solicitado:
        export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/l10n
+chmod 644 ~/.ssh/id_dsa.pub
        
+
        3. 
+
      3. Copie e cole a chave SSH no espa??o fornecido para completar a aplica????o da conta.
        4. 
+
      
+
      
+
      
+
      2.3. Criando uma chave GPG
      
+
        
+
      1. 
+
        Gere uma chave digitando em uma linha de comando:
        
+
        gpg --gen-key
        
+
        Uma s??rie de ??tens ir??o gui??-lo por todo o processo. Os valores padr??es devem sersuficientes na maioria dos casos. Lembre-se de escolher uma boa senha.
        
+
        
+
+
+
+
+
+
        [Dica]Escolhendo uma Boa Senha
        
+
        Uma boa senha:
        
+
          
+
        • consiste de letras mai??sculas e min??sculas, n??meros, pontua????es e outros caracteres
          • 
+
        • n??o inclui quaisquer palavras ou nomes, com ou sem substitui????es
          • 
+
        • n??o ?? a mesma senha utilizada em outros sistemas
          • 
+
        
+
        
+
        2. 
+
      2. No texto resultante, encontre sua ID da chave que se assemelha com "pub 1024D/1B2AFA1C". Sua ID ?? uma palavra de 8 caracteres depois da barra (/). No exemplo anterior, a ID da chave GPG ?? 1B2AFA1C. Anote sua ID da chave.
        3. 
+
      3. 
+
        Exporte sua chave p??blica para um servidor p??blico, a fim de que outros possam encontr??- la, com o seguinte comando, substituindo sua ID da chave:
        
+
        gpg --keyserver subkeys.pgp.net --send-keys GPGKEYID
        
+
        4. 
+
      
+
      
+
      
+
      2.4. Aplicando para uma Conta
      
+
        
+
      1. Para obter uma conta do Fedora, visite primeiro  https://admin.fedoraproject.org/accounts/ e selecione a op????o Apply for a new account (Pedir uma nova conta). 
        2. 
+
      2. Preencha o formul??rio e escolha uma senha para sua conta Fedora. Entre com as informa????es de sua ID da chave GPG e chave SSH no formul??rio. No campo Comments (Coment??rios), escreva a l??ngua em que voc?? planeja trabalhar.
        3. 
+
      
+
      
+
      
+
      2.5. Assinando o CLA
      
+
      Voc?? deve completar o "Contributors License Agreement", ou CLA.
      
+
        
+
      1. Visite https://admin.fedoraproject.org/accounts/send-cla.cgi. Autentique usando seu nome de usu??rio e senha do procedimento anterior.
        2. 
+
      2. Espere at?? receber um e-mail com um anexo. O anexo ?? um acordo que voc?? pode assinar ou devolver. Salve o anexo na sua ??rea de Trabalho.
        3. 
+
      3. Clique duas vezes no arquivo em sua ??rea de Trabalho para abri-lo em um editor de texto. Adicione a frase "I agree" e seu nome completo.
        4. 
+
      4. 
+
        Assine digitalmente o arquivo de texto usando a sua chave GPG com o seguinte comando, fornecendo a sua senha quando solicitado:
        
+
        gpg -a --sign fedora-icla-{username}.txt
        
+
        Agora existe um novo arquivo na sua ??rea de Trabalho com a extens??o .asc. Este arquivo ?? a vers??o assinada do CLA.
        
+
        5. 
+
      5. Abra seu cliente de e-mail novamente e responda o e-mail do CLA. Anexe o arquivo assinado, que termina com .asc e envie o e-mail.
        6. 
+
      
+
      
+
      
+
      2.6. Entre no Grupo cvsl10n
+
      
+
        
+
      1. Visite https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1. Selecione a op????o Add new membership (Adicionar novo membro) no bot??o da p??gina. No campo Groupname, digite cvsl10n e selecione Add (Adicionar). 
        2. 
+
      2. Um administrador ?? notificado da sua requisi????o e se oferece para patrocinar/coordenar voc??. Isto pode levar uma hora ou apena alguns minutos.
        3. 
+
      
+
      
+
+
+
+
+
+
      [Cuidado]Cuidado
      Os passos restantes ajudam voc?? a testar seu acesso e lhe concedem privil??gios em toda a Infra-estrutura do Fedora que voc?? poder?? precisar num futuro pr??ximo. Mandedores e pessoas que iniciam a tradu????o para um novo idioma deveriam segui-los. Embora eles sejam opcionais para os tradutores, todos s??o incentivados a segui-los.
      
+
      
+
      
+
      2.7. Testando Seu Acesso
      
+
        
+
      1. 
+
        Instale o pacote cvs, caso ainda n??o esteja instalado, com o seguinte comando:
        
+
        su -c 'yum install cvs'
        
+
        2. 
+
      2. 
+
        Baixe alguns arquivos PO com o seguinte comando, substituindo seu nome de usu??rio e fornecendo sua frase senha da chave SSH quando solicitado:
        
+
        export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/l10n
 cvs co web 
-ls web/flpweb/po
      2.8. Criando uma Conta na Wiki
      1. Visite http://fedoraproject.org/wiki/UserPreferences. Para seu nome se usu??rio, escolha algo do g??nero como 'NomeSobrenome' e selecione Create Profile (Criar Perfil).
      2. Um usu??rio atual da wiki pode dar a voc?? acesso de edi????o na mesma. Contate algu??m do Grupo de Edi????o em http://fedoraproject.org/wiki/EditGroup/, ou adicione seu nome no EditGroupQueue em http://fedoraproject.org/wiki/EditGroupQueue/,!
  desta maneira algu??m ir?? adicionar voc?? rapidamente no grupo de edi????o.
      3. Se voc?? est?? iniciando um novo idioma ou gostaria de se tornar o mantedor de um, adicione suas informa????es na p??gina L10N/Teams em http://fedoraproject.org/wiki/L10N/Teams/.
      2.9. Apresenta????o
      1. Uma vez que voc?? tenha acesso de edi????o na wiki, crie uma p??gina pessoal numa URL tipo: http://fedoraproject.org/wiki/NomeSobrenome/. Isto ?? muito ??til para os colaboradores do Fedora se conhecerem e contatarem uns aos outros.
      2. Poste uma pequena apresenta????o sua http://f!
 edorapro
ject.org/wiki/L10N/Join/SelfIntroduction/ na lista fedora-trans-list e na lista de sua equipe local.
      2.10. Crie uma conta no Bugzilla
      Visite https://bugzilla.redhat.com/bugzilla/createaccount.cgi/ para criar um conta Bugzilla.
      2.11. Checklist
      Agora voc?? deveria ter o seguinte:
      • Subscrevido-se na lista fedora-trans-list e na lista de discuss??o espec??fica de sua l??ngua, caso exista uma
      • Uma chave SSH
      • Uma chave GPG
      • Uma conta Fedora
      • Membro do !
 grupo cvsl10n
      • Uma conta na wiki
      • Seu idioma e time de tradu????o aparece em http://fedoraproject.org/wiki/L10N/Teams/
      • Uma conta no Bugzilla
      • Uma p??gina pessoal na wiki
      • Uma auto apresenta????o (self-introduction) enviada para a lista de discuss??o
      Sente-se e aprecie a sua realiza????o. Voc?? agora ?? um membro totalmente reconhecido da comunidade Fedora, capaz de assinar e-mails e documentos digitalmente, enviar contribui????es para nosso CVS, publicar conte??do na wiki, relatar bugs, acompanhar discuss??es dos nossos grupos e participar de outros times do Fedora.
      Anterior??????Pr??xima
      Guia R??pido de Tradu????o??Principal??3. Traduzindo Programas
      
+ls web/flpweb/po
      +
      3. +
    +
    +
    +

    2.8. Criando uma Conta na Wiki

    +
      +

    1. Visite http://fedoraproject.org/wiki/UserPreferences. Para seu nome se usu??rio, escolha algo do g??nero como 'NomeSobrenome' e selecione Create Profile (Criar Perfil).

      2. +

    2. Um usu??rio atual da wiki pode dar a voc?? acesso de edi????o na mesma. Contate algu??m do Grupo de Edi????o em http://fedoraproject.org/wiki/EditGroup/, ou adicione seu nome no EditGroupQueue em http://fedoraproject.org/wiki/EditGroupQueue/, desta maneira algu??m ir?? adicionar voc?? rapidamente no grupo de edi????o.

      3. +

    3. Se voc?? est?? iniciando um novo idioma ou gostaria de se tornar o mantedor de um, adicione suas informa????es na p??gina L10N/Teams em http://fedoraproject.org/wiki/L10N/Teams/.

      4. +
    +
    +
    +

    2.9. Apresenta????o

    +
      +

    1. Uma vez que voc?? tenha acesso de edi????o na wiki, crie uma p??gina pessoal numa URL tipo: http://fedoraproject.org/wiki/NomeSobrenome/. Isto ?? muito ??til para os colaboradores do Fedora se conhecerem e contatarem uns aos outros.

      2. +

    2. Poste uma pequena apresenta????o sua http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/ na lista fedora-trans-list e na lista de sua equipe local.

      3. +
    +
    +
    +

    2.10. Crie uma conta no Bugzilla

    +

    Visite https://bugzilla.redhat.com/bugzilla/createaccount.cgi/ para criar um conta Bugzilla.

    +
    +
    +

    2.11. Checklist

    +

    Agora voc?? deveria ter o seguinte:

    +
      +

    • Subscrevido-se na lista fedora-trans-list e na lista de discuss??o espec??fica de sua l??ngua, caso exista uma

      • +

    • Uma chave SSH

      • +

    • Uma chave GPG

      • +

    • Uma conta Fedora

      • +

    • Membro do grupo cvsl10n

      • +

    • Uma conta na wiki

      • +

    • Seu idioma e time de tradu????o aparece em http://fedoraproject.org/wiki/L10N/Teams/

      • +

    • Uma conta no Bugzilla

      • +

    • Uma p??gina pessoal na wiki

      • +

    • Uma auto apresenta????o (self-introduction) enviada para a lista de discuss??o

      • +
    +

    Sente-se e aprecie a sua realiza????o. Voc?? agora ?? um membro totalmente reconhecido da comunidade Fedora, capaz de assinar e-mails e documentos digitalmente, enviar contribui????es para nosso CVS, publicar conte??do na wiki, relatar bugs, acompanhar discuss??es dos nossos grupos e participar de outros times do Fedora.

    +
    + +
    +
    + + + + + + + + + + + +
    +Anterior??????Pr??xima +
    Guia R??pido de Tradu????o??Principal??3. Traduzindo Programas
    +
    + displayFooter('$Date$'); ?> + Index: sn_translating_docs.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/sn_translating_docs.php,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- sn_translating_docs.php 29 Nov 2007 01:47:32 -0000 1.17 +++ sn_translating_docs.php 19 Mar 2008 13:45:38 -0000 1.18 @@ -1,3 +1,15 @@ + + + +4. Traduzindo Documenta????o + + + + + + + + -
    4. Traduzindo Documenta????o
    Anterior??????Pr??xima

    4. Traduzindo Documenta????o

    Para traduzir os documentos do Fedora, torne-se um membro do grupo cvsl10n. Para mais informa????es sobre a conta e subscri????es, consulte a Se????o??2, ???Contas e Inscri????es???.

    Para traduzir a documenta????o, voc?? precisa de um sistema Fedora 5 ou posterior com os seguintes pacote! s instalados:

    • gnome-doc-utils

    • xmlto

    • make

    O pacote gnome-doc-utils fornece o comando xml2po e n??o requer que voc?? instale o ambiente de desktop GNOME. Os pacotes xmlto e make cont??m as ferramentas necess??rias para testar a constru????o de documentos e tradu????es.

    Para instalar esses pacotes, use o seguinte comando:

    su -c 'yum install gnome-doc-utils xmlto make'

    4.1. Iniciando

    A documenta????o do Fedora est?? armazenada em um reposit??rio CVS dentro do diret??rio docs/. Para listar os m??dulos dispon??veis, exec! ute os s eguintes comandos:

    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
-cvs co -c

    Para baixar um m??dulo para traduzir, liste os m??dulos atuais do reposit??rio e baixe o m??dulo que tem interesse. Voc?? tamb??m deve baixar o m??dulo docs-common para trabalhar com alguns m??dulos.

    +
+
    
+
+
+
+
+
+
+
+
    4. Traduzindo Documenta????o
    
+Anterior??????Pr??xima
+
    
+
    
+
    
+
    
+
    4. Traduzindo Documenta????o
    
+
    Para traduzir os documentos do Fedora, torne-se um membro do grupo cvsl10n. Para mais informa????es sobre a conta e subscri????es, consulte a Se????o??2, ???Contas e Inscri????es???.
    
+
    Para traduzir a documenta????o, voc?? precisa de um sistema Fedora 5 ou posterior com os seguintes pacotes instalados:
    
+
      
+
    • gnome-doc-utils
      • 
+
    • xmlto
      • 
+
    • make
      • 
+
    
+
    O pacote gnome-doc-utils fornece o comando xml2po e n??o requer que voc?? instale o ambiente de desktop GNOME. Os pacotes xmlto e make cont??m as ferramentas necess??rias para testar a constru????o de documentos e tradu????es.
    
+
    Para instalar esses pacotes, use o seguinte comando:
    
+
    su -c 'yum install gnome-doc-utils xmlto make'
    
+
    
+
    4.1. Iniciando
    
+
    A documenta????o do Fedora est?? armazenada em um reposit??rio CVS dentro do diret??rio docs/. Para listar os m??dulos dispon??veis, execute os seguintes comandos:
    
+
    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
+cvs co -c
    
+
    Para baixar um m??dulo para traduzir, liste os m??dulos atuais do reposit??rio e baixe o m??dulo que tem interesse. Voc?? tamb??m deve baixar o m??dulo docs-common para trabalhar com alguns m??dulos.
    
+
           cvs co release-notes/
-    
    Alguns m??dulos s??o release specific, ou seja, eles possuem uma branch, ou subdiret??rio, para cada vers??o do Fedora:
    ls release-notes/
-CVS  F-7  FC-5  FC-6  FC3  FC4  devel
    A ??rvore de diret??rio devel/ ?? usada para vers??es futuras do Fedora. Freq??entemente os tradutores trabalham sobre ela e as mudan??as s??o portadas para as a??vores de diret??rio anteriores conforme necess??rio.
    4.2. Criando Arquivos Comuns
    Se voc?? est?? criando a primeira tradu????o local para um documento, voc?? deve primeiramente traduzir os arquivos comuns de entidades. As entidades comuns est??o localizados em docs-common/common/.
    [Nota]Um exemplo de Local/Idioma ?? pt_BR
    Os exemplos seguintes usam o c??digo de local pt_BR. Substitua este c??digo nos comando pelo seu c??digo local, conforme necess??rio. 
    1. Leia o arquivo README.txt em docs-common/common/entities e siga as dire????es para criar novas entidades.
    2. Depois de ter criado as entidades comums para seu idioma e comitado os resultados para o CVS, crie os arquivos locais para as notas legais:
      cd docs-common/common/
+    
      
+
      Alguns m??dulos s??o release specific, ou seja, eles possuem uma branch, ou subdiret??rio, para cada vers??o do Fedora:
      
+
      ls release-notes/
+CVS  F-7  FC-5  FC-6  FC3  FC4  devel
      
+
      A ??rvore de diret??rio devel/ ?? usada para vers??es futuras do Fedora. Freq??entemente os tradutores trabalham sobre ela e as mudan??as s??o portadas para as a??vores de diret??rio anteriores conforme necess??rio.
      
+
    
+
    
+
    4.2. Criando Arquivos Comuns
    
+
    Se voc?? est?? criando a primeira tradu????o local para um documento, voc?? deve primeiramente traduzir os arquivos comuns de entidades. As entidades comuns est??o localizados em docs-common/common/.
    
+
    
+
+
+
+
+
+
    [Nota]Um exemplo de Local/Idioma ?? pt_BR
+
    Os exemplos seguintes usam o c??digo de local pt_BR. Substitua este c??digo nos comando pelo seu c??digo local, conforme necess??rio. 
    
+
      
+
    1. Leia o arquivo README.txt em docs-common/common/entities e siga as dire????es para criar novas entidades.
      2. 
+
    2. 
+
      Depois de ter criado as entidades comums para seu idioma e comitado os resultados para o CVS, crie os arquivos locais para as notas legais:
      
+
      cd docs-common/common/
 cp legalnotice-opl-en_US.xml legalnotice-opl-pt_BR.xml
 cp legalnotice-relnotes-en_US.xml legalnotice-relnotes-pt_BR.xml	
-
      [Importante]N??o Traduza o Aviso Legal
      Para assegurar que ?? legalmente equivalente em todos os locais, n??o traduza o OPL. 
    3. Depois disso, comite tamb??m os arquivos no CVS:
      cvs add legalnotice-*-pt_BR.xml
-cvs ci -m 'Added legal notices for pt_BR' legalnotice-*-pt_BR.xml
    4. Em seguida, construa a marca d'agua do rascunho (draft) para sua localiza????o na pasta docs-common/images/
      cd docs-common/images/
-cp watermark-en_US.svg watermark-pt_BR.svg
      Traduza os elementos textos do SVG. Ent??o adicione seu arquivo SVG local no Makefile, contrua o PNG e envie (commit) os resultados:
      make watermark-pt_BR.png
+
      
+
      
+
+
+
+
+
+
      [Importante]N??o Traduza o Aviso Legal
      Para assegurar que ?? legalmente equivalente em todos os locais, n??o traduza o OPL. 
      
+
      5. 
+
    5. 
+
      Depois disso, comite tamb??m os arquivos no CVS:
      
+
      cvs add legalnotice-*-pt_BR.xml
+cvs ci -m 'Added legal notices for pt_BR' legalnotice-*-pt_BR.xml
      
+
      6. 
+
    6. 
+
      Em seguida, construa a marca d'agua do rascunho (draft) para sua localiza????o na pasta docs-common/images/
      
+
      cd docs-common/images/
+cp watermark-en_US.svg watermark-pt_BR.svg
      
+
      Traduza os elementos textos do SVG. Ent??o adicione seu arquivo SVG local no Makefile, contrua o PNG e envie (commit) os resultados:
      
+
      make watermark-pt_BR.png
 cvs add watermark-pt_BR*
-cvs ci -m 'Added pt_BR images' Makefile watermark-pt_BR*
    [Importante]Erros de Constru????o
    Se voc?? n??o criar essas entradas comuns, a constru????o do seu documento pode falhar.
    4.3. Usando Aplica????es de Tradu????o
    O diret??rio .po cont??m os arquivos  .po usados para traduzir conte??do. Ele tamb??m cont?!
 ?m um arquivo .po, ou um template PO, o qual ?? usado para criar novos arquivos .po quando necess??rio.
    Se o diret??rio po/ n??o existir, voc?? pode cri??-lo e traduzir um arquivo de molde (template) com os seguintes comandos:
    mkdir po
+cvs ci -m 'Added pt_BR images' Makefile watermark-pt_BR*
    
+
+
    
+
    
+
+
+
+
+
+
    [Importante]Erros de Constru????o
    Se voc?? n??o criar essas entradas comuns, a constru????o do seu documento pode falhar.
    
+
    
+
    
+
    4.3. Usando Aplica????es de Tradu????o
    
+
    O diret??rio .po cont??m os arquivos  .po usados para traduzir conte??do. Ele tamb??m cont??m um arquivo .po, ou um template PO, o qual ?? usado para criar novos arquivos .po quando necess??rio.
    
+
    Se o diret??rio po/ n??o existir, voc?? pode cri??-lo e traduzir um arquivo de molde (template) com os seguintes comandos:
    
+
    mkdir po
 cvs add po/
 make pot
-
    [Cuidado]N??o Fa??a Mudan??as Manuais Nos Arquivos POT
    Autores e editores geram os arquivos POT a partir de arquivos XML fontes, que sobrescrevem qualquer mudan??a manual em um arquivo POT. Se voc?? encontrar um problema numa mensagem original de um arquivo POT, acesse o Bugzilla em https://bugzilla.redhat.com para reportar um bug contra o documento.
    Para trabalhar com um editor de .po assim como o KBabel ou o gtranslator, siga os seguintes passos:
    [Nota]Um exemplo de Local/Idioma ?? pt_BR
    Os exemplos seguintes usam o c??digo de local pt_BR. Substitua este c??digo nos comando pelo seu c??digo local, conforme necess??rio. 
    1. Mudan??a de Diret??rio
      Em um terminal, v?? ao diret??rio do documento que voc?? quer traduzir:
      cd ~/docs/example-tutorial
    2. Adicionar um Local na Lista
      Para adicionar seu local, voc?? deve lo!
 calizar e mudar a lista de locais apropriada. Alguns documento!
 s est??o
 usando o arquivo po/LINGUAS, como padronizados no projeto GNOME, para trilhar locais. Alguns documentos n??o foram atualizados para este padr??o ainda. Se voc?? achar o m??dulo que voc?? esta traduzindo n??o atualizado, notifique o Projeto de Documenta????o do Fedora ou reporte um bug usando o Bugzilla.
      Adicione o c??digo do seu idioma de tradu????o ?? lista no arquivo po/LINGUAS. Mantenha a lista em ordem alfab??tica.
    3. Crie um Arquivo PO
      Fa??a um novo arquivo .po para sua localidade:
      make po/pt_BR.po
    4. Traduzir as Frases
      Para traduzir o arquivo, use o mesmo aplicativo usado para traduzir programas:
      kbabel po/pt_BR.po
    5. Verificando a Integridade
      Antes de enviar suas mudan??as, verifique a integridade do XML com o seguinte comando. Isto garante a constru????o do documento sem erros para todos os usu??rios.
      make html-pt_BR
      Voc?? pode ler os arquivos HTML resultantes com um navegador Web.
      <
/table>
    6. Enviar as Tradu????es
      Quando voc?? tiver terminado sua tradu????o, envie o arquivo .po. Voc?? poder?? ver a percentagem de finaliza????o, ou outra mensagem ??til, na altura do envio.
      cvs ci -m 'Traduzindo... 400/10/126' po/pt_BR.po
      7. 4.4. O que Traduzir?
      Os mais importantes m??dulos/diret??rios de documenta????o para cada vers??o do Fedora s??o os seguintes:
      • docs-common/common/entities
      • release-notes/devel
      • homepage/devel
      • install-guide/devel
      • about-fedora/devel
      • readme/devel
      • readme-burning-isos/devel
      • readme-live-image/devel
      Para ver todos os documentos dispon??veis no reposit??rio de documenta????o, execute:
      export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
-cvs co -c
      [Importante]Sempre Teste Suas Tradu????es
      N??o passe para o pr??ximo passo ou submeta o arquivo at?? que voc?? teste seu trabalho nesta etapa. Modifica????es err??neas podem quebrar documentos para outros!
  usu??rios, editores e para aplica????es automatizadas.
      Anterior??????Pr??xima
      3. Traduzindo Programas??Principal????ndice Remissivo
      
+
    +
    + + + + + +
    [Cuidado]N??o Fa??a Mudan??as Manuais Nos Arquivos POT

    Autores e editores geram os arquivos POT a partir de arquivos XML fontes, que sobrescrevem qualquer mudan??a manual em um arquivo POT. Se voc?? encontrar um problema numa mensagem original de um arquivo POT, acesse o Bugzilla em https://bugzilla.redhat.com para reportar um bug contra o documento.

    +

    Para trabalhar com um editor de .po assim como o KBabel ou o gtranslator, siga os seguintes passos:

    +
    + + + + + +
    [Nota]Um exemplo de Local/Idioma ?? pt_BR +

    Os exemplos seguintes usam o c??digo de local pt_BR. Substitua este c??digo nos comando pelo seu c??digo local, conforme necess??rio.

    +
      +
    1. +

      Mudan??a de Diret??rio

      +

      Em um terminal, v?? ao diret??rio do documento que voc?? quer traduzir:

      +
      cd ~/docs/example-tutorial
      +
      2. +
    2. +

      Adicionar um Local na Lista

      +

      Para adicionar seu local, voc?? deve localizar e mudar a lista de locais apropriada. Alguns documentos est??o usando o arquivo po/LINGUAS, como padronizados no projeto GNOME, para trilhar locais. Alguns documentos n??o foram atualizados para este padr??o ainda. Se voc?? achar o m??dulo que voc?? esta traduzindo n??o atualizado, notifique o Projeto de Documenta????o do Fedora ou reporte um bug usando o Bugzilla.

      +

      Adicione o c??digo do seu idioma de tradu????o ?? lista no arquivo po/LINGUAS. Mantenha a lista em ordem alfab??tica.

      +
      3. +
    3. +

      Crie um Arquivo PO

      +

      Fa??a um novo arquivo .po para sua localidade:

      +
      make po/pt_BR.po
      +
      4. +
    4. +

      Traduzir as Frases

      +

      Para traduzir o arquivo, use o mesmo aplicativo usado para traduzir programas:

      +
      kbabel po/pt_BR.po
      +
      5. +
    5. +

      Verificando a Integridade

      +

      Antes de enviar suas mudan??as, verifique a integridade do XML com o seguinte comando. Isto garante a constru????o do documento sem erros para todos os usu??rios.

      +
      make html-pt_BR
      +

      Voc?? pode ler os arquivos HTML resultantes com um navegador Web.

      +
      + + + + + +
      [Importante]Sempre Teste Suas Tradu????es

      N??o passe para o pr??ximo passo ou submeta o arquivo at?? que voc?? teste seu trabalho nesta etapa. Modifica????es err??neas podem quebrar documentos para outros usu??rios, editores e para aplica????es automatizadas.

      +
      6. +
    6. +

      Enviar as Tradu????es

      +

      Quando voc?? tiver terminado sua tradu????o, envie o arquivo .po. Voc?? poder?? ver a percentagem de finaliza????o, ou outra mensagem ??til, na altura do envio.

      +
      cvs ci -m 'Traduzindo... 400/10/126' po/pt_BR.po
      +
      7. +
    +
    +
    +

    4.4. O que Traduzir?

    +

    Os mais importantes m??dulos/diret??rios de documenta????o para cada vers??o do Fedora s??o os seguintes:

    +
      +

    • docs-common/common/entities

      • +

    • release-notes/devel

      • +

    • homepage/devel

      • +

    • install-guide/devel

      • +

    • about-fedora/devel

      • +

    • readme/devel

      • +

    • readme-burning-isos/devel

      • +

    • readme-live-image/devel

      • +
    +

    Para ver todos os documentos dispon??veis no reposit??rio de documenta????o, execute:

    +
    export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
+cvs co -c
    +
    +
    +
    +
    + + + + + + + + + + + +
    +Anterior??????Pr??xima +
    3. Traduzindo Programas??Principal????ndice Remissivo
    +
    + displayFooter('$Date$'); ?> + Index: sn_translating_software.php =================================================================== RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/pt_BR/sn_translating_software.php,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- sn_translating_software.php 29 Nov 2007 01:47:32 -0000 1.17 +++ sn_translating_software.php 19 Mar 2008 13:45:38 -0000 1.18 @@ -1,3 +1,15 @@ + + + +3. Traduzindo Programas + + + + + + + + -
    3. Traduzindo Programas
    Anterior??????Pr??xima

    3. Traduzindo Programas

    A parte traduz??vel de um pacote de um aplica????o est?? dispon??vel em um ou mais arquivos do tipo po. Estes arquivos podem ser mantidos em uma s??rie de sistemas de controle de vers??o (VCSs), dependendo do projeto, tais como o CVS, Subversion, Mercurial ou ainda o git. Eles podem ser hospedado em ambos os servidores fedoraproject.org ou i18n.redhat.com . O sistema i18n.redhat.com n??o ?? habilitado para trabalhar com o grupo cvsl10n. Para criar uma conta em i18n.redhat.com, por favor, visite http://i18n.redhat.com/cgi-bin/i18n-signup/. Esta advert??ncia provavelmente estar?? obsoleta em breve.

    Este cap??tulo explana como traduzir os m??dulos hospedados em fedoraproject.org. Tradutores trabalham em duas interfaces, uma para obter os m??dulos e outra para enviar as tradu????es dos m??dulos. Antes de voc?? iniciar, voc?? deve preparar o diret??rio que armazenar?? seus arquivos po.

    3.1. Estrutura de Arquivos

    Par! a encontrar quais m??dulos s??o traduz??veis, visite a Lista d! e m??dul os em https://publictest5.fedora.redhat.com/submit/module/.

    Antes de voc?? baixar qualquer arquivo, prepare a estrutura para armazenar estes arquivos. O estrutura descrita abaixo ?? um exemplo e sua estrutura pode ser formatada diferentemente. Por exemplo, se voc?? quiser baixar o m??dulo comps para traduzi-lo, crie a seguinte estrutura de diret??rios:

    mkdir -p ~/myproject/comps/

    Para trabalhar em outro m??dulo posteriormente, crie um outro diret??rio com o nome do m??dulo abaixo do diret??rio pai myproject.

    3.2. Obtendo e Traduzindo M??dulos

    Agora que voc?? tem a estrutura de diret??rios preparada, voc?? p! ode baixar um arquivo para traduzir.

    1. Visite http://translate.fedoraproject.org/module/ e selecione um m??dulo. A interface ir?? lhe redirecionar para uma p??gina de m??dulo semelhante a essa http://translate.fedoraproject.org/module/comps/.

    2. Des??a na p??gina para encontrar a tabela de todos os arquivos po dispon??veis. O arquivo pot aparece no topo da listagem. Use o ??cone verde de download pr??ximo a cada nome de idioma para baixar o arquivo para o diret??rio que voc?? criou na se????o anterior.

    3. Sabendo que o nome do arquivo a ser enviado segue a conven????o de nome lang.po, mude o nome do arquivo baixado. O exemplo seguinte usa localid! ade Japonesa para o arquivo po.

      ls ~/myproject/comps/
+
+
      
+
+
+
+
+
+
+
+
      3. Traduzindo Programas
      
+Anterior??????Pr??xima
+
      
+
      
+
      
+
      
+
      3. Traduzindo Programas
      
+
      A parte traduz??vel de um pacote de um aplica????o est?? dispon??vel em um ou mais arquivos do tipo po. Estes arquivos podem ser mantidos em uma s??rie de sistemas de controle de vers??o (VCSs), dependendo do projeto, tais como o CVS, Subversion, Mercurial ou ainda o git. Eles podem ser hospedados em fedoraproject.org ou outros sistemas.
      
+
      Este cap??tulo explana como traduzir os m??dulos hospedados em fedoraproject.org. Tradutores trabalham em duas interfaces, uma para obter os m??dulos e outra para enviar as tradu????es dos m??dulos. Antes de voc?? iniciar, voc?? deve preparar o diret??rio que armazenar?? seus arquivos po.
      
+
      
+
      3.1. Estrutura de Arquivos
      
+
      Para encontrar quais m??dulos s??o traduz??veis, visite a Lista de m??dulos em https://publictest5.fedora.redhat.com/submit/module/.
      
+
      Antes de voc?? baixar qualquer arquivo, prepare a estrutura para armazenar estes arquivos. O estrutura descrita abaixo ?? um exemplo e sua estrutura pode ser formatada diferentemente. Por exemplo, se voc?? quiser baixar o m??dulo comps para traduzi-lo, crie a seguinte estrutura de diret??rios:
      
+
      mkdir -p ~/myproject/comps/
      
+
      Para trabalhar em outro m??dulo posteriormente, crie um outro diret??rio com o nome do m??dulo abaixo do diret??rio pai myproject.
      
+
      
+
      
+
      3.2. Obtendo e Traduzindo M??dulos
      
+
      Agora que voc?? tem a estrutura de diret??rios preparada, voc?? pode baixar um arquivo para traduzir.
      
+
        
+
      1. Visite a p??gina do seu idioma com o link http://translate.fedoraproject.org/languages/pt_BR/ e selecione um marcador de vers??o. A interface ir?? lhe redirecionar para uma p??gina de vers??o semelhante a essa http://translate.fedoraproject.org/languages/pt_BR/fedora-9/.
        2. 
+
      2. Des??a na p??gina para encontrar a tabela de todos os m??dulos dispon??veis para aquela vers??o. Use o ??cone verde de download, pr??ximo a cada nome de idioma, para baixar o arquivo para o diret??rio que voc?? criou na se????o anterior.
        3. 
+
      3. 
+
        Sabendo que o nome do arquivo a ser enviado segue a conven????o de nome lang.po, mude o nome do arquivo baixado. O exemplo seguinte usa localidade Japonesa para o arquivo po.
        
+
        ls ~/myproject/comps/
 comps.HEAD.ja.po
 mv ~/myproject/comps/comps.HEAD.ja.po ja.po 
 ls ~/myproject/comps/
-ja.po
      4. Agora que o arquivo j?? est?? pronto para ser traduzido. Traduza o arquivo po para seu idioma em um editor de arquivos po como o KBabel ou gtranslator.
      5. Verifique a integridade do seu arquivo antes de envi??-lo.
        msgfmt -cvo /dev/null ja.po
      [Importante]Importante
      Se alguma mensagem de erro aparecer, corrija a mesma antes de enviar a tradu????o.
      3.3. Enviando M??dulos
      Uma vez que voc?? tenha finalizado o trabalho de tradu????o, envie o arquivo usando uma interface separada chamada Transifex. Voc?? pode encontrar informa????es detalhadas sobre essa ferramente web em https://publictest5.fedora.redhat.com/submit/.
      1. Visite https://publictest5.fedora.redhat.com/submit/ e clique no link Jump to Modules! (Pular para os M??dulos), para ir para a p??gina Modules and repositories (M??dulos e reposit??rios). Esta p??gina mostra todos os m??dulos que v!
 oc?? pode enviar mudan??as. Encontre o m??dulo para enviar na !
 lista e 
selecione-o para visitar a p??gina Submit (Enviar) daquele m??dulo.
      2. Login
        No fim da p??gina Submit, selecione Authenticate as a translator (Autenticar como um tradutor) para visitar a p??gina de Login. Autentique com seu usu??rio e senha do Sistema de Contas do Fedora (Fedora Account System - FAS). Feito o login com sucesso, a p??gina Submit aparece.
      3. Submit
        Na se????o rotulada como Local file (Arquivo local), clique no bot??o para localizar seu arquivo traduzido.
        Na se????o rotulada como Destination file (Arquivo de destino), clique no menu !
 Overwrite an existing file (Sobrescrever um arquivo existente) para selecionar seu idioma.
        Na se????o rotulada como Commit message (Mensagem de envio), entre com um coment??rio para descrever seu trabalho.
        Selecione o bot??o Preview (Pr??-visualiza????o) para prosseguir para a p??gina Preview submission (Pr??-visualiza????o de envio). Verifique a se????o Differences (Diferen??as) para verificar suas mudan??as e selecione o bot??o Submit.
        A p??gina Submit aparece e mostra a mensagem Your submission was committed successfully (Sua submiss??o foi enviada com sucesso). Se voc?? obter um erro ou outra mensagem de!
  sucesso, por favor poste na lista de discuss??o do Projeto de!
  Tradu??
??o do Fedora, a fim de que isto possa ser resolvido.
      3.4. Adicionando um Novo Arquivo .po
      Se n??o existir um arquivo .po para seu idioma, adicione-o.
      1. Baixe o arquivo pot e copie-o como seu pr??prio arquivo po de idioma.
        cp ~/myproject/comps/comps.HEAD.pot ja.po
+ja.po
        
+
        2. 
+
      2. Agora que o arquivo j?? est?? pronto para ser traduzido. Traduza o arquivo po para seu idioma em um editor de arquivos po como o KBabel ou gtranslator.
        3. 
+
      3. 
+
        Verifique a integridade do seu arquivo antes de envi??-lo.
        
+
        msgfmt -cvo /dev/null ja.po
        
+
        4. 
+
      
+
      
+
+
+
+
+
+
      [Importante]Importante
      Se alguma mensagem de erro aparecer, corrija a mesma antes de enviar a tradu????o.
      
+
      
+
      
+
      3.3. Enviando M??dulos
      
+
      Uma vez que voc?? tenha finalizado o trabalho de tradu????o, envie o arquivo usando uma interface separada chamada Transifex. Voc?? pode encontrar informa????es detalhadas sobre essa ferramente web em https://publictest5.fedora.redhat.com/submit/. 
      
+
        
+
      1. Visite https://translate.fedoraproject.org/submit e clique no link Jump to Modules! (Pular para os M??dulos), para ir para a p??gina Modules and repositories (M??dulos e reposit??rios). Esta p??gina mostra todos os m??dulos que voc?? pode enviar mudan??as. Encontre o m??dulo para enviar na lista e selecione-o para visitar a p??gina Submit (Enviar) daquele m??dulo.
        2. 
+
      2. 
+
        Login
        
+
        No fim da p??gina Submit, selecione Authenticate as a translator (Autenticar como um tradutor) para visitar a p??gina de Login. Autentique com seu usu??rio e senha do Sistema de Contas do Fedora (Fedora Account System - FAS). Feito o login com sucesso, a p??gina Submit aparece.
        
+
        3. 
+
      3. 
+
        Submit
        
+
        Na se????o rotulada como Local file (Arquivo local), clique no bot??o para localizar seu arquivo traduzido.
        
+
        Na se????o rotulada como Destination file (Arquivo de destino), clique no menu Overwrite an existing file (Sobrescrever um arquivo existente) para selecionar seu idioma.
        
+
        Na se????o rotulada como Commit message (Mensagem de envio), entre com um coment??rio para descrever seu trabalho.
        
+
        Selecione o bot??o Preview (Pr??-visualiza????o) para prosseguir para a p??gina Preview submission (Pr??-visualiza????o de envio). Verifique a se????o Differences (Diferen??as) para verificar suas mudan??as e selecione o bot??o Submit.
        
+
        A p??gina Submit aparece e mostra a mensagem Your submission was committed successfully (Sua submiss??o foi enviada com sucesso). Se voc?? obter um erro ou outra mensagem de sucesso, por favor poste na lista de discuss??o do Projeto de Tradu????o do Fedora, a fim de que isto possa ser resolvido.
        
+
        4. 
+
      
+
      
+
      
+
      3.4. Adicionando um Novo Arquivo .po
      
+
      Se n??o existir um arquivo .po para seu idioma, adicione-o.
      
+
        
+
      1. 
+
        Baixe o arquivo pot e copie-o como seu pr??prio arquivo po de idioma.
        
+
        cp ~/myproject/comps/comps.HEAD.pot ja.po
 kbabel ja.po
-msgfmt -cvo /dev/null ja.po
      2. Uma vez que voc?? finalizou a tradu????o, siga os mesmos passos para verifica????o e envio de sua tradu????o descritas na se????o anterior.
      3. Na se????o rotulada como Destination file (Arquivo de destino), digite o nome no novo arquivo no campo Type the name for a new one: (Digite o nome para um novo arquivo), substituindo o nome do arquivo com seu local:
        po/ja.po
      3.5. Verifica????o Ortogr??fica
      Para revisar sua tradu????o como parte da aplica????o, siga os seguintes passos:
      1. Mude o diret??rio para o pacote que voc?? deseja revisar:
        cd ~/myproject/package_name
      2. Converta o arquivo .po em um arquivo .mo com o commando msgfmt:
        msgfmt l??ngua.po
      3. Substitua o arquivo .mo existente em /usr/share/locale/lang/LC_MESSAGES/. Primeiro, fa??a uma c??pia de seguran??a do arquivo existente:
        cp /usr/share/locale/l??ngua/LC_MESSAGES/package_name.mo package_name.mo-backup
-mv package_name.mo /usr/share/locale/l??ngua/LC_MESSAGES/
      4. Verifique o pacote com as mensagens traduzidas, como parte da aplica????o:
        LANG=l??nguapackage_command
      A aplica????o selecionada com o pacote traduzido ir?? ent??o executar com as mensagens traduzidas.
      Anterior??????Pr??xima
      2. Contas e Inscri????es??Principal??4. Traduzindo Documenta????o
      
+msgfmt -cvo /dev/null ja.po
      +
      4. +

    4. Uma vez que voc?? finalizou a tradu????o, siga os mesmos passos para verifica????o e envio de sua tradu????o descritas na se????o anterior.

      5. +
    5. +

      Na se????o rotulada como Destination file (Arquivo de destino), digite o nome no novo arquivo no campo Type the name for a new one: (Digite o nome para um novo arquivo), substituindo o nome do arquivo com seu local:

      +
      po/ja.po
      +
      6. +
    +
    +
    +

    3.5. Verifica????o Ortogr??fica

    +

    Para revisar sua tradu????o como parte da aplica????o, siga os seguintes passos:

    +
      +
    1. +

      Mude o diret??rio para o pacote que voc?? deseja revisar:

      +
      cd ~/myproject/package_name
      +
      2. +
    2. +

      Converta o arquivo .po em um arquivo .mo com o commando msgfmt:

      +
      msgfmt l??ngua.po
      +
      3. +
    3. +

      Substitua o arquivo .mo existente em /usr/share/locale/lang/LC_MESSAGES/. Primeiro, fa??a uma c??pia de seguran??a do arquivo existente:

      +
      cp /usr/share/locale/l??ngua/LC_MESSAGES/package_name.mo package_name.mo-backup
+mv package_name.mo /usr/share/locale/l??ngua/LC_MESSAGES/
      +
      4. +
    4. +

      Verifique o pacote com as mensagens traduzidas, como parte da aplica????o:

      +
      LANG=l??nguapackage_command
      +
      5. +
    +

    A aplica????o selecionada com o pacote traduzido ir?? ent??o executar com as mensagens traduzidas.

    +
    +
    +
    +
    + + + + + + + + + + + +
    +Anterior??????Pr??xima +
    2. Contas e Inscri????es??Principal??4. Traduzindo Documenta????o
    +
    + displayFooter('$Date$'); ?> + From joedarcy at MIT.EDU Wed Mar 19 18:31:22 2008 From: joedarcy at MIT.EDU (Joe Darcy) Date: Wed, 19 Mar 2008 14:31:22 -0400 Subject: Fedora 8 image files Message-ID: <47E15BFA.4070908@mit.edu> To whom it may concern: I've tried multiple times to download the image of Fedora 8, both Bittorrent and from a mirror. In all cases, when I have the media test itself, it says that the file is corrupted and I shouldn't install. Perhaps there is a problem with the files available for download. Thank you. J Darcy From ricky at fedoraproject.org Wed Mar 19 19:04:52 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Wed, 19 Mar 2008 15:04:52 -0400 Subject: Fedora 8 image files In-Reply-To: <47E15BFA.4070908@mit.edu> References: <47E15BFA.4070908@mit.edu> Message-ID: <20080319190451.GB1382@Max.nyc1.dsl.speakeasy.net> On 2008-03-19 02:31:22 PM, Joe Darcy wrote: > To whom it may concern: > > I've tried multiple times to download the image of Fedora 8, both > Bittorrent and from a mirror. In all cases, when I have the media test > itself, it says that the file is corrupted and I shouldn't install. > Perhaps there is a problem with the files available for download. If you experienced the exact same problem with BitTorrent, then it is unlikely that the problem is on our side. BitTorrent does hash checking, so it would be very unlikely that you got a corrupted file from there. Is there any other place where there could be a problem? You might also have some luck with some of the resources listed at http://fedoraproject.org/wiki/Communicate. Good luck, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Matt_Domsch at dell.com Fri Mar 21 02:28:46 2008 From: Matt_Domsch at dell.com (Matt Domsch) Date: Thu, 20 Mar 2008 21:28:46 -0500 Subject: request for mirror In-Reply-To: References: Message-ID: <20080321022846.GA30492@auslistsprd01.us.dell.com> On Tue, Mar 18, 2008 at 02:15:38PM +0800, AnyongXia at viatech.com.cn wrote: > HI, > > I have builded a server with fedora 7, and I want to make a mirror of your > websites, please recommend the tool for this. Thank you! If you mean to mirror the software, please see http://fedoraproject.org/wiki/Infrastructure/Mirroring. Thanks, Matt Fedora Mirror Wrangler -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux From kwade at redhat.com Fri Mar 21 06:02:56 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 20 Mar 2008 23:02:56 -0700 Subject: feeds mock-up for front page In-Reply-To: <1205562651.13919.170.camel@calliope.phig.org> References: <1205451857.13919.20.camel@calliope.phig.org> <20080314015304.GF5429@Max.nyc1.dsl.speakeasy.net> <47D9DC4F.7070309@fedoraproject.org> <1205466012.11635.2.camel@localhost.localdomain> <1205470061.13919.43.camel@calliope.phig.org> <1205554988.13919.136.camel@calliope.phig.org> <20080315043437.GG5626@Max.nyc1.dsl.speakeasy.net> <1205562651.13919.170.camel@calliope.phig.org> Message-ID: <1206079376.29963.20.camel@calliope.phig.org> On Fri, 2008-03-14 at 23:30 -0700, Karsten 'quaid' Wade wrote: > --- > "Fedora Weekly News" > http://fedora-tchung.blogspot.com/feeds/posts/default > ---- > "Red Hat Magazine/Dev Fu/Truth Happens" or "Red Hat Magazine" > http://www.redhatmagazine.com/category/fedora/feed > http://developer.redhatmagazine.com/category/fedora/feed > http://truthhappens.redhatmagazine.com/feed > --- > "Fedora Announcements" > rss://fedora-announce-list at redhat.com (?) > http://news.fedoraproject.org/feed > --- I left out the Planet ... which might be OK, since it gets a lot of updates that aren't too Fedora specific for the general audience. OTOH, it shows what is happening in our community. If we include it, I would put it in the last section, like this: --- "Informative Fedora" rss://fedora-announce-list at redhat.com (?) http://news.fedoraproject.org/feed http://planet.fedoraproject.org/atom.xml --- -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mmcgrath at redhat.com Mon Mar 24 00:44:36 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Sun, 23 Mar 2008 19:44:36 -0500 (CDT) Subject: Beta Release Notes In-Reply-To: <1205932635.12292.27.camel@localhost.localdomain> References: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> <1205847389.25162.77.camel@localhost.localdomain> <1205858865.13919.361.camel@calliope.phig.org> <1205932635.12292.27.camel@localhost.localdomain> Message-ID: On Wed, 19 Mar 2008, Paul W. Frields wrote: > On Tue, 2008-03-18 at 09:47 -0700, Karsten 'quaid' Wade wrote: > > On Tue, 2008-03-18 at 09:36 -0400, Paul W. Frields wrote: > > > On Mon, 2008-03-17 at 11:15 -0600, Jonathan Roberts wrote: > > > > Hi all, > > > > > > > > I wondered if somebody could help me out and create a static version of the > > > > Beta release notes at > > > > http://fedoraproject.org/wiki/Releases/9/Beta/ReleaseNotes ? > > > > > > > > Hopefully we'll be able to avoid the problems this caused with the Alpha > > > > release :) > > > > > > Great point. We should also give thought to where we provide links to > > > these notes too, and direct them to the static page. > > > > IIRC, the actual wiki page is turned 'immutable' and actually served as > > static from that URL. > > If there's not a significant load from calling Moin and having it > assemble everything to display the page, then that sounds fine. Did > that work OK, performance-wise, in the past? They've always performed horribly in the past. Basically we use wget to get the page and then use apache to serve just that link as a static page. We've had to do this for almost every release when someone linked to the wiki directly. We try to do it as close to the date a possible though because the page cannot be changed without taking the static option away. -Mike From kwade at redhat.com Mon Mar 24 04:18:10 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Sun, 23 Mar 2008 21:18:10 -0700 Subject: Beta Release Notes In-Reply-To: References: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> <1205847389.25162.77.camel@localhost.localdomain> <1205858865.13919.361.camel@calliope.phig.org> <1205932635.12292.27.camel@localhost.localdomain> Message-ID: <1206332290.29963.150.camel@calliope.phig.org> On Sun, 2008-03-23 at 19:44 -0500, Mike McGrath wrote: > On Wed, 19 Mar 2008, Paul W. Frields wrote: > > If there's not a significant load from calling Moin and having it > > assemble everything to display the page, then that sounds fine. Did > > that work OK, performance-wise, in the past? > > They've always performed horribly in the past. Basically we use wget to > get the page and then use apache to serve just that link as a static page. > We've had to do this for almost every release when someone linked to the > wiki directly. > > We try to do it as close to the date a possible though because the page > cannot be changed without taking the static option away. I pulled the websites code and started to put together a static HTML page from the Beta release notes on the wiki. The biggest hassle is the conversion. I actually rendered the page as DocBook, then wrote that to HTML, and am pulling from that into a page in the fedoraproject.org tree. Maybe we'll have this ready by tomorrow? - Karsten -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From renich at woralelandia.com Mon Mar 24 08:30:09 2008 From: renich at woralelandia.com (Renich Bon Ciric) Date: Mon, 24 Mar 2008 02:30:09 -0600 Subject: wrong account name Message-ID: <1206347409.19761.3.camel@localhost6.localdomain6> Hello, I need to change my account name from renich to renichbon so I can be a wiki editor. Can you help me? # was @: https://admin.fedoraproject.org/accounts/home -- Renich Bon Ciric Woralelandia -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mostafa at daneshvar.org.uk Mon Mar 24 14:01:58 2008 From: mostafa at daneshvar.org.uk (Mostafa Daneshvar) Date: Mon, 24 Mar 2008 18:31:58 +0430 Subject: wrong account name In-Reply-To: <1206347409.19761.3.camel@localhost6.localdomain6> References: <1206347409.19761.3.camel@localhost6.localdomain6> Message-ID: <200803241832.07815.mostafa@daneshvar.org.uk> On Do shanbe 05 Farvardin 1387 13:00:09 Renich Bon Ciric wrote: > Hello, > > I need to change my account name from renich to renichbon so I can be a > wiki editor. > > Can you help me? > > # was @: > https://admin.fedoraproject.org/accounts/home As long as I know there is no way to modify your account name. I suppose you should begin registration process again with your desired account name. -- Mostafa Daneshvar -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From ricky at fedoraproject.org Mon Mar 24 14:09:21 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Mon, 24 Mar 2008 10:09:21 -0400 Subject: wrong account name In-Reply-To: <1206347409.19761.3.camel@localhost6.localdomain6> References: <1206347409.19761.3.camel@localhost6.localdomain6> Message-ID: <20080324140921.GA8871@Max.nyc1.dsl.speakeasy.net> On 2008-03-24 02:30:09 AM, Renich Bon Ciric wrote: > Hello, > > I need to change my account name from renich to renichbon so I can be a > wiki editor. > > Can you help me? > > # was @: > https://admin.fedoraproject.org/accounts/home You wikiname is completely separate from your FAS username, so the FirstnameLastname requirement only applies there. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Mon Mar 24 23:09:33 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 24 Mar 2008 16:09:33 -0700 Subject: Beta Release Notes In-Reply-To: <1206332290.29963.150.camel@calliope.phig.org> References: <87736064e3c13ccd0860150041a872e6@www.questionsplease.org> <1205847389.25162.77.camel@localhost.localdomain> <1205858865.13919.361.camel@calliope.phig.org> <1205932635.12292.27.camel@localhost.localdomain> <1206332290.29963.150.camel@calliope.phig.org> Message-ID: <1206400173.4531.4.camel@calliope.phig.org> On Sun, 2008-03-23 at 21:18 -0700, Karsten 'quaid' Wade wrote: > Maybe we'll have this ready by tomorrow? Yep, Paul just tweaked one of my misteaks and committed that. It's ready to final QA and push to live. -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From jonrob at fedoraproject.org Tue Mar 25 23:04:02 2008 From: jonrob at fedoraproject.org (Jonathan Roberts) Date: Tue, 25 Mar 2008 17:04:02 -0600 Subject: news.fedoraproject.org Message-ID: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> Evening all, We've been talking for a while about setting up a news.fedoraproject.org site, for a number of different uses. Thanks to the hard work of Frank Chiulli we now have a test install of Lyceum on publictest 1 for our use :) Before moving forward with this, we need to deal with a number of issues: 1) What do we actually want to use the site for? My thoughts are that we use it for Fedora Weekly News, along with other marketing stuff such as interviews and announcements - similar to what press.redhat.com is. 2) Depending on the above, do we want to use Lyceum or Wordpress? Infra would like us to have whatever solution we use packaged and yumable on Fedora; Wordpress is already in while Lyceum needs packaging. As I understand it Lyceum allows us to have multiple blogs and is what's used by Red Hat Magazine. Wordpress only allows for the one blog, but would also allow multiple authors/editors on a single blog (I think). 3) Experiment and play - find a work flow that's right for us! We may need some test material for this, such as an example FWN release or a mock announcement. 4) We need a theme. I've started on one, and whatever we create for Wordpress should also work on Lyceum, though we've had some problems with this! If you're interested to see what I've got so far, test.questionsplease.org will let you :) I can make this available for people to use as a base. All I've done is create a simple Wordpress template that uses the ids and classes from fedora.css, and point at that for the style sheet. I'll upload this to my fedorapeople space soon... Anyone is welcome to sign up and we can start adding people in different roles to the Fedora News blog I created in Lyceum, but the URL for the install is on another box...Rahul, Frank, can you help me out here? I think that's all for now. Does anybody have any thoughts or ideas about this? Ah, and finally, could we keep all replies to the marketing list, if people think that's appropriate? Better to do everything once than 5 times! Best wishes, and sorry for all the stuff I've probably forgotten! Jon From sundaram at fedoraproject.org Tue Mar 25 23:12:15 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 26 Mar 2008 04:42:15 +0530 Subject: news.fedoraproject.org In-Reply-To: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> References: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> Message-ID: <47E986CF.1080104@fedoraproject.org> Jonathan Roberts wrote: > Anyone is welcome to sign up and we can start adding people in different > roles to the Fedora News blog I created in Lyceum, but the URL for the > install is on another box...Rahul, Frank, can you help me out here? You want https://publictest1.fedoraproject.org/lyceum/portal.php Rahul From tchung at fedoraproject.org Wed Mar 26 02:18:04 2008 From: tchung at fedoraproject.org (Thomas Chung) Date: Tue, 25 Mar 2008 19:18:04 -0700 Subject: news.fedoraproject.org In-Reply-To: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> References: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> Message-ID: <369bce3b0803251918m2e54e350sfb4d53ea932f002b@mail.gmail.com> On Tue, Mar 25, 2008 at 4:04 PM, Jonathan Roberts wrote: > 2) Depending on the above, do we want to use Lyceum or Wordpress? Infra > would like us to have whatever solution we use packaged and yumable on > Fedora; Wordpress is already in while Lyceum needs packaging. As I > understand it Lyceum allows us to have multiple blogs and is what's used by > Red Hat Magazine. Wordpress only allows for the one blog, but would also > allow multiple authors/editors on a single blog (I think). One of the question we need to answer is why Lyceum instead of WordPress. We can get some answer from their FAQ page[1] but, I also have some concerns on WordPress plugins compatibility with Lyceum. WordPress already have thousands of useful plugins[2] and there have been some reports that not all WordPress pugins are compatible with Lyceum and they may need to re-written or ported over. I guess the real question is do we really need multi-blogger for our needs? We appreciated if we can hear your comments or suggestions. Regards, [1] http://lyceum.ibiblio.org/faq/ [2] http://wordpress.org/extend/plugins/ -- Thomas Chung http://fedoraproject.org/wiki/ThomasChung From richard-harrison at comcast.net Wed Mar 26 03:16:48 2008 From: richard-harrison at comcast.net (richard-harrison at comcast.net) Date: Wed, 26 Mar 2008 03:16:48 +0000 Subject: news.fedoraproject.org Message-ID: <032620080316.8070.47E9C020000AB3A600001F86221656627602019C079D9D0E08D30B9D0E080C079D@comcast.net> > appreciated if we can hear your comments or suggestions. >From Lyceum's faq: "The main difference between Lyceum and MU is the database schema. MU creates a set of tables for each blog in a system. Lyceum uses a fixed number of tables for the entire system." >From a resource/performance perspective, is that wise? How great a risk is there that "small" and "medium" (fuzzy terms) volume blogs may suffer performance hits due to their "much larger" brethren? What about backup and maintenance issues, e.g., one table "issue" kills many blogs? Since I have no sense of projected data volume or anticipated numbers of blogs competing for shared resources/tables, these questions are blind. From ivazqueznet at gmail.com Wed Mar 26 03:34:46 2008 From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams) Date: Tue, 25 Mar 2008 23:34:46 -0400 Subject: news.fedoraproject.org In-Reply-To: <032620080316.8070.47E9C020000AB3A600001F86221656627602019C079D9D0E08D30B9D0E080C079D@comcast.net> References: <032620080316.8070.47E9C020000AB3A600001F86221656627602019C079D9D0E08D30B9D0E080C079D@comcast.net> Message-ID: <1206502486.24545.7.camel@ignacio.lan> On Wed, 2008-03-26 at 03:16 +0000, richard-harrison at comcast.net wrote: > > appreciated if we can hear your comments or suggestions. > From Lyceum's faq: > > "The main difference between Lyceum and MU is the database schema. MU > creates a set of tables for each blog in a system. Lyceum uses a fixed > number of tables for the entire system." IOW, Lyceum does it right, MU does it wrong, from a strictly technical standpoint. > From a resource/performance perspective, is that wise? How great a > risk is there that "small" and "medium" (fuzzy terms) volume blogs may > suffer performance hits due to their "much larger" brethren? Unless the software is coded in a grossly inappropriate manner, little to none. -- Ignacio Vazquez-Abrams PLEASE don't CC me; I'm already subscribed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From richard-harrison at comcast.net Wed Mar 26 04:33:28 2008 From: richard-harrison at comcast.net (richard-harrison at comcast.net) Date: Wed, 26 Mar 2008 04:33:28 +0000 Subject: news.fedoraproject.org Message-ID: <032620080433.5455.47E9D21800031C3D0000154F221205921402019C079D9D0E08D30B9D0E080C079D@comcast.net> >> "The main difference between Lyceum and MU is the database schema. MU >> creates a set of tables for each blog in a system. Lyceum uses a fixed >> number of tables for the entire system." > IOW, Lyceum does it right, MU does it wrong, from a strictly technical >standpoint. "Strictly technical" in what sense? >> From a resource/performance perspective, is that wise? How great a >> risk is there that "small" and "medium" (fuzzy terms) volume blogs may >> suffer performance hits due to their "much larger" brethren? > Unless the software is coded in a grossly inappropriate manner, little > to none. My question was directed at physical resources and access issues related to data volume. After a certain scaling point, no matter how grossly appropriate the coding of the software, negative impacts related to contention for tables and physical resources will happen. I am asking people likely to have knowledge of projected/expected data volumes to consider those risks. From kwade at redhat.com Wed Mar 26 05:06:09 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 25 Mar 2008 22:06:09 -0700 Subject: news.fedoraproject.org In-Reply-To: <369bce3b0803251918m2e54e350sfb4d53ea932f002b@mail.gmail.com> References: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> <369bce3b0803251918m2e54e350sfb4d53ea932f002b@mail.gmail.com> Message-ID: <1206507969.4531.156.camel@calliope.phig.org> On Tue, 2008-03-25 at 19:18 -0700, Thomas Chung wrote: > I guess the > real question is do we really need multi-blogger for our needs? To be honest, news.fp.org may not need more than a single-blog Wordpress installation. I believe such a system can handle multiple-writers/editors, all within one blog. From an infrastructure Big View, I think a multi-blog system is best. The resources put into configuring and maintaining yield a reusable system. Right now we don't have another use for a blog engine, but we could come up with one at any time. :) - Karsten, who actually does have another use, the return of the old FWN-style short how-to articles. -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sudheer.s at binaryvibes.co.in Wed Mar 26 07:45:45 2008 From: sudheer.s at binaryvibes.co.in (Sudheer) Date: Wed, 26 Mar 2008 13:15:45 +0530 Subject: news.fedoraproject.org In-Reply-To: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> References: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> Message-ID: <47E9FF29.6060002@binaryvibes.co.in> Jonathan Roberts wrote: > Evening all, > > We've been talking for a while about setting up a news.fedoraproject.org > site, for a number of different uses. Thanks to the hard work of Frank > Chiulli we now have a test install of Lyceum on publictest 1 for our use :) > Before moving forward with this, we need to deal with a number of issues: > > 1) What do we actually want to use the site for? > > My thoughts are that we use it for Fedora Weekly News, along with other > marketing stuff such as interviews and announcements - similar to what > press.redhat.com is. > > 2) Depending on the above, do we want to use Lyceum or Wordpress? Infra > would like us to have whatever solution we use packaged and yumable on > Fedora; Wordpress is already in while Lyceum needs packaging. As I > understand it Lyceum allows us to have multiple blogs and is what's used by > Red Hat Magazine. Wordpress only allows for the one blog, but would also > allow multiple authors/editors on a single blog (I think). > > I recommend Drupal. It provides multi user blog and whole lot of other features. > 3) Experiment and play - find a work flow that's right for us! We may need > some test material for this, such as an example FWN release or a mock > announcement. > > 4) We need a theme. I've started on one, and whatever we create for > Wordpress should also work on Lyceum, though we've had some problems with > this! If you're interested to see what I've got so far, > test.questionsplease.org will let you :) I can make this available for > people to use as a base. All I've done is create a simple Wordpress > template that uses the ids and classes from fedora.css, and point at that > for the style sheet. I'll upload this to my fedorapeople space soon... > > I would be glad to help set-up Drupal for news.fedoraproject.org. > Anyone is welcome to sign up and we can start adding people in different > roles to the Fedora News blog I created in Lyceum, but the URL for the > install is on another box...Rahul, Frank, can you help me out here? > > I think that's all for now. Does anybody have any thoughts or ideas about > this? Ah, and finally, could we keep all replies to the marketing list, if > people think that's appropriate? Better to do everything once than 5 times! > > > Best wishes, and sorry for all the stuff I've probably forgotten! > > Jon > > -- With warm regards, Sudheer. S http://binaryvibes.co.in From pemboa at gmail.com Wed Mar 26 18:53:02 2008 From: pemboa at gmail.com (Arthur Pemberton) Date: Wed, 26 Mar 2008 13:53:02 -0500 Subject: GSoC Idea: Web UI to manage FreeMedia Message-ID: <16de708d0803261153g6ca54543s581f7398dfca0fac@mail.gmail.com> Would a proposal to develop a (likely Django, definitely python based) UI to manage the free media distribution process be welcome? I imagine that the proposal/project process is getting pretty competitive. I have an associate who is interested in participating, and I would be willing to mentor/assist as necessary. Arthur Pemberton -- Fedora 7 : sipping some of that moonshine ( www.pembo13.com ) From nicu_fedora at nicubunu.ro Thu Mar 27 12:22:46 2008 From: nicu_fedora at nicubunu.ro (Nicu Buculei) Date: Thu, 27 Mar 2008 14:22:46 +0200 Subject: Release counter for F9 Message-ID: <47EB9196.4000209@nicubunu.ro> The release counter we had for F8 proved to be quite popular, so is natural to have this time another one, maybe with some improvements. With the release scheduled for April 29, about a month from now, I think it is a good time to start planning it. A first thing would be, IMO, to define when we start counting. I see two possible scenarios: either from a certain number of days in advance (30 days sounds plausible) or from the Release Candidate. For the graphics, I think we can base them on the Beta banner made by Mo [1], but we can be open for another approaches. I think is easy enough to get all the images pre-rendered in advance by the Art team and not rely on a cron job do produce them daily. Embedding in the website in another part: for F8 we had something like 01.png ... 15.png and the HTML was changed to include the proper image. I see here a lot of potential for improvement: provide something that people can include on their own pages/websites/blog and spread the waiting game all over the web. We can do that having a single image like f9counter.png updated daily, but this may not be very cache-friendly (people may get an old version from an un-updated cache), a JavaScript widget may be a better solution. Please reply on the Art list about the graphics and on the Websites list about the implementation. [1] - http://fedoraproject.org/wiki/Artwork/PromoBanners#head-168c7c266a7785106cc25828a803c858cdfbe50e -- nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com Cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/ Open Clip Art Library: http://www.openclipart.org my Fedora stuff: http://fedora.nicubunu.ro From stickster at gmail.com Thu Mar 27 15:33:21 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 27 Mar 2008 11:33:21 -0400 Subject: news.fedoraproject.org In-Reply-To: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> References: <416ff6804984c15d497dd9698f1fe4bb@www.questionsplease.org> Message-ID: <1206632001.4736.7.camel@localhost.localdomain> On Tue, 2008-03-25 at 17:04 -0600, Jonathan Roberts wrote: > Evening all, > > We've been talking for a while about setting up a news.fedoraproject.org > site, for a number of different uses. Thanks to the hard work of Frank > Chiulli we now have a test install of Lyceum on publictest 1 for our use :) > Before moving forward with this, we need to deal with a number of issues: > > 1) What do we actually want to use the site for? > > My thoughts are that we use it for Fedora Weekly News, along with other > marketing stuff such as interviews and announcements - similar to what > press.redhat.com is. Agreed, and it doesn't ever hurt to reaggregate stuff either. > 2) Depending on the above, do we want to use Lyceum or Wordpress? Infra > would like us to have whatever solution we use packaged and yumable on > Fedora; Wordpress is already in while Lyceum needs packaging. As I > understand it Lyceum allows us to have multiple blogs and is what's used by > Red Hat Magazine. Wordpress only allows for the one blog, but would also > allow multiple authors/editors on a single blog (I think). One thing I would like to see, and which I mentioned to Seth Vidal at FUDCon in Raleigh in January, was a way for us to offer blogs as a service to our account holders. The HTTPS work that Frank has done was probably a key action in making that possible, but I'm not sure exactly how close that gets us. It wouldn't be too hard for us to act as an OpenID provider for our account holders either, which is another nice way of advertising and pushing open standards. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Thu Mar 27 19:23:19 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 27 Mar 2008 19:23:19 +0000 Subject: Torrent history Message-ID: <1206645799.4736.32.camel@localhost.localdomain> Is there any historical information on torrent downloads for F8 testing phases? i.e. Week-by-week downloads or something similar? The final numbers appear to be gone from the tracker page -- was anything retained somewhere I could peruse? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From invert01 at gmail.com Wed Mar 26 18:56:46 2008 From: invert01 at gmail.com (Aaron Yates) Date: Wed, 26 Mar 2008 18:56:46 +0000 Subject: Account admin page errors? Message-ID: <80ef5880803261156h63597e96i26ea392a7ced65a3@mail.gmail.com> Hi Webmaster, Sorry to bother you with this, I'm trying to set up my account on the account admin page (add my IRC nick and SSH cert, basic details are already in there), but when I submit the form I get the following error: Error! The following error(s) have occured with your request: - locale: The language 'en' is not available. I'm not entirely sure what's going on? Any advice would be very much appreciated! Thanks, Aaron Yates -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhodesiansprings at yahoo.com Wed Mar 26 22:51:56 2008 From: rhodesiansprings at yahoo.com (J.Rhodes) Date: Wed, 26 Mar 2008 15:51:56 -0700 (PDT) Subject: Spam Message-ID: <779332.46066.qm@web37907.mail.mud.yahoo.com> There is spam being generated by a page that seems to behosted or connected with your site. I’m receiving 3 to four emailsevery hour from various user names: Carolyn Pena [Stephen at worndrying.info] Martin Franks [Roger at worndrying.info] Etc. And they are being sent to moonlightshinner at yahoo.com so I don’tknow how they are making it to my address...and I never signed up/heard aboutthis site. The content of each one is exactly the same: So how is your month going so far. Lets see, the stockmarket is down, unemployment is up, gas prices are through the roof, the powersthat be finally admit that we are in a recession, houses being reposseesed areat an all time high, and through all of this you still have bills staring youin face that have to be taken care of no matter what is going on around you.Don't give up, there is hope for you, all you have to do is go here http://drainput.info/Cryptographer/this is your way to the light at the end of the tunnel. http://drainput.info/remove2/to unsubscribe. hl2toepzss8S[$3=$[88FAiRd$ss0,szIz[z=]RPmW%iRd$ss0,szIS[SOss3RWS[_F6fiRd$ss0,szIzsS9sOiRd$ss0,szIzu$dA93iRd$ss0,szIAd,$dFS|AsF33iRd$ss0,szIzdA[8dNdAHWm66iRd$ss0,szI8[,]|Ad9siRd$ss0,szIS=8P8[ diRd$ss0,szIz[==OdORummiRd$ss0,szIzRP8F8dPOssiRd$ss0,szIzd3$F=s8Pd9dziRd$ss0,szI|A[8,F==Q9[6QmiRd$ss0,szIA$s9F=[d8=|A[8=iRd$ss0,szI|[8FP8n3PmiRd$ss0,szIszsS[8,s8iRd$ss0,szI8R,zs-3?d83F9iRd$ss0,szI8d=,dA%W9dNFiRd$ss0,szIzd*,sA9s8iRd$ss0,szIs=zd89dAAdiRd$ss0,szISs]s3dzdiRd$ss0,szISn,]R=FNF8=PHHiRd$ss0,szISss][8Wn6mWfQfiRd$ss0,szIzP_Ad8,F=[OdiRd$ss0,szIs8SRm=$s36=$[8FiRd$ss0,szpo2l4lr ___ I would unsubscribe but being just a little bit put offand skeptical about the whole thing (and my desire not to test my luck with anysort of Trojan, scam or whatnot)... I’m not inclined to click theirlink. Would you please look into that and see if itslegitimate. Im sure im not the only one receiving these and if there isanything fishy going on, you all would be in a better position to find out. Thanks again, John No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.0/1343 - Release Date: 3/25/2008 7:17 PM --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From admin at ev5unleash.com Thu Mar 27 22:38:57 2008 From: admin at ev5unleash.com (Evan Janusziewicz) Date: Thu, 27 Mar 2008 18:38:57 -0400 Subject: Ad on our site. Message-ID: <000601c8905b$5b927e10$12b77a30$@com> Hello, I am Evan J, the Webmaster of ev5unleash.com (http://www.ev5unleash.com). I'm trying to offer free solutions to the community in my area and around the world and I would like to advertise Fedora on my website. I would like to ask your permission to do so. For more information please reply to this e-mail. Evan J from ev5unleash.com admin at ev5unleash.com http://www.ev5unleash.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricky at fedoraproject.org Thu Mar 27 22:58:05 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 27 Mar 2008 18:58:05 -0400 Subject: Account admin page errors? In-Reply-To: <80ef5880803261156h63597e96i26ea392a7ced65a3@mail.gmail.com> References: <80ef5880803261156h63597e96i26ea392a7ced65a3@mail.gmail.com> Message-ID: <20080327225805.GC31459@Max.nyc1.dsl.speakeasy.net> On 2008-03-26 06:56:46 PM, Aaron Yates wrote: > Sorry to bother you with this, I'm trying to set up my account on the > account admin page (add my IRC nick and SSH cert, basic details are already > in there), but when I submit the form I get the following error: Sorry about this, we had a bug in our latest update. That should be fixed now. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mmcgrath at redhat.com Thu Mar 27 22:56:22 2008 From: mmcgrath at redhat.com (Mike McGrath) Date: Thu, 27 Mar 2008 17:56:22 -0500 (CDT) Subject: Account admin page errors? In-Reply-To: <20080327225805.GC31459@Max.nyc1.dsl.speakeasy.net> References: <80ef5880803261156h63597e96i26ea392a7ced65a3@mail.gmail.com> <20080327225805.GC31459@Max.nyc1.dsl.speakeasy.net> Message-ID: On Thu, 27 Mar 2008, Ricky Zhou wrote: > On 2008-03-26 06:56:46 PM, Aaron Yates wrote: > > Sorry to bother you with this, I'm trying to set up my account on the > > account admin page (add my IRC nick and SSH cert, basic details are already > > in there), but when I submit the form I get the following error: > Sorry about this, we had a bug in our latest update. That should be > fixed now. > Very strange, this mail got delayed by about a day. -Mike From ricky at fedoraproject.org Thu Mar 27 23:04:17 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 27 Mar 2008 19:04:17 -0400 Subject: Spam In-Reply-To: <779332.46066.qm@web37907.mail.mud.yahoo.com> References: <779332.46066.qm@web37907.mail.mud.yahoo.com> Message-ID: <20080327230417.GD31459@Max.nyc1.dsl.speakeasy.net> On 2008-03-26 03:51:56 PM, J.Rhodes wrote: > There is spam being generated by a page that seems to behosted or > connected with your site. I’m receiving 3 to four emailsevery > hour from various user names: I can't get to any of the links from the email, but I assume that you're referring a page that looks like: http://fedoraproject.org/wiki/ServerTestPage?action=AttachFile&do=get&target=httpd_test_page.png That is a test page included with our operating system; we don't actually control the site in question. For more information, please refer to http://fedoraproject.org/wiki/ServerTestPage. You should probably report this kind of thing to the abuse address of their ISP/host. You should be able to look up the contact information by doing a whois lookup on their domain/IP address. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ricky at fedoraproject.org Thu Mar 27 23:10:45 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 27 Mar 2008 19:10:45 -0400 Subject: Release counter for F9 In-Reply-To: <47EB9196.4000209@nicubunu.ro> References: <47EB9196.4000209@nicubunu.ro> Message-ID: <20080327231045.GE31459@Max.nyc1.dsl.speakeasy.net> On 2008-03-27 02:22:46 PM, Nicu Buculei wrote: > For the graphics, I think we can base them on the Beta banner made by Mo > [1], but we can be open for another approaches. > I think is easy enough to get all the images pre-rendered in advance by the > Art team and not rely on a cron job do produce them daily. That might depend on whether there's any text in image. If there is text, I've spoken to Mo about the possiblity of extracting strings for translation (and automatically generating images for all days/languages). > Embedding in the website in another part: for F8 we had something like > 01.png ... 15.png and the HTML was changed to include the proper image. > I see here a lot of potential for improvement: provide something that > people can include on their own pages/websites/blog and spread the waiting > game all over the web. > We can do that having a single image like f9counter.png updated daily, but > this may not be very cache-friendly (people may get an old version from an > un-updated cache), a JavaScript widget may be a better solution. For F8, I think we actually ended up including some javascript to update the image (http://fedoraproject.org/static/js/release-counter.js). All of the URLs there are absolute (so anybody can include this script to get their own counter). Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ivazqueznet at gmail.com Fri Mar 28 01:21:05 2008 From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams) Date: Thu, 27 Mar 2008 21:21:05 -0400 Subject: Ad on our site. In-Reply-To: <000601c8905b$5b927e10$12b77a30$@com> References: <000601c8905b$5b927e10$12b77a30$@com> Message-ID: <1206667265.24545.16.camel@ignacio.lan> On Thu, 2008-03-27 at 18:38 -0400, Evan Janusziewicz wrote: > Hello, > > > > I am Evan J, the Webmaster of ev5unleash.com > (http://www.ev5unleash.com). I?m trying to offer free solutions to the > community in my area and around the world and I would like to > advertise Fedora on my website. I would like to ask your permission to > do so. For more information please reply to this e-mail. > > > > Evan J from ev5unleash.com > > admin at ev5unleash.com > > http://www.ev5unleash.com/ Thank you for your interest. Unfortunately we are unable to permit your request at this time. Have a pleasant day. -- Ignacio Vazquez-Abrams -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From bicycle.nutz at gmail.com Fri Mar 28 02:15:48 2008 From: bicycle.nutz at gmail.com (Craig Thomas) Date: Thu, 27 Mar 2008 22:15:48 -0400 Subject: misc tickets and some general questions for all Message-ID: Hi All, In reviewing the tickets labled 'Webmaster' here: https://hosted.fedoraproject.org/fedora-infrastructure/report/1?sort=component&asc=0 I have run into several questions. Seemingly crufty items first: #'s : 181, 206 and perhaps 55 all seem like good candidates to be closed to me, but what do the rest of us think? ( A couple of others that I noticed, but are not explicitly webmaster are: 114 and 221 ) Which leaves 3 webmaster tickets I have questions about: 467 - are we planning on changing the get-fedora page for the release of f9 ? if so, do we think we should put live media first? is that _our_ decision to make? which ties into # 411 ? what are we doing for the F9 release? am I missing something on the wiki or in the tickets ? and 357, RSS feeds on the home page (very cool) . Is the code mentioned in the ticket already in the git repo and I am not seeing it? I am not certain, but I suspect we have more 'webistes' work than the trac tickets on hosted.fp.o ? Cheers, -- Craig From stickster at gmail.com Fri Mar 28 02:25:30 2008 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 27 Mar 2008 22:25:30 -0400 Subject: Fedora fan sites? Message-ID: <1206671130.24319.30.camel@localhost.localdomain> There are a lot of people out there who love Fedora. Some of them run web sites. Some of them want to run web sites that talk about Fedora, and they might want to use our open code to provide the site assets. We don't necessarily want these sites to look just like our site, because then it's easy for visitors to be confused about whether they're on an official site or not. Then the attendant brand weakening, blah blah blah... Is anyone CSS-savvy interested in whipping up a companion "fedora-fan.css" for our web site that would allow people who love us and use our code to have a style sheet all ready to use that's not just like ours, but somewhat attractive, functional, and (dare I say it?) complementary to the official Fedora theme? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From bicycle.nutz at gmail.com Fri Mar 28 02:47:21 2008 From: bicycle.nutz at gmail.com (Craig Thomas) Date: Thu, 27 Mar 2008 22:47:21 -0400 Subject: Fedora fan sites? In-Reply-To: <1206671130.24319.30.camel@localhost.localdomain> References: <1206671130.24319.30.camel@localhost.localdomain> Message-ID: 2008/3/27 Paul W. Frields : > There are a lot of people out there who love Fedora. Some of them run > web sites. Some of them want to run web sites that talk about Fedora, > and they might want to use our open code to provide the site assets. We > don't necessarily want these sites to look just like our site, because > then it's easy for visitors to be confused about whether they're on an > official site or not. Then the attendant brand weakening, blah blah > blah... > > Is anyone CSS-savvy interested in whipping up a companion > "fedora-fan.css" for our web site that would allow people who love us > and use our code to have a style sheet all ready to use that's not just > like ours, but somewhat attractive, functional, and (dare I say it?) > complementary to the official Fedora theme? I like this idea, but I am not sure that a .css file is the right approach. To be effective in terms of a site's 'look', CSS tends to get pretty specific, pretty quickly. We could offer a .css file with default fonts and colors for links and such .However, unless we offer the markup as well, the CSS 'rules' wont have any 'hooks' into the unknown code using the .css file to do much. Most likely rendering them barely useful, or worse, in terms of 'talking up' fedora on fan sites. I think better would be to offer the planned RSS feeds, our banners and count down graphics (and anything else) as 'widgets' to use on those sites. The same way the count down graphics we used for F8 was just a .js file anyone could load and use on their site. my $.02 -- Craig > -- > Paul W. Frields http://paul.frields.org/ > gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 > http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ > irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug > > -- > Fedora-websites-list mailing list > Fedora-websites-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-websites-list > > From ricky at fedoraproject.org Fri Mar 28 02:52:20 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 27 Mar 2008 22:52:20 -0400 Subject: misc tickets and some general questions for all In-Reply-To: References: Message-ID: <20080328025220.GG31459@Max.nyc1.dsl.speakeasy.net> On 2008-03-27 10:15:48 PM, Craig Thomas wrote: > Seemingly crufty items first: > > #'s : 181, 206 and perhaps 55 181: download.fedora.redhat.com apache index CSS is outdated 206: uie (it's about the docs.fp.o theme) 55: Common Look and Feel I think these should still be addressed - It's just a matter of having the time to do it. if anybody's interested, feel free to pick these tasks up :) > ( A couple of others that I noticed, but are not explicitly webmaster > are: 114 and 221 ) 114: Better account system support for "trivial" accounts 221: awstats cannot be displayed I'm not sure about the current need for trivial accounts in FAS, but I'm pretty sure that 221 is still an issue. > 467 - are we planning on changing the get-fedora page for the release > of f9 ? if so, do we think we should put live media first? is that > _our_ decision to make? It can't hurt to start a discussion about it :) When I have a chance, I'll take a look at the logs for download.fedoraproject.org - if live media is more commonly downloaded, then I think it's a pretty easy choice. Otherwise, we'll want to look deeper into the target audience of that page. > which ties into # 411 ? what are we doing for the F9 release? am I > missing something on the wiki or in the tickets ? So far, I think this is just a tracking ticket for the F9 release (as described at http://fedoraproject.org/wiki/Infrastructure/SOP/Release) > and 357, RSS feeds on the home page (very cool) . Is the code > mentioned in the ticket already in the git repo and I am not seeing > it? Adding that (and an example page) in a few minutes. This is something that I'd like to have on the F9 site. > I am not certain, but I suspect we have more 'webistes' work than the > trac tickets on hosted.fp.o ? Yeah, definitely - sorry that I haven't been more active on this front - I've been caught up with FAS work for the past while. Right now, the biggest challenge for me is thinking of how to support l10n in a way that will scale well. Once we start adding pages, etc., we'll need ways to handle untranslated content, etc. Thanks for bringing these up, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From peter-sarazin at comcast.net Sun Mar 30 02:09:43 2008 From: peter-sarazin at comcast.net (Peter J. Sarazin) Date: Sat, 29 Mar 2008 21:09:43 -0500 Subject: downloading earlier versions of fedora Message-ID: <001801c8920b$1fb28d70$6400a8c0@odyssey> How do I navigate to earlier versions of fedora on your website? I want to install fedora on an older PC. Thank you. Peter J. Sarazin peter-sarazin at comcast.net http://www.PeterSarazin.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricky at fedoraproject.org Sun Mar 30 07:57:10 2008 From: ricky at fedoraproject.org (Ricky Zhou) Date: Sun, 30 Mar 2008 03:57:10 -0400 Subject: downloading earlier versions of fedora In-Reply-To: <001801c8920b$1fb28d70$6400a8c0@odyssey> References: <001801c8920b$1fb28d70$6400a8c0@odyssey> Message-ID: <20080330075710.GA9073@Max.nyc1.dsl.speakeasy.net> On 2008-03-29 09:09:43 PM, Peter J. Sarazin wrote: > How do I navigate to earlier versions of fedora on your website? > > I want to install fedora on an older PC. Currently, Fedora versions before 7 are unsupported (and current versions should run just fine on older computers). If you must, you can find older version of Fedora under the appropriate directories at http://download.fedoraproject.org/pub/fedora/linux/core/. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gradyfausta at laksmono.com Mon Mar 31 04:19:19 2008 From: gradyfausta at laksmono.com (Grady Laksmono) Date: Sun, 30 Mar 2008 21:19:19 -0700 Subject: Introduction Message-ID: Hello all, I'm Grady Laksmono and a student who would like to contribute with Fedora Website project. I'm currently a Web Programmer for College of Engineering, Computer Science, and Technology at California State University, Los Angeles. I use PHP in most of the web development work that I have done, but I'm really curious and have a high desire to learn more about Python. I'm quite new with the open source development and how can I contribute to the project, so is there any specific documentation that can help me to get started? I completed all of the checklists those are listed on the Wiki page, but I don't find information for some type of Subversions...? Thanks, Grady Laksmono www.laksmono.com From kwade at redhat.com Mon Mar 31 17:09:34 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 31 Mar 2008 10:09:34 -0700 Subject: feed'd front page ready Message-ID: <1206983374.30372.350.camel@calliope.phig.org> This weekend I worked with the RSS bits that Ricky committed last week and put together a 100% functional feed-enabled front page: http://quaid.fedorapeople.org/websites/index-rss.html Of course, that is just a static copy, the real changes are in my git checkout. I made a copy (using rsync) of my local repo to here: http://quaid.fedorapeople.org/websites/fedora-web/ The changes include a new class for fedora.css. Also, I used the rss.html that Ricky committed, changing it to be the feed using the new style, and then pulled that in to index.html with an XInclude. Took a bit of wrangling to get the CSS to work right inside of the #content class, but I finally got it done and a bit improved from last time. Unsure if this is the exact look that we want. I recommend two things: 1. We iterate on this design that I did and get it posted 2. Work on a better replacement, if/as we feel there is one needed If you all agree, I'll be glad to make the changes into fp.org/data/content/index.html directly and commit them for further review. Let me know if the git repo above is useful as-is, if I need to tweak something, or if you'd prefer that I post patches for review. - Karsten -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Mon Mar 31 17:19:49 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 31 Mar 2008 22:49:49 +0530 Subject: feed'd front page ready In-Reply-To: <1206983374.30372.350.camel@calliope.phig.org> References: <1206983374.30372.350.camel@calliope.phig.org> Message-ID: <47F11D35.6040701@fedoraproject.org> Karsten 'quaid' Wade wrote: > This weekend I worked with the RSS bits that Ricky committed last week > and put together a 100% functional feed-enabled front page: > > http://quaid.fedorapeople.org/websites/index-rss.html Change Fedora People to Planet Fedora please. Let's be consistent. Rahul From tchung at fedoraproject.org Mon Mar 31 17:44:43 2008 From: tchung at fedoraproject.org (Thomas Chung) Date: Mon, 31 Mar 2008 10:44:43 -0700 Subject: feed'd front page ready In-Reply-To: <47F11D35.6040701@fedoraproject.org> References: <1206983374.30372.350.camel@calliope.phig.org> <47F11D35.6040701@fedoraproject.org> Message-ID: <369bce3b0803311044v4568ca03ycbd912d4fe3daa1d@mail.gmail.com> On Mon, Mar 31, 2008 at 10:19 AM, Rahul Sundaram wrote: > Karsten 'quaid' Wade wrote: > > This weekend I worked with the RSS bits that Ricky committed last week > > and put together a 100% functional feed-enabled front page: > > > > http://quaid.fedorapeople.org/websites/index-rss.html > > Change Fedora People to Planet Fedora please. Let's be consistent. > > Rahul +1 -- Thomas Chung http://fedoraproject.org/wiki/ThomasChung From kwade at redhat.com Mon Mar 31 21:11:06 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 31 Mar 2008 14:11:06 -0700 Subject: feed'd front page ready In-Reply-To: <47F11D35.6040701@fedoraproject.org> References: <1206983374.30372.350.camel@calliope.phig.org> <47F11D35.6040701@fedoraproject.org> Message-ID: <1206997866.30372.419.camel@calliope.phig.org> On Mon, 2008-03-31 at 22:49 +0530, Rahul Sundaram wrote: > Karsten 'quaid' Wade wrote: > > This weekend I worked with the RSS bits that Ricky committed last week > > and put together a 100% functional feed-enabled front page: > > > > http://quaid.fedorapeople.org/websites/index-rss.html > > Change Fedora People to Planet Fedora please. Let's be consistent. Done. -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Mon Mar 31 21:31:48 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 31 Mar 2008 14:31:48 -0700 Subject: feed'd front page ready In-Reply-To: <1206983374.30372.350.camel@calliope.phig.org> References: <1206983374.30372.350.camel@calliope.phig.org> Message-ID: <1206999108.30372.432.camel@calliope.phig.org> I updated the static snapshot with some changes in the content but mainly the CSS. http://quaid.fedorapeople.org/websites/index-rss.html This style has multiple feeds in one column, with some feeds pulling only one update. For FWN, this works to put up one entry that changes weekly. Today I noticed when I rebuilt the page that the same entry for this week's FWN was up from the FWN feed and the fedora-announce-list feed. This is the state I captured in the current static page. I tried setting a bottom-border style for the
  • element, but the way the Python renders the page generates a new
  • for each item in a feed. This put a line under each title, which wasn't really needed for readability, and didn't show any separation of feeds within one column. Instead I used
    with a style wrapped in the #content
    . The
    is brought in contained in an
  • . This nicely forces a line between actual
  • elements in the source that separate the actual feed calls. It's an OK hack. How does it look visually? I tried it in white and the current dark gray. In all of this, I updated the dashed lines to dotted, to match the rest of the page style. I'll note here that all of this is solved in the single-column style that was put forth previously. I'm beginning to get interested in doing a single column version, as it would be useful under the banner widget on start.fp.o. In a single column, we can stack feed titles with the feed source: Planet Fedora Post title 1 Post title 2 Post title 3 News FWN Announcements f-announce-l feed f-dev-announce feed Fedora Stories Post title 1 Post title 2 Red Hat Magazine Post title 1 Post title 2 Dev Fu Post title 1 ... Karsten On Mon, 2008-03-31 at 10:09 -0700, Karsten 'quaid' Wade wrote: > This weekend I worked with the RSS bits that Ricky committed last week > and put together a 100% functional feed-enabled front page: > > http://quaid.fedorapeople.org/websites/index-rss.html > > Of course, that is just a static copy, the real changes are in my git > checkout. I made a copy (using rsync) of my local repo to here: > > http://quaid.fedorapeople.org/websites/fedora-web/ > > The changes include a new class for fedora.css. Also, I used the > rss.html that Ricky committed, changing it to be the feed using the new > style, and then pulled that in to index.html with an XInclude. Took a > bit of wrangling to get the CSS to work right inside of the #content > class, but I finally got it done and a bit improved from last time. > > Unsure if this is the exact look that we want. I recommend two things: > > 1. We iterate on this design that I did and get it posted > 2. Work on a better replacement, if/as we feel there is one needed > > If you all agree, I'll be glad to make the changes into > fp.org/data/content/index.html directly and commit them for further > review. Let me know if the git repo above is useful as-is, if I need to > tweak something, or if you'd prefer that I post patches for review. > > - Karsten -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: