Denis M. | 30 Mar 2013 21:17
Picon
Gravatar

Expanding categories' descriptions

Hello,

I believe it's necessary to bring this matter here. I think it's a good idea to expand the categories' descriptions (found in the corresponding metadata.xml files) with more accurate descriptions of which packages are welcome to fit in which categories.

The current descriptions are very vague and aren't probably in the best shape to bring users' a good idea what certain category is about and what packages are to be found there.

This can also be an issue for (new) ebuild-writers (either user-contributing ebuilds or just gentoo developers that are not sure about it).

This is of course checked by a gentoo developer if new ebuilds are to be submitted via the bugzilla, but I still think we should provide a better understanding of the categories.

If expanding the metadata.xml files does not seem a good idea, we should at least make a little bit more comprehensive description somewhere in the gentoo.org/doc/ or wiki.gentoo.org pages.

What do you think about it?


Regards,
Denis M. (Phr33d0m)
Sven Vermeulen | 20 Mar 2013 18:13
Picon
Favicon
Gravatar

[RFC] GDP policy updates

Hi guys,

I'd like to suggest a few changes on our GDP policy, namely:

- updating the license comment if you use a different license should be
  mandatory (hence switch from "should" to "must")

  Reason: I think this is a "typo" as "must" fits more in the idea of that
  paragraph.

- drop using metadoc.xml for registering long outstanding bugs

  Reason: it was a nice idea, but never truely used

- have project lead (or delegated person) "decide" on the recruitment
  process / progress

  Reason: we already dropped the time frame windows in the past, but wasn't
  really clear who then decides that a phase can go through or not. So make
  it explicit that it is the lead (or a delegated person)

- drop mandatory gdp quiz, make it recommended

  Reason: we already have a contribution period where the recruit sends in
  contributions or patches; the knowledge on the GuideXML, as far as needed
  for the tasks the recruit wants to do, should be apparent from the
  contributions.

  The quiz requires more knowledge than we might expect from most
  documentation developers (not in the past, but given the resources at hand
  right now, it makes sense to remove the mandatory requirement).

Below is the suggested change on the policy.

Comments are of course welcome (otherwise I wouldn't mail to the mailinglist
:-P)

Wkr,
	Sven Vermeulen

Index: doc-policy.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v
retrieving revision 1.27
diff -u -B -r1.27 doc-policy.xml
--- doc-policy.xml	29 Nov 2011 19:01:23 -0000	1.27
+++ doc-policy.xml	20 Mar 2013 17:04:40 -0000
 <at>  <at>  -186,7 +186,7  <at>  <at> 

 <p>
 If the 2.5 version is used, the tag can be either <c>&lt;license /&gt;</c> or
-<c>&lt;license version="2.5" /&gt;</c>. In either case should the comment be
+<c>&lt;license version="2.5" /&gt;</c>. In either case must the comment be
 updated to refer to the correct version URL.
 </p>

 <at>  <at>  -200,9 +200,7  <at>  <at> 
 Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
 should be handled as fast as possible. If a bug cannot be handled
 in a timely fashion, the reporter of that bug should be informed about
-this using a comment on the bug, and the bug should be registered in the
-<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if
-applicable.
+this using a comment on the bug.
 </p>

 <p>
 <at>  <at>  -377,9 +375,10  <at>  <at> 

 <p>
 If you feel that you have shown sufficient amount of contributions, contact
-the project lead of the Gentoo Documentation Project. He will ask you for your
-coordinates and other information, and then arrange for the next phase to be
-started.
+the project lead of the Gentoo Documentation Project who will review the
+contributions and the timeframe (or delegate this towards another GDP member).
+He will ask you for your coordinates and other information, and
+then arrange for the next phase to be started.
 </p>

 </body>
 <at>  <at>  -403,22 +402,20  <at>  <at> 
 </p>

 <p>
-During this period, the recruit:
+During this period, the recruit: is advised to learn about Gentoo's inner workings.
+This is required as he or she will be asked later on to answer Gentoo's <uri
+link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
 </p>

