Wikiversity:Colloquium

From Wikiversity
Jump to navigation Jump to search
Start your discussion here
Please do not include wiki markup or links in section titles.
Sign your posts with   ~~~~
Welcome

Do you have questions, comments or suggestions about Wikiversity? That is what this page is for! Before asking a question, you can find some general information at:

Shortcut:
WV:C

Organization of Wikiversity
Policies
Discussions
Support staff

Purge Cache - Colloquium Archives - RSS version

var wgArticlePath = "/wiki/$1"; var wgServer = "http://en.wikiversity.org"; var wgPageName = "Wikiversity:Colloquium"; var wgTitle = "Wikiversity Colloquium"; var wgContentLanguage = "en"; var x-feed-reverse = "true"; var x-blog-description = "You have questions, comments or suggestions about Wikiversity? That's what this page is for!";

RSS

"Education [...] is a process of living and not a preparation for future living." — John Dewey (discuss)


VisualEditor default for new users?

What are out current settings on whether VisualEditor is the default? I've had a few new users tell me that they've often had source editor seem to come up as their default editor unless they specifically change it. Therefore:

  1. Is it possible to make VisualEditor the default interface for new users?
  2. Would people like to activate this?
  3. Are there other useful VE settings options to consider?

T.Shafee(Evo﹠Evo)talk 11:50, 18 March 2020 (UTC)[reply]

I guess it depends on the users. People that edit/author learning resources with much workload to create mathematical formulas in LaTeX might prefer source editor in comparison to visual editor. I would recommend, that user answer a checkbox in the registration/login process if they prefer visual or source editor. The link includes a wikiversity link to help page, that shows/explains PROs and CONs of visual and source editor, so that new users can make sound decision about editor default settings.
But my opinion is not representative in the community --Bert Niehaus (discuss • contribs) 12:02, 18 March 2020 (UTC)[reply]
Visual editing is still a beta feature (Special:Preferences#mw-prefsection-betafeatures). It is not on by default (mw:VisualEditor/Rollouts), and not widely adopted (1,500+ users at present). We have to request that it be enabled. The last time I tried, it only got one vote. People need to engage if we're going to improve the Wikiversity experience. And, if there's any support for this, I also recommend that we enable the mw: UploadWizard. Most file uploads to Wikiversity are deleted due to incomplete or improper licensing. -- Dave Braunschweig (discuss • contribs) 13:09, 18 March 2020 (UTC)[reply]
Definitely also agree with activating mw: UploadWizard. Uploading files to wikiversity is still pretty clunky, and I've found often trips up users that are used to commons or wikipedia. T.Shafee(Evo﹠Evo)talk 23:17, 10 April 2020 (UTC)[reply]

I've had a couple of additional new editors struggle with source editing (especially tables, example). Several have expressed frustration at the multiple steps required to find out that visualeditor exists and how to activate it. Is the request process particularly long? Does it need to be done here or over at MW? All wikijournal contributors who weren't already experienced wikipedians that I've spoken to have expressed a preference for visualeditor (especially for pages with tables and references). T.Shafee(Evo﹠Evo)talk 02:34, 14 May 2020 (UTC)[reply]

@Evolution and evolvability: See the item below on the Discussion Reply Tool. We have to have a discussion and vote. Once there is consensus, we submit a Phabricator ticket. How long it takes for that to be processed depends on who accepts the task and what's involved. Some things can take a week or two. Others have stalled out after months of waiting. Sometimes, we can ping someone and get it picked up again. But for now, we need a discussion and vote before we can initiate the ticket. -- Dave Braunschweig (discuss • contribs) 14:41, 14 May 2020 (UTC)[reply]
@Dave Braunschweig and Bert Niehaus:: What would be the next steps to implement this? I think it's reasonable to say the consensus is to activate VE as the default, with the option for experienced editors to switch to editing source code if they prefer. T.Shafee(Evo﹠Evo)talk 12:24, 20 July 2020 (UTC)[reply]
@Evolution and evolvability: Create a Phabricator request and include a link to this discussion. Then wait. If it takes more than a month, ask them what additional information they need or how we can help the request move forward. Then wait some more. Sometimes it goes very quickly, sometimes not. They're all volunteers, too. -- Dave Braunschweig (discuss • contribs) 14:18, 20 July 2020 (UTC)[reply]
@Dave Braunschweig: Done (link). All welcome to review and edit the request. T.Shafee(Evo﹠Evo)talk 01:51, 28 July 2020 (UTC)[reply]
phabricator request marked as implemented and ticket closed as resolved. T.Shafee(Evo﹠Evo)talk 10:20, 6 August 2020 (UTC)[reply]

Discussion

We have a proposal to make the VisualEditor the default editor. We need to determine whether this is for all users or only for all logged-in users. Please discuss and vote. -- Dave Braunschweig (discuss • contribs) 14:41, 14 May 2020 (UTC)[reply]

(From VE and Source Code Editing) The VE will be good for newbies. The source code editor will be necessary to move on to more specific modification of learning resources e.g. editing of quizzes, mathematical syntax and or specific interactive elements of learning resource in the future. If people are taught to use VE only, they might have difficulties to change to source code editing later, e.g. for mathematical expressions the authors might not be able to edit the syntax because they were never exposed mathematical expression or mathematical syntax in general, that is needed in computer science, chemistry, physics, ... . The VE will reduced possible obstacles for beginners and shift those obstacles to a later phase of advanced authoring, in which the source code editing might be without alternative. It would be of advantage to guide authors from the VE to source code editing or visualize changes within the VE simultaneously in a source code editing window or visualizes source code for cross-checking before saving, ....? --Bert Niehaus (discuss • contribs) 13:48, 27 July 2020 (UTC)[reply]
@Bert Niehaus: Regarding training, My understanding is that we've minimal training material currently. One possibility is specific training material on wikiversity on what can't be done in VE but can be done in source editor. Alternatively, is this information already already on another wiki's help pages that we can simply point to? T.Shafee(Evo﹠Evo)talk 00:52, 29 July 2020 (UTC)[reply]
Maybe just an additional button/checkbox "Show Wiki Source before publishing" next to "Publish Change" could be one option to increase visibility of source syntax, so that switching to source code editing runs smoothers. May also advanced users may change their workflow, e.g. writing the text and sections with VE and then finally before publishing the authors add the mathematical expressions source code for the learning resource.--Bert Niehaus (discuss • contribs) 10:39, 29 July 2020 (UTC)[reply]

Voting

Discussion Reply Tool

There is a new discussion reply tool. It automatically indents and signs replies. See Wikiversity:Newsletters/VisualEditor#Editing news 2020 #1 – Discussion tools for more information. If we want it enabled on Wikiversity, we need to request it. Please discuss and vote.

Discussion

Voting

Invitation to participate in the conversation

We are excited to share a draft of the Universal Code of Conduct, which the Wikimedia Foundation Board of Trustees called for earlier this year, for your review and feedback. The discussion will be open until October 6, 2020.

The UCoC Drafting Committee wants to learn which parts of the draft would present challenges for you or your work. What is missing from this draft? What do you like, and what could be improved?

Please join the conversation and share this invitation with others who may be interested to join, too.

To reduce language barriers during the process, you are welcomed to translate this message and the Universal Code of Conduct/Draft review. You and your community may choose to provide your opinions/feedback using your local languages.

To learn more about the UCoC project, see the Universal Code of Conduct page, and the FAQ, on Meta.

Thanks in advance for your attention and contributions, The Trust and Safety team at Wikimedia Foundation, 17:55, 10 September 2020 (UTC) 

Neurocryptoeconomics

Hello I am new to wikiversity, I am just trying to define a new field (Neurocryptoeconomics), and someone deleted the page. Also reposting results in error as the page is harmful (while it is not). This is a new field, and I sincerely believe to allow may definition and as the field grows, other can come in and edit the definition and add to the page accordingly( ref of def: @NeuroCryptoEcon). Kindly please help,

This definition is only a plus and can be edited later by anyone and describes a nascent field.

Thank you for your consideration, (The preceding unsigned comment was added by Neurocryptoeconomics (talk • contribs) 08:34, 11 September 2020 (UTC))[reply]

@Neurocryptoeconomics: Did you talk with the person who deleted it directly? —Justin (koavf)❤T☮C☺M☯ 08:56, 11 September 2020 (UTC)[reply]

@Justin

Yes I emailed him twice but he did not reply. I just would like to post the definition to introduce a new field that is growing, and can the post can be edited later anytime by anyone as the field grows. I hope Wikiversity reconsiders its decision. Thank you very much (The preceding unsigned comment was added by Neurocryptoeconomics (talk • contribs) 10:24, 11 September 2020 (UTC))[reply]

@Neurocryptoeconomics: I have temporarily restored this page, but with a notice that the content provided belongs at Wikipedia, not Wikiversity. If you want to add definitions, that's an encyclopedia article and belongs there. There are four other important points that will prevent further development on this effort at the moment.
  1. The topic is so new that there is apparently only one author in the world who has any information on this subject, according to Google search.
  2. Your choice of user name and self reference for the definition suggests that yours is a single-purpose account focused on self-promotion.
  3. When people bring new ideas to Wikiversity first that no one else has ever heard of, it is almost always fringe science resulting in net-negative effects on Wikiversity and the user ends up being blocked.
  4. Your approach thus far has ignored a variety of standard Wikiversity cultural norms, indicating you have much more interest in your topic than you do in our community. Refer to the item above for how this typically turns out.
If you are truly interested in providing learning resources (not encyclopedia content) regarding Neurocryptoeconomics, I recommend that you create a Draft:Neurocryptoeconomics page and provide sufficient content that a respected Wikiversity editor supports your efforts to move that content to become a main space resource. -- Dave Braunschweig (discuss • contribs) 14:34, 11 September 2020 (UTC)[reply]

Thanks Dave for the details

Yes, at this point I just want to provide the definition.

Thanks a lot for all the explanation (The preceding unsigned comment was added by Neurocryptoeconomics (talk • contribs) 14:54, 11 September 2020 (UTC))[reply]

Do I have the right to ask for funding of my research project?

Do I have the right to ask for funding of my research project at its Wikiversity pages? --VictorPorton (discuss • contribs) 21:06, 16 September 2020 (UTC)[reply]

You may not use Wikiversity to personally profit from your contributions. -- Dave Braunschweig (discuss • contribs) 23:20, 16 September 2020 (UTC)[reply]
@VictorPorton: If you have work that will be published here or if you are doing research that could improve Wikiversity as a resource, you may consider applying for a grant. —Justin (koavf)❤T☮C☺M☯ 23:34, 16 September 2020 (UTC)[reply]

This project was seeking to generate direct financial benefit to the contributor in violation of Wikiversity:Deletions. It has been deleted. This is the second or third attempt by this user to use Wikiversity to generate direct financial benefit to the contributor. The user's account has been blocked. -- Dave Braunschweig (discuss • contribs) 23:54, 16 September 2020 (UTC)[reply]

It's a very weird, very desperate position to see someone using this site to try to get money. To anyone else reading this, you have a 0% chance of that: please get a real job instead. —Justin (koavf)❤T☮C☺M☯ 00:24, 17 September 2020 (UTC)[reply]

New feature: Watchlist Expiry

Hello, everyone! The Community Tech team will be releasing a new feature, which is called Watchlist Expiry. With this feature, you can optionally select to watch a page for a temporary period of time. This feature was developed in response to the #7 request from the 2019 Community Wishlist Survey. To find out when the feature will be enabled on your wiki, you can check out the release schedule on Meta-wiki. To test out the feature before deployment, you can visit Mediawiki.org or testwiki. Once the feature is enabled on your wiki, we invite you to share your feedback on the project talk page. For more information, you can refer to the documentation page. Thank you in advance, and we look forward to reading your feedback! --IFried (WMF) (discuss • contribs) 16:52, 23 September 2020 (UTC)[reply]

Global ban RFC for Nrcprm2026/James Salsman

Nrcprm2026, better known as James Salsman, has an active discussion regarding a possible global ban.--GZWDer (discuss • contribs) 07:56, 26 September 2020 (UTC)[reply]

Related user accounts are:
Dave Braunschweig (discuss • contribs) 13:36, 26 September 2020 (UTC)[reply]
Retrieved from "https://en.wikiversity.org/w/index.php?title=Wikiversity:Colloquium&oldid=2210775"