Project Foundation: Survey

Re: Project Foundation: Survey

Thu, 05 Apr 2018 07:15:54 +0000

Same as -PL on -IT. The thread is on but only one person has talked thus far.

Re: Project Foundation: Survey

Mon, 02 Apr 2018 11:21:57 +0000

Just noting that PL is still working on it. I will post results as soon as i will get them.

Re: Project Foundation: Survey

Thu, 22 Mar 2018 13:58:22 +0000

Posting the results a bit late but eh, French people aren't known to stick to deadlines.

Population and activities: 83 members and staff

What features are absolutely necessary?

Do you think we could add some features?

Do you think we could improve some features?

What are the drawbacks of the current platform?

Re: Project Foundation: Survey

Thu, 15 Mar 2018 08:16:39 +0000

Great, I have forgotten to forward the intermediate results.

These ideas are not sorted by priority. Topics regarding administration are marked with "Admin:". This is a lot, from highly important to nice to have, so buckle up:

+ show block

– hide block

Articles:

Support of Wikidot Syntax, maybe in a module or tag or so, in addition to other Syntaxes
Optional WYSIWYG editor
Simpler editing of sections
Showing all line breaks and spaces, maybe add possibility to switch that on and off
Wikipedia-like categories instead or in addition to tags
A personal special letter sheet that can be shown or hidden in the editor, and can be customly filled e.g. with the greek alphabet, gothic letters etc.
- Admin: A standard letter sheet for each branch, for language specific characters
Style editing of page elements via interface (instead of writing the code by hand)
Application of CSS elements in the preview
A personal note-panel that can be shown and hidden everywhere (e.g. to store standard phrases)
Per page Meta data, showing the creator, translator etc. without necessity to use the comments

Embeddables and code in Articles:

Simple handling of embeddables, e.g. via drop down list or inserting-wizard
Support of not-embedded descriptions in embeddables like on Wikipedia
Simple handling of classes and styles, e.g. also via drop down list
Support embedding of external services without iframe (or better iframes)
- Admin: A list of all embedded external references on the site
- Admin: site-wide blacklist for external references
Support of the same (relevant) modules and snippets (or their functions) like on Wikidot

Site Structure:

Wiki structure, with as few user-side structural changes as possible
Support of all common page elements by theme, also of elements that get established by the users
Support of umlauts and special characters in unix-names, according to current standarts
Admin: Possibility to add something directly to , globally as well as page-wise
Support of SSL and the like
At least one server in Europe
Admin: Every branch remains administrative and structural independent
Admin: EN has no global decision power although they mainly provide the platform
Support of a module to add content to the sidebar page-wise
Admin: Good API hurr durr
Admin: Automatic maintenance functions, e.g. recounting of ratings or so
Admin: Option to remove malicious ratings page wise and site wide
Admin: Addition of filter tags e.g. for child safety locks, personal blocking or filter functions (tags like "gore", "spiders", "sexual", "nazis", "jumpscare" etc.) so sensitive users and parents can block unwanted content
Admin: Better support for translation of the site itself. So single strings and sentence-segments but whole paragraphs
- Admin: Option for a "live-translation" where chosen users can enable a translation-mode and translate site elements in place, so they don't have to guess where a string can be found
Simple Cross-branch linking, e.g. [[[SCP-173|DE]]] for the german translation of SCP-173
- Same for attached images, e.g. [[image SCP-173|DE|img1.png]]
Option to clone an existing page to a Sandbox, to ease translation
- Option to transmit the content or a section of the Sandbox directly to the site when the translation is finished
Option for sandbox-owners to give edit-rights to certain users
Option to disable voting for certain pages like attachements, or options to vote for the full work (SCP+attachements) instead of each page
Native support of achievements and automatic achievement achieving where possible. Optional for each branch

User profiles:

Shared user database
Admin: User management per branch
Admin: Unlimited user roles per branch and individual rights management and namespace-wise access policy
Customizable user profile page like on Wikipedia
List of creations, translations etc. of the user in the profile
Better overview over own works and translations
Personal file manager
Better watch-options (e.g. notifications for comments on own work)
Option to show a warning before showing pages, images or forum threads, marked with certain filter-tags
- Admin: Option to support optional branch specific standard filter lists (according to local law or so)
Child safety lock function that can block pages, images and threads completely, based on filter tags
- Option to block certain users via child safety lock
- Access via parent-password or linked parent-account
Configurable user-blocking (everything, just PMs, forum posts, articles etc.)
Better activity feed
- Option to watch forum threads
Option for all users to choose a menu language for each branch
Public and/or private favorite list(s)

GUI:

Modern theme (less Windows 7-like)
Option to choose from multiple fully compatible themes
No limitation of the current handling
Optional reading mode, where the menus and header are hidden

Forum:

Support of more code in forum threads
Option to collapse or expand all images in the forum by default
Option to attach files to forum posts
Option to easily quote sentences or sections of a page in the forums and add a link to that section
Option for automatic thread cleanup (moving inactive threads to a hidden section)
Option to delete threads
Option to limit the amount of active threads a user can create in certain categories