-<ul>
-  <li>
-    is advised to learn about Gentoo's inner workings.
-    This is required as he or she will be asked later on to answer Gentoo's <uri
-    link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
-  </li>
-  <li>
-    will be asked to fill in the <uri
-    link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project
-    Quiz</uri>. He or she needs to successfully pass this entire quiz
-    (all questions) before we can continue with the next Phase.
-  </li>
-</ul>
+<p>
+It is also recommended, but not automatically required, to fill in the <uri
+link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project Quiz</uri>.
+This will assist the recruit in learning more about how the Gentoo Documentation
+Project documentation works. If at a later time the Gentoo Documentation Project
+lead feels that the recruit (or by then editor or author) shows insufficient
+knowledge on this, he might ask the recruit (or by then editor or author) to
+work on the quiz after all.
+</p>

 </body>
 </section>
 <at>  <at>  -441,9 +438,9  <at>  <at> 

 <p>
 If the recruit is already a Gentoo Developer, the same recruitment process is
-followed, but the staffing quiz is not necessary anymore. However, the <uri
+followed, but of course the staffing quiz is not necessary anymore. The <uri
 link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project Quiz</uri> is
-still mandatory.
+still recommended.
 </p>

 </body>

Xavier Miller | 13 Mar 2013 09:13
Gravatar

French documentation : no more cam's French documentation information

Hello,

After some months of inactivity, some french speaking volunteers  
proposed to continue to contribute to the update of the very old  
french documentation.

I tried to get the status left by the official absent team, but the  
page with the tools is no more accessible :  
https://dev.gentoo.org/~cam/gentoo-doc-fr/ is dead.

So the volunteers cannot contribute, I will stop this volunteer lead  
and let the french documentation in the hands of the Gentoo developers.

Could you please update that documnentation or delete it ? It is too  
comfusing for french-speaking people, we get still now remarks about  
HAL (can I say "LOL" ?).

Kind regards,
Xavier Miller.

José Fournier | 27 Feb 2013 07:26
Favicon

Date problem

Hi everybody,

I am new on your list and I am trying to update the French handbook but 
I feel uncomfortable with some aspects in the translation/publication 
process. I take an example to illustrate my point.

Consider the file /doc/en/handbook/hb-install-x86+amd64-medium.xml.

According to 
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/doc/en/, 
the last EN version committed is 1.28,  committed 3 months ago.
It is also the one I translated and that Sven nicely committed for me a 
few days ago. Till now, everything seems OK.

Nevertheless, going to the Gentoo site and reading the page I can see : 
"Page updated on Feb 11, 2013" and for the French counterpart "Last 
update 1Nov 12, 2012, an original version dated Feb 11, 2013 exist (in 
French on the page of course).

My question is why this discrepancy ? The files are the same, the 
version and date tags are identical,  but the French user is made 
uncomfortable, thinking what he is reading is out of date !
If something newer exists somewhere, not already committed, there should 
be the same warning on both pages. Isn't it ? What seems very important 
to me, is that the French ( or any non English) reader is made aware 
that the French (non English) and English versions of the text match 
perfectly, releasing him/she from any doubt. Is there something I missed ?

Thank you in advance for explanation

Best regards

José

Dale | 20 Jan 2013 01:31
Picon

Re: unsubscribe

Arie <at> yahoo wrote:
body p { margin-bottom: 0cm; margin-top: 0pt; }

Try this:
List-Unsubscribe: <mailto:gentoo-doc+unsubscribe <at> lists.gentoo.org> Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Daniel Meltzer | 17 Jan 2013 06:04
Picon

[PATCH 1/3] Bring gentoo-x86-quickinstall in line with many of the changes that have been made to the official handbook. It would probably make sense down the line to turn this into a 64 bit quickinstall guide, as that's rapidly becoming the common denominator for new users. This commit makes the following changes:

* Suggest using emerge-webrsync instead of downloading a portage snapshot and
unpacking.
* Recommend mounting /sys for grub2 and other bootloader users.
* Remove the unnecessary env-update after entering chroot.
* Add ext4 to filesystems and suggest it as default for /.  We can probably remove
jfs and reiserfs from this list to keep it less overwhelming, but thats a debate
for another day.
* Additional net interfaces should be symlinked to net.lo, not net.eth0, as
net.eth0 is itself a symlink to net.lo
---
 .../doc/en/gentoo-x86-quickinstall-stage.xml       | 50 ++++++++--------------
 .../doc/en/gentoo-x86-quickinstall-system.xml      |  8 ++--
 xml/htdocs/doc/en/gentoo-x86-quickinstall.xml      | 18 ++++----
 3 files changed, 30 insertions(+), 46 deletions(-)

diff --git a/xml/htdocs/doc/en/gentoo-x86-quickinstall-stage.xml b/xml/htdocs/doc/en/gentoo-x86-quickinstall-stage.xml
index dd48c41..ccc72ee 100644
--- a/xml/htdocs/doc/en/gentoo-x86-quickinstall-stage.xml
+++ b/xml/htdocs/doc/en/gentoo-x86-quickinstall-stage.xml
 <at>  <at>  -4,8 +4,8  <at>  <at> 

 <included>

-<version>14</version>
-<date>2012-02-29</date>
+<version>15</version>
+<date>2013-01-16</date>

 <section>
 <title>Setting Up The Stage</title>
 <at>  <at>  -54,31 +54,6  <at>  <at>  user  1m2.920s
 sys   0m7.530s
 </pre>

-<p>
-Install the latest Portage snapshot. Proceed as for the stage3 archive: choose
-a nearby mirror from our <uri link="/main/en/mirrors.xml">list</uri>, download
-the latest snapshot and unpack it.
-</p>
-
-<pre caption="Download the latest Portage snapshot">
-livecd gentoo # <i>cd /mnt/gentoo/usr</i>
-livecd usr # <i>links http://www.gentoo.org/main/en/mirrors.xml</i>
-<comment>(Pick a mirror, move to the snapshots/ directory,
-highlight <b>portage-latest.tar.bz2</b> and press D to download it)</comment>
-
-<comment>(<b>Or</b> download it directly with wget without choosing a nearby mirror)</comment>
-livecd gentoo # <i>cd /mnt/gentoo/usr</i>
-livecd usr # <i>wget http://distfiles.gentoo.org/snapshots/portage-latest.tar.bz2</i>
-</pre>
-
-<pre caption="Unpack the Portage snapshot">
-livecd usr # <i>time tar xjf portage-lat*</i>
-
-real  0m40.523s
-user  0m28.280s
-sys   0m8.240s
-</pre>
-
 </body>
 </section>
 <section>
 <at>  <at>  -86,19 +61,28  <at>  <at>  sys   0m8.240s
 <body>

 <p>
-Mount the <path>/proc</path> &amp; <path>/dev</path> file systems, copy over
-the <path>/etc/resolv.conf</path> file, then chroot into your Gentoo
-environment.
+Mount the <path>/proc</path>, <path>/dev</path>, and <path>/sys</path> file 
+systems, copy over the <path>/etc/resolv.conf</path> file, then chroot into 
+your Gentoo environment.
 </p>

 <pre caption="Chroot">
 livecd usr # <i>cd /</i>
 livecd / # <i>mount -t proc proc /mnt/gentoo/proc</i>
 livecd / # <i>mount --rbind /dev /mnt/gentoo/dev</i>
-livecd / # <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/≤/i>
+livecd / # <i>mount --rbind /sys /mnt/gentoo/sys</i>
+livecd / # <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/≤/i> 
 livecd / # <i>chroot /mnt/gentoo /bin/bash</i>
-livecd / # <i>env-update &amp;&amp; source /etc/profile</i>
->>> Regenerating /etc/ld.so.cache...
+livecd / # <i>source /etc/profile</i>
+</pre>
+
+<p>
+Fetch the latest portage snapshot from the mirrors using emerge-webrsync.
+</p>
+
+<pre caption="Running emerge-webrsync to install a Portage snapshot">
+livecd / # <i>mkdir /usr/portage</i>
+livecd / # <i>emerge webrsync</i>
 </pre>

 </body>
diff --git a/xml/htdocs/doc/en/gentoo-x86-quickinstall-system.xml b/xml/htdocs/doc/en/gentoo-x86-quickinstall-system.xml
index b4b7e45..34c7b5e 100644
--- a/xml/htdocs/doc/en/gentoo-x86-quickinstall-system.xml
+++ b/xml/htdocs/doc/en/gentoo-x86-quickinstall-system.xml
 <at>  <at>  -4,8 +4,8  <at>  <at> 

 <included>

-<version>7</version>
-<date>2012-03-31</date>
+<version>8</version>
+<date>2013-01-16</date>

 <section>
 <title>Configure the system</title>
 <at>  <at>  -22,7 +22,7  <at>  <at>  file systems match your installation.
 livecd linux # <i>cd /etc</i>
 livecd etc # <i>nano -w fstab</i>
 /dev/≤i>sda1</i>   /boot     ext2    noauto,noatime     1 2
-/dev/≤i>sda3</i>   /         ext3    noatime            0 1
+/dev/≤i>sda3</i>   /         ext4    noatime            0 1
 /dev/≤i>sda2</i>   none      swap    sw                 0 0
 </pre>

 <at>  <at>  -58,7 +58,7  <at>  <at>  livecd etc # <i>nano -w fstab</i>
 <p>
 Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</c>
 init script to the default run level. If you have multiple NICs, symlink them
-to the <c>net.eth0</c> init script and add them to the default run level as
+to the <c>net.lo</c> init script and add them to the default run level as
 well. Don't forget to set your hostname too. Either edit
 <path>/etc/conf.d/net</path> and <path>/etc/conf.d/hostname</path> with
 <c>nano</c> or use the following commands:
diff --git a/xml/htdocs/doc/en/gentoo-x86-quickinstall.xml b/xml/htdocs/doc/en/gentoo-x86-quickinstall.xml
index 06200d0..90f010d 100644
--- a/xml/htdocs/doc/en/gentoo-x86-quickinstall.xml
+++ b/xml/htdocs/doc/en/gentoo-x86-quickinstall.xml
 <at>  <at>  -29,8 +29,8  <at>  <at>  want to follow this guide.
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>

-<version>27</version>
-<date>2012-03-31</date>
+<version>28</version>
+<date>2013-01-16</date>

 <chapter>
 <title>Introduction</title>
 <at>  <at>  -112,17 +112,17  <at>  <at>  Units = cylinders of 16065 * 512 = 8225280 bytes
 </pre>

 <p>
-Use <c>mke2fs</c>, <c>mke2fs -j</c>, <c>mkreiserfs</c>, <c>mkfs.xfs</c> and
-<c>mkfs.jfs</c> to create file systems on your Linux partitions. Initialize your
-swap partition using <c>mkswap</c> and <c>swapon</c>.
+Use <c>mkfs.ext2</c>, <c>mkfs.ext3</c>, <c>mkfs.ext4</c>, <c>mkreiserfs</c>, 
+<c>mkfs.xfs</c> and <c>mkfs.jfs</c> to create file systems on your Linux 
+partitions. Initialize your swap partition using <c>mkswap</c> and <c>swapon</c>.
 </p>

 <pre caption="Create the file systems and activate swap">
 <comment>(ext2 is all you need on the /boot partition)</comment>
-livecd ~ # <i>mke2fs /dev/sda1</i>
+livecd ~ # <i>mkfs.ext2 /dev/sda1</i>

