Hi,
I'm interested in working on the 'WikiMedia Identities Editor' project for
Google Summer of Code 2014.
The basic idea of the project is to have a platform where the contributors
of MediaWiki can maintain an online identity.
The current procedures are not so easy to follow and also not very
systematic.
We need a good web-application that allows community members to create and
maintain their online identities. Furthermore, a search feature, to find
community members and their contributions(optional), would be useful.
Here is my full proposal:
https://www.mediawiki.org/wiki/User:Vinay_raghavan/GSOC2014_proposal
My user page:
https://www.mediawiki.org/wiki/User:Vinay_raghavan
I would really appreciate any sort of feedback on my proposal.
Thanks,
Vinay Raghavan
vinayraghavan(a)outlook.com
Hello,
Please ignore my earlier mail, i have done some editing in my draft and
mailing it again.
I am Rahul Mishra,final year undergraduate and pursuing
my B-Tech form Netaji Subhash Engineering College having
majors Computer Sciences & Engineering.
I am very much interested in the project of "A system for reviewing funding
requests" and proposed a draft titled "A system for reviewing funding
requests".
Please review my draft and please give your valuable advise/suggestions,
so that
i can further improve my proposal and make it better.
Link to my Userpage.
https://www.mediawiki.org/wiki/User:Rahulmishra22
Link to the project.
https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014#A_system_for_revi…
Link to the Proposal.
https://www.mediawiki.org/wiki/Rahulmishra22/A_System_for_reviewing_Funding…
Thank you,
Rahul Mishra.
Dept. of CSE,
NSEC.
This may be controversial but hopefully there is logic in what I'm about to see.
I just took a look at Cologne Blue and there are a huge host of CSS
issues. It makes me wonder if anyone is actually maintaining it. All
the other skins seems to render nicely. Coordinates overlap the header
and the Echo button is overlapping other text. It just looks shoddy
[1].
Firstly is anyone actively maintaining it for Wikimedia sites?
Secondly, how widely used is it on our production Wikimedia wikis?
I suspect it would be a good idea to at the very least move it into
its own extension and possibly disable it on some Wikimedia sites or
all Wikimedia sites.
>From my personal opinion, the less skins we have to maintain on
Wikimedia sites on the better, and if no one actively cares or uses a
skin then it is silly to invest time in doing so...
[1] http://imgur.com/hNZAFUb,bRHdhCS
Hi,
I've publish a proposal[1] about Wikimedia Identities Editor. The mentors
will be Alvaro del Castillo, Daniel Izquierdo. Mediawiki Community Metrics
is a Wikimedia project which goal is to describe how the MediaWiki /
Wikimedia tech community is doing.
But it is lack of the management tools to allow the community member to
manage their profile and update their info on the Web interface. We should
also provide OAuth login as an option and provide locale settings.
Please help me review the proposal. Feedback is welcome.
[1]:https://www.mediawiki.org/wiki/User:Fantasticfears/GSoC_2014
--
Regards,
Erick Guan/管啸 (fantasticfears)
Hi everyone,
I am interested in a GSoC 2014 project with the Wikimedia Foudation
The project aims at solving a few critical bugs in the Mediawiki Translate
extension and making it much more efficient and better.
These are the bugs included in the project. Please tell if you have any
suggestions :)
1-Having the page title optionally selected for translation. In a few
cases, the title mightn't be relevant and it shouldn't be translated.
2-This is a bug with core. Requirement to set the content language while
creating a page.
3-The translated page isn't updated when a translation unit page is moved
or deleted.
4-Redesign of interface of the extension on pages and the language bar.
5-Changes in Special:AggregateGroups-Currently, it is not possible to
change an aggregate group description or group name on
Special:AggregateGroups. Also, the page should have a read-only output for
users with insufficient permissions.
Please check-out the detailed explanation of these bugs and aimed
implementation.
I would really appreciate some feedback.
https://www.mediawiki.org/wiki/User:Kunalgrover05/GSoc_Proposal
Thank You.
Kunal Grover
II Year B.Tech
Department of Mechanical Engineering
IIT Madras, Chennai, India.
Hi everyone,
I am interested in a GSoC 2014 project with the Wikimedia Foudation
The project aims at solving a few critical bugs in the Mediawiki Translate
extension and making it much more efficient and better.
These are the bugs included in the project. Please tell if you have any
suggestions :)
1-Having the page title optionally selected for translation. In a few
cases, the title mightn't be relevant and it shouldn't be translated.
2-This is a bug with core. Requirement to set the content language while
creating a page.
3-The translated page isn't updated when a translation unit page is moved
or deleted.
4-Redesign of interface of the extension on pages and the language bar.
5-Changes in Special:AggregateGroups-Currently, it is not possible to
change an aggregate group description or group name on
Special:AggregateGroups. Also, the page should have a read-only output for
users with insufficient permissions.
Please check-out the detailed explanation of these bugs and aimed
implementation.
I would really appreciate some feedback.
https://www.mediawiki.org/wiki/User:Kunalgrover05/GSoc_Proposal
Thank You.
Kunal Grover
II Year B.Tech
Department of Mechanical Engineering
IIT Madras, Chennai, India.
Hi,
As the deadline is comming, I come to publicize myself again :)
I have just updated the core part of my proposal [1]. Hope to see any
advice or comments. Thanks a lot!
[1]
https://www.mediawiki.org/wiki/User:Xiaoxiangquan/UniversalLanguageSelector…
*---------------------About Chinese Font Tailor--------------------*
In the ULS webfonts's repository( ULS:/data/fontrepo/fonts ), Autonym
contains all the characters needed for the ULS UI. It only needs tens of
Chinese characters, so only keep them, and kick the other tens of thousands
out. That's how Chinese Font Tailor will work! But it's for general
purpose, not only for UI.
*I think there are two approaches.*
- Aggressive update: Whenever a page is updated, scan it to see what
characters are used and then generate the font for it.
Advantage: quick response for visiting
Disadvantage: it seems to affect the external logic
- Lazy update: Whenever a page is visited and ULS is called, scan it to see
what characters are used and then generate the font for it. Cache the font
with a timestamp, then we can use it directly in future when finding it
up-to-date after comparing the font's and the page's timestamp.
Advantage: better cohesion
Disadvantage: may cause notable delay for the first visiting
I myself suggest the latter one, as wiki pages tend to Write Once and Read
Many.
*Implementation*
- A script that run on server will tailor the font file for a specified
page called ABC. The font file will be named ABC_FONT-NAME_TIMESTAMP.ttf.
- Modify the webfonts js (ULS:/resources/js/) to pack some parameters
needed, such as the page name
- A php script serve the right font for the webfonts' call.
----------------------------------------------------
Best regards,
A new wiki page is born:
https://www.mediawiki.org/wiki/Upstream_projects
Please help listing the right projects, adding their contacts and links.
The idea is to get a clear picture of the upstream projects we rely on, and
also of the people in our community that know best about them.
The page has three sections that correspond to different types of upstream:
* projects we develop that we want others to use and contribute to (e.g.
MediaWiki)
* projects others develop and we embed in our architecture (e.g.
Elasticsearch)
* projects others develop and we embed in our processes (e.g. Jenkins)
These projects define our location in the free software map. The health of
our projects depends on their own health, and also on the health of our
common links.
Currently we rely in the knowledge and contacts of official and unofficial
maintainers of these tools, who are frequently members of these upstream
communities by their own initiative. If you are one of them, you probably
see the usefulness of documenting these links.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil