[kde-community] stackexange site for krita

Scott Petrovic scottpetrovic at gmail.com
Thu May 28 14:04:06 BST 2015 

WordPress multi-site might be worth a try. I am sure if I spent a lot of
time modifying the plug-in, I might be able to get it to work. One issue
with modifying plug-ins is that any updates to WordPress or other plug-ins
could be a problem. If there is an update by the plug-in author or
WordPress, there is no easy way to patch it in.

I did see in a different email thread that Ben mentioned something about
content in WordPress multi-site being shared. With how I understand
WordPress multi-site, these are the main differences

WordPress Multisite
1. Has a new role Super User that controls all sites
2. New network admin area. Plugins and themes are installed here and
managed for each site. Only Super Users can do this (probably Ben)
3. Out of the 11 database tables that WordPress usually creates for a
single site, 9 of those are duplicated for each new site. This keeps the
content separate


This might be a good project to test WordPress multi-site out. I will help
in any way I can.
Scott











On Thu, May 28, 2015 at 7:19 AM, Ben Cooksley <bcooksley at kde.org> wrote:

> On Tue, May 26, 2015 at 1:36 PM, Scott Petrovic <scottpetrovic at gmail.com>
> wrote:
> > The way we are designing this Q&A site, I am starting to think it is a
> bit
> > clumsy. This "answer to a question" will always be specific to a project.
> > Even if we get the filtering thing to work, it will always need to be
> > filtered on every page. Every project will have to have this sticky
> state -
> > hiding all other project questions and answers from the end user. It
> adds a
> > level of 'required configuration' that doesn't exist in Q&A sites. This
> just
> > seems clunky and unnecessary.
> >
> > I almost feel that this solution needs to take a slightly different
> > approach.
> >
> > 1. Have http://answers.kde.org/kde/ go to a KDE specific Q&A site.
> "What is
> > KDE". "How do I help with translations". Things like that.
> > http://answers.kde.org could also redirect to here
> >
> > 2. From there, individual projects will need to request their own Q&A
> site
> > if they really think they are wanting one. Krita would be (
> > https://answers.kde.org/krita/ )
> >
> > With the Krita pilot site, KDE will be able to decide if the WordPress +
> > plugin is a good standard for any future infrastructure requests. If the
> > Krita version is successful, I could also help if KDE wants to have a
> more
> > general purpose KDE themed version. This KDE version could also be the
> base
> > theme for any new projects that are created in the future.
> >
> > How does this direction sound? Are there technical hurdles with this?
> What
> > are the downsides?
>
> This direction is fine with me, assuming the current plugin can't work
> with all applications sharing the same instance.
> I'd recommend we use Wordpress Multi-Site functionality as the core is
> essentially the same for each subsite.
>
> >
> > Scott
>
> Cheers,
> Ben
>
> >
> >
> > On Sat, May 16, 2015 at 8:27 AM, Scott Petrovic <scottpetrovic at gmail.com
> >
> > wrote:
> >>
> >> Alright.
> >>
> >> Carl - I think once we start adding content to this and use it, we don't
> >> want to have the possibility of everything being deleted. A lot of
> people
> >> are going to be spending time building this up. It would be
> disheartening
> >> since this is part of a support system. Links will be pointing to this
> in
> >> blogs. We will be referencing it in IRC and forums - in addition to any
> SEO
> >> benefits that would be lost in the trial months. We need to get a good
> long
> >> term solution in place and then roll with it. I think that will create
> more
> >> confidence and drive higher usage as well.
> >>
> >> Rick - you seem to have a solution for this. Do you want to take a stab
> at
> >> making the fixes? With the direction we were going, we were wanting to
> have
> >> the search be filtered by category. Also, it would be nice to have a URL
> >> that would make the categories sticky. That way when you are on a
> product,
> >> it will stay on that project. This will make it easier for a project to
> link
> >> to the Q&A site and they know everything will be filtered by their
> project.
> >> If interested, you can probably put in a infrastructure support ticket
> to
> >> get access (https://sysadmin.kde.org/tickets/).
> >>
> >>
> >> For the styling, we will have to make it KDE styled since it will be for
> >> all projects. Making the design look like Krita branding would be
> confusing.
> >> Scott
> >>
> >>
> >>
> >>
> >> On Thu, May 14, 2015 at 1:25 AM, Rick.Timmis <Rick.Timmis at abazander.com
> >
> >> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Sent from my Dragon 32
> >>>
> >>> Carl Symons <carlsymons at gmail.com> wrote:
> >>> On 05/13/2015 06:02 PM, Scott Petrovic wrote:
> >>> > I started configuring the Q&A site plugin.
> >>> >
> >>> > https://answers.kde.org/
> >>> >
> >>> > You can search for questions or add your own. One issue I am having
> >>> > with
> >>> > this plug-in is you cannot filter by category(product) before you
> ask a
> >>> > question. All of the different products get lumped together in the
> same
> >>> > search. For the questions I made, typing in "transform" will bring up
> >>> > questions in multiple products. There is no way to tell what product
> a
> >>> > question belongs to currently.
> >>> >
> >>> > Out of the solutions that I have found, I haven't seen a Q&A site
> >>> > solution that is designed in the direction we were going (select a
> >>> > category, then ask a question). Does anyone else have any thoughts?
> >>> >
> >>> > Scott
> >>> >
> >>>
> >>> My first thought is that this is not ready for general KDE Q&A. The
> plan
> >>> was to get the wrinkles out with Krita, using this as a pilot (and dev
> >>> site). People need to know that it is likely that there will be major
> >>> tweaks, as well as the possibility that all the data may disappear.
> >>>
> >>> I agree with you Scott. I would expect to be able to look for questions
> >>> dealing with Krita and not get other products. It doesn't work like I
> >>> thought it would.
> >>>
> >>> Carl
> >>>
> >>> Hi
> >>>
> >>> I think the Ajax type ahead search might be the cause of the problem. I
> >>> don't think it will work well with lots of data and results. Also it
> is most
> >>> likely not honouring the category selected. Can it be turned off ?
> >>>
> >>> I really like this as a starting point, clean, simple and the
> categories
> >>> are perfect for KDE Applications.
> >>>
> >>> Support for wildcard entries would be good too.
> >>>
> >>> So far I like it
> >>>
> >>> Rick
> >>> >
> >>> >
> >>> > On Mon, May 11, 2015 at 2:23 AM, Boudewijn Rempt <boud at valdyas.org
> >>> > <mailto:boud at valdyas.org>> wrote:
> >>> >
> >>> >     --
> >>> >     Boudewijn Rempt | http://www.valdyas.org | https://www.krita.org
> >>> >
> >>> >     On Wed, 6 May 2015, Luca Beltrame wrote:
> >>> >
> >>> >         Boudewijn Rempt wrote:
> >>> >
> >>> >         Hello Boudewijn,
> >>> >
> >>> >         first of all thanks for replying.
> >>> >
> >>> >             model. The forum encourages discussion and sharing work,
> >>> >             while here we
> >>> >             want to have a question per topic, answers, and a kind of
> >>> >             game system
> >>> >
> >>> >
> >>> >         Do you think that such a way would be better suited for
> Krita?
> >>> > I
> >>> >         ask because at least in the forums I man (not Krita, you guys
> >>> >         are too good at it yourselves ;) I see (still occasionally
> >>> >         though) other users stepping in and giving advice (this is
> most
> >>> >         evident in the Plasma 5 forum).
> >>> >
> >>> >
> >>> >     Well, as I said, it's mostly a different kind of interaction, so
> >>> >     what I want is give users what they're expecting: a forum for
> >>> >     wide-ranging discussion-type interaction and a q&a site for
> >>> >     questions and answers. The one doesn't replace the other.
> >>> >
> >>> >
> >>> >         OK, that's not the level of involvement I'd like to see, but
> >>> >         it's a start.
> >>> >
> >>> >             where answers can be upvoted or downvoted and marked as
> >>> >             correct. And then
> >>> >             the site must be easily searchable.
> >>> >
> >>> >
> >>> >         This last sentence warrants some additional questions: what
> are
> >>> >         issues w/search?
> >>> >
> >>> >
> >>> >     It's a matter of how google indexes stuff, I'd say.
> >>> >
> >>> >     Boudewijn
> >>> >
> >>> >
> >>> >     _______________________________________________
> >>> >     kde-community mailing list
> >>> >     kde-community at kde.org <mailto:kde-community at kde.org>
> >>> >     https://mail.kde.org/mailman/listinfo/kde-community
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > kde-community mailing list
> >>> > kde-community at kde.org
> >>> > https://mail.kde.org/mailman/listinfo/kde-community
> >>> >
> >>>
> >>> _______________________________________________
> >>> kde-community mailing list
> >>> kde-community at kde.org
> >>> https://mail.kde.org/mailman/listinfo/kde-community
> >>>
> >>> _______________________________________________
> >>> kde-community mailing list
> >>> kde-community at kde.org
> >>> https://mail.kde.org/mailman/listinfo/kde-community
> >>
> >>
> >
> >
> > _______________________________________________
> > kde-community mailing list
> > kde-community at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-community
> _______________________________________________
> kde-community mailing list
> kde-community at kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20150528/81dd9fbc/attachment.htm>

More information about the kde-community mailing list