-<comment>(Let's use ext3 on the main partition)</comment>
-livecd ~ # <i>mke2fs -j /dev/sda3</i>
+<comment>(Let's use ext4 on the main partition)</comment>
+livecd ~ # <i>mkfs.ext4 /dev/sda3</i>

 <comment>(Create and activate swap)</comment>
 livecd ~ # <i>mkswap /dev/sda2 &amp;&amp; swapon /dev/sda2</i>
 <at>  <at>  -204,7 +204,7  <at>  <at>  Exit the chrooted environment, unmount all file systems and reboot:
 <pre caption="Reboot">
 livecd conf.d # <i>exit</i>
 livecd / # <i>umount -l /mnt/gentoo/dev{/shm,/pts,}</i>
-livecd / # <i>umount -l /mnt/gentoo{/proc,/boot,}</i>
+livecd / # <i>umount -l /mnt/gentoo{/proc,/boot,/sys,}</i>
 livecd / # <i>reboot</i>
 <comment>(Don't forget to remove the CD)</comment>
 </pre>
--

-- 
1.7.12.4

Daniel Meltzer | 17 Jan 2013 05:59
Picon

Some Updates to the Quick Install Guide

Hello Everyone.

I recently reinstalled gentoo after a long hiatus, and noticed that a
lot of documentation has aged a bit over time and grown out of sync.
Being that I dislike this, I'm setting out to try and clean some of it
up.  My first project was updating the quickinstall guide to reflect
some of the changes that have been made to the handbook over the last
few years.  I doubt I have covered all of them, but I think this takes
care of the glaring differences.  I'm going to send these along via
the fancy git commands this time.  If you want me to make them go to
bugzilla in the future I'll be happy to do that, this just seemed like
a more approachable first step. 

I think it would make sense to turn this into a x86/amd64 combined
guide as well, I haven't started on that yet but with the prevelance
of 64bit systems these days the x86 is kind of falling by the wayside.
Please take a look at these patches, and let me know what you think.
I will send more as time permits.

Thanks,

Dan.

Sven Vermeulen | 7 Oct 2012 10:21
Picon
Favicon
Gravatar

Removal of link attribute in guide.dtd

Hi guys,

I will be removing the link attribute within the guide.dtd soon so that
newly committed changes (and documents) cannot use the "<guide link=.../>"
stuff anymore. See also bug #379883 [1].

Wkr,
	Sven Vermeulen

[1] https://bugs.gentoo.org/show_bug.cgi?id=379883

Sergey Tumanov | 3 Sep 2012 16:20
Picon

Documentation translation

Hi, friends!

Sorry for writing for the second time: recently I've got hundreds of 
SPAM e-mail on my request. Sending it ones again.

My name is Sergey, I'm from Moscow Russia!

On the gentoo official website I didn't find any translation to Russian. 
I know there are some old documents, but it's written that they are not 
actual. Do you need some support in translation of documentation to 
Russian? If yes, please provide me with contact and information what 
should be done.

Kind regards,
Sergey

boxoffice | 3 Sep 2012 12:49

Barn Theatre Box Office

Thank you for contacting the Barn Theatre Box Office!

As a organization staffed entirely by volunteers, we're sorry we may not get to your note as quickly as an
organization with a full-time staff.

But rest assured that during production weeks, we are monitoring this mailbox on a daily basis (more often
than that, actually!), and you *will* receive a response and/or confirmation from us regarding your
ticket request!

**Please note:  we are NOT able to take/confirm reservations if your request is within 24 hours of the
performance you wish to attend.So if you would like tickets for a performance that is *less* than 24 hours
away, please do NOT make a reservation.  Instead, please come to the Box Office at least 20 minutes before
that performance and we will do our best to accommodate your request!

Thank you again for your ticket inquiry -- we will be in touch and we look forward to seeing you at The Barn!

[This is an automated response.

boxoffice | 3 Sep 2012 12:48

Barn Theatre Box Office

Thank you for contacting the Barn Theatre Box Office!

As a organization staffed entirely by volunteers, we're sorry we may not get to your note as quickly as an
organization with a full-time staff.

But rest assured that during production weeks, we are monitoring this mailbox on a daily basis (more often
than that, actually!), and you *will* receive a response and/or confirmation from us regarding your
ticket request!

**Please note:  we are NOT able to take/confirm reservations if your request is within 24 hours of the
performance you wish to attend.So if you would like tickets for a performance that is *less* than 24 hours
away, please do NOT make a reservation.  Instead, please come to the Box Office at least 20 minutes before
that performance and we will do our best to accommodate your request!

Thank you again for your ticket inquiry -- we will be in touch and we look forward to seeing you at The Barn!

[This is an automated response.


Gmane