08:24, 16 December 2013 (UTC)
Jump to navigation Jump to search
Reply to "Global Collaboration products newsletter: 2017-11"
Reply to "Latest message for Collaboration team newsletter; Growth team's newsletter invite"
Reply to "Support Low-Budget Wikis"
Reply to "Alterar Página Principal"
Reply to "Summer of Code proposal feedback"
Reply to "Collaboration products newsletter: 2018-03"
Reply to "Collaboration products newsletter: 2018-02"
Reply to "Global Collaboration products newsletter: 2018-01"
15:36, 21 November 2017 (UTC)
Latest message for Collaboration team newsletter; Growth team's newsletter invite
Sorry to use English if that's not your favorite language.
You are receiving this message because you were reading the Collaboration team newsletter.
The Collaboration team doesn't longer exists. That team was working on building features that encourage collaboration. This is the latest message for that newsletter.
The Growth Team, formed in July 2018, supports some former Collaboration projects. The Growth Team's main objective is to ease new editors' first steps on wikis, through software changes. You can discover all objectives and missions of the Growth team on its page.
If you wish to be informed about Growth team's updates about easing new users first steps, you can subscribe to the new list to get updates. The first message from Growth –with a call for feedback on a new project– will be posted in a few days!
If you have questions or you want to share experiences made on your wiki about new users' first steps, please post them on the team talk page, in any language.
Support Low-Budget Wikis
I'm building a wiki on a shared webhost, who doesn't support node.js.
Of course i love the new VisualEditor, but without node.js, we cannot use it.
Meantime, WikiEditor is really showing it's age. Other wysiwyg editors, like TinyMCE, CKEditor, etc are buggy or no longer supported (mostly the latter).
I strongly believe MediaWiki's social mission compels you to support low-budget wikis. But if WikiEditor continues to be lame and neglected, while VisualEditor gets all the attention, then you're being elitist, and neglecting MediaWiki's social mission.
Looking forward to your reply.
Hi, I have been thinking about your question and what comes is my personal answer. I am not "the right person to contact" but maybe I can help you.
There are wiki farms out there offering free wikis, also with VisualEditor and/or decent editors. Would this be an option for you?
If it's configurable as I need, and going to exist for years, then yes.
I tried the following for a while, and it wasn't bad.
But self-hosting offers more of the options I need, and I know it's not going anywhere.
Note, running a private server is resource intensive, as you mentioned. But shared hosting is less so.
According to this list, miraheze is the only free option that supports visualEditor (with no advertising -- that's a requirement).
Know of any others?
The few paid options matching my self hosted features (incl domain, extensions, flex licensing, custom permissions, etc) plus visualEditor start at yearly $100+ on up to $3,500.
That's not what I would call "low-budget".
My shared hosting, which includes all above plus email hosting and webhosting for 2 more websites, is $15 first year, $50 ea year after. visualEditor is the only missing piece.
My main point with this thread concerns WM core, not hosting. The whole point of open source is access, not restriction.
When it comes to the Wikimedia Foundation, the priority is to improve the user experience of editors, including those without the luxury of a desktop or high bandwidth. Plans go in the direction of offering a better mobile editing experience, because for millions of people low-cost really means regular access to mobile but less so to a desktop.
I guess this explains why the Foundation is investing in VisualEditor and mobile editing via web and native apps, and why there are no plans to develop the legacy editors further.
But anyway, as said all these are just my personal opinions. My talk page and myself are in fact not the best to provide the best informed answer. If you want to discuss this further, I recommend you to do it directly with the developers at the wikitech-l mailing list.
Extensão para relatório de acessos
Bom dia amigos.
Preciso saber quantos acessos foram realizados por página. Existem alguma extensão que faça isso?
Hi, this is just my personal Talk page. If you have more questions, please ask in Project:Support desk, where others will be able to help as well. Thank you.
Alterar Página Principal
Preciso alterar a página principal utilizada pelo sistema, ao abrir preciso que chame uma página especifica e não a página principal.
Também gostaria de saber se há a possibilidade de alteração do nome de uma página já criada.
I solved the problem with your tip. Thank you very much.
Summer of Code proposal feedback
Hi Qgil! I've been working on my Summer of Code/OPW proposal and was hoping to get some feedback on it before I got too far along. It's not on the list of recommended project ideas, so I wanted to make sure you thought it was feasible and that it had some chance of receiving broader support. Thanks! (talk) 12:49, 11 April 2013 (UTC)
Interesting idea, and very good project proposal structure overall. You have clearly invested a lot of thought and time already. Congratulations?
Have you found a mentor? In any case, the next steps recommended are:
- Creating a new enhancement request in Bugzilla, unless there is already an open report about this.
- Sending an email to wikitech-l pointing to the wiki page of your proposal and the bug report.
Good luck! And see you there.
I have not found a mentor yet, no. I sent an email yesterday to User:Raylton P. Sousa, who maintains the BookManager extension and was on the mentors list for GSoC 2012, but I've not heard back as of yet. Do you have any suggestions for people who might have relevant knowledge and would be willing to mentor?
As for Bugzilla, there are quite a few bugs that are somewhat related. The issue of having a way to represent books is namely mentioned in bug 15071. There are also a number of bugs specifically related to the BookManager extension here. Do you think I need to create a new request, or are these close enough?
I will send an email to wikitech-l shortly.
Bug 15071 is blocking several others and it's followed already by 12 people, including some maintainers that have commented. So yes, it's a good destination to announce your project proposal.
Raylton was indeed interested in mentoring. Being a maintainer of the BookManager extension and a pt.wikibooks.org admin he seems to be the ideal mentor for your project, yes. But you don't need to wait for his answer to announce your project idea at Bugzilla and wikitech-l.
But before I would still try to polish your project summary a bit. Are you able to summarize in one sentence the solution your project aims to deliver? If you can, use it as opening of the summary. It's amazing how impatient readers are nowadays... :)
Alright, I will announce the project there and on wikitech-l after I put a little more work into the proposal! Thanks for the feedback.
12:25, 26 March 2018 (UTC)
11:29, 5 March 2018 (UTC)
00:56, 25 January 2018 (UTC)