[Wikitech-l] Seeking Guidance for Open Source Contribution

[Makwana Nikunj]

Dear Learning Equality Team,

My name is Nikunj Makwana, and I am currently a third-year computer science
undergraduate at Government Engineering College, Dahod. I have some
experience in programming languages like html, css , js, react, java. My
primary skills lie in js, I am passionate about open-source and have
recently participated in Hacktoberfest 2023. I am now seeking mentorship to
improve my skills in open-source development. I am keen to contribute to
your projects and would appreciate your guidance on how to get started.
Your mentorship would be valuable to me, and I look forward to hearing from
you soon.
Thank you for your time.
Best regards,
Nikunj Makwana
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Seeking Guidance for Open Source Contribution

[Vasanth Gopa]

Hi Makwana,

Appreciate your enthusiasm & interest, please see the following resources
for getting started :)

- https://www.mediawiki.org/wiki/New_Developers
- https://developer.wikimedia.org/

Regards,
Vasanth Gopa

On Wed, Oct 25, 2023 at 4:34 PM Makwana Nikunj  wrote:

> Dear Learning Equality Team,
>
> My name is Nikunj Makwana, and I am currently a third-year computer
> science undergraduate at Government Engineering College, Dahod. I have some
> experience in programming languages like html, css , js, react, java. My
> primary skills lie in js, I am passionate about open-source and have
> recently participated in Hacktoberfest 2023. I am now seeking mentorship to
> improve my skills in open-source development. I am keen to contribute to
> your projects and would appreciate your guidance on how to get started.
> Your mentorship would be valuable to me, and I look forward to hearing from
> you soon.
> Thank you for your time.
> Best regards,
> Nikunj Makwana
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/



-- 
Regards,

Gopa Vasanth 
Twitter  | LinkedIn
 | GitHub
 | Gerrit


“Yesterday is not ours to recover, but tomorrow is ours to win or lose.”
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Announcing Codex 1.0

[Roan Kattouw]

Today the Design Systems Team
 is announcing the
release of Codex 1.0!
What is Codex?

Codex  is the new design system
for Wikimedia. Over the past 2 years, the Design Systems Team and
contributors from the Wikimedia Foundation, Wikimedia Deutschland, and the
volunteer communities have collaborated to create a centralized design
system to serve Wikimedia projects. Codex provides more equitable
experiences for all Wikimedia movement participants, and makes it easier
and faster to design and build consistent user interfaces. With Codex, we
aim to enable more people to contribute to the mission.

Codex provides a library of design tokens
, user
interface components
, and
catalog of icons
 to use with
these components. Through the Codex Figma libraries, designers can reuse
these shared components

, tokens
,
and assets

in
their designs. For developers, Codex provides components built with Vue.js,
as well as some CSS-only components that do not require JavaScript to use.

Codex is already being used for Wikifunctions
, Vector 2022
,
the Growth Mentor Dashboard
 and Impact Module
, the New
Pages Feed

, MediaSearch ,
NearbyPages ,
QuickSurveys , and
ReadingLists .
Projects currently under development using Codex include Accessibility for
reading
 and
the Incident Reporting System
.

Codex provides a set of core components

that
cover a wide range of Wikimedia user interface needs, but does not
necessarily provide equivalents of all components in OOUI
. If you find that a component you
were expecting to use is missing, please talk to the Design Systems Team
 and
we'd be happy to help you. We strongly encourage contribution to Codex
, in
line with our vision of being a collaborative project guided by stewardship.
Why 1.0 now?

The Design Systems Team has been working towards this milestone for a
number of months now. Based on early feedback, we’ve already made
improvements to the developer experience of using Codex, like providing
ready-to-go example repos
 of using
Codex in a MediaWiki extension and changing our code snippets in the doc
site for easier copy-paste into non-TypeScript and MediaWiki-specific
projects.

We also dedicated significant time and effort ensuring accessibility of
Codex components and assets conform to WCAG 2.1 AA and other standards, and
plan to engage with groups like the American Foundation for the Blind for
further improvements.

We’ve been consolidating various design resources (like the design style
guide ) into Codex so there is a
single source of truth for Wikimedia front-end development and design
standards. This is to clarify Codex’s role not just as a UI library, but as
the design system for Wikimedia.
Who should use Codex?

Everyone! Some foundational elements like design tokens can and should be
used in all Wikimedia software going forward. Most of the MediaWiki code
that uses the older pre-token variables from mediawiki.ui has already been
migrated to use the Codex tokens instead. The Codex wiki documentation
 has more
information about using design tokens (and other elements) in MediaWiki.

At this time, Codex components are most suitable for client-side features
that don't have complex requirements for non-JavaScript support, or for
server-rendered interfaces that don't need much interactivity. Features
requiring both 

[Wikitech-l] Re: Announcing Codex 1.0

[Derk-Jan Hartman]

Congratulations team (and the predecessor teams) !

We started talking about needing a new way forward all the way back in
2017, with an RFC started in 2019, we choose Vue in 2020 and the teams have
been building new foundations since, so far culminating in Codex !!

I'm sure there is much work left to do as the web and MediaWiki is ever
evolving. Just recently the web finally added CSS nesting

for instance, and new features like :has()
 and :user-valid()
 selectors.
Unfortunately Wikipedia/MediaWiki and specifically user scripts can have
problems trying to keep up with so many changes. It is great to see that es6
, less
, import,
require  and
recently even source maps  are
slowly finding their way into our ecosystem, all while supporting as many
older browsers as possible and building one of the fastest websites in the
world.

These improvements are only possible because dedicated people work hard to
analyze the problems and these changes, devise solutions to slowly
introduce them without breaking everything, align peers, fight to get time
to work on it. All to shepherd them into existence, laborious and
challenging as it may be at times.

Keep up the great work, but lets take a moment and celebrate the official
birth of an entire new design system !

DJ



On Wed, Oct 25, 2023 at 6:07 PM Roan Kattouw  wrote:

> Today the Design Systems Team
>  is announcing the
> release of Codex 1.0!
> What is Codex?
>
> Codex  is the new design system
> for Wikimedia. Over the past 2 years, the Design Systems Team and
> contributors from the Wikimedia Foundation, Wikimedia Deutschland, and the
> volunteer communities have collaborated to create a centralized design
> system to serve Wikimedia projects. Codex provides more equitable
> experiences for all Wikimedia movement participants, and makes it easier
> and faster to design and build consistent user interfaces. With Codex, we
> aim to enable more people to contribute to the mission.
>
> Codex provides a library of design tokens
> ,
> user interface components
> , and
> catalog of icons
>  to use with
> these components. Through the Codex Figma libraries, designers can reuse
> these shared components
> 
> , tokens
> ,
> and assets
> 
>  in
> their designs. For developers, Codex provides components built with Vue.js,
> as well as some CSS-only components that do not require JavaScript to use.
>
> Codex is already being used for Wikifunctions
> , Vector 2022
> ,
> the Growth Mentor Dashboard
>  and Impact Module
> , the New
> Pages Feed
> 
> , MediaSearch ,
> NearbyPages ,
> QuickSurveys , and
> ReadingLists .
> Projects currently under development using Codex include Accessibility
> for reading
>  and
> the Incident Reporting System
> .
>
> Codex provides a set of core components
>  
> that
> cover a wide range of Wikimedia user interface needs, but does not
> necessarily provide equivalents of all components in OOUI
> . If you find that a component you
> were expecting to use is missing, please talk to the Design Systems Team
>  and
> we'd be happy to help you. We strongly encourage contribution to Codex
> 

[Wikitech-l] [request for feedback] Community configuration 2.0: Letting admins to change MediaWiki configuration, on-wiki: validation

[Martin Urbanec]

Hello everyone,

I'm Martin Urbanec from the Wikimedia Foundation's Growth team
. During the 2023-24 fiscal year,
we're working on Community configuration 2.0
, an extension
that empowers administrators to modify a subset of MediaWiki configuration
on-wiki, so that they can customize features to their needs. The Growth
team implemented this for its own features and since it was a great help in
scaling, we decided to generalize what we created and offer it to all
Wikimedia developers.

The Growth team spent a couple of months on planning Community
configuration 2.0 as well as discussing the project with its potential
users. You can read more information in the project page at MediaWiki.org
 and the Product
Requirements Document

.

The first aspect the Growth team is looking to define is configuration
validation, so that a malformed configuration file doesn’t cause the
MediaWiki instance to fail. We wrote our proposal regarding validation as a
Phabricator task at https://phabricator.wikimedia.org/T349757.

With this email, we would like to ask for your feedback, which you can
submit via Phabricator: https://phabricator.wikimedia.org/T349757. If you
feel so, we also invite you to read the Product Requirements Document and
submit any feedback as comments within that document. We would appreciate
it if you can submit any feedback before the end of *November 08, 2023*. In
case you have other questions about Community configuration, feel free to
ask them at the MediaWiki.org project talk page
.

Looking forward to reading your feedback!

For the Growth team,

*Martin Urbanec* (he/him)
Senior Software Engineer (Growth)
Wikimedia Foundation 
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Announcing Codex 1.0

[Amir Sarabadani]

I want to echo what the DJ has said. I managed to write a pretty decent
gadget in just a couple of hours thanks to Codex, something that used to
take days at least. This is really exciting to see. Thank you to all who
have worked on this tirelessly for years. Kudos and congratulations.

Am Mi., 25. Okt. 2023 um 20:28 Uhr schrieb Derk-Jan Hartman <
d.j.hartman+wmf...@gmail.com>:

> Congratulations team (and the predecessor teams) !
>
> We started talking about needing a new way forward all the way back in
> 2017, with an RFC started in 2019, we choose Vue in 2020 and the teams have
> been building new foundations since, so far culminating in Codex !!
>
> I'm sure there is much work left to do as the web and MediaWiki is ever
> evolving. Just recently the web finally added CSS nesting
> 
> for instance, and new features like :has()
>  and :user-valid()
>  selectors.
> Unfortunately Wikipedia/MediaWiki and specifically user scripts can have
> problems trying to keep up with so many changes. It is great to see that
> es6 , less
> , import,
> require  and
> recently even source maps  are
> slowly finding their way into our ecosystem, all while supporting as many
> older browsers as possible and building one of the fastest websites in the
> world.
>
> These improvements are only possible because dedicated people work hard to
> analyze the problems and these changes, devise solutions to slowly
> introduce them without breaking everything, align peers, fight to get time
> to work on it. All to shepherd them into existence, laborious and
> challenging as it may be at times.
>
> Keep up the great work, but lets take a moment and celebrate the official
> birth of an entire new design system !
>
> DJ
>
>
>
> On Wed, Oct 25, 2023 at 6:07 PM Roan Kattouw 
> wrote:
>
>> Today the Design Systems Team
>>  is announcing the
>> release of Codex 1.0!
>> What is Codex?
>>
>> Codex  is the new design system
>> for Wikimedia. Over the past 2 years, the Design Systems Team and
>> contributors from the Wikimedia Foundation, Wikimedia Deutschland, and the
>> volunteer communities have collaborated to create a centralized design
>> system to serve Wikimedia projects. Codex provides more equitable
>> experiences for all Wikimedia movement participants, and makes it easier
>> and faster to design and build consistent user interfaces. With Codex, we
>> aim to enable more people to contribute to the mission.
>>
>> Codex provides a library of design tokens
>> ,
>> user interface components
>> , and
>> catalog of icons
>>  to use with
>> these components. Through the Codex Figma libraries, designers can reuse
>> these shared components
>> 
>> , tokens
>> ,
>> and assets
>> 
>>  in
>> their designs. For developers, Codex provides components built with Vue.js,
>> as well as some CSS-only components that do not require JavaScript to use.
>>
>> Codex is already being used for Wikifunctions
>> , Vector 2022
>> ,
>> the Growth Mentor Dashboard
>>  and Impact
>> Module ,
>> the New Pages Feed
>> 
>> , MediaSearch ,
>> NearbyPages ,
>> QuickSurveys ,
>> and ReadingLists .
>> Projects currently under development using Codex include Accessibility
>> for reading
>>  and
>> the Incident Reporting System
>> .
>>
>> Codex provides a set of core components
>> 

