KDevelop Website

[Milian Wolff]

Hey you two, I'll replay to both of you in this mail.

Amilcar do Carmo Lucas, 04.01.2011:
> On 01/03/2011 04:24 PM, Sam S. wrote:
> >> Please add those to the git repo of the website.
> > 
> > Ok, I will.
> > 
> > Btw, have you decided on a workflow for adding/editing website content
> > yet? If I understood correctly one concern with the old website was that
> > it didn't make it easy for people to contribute/improve content, since
> > all changes had to be manually applied by the webmaster.
> > Now that the website uses a CMS (Drupal) with advanced user management
> > capabilities, you could allow more permissive (but still safe and
> > moderated) work-flow rules.

I've already created two roles "editor" and "admin". Editor can do pretty much 
everything besides core administrations, while the latter can do everything. 
Most contributors to KDevelop that registered an account got into the latter 
group as I trust you all.

> > For example, I would suggest the following:
> >    - Everyone who is not specifically blocked by the webmaster(s) can
> > 
> > freely create an account. (Ideally, accounts would be shared between
> > website and wiki, but I don't know if that's possible.)

OpenID is enabled. And right now the registration is moderated since I don't 
want random people to get extended rights. This kind of reviewing is simple 
and I think I'll keep it in place.

> >    - Everyone with an account can freely edit existing nodes or
> > 
> > add/edit translations for existing nodes
> > 
> >    - However, edits by "normal" accounts don't get published
> > 
> > automatically, but are instead saved as pending revisions
> > 
> >    - "Moderators" can publish pending revisions at any time (and also
> > 
> > revert to previous revisions, etc.)
> > 
> >    - All KDevelop "core developers" could be given moderator
> > 
> > privileges, in order to not put the burden on a single webmaster

While this sounds nice, I doubt it will work. Rather I'd like to have a bunch 
of people I trust with accounts to create and edit content freely. After all I 
doubt many of us will start to keep an eye on the website and review new 
stuff. I'd rather get rid of any such bureaucracy. The initial "apply for 
account" step should be enough. If not, we can always change that later.

> > Dupal core in combination with the Revisioning
> > (http://drupal.org/project/revisioning) module can take care of all of
> > this, and also provide a nice "pending revisions" list.

This sounds interesting. I was looking for a way to force new revisions for 
any kind of editing on nodes. This might do the job, will have to review it 
later. Thanks.

> > It also allows to apply these workflow rules on a per-content-type
> > basis, so for example nodes of type "News Item" and "KDevelop release"
> > could be exempt from collaborative editing and only editable by the
> > webmaster / release-coordinator, respectively.

I think this will work fine without any extended access management here. After 
all I do the releases, hence I'll probably also write the release 
announcement. If someone wants to write a news for KDevelop, go for it. I 
expect everyone to handle in his best intends for KDevelop and if in doubt 
will ask the team.

> > What do you think?
> > 
> > The only thing I'm not sure how well this "revisioning" stuff would
> > work with, is translations (because I've never tried that).
> > But hopefully it can somehow be set up to work together cleanly.
> > (I do assume you intend to make the website fully translatable, like
> > the old one? It seems you'll need the i18n
> > (http://drupal.org/project/i18n) module for that, and, for a smooth UI
> > &  workflow experience, most likely some additional helper modules on
> > top of that.)

Right, eventually I do think that we can offer people to translate the 
website. But it's low-prio right now. Getting (good) content in english should 
be the first thing to do ;-)

> I like your plan.
> I prupose the following roadmap:
> Use January to get the website in shape.

I think this can be done, haven't had any time the past days but hope to get 
more done this week. Also dereine (a Drupal developer) helped out already to 
port some sites. Many thanks for that.

> Transfer the kdevelop.org domain once the new website is stable.
> Keep the kdevelop.de domain for the old website.

I'd rather have something like legacy.kdevelop.org or similar and forward 
kdevelop.de to kdevelop.org. SEO wise everything else would be a nightmare 
imo. It would be cool if you could also try to prepare a 3.5 version of the 
old website, considering that all KDevelop 4 related content should be on the 
new website eventually. And of course we need to link both websites eventually 
so users find both as required.

> Once the new website is in place I'll make the forum and the wiki
> read-only.
> 
> Is that OK ?

That sounds very good.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110104/5eb2525e/attachment.sig>