-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Team page #235
Conversation
Should we replace mentions of the jQuery Foundation? Technically, they weren't members of the OpenJS Foundation, but they were possibly included in the move to the JS Foundation. But, to remove ambiguity, it could say "previously jQuery Foundation" or something to that effect. |
Done. |
<li> | ||
<img src="https://secure.gravatar.com/avatar/6e836e35b57421faa0067702089ed46e?size=120" alt=""> | ||
<h2>Rafael Xavier</h2> | ||
<h3>Globalize Lead</h3> | ||
</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still consider Globalize as part of the jQuery portfolio? I know there were plans to rebuild some jQuery UI widgets on top of globalize but I'm not sure if anything really happened here (@fnagel?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a preference either way.
I figured for jQuery Core/UI/Mobile/Infra it's easiest to keep a single team page here. Globalize does use jQuery Infra for its domain redirect, and its branding/logo follow the jQuery style. QUnit likewise, but QUnit has its own website and team.
For Globalize we don't have a website, and it's not deprecated or archived (essentially a direct project under OpenJS). We could also list Rafael as former jQuery Team member, "Globalize Lead" but it's slightly confusing in that state since it is a current project and current role. I left Rafael as current team member since that's how it is today and seems the least change in one go 🙂. I'll follow what you and Timmy prefer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Globalize may not be deprecated or archived, but it's had very little activity since 2018. Perhaps it should be deprecated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the former jQuery UI team planned to integrate it into the reworked calendar / datepicker widgets. Sadly those have never been released but Globalize was utilized for localization of the calendar widget. See here for more info:
https://jqueryui.pbworks.com/w/page/12137778/Datepicker
https://github.com/jquery/jquery-ui/tree/datepicker
Afaik Globalize is no longer active. It died more or less when Scott, Jörn and all the others left the team.
When looking at the commits, its only kept alive but not actively developed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I asked on the OpenJSF Slack how do we want to approach Globalize.
@rxaviers any input from you would be very helpful here as well!
Are we also going to redirect https://jquery.org/team/ to this new page? |
dadccc0
to
c6371d6
Compare
@mgol Yeah, that's the proposal. Would you be in favour of that? |
Yes! |
Ref jquery/jquery.org#139