<div class="gmail_quote"><meta http-equiv="content-type" content="text/html; charset=utf-8">Hi,</div><div class="gmail_quote">Regarding the CMS, I'll have to align myself with Milian, even if I find your work (Amilcar) really valuable, we don't want to maintain that code so in the long run it's better just to use something already established. That will ease the website maintaining. I hope that will be the first step to a KDE-ification of the *<a href="http://kdevelop.org">kdevelop.org</a> services that came from an island elsewhere which brought a look of fragmented community.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">On Thu, Dec 30, 2010 at 3:25 PM, Milian Wolff <span dir="ltr"><<a href="mailto:mail@milianw.de">mail@milianw.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<a href="mailto:amilcar@ida.ing.tu-bs.de">amilcar@ida.ing.tu-bs.de</a>, 30.12.2010:<br>
<div class="im">> Hi all.<br>
><br>
> My plan is to copy part of the KDev4 content from the wiki to the website,<br>
> After that improve the website a bit to make it more similar to Sam's<br>
> mockups.<br>
> Once that is done we can calmly move to Drupal or typo3. No need to rush.<br>
> We do have a working structure (custom CMS), what we lack is content<br>
> although anyone can edit the wiki.<br>
<br>
</div>*sigh*. Sorry amilcar, but this is just ... wrong. Really, you might like your<br>
CMS but it is a royal pain to work with. There is just no point in wasting any<br>
more time on it. I will continue to work on the Drupal page, as far as I can<br>
see it it's nearly done. Only the template needs to be ported, which I'll<br>
continue to do now.<br>
<div class="im"><br>
> So I sugest we keep adding and improving content in the wiki and later on<br>
> import the content into drupal.<br>
<br>
</div>While a wiki is nice and good for some things, a real website is imo much<br>
better marketing wise. It looks official and is all found easily from one<br>
place.<br>
<br>
I'll continue to use the Wiki for HowTos, Release Schedules etc. but stuff<br>
like feature comparison, FAQ, etc. should be integrated into the website.<br></blockquote><div><br></div><div>How are we going to contribute the texts?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> The current custom CMS is a bit like unix, lots of small and very good<br>
> tools put together to achieve a task. Drupal is like windows, big,<br>
> massive, shiny, but it will take a while before it bends like you want it<br>
> to :)<br>
<br>
</div>Bullshit.<br>
<div class="im"><br>
> But is I do belive that in the long run drupal makes more sense.<br>
<br>
</div>You should try to think on how to change the old website to make it clear it<br>
only contains legacy content, and on how to link to the new page soon. Also it<br>
would be good if you can tell me who owns the <a href="http://kdevelop.org" target="_blank">kdevelop.org</a> domain. If it's<br>
you, please think about moving the domain to the <a href="http://kollide.net" target="_blank">kollide.net</a> server<br>
eventually. Maybe move the existing website to something like<br>
<a href="http://legacy.kdevelop.org" target="_blank">legacy.kdevelop.org</a><br>
<div><div></div><div class="h5"><br>
Bye<br>
--<br>
Milian Wolff<br>
<a href="mailto:mail@milianw.de">mail@milianw.de</a><br>
<a href="http://milianw.de" target="_blank">http://milianw.de</a><br>
</div></div><br>--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br><br></blockquote></div><br><div>Aleix</div>