<div dir="ltr"><div><div><div><div><div><div><div>Does anyone have comments on LampCMS? <a href="https://github.com/snytkine/LampCMS">https://github.com/snytkine/LampCMS</a><br><br></div>These are why I think it is the best solution for KDE as a platform<br><br></div>1. Open source. We can take the source code and add it to the infrastructure (so it is KDE hosted)<br></div>2. It has easy access for logging in (facebook, twitter, linkedIn, Google+).<br></div>3. While though it doesn't have a large developer base, it seems moderately maintained.<br><br></div>For the Krita instance of this, I was planning on re-skinning it after it would be hosted, so it should look quite nice and consistent. For the point of view about bad answers being written...<br></div><br></div><div>Even looking at Krita's documentation on KDE, it is not up to date. In other words, there are errors for anyone that tries to download Krita now and seek instruction from the 'source'. We have to realize that as a user base gets larger, it will become impossible for developers to answer the amount of questions people have. We have to think of a better way to rely on the community to help us with this aspect. We already ask the non-KDE community to do things like find bug fixes, feature requests, an test builds. <br><br></div><div>Having people help is usually a good idea (I think most of us here are volunteers). There will be bad answers on the Q&A platform. There will also be excellent answers as well. People expect there to be bad answers on a QA platform. People expect the voting system to help filter out the bad, not eliminate it . <br><br>It is possible that you will get bad answers from doing a google search. Does that stop you from using search engines?<br></div><div><br></div><div>those are my thoughts<br></div><div>Scott<br></div><div><div><br><br><br><br><div><div><div><div><div><div><br><br><br></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 27, 2015 at 3:26 AM, Boudewijn Rempt <span dir="ltr"><<a href="mailto:boud@valdyas.org" target="_blank">boud@valdyas.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm fine with anything that Scott likes :-) I'd really like to experiment with this. Who knows, it might be valuable experience for other KDE projects as well. So, what's the next step?<div class="HOEnZb"><div class="h5"><br>
<br>
On Wed, 25 Feb 2015, Scott Petrovic wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think Laszlo's suggestion with OSQA looks like a pretty good solution. I personally think a slightly better<br>
open source one is Lamp CMS <a href="http://support.lampcms.com/" target="_blank">http://support.lampcms.com/</a><br>
I would personally prefer using Lamp CMS only because it integrates directly with other popular platforms like<br>
Google+ and Facebook. This is less friction for people to post questions and answers without having to sign up<br>
for yet another account. Not sure if social media integration is considered a 'dependency' though.<br>
<br>
Scott<br>
<br>
On Wed, Feb 25, 2015 at 10:12 AM, Laszlo Papp <<a href="mailto:lpapp@kde.org" target="_blank">lpapp@kde.org</a>> wrote:<br>
I would personally much prefer integrating this into the KDE<br>
infrastructure rather than KDE going to Stack Exchange:<br>
<a href="http://www.osqa.net/" target="_blank">http://www.osqa.net/</a><br>
<br>
StackExchange is a commercial entity without open source accessbility<br>
to the implementation. Also, you need to comply with what<br>
StackExchange likes in the end of the day.<br>
<br>
On Wed, Feb 25, 2015 at 4:09 PM, Boudewijn Rempt <<a href="mailto:boud@valdyas.org" target="_blank">boud@valdyas.org</a>> wrote:<br>
> This is a question that came up on the #krita channel today. Our forums are<br>
> awesome, but not the best place for question and answer type of exchanges.<br>
> We even see questions appear on yahoo answers!<br>
><br>
> One proposal was to create a <a href="http://krita.stackexchange.com" target="_blank">krita.stackexchange.com</a>, like<br>
> <a href="http://blender.stackexchange.com/" target="_blank">http://blender.stackexchange.<u></u>com/</a>. However, this is infra that's outside of<br>
> KDE. I don't know of anything equivalent, though!<br>
><br>
> So, what I wanted to get input on is: would creating a<br>
> <a href="http://krita.stackexchange.com" target="_blank">krita.stackexchange.com</a> be against the manifesto? And if so, is there any<br>
> equivalent (in terms of user-friendliness, googleability and<br>
> recognizability) that we can use withing KDE's infra structure?<br>
><br>
> For all clarity; this isn't a wiki, and it isn't a forum. It works in a very<br>
> different way.<br>
><br>
> Boudewijn<br>
><br>
> (Willing to experiment so fewer people wonder where their layers have gone.<br>
> <a href="https://answers.yahoo.com/question/index?qid=20150224214426AAbFtKj" target="_blank">https://answers.yahoo.com/<u></u>question/index?qid=<u></u>20150224214426AAbFtKj</a>)<br>
> ______________________________<u></u>_________________<br>
> kde-community mailing list<br>
> <a href="mailto:kde-community@kde.org" target="_blank">kde-community@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/kde-community" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/kde-community</a><br>
______________________________<u></u>_________________<br>
Krita mailing list<br>
<a href="mailto:kimageshop@kde.org" target="_blank">kimageshop@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kimageshop" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/kimageshop</a><br>
<br>
<br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
Krita mailing list<br>
<a href="mailto:kimageshop@kde.org" target="_blank">kimageshop@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kimageshop" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/kimageshop</a><br>
</div></div></blockquote></div><br></div></div>