From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Cc: Theo Chatzimichos <tampakrap@gentoo.org>, dberkholz@gentoo.org
Subject: [gentoo-doc] okupy, a Django rewrite of www.g.o
Date: Thu, 02 Jun 2011 12:13:10 +0200 [thread overview]
Message-ID: <4DE76236.5010704@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2863 bytes --]
Hi,
yesterday I read Theo's blog post [1] about his upcoming GSoC project,
which apparently is about using Django for www.g.o, and has some
implications for the way how the GDP works.
I have a few comments/notes that I want to say here. They reflect my
personal opinion, which is based on six years of working with docs. I
have no idea whether they match the opinion of the rest of the GDP.
First of all, a suggestion -- maybe, when you want to do something to
the docs (like change the presentation layer, integrate a WYSIWYG
editor, convert to git from CVS, or stuff like that -- which are all the
objectives of the project [2]), maybe it would be a great idea to
contact the GDP first. There are fine contacts for chatting with us,
either the nice gentoo-doc ML, or the #gentoo-doc IRC channel, or the
docs-team@g.o alias. I have no idea whether Theo contacted anyone
directly, but I'm sure I haven't received anything through any of these
channels. That's bad, and it means that there's a communication problem
somewhere.
The project description speaks about a perceived problem with editing
the GuideXML files. This issue has been raised many times. My impression
is that people failed to support that assertion with anything
substantial; the people who argue that "there should be something" are
typically not doing much GDP work. That impression might be flawed, of
course.
Theo also mentions that "By all appearances Gorg has been abandoned as a
project. This has resulted in difficulty in maintaining the Gentoo
website, and also makes the work of updating the website's design or
functionality all the more troublesome." and goes on to mention that
"Gorg as an abandoned project is suffering from bugs that get pilled up,
not to mention possible security risks that may arise". Can I ask for a
reference to the "bugs that get pilled up", and to Gorg resulting in
"difficulty in maintaining the Gentoo website"?
Please don't get me wrong, I certainly do not want to hinder any efforts
targeted at making our website better, or our workflow faster for those
that really contribute. I just tend to get slightly upset when I see an
approved GSoC project which will, IMHO, fundamentally change the way how
GDP works, then read a few assertions that fail to persuade me, and
realize that I can't find any notice of what is going to happen until
after the project got approved -- that's a sure way to piss me of.
Anyway, I really hope I'm just a weird, grumpy guy who somehow missed a
well-targeted discussion. Hence, please do correct my impressions.
In the meanwhile, have fun
Jan
[1] http://blogs.gentoo.org/tampakrap/accepted-for-gentoo-gsoc-2011/
[2]
http://www.google-melange.com/gsoc/project/google/gsoc2011/tampakrap/27001
--
Trojita, a fast e-mail client -- http://trojita.flaska.net/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2011-06-02 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:13 Jan Kundrát [this message]
2011-06-02 10:29 ` [gentoo-doc] Re: okupy, a Django rewrite of www.g.o Theo Chatzimichos
2011-06-02 11:47 ` Jan Kundrát
2011-06-02 11:54 ` Theo Chatzimichos
2011-06-02 12:15 ` Jan Kundrát
2011-06-02 17:22 ` wireless
2011-06-02 18:35 ` Nils Larsson
2011-06-05 22:51 ` Jan Kundrát
2011-06-07 9:35 ` Joshua Saddler
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=4DE76236.5010704@gentoo.org \
--to=jkt@gentoo.org \
--cc=dberkholz@gentoo.org \
--cc=gentoo-doc@lists.gentoo.org \
--cc=tampakrap@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