Re: Release notes and wgo revamp

["Quim Gil" <quimgil gmail com>]

Hi,

Diego:

> I see, I just read something about that on the wiki.

We spent literally months planning and also documenting in wiki pages
what we planned. I recommend you to pick one task (and only one task
to start with), make sure you know everything about it and then
execute until you complete it. Then another one. Choose your task,
please.


Claus:

> you want to move WGO to the new system
> althought you didn't convert any of the old content yet.

The plan was to build a revamped wgo and then substitute the current
wgo on March 14th. I'm suggesting to keep the plan, if possible. We
won't wipe out the current wgo if we haven't been able to produce
something better by then, obviously.

> what happens to the old URLs that other pages and sites
> link to? Didn't we say the revamp should not break stuff if possible?

Now I see that we didn agree a policy about this. Feel free to suggest
one: http://live.gnome.org/GnomeWeb/WebPolicies . However, what we
said is that no old URLs should break and good use of redirects needs
to be done. But this is nothing new, since the beginning we knew that
we would create a lot of URLs different than the current ones.

> what you mean by keeping the release notes
> "simple and create part of their content as GNOME Products pages".

In fact the important question now is who is going to coordinate the
2.18 release notes. As usual, the person driving will set most of the
rules of the game. Without that person is quite useless that we start
discussing what to do, as we proved in the 2.16 process.

> Moving to the Plone system now will just make things worse.
> Try doing it for 2.20

Thanks for the advice. I insist: no move will be done if the revamped
site is not ready by March 14th. To me there is not anything worse
that keep this revamp stalled.

My point of view is that the work needs to be done anyway., If it's
ready for 2.18, great. If not let's see if we have it for 2.18.1. If
not, let's discuss what to do. There is no point for me to keep my
arms crossed now that I want to invest time again on this. I still
have a board assignment to revamp wgo. You can keep contributing to
the revamp as you prefer.


> There is content at the current WGO. In fact, lots of content.

Of course, who has forgotten that? We have got always in mind that
useful content needs to be migrated. This is a factor that can help us
getting the work done before the 2.18 deadline. Migrating content to a
CMS is technically quite straightforward, once you know what you want
to move and where.

Joachim:

I like very much this topic, this is why I started a series of blog
posts trying to shake up ideas:
http://desdeamericaconamor.org/blog/free-software-and-its-writers . I
wish I could  share a fruitful discussion now, but at this point I
feel more like investing my GNOME time in JFDI.

Activity usually helps getting active people. Inactivity usually helps
loosing inactive people. There are too many exceptions to make a
principle from this, but at least being active your are more likely to
get things done.  :)

--
Quim Gil /// http://desdeamericaconamor.org