File handling:

Support of SVGs and other modern web-file-types
Optional per-file-page like on Wikipedia, just less complicated
Support of mass-uploads without Flash
Admin: Administrative file manager (e.g. like Windows Explorer)
Admin: Options to limit uploads (file size, resolution, file types)
Option to protect files from editing or overwriting (e.g. non-CC BY-SA files)
User-specific file manager
Global file database like Wiki Commons

Cross-branch features:

Native support of multilingual sites like ND
Native support of the interwiki-module and option to add aliases for the same page with different unix-name
Easy site creation for new branches

– hide block

Re: Project Foundation: Survey

Mon, 12 Mar 2018 04:23:08 +0000

http://ko.scp-wiki.net/forum/t-5408236/

SCP-KO users want nothing special, but want to make sure that current features of wikidot is available in new platform.

Re: Project Foundation: Survey

Sun, 11 Mar 2018 14:44:06 +0000

Sharing my thoughts on all this things. All of the following points based on the continuing development of our own platform instead of using something like mediawiki.

1. Article

Nothing interesting here for the first few stages of development.
I'm still insist on using of markdown and happy to see that I'm not alone. It looks like the only reasonable choice.

2. Embeddables and code in Articles

I'm strictly against usage of custom user code and styles.
Yes, they're helping us now to plug the holes in the wikidot functionality, but they bring a lot of troubles in terms of unification, maintenance and security. I believe that design of new hubs and pages AND custom integrated functionality should be added and updated only via staff members. You may say that it will add workload to staffers and that's true, but I think that custom features & design should be privilege for pages that already have good content, not vice versa.

3. Site Structure

- Sites (EN, RU, etc.)
- Namespaces (sandbox, drafts, etc.)
- Pages
- Pages revisions (just like in wikidot, but maybe with branches)

- Global tags (object, tale, euclid, etc.)
- Local tags (site-specific things)

4. User profile

Nothing to tell here now.
Maybe we (scp-ru) will use Discord as intermediate source of user accounts for migration since we already have simple mechanism of tethering wikidot accounts to discord ones.

5. GUI

What?

6. Forum

Nothing to say here now, not at this point of time. I don't see any big problems here, something similar to the current structure would work.

7. File handling

Current model is pretty good, but maybe we'll want to move files from articles to some separated place.

8. Cross-branch features

Interwiki should be integrated into the platform itself.

Global tags can be useful.

9. Administrative features

Irrelevant question at this stage of development, since there are too many details.

Re: Project Foundation: Survey

Sat, 10 Mar 2018 12:57:40 +0000

On March 6, SCP-JP started asking for opinions from the members via forum
Here: [http://ja.scp-wiki.net/forum/t-5416518/proj:foundation]

Interim Report
These are only a brief summary: I'll give a detailed description later.

Articles

ruby (furigana)
tab
list
editing in markdown

Embeddables and code in Articles

showing modal window about credit
html embedding ( in sandbox )
inter-wiki link

Site Structure

integration to scpperDB
poll module
versatile ListPages
CSS Module
hiding “Look who rated this page”
batch editing
Powerful api

User profiles

user activity

more useful search engine (Wikidot can’t search in Japanese certainly)

Forum

option about removing thread completely
IRC Server

Cross-branch features

inter-wiki list module

Administrative features regarding all of the above

bulk deletion of draft data
Non-Roman characters in URL link functions

Project Foundation: Survey

Thu, 01 Mar 2018 10:37:57 +0000

You may have heard of Project Foundation: relocation of the whole community from Wikidot to another platform.

Wikidot is becoming more and more unreliable and unstable, and it has not gotten any updates for years now. This makes relocating to another platform inevitable on the long run, and as it isn't getting better with Wikidot, the earlier we finish it, the better. Of course we could just transfer to another Wiki-farm. But there the problems would not necessarily end, and of all Wiki-farms, Wikidot is one of the better choices, as others are full of advertisements or are having stricter regulations. So the possibly best solution would be to create an own platform.

Don't worry, the content and even votes can be transferred automatically. Also financial and legal questions will be settled in future steps. There are people who can and will program the new platform from scratch if necessary. It is also planned that all branches find a new home there. All is in good hands and this time it will be finished, thereof I am certain.

Currently there is no definite date or plans. And for the start, it would be beneficial to know what features we want to keep, and what features we want to have in the future. Therefore I ask all branches to conduct a survey to answer these questions for their branch.

These are the categories the ideas and wishes should be sorted into:

Articles (creation, writing, editing, tags, rating, other article-specific features)
Embeddables and code in Articles
Site Structure
User profiles
GUI
Forum
File handling
Cross-branch features
Administrative features regarding all of the above

How you get the information is up to you. You can ask your users, keep it among staff or dedicate one single user to answer the survey, just as you like. You may priorize wishes and ideas. Everything is allowed, you can add as many entries as you want. No idea is too weird. This basically is one big brainstorming and the ideas are being evaluated later.

This survey will actually run till the 31th March, though we may choose to prolong it. Anyway please give us an intermediate result on the 10th March.