Wikiversity:Colloquium/archives/August 2015

What does a Healthy Community look like to you? edit

 

Hi,
The Community Engagement department at the Wikimedia Foundation has launched a new learning campaign. The WMF wants to record community impressions about what makes a healthy online community. Share your views and/or create a drawing and take a chance to win a Wikimania 2016 scholarship! Join the WMF as we begin a conversation about Community Health. Contribute a drawing or answer the questions on the campaign's page.

Why get involved? edit

The world is changing. The way we relate to knowledge is transforming. As the next billion people come online, the Wikimedia movement is working to bring more users on the wiki projects. The way we interact and collaborate online are key to building sustainable projects. How accessible are Wikimedia projects to newcomers today? Are we helping each other learn?
Share your views on this matter that affects us all!
We invite everyone to take part in this learning campaign. Wikimedia Foundation will distribute one Wikimania Scholarship 2016 among those participants who are eligible.

More information edit


Happy editing!

MediaWiki message delivery (discusscontribs) 23:42, 31 July 2015 (UTC)[reply]

A healthy community is a divers community. I think the Wikimedia project can become more divers if projects like the Wikiversities get more attention. In the Netherlands, for example, everybody knows about Wikipedia, just a few people know about Wikiversity. To promote Wikiversity we could start a discussion or come up with a proposel. Who has any thoughts on this? Timboliu (discusscontribs) 15:13, 3 August 2015 (UTC)[reply]

Topic namespace borked edit

See [1]. Clicking on any page, I get a message
Bad title
The requested page title was invalid. Pages in the Topic namespace are automatically created by Flow.

Did someone implement Flow here? Extension:Flow I need to stem the Flow of foam from my mouth....

I see that the extension is installed, and was recently updated. I thought these things were not done without local request or consultation. I know little about Flow, but I know that the predecessor Liquid Threads was known for completely garbaging namespaces, I saw it happen with a wiki. There is a Special command, Special:EnableFlow. To use it requires being in the group Flowbots. There is one user in that page, created today. User:Flow talk page manager. I'm going to continue looking into this, but want to post this immediately. --Abd (discusscontribs) 03:55, 4 August 2015 (UTC)[reply]

It's not confirmed, but it appears that Flow was implemented WMF-wide with no announcement and discussion. This is one of a fair number of abrupt WMF developer actions, some of which have caused widespread disruption. In this case, Flow appears to assume that no Topic namespace already exists. We just might be the only wiki affected, because we may have the only pre-existing namespace with that name. All wikis now have a Topic namespace, and you can see it on enwikipedia, where flow has been under test for about two years. We are probably the only one with a Topic talk namespace. We now have two Topic namespaces with the same name. All links into the existing Topic namespace fail, because they are first looking for the Flow topic namespace, and the pagenames don't exist there. We will probably need developer intervention. Hopefully, the Flow namespace can be changed. I know it is possible for it to be different, because on fr.wikiversity, it is called Sujet. So here it could be called Subject. Support?

Hi, sorry about this, it was completely unintentional. Flow was supposed to be deployed but not enabled on any pages so if people asked for specific pages to be Flow enabled, it could be done easier, without involving developers and sysadmins. But we missed that the Topic namespace conflicts with the content "Topic" namespace here. I've disabled Flow entirely here (and on the Japanese Wikiversity) until that can be figured out. Legoktm (discusscontribs) 06:36, 4 August 2015 (UTC)[reply]

Thanks for the prompt response. We will discuss the name to be used here. Maybe it will be Topic, if Dave's proposal has legs! --Abd (discusscontribs) 14:25, 4 August 2015 (UTC)[reply]

Topic Namespace edit

We have been brought to a crossroad. The discussion tool mw:Flow uses the Topic: namespace to manage content discussions. Flow can be implemented in a different namespace, however, at this point it appears that we would be the only English-language wiki to do so. We can also change / rename the Topic namespace to something else and move/rename existing Topic: resources.

Of the choices available, I would advocate for renaming the Topic: namespace. It's use is confusing now, and will be exponentially more confusing once everyone else in the world is trained to recognize Topic: as a Flow discussion. I see that Wikipedia uses a Wikipedia: Project namespace for their collaboration efforts. Perhaps Wikiversity: Topic would work here, retaining the history of Topic while moving the content to the Wikiversity: namespace.

Technically, moving/renaming all of the Topic pages and correcting the links can be accomplished by bot relatively easily. So, the decision should be based on what is best for Wikiversity, not how much work would be involved.

What does the community want to do? Do we use a different namespace for Flow? If so, what? Do we use a different name for Topic:? If so, what? -- Dave Braunschweig (discusscontribs) 12:56, 4 August 2015 (UTC)[reply]

Dave, your analysis I found a bit fuzzy. There really are two separate issues here. Flow does not necessarily use a namespace called Topic. If I'm correct, as it was written, it uses a namespace that means topic in the wiki language, and the bug was that it did not check for the pre-existence of that namespace name. This also hit, apparently, two other wikis, including ja.wikiversity. One of the problems here is that they did not communicate with the communities about what they wanted. In my opinion, for English, Topic is actually a poor name. Flow might be much better. There are two issues here, so I will separate them. --Abd (discusscontribs) 16:00, 4 August 2015 (UTC)[reply]

Flow namespace edit

Flow uses a distinct namespace for Flow discussions. I recommend that before we ask for Flow to be re-enabled, we investigate Flow. I did experience a MediaWiki installation where the manager had a bright idea to install Liquid Threads, and did it unilaterally. It caused massive disruption. I hated LT at first, and so did most, because people were very accustomed to using MediaWiki. While LT procedures might seem intuitive to the software developers, they often are not to users, who are diverse, and, bottom line, everyone has years invested in things working in an accustomed way. So good upgrades allow integration with the old. LT, it turned out, could not be converted back to standard MediaWiki without massive database work. Irreversible changes to software? Ick.

Now, while I had some fear that this would be irreversible, when I investigated more, I became clear that the problem was probably very simple and that Flow had not damaged the database, it merely made it impossible to read the existing Topic pages while Flow was installed, because of the namespace conflict. So the first question has two aspects: Do we want to allow Flow to be implemented, and then what is the namespace? It is already the case that Flow namespaces vary. There is no reason to make an emergency need to massively modify the existing namespace and all links to it, including links in history that might come back, just to deal with Flow. I'm sure that when developers re-enable Flow, we can have a different namespace. I recommend Flow, as my first thought. It is specific, and informative, and will not cause confusion. In actual usage, the namespace is automatic on pages with Flow enabled, if I'm correct. As the error message pointed out, we cannot create Flow namespace names, it appears they are automatic and not human-understandable, they are merely unique. See [2], the MediaWikiwiki Flow namespace, called "Topic."

MediWikiwiki also has Thread and Thread talk namespaces. There are links to Thread: pages that appear to connect with Flow pages in the Topic namespace. Look at this mess, preserved as "entertainment." There are many Flow issues, and I'd want at least a few users here to be very familiar with Flow before we allow it. On the other hand, if it is *safe*, i.e., if changes are reversible, if Flow pages can be converted back to standard MediaWiki, then I would be in favor of at least experimenting with it. It could, however, bifurcate our community into those who know how to use Flow and who are comfortable with it, and those who are not. The Flow team set up the page to be used to report problems to be a Flow page, and I had a devil of a time creating that report, initially, my work kept disappearing, etc. I eventually noticed the symbol at the bottom allowing the use of normal wikitext, but by then I'd already managed to stumble through the process. --Abd (discusscontribs) 16:00, 4 August 2015 (UTC)[reply]

+1 for putting Flow (whatever it is but assuming it is WMF-endorsed and that some people might want to experiment with it) in a namespace called Flow -- Jtneill - Talk - c 10:57, 14 August 2015 (UTC)[reply]

The Topic namespace edit

Wikiversity started out with a set of enthusiastic users with little experience. You can see draft policies that were never implemented, structures, and ... the namespace structure. As far as I can tell, the community never clearly defined many things, and as a result, thousands of users did whatever seemed right to them. So we had -- and still have -- many mainspace resources that are probably not appropriate for top-level mainspace, and the Topic and School and Portal namespaces, someone explain them to me clearly, I still don't get it. Believe me, if it is not clear to me, it is not clear to most users. That doesn't mean that the user doesn't have an idea. They have ideas. Many ideas. That don't match, because we never did the work to find consensus and clarify these things. When consensus was not quick, the early Wikiversitans just punted. It's a very wiki thing to do.

