Hi Dmitry
Thank you for this email, it makes the context, and reason, clear.
I think a Wiki style solution wojld be best, but care must be taken to manage
its house keeping.
What would be really cool is an IRC Bot that could then search the Wiki and
post links back.
Rick Timmis
Sent from my Dragon 32Dmitry Kazakov <[email protected]> wrote:Hi!
I'm sorry for jumping in a bit lately. My initial request on IRC, which
resulted in this stackoverflow discussion was the following:
I asked for a kind of "knowledge base", where I (developer) could search for
popular answers really quickly and copy/paste the link into IRC/social networks
to help people with their (really trivial and common) problems.
The point is there are lots and lots trivial questions which will be being
asked or raised regularly, so we need to have them somewhere in easy access.
Examples:
1) How to generate a tablet log?
2) How to compile Krita?
3) How to generate a backtrace for Krita crash?
Right now I use launchpad's framework, but it is really-really limited. You
cannot even add a screenshot :(
Here: https://answers.launchpad.net/krita-ru/+faqs
So I was even though about moving all these answers into wiki, but it seems
like a special solution like LampCMS might help better in this situation.
The requirements for this system for me:
1) Easy to add a pair Question/Answer (yep, self-dialog)
2) Easy to search for a question, and easy to paste the link to an answer on IRC
3) The ability for users to ask/answer questions is nice, but for me it is
secondary :)
On Fri, Feb 27, 2015 at 3:42 PM, Scott Petrovic <[email protected]> wrote:
Does anyone have comments on LampCMS? https://github.com/snytkine/LampCMS
These are why I think it is the best solution for KDE as a platform
1. Open source. We can take the source code and add it to the infrastructure
(so it is KDE hosted)
2. It has easy access for logging in (facebook, twitter, linkedIn, Google+).
3. While though it doesn't have a large developer base, it seems moderately
maintained.
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...
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.
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 .
It is possible that you will get bad answers from doing a google search. Does
that stop you from using search engines?
those are my thoughts
Scott
On Fri, Feb 27, 2015 at 3:26 AM, Boudewijn Rempt <[email protected]> wrote:
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?
On Wed, 25 Feb 2015, Scott Petrovic wrote:
I think Laszlo's suggestion with OSQA looks like a pretty good solution. I
personally think a slightly better
open source one is Lamp CMS http://support.lampcms.com/
I would personally prefer using Lamp CMS only because it integrates directly
with other popular platforms like
Google+ and Facebook. This is less friction for people to post questions and
answers without having to sign up
for yet another account. Not sure if social media integration is considered a
'dependency' though.
Scott
On Wed, Feb 25, 2015 at 10:12 AM, Laszlo Papp <[email protected]> wrote:
I would personally much prefer integrating this into the KDE
infrastructure rather than KDE going to Stack Exchange:
http://www.osqa.net/
StackExchange is a commercial entity without open source accessbility
to the implementation. Also, you need to comply with what
StackExchange likes in the end of the day.
On Wed, Feb 25, 2015 at 4:09 PM, Boudewijn Rempt <[email protected]> wrote:
> This is a question that came up on the #krita channel today. Our forums
are
> awesome, but not the best place for question and answer type of
exchanges.
> We even see questions appear on yahoo answers!
>
> One proposal was to create a krita.stackexchange.com, like
> http://blender.stackexchange.com/. However, this is infra that's
outside of
> KDE. I don't know of anything equivalent, though!
>
> So, what I wanted to get input on is: would creating a
> krita.stackexchange.com be against the manifesto? And if so, is there
any
> equivalent (in terms of user-friendliness, googleability and
> recognizability) that we can use withing KDE's infra structure?
>
> For all clarity; this isn't a wiki, and it isn't a forum. It works in a
very
> different way.
>
> Boudewijn
>
> (Willing to experiment so fewer people wonder where their layers have
gone.
> https://answers.yahoo.com/question/index?qid=20150224214426AAbFtKj)
> _______________________________________________
> kde-community mailing list
> [email protected]
> https://mail.kde.org/mailman/listinfo/kde-community
_______________________________________________
Krita mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kimageshop
_______________________________________________
Krita mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kimageshop
_______________________________________________
Krita mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kimageshop
--
Dmitry Kazakov
_______________________________________________
kde-community mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-community
