When I look at popular webpages where you can share your content like image
webpages, openclipart, ... they are all very simple.
One overview page with Screenshots and description how is the developer and
categories.
Upload page with uploader, title, description, category and licence. Maybe
tested with version.
Detail page show the selected item and related stuff like other stuff from
user, related things.
Page moderator can edit categories and block content.
Users can rate and review stuff. Maybe it could be useful that users can
submit updates and the origin contributor can review it or update it. So
something like collaborative work.
Contributors have an profile with links to payment pages like patrons, ...
on each template or extensions page you see user information and patron
page links.
The page can be used for extensions, templates, documentations, ...
Nice things would be to have something like a connection to libreoffice
online where you can see if the template, extensions work (for page
moderators).
Categories: each app is an category and than some (not more than 10) other
categories.
Bjoern Michaelsen <bjoern.michaelsen@libreoffice.org> schrieb am Fr., 12.
Okt. 2018, 16:02:
Hi Maarten,
On Fri, Oct 12, 2018 at 02:06:54PM +0200, Maarten Brouwers (murb) wrote:
What about adapting Mozilla’s extension-site?
So lets phrase the problem differently: We are not lacking tools or
platforms.
We are lacking volunteers to maintain, develop and moderate on platforms.
So if
you find a team of 2 to 3 enthusiastic volunteers that are willing to push
a
platform forward that is great. That platform can be Mozilla Addons,
Askbot,
Plone or something else.
OTOH that is for later: This is the design list and the focus should be on
identifying the vital core features needed on a solution. I opened the
discussion with Askbot as it provides this:
- We currently have a well-maintained instance.
- We currently have active moderators on that site.
- We were able to purchase development on AskBot.
So the workflow has to be:
1/ Identify core needs and usecases
2/ Find volunteers, enthusiasts and maintainers, who can provide these core
usecases with ~whatever tool they want.
3/ Implement MVP on a platform and extend usecases as volunteer resources
allow
(maybe topped up with some payed development, if that is worth it)
The tools are NOT the important part of this. People are. Considering
AskBot,
which has 100 to 1000 moderators:
https://ask.libreoffice.org/en/badges/14/supporter/
https://ask.libreoffice.org/en/badges/9/critic/
instead of _only_ considering Plone, because "we always used it" is putting
people first.
So tl;dr: This is the design list, we do 1/ "Identify core needs and
usecases"
here. No tools/platform discussion[1]. Next up would be finding
enthusiastic
people willing to work on this. For the most part, they can use whatever
tool
they want, if they get stuff done. Even if I think their tool is horrible
or
"a bus turned into a car", I am happy, if the users of the site are happy
and
there is an active set of volunteers[2] maintaining it.
Best,
Bjoern
[1] And again: Saying "Do not limit yourself to Plone" is exactly that: It
keeps the tools out of a discussion that should identify core usecases.
[2] https://en.wikipedia.org/wiki/Bus_factor
--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
Privacy Policy: https://www.documentfoundation.org/privacy
--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.