Wikis, as they normally develop, are not good for building well-organized and reliable structures, unless the users are highly motivated, and most users don't want to get involved with difficult structural issues. They just want to do their own work, and indeed, the goal of those who do care about structure should bem, my opinion and stand, to enabled and empower them. They, educated users (and materials that document this and make it more widely available) are our product, not just the materials.

Wikiversity is, in the WMF structure, unique, and that uniqueness is largely, though not entirely, in the English Wikiversity, I can say, having a little other-language Wikiversity experience now (and a lot of non-WV experience!). We can be a model and a light, but one of the things that inhibits this is that others come, look at our "structure," i.e., the mess, and run in horror. As well, they vote to shut down wikiversity as a haven for trolls and fringe theorists and nut cases. However, consider the general opinion of society on academia. Common: Ivory-tower, flaming liberals, and did you read about that pedophile-apologist, Harris Mirkin, who wanted to legalize pedophilia? (See Sexual politics) (Mirkin was not an apologist for pedophilia, he was a political science professor, head of his department, who dared to publish an article, in a peer-reviewed journal, on the political phases that highly controversial topics can go through. The state legislature voted to cut the university budget by $50,000 because of the flap. The university defended him, and he died some years later, head of his department.) Will we defend our "radicals"?

We have, in the past, and it has sometimes been disruptive. I was indef blocked here for standing for consensus, filing an RCA on what I saw as disruptive activity, and which was really disruptive activity, if carefully examined. My unblock template stood with no action for two years, that's how far down our custodial process fell. Now, you can look at RCA, and with what I did yesterday, you can immediately see, color-coded, what's needed with request templates.

Let's do this right. Sanely determining our namespace usage is not likely to be "wiki." I.e., quick. I suggest a working group, users interested in small scale, but detailed, research and discussion, preparing a report to go to the community. If one other user is interested, we have a structure for such discussions, the Wikiversity:Assembly, which is also an experiment in an attempt to expand our understanding of consensus. It's been totally inactive since I was blocked for two years, and I haven't pushed it at all. It's just an option, and the Assembly was not designed to be a government, but an advisory body. --Abd (discusscontribs) 16:00, 4 August 2015 (UTC)[reply]

+1 for moving content from little used namespaces (such as Topic, School, Portal) into the main space and then removing those namespaces. These namespaces were set up as experiments and really haven't taken off and IMHO serve little purpose other than to add unnecessary complexity to the structure. However, if Flow is enabled into a currently non-used namespace, then then this can be treated a separate issue. -- Jtneill - Talk - c 11:01, 14 August 2015 (UTC)[reply]

About Wikiversity edit

I'm making this into a subtopic, it begins with an answer to my post of 16:00, 4 August 2015, above. Please discuss Topic namespace above! --Abd (discusscontribs) 20:45, 5 August 2015 (UTC)[reply]

@Abd: Totally agreed. I think that wv is a little bit of a rogue amongst WMF projects because it's not really clear what the scope of it is and even a decade after being founded, it's like the Wild West in terms of content. —Justin (koavf)TCM 18:11, 5 August 2015 (UTC)[reply]
Thanks. Consider what it meant to be the Wild West. It was a dangerous, difficult, and often undisciplined place, but should it have been therefore nuked?
The Wikiversity scope was deliberately maximally broad. There were two description: one was relatively staid, "educational materials." I think of class handouts that the teacher mimeographs prints and hands out. Wikibooks was for textbooks. Can we have very small textbooks? Okay, that's educational materials. There are plenty of Wikibooks that are wild like Wikiversity, because the wiki "designers," if we want to call them that, did not factor for the difficulties of maintenance. Hey, it's a wiki! It can only get better! Right? The reality: some does and some doesn't. Wikis are not magic.
The other description was "learning by doing." Learning what? Academic subjects only? How about How to build a pykrete bong, the standard Wikiversity punching bag. But I know children and teenagers, especially, give them freedom and they build an entire new world, using what they find, or creating it anew. Some of us don't want a new world, and dig in our heels to try to stop it. But it's useless, we don't survive, survival is a game we always lose, unless we see our own survival in those who come after us.
Showing them how to learn (by demonstrating it) is far more effective than trying to teach them what we have learned. Fishing vs. fish. Fishing lasts a lifetime, fish rot and smell bad very quickly. --Abd (discusscontribs) 18:54, 5 August 2015 (UTC)[reply]
What we can do is to offer the tools we have developed, maybe share some of our own mistakes, so they don't have to repeat them unless they want to check it out, but control them? No way. Attempts to do it generate screwed up kids, often emotionally and socially disabled.
@Abd: No doubt. Being the Wild West means that you can also go all kinds of places and make all kinds of content. Some of it very good, some of it very not, and some of it very weird. The fact that things are so loose here means that we can do some interesting and useful experimentation. —Justin (koavf)TCM 19:15, 5 August 2015 (UTC)[reply]
Folks, let me introduce Koavf, in case you don't know. This is the user whose account breaks edit counters, they give up. 1.5 million contributions cross-wiki. Now, a little point. Look at his en.wiki block log. It's long.
My Wikipedia Review signature has:
Abd's first law: To change the world, it must be easy.
Abd's corollary: If it's hard, we aren't doing it in the best way, or the world isn't ready to change yet.
Wikipedia Rule Number One: If a rule prevents you from improving the project, ignore it.
Corollary Number One: If you haven't been blocked, you aren't trying hard enough.
Some people are blocked because they are idiots unskilled. Some because they are trolls or have a disruptive agenda.
And some because they are working hard, and, not only will this correlate with more errors, if you follow Wikipedia Rule Number One, you will break rules, and sooner or later someone will enforce the rule. Wikipedia set up a very interesting experiment, but forgot that it was an experiment. The setup conditions rapidly became The Way We Do Things, and deviation became punishable. Some truly excellent users still work within that system, but by the time I ran into serious idiocy opposition, they were leaving in large numbers. The best -- those who tended to support my work, naturally! -- were retiring, formally or otherwise. Some soldier on.
So a special welcome to you, Koavf. We will be, I hope, developing some resources on wiki editing, best practices, etc. Your views would certainly be welcome. Unless, of course, you are wrong about something.
Just kidding. The right to be wrong is crucial. --Abd (discusscontribs) 20:02, 5 August 2015 (UTC)[reply]
@Abd: No doubt. I've always meant to branch out to more WMF projects and this one is definitely interesting because of its wide scope. I've posted a couple of feelers (you can see in my contributions) for studying Spanish and chess collaboratively but I haven't made any serious efforts on here yet. —Justin (koavf)TCM 20:08, 5 August 2015 (UTC)[reply]
@Koavf: While collaboration here is wonderful when it happens, this tends to be more like the desert areas in the Wild West. Most resources are developed by someone working alone. Or sometimes, years later, someone else pops in.
What is especially interesting here is the possibility of deep exploration of topics, with original research (which includes developed personal opinions). On Wikipedia, as you know, when people want to discuss the topic of the article, they are squelched. I'm looking to encourage Wikipedians to place sister wiki templates on Wikipedia articles where we have resources, and even to create matching resources here. Those frustrated wanna-be participants in conversation could be channeled here, and one can learn a hundred times as much from participation here as from an article on Wikipedia, and the knowledge can be more reliable (because sources will not just be linked, they can be reviewed, classified, studied in detail, discussed, etc. This is the good stuff that one can get from writing research papers at a university, in spades if one can find review by an expert. (As a result of my study here, this year, I was published in a mainstream peer-reviewed journal. As a result of my wiki studies, which I wrote about -- as condensed advice -- in some email with a Nobel Prize winner and some others, I was given an astonishing sum of money to support my work. So ... there is a real world out there, and it is not Wiki Land.)
On what became my Favorite Topic, Cold fusion -- contrary to what you might read in a certain ArbCom case, my interest in cold fusion came after I confronted admin abuse there -- there have been discussions here with people with very different views, and out of those, some serious questions were developed, taken to scientists, and answers generated, new knowledge, that didn't exist before. (In this case, those very familiar with the research techniques already knew the facts, but it had never been documented, and so one could imagine experimental artifacts that, in fact, were not possible. The new study was done by a skeptical scientist, who reviewed old experimental data, did the math, taking the suggestion very seriously, and concluded that if there was a problem, the suggestion wasn't it. Nice try, though!
In any real university, knowledge is not just transmitted, it is developed, and discussion is very much a part of that. In advanced models of education, students are not told the "answers." They are asked to inquire, discuss, test, experiment, etc.
I do a lot of wiki research. As a result, I know things about wikis and wiki behavior that may not be known, or known as deeply, by anyone else on the planet. That doesn't mean that I'm right. It does mean that my views are informed by a lot of experience. Any Wikipedia editor who does serious article research knows about this effect. Much of what you learn you cannot put in a Wikipedia article, because it is an encyclopedia, not a seminar on the topic. We have seminars on topics, you can go as deep as you like. You are not required to source what you write, not unless someone challenges it, and even then, we will neutralize possible POV issues with balance and attribution instead of removal or deletion. After all, your opinion is your opinion, and you are the world's foremost authority on your opinion.
This research, recorded here, can create a disorganized mess. However, these messes can be organized, a messy page can be summarized, for example, with the original archived to history. If someone does that, the work is highly educational! What is truly built here, though, is not the "educational resource," though those are being created. It is the educated person. What I am creating by my work here, all of it, is me. --Abd (discusscontribs) 20:42, 5 August 2015 (UTC)[reply]
Wow! Good read! Why don't we copy some of these insights on the vision-/ best practices page? Timboliu (discusscontribs) 08:57, 6 August 2015 (UTC)[reply]

hi my names is katrina edit

اريد التحدث بموضوع التاريخ

This was followed by the lede from w:Marylin Monroe and some test wikicode.

The Arabic means: "I want to talk any more about history." and then the user brought up some history, perhaps her specific interest. I will assume that her name is actually Katrina.
Katrina, welcome to Wikiversity! If you will add something to User talk:Abd, I will respond there, and help you find ways to discuss whatever interests you, on Wikiversity. I recommend that you register an account, which I can then support. As long as you edit without an account, your contributions, if there is anything out of place about them, or they are not understood, might be removed, as these comments were at first. So, to repeat:
  1. Register an account. If you cannot do this for some reason, it's okay, but it will all get much easier if you have an account.
  2. Follow this link [3] to add a comment to my user page. Don't worry. You may write in Arabic if you prefer, it is acceptable there. You are from the city where the oldest university in the world was founded, and that is important to me.
as-salaamu ^alaykum. --Abd (discusscontribs) 16:15, 5 August 2015 (UTC)[reply]
كاترينا، مرحبا بكم في ويكي الجامعة! إذا كنت سوف تضيف شيئا إلى نقاش المستخدم: عبد، وسوف تستجيب هناك، ومساعدتك في العثور على طرق لمناقشة كل ما المصالح لكم، على ويكي الجامعة. ننصحك بأن تسجيل حساب جديد، وهو ما يمكن أن تدعم ذلك الحين. طالما قمت بتحرير دون حساب، مساهماتكم، إذا كان هناك أي شيء للخروج من المكان عنهم، أو ليست مفهومة أنها قد تكون إزالتها، حيث كانت هذه التعليقات في البداية. لذلك، لأكرر:
  1. تسجيل حساب. إذا كنت لا تستطيع أن تفعل هذا لسبب ما، لا بأس، ولكنه سوف تحصل على كل أسهل بكثير إذا كان لديك حساب.
  2. اتبع هذا الرابط [4] لإضافة تعليق على الصفحة المستعمل بلدي. لا تقلق. تستطيع الكتابة باللغة العربية إذا كنت تفضل ذلك، فإنه من المقبول هناك. كنت من المدينة حيث تأسست أقدم جامعة في العالم، وهذا هو المهم بالنسبة لي.
كما: السلام عليكم. - Abd (discusscontribs) 16:15, 5 August 2015 (UTC)[reply]

Women's Volleyball edit

User Abd has requested a custodian to implement two suggestions that he believes may reduce IP vandalism and promote greater involvement of women here at Wikiversity. As someone who has played volleyball for decades, I am willing to implement these two suggestions, assuming I can figure out how and there are no Wikiversity-centered project objections. These as I understand them are

  1. assign User:Lainerraithe to a user group Wikiversity:IP block exemption and
  2. add 122.53.156.60 to Special:GlobalBlockWhitelist.

I will attempt to do these unless I receive Wikiversity-specific objections from other community members. Please feel free to comment, question, criticize, object, or record other concerns. I believe this effort is worthwhile for these reasons:

  1. we may be able to increase female participation in Wikiversity - this is a WMF-wide, and Wikipedia-specific serious concern,
  2. we may be able to produce a way to reduce IP vandalism,
  3. we may be able to increase participation here of collegiate-oriented, or professional volleyball players, as well as students at all levels, and
  4. we may be able to increase connectivity-based learning that is used to create the playoff-type grids this (these) users have been creating and constructing. --Marshallsumter (discusscontribs) 18:37, 6 August 2015 (UTC)[reply]
Thanks, Marshall. It is a long shot, as to these specific users, but is unlikely to do harm. If anyone wants details, I'm researching this affair at User:Abd/Volleyball; that is not complete and a report has not been written, it is only a study in process at this time.
This is a learning project, for me as much or more as for them. How can we increase our diversity, be welcoming, foster learning, clear project goals, and protect Wikiversity and other projects, and how do we do all of this efficiently? --Abd (discusscontribs) 19:44, 6 August 2015 (UTC)[reply]

In considering this request, it is important to also read User_talk:Billinghurst. This isn't simply a request to whitelist a user. It is also a request that influences steward participation at Wikiversity. That doesn't mean proceed or don't proceed. It just means understand the implications of the request before acting. -- Dave Braunschweig (discusscontribs) 21:15, 6 August 2015 (UTC)[reply]

That's an unfortunate suggestion, because there are no easy-to-understand implications that will be seen by looking at that page. It shows that Billinghurst is irritated that his action was privately questioned, and irritated even more when it was discussed, though he created that discussion. Had he merely ignored the mail or privately declined, or publicly declined without self-justification, it would have been over. That is more what stewards usually do.
There are no "implications" as to steward participation.
If anyone is concerned about negative impact from this, I encourage them to voice the concern, specifically, instead of with vague claims such as that it will "influence steward participation." I know both this case and steward practice quite well. --Abd (discusscontribs) 23:49, 6 August 2015 (UTC)[reply]
Delay can cause harm here. I have created notification of Team Volleyball, by adding a templated notice to all the involved user talk pages, to all the major Volleyball talk pages, and a templated notice on those major pages, addressed to Team Volleyball, to look at the Talk page. However, at this point, there may be no way for those users to contact us, unless they send email to me, my address has been provided, but this could be a big step for them. If this minimal action is done, they will have a way to communicate through the wiki. Blocked users that are not locked will be able to request unblock, etc., or they may simply work on the resources. Every time they see a notice that they are unable to edit, the probability increases that they will never look back. We may only have a window of opportunity. Hence, at this point, I request going ahead. I recommend that custodians and other users ping me if they see any related problematic editing. If there is any problem, the IP whitelisting can easily be reversed, and I commit to supporting any necessary cleanup.
In collaborating with users from another culture, we may need to develop cultural sensitivity. See w:Tampo. It is normal behavior, culturally, under the conditions these users encountered, that they not be communicative. --Abd (discusscontribs) 16:18, 7 August 2015 (UTC)[reply]
I understand that you believe you are absolutely correct in your actions, but you continue to act without first gaining support of the community. There is a choice to be made. Welcoming the users is rejecting the actions of a steward who has supported us. I again ask that you stop and let the community decide what it wants. -- Dave Braunschweig (discusscontribs) 16:53, 7 August 2015 (UTC)[reply]
Stop what? Correcting misrepresentations? Dave, you have made an unnecessary claim, based on your own interpretation of events, you continue to argue your position, then object when I respond to the claims you make. Indeed, let the community make the decision, if it wants to. --Abd (discusscontribs) 00:46, 8 August 2015 (UTC)[reply]
Locally unblocking is not "rejecting the actions of a steward." Detailed response with history.
I do not believe as Dave claims, and object to the ad-hominem argument. This is a wiki, my actions are visible, and have been supported. Nothing I have done requires a priori community approval. There is no opposition in what I've asked for to the action of the steward, who acted to protect global wikis from disruption. I cannot say that his action was outside of normal discretion and steward practice.
Other stewards have reversed such actions when it was requested, including a recent request by me. I initially made the request on WV:RCA, which is the proper venue for such. Dave argued against it there, but Marshall was inclined to grant the request, so he came here for review. Dave pointed to a discussion as an indirect argument against the request, a discussion where both of us (the steward and I) were highly informed about the situation, and understanding that situation, for others, would be work. It is not necessary, this is effectively an unblock, and unblocks can easily be done. There is no wheel-warring involved, no locally blocked user will be enabled by this request.
You could have objected to the action, formally, but, in fact, you simply declined to do it yourself and said "I won't stand in the way of any custodian who wants to oversee this ..." and then expressed an opinion that represents a surprising misunderstanding of how projects are created and run on Wikiversity. The default is not "no approval," the default is approval and, for example, we don't delete pages without consensus to delete. No consensus is required to keep, nor is consensus required for ordinary editorial actions.
My request here does not reverse the steward's action, and this is well-understood globally. This is one of the known uses of IP block exemption. Our exemption has no effect other than here. The steward suggested that the users could appeal the block at meta, but (1) they would have to know how to do that and probably don't, and (2) that would be asking for a reversal of the steward action, an entirely different issue, far more complex, because it would affect all the wikis, and at least some wanted these users blocked. A steward would not edit the local rights, this is generally a local prerogative, and the steward explicitly did not act locally. Billinghurst is not objecting to our allowing this work, he was explicit about that. We have long welcomed users who were blocked elsewhere, including users who were globally locked.
I know of one case where this caused local disruption, and in that case, I was not the one who unblocked the user, I saw that this would be premature without agreements being in place. My sense is that the unblock was a parting shot from a sysop about to lose his privileges. The interesting thing is that the user actually did some positive work for a time. It later broke down. I have never formally studied why and how. I'd rather not guess.
In another extremely controversial case, our community was divided, there was no consensus either way, but our standing tradition was to not block users who were not disruptive here; the user was blocked locally only for the reason of "global ban." In fact, the steward deciding that case had opined, when I asked him, that local communities could opt out. So I supported that, raised the issue, discussed it, there was no consensus for block, and our blocking custodian's clearly expressed opinion in a similar case (a global lock claimed to be a ban) had been "it takes consensus to maintain a block, not consensus to unblock" (which is strong wiki tradition). So, after discussion, I unblocked, and was emergency desysopped over it, without necessity. I have never wheel-warred. Yet wheel-warring was used to undo my action. I had discussed the issue, but reblocking was not discussed.
Dave, please drop the cudgel. The independence of Wikiversity is crucial. That does not extend to causing harm elsewhere, and this action not only would not cause harm, it would be more likely to prevent it. --Abd (discusscontribs) 00:46, 8 August 2015 (UTC)[reply]
I would need to see an explanation from the blocked users before supporting an unblock. I think Abd should be commended for reaching out to these people (or this person). But while Wikiversity's effort offer universal and free education to everyone is both noble and achievable, there are 7 billion people on this planet, and we cannot serve each and every one of them. If these soccer fans don't answer via email, it's time to let them go and devote our attention to people who seem more interested. --Guy vandegrift (discusscontribs) 03:10, 8 August 2015 (UTC)[reply]
Thanks, Guy. Not soccer, volleyball. I've asked for email, and I could verify the source IP of a mail to me, but we do not require users to set up email. What you are expecting is a cultural norm for us, response to questions that may be seen as confrontational. I don't know if you have looked at w:tampo. We are expecting something outside their cultural norms. We are accustomed, when we edit wikis, to behavior that would be, in some other cultures, highly offensive. We engage in this behavior, and thinklittle of it. It is "wiki normal."
You seem to think I am asking for unblock. The account I have named is not blocked, nor is it locked. Yet the user cannot edit here. Hence IP block exemption and global block whitelisting. This should not require high discussion, and like URL whitelisting, this should be routine for us. For obvious reasons, we only allow a few trusted users to edit user rights and MediaWiki pages, but when requested by a user in good standing, it should be done unless there are strong reasons against it. (And even then, unless the reasons are clear and expressed before it is done, it should be done, and then undone if emergency exception appears. These are basic wiki principles that allow normal efficiency.)
The IP is only blocked globally because a steward presumably identified it as Team Volleyball IP. That IP has edits here. It is not blocked here. It was not being disruptive as IP. The global issues are complex, and I'm not asking for a major move, I am asking for something very simple, something I'd definitely have done without hesitation were I a custodian, -- as, by our policy, I should be --, and I very much doubt that a flap would have developed. (I would not even have asked the steward, and the steward would not have objected or acted to prevent or reverse it.)
Some of Team Volleyball was locally blocked indef, but this was an attempt to encourage them to communicate. Their talk page access was not cut off. It is now cut off by the global lock, they cannot edit Wikiversity logged-in, and, because of the global block, they cannot edit anonymously, I am guessing this cuts off the entire island of w:Camiguin. The steward treated them as globally banned, ad hoc, but they are not globally banned according to global ban policy and the Terms of Use. I have demonstrated, many times, that users may, when locked, create new accounts here, and when they do not use those accounts disruptively cross-wiki, this is not a policy violation, and it is allowed, they are not pursued and locked.
It is obvious that the small team we have here could not do this for seven billion people. However, we can do it with one at a time, and we can set up scalable structure. All it takes, now, is one user willing to stand for inclusiveness, and cooperative custodians. Are there any other volunteers? Perhaps we need to have a true Wikiversity:Welcoming committee, not just a template that tells new users to Be Bold and then we slap them down when they are. --Abd (discusscontribs) 14:37, 8 August 2015 (UTC)[reply]

Two questions:

  1. What is the difference between a block and a lock?
  2. Is there a block/lock so strong that it cannot be appealed on MetaWiki?
I think the answers are: A "lock" locks the user from logging in. A "block" prevents the user from editing. If that is true, IP addresses are blocked, not locked, because they never log in (with a password). And, MetaWiki allows people to appeal a block from an IP address. Is this right?--Guy vandegrift (discusscontribs) 10:15, 9 August 2015 (UTC)[reply]
Generally correct. There are three states: blocked, locked, and banned. blocks and locks are of accounts, and are sometimes interpreted to be of users as well. I.e., if a user is blocked, and creates a new account, and this is blocked merely for "block evasion," this is evidence that the user is site-banned, at least during the existence of a block.
It is commonly stated on meta that a lock is not a ban, even though locks are used to enforce bans. Actual steward behavior, however, shows that some of them do treat locked users as banned. (alternate accounts blocked on sight, without any editing, sometimes). There are two kinds of global bans. The first was established by the community as policy, m:Global bans. This is a difficult process, reserved for massive disruption. It's really never been used since it was implemented, though it has been tried a couple of times.
If a ban is implemented by a lock, appeal is possible by IP. I've seen, however, the IP be immediately blocked, and the edits reverted, so ... maybe. Locks do not affect anonymous editing in any way and they do not prevent creating of new accounts. Recently, lock behavior was apparently changed to automatically cut off all email (from the user and to the user).
The other type of ban is a WMF Office action. Those used to be very rare, and very private. That changed at the end of last year, and it has caused enormous disruption, mostly on Commons, where a popular administrator was globally locked. These are not explained, and many users are concerned about lack of due process, but the WMF is adamant that this is necessary, and cannot be discussed.
Neither type of ban is involved here, and the lock was not based, as far as I can see, on a community request. I have often filed lock requests for cross-wiki vandals and spammers, and unless there is good evidence of cross-wiki disruption that cannot be handled locally, they will usually be declined. However, at the same time, some stewards routinely use global locks with newly-registered accounts, even with no edits. They are obviously checkusering new account registrations, looking for spammers who will register many accounts quickly, before using them. In the present cases, accounts were locked that had never been used. However, as I recall at the moment, they had obvious sock names. These users, in fact, did not attempt to conceal their connection with each other in any way. The obvious multiple sock accounts (numbered!) were used to allow them to set up user talk pages as templates, which they then used for content creation on Wikipedia. It actually worked for a time. They were never warned over it.
A global block is only of an IP address or range. Deliberately, they do not prevent editing on meta. So, yes, a user can appeal a global block on meta. However, in this case, the users in question have been, in the judgment of the blocking steward, disruptive globally. While a more careful examination of their contributions shows to me that this disruption was not as serious as it looks on casual examination, (for example, a huge number of edits to the user's own talk page), the fact remains that it is unlikely in the near future that these users will be making positive contributions anywhere but here on Wikiversity. Appealing for a lifting of the block, then, on meta, I would not personally support, not without some established behavior that would make this unlikely to be disruptive. We can handle a modest level of "disruption" here. That is, the user may make mistakes that require some work to fix. When welcoming users like this, I commit to personally providing that kind of support. I'm not committing to that globally, and couldn't do it anyway on en.wikipedia, where I'm banned.
What is appropriate here, then, is the very limited unblocking locally. This is done in two ways: by IP block exemption -- which is used for any account in good standing which is caught by a global block (which can happen with many causes), and by exempting the IP block from being active on Wikiversity. This would essentially allow any unlocked account to be used here, they would not be blocked because they originate from the blocked IP, which I suspect could be the only IP available from the island of Camiguin. There is no sign of any other IP having been used by these users. The global block exemption would also allow them to create new accounts here if they need that. Even if there is more than one of these users -- it is possible -- they may easily appear to a checkuser (i.e., a steward) as a single user. --Abd (discusscontribs) 19:59, 9 August 2015 (UTC)[reply]
I have assigned User:Lainerraithe to a user group Wikiversity:IP block exemption. --Marshallsumter (discusscontribs) 12:24, 13 August 2015 (UTC)[reply]
Thank you. That is a big step. However, we do not know that Lainerraithe is the same as the other users, we only know that the appearance is of identity, i.e., using the same IP and possibly the same computer or other similarities, leading to checkuser identification as socks. If there are users other than Lanierraithe, this will not help them. Because all (but one) of the related accounts were locked, they may attempt to edit IP or to create a new account, which, from history, will be easily recognized by the interest in volleyball. While any new accounts will not then be locked, they will still be unable to edit elsewhere because of the hard-blocked IP.
However, I will modify the templates so that if any member of Team Volleyball looks, they will see this development.
I will monitor contibutions of Lainerraithe and the IP to handle any difficulties. --Abd (discusscontribs) 13:24, 13 August 2015 (UTC)[reply]
I have added 122.53.156.60 to Special:GlobalBlockWhitelist, with the result, "You have successfully disabled the global block #50055 on the IP address 122.53.156.60 on Wikiversity." Good luck with the learning project! --Marshallsumter (discusscontribs) 19:15, 13 August 2015 (UTC)[reply]
Thanks, Marshall. It's a long shot, because once users conclude they are thoroughly banned, they often will not look back. But we can try. There is some possibility that this will bear fruit. It might take time. The unfortunate thing here is that the users did not set up email. That's all too common, I've found. However, email would not do any good with all but the unlocked users (a global lock disables all email to the user, now, it was not that way until sometime this year.)
Contributions for the IP shows both the global block and the local bypass: Special:Contributions/122.53.156.60. --Abd (discusscontribs) 22:50, 13 August 2015 (UTC)[reply]

meaning edit

--112.199.99.91 (discuss) 06:12, 7 August 2015 (UTC) hello, what is the meaning of the word Reich?[reply]

This is a start wikt:reich. —Justin (koavf)TCM 14:23, 7 August 2015 (UTC)[reply]


(edit conflict with above) This question was removed by a user who perhaps believed this was not the place to ask questions like that. However, we do invite "questions" on the Colloquium (see Template:Welcome, and, while we might want to keep the Colloquium for questions about Wikiversity, we have not made this crystal clear, and because we want to be welcoming, we also need to tolerate this, and a response should be in the place where the question was asked, ideally, or at least a link to a response. This is an IP user, creating special difficulties. So:
  • See wikt:Reich for definitions. I could say more, but not here. If you want to explore any issue here on Wikiversity, please go to Wikiversity:Help desk or to my User talk page and ask or comment. I will respond where you ask. Any other user may make this offer.
  • Register an account! This allows us to communicate much more reliably with you. If you set up email, which is highly recommended if possible, you can even be notified by email of changes to pages that you specify, and especially your own User talk page, so that you will know if anyone is trying to communicate with you. Email is private, and nobody will know your email address. You can control if other users can send you email through the wiki, and they will not know your email address unless you respond to them by email. I know of no good reason not to enable email, and have seen many, many problems when email was not enabled.
  • From your IP address, we see you are likely editing from Manila, or from an area of the Philippines served by a provider in Manila. We have a current situation with a set of users probably from Camiquin, similarly using, we think, an IP from Manila, probably a mobile phone provider. There are language and cultural difficulties, so, if you care to engage with us, you could be of help. Please consider registering an account, even if just to say "Hello." Put that on my talk page, not here! This page is intended for discussions about Wikiversity, or problems with the wiki or community or the like.
  • General questions may be asked on Wikiversity:Help desk. And....
  • Welcome! Thanks for your interest in Wikiversity. --Abd (discusscontribs) 14:30, 7 August 2015 (UTC)[reply]

power engineering edit

--119.154.208.205 (discuss) 07:57, 12 August 2015 (UTC)[reply]

Welcome to Wikiversity, all the way from Pakistan! The Colloquium is for discussing Wikiversity and the community. If you want to discuss the topic of power engineering, it is best if you register an account, because then it is easier to communicate with you. You may also ask questions of me or other users. To ask me a question or to seek help, you can add a topic on my user talk page with this link.

You may also look at School:Electrical engineering and participate there. Again, it is best if you register an account, but you may continue to edit anonymously; user accounts are actually more anonymous than the way you edited, which told me where you were from, probably. We do encourage real-name accounts here on Wikiversity, but it is not required.

(I have responded here because the user is more likely to look here. I will also drop a note on the IP talk page.) --Abd (discusscontribs) 13:23, 12 August 2015 (UTC)[reply]

Search results are prioritising talk pages? edit

I've noticed recently that Wikiversity search results seem to be be ranking talk pages higher than corresponding resource pages. Can others confirm? This seems undesirable. Generally, a searcher would want resource pages listed before corresponding talk pages? Example: Emotion regulation, Childhood emotion, Self-discipline -- Jtneill - Talk - c 10:45, 14 August 2015 (UTC)[reply]

VisualEditor News #4—2015 edit

This newsletter has been moved to Wikiversity:Newsletters/VisualEditor. If there is commentary relevant to Wikiversity, portions may be copied back here for general discussion. I am setting up the newsletter subscription to go to the newsletters subpage for the future. Anyone interested in following this may watchlist the newsletter page, or may subscribe directly, putting their user talk page on the distribution list. --Abd (discusscontribs) 22:21, 17 August 2015 (UTC)[reply]

Comment edit

We have moved other mass-posted newsletters to special pages. Those had resulted from a user here, who also had a personal subscription, putting the Colloquium on the subscription list. In this case, the newsletter is posted by a WMF account, who is using mass-mail with a separate list. If a newsletter has a special page, as with Wikiversity:Newsletters, then those who want to see the newsletter may watchlist the newsletter page, or may request a direct subscription. This newsletter, in particular, is likely to confuse newcomers, and the newsletter is not a discussion of Wikiversity, the purpose of the Colloquium. There is a subscription list. m:VisualEditor/Newsletter/Wikis with VE. As I have done this before, and it enjoyed rough consensus (and stood), I am creating Wikiversity:Newsletters/VisualEditor and will point the subscription to that page. After a delay to allow contrary comment, I will also move past issues of this newsletter from the Colloquium or Archives. If there was comment, I will specially handle that. --Abd (discusscontribs) 16:28, 15 August 2015 (UTC)[reply]

All issues have been moved from the 2015 Archive to the Newsletters subpage, so one can see the entire set of issues for this year there, and new issues should come into that page. I intend to move the remainder from prior years to year-specific archives. --Abd (discusscontribs) 17:02, 18 August 2015 (UTC)[reply]

Canvassing or notification of the knowledgeable of discussions of interest? edit

I was, today, warned by a custodian about canvassing. The warning and a discussion are at User_talk:Abd#Canvassing (permanent link). Comments are welcome there as well as here. I found this warning chilling. One of the standard wiki problems is premature discussion and "vote." When general participants, with no knowledge of a specific issue, are notified of a discussion by a post to the Colloquium, for example, when the discussion is just beginning, we often see knee-jerk responses, not informed. Hence I do not escalate discussions to the Colloquium, absent emergency, until there has been at least some support for a proposed change or action, and if there is no opposition, I don't bring issues here merely to "broaden consensus," if there is no sign of necessity. But, of course, anyone can bring an issue here if they believe it needs broader input. This is standard wikipedia dispute resolution process, if one actually studies it. One starts with small scale discussion. (It's often neglected, with much damage resulting.) In such small scale discussions, it is ideal if the participants are knowledgeable and if they develop evidence and clear argument. Then, if later needed, there is something for the community to chew on.

We have a proposed canvassing policy, I've worked on it some. As it is, I consider it only enforceable with high hazard. It requires a judgment of intention, which can be highly subjective. It also requires a decision process ostensibly under attempted influence, where numbers of comments will count, and does not apply to discussion process, which would naturally solicit participation by those known to be interested, until and unless broader input is considered necessary. Major changes to the page involved here have historically been made without soliciting broad comment.

The change I'd made to the deletion guideline page was not opposed, as to the actual change, not when I first proposed the change, a year ago, nor when I actually made it the other day. The only objection was process, that there had not been "discussion and consensus," that it was "unilateral." Given that discussion was initiated a year ago, the first objection was strange. However, the issue of deletion of files moved to Commons arose the other day, again, so I did make the change I'd proposed a year ago, and to which there has been no actual opposition. Nobody has argued, since the problem has been noticed, that we should delete files that have been copied to Commons.

That change was reverted as "unilateral."[5] So my first task was to identify if any user in good standing supported the change. Since there was an active discussion going on, on a user talk page, I informed that user. I informed another user whom I knew had experience with the issue. I pinged a Commons administrator who had just written on the issue. I did not "direct" any of these users to comment in any particular way. However, my selection can be claimed to be biased. However, that's a radical misunderstanding of wiki process. We want to avoid bias when we vote. Which, wink wink, nod nod, we don't do. In fact, we do, on occasion. If there is voting, there is possible damage from biased canvassing of votes. (The real problem, in that case, is a lazy closer.)

However, we were not at that stage of decision process, and still aren't.

So why have I brought this here? There is my obvious concern -- I have effectively been threatened with a block, that is how a notice like that from a custodian is routinely taken, and I have little doubt that if I repeated the behavior without suport, I'd be blocked. More, increasingly, I've seen signs of Wiki studies/Wiki disease in the behavior of the custodian. This syndrome arises when users takes and exercise high responsibility for the maintenance of a wiki, as this custodian has done. In other words, this can afflict our most valuable users. Slogging away at dealing with vandalism, spam, and disruption, the users begin to burn out, becomes impatient, and at the same time become increasingly controlling. After all, they are the most active users, surely they know better than those who are not working so hard. (And this may actually be true, but the thinking leads to more burnout.) So far, the deviations from policy that I've seen are small, and they normally start with what is on the edge, controversial. However, over time, established policy and traditions are shoved aside and the user's actions become more and more abusive. We have already suffered some damage, which I will document if it is ever necessary. I hope it is not. What I suggest is that the custodian recognize that he has become peevish and unfriendly. That's a sign of the syndrome. The way for healing to take place is to back off, support wider community involvement in, say, deletion decisions and especially blocks, and to become careful about warnings, all of which have, in the past, driven users away. --Abd (discusscontribs) 18:25, 18 August 2015 (UTC)[reply]

  Comment

  • User:Abd has been changing Wikiversity:Deletions without first seeking consensus. The community needs to decide whether it wants users to discuss proposed changes to policies and procedures before changes are made, or if it wants users to be free to make changes and have someone else catch and challenge the change. To me, consensus requires discussion before change rather than discussion after the fact. To act unilaterally is imposing one's will on the community. But I will support the community's decision one way or the other.
  • Separately, the community should decide how it wants to be informed of such discussions when they occur. Should policy and procedure changes be left to the discussion page of the associated policy or procedure, or should they be brought to the colloquium or (to the extreme) placed in a system announcement? It is my perception that most users do not watch policy and procedure pages, and would be left out of the discussion if notice is left to the discussion page only.
  • Regarding canvassing, any attempt to select individual users for notification is inherently subject to interpretation. There's no need for it when we have ways to inform everyone of relevant discussions. The community should decide whether it supports selective notice or whether it prefers open notice on these discussions.
  • Finally, regarding the unnecessary drama, hysteria, and personal attack included in the post above, I leave it to the community to review the relevant posts and determine whether my actions represent appropriate custodianship of Wikiversity by limiting unilateral actions that do not have demonstrated community consensus, or whether this effort is exceeding the community's wishes.
  • Dave Braunschweig (discusscontribs) 19:09, 18 August 2015 (UTC)[reply]
  •   Support I support both of you for bringing this matter here as well as discussing it at Wikiversity:Deletions. This seems to be a complicated matter, especially regarding transferring files to Commons, followed by deletion of the File here.
One idea that occurred to me after reading some of the discussion was that we could somehow here categorize files transferred to Commons and deleted here so that if they are deleted at Commons we could evaluate them here and restore their visibility as a Fair Use file.
Another matter is downloading a file from Commons that I use here so that if Commons deletes the file I have a copy here. Not deleting files transferred to Commons or copied here from Commons for potential availability may be a further complication. Someone would probably put the duplicate here up for deletion (because there is a copy at Commons) only to be zapped if Commons deletes the file there. So a general policy of not deleting files that exist at Commons and here may be better. Or as Green Giant has commented finding a better solution at Commons that doesn't hurt the other WMF projects may be the way to go. --Marshallsumter (discusscontribs) 20:21, 18 August 2015 (UTC)[reply]
Support what, Marshall? Meanwhile, I did not bring the issue of the deletion guideline here, that is still under discussion on Wikiversity talk:Deletions. This is only about the claim of "canvassing" and the warning, because I do not disregard administrative warnings. I either accept them or create discussion of them. (And that is how I have advised many other users.)
My position, expressed here, is that Dave has become over-involved. That is not a "personal attack," Custodians must be open to criticism like that. I have not yet presented evidence of over-involvement, but Dave provides it here. "Unnecessary drama, hysteria, and personal attack" is a personal attack. If Dave had not become involved, he'd know that. His behavior has shifted.
I am not a custodian, and being subject to a personal attack by a custodian is a matter of concern. Who restrains custodians? I know how to do it, and I've done it. It's an ugly mess and requires a huge expenditure of time. I would vastly prefer to avoid that. Nevertheless, wikis will go downhill if the community does not prevent it. It is natural.
If Dave wants to raise the issue of guideline change process, he's free to do that, but that is not why I created this. I created it because Dave waved his block tool at me, and now insults me because I refer to it. He has not neutralized the threat.
The warning was not about changing the deletion guideline page. It was about alleged canvassing. As defined in the Wikipedia guideline, and as defined in our draft policy, I did not "canvass," because there was no open poll. There was a discussion, and inviting concerned users to a discussion is not canvassing, it is just plain common sense, and a step toward generating consensus, which is only complete if objection vanishes. But Dave has, I'm suspecting, developed a win-lose mentality here. He thinks what I was doing was "wrong," so it must be stopped. That is precisely Wiki disease.
So what is really going on here is an assumption of bad faith on the part of Dave. He thinks of what I was doing as attempting to "impose" my "will" on the community. Yet no edit to the guidelines can do that. Further, it is the contrary of what I want.
I was threatened with consequences, effectively, for doing what I consider normal on wikis, facilitating informed discussions. That's not tolerable. How we actually change policies and guidelines is secondary to this, and is a separate issue.
If I do what I did in inviting comment, in this case, not as a general principle, is Dave allowed to warn me not to do it, backed by his authority as a custodian? --Abd (discusscontribs) 20:51, 18 August 2015 (UTC)[reply]
  •   Support Please see the discussion Talk:Art practices were Abd has informed me that he is planning to "escalate" (I thought this was a transitive verb), which I understand as suggesting that he will canvass again. He has also indicated that he is considering turning this into a "test case". I also feel that Abd is misrepresenting Dave Braunschweig, who requested that he stop canvassing. This, imho, falls short of a warning, much less a formal warning, which would have to explicitly state that it constituted a formal warning in order to be such. I find myself in agreement with David that he has been subject to a personal attack, and I do not feel there is any basis to Abd's claim that this in turn is a personal attack.Leutha (discusscontribs) 16:19, 30 August 2015 (UTC)[reply]

Newbie to wikiversity policies edit

Hi, I'm new to the Wikiversity policies, but I would like to participate in the discussion. I tried to read the above conversation but I don't understand what the questions are. Is the question what cavassing is? Or should it be allowed to ask other users to participate in a discussion? Maybe someone can explain in simple words what we are talking about? Thanks! Timboliu (discusscontribs) 10:37, 19 August 2015 (UTC)[reply]

I started the section, and my question is whether or not I should be formally warned for inviting users to participate in a discussion, according to the example given. A formal warning is a preceding step to a block. So, if I repeated what I actually did -- which was documented either here or on the linked talk page discussion -- could I be blocked? The question is really about administrative behavior. However, the canvassing issue is related.
I would agree that if I violated our canvassing policy (even though it is only a draft), a warning could be proper.
Canvassing is defined in our page, Wikiversity:Canvassing, which is a proposed policy, and w:Wikipedia:Canvassing, which is an approved guideline there. Our policies can and do differ from those of Wikipedia, but an assessment of canvassing has to do with voting and a biased solicitation of voters. I have given my interpretation of what I did, and it was not canvassing, neither in intention nor in practice (because no voting had been set up). It was invitation to discussion, which is allowed -- and which can be biased, in fact, but bias is difficult to prove or disprove. Perhaps Dave might want to explain differently.
Another issue raised is civility. Where there violations of WV:Civility policy here? I would not raise the issue at this level of incivility except that the user I consider to have been uncivil is the administrator warning me. Thus my concern is amplified. In the other direction, I have noted what seems to me to be a pattern of behavior that commonly develops on wikis. That could be considered "personal," but administrators, traditionally, are expected to be subject to criticism at that level. So that's another issue for community consideration. --Abd (discusscontribs) 21:26, 19 August 2015 (UTC)[reply]
Abd, Thanks for the explanation. According to me, asking other people to join a discussion should'nt be a reason to give someone a warning. Timboliu (discusscontribs) 14:04, 20 August 2015 (UTC)[reply]
Thanks. Frankly, I think we should dump the canvassing policy entirely, even for polls. But this requires clarity on how discussions are closed, i.e, turned into actual decisions. Canvassing is a problem with voting where numbers matter. It is more of a problem, as well, when there is off-wiki canvassing. So it is weird to sanction on-wiki canvassing when off-wiki canvassing is so easy, and isn't transparent at all. There are better solutions that will improve the quality of discussion. That will take some work. --Abd (discusscontribs) 14:16, 20 August 2015 (UTC)[reply]
I'm not quite sure of all the background here, but Dave may be concerned that at times I will back Abd on issues when it may not be wise to do so. I both respect and listen to his opinions. Regarding the canvassing, I was accused of doing this on Wikipedia by asking those who in the past had voted in my favor to vote on the dominant group issue. Asking those who had voted against me in the past seemed pointless. The problem with the canvassing issue is the presumption of guilt. Those who had voted in my favor in the past voted against dominant group indicating to me that the issue was too hot for Wikipedia. I placed no faith in those who had voted against me in the past because they never showed objectivity. The question of canvassing to me means summoning a gang (or my favorite: a bunch of drunks in a bar) to support one's position independent of objectivity. I believe Dave is referring to how others may view perhaps my loyalty to Abd. I do evaluate each action I decide to endorse. But Dave is right if he's referring to predicting the actions of power people. Sometimes even giving the appearance of summoning a bunch of drunks in a bar may cause undue harm. I hope this helps. --Marshallsumter (discusscontribs) 22:19, 20 August 2015 (UTC)[reply]

From Wikiversity: Canvassing, "Canvassing is contacting like-minded individuals to coordinate efforts for a pending decision." The discussion in question is clearly intended to generate a decision, so any suggestion that this isn't canvassing from that point of view is a non-starter. The potential arguments that could be made here are whether the individuals are like-minded, and whether any efforts to coordinate are involved. I would say that the individuals contacted were, indeed, like-minded, but no overt effort to coordinate a response was included, nor would overt efforts to coordinate be necessary. The simple notification is an effort to coordinate like-minded individuals. But, most importantly, it is an unnecessary approach intended to limit discussion to those invited rather than including the community in a public discussion on Wikiversity policies and procedures.

This has nothing to do with the individuals involved. The best policies are developed when you don't know which side of a policy you will be on when it is implemented. The assumption that any one of us should be left out of a discussion of Wikiversity policies and procedures, or that any one of us would attempt to influence that discussion by inviting only certain members of the community to participate violates my appreciation of the spirit of community. A discussion on policy or procedures that any of us should be invited to is a discussion on policy or procedures that all of us should be invited to. It's that simple.

Dave Braunschweig (discusscontribs) 23:00, 20 August 2015 (UTC)[reply]

The above presents a straw man argument: that anyone should be "left out." It completely misses that broad invitation before there is even a single agreement is premature. Classic deliberative process will not even consider a proposal until it has a second. And members of organizations routinely "solicit" a second. Whom did I invite? One of the founders of Wikiversity, a custodian, Marshall, and a Commons administrator. While I had an idea about likely positions of the first two, the third was invited for expertise. Only Marshall and the Commons custodian have commented. The idea that I want to "control" Wikiversity by selective and biased invitation is an accusation of bad faith. It's uncivil, and it should stop. All what I did would do is to likely cause some additional comment there. Anyone who thinks there should be wider participation would be welcome to also invite others. There was no poll, so no "canvassing," at all. This is completely crazy that inviting others who would be known to be interested in or who would have something to contribute to a discussion, is considered a prohibited thing, and Dave is not reassuring me that there is no hazard, at the same time as he misrepresents my position. Notice: he states that "attempt to influence a discussion" violates his appreciation of the spirit of community. But academic communities, especially, need and respect diversity. And people do advocate for their positions. Functional communities not only tolerate that, they welcome it. What violates the spirit of community are assumptions of bad faith, straw man arguments, unnecessary warnings by administrators, accusing someone who complains about a warning of "hysteria," custodians who use tools according to their own opinions and without necessity, and so on. My advice to all users has been to heed warnings, but to appeal if you disagree. So I appeal, and encounter more incivility. Dave is not an ordinary user, he has block buttons, and he's used them. He does -- usually, not always -- warn before blocking. So he warned. I'm supposed to ... what?
This is what I'm supposed to do. I'm supposed to appeal, to ask the community to resolve a dispute. If it doesn't happen here, I know what to do, it is WV:Community Review. What I'm seeing is intransigence on Dave's part. He is insisting that there was a hazard to the wiki here, requiring a warning. He is arguing strongly for it. That's his right, but ... it will lead, if there is no consensus negotiated, to a CR. Otherwise my participation in Wikiversity governance becomes entirely too hazardous. I need to know. --Abd (discusscontribs) 01:45, 21 August 2015 (UTC)[reply]
The concept of "inviting everyone" is devastating to participation, it actually kills it if over-used. The "community" should be explicitly invited only to prepared process, where evidence and arguments are already in place, which the community may then review and accept or reject. We are all invited to every page on the wiki, all we have to do is what Dave does, and what I sometimes do, watch Recent Changes. However, wikis don't work by "inviting all" until there is some level of presentation of evidence and arguments. Otherwise, one will may routinely get shallow, uninformed opinion. Further, if people are often invited to premature decision-making, they burn out, they stop responding. --Abd (discusscontribs) 01:21, 21 August 2015 (UTC)[reply]
Extended review and discussion (to see this, click on the down-arrow on the right)
Rather, when wikis are functional, decisions are made ad-hoc. One person may make a change. If that is opposed, then there is discussion, starting with the two. w:WP:DR was my long-term study. If the two cannot find consensus, then involve a third or sometimes more. I often did this with good effect. This is not yet at the poll or RfC level. So, if consensus cannot be found with three or so, there is RfC. This is the first process that is collective, everyone invited. However, in fact, only those who follow the RfC link pages show up. Then (often skipping RfC) there are noticeboards, and this is where many users go. It is where pitchforks and feathers are ready, with a pot of tar simmering. The founder of w:WP:ANI later wrote that he regretted it. (Sane users do not have ANI on their watchlists, it overwhelms everything else. It could have worked, but only with organizing structure, and Wikipedia never figured out how to do that. Noticeboard filing, early on, generally neglects mediation, which is another step short of full community notice. Arbitration is considered the last resort, but, in fact, the other steps are often skipped even with ArbCom filings.
So the system works better when a dispute, or proposal, is first discussed by a very small group. Routinely, for years, I have often proposed changes to policy and there has been no response. That's normal on wikis. I then, after a decent pause, go ahead and make the change. I have the first level of consensus, no opposition to a proposal. (It's very similar to actually making a change that nobody objects to.). If anyone objects, there is, then, no-consensus, and so we discuss and attempt to find consensus.
So: consider WV:Deletions. This was marked "guideline," by placing Template:Guideline at the top. How did that happen? Was the community consulted? How?
I had worked on the proposed policy in 2011. I was then blocked for almost two years, it's tempting to bring in the story, because it's related, but I won't. In 2012, then, there were major changes made to the page, and there was a straw poll. One might notice that while the poll was in process, from 10 January 2012, to 16 February 2012, there were still changes being made. This is a common process issue on wikis: there is a poll on something but what the something is, is a moving target, so how does one consider the early comments? Often the distinction is totally missed, and early comments supporting a proposal are taken as support, even if the proposal changed greatly. This is a wiki structural problem.
The close was to mark the page as a guideline. Now, had the community been invited? Yes. Wikiversity:Colloquium/archives/January_2012#Discussion_to_confirm_the_Deletion_policy.

However, to what were they invited? A discussion? No. A poll, with a stated purpose of "confirming the deletion policy." This is that Talk page as it would appear to anyone following the link at that time. I'd look at this and say "Huh?" There were just massive changes. Have they been discussed? Collingwood objected to the poll being on that page. Darklama objected to the objection. No further discussion occurred on the Colloquium. Do people know who Collingwood was? I was very interested to see that comment, because there was another Colloquium request a little after that, from a very low edit count user that I might have suspected was Collingwood. If Collingwood was socking at that time, he was risking his entire position. I don't think he'd do it. Anyway, Collingwood was highly experienced, if he is whom the WMF claimed, he'd been a bureaucrat and checkuser and administrator. I don't agree with his objection, that talk page was the place. However, Collingwood did not object to the real problem. Massive changes with no invited review of a discussion. He did point out a related problem, lack of specificity.

In fact, there was no discussion. Looking at the history of the talk page, 2 days before the invitation to the straw poll, Darklama had moved all the discussion on the Talk page to the Archive which he created for that purpose.[6] The last discussion on that page had been proposed changes ... by me, before I was blocked. Some changes I'd made stuck. The massive editing from January 6 to January 10, when the poll was created, was done with no discussion other than in edit summaries.
I consider the tagging of the page as a guideline as being established consensus, but I'm pointing all this out to show how ragged our actual practice is.
There are so many questions. First of all, active in editing in the short period preceding the poll: Claritas, Adambro, Happy Camper, Darklama. and Begoon. They were, then, active, and can be expected to be likely to comment in the poll. Begoon did not comment.
Who commented? The poll was started by Claritas, first comment from User:MyNameWasTaken, asking WTF? My brief summary! Collingwood suggested that the actual version being voted on be linked. Happy Camper wrote that the goal was to involve more editors in editing the page... so it would change. He says the poll is "just a straw poll to get a sense of where things are at." It was already clear where they were at, before the burst of editing. The proposed policy page was functioning as policy, and was not under heavy dispute. That is, there was already general consensus on it. However, a large pile of undiscussed changes would shift that. The page was a collection of subpolicies, each severable. Normal creation of documents like that is done piecemeal. Happy Camper's response was contradictory to the stated purpose of the poll. It is likely that the closing consensus (Happy Camper's close) was to adopt the page, not as policy as the poll stated, but as a guideline, and the sense was that lots of work remained to be done.
Leutha opined that if the poll was supportive, the page should be protected to protect it from change. So Leutha was thinking about a policy, as the proposal was labelled, though we haven't had a policy of protecting policies. And we have had at least one user supporting this poll who had, in the past, made major changes to policy pages without discussion. Of course, he's a custodian....
User Rf commented in support. This user has low edit count, so almost certainly came from the Colloquium announcement.
Marshall Sumter made extensive comments. Wasn't happy with aspects of the page as policy. Ultimately voted Oppose, unless particular language was used, "Deletion can harm Wikiversity when participants are lost and works that could have become useful with enough time are removed." That language was not incorporated. However, then, there was discussion with Happy Camper and Darklama, and Marshall agreed to the "guideline" proposal, and it was as guideline that consensus appeared, at least among those who continued to comment. It was expected that there was going to be subsantial work on it, but this has been common on Wikiversity. Work was done, changes were proposed, and ... nothing. No comment. So, then, the proposer -- often me -- makes the change. Reverted because "not consensus." That is absolutely crazy. If it's wrong, if it's harmful, if it's damage, revert it! But just because it isn't consensus? How does it become consensus, without specific editing? Policies are stronger, and changing a policy without discussion is problematic, but Wikiversity has always allowed changes to even policies without discussion if nobody objects." And look at the page history: Lots of changes without discussion, even after tagged as a "guideline." Were they "substantial changes?" That's a matter of opinion, isn't it?
But there was discussion in the instant case. There was no revert warring, that is really what the "guideline" guideline means. This was never intended to prevent editing; if it was desired to prevent editing, the page would be protected, forcing custodian approval, which properly would be based on discussion (not the custodian's personal opinion).
My opinion: the announcement on the Colloquium was necessary for policy, but, in fact, a policy discussion should have been firmly grounded in a set of discussed sections of the proposed policy. It should have been site-messaged, not merely announced on the Colloquium. Before going to the Colloquium, the users should have high consensus, if possible, on each section, individually. (It's well known that voting on a complex proposal en masse is poor process, unless preceded by careful, detailed process). Then the community would be asked for additional comment, on the Colloquium,. which would be considered to create a final proposal likely to be approved with genuine consensus.
The final proposal, then, would be a Yes/No poll on a specific version, as Collingwood wanted to see. Wikiversity has only rarely done good process on this stuff. Mostly it's difficult to get any participation. However, if there is a small working group that finds internal consensus, that presents a proposal that is well-thought out, kinks are already worked out, and this is then submitted to the community in a clear way, such that opposition is welcomed, if no opposition appears, this may be considered high consensus. A closer should consider all evidence and arguments. If we want something wider than that, we need the Wikiversity:Assembly. Where are our political science professors?
As to canvassing, canvassing has no effect on actual consensus. It reveals the position of individuals, only. Decisions are not to be made by numbers of votes, and we except custodian/bureaucrat votes (and sometimes removals) as an exception, and that exception has clearly done harm here. The problem with canvassing is created by poor decision process that violates w:WP:NOTAVOTE. --Abd (discusscontribs) 01:21, 21 August 2015 (UTC)[reply]

Learning project applications edit

Hi,

I would like to start a learning project about applications.

Who wants to help me set up this learning project?

https://en.wikiversity.org/wiki/User:Timboliu/Applications

Regards,

Tim, Timboliu (discusscontribs) 21:44, 18 August 2015 (UTC)[reply]

Hi Timboliu, what kind of applications do you mean? --I8086 (discusscontribs) 00:16, 19 August 2015 (UTC)[reply]
Hi I8086, examples of applications are: Microsoft Excel, WebMaker. Here you can find an overview of some applications. We could not only describe their functionality, but also make suggestions how an application can be improved. Timboliu (discusscontribs) 08:15, 19 August 2015 (UTC)[reply]
Those sound like the applications I know! I'll try to work on them whenever I get some time on Wikiversity. --I8086 (discusscontribs) 13:57, 20 August 2015 (UTC)[reply]
I8086, Great! I love to hear about your favourite application. Timboliu (discusscontribs) 14:00, 20 August 2015 (UTC)[reply]

How can we improve Wikimedia grants to support you better? edit

Hello,

The Wikimedia Foundation would like your feedback about how we can reimagine Wikimedia Foundation grants, to better support people and ideas in your Wikimedia project. Ways to participate:

Feedback is welcome in any language.

With thanks,

I JethroBT (WMF), Community Resources, Wikimedia Foundation. 05:22, 19 August 2015 (UTC)[reply]