Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Maarten Brouwers (murb)
Hi Cor, > My impression is not that people in this discussion think that it will > be easy per see. I got a bit different impression, and still see the extensive requirements doc (also the new one) highly contrasting with what I read as the idea of ‘just start iterating from

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Maarten Brouwers (murb)
Hi Bjoern, > That -- and the fact that we have 45.000 accounts on it -- are the reason I > brought up Askbot. Content and accounts are the things that are hard earned > on a > platform, maintainers and moderators are a bit easier, but still hard. The > pure technical platform is the easiest

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Maarten Brouwers (murb)
Forgot that Bjoern actually mentioned some of the somehows Technical infrastructure was lacking for contributors: > [1] Seen e.g. by: >a/ repeated cries for help on twitter, some examples: (both technical > issues) > https://twitter.com/nimbleslides/status/1020899933161848832 >

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Maarten Brouwers (murb)
Hi Bjoern, > Stating that a classic CMS is by definition better suited for the task at hand > than something more interactive like discourse is a foregone conclusion. Given > that the lack of community involvement is the core reason for many limitations > of the current setup, its not a valid

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Bjoern Michaelsen
Hi, On Sun, Oct 14, 2018 at 03:54:13PM +0200, Maarten Brouwers (murb) wrote: > Sure, but again, I doubt it matters to an extensions website. Mozilla has no > OAuth, and still has imho a great extensions website. In an ideal world > everyone contributes and consumes, but in reality it is just a

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Bjoern Michaelsen
Hi Maarten, On Sun, Oct 14, 2018 at 01:55:38PM +0200, Maarten Brouwers (murb) wrote: > Maintaining software doesn’t become easier when you build a complex tool (an > extensions website) on something that isn’t meant for it (a Q/A site). Its really simple: Dont tell others "Do not consider

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Bjoern Michaelsen
Hi, addendum: On Sun, Oct 14, 2018 at 02:14:36PM +0200, Bjoern Michaelsen wrote: > For the community the decision should go with the team that gets the most > content, interaction and users on their platform. I dont care if someone > thinks > the platform was not made for the task -- it there

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Bjoern Michaelsen
Hi, On Sun, Oct 14, 2018 at 01:24:10PM +0200, Maarten Brouwers (murb) wrote: > I got a bit different impression, and still see the extensive requirements > doc (also the new one) highly contrasting with what I read as the idea of > ‘just start iterating from ask.libreoffice.org

Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

2018-10-14 Thread Cor Nouws
Hi Maarten, Maarten Brouwers (murb) wrote on 14-10-18 11:57: > I wonder how important having existing accounts is for an extension > site. I’d like to be convinced otherwise, but I think that a usable > submission & maintenance process will convince people to contribute > their extensions. A