On Tuesday 10 January 2006 19:44, Stuart Herbert wrote:
>
> Why not just let herds carry on creating entries under /proj/en/? If
> they're part of a larger project, that project can just link to the
> herd's page. Our directory structure doesn't have to reflect a
> biological classification tree
On Tuesday 10 January 2006 16:09, Michael Cummings wrote:
> I have to side with lance on this one (ouch) - i have some docs i'd
> love to post for perl herd related stuff, but we are by no means a
> project, nor do we fit nicely into anything.
>
> *sigh* now there's the story of my life in a nutshe
On Tuesday 10 January 2006 15:20, Lance Albertson wrote:
> Donnie Berkholz wrote:
> > Lance Albertson wrote:
> > | I understand the block was lifted for projects, but that doesn't
> > | mean herds should all should fit underneath proj/.
> >
> > I agree. What I meant is that herds should be grouping
Ciaran McCreesh wrote: [Fri Jan 13 2006, 08:48:21AM CST]
> Very easy to screw up, especially since docutils goes to great lengths
> to create output even if the input is highly weird. My own parser moans
> on anything like that -- it disallows most nested structure markup --
> which means it's usel
On Tue, 10 Jan 2006 15:12:27 -0600 Lance Albertson
<[EMAIL PROTECTED]> wrote:
| Last I knew, its not a simple task for generating those nice looking
| html pages that ciaranm made a while back for the developer docs.
| When I asked him about (he can probably provide more detail), It took
| a lot of
Sven Vermeulen wrote:
Lance Albertson said:
I can probably setup toucan to use gorg in some fashion if I had a few
folks to test it with. I'm sure that would make things easier for a lot
of people for rendering things.
Since documentation posted on dev.gentoo.org isn't Gentoo's by default, i
Lance Albertson said:
> I can probably setup toucan to use gorg in some fashion if I had a few
> folks to test it with. I'm sure that would make things easier for a lot
> of people for rendering things.
Since documentation posted on dev.gentoo.org isn't Gentoo's by default, it
might not be a good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stuart Herbert wrote:
| Don't you think that maybe you're trying to bash square pegs into
| round holes just for the sake of some sort of order that perhaps
| doesn't actually benefit anyone at all?
|
| Where did the requirement that a herd has to be
Lance Albertson wrote:
> Aron Griffis wrote:
>> Grant Goodyear wrote:[Tue Jan 10 2006, 11:09:15AM EST]
>>
>>> As an aside, it's ciarnanm has already put work in on developing an RST to
>>> guidexml converter, so I wouldn't worry too much about RST not scaling.
>>
>> Could that be used dynam
Aron Griffis wrote:
> Grant Goodyear wrote: [Tue Jan 10 2006, 11:09:15AM EST]
>
>>As an aside, it's ciarnanm has already put work in on developing an RST to
>>guidexml converter, so I wouldn't worry too much about RST not scaling.
>
>
> Could that be used dynamically on the server? The last tim
Hi Donnie,
On 1/10/06, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Donnie Berkholz wrote:
> | I don't want to get into the habit of inconsistency and finding herds in
> | two different locations.
>
> To clarify, add an "either" onto the end of t
Grant Goodyear wrote: [Tue Jan 10 2006, 11:09:15AM EST]
> As an aside, it's ciarnanm has already put work in on developing an RST to
> guidexml converter, so I wouldn't worry too much about RST not scaling.
Could that be used dynamically on the server? The last time I was
familiar with the gent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I don't want to get into the habit of inconsistency and finding herds in
| two different locations.
To clarify, add an "either" onto the end of that.
| Thanks,
| Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| But herd != project. They are two distinct things. There are a couple of
| cases where they both are the same, but others where it isn't. For
| example, what project would netmon fit under? They aren't actively
| trying to cre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| Chris Gianelloni wrote:
|>I think that would be a wonderful idea. What would we do about herds
|>that are a project? Simply throw in a redirect under the herd name to
|>the project name?
|>
|
|
| Unless they already reside i
Lance Albertson wrote: [Tue Jan 10 2006, 12:00:03AM CST]
> What if instead of having proj/en we did herd/en on www? Of course, that
> doesn't help the whole "GuideXML is hard" bit. I like the idea of using
> RST, but it doesn't seem very scalable at this time. Maybe, instead of
> that, we created s
On Tue, 2006-01-10 at 08:20 -0600, Lance Albertson wrote:
> But herd != project. They are two distinct things. There are a couple of
> cases where they both are the same, but others where it isn't. For
> example, what project would netmon fit under? They aren't actively
> trying to create a specifi
Donnie Berkholz wrote:
> Lance Albertson wrote:
> | I understand the block was lifted for projects, but that doesn't mean
> | herds should all should fit underneath proj/.
>
> I agree. What I meant is that herds should be grouping together to form
> new projects if they don't fit in an existing o
Chris Gianelloni wrote:
> On Tue, 2006-01-10 at 01:17 -0600, Lance Albertson wrote:
>
>>I understand the block was lifted for projects, but that doesn't mean
>>herds should all should fit underneath proj/. I think we should open up
>>a similar space just for herds.
>
>
> I think that would be a
Chris Gianelloni said:
> Really, I think that the number of bugs the GDP gets is probably fairly
> minimal for project-based documentation. Perhaps we could have
> something added to the project dtd that adds a little blurb at the
> bottom to file bugs for project documentation against the project
On Tue, 2006-01-10 at 01:17 -0600, Lance Albertson wrote:
> I understand the block was lifted for projects, but that doesn't mean
> herds should all should fit underneath proj/. I think we should open up
> a similar space just for herds.
I think that would be a wonderful idea. What would we do ab
On Mon, 2006-01-09 at 22:54 -0800, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sven Vermeulen wrote:
> | We have already received many bugs for documentation in /proj/* which is
> | not GDPs. I had no issue with this as I hoped this would be a transient
> | state w
Donnie Berkholz wrote:
> Sven Vermeulen wrote:
> | We have already received many bugs for documentation in /proj/* which is
> | not GDPs. I had no issue with this as I hoped this would be a transient
> | state where the documentation is eventually handed over to the GDP so
> that
> | both the proje
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| Donnie Berkholz wrote:
|
|>Lance Albertson wrote:
|>| What if instead of having proj/en we did herd/en on www? Of course, that
|>| doesn't help the whole "GuideXML is hard" bit. I like the idea of using
|>| RST, but it doesn't
On Tue, 10 Jan 2006 01:17:06 -0600
Lance Albertson <[EMAIL PROTECTED]> wrote:
> Donnie Berkholz wrote:
> > Lance Albertson wrote:
> > | What if instead of having proj/en we did herd/en on www? Of
> > course, that | doesn't help the whole "GuideXML is hard" bit. I
> > like the idea of using | RST,
Donnie Berkholz wrote:
> Lance Albertson wrote:
> | What if instead of having proj/en we did herd/en on www? Of course, that
> | doesn't help the whole "GuideXML is hard" bit. I like the idea of using
> | RST, but it doesn't seem very scalable at this time. Maybe, instead of
> | that, we created so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| What if instead of having proj/en we did herd/en on www? Of course, that
| doesn't help the whole "GuideXML is hard" bit. I like the idea of using
| RST, but it doesn't seem very scalable at this time. Maybe, instead of
| that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Vermeulen wrote:
| We have already received many bugs for documentation in /proj/* which is
| not GDPs. I had no issue with this as I hoped this would be a transient
| state where the documentation is eventually handed over to the GDP so that
| b
Sven Vermeulen wrote:
> On Sun, Jan 08, 2006 at 06:45:01PM +, Luis Medinas wrote:
>
>>We could start a public wiki displaying all herds and projects. It would
>>be great to add some low level docs, herds/project goals, ideas and so.
>>Even the users could be allowed to edit and share informati
On Sun, Jan 08, 2006 at 06:45:01PM +, Luis Medinas wrote:
> We could start a public wiki displaying all herds and projects. It would
> be great to add some low level docs, herds/project goals, ideas and so.
> Even the users could be allowed to edit and share information.
I would personally wel
On Monday 09 January 2006 21:04, Tom Martin wrote:
> The devmanual has an an enormous number of links, citations and cross
> references. I'd imagine that's what really takes time to generate. For
> things like this, it would be very fast.
Might be good to test moinmoin's RST support then.
--
Dieg
On Mon, 9 Jan 2006 18:11:42 +0100
"Diego 'Flameeyes' Pettenò" <[EMAIL PROTECTED]> wrote:
> And IIRC ciaranm said it took quite a while to render the devmanual
> from RST to HTML, would be difficult to sync hourly then.
The devmanual has an an enormous number of links, citations and cross
referenc
Grant Goodyear wrote:
> Diego 'Flameeyes' Pettenò wrote: [Sun Jan 08 2006, 11:59:40AM CST]
>
>>I originally thought of putting it on my devspace, but using GuideXML
>>there is a bit tricky, at least for me (as xsltproc seems to refuse
>>working on the pure xml directly).
>
>
> I actually prefer
Grant Goodyear wrote:
> Again, I like devspace for these things. Of course, particularly useful
> docs would likely be adopted by the GDP (with the permission of the
> author, of course).
Thinking about legal issues (and about tracking all contributors among
developers) - please use CC-BY-SA [1]
Diego 'Flameeyes' Pettenò wrote: [Sun Jan 08 2006, 11:59:40AM CST]
> I originally thought of putting it on my devspace, but using GuideXML
> there is a bit tricky, at least for me (as xsltproc seems to refuse
> working on the pure xml directly).
I actually prefer devspace for these sorts of docs.
On Mon, 9 Jan 2006 16:47:57 +
Tom Martin <[EMAIL PROTECTED]> wrote:
> On Mon, 9 Jan 2006 09:34:22 -0500
> Aron Griffis <[EMAIL PROTECTED]> wrote:
>
> > Brian Harring wrote:[Sun Jan 08 2006, 09:16:36PM EST]
> > > Regardless, (imo) it's already been laid out why guideXML'ifying
> > > e
Sending this to the ml, tom already has heard the reasons but throwing
them out for others to comment on...
On Mon, Jan 09, 2006 at 04:47:57PM +, Tom Martin wrote:
> > I realize this doesn't address the *rest* of what you said, though...
> These little 'howtos' are potentially very short,
On Sunday 08 January 2006 18:59, Diego 'Flameeyes' Pettenò wrote:
> Okay let's forget the flames and talk about something related to
> practical development today :)
Sigh ok no practical development at this come out as a discussion/flame again.
What I was thinking of is _not_:
- a wiki writable
On Mon, 9 Jan 2006 09:34:22 -0500
Aron Griffis <[EMAIL PROTECTED]> wrote:
> Brian Harring wrote: [Sun Jan 08 2006, 09:16:36PM EST]
> > Regardless, (imo) it's already been laid out why guideXML'ifying
> > everything doesn't totally work. Three reasons...
> >
> > A) bit of work required just to
Brian Harring wrote:[Sun Jan 08 2006, 09:16:36PM EST]
> Regardless, (imo) it's already been laid out why guideXML'ifying
> everything doesn't totally work. Three reasons...
>
> A) bit of work required just to jot down a quick list of "this is
> broke, fix it" that's going to be thrown out 2
On Monday 09 January 2006 03:14, Marius Mauch wrote:
> Find a nice place in www.gentoo.org/proj/
Okay that's what I try to do most of the time, in this specific case, I'm
probably going to ask for space to qa project (as fixing --as-needed problems
or parallel make issues and such is imho QA-rela
On Sun, Jan 08, 2006 at 11:30:16PM +, Stuart Herbert wrote:
> On Sun, 2006-01-08 at 12:54 -0600, Lance Albertson wrote:
> > > We could start a public wiki displaying all herds and projects. It would
> > > be great to add some low level docs, herds/project goals, ideas and so.
> > > Even the use
On Sun, 8 Jan 2006 18:59:40 +0100
"Diego 'Flameeyes' Pettenò" <[EMAIL PROTECTED]> wrote:
> I originally thought of putting it on my devspace, but using GuideXML
> there is a bit tricky, at least for me (as xsltproc seems to refuse
> working on the pure xml directly).
>
> So I was thinking if we h
On Sun, 2006-01-08 at 12:54 -0600, Lance Albertson wrote:
> > We could start a public wiki displaying all herds and projects. It would
> > be great to add some low level docs, herds/project goals, ideas and so.
> > Even the users could be allowed to edit and share information.
>
> Anything like th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
> Luis Medinas wrote:
>
>>On Sun, 2006-01-08 at 12:54 -0600, Lance Albertson wrote:
>
>
> I had thought about creating some kind of a site like this, but not
> necessarily in a wiki form. I don't like the idea of letting user
On Sunday 08 January 2006 19:07, Renat Lumpau wrote:
> Devwiki
i thought of devwiki when I started writing Gentoo/Alt documentation. I then
discarded the idea for a series of reason, the first of which is the one
already stated by Brian, that the docs results unreadable by non-devs, and
also not
On Sun, 2006-01-08 at 13:31 -0600, Lance Albertson wrote:
> > Indeed it's GDP area but to expose project goals, status and low level
> > docs isn't even related with GDP. We can't maintain the high level of
> > docs like GDP does and it's not even your goal. I think the public wiki
> > idea will im
Luis Medinas wrote:
> On Sun, 2006-01-08 at 12:54 -0600, Lance Albertson wrote:
>
Devwiki is effectively inaccesable to non gentoo folks (whether in
access, or in navigating the beast), thus it's a no go.
Any docs generated should be googable imo.
>>>
>>>
>>>We could start a publ
On Sun, 2006-01-08 at 12:54 -0600, Lance Albertson wrote:
> >>Devwiki is effectively inaccesable to non gentoo folks (whether in
> >>access, or in navigating the beast), thus it's a no go.
> >>
> >>Any docs generated should be googable imo.
> >
> >
> > We could start a public wiki displaying all
Luis Medinas wrote:
> On Sun, 2006-01-08 at 10:31 -0800, Brian Harring wrote:
>
>>On Sun, Jan 08, 2006 at 06:07:48PM +, Renat Lumpau wrote:
>>
>>>On Sun, Jan 08, 2006 at 06:59:40PM +0100, Diego 'Flameeyes' Petten? wrote:
>>>
GDP might be the place where to put them, but as they are mainly
Brian Harring wrote:
> On Sun, Jan 08, 2006 at 06:07:48PM +, Renat Lumpau wrote:
>
>>On Sun, Jan 08, 2006 at 06:59:40PM +0100, Diego 'Flameeyes' Petten? wrote:
>>
>>>GDP might be the place where to put them, but as they are mainly
>>>developer-oriented, they might be better accessed directly
On Sun, 2006-01-08 at 10:31 -0800, Brian Harring wrote:
> On Sun, Jan 08, 2006 at 06:07:48PM +, Renat Lumpau wrote:
> > On Sun, Jan 08, 2006 at 06:59:40PM +0100, Diego 'Flameeyes' Petten? wrote:
> > > GDP might be the place where to put them, but as they are mainly
> > > developer-oriented, th
On Sun, Jan 08, 2006 at 06:07:48PM +, Renat Lumpau wrote:
> On Sun, Jan 08, 2006 at 06:59:40PM +0100, Diego 'Flameeyes' Petten? wrote:
> > GDP might be the place where to put them, but as they are mainly
> > developer-oriented, they might be better accessed directly by devs (at
> > least
> >
On Sun, Jan 08, 2006 at 06:59:40PM +0100, Diego 'Flameeyes' Petten? wrote:
> GDP might be the place where to put them, but as they are mainly
> developer-oriented, they might be better accessed directly by devs (at least
> for the first steps until they are drafts).
>
> What people think about t
Okay let's forget the flames and talk about something related to practical
development today :)
As people reading my blog might already know, I've been experimenting with
--as-needed LDFLAG in the past days. It seems pretty stable when you don't
have GNOME installed (as many libraries from GNOM
55 matches
Mail list logo
