Add Hungarian site language

[dlakatos847]

Description

Open edX Hungarian translation is at 100% yet the language could not be selected in the Account MFE. Fixes #1391.

How Has This Been Tested?

• Tutor main + Open edX master
• launch dev edX
• MFE + Indigo plugins install and enable
• frontend-app-account mount + MFE rebuilt
• pull frontend-app-account translations with atlas
• create superuser + login
• set Hungarian language via http://apps.local.openedx.io:1997/account/#site-preferences
• verify database content

mysql> use openedx;
Database changed
mysql> select `key`,`value` from user_api_userpreference;
+-----------+-------+
| key       | value |
+-----------+-------+
| pref-lang | hu    |
+-----------+-------+
1 row in set (0.00 sec)

Screenshots/sandbox:

Include a link to the sandbox for design changes or screenshot for before and after. Remove this section if it's not applicable.

Before	After

[openedx-webhooks]

Thanks for the pull request, @dlakatos847!

This repository is currently maintained by @jacobo-dominguez-wgu.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[mphilbrick211]

Hi @dlakatos847 and thank you for this contribution! Please let me know if you have any questions regarding submitting a CLA form. Thank you!

[dlakatos847]

Hi @dlakatos847 and thank you for this contribution! Please let me know if you have any questions regarding submitting a CLA form. Thank you!

Hi @mphilbrick211,
Thank you for your welcome. I received the Docusign link in email, we are running the document through our legal processes right now.
There were some conflicting information in some Open edX contributor wiki pages. I'm working for the company @sysagnostic, but as I understood, contributions via a company CLAs are only accepted if the company commits resources (engineer man-hours) to the @openedx project. We are unable to commit resources right now, maybe in the future. Our contribution schedule is expected to be random for now.
Should I still sign the individual CLA I have in my inbox or should I contact Axim's legal department via email instead?

[mphilbrick211]

Hi @dlakatos847 and thank you for this contribution! Please let me know if you have any questions regarding submitting a CLA form. Thank you!

Hi @mphilbrick211, Thank you for your welcome. I received the Docusign link in email, we are running the document through our legal processes right now. There were some conflicting information in some Open edX contributor wiki pages. I'm working for the company @sysagnostic, but as I understood, contributions via a company CLAs are only accepted if the company commits resources (engineer man-hours) to the @openedx project. We are unable to commit resources right now, maybe in the future. Our contribution schedule is expected to be random for now. Should I still sign the individual CLA I have in my inbox or should I contact Axim's legal department via email instead?

@dlakatos847 - I've reached out to our legal side as well to see if I can get you some guidance. Stay tuned!

[mphilbrick211]

@dlakatos847 per our legal team, first we need to confirm the following:

• If you are contributing your own contributions (not your company's) to the Open edX community, then you should complete the Individual CLA.
• If you would be contributing on behalf of your company, then we can look at the appropriate agreement for your company.

Regarding the question on committing resources, that doesn't apply here. I think you may be referring to our "core contributor" program, which is separate from being a general contributor. Core contributors are individuals who commit a certain number of hours per month to maintaining / improving the platform... whereas an entity / master service agreement with your company would simply allow you to contribute on behalf of the company as needed. You can also add additional coworkers to the entity agreement as needed by reaching out to our support team. There are no minimum time requirements with the entity agreement.

Please let me know if this helps clear things up, and which type of agreement you'd like to proceed with. Thanks!

[dlakatos847]

@mphilbrick211 Thank you very much for the clarification. As my colleague @rblst and I are intending to contribute to the @openedx project on behalf of our company @sysagnostic, signing an entity CLA seems to be the appropriate choice. I recommend to continue the discussion about the signing process and details of the agreement in a private channel of your choice:

• mailto:ceo@sysagnostic.com
• direct Slack messaging

Looking forward hearing from you.