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