[Wikitech-l] Re: Announcing Codex 1.0

[Dan Andreescu]

I am so happy.  Thank you.

On Wed, Oct 25, 2023 at 17:02 Amir Sarabadani  wrote:

> I want to echo what the DJ has said. I managed to write a pretty decent
> gadget in just a couple of hours thanks to Codex, something that used to
> take days at least. This is really exciting to see. Thank you to all who
> have worked on this tirelessly for years. Kudos and congratulations.
>
> Am Mi., 25. Okt. 2023 um 20:28 Uhr schrieb Derk-Jan Hartman <
> d.j.hartman+wmf...@gmail.com>:
>
>> Congratulations team (and the predecessor teams) !
>>
>> We started talking about needing a new way forward all the way back in
>> 2017, with an RFC started in 2019, we choose Vue in 2020 and the teams have
>> been building new foundations since, so far culminating in Codex !!
>>
>> I'm sure there is much work left to do as the web and MediaWiki is ever
>> evolving. Just recently the web finally added CSS nesting
>> 
>> for instance, and new features like :has()
>>  and :user-valid()
>> 
>> selectors. Unfortunately Wikipedia/MediaWiki and specifically user scripts
>> can have problems trying to keep up with so many changes. It is great to
>> see that es6 , less
>> , import,
>> require 
>> and recently even source maps 
>> are slowly finding their way into our ecosystem, all while supporting as
>> many older browsers as possible and building one of the fastest websites in
>> the world.
>>
>> These improvements are only possible because dedicated people work hard
>> to analyze the problems and these changes, devise solutions to slowly
>> introduce them without breaking everything, align peers, fight to get time
>> to work on it. All to shepherd them into existence, laborious and
>> challenging as it may be at times.
>>
>> Keep up the great work, but lets take a moment and celebrate the official
>> birth of an entire new design system !
>>
>> DJ
>>
>>
>>
>> On Wed, Oct 25, 2023 at 6:07 PM Roan Kattouw 
>> wrote:
>>
>>> Today the Design Systems Team
>>>  is announcing the
>>> release of Codex 1.0!
>>> What is Codex?
>>>
>>> Codex  is the new design
>>> system for Wikimedia. Over the past 2 years, the Design Systems Team and
>>> contributors from the Wikimedia Foundation, Wikimedia Deutschland, and the
>>> volunteer communities have collaborated to create a centralized design
>>> system to serve Wikimedia projects. Codex provides more equitable
>>> experiences for all Wikimedia movement participants, and makes it easier
>>> and faster to design and build consistent user interfaces. With Codex, we
>>> aim to enable more people to contribute to the mission.
>>>
>>> Codex provides a library of design tokens
>>> ,
>>> user interface components
>>> , and
>>> catalog of icons
>>>  to use
>>> with these components. Through the Codex Figma libraries, designers can
>>> reuse these shared components
>>> 
>>> , tokens
>>> ,
>>> and assets
>>> 
>>>  in
>>> their designs. For developers, Codex provides components built with Vue.js,
>>> as well as some CSS-only components that do not require JavaScript to use.
>>>
>>> Codex is already being used for Wikifunctions
>>> , Vector 2022
>>> ,
>>> the Growth Mentor Dashboard
>>>  and Impact
>>> Module ,
>>> the New Pages Feed
>>> 
>>> , MediaSearch ,
>>> NearbyPages ,
>>> QuickSurveys ,
>>> and ReadingLists .
>>> Projects currently under development using Codex include Accessibility
>>> for reading
>>>  and
>>> the Incide

[Wikitech-l] Re: Announcing Codex 1.0

[p858snake]

If someone wants to propose a post about this for the mediawiki mastodon
account via mastocollab would be great :)


https://www.mediawiki.org/wiki/Project:Mastodon
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/