From: "Alec Warner" <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] {Guide,Project,Foo}XML too confusing for many devs?
Date: Mon, 26 Mar 2007 08:05:58 -0700 (PDT) [thread overview]
Message-ID: <52589.67.180.39.52.1174921558.squirrel@webmail.scriptkitty.com> (raw)
First off, this is not a discussion on why XML sucks, or why we shouldn't
be using XML or anything like that. This is not a discussion about what
we should be using instead of XML. This is a discussion about using XML
for our webpages.
Many projects have old and nasty webpages. This has been a problem within
gentoo since before I arrived and probably has been a problem since we
started having webpages. One of the issues I wish to address is whether
or not writing webpages in XML (Guide or Project or something_else) is
just too much of a barrier for many people. I've personally always been
pretty much a 'copy something that works and edit the bits I need' kind of
a guy. There is certainly a large body of work to steal^H^H^H^H^Hcopy
from. However when something you are working on doesn't fit inside of
something that has already been done it becomes very difficult to make it
'fit' into our existing XML structure.
This forces you to either ask for help from the masters of GuideXML (aka
the Docs team) or try and figure out how the hell to write the xsl and
dtd's yourself, or give up. Personally I think most people end up at the
latter case (the giving up one). I know developers that won't even touch
any webpages at all; I can only assume that they just hate XML long time
and find the whole issue of writing pages complicated and burdoning.
So this is getting pretty long winded; my basic question is do you as a
developer find writing web pages to be confusing or difficult? Is there
not a good tutorial for learning our webpage XML syntax? Do you find that
you bump up against restrictions in the DTD or other problems that prevent
you from expressing yourself properly? Do you have any idea how to
actually go about extending GuideXML (or the other XML's we provide) Have
you ever tried? Could we improve training with regards to any of this?
Thanks,
-Alec
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2007-03-26 15:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 15:05 Alec Warner [this message]
2007-03-26 15:29 ` [gentoo-dev] {Guide,Project,Foo}XML too confusing for many devs? Chris Gianelloni
2007-03-26 15:49 ` William L. Thomson Jr.
2007-03-26 22:34 ` Paul de Vrieze
2007-03-26 15:56 ` Kevin F. Quinn
2007-03-26 17:01 ` Mike Bonar
2007-03-26 18:50 ` Chris Gianelloni
2007-03-28 12:29 ` Vlastimil Babka
2007-03-28 15:50 ` Chris Gianelloni
2007-03-26 17:45 ` Mike Frysinger
2007-03-26 18:16 ` "José Luis Rivero (yoswink)"
2007-03-26 20:35 ` Dawid Węgliński
2007-03-26 18:53 ` Catalin Zamfir Alexandru
2007-03-26 19:05 ` Jakub Moc
2007-03-26 19:15 ` "José Luis Rivero (yoswink)"
2007-03-26 19:46 ` Lars Weiler
2007-03-26 22:15 ` Chris Gianelloni
2007-03-26 22:38 ` Paul de Vrieze
2007-03-27 0:59 ` [gentoo-dev] {Guide,Project, Foo}XML " Alec Warner
2007-03-28 8:13 ` Denis Dupeyron
2007-03-28 8:49 ` Josh Saddler
2007-03-28 11:32 ` Paul de Vrieze
2007-03-28 12:08 ` Denis Dupeyron
2007-03-28 13:10 ` Paul de Vrieze
2007-03-26 21:36 ` [gentoo-dev] {Guide,Project,Foo}XML " Anant Narayanan
2007-03-28 12:33 ` Vlastimil Babka
2007-03-28 19:44 ` Anant Narayanan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52589.67.180.39.52.1174921558.squirrel@webmail.scriptkitty.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox