Somebody should update this page to reflect that he left the WMF last October.
User talk:Jorm (WMF)
About this board
|This page uses the Flow extension, a new piece of discussion and collaboration software. We need your feedback at Talk:Flow or en:WT:Flow (not on this page, please!) over the coming months, to help make it the system we all want to use. Please do random testing at Talk:Sandbox. See the Main FAQ and the Design FAQ for some basic details and answers, and a list of future feature ideas that have been suggested so far.|
Previous discussion is archived at User talk:Jorm (WMF)/Archive 1.
Out of date
It was November.
Source codes for LiquidThreads version 3
Hi could I have the source codes for liquidthread version 3 please.
126.96.36.199: I'm sorry, but there isn't any source code for LiquidThreads version 3.0. We never made it into the development cycle.
Oh ok but when building the project didnt you save the codes they may not be in development now but they would have had to be saved some where.
188.8.131.52: There are designs but there isn't any computer code. There's nothing to have been saved.
Partial Apology and Questions
My apologies for losing my cool on the Flow talk page a few days ago. It was just such a shock that something that I hadn't heard of was well underway. That said; I still think the system is extremely flawed and not anything I want to partake in. Now, I want to ask a few questions that I think need clarifying. It's your choice if you want to answer them, but I think it would help a bit with the mass confusion involved with this.
1: How does this affect the MonoBook skin?
2: Will Twinkle be adapted into new systems?
3: Why is the history page disjointed on Flow pages? Keep it all together.
4: Don't you think this new system gives administrators too much power? I'm very weary of someone being able to deny my opinions like that. In the current system, opinions are at least fairly considered and easy to revert back in, if need be.
5: Will older pages be archived with the current Talkpage system? This question is an obvious deal breaker.
6: Why does Wikipedia seem to be copying Wikia now-a-days*? First Visual Editor (which was tolerable except for not being able to code correctly), and now this.
7: Will SineBot be deactivated?
8: Why can't I make an edit summary?
Thank you for looking over this and considering my opinion. However, I think that we'll be like a ghost town by 2018 if this goes into effect. Not to sound threatening; but I'll try to code out the Flow system on my talk page if I'd need to. If I can't find a loophole, I sincerely doubt that I could use Wikimedia or any other Foundation websites; except to view articles.
- Yes, I know Jimbo owns both websites. We're supposed to be at a more professional level though.
By the way, I don't want the asterisk to bullet. That looks way too much like something you'd do in a PowerPoint.
Thebirdlover: Hi. I'm the community liaison assigned to this project, so I'll jump in and offer some answers.
- It should work fine in MonoBook, but do let us know if you find any bugs.
- Building Flow up into a cohesive system that works with, and improves, our existing workflows, is definitely part of the plan. Bots etc, too. An API overhaul is underway, by an experienced bot-wrangler dev.
- The Board-history and Topic-history pages are currently being overhauled. (They'll look drastically more like what we're used too, at some point soon). Having a separated Topic-history will be incredibly useful, but they do indeed need&intend to also include the full Topic-history within the Board-history.
- There's a good table of "experimental vs confirmed" settings, at Flow/FAQ#Components of the discussion system, which should help explain this (see the "Comment editing" row, in particular). See also the item further down that page, Flow/FAQ#Will we be able to edit other people's posts?
- See Flow/FAQ#What will happen to current talkpage discussions?
- There are various projects to make Wiki[p/m]edia less complicated for people aren't at ease with dense markup text, and also to improve the processes for those of us that are comfortable with it all. (Eg. I for one, will be very happy to not be using <dl> and <dd> markup to create comment-indents (as we currently do with :: etc). Properly separated and attributed posts, with individual histories, will make various powerful tools a lot easier to integrate with our discussions.)
- Sinebot won't be needed.
- There's a good discussion about Edit-summaries at w:Wikipedia talk:Flow/Archive 7#Edit summaries. I recently posted a followup update at w:Wikipedia talk:Flow#Watchlist items (but check out that initial discussion first).
- Flow is currently just being developed around wikimarkup editing (aka' edit source'), hence your asterisk should be a bulletpoint! The VisualEditor will be added as an alternative input method, in the near future. (An easy addition, as it's all built on Parsoid).
There are tons of features yet to come - this is a very complicated and long-term project (1-2 years at least), that needs our (community) input throughout the process. Slow and steady improvement will turn it into the upgraded system that everyone wants.
HTH. I'd suggest asking further/followup questions on the Flow talkpage (mww or enwiki), so that other interested editors can help answer, or add to your questions. :)
Just so you know, I don't mean to sound snarky. I hope I didn't give you that impression.
Aww, you have no love on your talk page :(
Well it took me a good 14 seconds to find out how to reply. Was expecting to press a button / link in the gray box saying "Aww, you have no love on your talk page :(".
Also Wikilove is not around :-(
Hopefully I will received a notification whenever someone reply :]