Joomla! Documentation - User contributions [en]

Pizza Bugs and Fun 2024/Contributors List August-Event

2024-08-24T10:47:28Z

Flyingwombats: /* UK */

<noinclude><languages /></noinclude>

[[File:PBF24.2_large.jpg|center]]

Back to [[https://www.pizza-bugs-fun.com/<translate> en</translate> / Pizza, Bugs & Fun]]

<translate>
''Edit the page and add your name to have your contribution to PBF2024.2 recorded.''

== These awesome Joomlers contributed to Pizza, Bugs & Fun 2024 August Event ==

====Austria====
* Harald Leithner

====France====
* Emmanuel Lemor

====Germany====
* Benjamin Trenkle

====Greece====

====Italy====

====Kenya====
* James Gichuru

====Netherlands====
* Anja de Crom
* Peter Martin
* Tom van der Laan

====Spain====

====Switzerland====

====Uganda====

====UK====
* Phil Walton

====USA====
* Olivier Buisard

====Vietnam====

</translate>

[[Category:Volunteer Engagement{{#translation:}}]]
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]

Joomla:Code of Conduct (COC)

2023-11-01T15:45:33Z

Flyingwombats: Edit the code of conduct url

<noinclude><languages /></noinclude>

<translate>
This document outlines the Code of Conduct for all persons volunteering their service to the Joomla Project and/or Open Source Matters. It covers your behaviour as a member of the Joomla community, in any forum, mailing list, Wiki, Web site, IRC channel, install-fest, public meeting or private correspondence. If you cannot agree to any of these principles, then volunteering in the Joomla Project is not for you. Contributing to our community assumes acceptance of these principles:</translate>

<translate>
== Be Considerate == 
</translate>
<translate>
You are working with others as a team so be considerate of how your actions or contribution affects your colleagues and the community as a whole.</translate>

<translate>
== Be Respectful == 
</translate>
<translate>
Treat one another and members of the community with respect. Everyone can make a valuable contribution to Joomla. We may not always agree, but disagreement is no excuse for poor behavior or poor manners.</translate>
<translate>

We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect the members of Joomla community to be respectful when dealing with other volunteers as well as with people from outside projects and initiatives and with users.</translate>
<translate>

Avoid becoming involved in flame wars, trolling, personal attacks, and repetitive arguments. Take the matters "outside" (off-list, etc) if it helps resolve the situation, and do not use communal methods of communication to be a vehicle for your private "wall of shame."</translate>

<translate>
== Be Collaborative == 
</translate>

<translate>
Joomla is free software and about collaboration and working together. Collaboration reduces redundancy of work done in the free software world, and improves the quality of the software produced regardless of whether you are writing code or performing some other task.
</translate>

<translate>
When you disagree, consult others. Disagreements, both political and technical, happen all the time, and Joomla is no exception. Disagreement, debate and constructive criticism is often how progress is made and are a necessary part of doing complex work in a team. The important goal is not to avoid disagreements or differing views but to resolve them constructively. Above all, avoid making conflicts about the work into personal conflicts. Debate should never include reference to someone's nationality, gender, religion or other personal characteristics. You should turn to the community and to the community process to seek advice and to resolve disagreements. Team leaders and Department Coordinators are able to help you figure out which direction will be most acceptable.
</translate>

<translate>
When you are unsure, ask for help. Nobody knows everything and nobody is expected to be perfect. Asking questions avoids many problems down the road and so questions are encouraged. Those who are asked should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Off-topic questions, such as requests for help on a development mailing list, detract from productive discussion.
</translate>

<translate>
== Step Down Considerately == 
</translate>
<translate>
People on every project come and go, and Joomla is no different. When you leave or disengage from the community, in whole or in part, we ask that you do so in a way that minimizes disruption to the Project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you leave off.</translate>

<translate>
== Be Available == 
</translate>
<translate>
Check your e-mails regularly and answer them promptly—even if it's "I'll get back to you."</translate>

<translate>
== Be Honest == 
</translate>
<translate>
Sometimes the hardest thing to say is "no" or admit you've forgotten do something. Be honest with each other and yourself with regards to what you say and what you can realistically commit to.</translate>

<translate>
== Follow the Rules == 
</translate>
<translate>
Volunteers are expected to uphold Joomla's licensing and trademark requirements including, but not limited to, compliance on their own or affiliate Web sites and extensions. Make sure you have sought the appropriate approvals for domain name, name and logo usage prior to volunteering and that any extensions you distribute comply with the Joomla license.</translate>

<translate>
All work contributed to the Project, whether code, documentation or other material, must observe the appropriate licenses as set down by the Core Team and Open Source Matters.</translate>

<translate>
Some contributors represent the Joomla Project in specific areas, but you should not speak on behalf of the Project or present yourself as an official representative of the Project unless you are specifically authorized to do so, and you should never state your opinions as the official policies of the Project.</translate>

<translate>
== Exercise Discretion and Confidentiality at Appropriate Times == </translate>
<translate>

Depending on your role, you will be privy to various levels of information. As a volunteer you are expected to keep site access details (such as logins, FTP details, etc.) secure at all times.</translate>
<translate>

Information contained within private forums (for example, about serious security matters, legal cases, or personal details), private mailing lists, chats or other mediums is also to be kept confidential even after you have discontinued your service. Breaches in the area of privacy and confidentiality are taken very seriously by the Project.</translate>

<translate>
== Conflict of Interest == 
</translate>
<translate>

When using Project resources or making decisions within the board, your department, team, or subteam or the concerning Project's policy positions, you must do so based only on the best interests of the Project and its user community. If you have a situation or affiliation that might constitute or lead to a conflict of interest or might be perceived by a reasonable person in the community to be a conflict of interest, disclose this to your Team Leaders or the team as a whole. If appropriate, after discussing with your team, you should remove yourself from specific decisions or discussions in which you may have a conflict of interest.</translate>

<translate>
== Conflict Resolution Team == </translate>
<translate>

Should you wish to make a CoC violation report or are facing a conflict that has failed to be resolved in the manner set out in this CoC, please [https://docs.google.com/forms/d/e/1FAIpQLSea_VL9NUvUM3iX-gptNuJe5oz5-jp9y5Y4v9ZyKImblfYTcQ/viewform click here] to access the report form.</translate>

<translate>
== The Fine Print == 
</translate>
<translate>
Members of the board of Open Source Matters are governed by additional guidelines and requirements and, where a conflict exists, these take precedence over this Code of Conduct.<tvar|ref3><ref>https://www.opensourcematters.org/organisation/by-laws-policies.html</ref></>
</translate>

<translate>
== The Last Bit == 
</translate>
<translate>
This Code of Conduct has changed over time and will continue to develop, but was originally derived, with permission, from the Ubuntu CoC.</translate>

<translate>
These principals can also be found on the main joomla.org website under, [<tvar|url>https://www.opensourcematters.org/organisation/by-laws-policies.html</> Volunteer Code of Conduct].</translate>

<translate>
== References == 
</translate>
<references/>

<translate>

[[Category:Governance]]
[[Category:Project Policy]]
</translate>

Joomla:Code of Conduct (COC)

2023-11-01T15:42:02Z

Flyingwombats: Corrected the code of conduct url

<noinclude><languages /></noinclude>

<translate>
This document outlines the Code of Conduct for all persons volunteering their service to the Joomla Project and/or Open Source Matters. It covers your behaviour as a member of the Joomla community, in any forum, mailing list, Wiki, Web site, IRC channel, install-fest, public meeting or private correspondence. If you cannot agree to any of these principles, then volunteering in the Joomla Project is not for you. Contributing to our community assumes acceptance of these principles:</translate>

<translate>
== Be Considerate == 
</translate>
<translate>
You are working with others as a team so be considerate of how your actions or contribution affects your colleagues and the community as a whole.</translate>

<translate>
== Be Respectful == 
</translate>
<translate>
Treat one another and members of the community with respect. Everyone can make a valuable contribution to Joomla. We may not always agree, but disagreement is no excuse for poor behavior or poor manners.</translate>
<translate>

We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect the members of Joomla community to be respectful when dealing with other volunteers as well as with people from outside projects and initiatives and with users.</translate>
<translate>

Avoid becoming involved in flame wars, trolling, personal attacks, and repetitive arguments. Take the matters "outside" (off-list, etc) if it helps resolve the situation, and do not use communal methods of communication to be a vehicle for your private "wall of shame."</translate>

<translate>
== Be Collaborative == 
</translate>

<translate>
Joomla is free software and about collaboration and working together. Collaboration reduces redundancy of work done in the free software world, and improves the quality of the software produced regardless of whether you are writing code or performing some other task.
</translate>

<translate>
When you disagree, consult others. Disagreements, both political and technical, happen all the time, and Joomla is no exception. Disagreement, debate and constructive criticism is often how progress is made and are a necessary part of doing complex work in a team. The important goal is not to avoid disagreements or differing views but to resolve them constructively. Above all, avoid making conflicts about the work into personal conflicts. Debate should never include reference to someone's nationality, gender, religion or other personal characteristics. You should turn to the community and to the community process to seek advice and to resolve disagreements. Team leaders and Department Coordinators are able to help you figure out which direction will be most acceptable.
</translate>

<translate>
When you are unsure, ask for help. Nobody knows everything and nobody is expected to be perfect. Asking questions avoids many problems down the road and so questions are encouraged. Those who are asked should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Off-topic questions, such as requests for help on a development mailing list, detract from productive discussion.
</translate>

<translate>
== Step Down Considerately == 
</translate>
<translate>
People on every project come and go, and Joomla is no different. When you leave or disengage from the community, in whole or in part, we ask that you do so in a way that minimizes disruption to the Project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you leave off.</translate>

<translate>
== Be Available == 
</translate>
<translate>
Check your e-mails regularly and answer them promptly—even if it's "I'll get back to you."</translate>

<translate>
== Be Honest == 
</translate>
<translate>
Sometimes the hardest thing to say is "no" or admit you've forgotten do something. Be honest with each other and yourself with regards to what you say and what you can realistically commit to.</translate>

<translate>
== Follow the Rules == 
</translate>
<translate>
Volunteers are expected to uphold Joomla's licensing and trademark requirements including, but not limited to, compliance on their own or affiliate Web sites and extensions. Make sure you have sought the appropriate approvals for domain name, name and logo usage prior to volunteering and that any extensions you distribute comply with the Joomla license.</translate>

<translate>
All work contributed to the Project, whether code, documentation or other material, must observe the appropriate licenses as set down by the Core Team and Open Source Matters.</translate>

<translate>
Some contributors represent the Joomla Project in specific areas, but you should not speak on behalf of the Project or present yourself as an official representative of the Project unless you are specifically authorized to do so, and you should never state your opinions as the official policies of the Project.</translate>

<translate>
== Exercise Discretion and Confidentiality at Appropriate Times == </translate>
<translate>

Depending on your role, you will be privy to various levels of information. As a volunteer you are expected to keep site access details (such as logins, FTP details, etc.) secure at all times.</translate>
<translate>

Information contained within private forums (for example, about serious security matters, legal cases, or personal details), private mailing lists, chats or other mediums is also to be kept confidential even after you have discontinued your service. Breaches in the area of privacy and confidentiality are taken very seriously by the Project.</translate>

<translate>
== Conflict of Interest == 
</translate>
<translate>

When using Project resources or making decisions within the board, your department, team, or subteam or the concerning Project's policy positions, you must do so based only on the best interests of the Project and its user community. If you have a situation or affiliation that might constitute or lead to a conflict of interest or might be perceived by a reasonable person in the community to be a conflict of interest, disclose this to your Team Leaders or the team as a whole. If appropriate, after discussing with your team, you should remove yourself from specific decisions or discussions in which you may have a conflict of interest.</translate>

<translate>
== Conflict Resolution Team == </translate>
<translate>

Should you wish to make a CoC violation report or are facing a conflict that has failed to be resolved in the manner set out in this CoC, please [https://docs.google.com/forms/d/e/1FAIpQLSea_VL9NUvUM3iX-gptNuJe5oz5-jp9y5Y4v9ZyKImblfYTcQ/viewform click here] to access the report form.</translate>

<translate>
== The Fine Print == 
</translate>
<translate>
Members of the board of Open Source Matters are governed by additional guidelines and requirements and, where a conflict exists, these take precedence over this Code of Conduct.<tvar|ref3><ref>http://opensourcematters.org/about/organization/by-laws-policies.html</ref></>
</translate>

<translate>
== The Last Bit == 
</translate>
<translate>
This Code of Conduct has changed over time and will continue to develop, but was originally derived, with permission, from the Ubuntu CoC.</translate>

<translate>
These principals can also be found on the main joomla.org website under, [<tvar|url>https://www.opensourcematters.org/organisation/by-laws-policies.html</> Volunteer Code of Conduct].</translate>

<translate>
== References == 
</translate>
<references/>

<translate>

[[Category:Governance]]
[[Category:Project Policy]]
</translate>

Joomla! Awards

2022-05-16T13:40:46Z

Flyingwombats: /* {{bullet}}2022: Spring 2022 Best-Of Awards, Highly Recommended, Overall Hackathon Winner, Social Media Engagement */

<noinclude><languages /></noinclude>

<translate>
The Joomla! CMS has received many awards since it was created back in 2005. On this page, you can find an incomplete list of them.</translate>

== {{bullet}}2022: Spring 2022 Best-Of Awards, Highly Recommended, Overall Hackathon Winner, Social Media Engagement ==
'''Expert Insights''' - [https://expertinsights.com/insights/the-top-content-management-systems/ Spring 2022 Best-Of Awards]

'''FOSS Awards''' - [https://www.20i.com/foss-awards/winners Highly Recommended]

'''Cloudfest Hackathon''' - [https://blog.cloudfest.com/cloudfest-hackathon-2022-greatest-hackathon-ever/ Overall Hackathon Winner]

'''Cloudfest Hackathon''' - [https://blog.cloudfest.com/cloudfest-hackathon-2022-greatest-hackathon-ever/ Social Media Engagement]

== {{bullet}}2021: Best Open Source CMS, Best Free CMS, Best Open Source CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/oscar-who-were-celebrating-the-winners-of-the-2021-cms-critic-peoples-choice-awards/ Best Open Source CMS]

'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/oscar-who-were-celebrating-the-winners-of-the-2021-cms-critic-peoples-choice-awards/ Best Free CMS]

'''CMS Critic Critics Award''' - [https://www.cmscritic.com/introducing-the-winners-of-the-2021-cms-critics-choice-awards/ Best Open Source CMS]

== {{bullet}}2020: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2019: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2018: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2017: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2016: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2015: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [http://www.cmscritic.com/announcing-the-2015-winner-for-best-free-cms Best Free CMS]

== {{bullet}}2014: Best Open Source PHP CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/2014-best-open-source-php-cms/ Best Open Source PHP CMS]

== {{bullet}}2012: Best Open Source Application ==
'''Infoworld Bossie Awards''' - [https://www.infoworld.com/article/2606733/bossie-awards-2012--the-best-open-source-applications.html#slide5 Best Open Source Application]

== {{bullet}}2011: Best Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5394-joomla-wins-the-packt-open-source-cms-award.html Best Open Source CMS]

== {{bullet}}2010: 2nd Runner-up Hall of Fame CMS ==
'''Packt Open Source Awards''' - 2nd Runner-up Hall of Fame CMS

== {{bullet}}2009: Most Valued Person, Packt Hall of Fame CMS, 2nd Runner-up Best Open Source CMS ==
'''Packt Open Source Awards''' - [https://en.wikipedia.org/wiki/Joomla Open Source CMS Most Valued Person - Personal award Louis Landry]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 1st Runner-up Packt Hall of Fame CMS]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 2nd Runner-up Best Open Source CMS]

== {{bullet}}2008: Most Valued Person, Best Open Source CMS, Best Overall Open Source CMS ==
'''Packt Open Source Awards''' - [https://www.joomlatools.com/blog/2008/10/johan-janssens-nominated-for-most/ Open Source CMS Most Valued Person - Personal award Johan Janssens]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Open Source CMS]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Overall Open Source CMS]

== {{bullet}}2007: Best PHP Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html Best PHP Open Source CMS]

== {{bullet}}2006: Best Open Source CMS, Best Linux / Open Source Project==
'''Packt Open Source Awards''' [http://en.wikipedia.org/wiki/Packt#Open_Source_Awards] - [http://www.joomla.org/announcements/team-news/2275-joomla-2006-open-source-content-management-system-award-winner.html Best Open Source CMS]

'''UK Linux & Open Source Awards''' [https://forum.joomla.org/viewtopic.php?f=8&t=108064 Best Linux / Open Source Project] - [https://www.joomla.org/announcements/general-news/2165-joomla-wins-again-at-uk-linuxworld.html Joomla! Wins Again at UK LinuxWorld]

== {{bullet}}2005: Best Linux / Open Source Project ==
'''Linux & Open Source Awards in London''' [https://forum.joomla.org/viewtopic.php?f=8&t=10744 Best Linux / Open Source Project]

<noinclude>
[[Category:Joomla! Community{{#translation:}}]]
</noinclude>

Joomla! Awards

2022-05-15T16:09:40Z

Flyingwombats:

<noinclude><languages /></noinclude>

<translate>
The Joomla! CMS has received many awards since it was created back in 2005. On this page, you can find an incomplete list of them.</translate>

== {{bullet}}2022: Spring 2022 Best-Of Awards, Highly Recommended, Overall Hackathon Winner, Social Media Engagement ==
'''Expert Insights''' - [https://expertinsights.com/insights/the-top-content-management-systems/ Spring 2022 Best-Of Awards]

'''FOSS Awards''' - [https://www.20i.com/foss-awards/winners/ Highly Recommended]

'''Cloudfest Hackathon''' - [https://blog.cloudfest.com/cloudfest-hackathon-2022-greatest-hackathon-ever/ Overall Hackathon Winner]

'''Cloudfest Hackathon''' - [https://blog.cloudfest.com/cloudfest-hackathon-2022-greatest-hackathon-ever/ Social Media Engagement]

== {{bullet}}2021: Best Open Source CMS, Best Free CMS, Best Open Source CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/oscar-who-were-celebrating-the-winners-of-the-2021-cms-critic-peoples-choice-awards/ Best Open Source CMS]

'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/oscar-who-were-celebrating-the-winners-of-the-2021-cms-critic-peoples-choice-awards/ Best Free CMS]

'''CMS Critic Critics Award''' - [https://www.cmscritic.com/introducing-the-winners-of-the-2021-cms-critics-choice-awards/ Best Open Source CMS]

== {{bullet}}2020: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2019: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2018: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2017: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2016: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2015: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [http://www.cmscritic.com/announcing-the-2015-winner-for-best-free-cms Best Free CMS]

== {{bullet}}2014: Best Open Source PHP CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/2014-best-open-source-php-cms/ Best Open Source PHP CMS]

== {{bullet}}2012: Best Open Source Application ==
'''Infoworld Bossie Awards''' - [https://www.infoworld.com/article/2606733/bossie-awards-2012--the-best-open-source-applications.html#slide5 Best Open Source Application]

== {{bullet}}2011: Best Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5394-joomla-wins-the-packt-open-source-cms-award.html Best Open Source CMS]

== {{bullet}}2010: 2nd Runner-up Hall of Fame CMS ==
'''Packt Open Source Awards''' - 2nd Runner-up Hall of Fame CMS

== {{bullet}}2009: Most Valued Person, Packt Hall of Fame CMS, 2nd Runner-up Best Open Source CMS ==
'''Packt Open Source Awards''' - [https://en.wikipedia.org/wiki/Joomla Open Source CMS Most Valued Person - Personal award Louis Landry]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 1st Runner-up Packt Hall of Fame CMS]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 2nd Runner-up Best Open Source CMS]

== {{bullet}}2008: Most Valued Person, Best Open Source CMS, Best Overall Open Source CMS ==
'''Packt Open Source Awards''' - [https://www.joomlatools.com/blog/2008/10/johan-janssens-nominated-for-most/ Open Source CMS Most Valued Person - Personal award Johan Janssens]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Open Source CMS]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Overall Open Source CMS]

== {{bullet}}2007: Best PHP Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html Best PHP Open Source CMS]

== {{bullet}}2006: Best Open Source CMS, Best Linux / Open Source Project==
'''Packt Open Source Awards''' [http://en.wikipedia.org/wiki/Packt#Open_Source_Awards] - [http://www.joomla.org/announcements/team-news/2275-joomla-2006-open-source-content-management-system-award-winner.html Best Open Source CMS]

'''UK Linux & Open Source Awards''' [https://forum.joomla.org/viewtopic.php?f=8&t=108064 Best Linux / Open Source Project] - [https://www.joomla.org/announcements/general-news/2165-joomla-wins-again-at-uk-linuxworld.html Joomla! Wins Again at UK LinuxWorld]

== {{bullet}}2005: Best Linux / Open Source Project ==
'''Linux & Open Source Awards in London''' [https://forum.joomla.org/viewtopic.php?f=8&t=10744 Best Linux / Open Source Project]

<noinclude>
[[Category:Joomla! Community{{#translation:}}]]
</noinclude>

Joomla! Awards

2022-04-03T09:27:09Z

Flyingwombats: added the cms critics awards

<noinclude><languages /></noinclude>

<translate>
The Joomla! CMS has received many awards since it was created back in 2005. On this page, you can find an incomplete list of them.</translate>

== {{bullet}}2021: Best Open Source CMS, Best Free CMS, Best Open Source CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/oscar-who-were-celebrating-the-winners-of-the-2021-cms-critic-peoples-choice-awards/ Best Open Source CMS]

'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/oscar-who-were-celebrating-the-winners-of-the-2021-cms-critic-peoples-choice-awards/ Best Free CMS]

'''CMS Critic Critics Award''' - [https://www.cmscritic.com/introducing-the-winners-of-the-2021-cms-critics-choice-awards/ Best Open Source CMS]

== {{bullet}}2020: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2019: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2018: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2017: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2016: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/cms-critic-awards Best Free CMS]

== {{bullet}}2015: Best Free CMS ==
'''CMS Critic People's Choice Awards''' - [http://www.cmscritic.com/announcing-the-2015-winner-for-best-free-cms Best Free CMS]

== {{bullet}}2014: Best Open Source PHP CMS ==
'''CMS Critic People's Choice Awards''' - [https://www.cmscritic.com/2014-best-open-source-php-cms/ Best Open Source PHP CMS]

== {{bullet}}2012: Best Open Source Application ==
'''Infoworld Bossie Awards''' - [https://www.infoworld.com/article/2606733/bossie-awards-2012--the-best-open-source-applications.html#slide5 Best Open Source Application]

== {{bullet}}2011: Best Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5394-joomla-wins-the-packt-open-source-cms-award.html Best Open Source CMS]

== {{bullet}}2010: 2nd Runner-up Hall of Fame CMS ==
'''Packt Open Source Awards''' - 2nd Runner-up Hall of Fame CMS

== {{bullet}}2009: Most Valued Person, Packt Hall of Fame CMS, 2nd Runner-up Best Open Source CMS ==
'''Packt Open Source Awards''' - [https://en.wikipedia.org/wiki/Joomla Open Source CMS Most Valued Person - Personal award Louis Landry]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 1st Runner-up Packt Hall of Fame CMS]

'''Packt Open Source Awards''' - [http://www.oscms-summit.org/cms/joomla/ 2nd Runner-up Best Open Source CMS]

== {{bullet}}2008: Most Valued Person, Best Open Source CMS, Best Overall Open Source CMS ==
'''Packt Open Source Awards''' - [https://www.joomlatools.com/blog/2008/10/johan-janssens-nominated-for-most/ Open Source CMS Most Valued Person - Personal award Johan Janssens]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Open Source CMS]

'''Packt Open Source Awards''' - [https://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html 1st Runner-up Best Overall Open Source CMS]

== {{bullet}}2007: Best PHP Open Source CMS ==
'''Packt Open Source Awards''' - [http://www.joomla.org/announcements/general-news/5218-packt-award-roundup-joomla-takes-runner-up.html Best PHP Open Source CMS]

== {{bullet}}2006: Best Open Source CMS, Best Linux / Open Source Project==
'''Packt Open Source Awards''' [http://en.wikipedia.org/wiki/Packt#Open_Source_Awards] - [http://www.joomla.org/announcements/team-news/2275-joomla-2006-open-source-content-management-system-award-winner.html Best Open Source CMS]

'''UK Linux & Open Source Awards''' [https://forum.joomla.org/viewtopic.php?f=8&t=108064 Best Linux / Open Source Project] - [https://www.joomla.org/announcements/general-news/2165-joomla-wins-again-at-uk-linuxworld.html Joomla! Wins Again at UK LinuxWorld]

== {{bullet}}2005: Best Linux / Open Source Project ==
'''Linux & Open Source Awards in London''' [https://forum.joomla.org/viewtopic.php?f=8&t=10744 Best Linux / Open Source Project]

<noinclude>
[[Category:Joomla! Community{{#translation:}}]]
</noinclude>

J4.x:Fix "Database Table Structure NOT Up to Date" before Update

2022-02-25T01:03:25Z

Flyingwombats:

==Errors reported==

When updating Joomla! the database table structure has to be up to date before the process can start.

The "Pre-Update Check for Joomla" complains if this is not the case.

[[File:J4-database-table-structure-up-to-date-no.jpg|Joomla! 4 - Pre-Update Check - database table structure not up to date]]

But when you go to 'System - Maintenance - Database' there is no entry available.

==Versions affected== 
{{tip|This was reported in any Joomla! 4.x versions.|title=General Information}} 

==What is the cause== 
This is caused by an empty #__schemas table in the database. Most likely this occurs when the Joomla! instance is not installed by the official Joomla! installer but e.g. though an customized script which did not fill in all required data.

==How to fix== 
You can fix this by adding the missing value to the table. First, you need the ID from Joomla!. Go to the #__extensions table via e.g. phpMyAdmin (or another database client). Search for name="files_joomla" and write down the ID (in our case 211).

Second, you need to know the latest SQL script which is installed. Go to "administrator/components/com_admin/sql/updates/mysql" and get the file name with the highest version. In this example, assume "4.0.3-2021-09-05.sql" is the filename with the highest version. Now you have to add this in your insert query as the second value:

<source lang="sql">
INSERT INTO `#__schemas` (`extension_id`, `version_id`) VALUES
(211, '4.0.3-2021-09-05');
</source>

or for PostgreSQL:
<source lang="sql">
INSERT INTO "#__schemas" ("extension_id", "version_id") VALUES
(211, '4.0.3-2021-09-05');
</source>

Replace "#__" by your database prefix (see Global Configuration) before running the statements.

Then go to "System - Maintenance - Database" and fix the tables.

Now the update should work as expected.

__NOTOC__

<noinclude>
[[Category:Version 4.1.0 FAQ{{#translation:}}]]
</noinclude>

Htaccess changes after joomla4.0.4

2021-10-27T19:13:50Z

Flyingwombats: /* Due to a file name change. */

==Due to a file name change.==
This change had to be made. It affects a small number of people. We wanted to get the information out before the problem could arise to help those in the small group who might be affected.
[[File:139115817-f4042c30-a773-41e3-a335-9998f9050a8e.png|htaccess change infographic]]

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.
Thanks to Brian Teeman for the infographic to help us understand it better.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a [[Htaccess_examples_(security)|htaccess script]].

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-27T19:10:20Z

Flyingwombats:

==Due to a file name change.==
This change had to be made. It affects a small group of people but we wanted to get the information out before the problem could arise to help those in the small group who might be affected.
[[File:139115817-f4042c30-a773-41e3-a335-9998f9050a8e.png|htaccess change infographic]]

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.
Thanks to Brian Teeman for the infographic to help us understand it better.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a [[Htaccess_examples_(security)|htaccess script]].

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-27T19:08:21Z

Flyingwombats:

==Due to a file name change which we needed to make there is a check you need to make in some circumstances.==
[[File:139115817-f4042c30-a773-41e3-a335-9998f9050a8e.png|htaccess change infographic]]

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.
Thanks to Brian Teeman for the infographic to help us understand it better.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a [[Htaccess_examples_(security)|htaccess script]].

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-27T19:06:46Z

Flyingwombats:

[[File:139115817-f4042c30-a773-41e3-a335-9998f9050a8e.png|htaccess change infographic]]

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.
Thanks to Brian Teeman for the infographic to help us understand it better.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a [[Htaccess_examples_(security)|htaccess script]].

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

File:139115817-f4042c30-a773-41e3-a335-9998f9050a8e.png

2021-10-27T19:04:50Z

Flyingwombats:

htaccess change infographic by Brian Teeman

Htaccess changes after joomla4.0.4

2021-10-19T17:53:48Z

Flyingwombats: /* Does it affect you? */

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a [[Htaccess_examples_(security)|htaccess script]].

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T17:51:06Z

Flyingwombats: /* Does it affect you? */

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a htaccess script.

[[https://docs.joomla.org/Htaccess_examples_(security)|Htaccess_examples_(security)]]

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T17:50:04Z

Flyingwombats: /* Does it affect you? */

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
Here is an example of such a htaccess script.

[[https://docs.joomla.org/Htaccess_examples_(security)]]

If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T17:48:17Z

Flyingwombats: /* What to change */

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-
==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3

RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later

RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T17:47:41Z

Flyingwombats: /* What to change */

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-
==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]
</pre>
And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3
<pre>
RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]
</pre>
## Joomla! Update (core feature) — Joomla versions 4.0.4 and later
<pre>
RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T16:18:56Z

Flyingwombats:

==Thanks to:==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-
==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3
RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later
RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T16:18:15Z

Flyingwombats:

==Thanks to==
Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.
==Does it affect you?==
If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-
==What to change==
<pre>
RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3
RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later
RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]
</pre>
If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Htaccess changes after joomla4.0.4

2021-10-19T16:12:58Z

Flyingwombats: Created page with "Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and..."

Thanks to Nicholas K. Dionysopoulos and all the people who worked on modernising the update process in Joomla!. Refactoring the code, removed over 50% make it more stable and logical which will result in making it more maintainable.

This is a great step forward in our approach to make Joomla! 4 slim and fast.

If you're using the hardened .htaccess version from the Joomla! documentation or those used in other htaccess examples, be aware, that you have to make a small change to not block your next update.
If you don't make these changes then you will find your updates after J4.0.4 blocked, so it is vital that you act and make this change.
If you have never used any of these more advanced htaccess files and only use the core file then this does not apply to you but it's worth looking through your htaccess file for the line with:-

RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]

And make the required changes if you do come across it in your files.

## Joomla! Update (core feature) — Joomla versions 2.5.1 through 4.0.3
RewriteRule ^administrator\/components\/com_joomlaupdate\/restore\.php$ - [L]

## Joomla! Update (core feature) — Joomla versions 4.0.4 and later
RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]

If you need more information https://github.com/joomla/joomla-cms/pull/35388

If you need further help then https://forum.joomla.org/ It Is an excellent place to find help and advice.

Help4Joomla

2021-10-17T11:42:18Z

Flyingwombats: Created page with "==What is Help4Joomla?== Help4Joomla is a list of people, and tasks they can do. If you add yourself to the list then others can contact you and ask for your help to accomplis..."

==What is Help4Joomla?==
Help4Joomla is a list of people, and tasks they can do. If you add yourself to the list then others can contact you and ask for your help to accomplish something needed.
Simply log in and add yourself, your native language and other languages you can communicate in and whether you are active at the moment.
Do not add other people. It's essential that this is a system driven by peoples desire to help out and they give their contact details.
{| class="wikitable sortable"
|-
! Name !! Task !! Native Language !! Other Languages !! Available to do the task !! Contact details
|-
| Phil Walton|| Proofreading and improving the readability of documents written by none English speakers || English || None || Available || https://volunteers.joomla.org/joomlers/1702-philip-walton
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|}

Time4Joomla

2021-09-22T08:37:26Z

Flyingwombats: /* Help Promote Joomla */

== What is Time4Joomla? ==
It is using those small chunks of time we all waste away on things that would help the Joomla project.

== How to give Time4Joomla ==
That's the great part with Time4Joomla, there are many ways you can help and you can dive in and find the task that fits your skill set and your time resources.

== Help Other Joomla Users ==
There's a number of Joomla community resources online that you can visit to share your expertise and experience with others. 

[http://Forum.joomla.org Forum.joomla.org]
[http://https://joomla.stackexchange.com/ Joomla Stack Exchange] 

There's active discussions across a number of social media platforms that you might be interested in participating in too. Participating in conversations can often help users

[https://www.facebook.com/groups/joomlanospam/ Joomla Facebook Group]
[https://www.linkedin.com/groups/52867/ Joomla Linkedin Group]
[https://www.reddit.com/r/joomla/ Joomla Reddit]

== Write Documentation for Joomla ==

[[Main Page|Docs.joomla.org]]
[[JDOC:How to Contribute to Joomla! Documentation|Get started contributing to Joomla Documentation.]]
== Translate Joomla ==
Check out this article from the [https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted Joomla Magazine] on how to get started.
== Test Joomla ==
The CMS release team has a sheet of tests that anyone who is familiar with Joomla can help complete. But your spare time may not fall within the release cycle window. If that's the case there is a project to automate some of these tests. If your journey to work results in a test written then that 15 minutes will save the project hours and days over the coming years!
== Help Promote Joomla ==
So under this heading would come voting in awards, finding awards to vote in and supporting Joomla in any comments section for an awards. A good example is the [https://www.cmscritic.com/cms-critic-awards/ CMS Critic Awards Nominations].

Keep an eye out for announcements in such online tools and find ways to participate, nominating Joomla, voting and promoting the joomla platform.

[https://www.trustradius.com/ TrustRadius] at the time of writing this article does not list Joomla in their top CMS.
https://www.trustradius.com/cms#toprated
In their criteria page they state the things that need to happen to make Joomla appear

* Recency: Product must have 10 or more recent reviews (from the past year)
* Rating: Product must have a trScore of 7.5 or higher
* Relevance: Product must earn at least 1.5% of the site traffic in the category
With a few more people spending some minutes filling in reports, Joomla can feature once again in such a forum.

=== Other ways to help ===

Find posts about joomla and add to them in the comments sections. Many articles are written by third parties and are often wrong in fact, based on very old versions or cast a poor light on Joomla. You can search out examples and then put your point of view. It's certainly more productive than reading the latest tips on removing red wine from the carpet and could just persuade someone to give Joomla another go.
Find a poll asking about cms and vote for Joomla

== Participate in Joomla Events ==
Around the world you'll find local [https://community.joomla.org/user-groups.html Joomla User Groups] and [https://community.joomla.org/events.html Joomla Events] running year-round. Post-pandemic, User Groups and Events should return to a more normal footing, but at the moment check the Joomla Events page for upcoming sessions, or follow various Joomla social media channels to see when events are announced.
== Get Involved with Joomla ==
That's far from the exhaustive list of ways to contribute to Joomla, but it's certainly a great list of ways to get started and giving some Time4Joomla.

If you do have more time available, and a skill set that you think can help the project, then there's a number of teams looking for members and contributors to help achieve their missions.

You can find more details about many of them in other [https://magazine.joomla.org/all-issues/tags/community-openings Community Openings articles] over recent months, or jump over to the [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla page]. The easiest way to tell us you're interested is to email contact-vet@community.joomla.org and tell us more about what your skills are and what you'd like to get involved with.

Time4Joomla

2021-09-22T08:26:28Z

Flyingwombats: /* What is Time4Joomla */

== What is Time4Joomla? ==
It is using those small chunks of time we all waste away on things that would help the Joomla project.

== How to give Time4Joomla ==
That's the great part with Time4Joomla, there are many ways you can help and you can dive in and find the task that fits your skill set and your time resources.

== Help Other Joomla Users ==
There's a number of Joomla community resources online that you can visit to share your expertise and experience with others. 

[http://Forum.joomla.org Forum.joomla.org]
[http://https://joomla.stackexchange.com/ Joomla Stack Exchange] 

There's active discussions across a number of social media platforms that you might be interested in participating in too. Participating in conversations can often help users

[https://www.facebook.com/groups/joomlanospam/ Joomla Facebook Group]
[https://www.linkedin.com/groups/52867/ Joomla Linkedin Group]
[https://www.reddit.com/r/joomla/ Joomla Reddit]

== Write Documentation for Joomla ==

[[Main Page|Docs.joomla.org]]
[[JDOC:How to Contribute to Joomla! Documentation|Get started contributing to Joomla Documentation.]]
== Translate Joomla ==
Check out this article from the [https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted Joomla Magazine] on how to get started.
== Test Joomla ==
The CMS release team has a sheet of tests that anyone who is familiar with Joomla can help complete. But your spare time may not fall within the release cycle window. If that's the case there is a project to automate some of these tests. If your journey to work results in a test written then that 15 minutes will save the project hours and days over the coming years!
== Help Promote Joomla ==
So under this heading would come voting in awards, finding awards to vote in and supporting Joomla in any comments section for an awards. A good example is the [https://www.cmscritic.com/cms-critic-awards/ CMS Critic Awards Nominations].

Keep an eye out for announcements in such online tools and find ways to participate, nominating Joomla, voting and promoting the joomla platform.

[https://www.trustradius.com/ TrustRadius] at the time of writing this article does not list Joomla. In their criteria page they state the things that need to happen to make Joomla appear

* Recency: Product must have 10 or more recent reviews (from the past year)
* Rating: Product must have a trScore of 7.5 or higher
* Relevance: Product must earn at least 1.5% of the site traffic in the category
With a few more people spending some minutes filling in reports, Joomla can feature once again in such a forum.

=== Other ways to help ===

Find posts about joomla and add to them in the comments sections. Many articles are written by third parties and are often wrong in fact, based on very old versions or cast a poor light on Joomla. You can search out examples and then put your point of view. It's certainly more productive than reading the latest tips on removing red wine from the carpet and could just persuade someone to give Joomla another go.
Find a poll asking about cms and vote for Joomla
== Participate in Joomla Events ==
Around the world you'll find local [https://community.joomla.org/user-groups.html Joomla User Groups] and [https://community.joomla.org/events.html Joomla Events] running year-round. Post-pandemic, User Groups and Events should return to a more normal footing, but at the moment check the Joomla Events page for upcoming sessions, or follow various Joomla social media channels to see when events are announced.
== Get Involved with Joomla ==
That's far from the exhaustive list of ways to contribute to Joomla, but it's certainly a great list of ways to get started and giving some Time4Joomla.

If you do have more time available, and a skill set that you think can help the project, then there's a number of teams looking for members and contributors to help achieve their missions.

You can find more details about many of them in other [https://magazine.joomla.org/all-issues/tags/community-openings Community Openings articles] over recent months, or jump over to the [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla page]. The easiest way to tell us you're interested is to email contact-vet@community.joomla.org and tell us more about what your skills are and what you'd like to get involved with.

Time4Joomla

2021-09-22T08:24:46Z

Flyingwombats:

== What is Time4Joomla ==
It is using those small chunks of time we all waste away on things that would help the Joomla project.
== How to give Time4Joomla ==
That's the great part with Time4Joomla, there are many ways you can help and you can dive in and find the task that fits your skill set and your time resources.

== Help Other Joomla Users ==
There's a number of Joomla community resources online that you can visit to share your expertise and experience with others. 

[http://Forum.joomla.org Forum.joomla.org]
[http://https://joomla.stackexchange.com/ Joomla Stack Exchange] 

There's active discussions across a number of social media platforms that you might be interested in participating in too. Participating in conversations can often help users

[https://www.facebook.com/groups/joomlanospam/ Joomla Facebook Group]
[https://www.linkedin.com/groups/52867/ Joomla Linkedin Group]
[https://www.reddit.com/r/joomla/ Joomla Reddit]

== Write Documentation for Joomla ==

[[Main Page|Docs.joomla.org]]
[[JDOC:How to Contribute to Joomla! Documentation|Get started contributing to Joomla Documentation.]]
== Translate Joomla ==
Check out this article from the [https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted Joomla Magazine] on how to get started.
== Test Joomla ==
The CMS release team has a sheet of tests that anyone who is familiar with Joomla can help complete. But your spare time may not fall within the release cycle window. If that's the case there is a project to automate some of these tests. If your journey to work results in a test written then that 15 minutes will save the project hours and days over the coming years!
== Help Promote Joomla ==
So under this heading would come voting in awards, finding awards to vote in and supporting Joomla in any comments section for an awards. A good example is the [https://www.cmscritic.com/cms-critic-awards/ CMS Critic Awards Nominations].

Keep an eye out for announcements in such online tools and find ways to participate, nominating Joomla, voting and promoting the joomla platform.

[https://www.trustradius.com/ TrustRadius] at the time of writing this article does not list Joomla. In their criteria page they state the things that need to happen to make Joomla appear

* Recency: Product must have 10 or more recent reviews (from the past year)
* Rating: Product must have a trScore of 7.5 or higher
* Relevance: Product must earn at least 1.5% of the site traffic in the category
With a few more people spending some minutes filling in reports, Joomla can feature once again in such a forum.

=== Other ways to help ===

Find posts about joomla and add to them in the comments sections. Many articles are written by third parties and are often wrong in fact, based on very old versions or cast a poor light on Joomla. You can search out examples and then put your point of view. It's certainly more productive than reading the latest tips on removing red wine from the carpet and could just persuade someone to give Joomla another go.
Find a poll asking about cms and vote for Joomla
== Participate in Joomla Events ==
Around the world you'll find local [https://community.joomla.org/user-groups.html Joomla User Groups] and [https://community.joomla.org/events.html Joomla Events] running year-round. Post-pandemic, User Groups and Events should return to a more normal footing, but at the moment check the Joomla Events page for upcoming sessions, or follow various Joomla social media channels to see when events are announced.
== Get Involved with Joomla ==
That's far from the exhaustive list of ways to contribute to Joomla, but it's certainly a great list of ways to get started and giving some Time4Joomla.

If you do have more time available, and a skill set that you think can help the project, then there's a number of teams looking for members and contributors to help achieve their missions.

You can find more details about many of them in other [https://magazine.joomla.org/all-issues/tags/community-openings Community Openings articles] over recent months, or jump over to the [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla page]. The easiest way to tell us you're interested is to email contact-vet@community.joomla.org and tell us more about what your skills are and what you'd like to get involved with.

Time4Joomla

2021-09-22T08:02:00Z

Flyingwombats: StaRTED PAGE

URLs in Joomla

2021-03-19T22:12:01Z

Flyingwombats: /* Other URI methods */

{{version/tutor|3.x}}

== Introduction ==
This is one of a series of [[API Guides]], which aim to help you understand how to use the Joomla APIs through providing detailed explanations and sample code which you can easily install and run.

This guide covers use of the <tt>JUri</tt> class (now known as <tt>Uri</tt>) and the use of the <tt>JRoute::_()</tt> method (now called <tt>Route</tt>). The Uri class enables you get the URL of the current webpage, and access parts of the URL. <tt>JRoute::_()</tt> is used to set up links to other webpage resources within your Joomla site.

== Getting the current URL ==
To get the URL of the current webpage do:
<source lang="php">
use Joomla\CMS\Uri\Uri;
$uri = Uri::getInstance();
$url = $uri->toString();
</source>
The advantage of using this method is that it handles any peculiarities of the webserver (eg Apache or IIS) and also performs some cleaning of the URL to avoid some types of injection attacks.

What gets returned from <tt>Uri::getInstance()</tt> isn't a PHP string of the URL, but rather a Joomla Uri object, which also holds internally the various parts of the URL, and provides getter and setter methods to read or write these URL parts as shown below.

http://fredbloggs:itsasecret@www.example.com:8080/path/to/Joomla/index.php?task=view&id=32#anchorthis
\__/ \________/ \________/ \_____________/ \__/\_______________________/ \_____________/ \________/
| | | | | | | |
scheme user pass host port path query fragment

The example column in the following table illustrates the result of each of the get methods on the URI above, all of which are strings.
{| class="wikitable"
|-
!Get method
!Set method
!Description
!Example
|-
|getFragment
|setFragment
|Fragment (everything after the '#'). This is often referred to as an anchor.
|anchorthis
|-
|getHost
|setHost
|Hostname or IP address. For example, 'www.joomla.org' or '192.168.2.45'.
|www.example.com
|-
|getPass
|setPass
|Password part of the authority. Don't use this!
|itsasecret
|-
|getPath
|setPath
|Path string. Note that the path always includes the leading "/" character.
|/path/to/Joomla/index.php
|-
|getPort
|setPort
|Port number. Specific schemes (protocols) have their own defaults (for example, 'http' is port 80, 'ftp' is port 21).
|8080
|-
|getQuery
|setQuery
|Query in string format. For example, "foo=bar&x=y".
|task=view&id=32
|-
|getScheme
|setScheme
|Scheme (protocol). For example, 'http', 'https', 'ftp'.
|http
|-
|getUser
|setUser
|Username part of the authority. Don't use this!
|fredbloggs
|-
|getVar
|setVar
|An individual query item value from within the query part. A query parameter may be removed using delVar.
|32
|}

(Note that passing the user/password in the URL in this fashion is generally deprecated and not recommended, and won't work on some browsers. In this guide below it's not considered.)

== root() and base() ==
<tt>base()</tt> and <tt>root()</tt> are static functions which return key URLs.

<tt>Uri::root($pathonly)</tt> is a static function which returns the URL to the root of the Joomla site. It may or may not be the same as the HTTP domain, depending upon how your webserver is configured. In the common case where a Joomla instance "mysite" is installed in a directory under the webserver document root you are likely to get:
* <tt>Uri::root()</tt> returns the string "http://www.mydomain.org/mysite/" (or https if you're using SSL, etc).
* <tt>Uri::root(true)</tt> returns the string "/mysite".

The second parameter to <tt>Uri::root()</tt>, namely <tt>$path</tt>, sets the path locally within the <tt>Uri</tt> class, and will get used in subsequent invocations of <tt>Uri::root()</tt>. '''Hence it's strongly advised that you don't set this parameter, as it could seriously muck up your website.'''

<tt>Uri::base()</tt> is similar to <tt>Uri::root()</tt> but what is returned depends on whether it's called from the site application or the administrator application.
* If you are on the site Uri::base() returns the same as Uri::root()
* If you are on the admin back-end Uri::base() returns Uri::root() plus "administrator", so using the example above:
** <tt>Uri::base()</tt> returns the string "http://www.mydomain.org/mysite/administrator/"
** <tt>Uri::base(true)</tt> returns the string "/mysite/administrator".

(This is similar to the [[Constants#Difference_between_JPATH_SITE.2C_JPATH_ROOT.2C_and_JPATH_BASE|Joomla Path constants]]).

== Other URI methods ==
As well as the methods above, the Joomla Uri provides the methods listed below. In the following example code snippets, <tt>$uri</tt> refers to a Uri instance, obtained for example through <tt>$uri = Uri::getInstance();</tt>.

* '''<tt>toString(array $parts = array('scheme', 'user', 'pass', 'host', 'port', 'path', 'query', 'fragment')) : string</tt>'''

<tt>toString()</tt> converts the Uri to a string, and allows you to select the parts of the URL which you want, eg

<tt>$uri->toString(array('scheme','host','port','path');</tt>

will return the URL minus any query or anchor (fragment).

* '''<tt>render()</tt>''' is similar to <tt>toString()</tt> in that it returns the parts of the URL you want, but as you have to pass the parts you want as a bitmask, it's preferable to use <tt>toString()</tt> instead.

* '''<tt>isSsl()<tt>''' returns true if the scheme is https, false otherwise, eg

<tt>$secure = $uri->isSsl();</tt>

* '''<tt>isInternal()</tt>''' returns true if the URL is within the Joomla instance (including the administrator area), false otherwise. Note that this is a static function, and you pass the URL as a string, eg

<tt>$internal = Uri::isInternal("myurl.org");</tt>

* '''<tt>current()</tt>''' returns the URL of the current page, minus any query string or fragment, eg
<tt>$currentURL = Uri::current();</tt>

and is basically equivalent to
<source lang="php">
$uri = Uri::getInstance();
$uri->toString(array('scheme','host','port','path'));
</source>

== External URLs ==
Usually if you're including an external URL in your website you will just specify it as a string, but there may be occasions where using the Uri class to manipulate parts of a URL could be useful. In this case you can do something like
<source lang="php">
$joomla = Uri::getInstance("//www.joomla.org");
$joomla->setScheme("https");
$joomla->setPath("/announcements");
$joomlaNews = $joomla->toString(); // https://www.joomla.org/announcements
echo "<a href='$joomlaNews'>Joomla news</a> ";
</source>
Joomla uses the PHP [https://www.php.net/manual/function.parse-url.php parse-url] method to parse the URL, so you need to be careful with including appropriate slashes in the URL and path.

== Internal Static URLs ==
To output a URL link to a file within the Joomla instance use:

<tt>$url = Uri::root() . 'path/from/joomla/root/to/file.typ';</tt>

For example, to make a URL which points to a file picture.jpg in the Joomla images folder use:

<tt>$url = Uri::root() . 'images/picture.jpg';</tt>

The advantage of this approach is that no changes need to be made if you change the name of your joomla site or domain, such as moving from a development environment, via testing to live, and particularly if you want to display absolute URLs on your live site.

== Internal Dynamic URLs ==
To create a URL which points to an item which is managed by a Joomla component com_example use an approach like what's below:
<source lang="php">
use Joomla\CMS\Router\Route;
$url = Route::_("index.php?option=com_example&view=showitem&id=14");
// or in the old naming convention:
$url = JRoute::_("index.php?option=com_example&view=showitem&id=14");
</source>
This is a bit trickier, as you have to know what parameters to set in the query part of the URL. However, if you set up (even temporarily) a menuitem which points to the appropriate view of the item type which you want to display then you should see in the Link field the parameters which you should add in the <tt>Route::_()</tt> call.

(Although this method's name is an underscore, there's nothing special about it – it's just an ordinary function).

=== Joomla Site Routing ===

The reason that using <tt>Route::_()</tt> is so important is that it will handle the conversion to SEF (Search Engine Friendly) URLs for the Joomla site.
[[File:router.jpg|center|800px]]
The piece of Joomla code which converts between the "internal URL format" (with query parameters defining the option, view, id, etc) and the SEF format (consisting of URL segments) is known as the Router, and this has 2 key methods.
# The <tt>build()</tt> method takes as input an array of the URL query variables, and based on these creates segments of the SEF URL. As the query variables are processed in sequence to produce the SEF URL segments they are removed from the input array. The <tt>Route::_()</tt> method gets an instance of the site Router class and calls <tt>build()</tt> to generate the SEF URL so that it can be displayed in an HTML link.
# The <tt>parse()</tt> method does the opposite. Whenever a user clicks on an SEF link Joomla will receive an HTTP GET request with a SEF URL. Joomla then obtains an instance of the site Router class and calls <tt>parse()</tt> passing an array of the URL segments. The Router code processes each of the segments in turn and generates the equivalent query variables, which are then set as PHP $_GET variables so that the Joomla code can call <tt>Factory::getApplication()->input->get('id')</tt> etc to access the variables as if they'd been query parameters with the HTTP GET request.

If you find that the URL returned from <tt>Route::_()</tt> still has query parameters then it may be that they are superfluous and you can omit them. However, there are circumstances where it may not be possible to remove all query parameters (specifically the Itemid parameter relating to the menuitem).

Even if you're not using SEF on your site, calling <tt>Route::_()</tt> will still cause some routing to be performed. For example, on a multilingual site you may find the <tt>lang</tt> parameter set on output, even though it wasn't set on your input parameter.

=== Route::_() Parameters ===
In addition to the input URL <tt>Route::_()</tt> takes the following parameters:
# <tt>$xhtml</tt> (default = true) – if true then the URL is passed through the PHP function <tt>htmlspecialchars()</tt> to convert special characters, such as "&" to "&amp;" and "<" to "&lt;" etc. Spaces in URLs always get converted to "%20", regardless of this parameter.

# <tt>$tls</tt> (default = self::TLS_IGNORE) – defines whether the output URL should be http or https or just the same as the current page. There are 3 possible values:
## Route::TLS_IGNORE (value 0) – if an absolute URL is requested, then the scheme (http or https) is set to the same as the current HTTP request
## Route::TLS_FORCE (value 1) – the scheme is set to https and an absolute URL is returned (regardless of the setting of the <tt>$absolute</tt> parameter).
## Route::TLS_DISABLE (value 2) – the scheme is set to http and an absolute URL is returned (regardless of the setting of the <tt>$absolute</tt> parameter).
# <tt>$absolute</tt> (default = false) – if true (or overridden by the <tt>$tls</tt> parameter) then an absolute URL is returned which includes the scheme, domain and port. If false then a root relative URL is output (where just the scheme, domain and port are missing).

=== Administrator Considerations ===
Since SEF URLs aren't implemented on the Administrator back-end there's less of a need to use <tt>Route::_()</tt>, but it's standard practice to do so.

Since Joomla 3.9 the <tt>Route::link()</tt> method has been available, which allows you to obtain an SEF URL to a site page when you're on the administrator application. You pass "site" as the <tt>$client</tt> parameter, and the other parameters are as for <tt>Route::_()</tt>, eg:
<source lang="php">
use Joomla\CMS\Router\Route;
$url = Route::link("site", "index.php?option=com_example&view=showitem&id=14);
</source>

=== Joomla Standard Query Parameters ===
The table below lists the more common query parameters which are used in constructing URLs with
<tt>Route::_()</tt>. It is not a comprehensive list.

{| class="wikitable"
|-
!Query Parameter
!Description
|-
|option
|The component (eg "com_contact") associated with the webpage you want to link to
|-
|view
|The view which the component displays on that page (eg "article" for com_content)
|-
|layout
|The layout php file (in tmpl directory under the view) to be used
|-
|id
|The id of the item to be shown
|-
|catid
|The id of the category associated with the item
|-
|Itemid
|The id of the menuitem which points to the webpage you want to link to
|-
|lang
|The language code
|-
|task
|In general the task parameter is of the form "firstpart.secondpart" and for a component called "com_example" Joomla will try to run an instance method called secondpart() of a controller class ExampleControllerFirstpart in a file firstpart.php in the com_example's controllers directory.
|-
|tmpl
|The template php file to use (instead of index.php). Commonly used with modals in the administrator back-end, by specifying tmpl=component to display the template component.php file in the modal iframe, which doesn't output the toolbar menu etc.
|-
|format
|The [[J4.x:Response_Formats|output format]] ('''''html''''', '''''json''''', '''''jsonapi''''', '''''feed''''', '''''xml''''', '''''raw''''', '''''image''''') expected. This controls which view file will be run or what kind of content the controller should send as response. The output format by default is '''''html'''''.
|}

== Sample Module Code ==
Below is the code for a simple Joomla module which you can install and run to demonstrate use of some of the functionality described above. If you are unsure about development and installing a Joomla module then following the tutorial at [[S:MyLanguage/J3.x:Creating a simple module/Introduction|Creating a simple module]] will help.

The code assumes that you have an article with id=1 in your Joomla instance, and an image in a file picture.jpg in the images folder; change the relevant lines of code appropriately if this is not the case.

The code can also easily be adapted to be an administrator module and include a call to the <tt>Route::link()</tt> function.

In a folder mod_uri_demo create the following 2 files:

<tt>mod_uri_demo.xml</tt>
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="3.1" client="site" method="upgrade">
<name>URI demo</name>
<version>1.0.1</version>
<description>Code demonstrating use of Joomla URI class</description>
<files>
<filename module="mod_uri_demo">mod_uri_demo.php</filename>
</files>
</extension>
</source>

<tt>mod_uri_demo.php</tt>
<source lang="php">
<?php
defined('_JEXEC') or die('Restricted Access');

use Joomla\CMS\Uri\Uri;
use Joomla\CMS\Router\Route;

// current URI
$uri = Uri::getInstance();
echo "Page URI is: " . $uri->toString() . " ";
echo "Scheme: " . $uri->getScheme() . ", Host: " . $uri->getHost() . " , Path: " . $uri->getPath() . " ";

// base() and root()
echo "URI base(): " . $uri->base() . ", pathonly: " . $uri->base(true) . " ";
echo "URI root(): " . $uri->root() . ", pathonly: " . $uri->root(true) . " ";

// External webpage
$joomla = Uri::getInstance("//www.joomla.org");
$joomla->setScheme("https");
$joomla->setPath("/announcements");
$joomlaNews = $joomla->toString();
echo "<a href='$joomlaNews'>Joomla news</a> ";

// static internal address - put picture.jpg in images folder
echo '<img src="' . Uri::root() . 'images/picture.jpg" alt="Link to images/picture.jpg"> ';

// link to article with id=1
$article1 = Route::_("index.php?option=com_content&view=article&id=1");
echo "URL for article 1: $article1 ";
echo "<a href='$article1'>First article</a> ";
</source>

Zip up the mod_uri_demo directory to create <tt>mod_uri_demo.zip</tt>.

Within your Joomla administrator go to Install Extensions and via the Upload Package File tab select this zip file to install this sample mod_uri_demo module.

Make this module visible by editing it (click on it within the Modules page) then:
# making its status Published
# selecting a position on the page for it to be shown
# on the menu assignment tab specify the pages it should appear on

When you visit a site web page then you should see the module in your selected position, and it should present a number of URLs and links demonstrating use of several of the Uri and Route class functions.

== Related Material ==
On the topic of SEF URLs see [[Search Engine Friendly URLs]] and [[J3.x:Supporting_SEF_URLs_in_your_component|Supporting SEF URLs in your component]].

A custom router is developed in steps [[J3.x:Developing_an_MVC_Component/Adding_an_alias|Adding an alias]], [[J3.x:Developing_an_MVC_Component/Using_the_language_filter_facility|Using the language filter facility]] and [[J3.x:Developing_an_MVC_Component/Adding_Associations|Adding Associations]] of the MVC Component Development tutorial.

[[Category:Development]]
[[Category:Tutorials]]
[[Category:Module Development]]
[[Category:Plugin Development]]
[[Category:Component Development]]

URLs in Joomla

2021-03-19T22:09:47Z

Flyingwombats: /* Other URI methods */

{{version/tutor|3.x}}

== Introduction ==
This is one of a series of [[API Guides]], which aim to help you understand how to use the Joomla APIs through providing detailed explanations and sample code which you can easily install and run.

This guide covers use of the <tt>JUri</tt> class (now known as <tt>Uri</tt>) and the use of the <tt>JRoute::_()</tt> method (now called <tt>Route</tt>). The Uri class enables you get the URL of the current webpage, and access parts of the URL. <tt>JRoute::_()</tt> is used to set up links to other webpage resources within your Joomla site.

== Getting the current URL ==
To get the URL of the current webpage do:
<source lang="php">
use Joomla\CMS\Uri\Uri;
$uri = Uri::getInstance();
$url = $uri->toString();
</source>
The advantage of using this method is that it handles any peculiarities of the webserver (eg Apache or IIS) and also performs some cleaning of the URL to avoid some types of injection attacks.

What gets returned from <tt>Uri::getInstance()</tt> isn't a PHP string of the URL, but rather a Joomla Uri object, which also holds internally the various parts of the URL, and provides getter and setter methods to read or write these URL parts as shown below.

http://fredbloggs:itsasecret@www.example.com:8080/path/to/Joomla/index.php?task=view&id=32#anchorthis
\__/ \________/ \________/ \_____________/ \__/\_______________________/ \_____________/ \________/
| | | | | | | |
scheme user pass host port path query fragment

The example column in the following table illustrates the result of each of the get methods on the URI above, all of which are strings.
{| class="wikitable"
|-
!Get method
!Set method
!Description
!Example
|-
|getFragment
|setFragment
|Fragment (everything after the '#'). This is often referred to as an anchor.
|anchorthis
|-
|getHost
|setHost
|Hostname or IP address. For example, 'www.joomla.org' or '192.168.2.45'.
|www.example.com
|-
|getPass
|setPass
|Password part of the authority. Don't use this!
|itsasecret
|-
|getPath
|setPath
|Path string. Note that the path always includes the leading "/" character.
|/path/to/Joomla/index.php
|-
|getPort
|setPort
|Port number. Specific schemes (protocols) have their own defaults (for example, 'http' is port 80, 'ftp' is port 21).
|8080
|-
|getQuery
|setQuery
|Query in string format. For example, "foo=bar&x=y".
|task=view&id=32
|-
|getScheme
|setScheme
|Scheme (protocol). For example, 'http', 'https', 'ftp'.
|http
|-
|getUser
|setUser
|Username part of the authority. Don't use this!
|fredbloggs
|-
|getVar
|setVar
|An individual query item value from within the query part. A query parameter may be removed using delVar.
|32
|}

(Note that passing the user/password in the URL in this fashion is generally deprecated and not recommended, and won't work on some browsers. In this guide below it's not considered.)

== root() and base() ==
<tt>base()</tt> and <tt>root()</tt> are static functions which return key URLs.

<tt>Uri::root($pathonly)</tt> is a static function which returns the URL to the root of the Joomla site. It may or may not be the same as the HTTP domain, depending upon how your webserver is configured. In the common case where a Joomla instance "mysite" is installed in a directory under the webserver document root you are likely to get:
* <tt>Uri::root()</tt> returns the string "http://www.mydomain.org/mysite/" (or https if you're using SSL, etc).
* <tt>Uri::root(true)</tt> returns the string "/mysite".

The second parameter to <tt>Uri::root()</tt>, namely <tt>$path</tt>, sets the path locally within the <tt>Uri</tt> class, and will get used in subsequent invocations of <tt>Uri::root()</tt>. '''Hence it's strongly advised that you don't set this parameter, as it could seriously muck up your website.'''

<tt>Uri::base()</tt> is similar to <tt>Uri::root()</tt> but what is returned depends on whether it's called from the site application or the administrator application.
* If you are on the site Uri::base() returns the same as Uri::root()
* If you are on the admin back-end Uri::base() returns Uri::root() plus "administrator", so using the example above:
** <tt>Uri::base()</tt> returns the string "http://www.mydomain.org/mysite/administrator/"
** <tt>Uri::base(true)</tt> returns the string "/mysite/administrator".

(This is similar to the [[Constants#Difference_between_JPATH_SITE.2C_JPATH_ROOT.2C_and_JPATH_BASE|Joomla Path constants]]).

== Other URI methods ==
As well as the methods above, the Joomla Uri provides the methods listed below. In the following example code snippets, <tt>$uri</tt> refers to a Uri instance, obtained for example through <tt>$uri = Uri::getInstance();</tt>.

* '''<tt>toString(array $parts = array('scheme', 'user', 'pass', 'host', 'port', 'path', 'query', 'fragment')) : string</tt>'''

<tt>toString()</tt> converts the Uri to a string, and allows you to select the parts of the URL which you want, eg

<tt>$uri->toString(array('scheme','host','port','path');</tt>

will return the URL minus any query or anchor (fragment).

* '''<tt>render()</tt>''' is similar to <tt>toString()</tt> in that it returns the parts of the URL you want, but as you have to pass the parts you want as a bitmask, it's preferable to use <tt>toString()</tt> instead.

* '''<tt>isSsl()<tt>''' returns true if the scheme is https, false otherwise, eg

<tt>$secure = $uri->isSsl();</tt>

* '''<tt>isInternal()</tt>''' returns true if the URL is within the Joomla instance (including the administrator area), false otherwise. Note that this is a static function, and you pass the URL as a string, eg

<tt>$internal = Uri::isInternal("myurl.org");</tt>

* '''<tt>current()</tt>''' returns the URL of the current page, minus any query string or fragment, eg
<tt>$currentURL = Uri::current();</tt>

and is basically equivalent to
<source lang="php">
<tt>$uri = Uri::getInstance();</tt>
<tt>$uri->toString(array('scheme','host','port','path'));</tt>
</source>

== External URLs ==
Usually if you're including an external URL in your website you will just specify it as a string, but there may be occasions where using the Uri class to manipulate parts of a URL could be useful. In this case you can do something like
<source lang="php">
$joomla = Uri::getInstance("//www.joomla.org");
$joomla->setScheme("https");
$joomla->setPath("/announcements");
$joomlaNews = $joomla->toString(); // https://www.joomla.org/announcements
echo "<a href='$joomlaNews'>Joomla news</a> ";
</source>
Joomla uses the PHP [https://www.php.net/manual/function.parse-url.php parse-url] method to parse the URL, so you need to be careful with including appropriate slashes in the URL and path.

== Internal Static URLs ==
To output a URL link to a file within the Joomla instance use:

<tt>$url = Uri::root() . 'path/from/joomla/root/to/file.typ';</tt>

For example, to make a URL which points to a file picture.jpg in the Joomla images folder use:

<tt>$url = Uri::root() . 'images/picture.jpg';</tt>

The advantage of this approach is that no changes need to be made if you change the name of your joomla site or domain, such as moving from a development environment, via testing to live, and particularly if you want to display absolute URLs on your live site.

== Internal Dynamic URLs ==
To create a URL which points to an item which is managed by a Joomla component com_example use an approach like what's below:
<source lang="php">
use Joomla\CMS\Router\Route;
$url = Route::_("index.php?option=com_example&view=showitem&id=14");
// or in the old naming convention:
$url = JRoute::_("index.php?option=com_example&view=showitem&id=14");
</source>
This is a bit trickier, as you have to know what parameters to set in the query part of the URL. However, if you set up (even temporarily) a menuitem which points to the appropriate view of the item type which you want to display then you should see in the Link field the parameters which you should add in the <tt>Route::_()</tt> call.

(Although this method's name is an underscore, there's nothing special about it – it's just an ordinary function).

=== Joomla Site Routing ===

The reason that using <tt>Route::_()</tt> is so important is that it will handle the conversion to SEF (Search Engine Friendly) URLs for the Joomla site.
[[File:router.jpg|center|800px]]
The piece of Joomla code which converts between the "internal URL format" (with query parameters defining the option, view, id, etc) and the SEF format (consisting of URL segments) is known as the Router, and this has 2 key methods.
# The <tt>build()</tt> method takes as input an array of the URL query variables, and based on these creates segments of the SEF URL. As the query variables are processed in sequence to produce the SEF URL segments they are removed from the input array. The <tt>Route::_()</tt> method gets an instance of the site Router class and calls <tt>build()</tt> to generate the SEF URL so that it can be displayed in an HTML link.
# The <tt>parse()</tt> method does the opposite. Whenever a user clicks on an SEF link Joomla will receive an HTTP GET request with a SEF URL. Joomla then obtains an instance of the site Router class and calls <tt>parse()</tt> passing an array of the URL segments. The Router code processes each of the segments in turn and generates the equivalent query variables, which are then set as PHP $_GET variables so that the Joomla code can call <tt>Factory::getApplication()->input->get('id')</tt> etc to access the variables as if they'd been query parameters with the HTTP GET request.

If you find that the URL returned from <tt>Route::_()</tt> still has query parameters then it may be that they are superfluous and you can omit them. However, there are circumstances where it may not be possible to remove all query parameters (specifically the Itemid parameter relating to the menuitem).

Even if you're not using SEF on your site, calling <tt>Route::_()</tt> will still cause some routing to be performed. For example, on a multilingual site you may find the <tt>lang</tt> parameter set on output, even though it wasn't set on your input parameter.

=== Route::_() Parameters ===
In addition to the input URL <tt>Route::_()</tt> takes the following parameters:
# <tt>$xhtml</tt> (default = true) – if true then the URL is passed through the PHP function <tt>htmlspecialchars()</tt> to convert special characters, such as "&" to "&amp;" and "<" to "&lt;" etc. Spaces in URLs always get converted to "%20", regardless of this parameter.

# <tt>$tls</tt> (default = self::TLS_IGNORE) – defines whether the output URL should be http or https or just the same as the current page. There are 3 possible values:
## Route::TLS_IGNORE (value 0) – if an absolute URL is requested, then the scheme (http or https) is set to the same as the current HTTP request
## Route::TLS_FORCE (value 1) – the scheme is set to https and an absolute URL is returned (regardless of the setting of the <tt>$absolute</tt> parameter).
## Route::TLS_DISABLE (value 2) – the scheme is set to http and an absolute URL is returned (regardless of the setting of the <tt>$absolute</tt> parameter).
# <tt>$absolute</tt> (default = false) – if true (or overridden by the <tt>$tls</tt> parameter) then an absolute URL is returned which includes the scheme, domain and port. If false then a root relative URL is output (where just the scheme, domain and port are missing).

=== Administrator Considerations ===
Since SEF URLs aren't implemented on the Administrator back-end there's less of a need to use <tt>Route::_()</tt>, but it's standard practice to do so.

Since Joomla 3.9 the <tt>Route::link()</tt> method has been available, which allows you to obtain an SEF URL to a site page when you're on the administrator application. You pass "site" as the <tt>$client</tt> parameter, and the other parameters are as for <tt>Route::_()</tt>, eg:
<source lang="php">
use Joomla\CMS\Router\Route;
$url = Route::link("site", "index.php?option=com_example&view=showitem&id=14);
</source>

=== Joomla Standard Query Parameters ===
The table below lists the more common query parameters which are used in constructing URLs with
<tt>Route::_()</tt>. It is not a comprehensive list.

{| class="wikitable"
|-
!Query Parameter
!Description
|-
|option
|The component (eg "com_contact") associated with the webpage you want to link to
|-
|view
|The view which the component displays on that page (eg "article" for com_content)
|-
|layout
|The layout php file (in tmpl directory under the view) to be used
|-
|id
|The id of the item to be shown
|-
|catid
|The id of the category associated with the item
|-
|Itemid
|The id of the menuitem which points to the webpage you want to link to
|-
|lang
|The language code
|-
|task
|In general the task parameter is of the form "firstpart.secondpart" and for a component called "com_example" Joomla will try to run an instance method called secondpart() of a controller class ExampleControllerFirstpart in a file firstpart.php in the com_example's controllers directory.
|-
|tmpl
|The template php file to use (instead of index.php). Commonly used with modals in the administrator back-end, by specifying tmpl=component to display the template component.php file in the modal iframe, which doesn't output the toolbar menu etc.
|-
|format
|The [[J4.x:Response_Formats|output format]] ('''''html''''', '''''json''''', '''''jsonapi''''', '''''feed''''', '''''xml''''', '''''raw''''', '''''image''''') expected. This controls which view file will be run or what kind of content the controller should send as response. The output format by default is '''''html'''''.
|}

== Sample Module Code ==
Below is the code for a simple Joomla module which you can install and run to demonstrate use of some of the functionality described above. If you are unsure about development and installing a Joomla module then following the tutorial at [[S:MyLanguage/J3.x:Creating a simple module/Introduction|Creating a simple module]] will help.

The code assumes that you have an article with id=1 in your Joomla instance, and an image in a file picture.jpg in the images folder; change the relevant lines of code appropriately if this is not the case.

The code can also easily be adapted to be an administrator module and include a call to the <tt>Route::link()</tt> function.

In a folder mod_uri_demo create the following 2 files:

<tt>mod_uri_demo.xml</tt>
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="3.1" client="site" method="upgrade">
<name>URI demo</name>
<version>1.0.1</version>
<description>Code demonstrating use of Joomla URI class</description>
<files>
<filename module="mod_uri_demo">mod_uri_demo.php</filename>
</files>
</extension>
</source>

<tt>mod_uri_demo.php</tt>
<source lang="php">
<?php
defined('_JEXEC') or die('Restricted Access');

use Joomla\CMS\Uri\Uri;
use Joomla\CMS\Router\Route;

// current URI
$uri = Uri::getInstance();
echo "Page URI is: " . $uri->toString() . " ";
echo "Scheme: " . $uri->getScheme() . ", Host: " . $uri->getHost() . " , Path: " . $uri->getPath() . " ";

// base() and root()
echo "URI base(): " . $uri->base() . ", pathonly: " . $uri->base(true) . " ";
echo "URI root(): " . $uri->root() . ", pathonly: " . $uri->root(true) . " ";

// External webpage
$joomla = Uri::getInstance("//www.joomla.org");
$joomla->setScheme("https");
$joomla->setPath("/announcements");
$joomlaNews = $joomla->toString();
echo "<a href='$joomlaNews'>Joomla news</a> ";

// static internal address - put picture.jpg in images folder
echo '<img src="' . Uri::root() . 'images/picture.jpg" alt="Link to images/picture.jpg"> ';

// link to article with id=1
$article1 = Route::_("index.php?option=com_content&view=article&id=1");
echo "URL for article 1: $article1 ";
echo "<a href='$article1'>First article</a> ";
</source>

Zip up the mod_uri_demo directory to create <tt>mod_uri_demo.zip</tt>.

Within your Joomla administrator go to Install Extensions and via the Upload Package File tab select this zip file to install this sample mod_uri_demo module.

Make this module visible by editing it (click on it within the Modules page) then:
# making its status Published
# selecting a position on the page for it to be shown
# on the menu assignment tab specify the pages it should appear on

When you visit a site web page then you should see the module in your selected position, and it should present a number of URLs and links demonstrating use of several of the Uri and Route class functions.

== Related Material ==
On the topic of SEF URLs see [[Search Engine Friendly URLs]] and [[J3.x:Supporting_SEF_URLs_in_your_component|Supporting SEF URLs in your component]].

A custom router is developed in steps [[J3.x:Developing_an_MVC_Component/Adding_an_alias|Adding an alias]], [[J3.x:Developing_an_MVC_Component/Using_the_language_filter_facility|Using the language filter facility]] and [[J3.x:Developing_an_MVC_Component/Adding_Associations|Adding Associations]] of the MVC Component Development tutorial.

[[Category:Development]]
[[Category:Tutorials]]
[[Category:Module Development]]
[[Category:Plugin Development]]
[[Category:Component Development]]

GSoC 2021 Project Ideas

2021-01-20T18:10:11Z

Flyingwombats: /* Difficulty */

{{Top portal heading|color=white-bkgd|text-color=#333|title=
Welcome to Joomla GSoC 2021 Projects Page }}
[[Image:Gsoc2016.png|150px|center|link=GSoC 2020]]

{{tip|title=The application for students is going to open soon!}}

Welcome to the [[GSoC_2021|Joomla Google Summer of Code (GSoC) 2021]] projects page.

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our [https://groups.google.com/forum/#!forum/jgsoc joomla-gsoc mailing list] and join our
[https://glip.com/joomla public Glip / Ringcentral chat tool].

'''''Note: The GSoC 2021 projects are displayed in no particular order'''''

==Project I: Frontend inline editing ==

===Project Description===
Implement a inline editing feature in the frontend for modules, articles, (and all other extensions, where it makes sense) (see: https://www.tiny.cloud/docs/demo/inline/)

See https://github.com/joomla/joomla-cms/pull/30476

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

Medium

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project II: Accessibility==

===Project Description===

Implement and improve several accessibility functions in Joomla!
Keyboard navigation

===Knowledge Prerequisite===
*Must have: PHP, mySQL, JS, CSS

===Difficulty===

Easy

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===

Easy

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]

[[Image:Gsoc2016.png|30px|center]]

==Project IV: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

Medium

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:mathur.geetanshu887@gmail.com Geetanshu Mathur]

[[Image:Gsoc2016.png|30px|center]]

{{tip|title=More Coming Soon!}}

[[Image:Gsoc2016.png|50px|center]]

<noinclude>
[[Category:Google Summer of Code 2021]]
[[Category:Google Summer of Code]]
</noinclude>

GSoC 2021 Project Ideas

2021-01-20T18:09:34Z

Flyingwombats: /* Difficulty */

{{Top portal heading|color=white-bkgd|text-color=#333|title=
Welcome to Joomla GSoC 2021 Projects Page }}
[[Image:Gsoc2016.png|150px|center|link=GSoC 2020]]

{{tip|title=The application for students is going to open soon!}}

Welcome to the [[GSoC_2021|Joomla Google Summer of Code (GSoC) 2021]] projects page.

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our [https://groups.google.com/forum/#!forum/jgsoc joomla-gsoc mailing list] and join our
[https://glip.com/joomla public Glip / Ringcentral chat tool].

'''''Note: The GSoC 2021 projects are displayed in no particular order'''''

==Project I: Frontend inline editing ==

===Project Description===
Implement a inline editing feature in the frontend for modules, articles, (and all other extensions, where it makes sense) (see: https://www.tiny.cloud/docs/demo/inline/)

See https://github.com/joomla/joomla-cms/pull/30476

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

Medium

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project II: Accessibility==

===Project Description===

Implement and improve several accessibility functions in Joomla!
Keyboard navigation

===Knowledge Prerequisite===
*Must have: PHP, mySQL, JS, CSS

===Difficulty===

Easy

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Medium

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]

[[Image:Gsoc2016.png|30px|center]]

==Project IV: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

Medium

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:mathur.geetanshu887@gmail.com Geetanshu Mathur]

[[Image:Gsoc2016.png|30px|center]]

{{tip|title=More Coming Soon!}}

[[Image:Gsoc2016.png|50px|center]]

<noinclude>
[[Category:Google Summer of Code 2021]]
[[Category:Google Summer of Code]]
</noinclude>

GSoC 2021 Project Ideas

2021-01-20T18:08:42Z

Flyingwombats: /* Difficulty */

{{Top portal heading|color=white-bkgd|text-color=#333|title=
Welcome to Joomla GSoC 2021 Projects Page }}
[[Image:Gsoc2016.png|150px|center|link=GSoC 2020]]

{{tip|title=The application for students is going to open soon!}}

Welcome to the [[GSoC_2021|Joomla Google Summer of Code (GSoC) 2021]] projects page.

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our [https://groups.google.com/forum/#!forum/jgsoc joomla-gsoc mailing list] and join our
[https://glip.com/joomla public Glip / Ringcentral chat tool].

'''''Note: The GSoC 2021 projects are displayed in no particular order'''''

==Project I: Frontend inline editing ==

===Project Description===
Implement a inline editing feature in the frontend for modules, articles, (and all other extensions, where it makes sense) (see: https://www.tiny.cloud/docs/demo/inline/)

See https://github.com/joomla/joomla-cms/pull/30476

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

Medium

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project II: Accessibility==

===Project Description===

Implement and improve several accessibility functions in Joomla!
Keyboard navigation

===Knowledge Prerequisite===
*Must have: PHP, mySQL, JS, CSS

===Difficulty===

Easy

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Medium

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]

[[Image:Gsoc2016.png|30px|center]]

==Project IV: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Moderate

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:mathur.geetanshu887@gmail.com Geetanshu Mathur]

[[Image:Gsoc2016.png|30px|center]]

{{tip|title=More Coming Soon!}}

[[Image:Gsoc2016.png|50px|center]]

<noinclude>
[[Category:Google Summer of Code 2021]]
[[Category:Google Summer of Code]]
</noinclude>

GSoC 2021 Project Ideas

2021-01-20T18:06:58Z

Flyingwombats: /* Difficulty */

{{Top portal heading|color=white-bkgd|text-color=#333|title=
Welcome to Joomla GSoC 2021 Projects Page }}
[[Image:Gsoc2016.png|150px|center|link=GSoC 2020]]

{{tip|title=The application for students is going to open soon!}}

Welcome to the [[GSoC_2021|Joomla Google Summer of Code (GSoC) 2021]] projects page.

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our [https://groups.google.com/forum/#!forum/jgsoc joomla-gsoc mailing list] and join our
[https://glip.com/joomla public Glip / Ringcentral chat tool].

'''''Note: The GSoC 2021 projects are displayed in no particular order'''''

==Project I: Frontend inline editing ==

===Project Description===
Implement a inline editing feature in the frontend for modules, articles, (and all other extensions, where it makes sense) (see: https://www.tiny.cloud/docs/demo/inline/)

See https://github.com/joomla/joomla-cms/pull/30476

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

Medium

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project II: Accessibility==

===Project Description===

Implement and improve several accessibility functions in Joomla!
Keyboard navigation

===Knowledge Prerequisite===
*Must have: PHP, mySQL, JS, CSS

===Difficulty===
*

===Mentors===
*

[[Image:Gsoc2016.png|30px|center]]

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Medium

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]

[[Image:Gsoc2016.png|30px|center]]

==Project IV: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Moderate

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:mathur.geetanshu887@gmail.com Geetanshu Mathur]

[[Image:Gsoc2016.png|30px|center]]

{{tip|title=More Coming Soon!}}

[[Image:Gsoc2016.png|50px|center]]

<noinclude>
[[Category:Google Summer of Code 2021]]
[[Category:Google Summer of Code]]
</noinclude>

GSoC 2021

2021-01-20T17:42:17Z

Flyingwombats: Rearrange adn remove old links

{{Top portal heading|color=white-bkgd|text-color=#333|title=Welcome to Joomla Google Summer of Code 2021 }}
[[Image:Gsoc2016.png|200px|center]]
<noinclude><languages /></noinclude>
<translate>

This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.


{{tip|title=Make sure to check out the [[GSoC 2021 Project Ideas|2021 project list]]}}

== CMS == 
Joomla developers are currently working on multiple projects: the Joomla CMS main 3.x Version and the upcoming new major version 4.0 (2021). Additionally there are many side projects related to testing, performance, and other things.


The Joomla CMS is the very popular and well known FOSS content management system powering currently around 3-4 % of the internet.

== What is GSoC? == 
Google Summer of Code is a program run by Google for college students interested in getting a stipend to contribute to Open Source Software. They will spend their summer with improving and writing new features for the project. [https://summerofcode.withgoogle.com/ Visit the Google Summer of Code website to learn more.]


*[https://volunteers.joomla.org/teams/google-summer-of-code-joomla-team Joomla GSoC Team on Joomla Volunteers Portal]

=== Project Timeline === 
The GSoC 2021 time line is available on the GSoC Site, we suggest you to go through it: [https://summerofcode.withgoogle.com/how-it-works]

=== Project Proposal === 
Please check the [[GSoC Student Application Template]] to understand what we are expecting from your proposal.


===Last years projects:===
*[https://summerofcode.withgoogle.com/archive/2019/organizations/6743345328553984/ Google Summer of Code for Joomla! 2019]
*[https://summerofcode.withgoogle.com/archive/2018/organizations/6484151049912320/ Google Summer of Code for Joomla! 2018]

== Information For Students == 
* [[GSoC 2021 Project Ideas|Joomla's project list]]
* [[GSoC Student Selection Criteria]]
* [[GSoC Student Application Template]]
* [https://groups.google.com/forum/?hl=en#!forum/jgsoc Joomla GSoC Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]

==Information for Mentors== 
*Want to be a mentor? Please check the [[GSoC Mentor Guidelines]].
*[[GSoC Mentors Selection Criteria]]


==Any questions please do contact the Joomla GSoC Core Team 2021:==
*[mailto:philip.walton@community.joomla.org Philip Walton (Lead and Admin)]
*[mailto:shivam.rajput@community.joomla.org Shivam Rajput (Admin)]
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle (Technical Lead)]
*[mailto:tobias.zulauf@community.joomla.org Tobias Zulauf (Infrastructure Lead)]

==Related Articles== 

===Google Summer of Code 2019=== 
*[https://community.joomla.org/gsoc-2019.html Joomla GSoC 2019 blog articles.]

===Google Summer of Code 2018=== 
*[https://community.joomla.org/gsoc-2018.html Joomla GSoC 2018 blog articles.]

===Google Summer of Code 2017=== 
*[https://community.joomla.org/gsoc-2017.html Joomla GSoC 2017 blog articles.]

===Google Summer of Code 2016=== 
*[https://magazine.joomla.org/issues/issue-sep-2016/item/3129-gsoc-every-story-has-an-ending-every-ending-is-a-new-beginning GSoC: Every Story Has An Ending. Every Ending Is A New Beginning.]
*[https://magazine.joomla.org/issues/issue-oct-2016/item/3143-the-brains-behind-joomla-gsoc The brains behind the Joomla! GSoC projects]
*[https://magazine.joomla.org/issues/issue-oct-2016/item/3152-gsoc-student-ruchiranga-wickramasinghe Interview with one of the 2016 students Ruchiranga Wickramasinghe]
*[http://magazine.joomla.org/issues/issue-feb-2016/item/2964-joomla-s-google-summer-of-code-gsoc-is-proud-to-announce-team-lead-puneet-kala Joomla's Google Summer of Code (GSoC) is Proud to Announce Team Lead: Puneet Kala]
*[http://community.joomla.org/blogs/community/1894-joomla-has-been-selected-as-a-google-summer-of-code-2016-mentor-organization.html Joomla! has been selected as a Google Summer of Code 2016 mentor organization]
*[https://community.joomla.org/gsoc-2016/3070-joomla-google-mentor-summit-gsoc16.html Joomla! is going to the 2016 Google Summer of Code Mentor Summit]
*[https://magazine.joomla.org/all-issues/tags/google-summer-of-code Articles on Joomla Community Magazine]
</translate>

<noinclude>
[[Category:Google Summer of Code 2020]]
[[Category:Google Summer of Code]]
</noinclude>

GSoC 2021

2021-01-20T17:25:09Z

Flyingwombats: Change the core team position in the document

{{Top portal heading|color=white-bkgd|text-color=#333|title=Welcome to Joomla Google Summer of Code 2021 }}
[[Image:Gsoc2016.png|200px|center]]
<noinclude><languages /></noinclude>
<translate>

This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.


{{tip|title=Make sure to check out the [[GSoC 2021 Project Ideas|2021 project list]]}}

== CMS == 
Joomla developers are currently working on multiple projects: the Joomla CMS main 3.x Version and the upcoming new major version 4.0 (2021). Additionally there are many side projects related to testing, performance, and other things.


The Joomla CMS is the very popular and well known FOSS content management system powering currently around 3-4 % of the internet.

== What is GSoC? == 
Google Summer of Code is a program run by Google for college students interested in getting a stipend to contribute to Open Source Software. They will spend their summer with improving and writing new features for the project. [https://summerofcode.withgoogle.com/ Visit the Google Summer of Code website to learn more.]


*[https://summerofcode.withgoogle.com/how-it-works/#timeline Google Summer of Code Timeline]
*[[GSOC_2016_Joomla_GIT_Workflow|Github Work Flow for GSoC Students and Mentors]]
*[https://volunteers.joomla.org/teams/google-summer-of-code-joomla-team Joomla GSoC Team on Joomla Volunteers Portal]


Last years projects:
*[https://summerofcode.withgoogle.com/archive/2019/organizations/6743345328553984/ Google Summer of Code for Joomla! 2019]
*[https://summerofcode.withgoogle.com/archive/2018/organizations/6484151049912320/ Google Summer of Code for Joomla! 2018]

== Information For Students == 
* [[GSoC 2021 Project Ideas|Joomla's project list]]
* [[GSoC Student Selection Criteria]]
* [[GSoC Student Application Template]]
* [https://groups.google.com/forum/?hl=en#!forum/jgsoc Joomla GSoC Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]

== Information For Mentors and Proposals == 
* [[GSoC_Ideas_Selection_Criteria_2020|GSoC Ideas Selection Criteria 2020]]

== General information == 
* [[GSOC_2016_Joomla_GIT_Workflow|Github Work Flow for GSoC Students and Mentors]]

=== Project Timeline === 
The GSoC 2020 time line is available on the GSoC Site, we suggest you to go through it: [https://summerofcode.withgoogle.com/how-it-works/#timeline GSoC 2020 Timeline]

=== Project Proposal === 
Please check the [[GSoC Student Application Template]] to understand what we are expecting from your proposal.

==Information for Mentors== 
*Want to be a mentor? Please check the [[GSoC Mentor Guidelines]].
*[[GSoC Mentors Selection Criteria]]

<hr>

==Any questions please do contact the Joomla GSoC Core Team 2021:==
*[mailto:philip.walton@community.joomla.org Philip Walton (Lead and Admin)]
*[mailto:shivam.rajput@community.joomla.org Shivam Rajput (Admin)]
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle (Technical Lead)]
*[mailto:tobias.zulauf@community.joomla.org Tobias Zulauf (Infrastructure Lead)]

==Related Articles== 

===Google Summer of Code 2019=== 
*[https://community.joomla.org/gsoc-2019.html Joomla GSoC 2019 blog articles.]

===Google Summer of Code 2018=== 
*[https://community.joomla.org/gsoc-2018.html Joomla GSoC 2018 blog articles.]

===Google Summer of Code 2017=== 
*[https://community.joomla.org/gsoc-2017.html Joomla GSoC 2017 blog articles.]

===Google Summer of Code 2016=== 
*[https://magazine.joomla.org/issues/issue-sep-2016/item/3129-gsoc-every-story-has-an-ending-every-ending-is-a-new-beginning GSoC: Every Story Has An Ending. Every Ending Is A New Beginning.]
*[https://magazine.joomla.org/issues/issue-oct-2016/item/3143-the-brains-behind-joomla-gsoc The brains behind the Joomla! GSoC projects]
*[https://magazine.joomla.org/issues/issue-oct-2016/item/3152-gsoc-student-ruchiranga-wickramasinghe Interview with one of the 2016 students Ruchiranga Wickramasinghe]
*[http://magazine.joomla.org/issues/issue-feb-2016/item/2964-joomla-s-google-summer-of-code-gsoc-is-proud-to-announce-team-lead-puneet-kala Joomla's Google Summer of Code (GSoC) is Proud to Announce Team Lead: Puneet Kala]
*[http://community.joomla.org/blogs/community/1894-joomla-has-been-selected-as-a-google-summer-of-code-2016-mentor-organization.html Joomla! has been selected as a Google Summer of Code 2016 mentor organization]
*[https://community.joomla.org/gsoc-2016/3070-joomla-google-mentor-summit-gsoc16.html Joomla! is going to the 2016 Google Summer of Code Mentor Summit]
*[https://magazine.joomla.org/all-issues/tags/google-summer-of-code Articles on Joomla Community Magazine]
</translate>

<noinclude>
[[Category:Google Summer of Code 2020]]
[[Category:Google Summer of Code]]
</noinclude>

Pizza Bugs and Fun 2020/Contributors List

2020-10-17T07:48:00Z

Flyingwombats: /* These awesome Joomlers contributed to Pizza, Bugs & Fun 2020 */

[[Image:pbf-2020<translate> en</translate>.png|1100px]]
<noinclude><languages /></noinclude>

[[File:PBF2020 CONTRIBUTORS.png|1100px|center]]

<translate>''Edit the page and add your name to have your contribution to PBF2020 recorded.''</translate>

== <translate>These awesome Joomlers contributed to Pizza, Bugs & Fun 2020</translate>==

Australia:
* Patrick Jackson (Melbourne JUG)
* Stuart Robertson (Brisbane JUG)
* Jenny McWilliam (Melbourne JUG)
UK
* Phil Walton

Bugs & Fun @Home

2020-09-12T14:00:14Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 00:00UTC to 12:00UTC Saturday, Weekly ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
[https://meet.google.com/bke-ufkq-eif Join on Google Meet: bke-ufkq-eif] [https://kps.fyi/utc Check your local time] 
''Meet URL is permanent every weekend until updated.''
 
 
'''Call into the Early Room from 00:00UTC to 12:00UTC to talk about anything Joomla!'''
 
Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements, but is up for a conversation on anything Joomla related if anyone's wanting to jump online.

=== Afternoon Room UTC ===

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
* '''Writing, reviewing, updating and improving current documents.'''
* '''Translating documents into different languages.'''</translate> 
<translate>
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]</translate>

=== <translate> Adventurer</translate> ===
* '''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub
====Accessibility====
https://github.com/joomla/joomla-cms/labels/a11y
====Release Blockers====
https://github.com/joomla/joomla-cms/labels/Release%20Blocker

=== <translate> Conqueror</translate> ===
* '''<translate> Creating pull requests</translate>''' 
<translate> This is where you are encouraged to make your own pull requests.</translate>
<translate>
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]</translate>

==<translate> Resources</translate>==
The following resources are available to help you to get the various jobs done.

===<translate> Joomla Docs</translate>===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===<translate> Joomla on GitHub</translate>===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===<translate> Joomla Issues on GitHub</translate>===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===<translate> Patch testing article</translate>===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===<translate> Patchtester 4 for Joomla 4 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc3 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc3]

===<translate> Patchtester 3 for Joomla 3 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===<translate> Prebuilt Packages</translate>===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===<translate> Setting up your J4 Environment</translate>===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta4-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta4-dev-Development-Full_Package.zip]

===<translate> Next Joomla 3 release candidate</translate>===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===<translate> Testing sheet for release candidates</translate>===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

<noinclude>[[Category:Events]][[Category:Pizza_Bugs_and_Fun]]</noinclude>

Bugs & Fun @Home

2020-08-15T09:10:40Z

Flyingwombats: /* Patchtester 4 for Joomla 4 download */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 00:00UTC to 12:00UTC Saturday, Weekly ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
[https://meet.google.com/bke-ufkq-eif Join on Google Meet: bke-ufkq-eif] [https://kps.fyi/utc Check your local time] 
''Meet URL is permanent every weekend until updated.''
 
 
'''Call into the Early Room from 00:00UTC to 12:00UTC to talk about anything Joomla!'''
 
Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements, but is up for a conversation on anything Joomla related if anyone's wanting to jump online.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday Weekly 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
* '''Writing, reviewing, updating and improving current documents.'''
* '''Translating documents into different languages.'''</translate> 
<translate>
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]</translate>

=== <translate> Adventurer</translate> ===
* '''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub
====Accessibility====
https://github.com/joomla/joomla-cms/labels/a11y
====Release Blockers====
https://github.com/joomla/joomla-cms/labels/Release%20Blocker

=== <translate> Conqueror</translate> ===
* '''<translate> Creating pull requests</translate>''' 
<translate> This is where you are encouraged to make your own pull requests.</translate>
<translate>
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]</translate>

==<translate> Resources</translate>==
The following resources are available to help you to get the various jobs done.

===<translate> Joomla Docs</translate>===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===<translate> Joomla on GitHub</translate>===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===<translate> Joomla Issues on GitHub</translate>===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===<translate> Patch testing article</translate>===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===<translate> Patchtester 4 for Joomla 4 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc3 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc3]

===<translate> Patchtester 3 for Joomla 3 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===<translate> Prebuilt Packages</translate>===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===<translate> Setting up your J4 Environment</translate>===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta4-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta4-dev-Development-Full_Package.zip]

===<translate> Next Joomla 3 release candidate</translate>===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===<translate> Testing sheet for release candidates</translate>===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

<noinclude>[[Category:Events]][[Category:Pizza_Bugs_and_Fun]]</noinclude>

Bugs & Fun @Home

2020-08-15T09:09:18Z

Flyingwombats: /* Joomla_4.0.0-beta4-dev-Development-Full_Package */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 00:00UTC to 12:00UTC Saturday, Weekly ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
[https://meet.google.com/bke-ufkq-eif Join on Google Meet: bke-ufkq-eif] [https://kps.fyi/utc Check your local time] 
''Meet URL is permanent every weekend until updated.''
 
 
'''Call into the Early Room from 00:00UTC to 12:00UTC to talk about anything Joomla!'''
 
Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements, but is up for a conversation on anything Joomla related if anyone's wanting to jump online.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday Weekly 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
* '''Writing, reviewing, updating and improving current documents.'''
* '''Translating documents into different languages.'''</translate> 
<translate>
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]</translate>

=== <translate> Adventurer</translate> ===
* '''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub
====Accessibility====
https://github.com/joomla/joomla-cms/labels/a11y
====Release Blockers====
https://github.com/joomla/joomla-cms/labels/Release%20Blocker

=== <translate> Conqueror</translate> ===
* '''<translate> Creating pull requests</translate>''' 
<translate> This is where you are encouraged to make your own pull requests.</translate>
<translate>
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]</translate>

==<translate> Resources</translate>==
The following resources are available to help you to get the various jobs done.

===<translate> Joomla Docs</translate>===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===<translate> Joomla on GitHub</translate>===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===<translate> Joomla Issues on GitHub</translate>===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===<translate> Patch testing article</translate>===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===<translate> Patchtester 4 for Joomla 4 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===<translate> Patchtester 3 for Joomla 3 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===<translate> Prebuilt Packages</translate>===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===<translate> Setting up your J4 Environment</translate>===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta4-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta4-dev-Development-Full_Package.zip]

===<translate> Next Joomla 3 release candidate</translate>===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===<translate> Testing sheet for release candidates</translate>===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

<noinclude>[[Category:Events]][[Category:Pizza_Bugs_and_Fun]]</noinclude>

Bugs & Fun @Home

2020-08-07T18:35:27Z

Flyingwombats: /* Adventurer */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 00:00UTC to 12:00UTC Saturday, Weekly ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
[https://meet.google.com/shu-xtpc-nvg Join on Google Meet: shu-xtpc-nvg] [https://kps.fyi/utc Check your local time] 
''Meet URL is permanent every weekend until updated.''
 
 
'''Call into the Early Room from 00:00UTC to 12:00UTC to talk about anything Joomla!'''
 
Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements, but is up for a conversation on anything Joomla related if anyone's wanting to jump online.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday Weekly 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
* '''Writing, reviewing, updating and improving current documents.'''
* '''Translating documents into different languages.'''</translate> 
<translate>
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]</translate>

=== <translate> Adventurer</translate> ===
* '''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub
====Accessibility====
https://github.com/joomla/joomla-cms/labels/a11y
====Release Blockers====
https://github.com/joomla/joomla-cms/labels/Release%20Blocker

=== <translate> Conqueror</translate> ===
* '''<translate> Creating pull requests</translate>''' 
<translate> This is where you are encouraged to make your own pull requests.</translate>
<translate>
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]</translate>

==<translate> Resources</translate>==
The following resources are available to help you to get the various jobs done.

===<translate> Joomla Docs</translate>===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===<translate> Joomla on GitHub</translate>===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===<translate> Joomla Issues on GitHub</translate>===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===<translate> Patch testing article</translate>===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===<translate> Patchtester 4 for Joomla 4 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===<translate> Patchtester 3 for Joomla 3 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===<translate> Prebuilt Packages</translate>===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===<translate> Setting up your J4 Environment</translate>===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===<translate> Next Joomla 3 release candidate</translate>===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===<translate> Testing sheet for release candidates</translate>===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

<noinclude>[[Category:Events]][[Category:Pizza_Bugs_and_Fun]]</noinclude>

Bugs & Fun @Home

2020-07-24T07:01:08Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 00:00UTC to 12:00UTC Weekly ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
[https://meet.google.com/shu-xtpc-nvg Join on Google Meet: shu-xtpc-nvg] [https://kps.fyi/utc Check your local time] 
''Meet URL is permanent every weekend until updated.''
 
 
'''Call into the Early Room from 00:00UTC to 12:00UTC to talk about anything Joomla!'''
 
Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements, but is up for a conversation on anything Joomla related if anyone's wanting to jump online.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday Weekly 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
* '''Writing, reviewing, updating and improving current documents.'''
* '''Translating documents into different languages.'''</translate> 
<translate>
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]</translate>

=== <translate> Adventurer</translate> ===
* '''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
* '''<translate> Creating pull requests</translate>''' 
<translate> This is where you are encouraged to make your own pull requests.</translate>
<translate>
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]</translate>

==<translate> Resources</translate>==
The following resources are available to help you to get the various jobs done.

===<translate> Joomla Docs</translate>===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===<translate> Joomla on GitHub</translate>===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===<translate> Joomla Issues on GitHub</translate>===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===<translate> Patch testing article</translate>===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===<translate> Patchtester 4 for Joomla 4 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===<translate> Patchtester 3 for Joomla 3 download</translate>===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===<translate> Prebuilt Packages</translate>===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===<translate> Setting up your J4 Environment</translate>===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===<translate> Next Joomla 3 release candidate</translate>===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===<translate> Testing sheet for release candidates</translate>===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

<noinclude>[[Category:Events]][[Category:Pizza_Bugs_and_Fun]]</noinclude>

Bugs & Fun @Home

2020-07-21T23:02:08Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 06:00UTC to 12:00UTC July 25 ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
Meet Link coming on Friday [https://kps.fyi/utc Check your local time] 
 
Call into the Early Room from 06:00UTC to 12:00UTC to talk about anything Joomla! Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements between conversations if anyone's wanting to jump online.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday July 25th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-07-17T06:49:56Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room 00:00UTC to 12:00UTC ===
'''Google Meet''' 
'''This weekend, it's more than just bug testing...''' 
[https://meet.google.com/kci-sdkc-ccz Google Meet: kci-sdkc-ccz] [https://kps.fyi/utc Check your local time] 
 
Call into the Early Room from 00:00UTC to 12:00UTC to talk about anything Joomla! Early Room Convenor, [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] is in Melbourne, Australia, which has gone back into Stage 3 COVID Restrictions following local outbreaks in Australia. So he's stuck at home, and will be doing some Joomla 4 Patch Testing and Documentation improvements between conversations if anyone's wanting to jump online.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday July 18th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-07-10T19:03:55Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room UTC ===
'''Zoom on Demand''' 
Saturday July 4th 
Though we don't have a formal Zoom room running this weekend for the Early Room, say hi in the RingCentral Bugs & Fun at Home channel, and a zoom on demand can be spun up if there's enough interest. Alternatively, reach out to [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] if you're not on RingCentral.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday July 11th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-07-03T14:44:48Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room UTC ===
'''Zoom on Demand''' 
Saturday July 4th 
Though we don't have a formal Zoom room running this weekend for the Early Room, say hi in the RingCentral Bugs & Fun at Home channel, and a zoom on demand can be spun up if there's enough interest. Alternatively, reach out to [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] if you're not on RingCentral.

=== Afternoon Room UTC ===
'''Zoom on Request''' 
Zoom Meeting on request from 13:00 - 15:00 UTC Saturday July 4th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet on Request''' 
Google Meet rooms are also available for each BFH on request if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-07-03T14:43:01Z

Flyingwombats: /* Afternoon Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room UTC ===
'''Zoom on Demand''' 
Saturday July 4th 
Though we don't have a formal Zoom room running this weekend for the Early Room, say hi in the RingCentral Bugs & Fun at Home channel, and a zoom on demand can be spun up if there's enough interest. Alternatively, reach out to [https://volunteers.joomla.org/joomlers/213-patrick-jackson Patrick Jackson] if you're not on RingCentral.

=== Afternoon Room UTC ===
'''Zoom''' 
Zoom Meeting from 13:00 - 15:00 UTC Saturday July 4th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-06-26T13:04:51Z

Flyingwombats: /* Early Room UTC */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room UTC ===
'''Zoom''' 
Zoom Meeting from 5:00 - 7:00 UTC Saturday June 27th 

=== Afternoon Room UTC ===
'''Zoom''' 
Zoom Meeting from 13:00 - 15:00 UTC Saturday June 27th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-06-26T13:03:50Z

Flyingwombats: /* Meeting rooms */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>
=== Early Room UTC ===
'''Zoom''' 
Zoom Meeting from 5:00 - 7:00 UTC Saturday June 27th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

=== Afternoon Room UTC ===
'''Zoom''' 
Zoom Meeting from 13:00 - 15:00 UTC Saturday June 27th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
13:00 - 15:00 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-06-20T06:26:41Z

Flyingwombats: /* Meeting rooms */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>

'''Zoom''' 
Zoom Meeting from 6:00 UTC Saturday June 20th 
https://us02web.zoom.us/j/87574501273?pwd=MFJ2aXNodktlRGhIdWQ0TXNnd2NLQT09 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
0600 UTC - 1800 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-06-17T11:22:47Z

Flyingwombats: /* Meeting rooms */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>

'''Zoom''' 
Zoom Meeting from 6:00 UTC Saturday June 20th 
https://us02web.zoom.us/meeting/tZMocO2trjooHdfimVItrs6o5dGQk0X6Hbue/ics?icsToken=98tyKuGvqzwuH9SUsh6ERpwEGY_CLO_ziH5BgqdblRLTKjRBcVX5Y-ZlA7kvKI74 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
0600 UTC - 1800 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-06-17T11:22:06Z

Flyingwombats: /* Meeting rooms */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>

'''Zoom''' 
Zoom Meeting from 6:00 UTC Saturday June 13th 
https://us02web.zoom.us/meeting/tZMocO2trjooHdfimVItrs6o5dGQk0X6Hbue/ics?icsToken=98tyKuGvqzwuH9SUsh6ERpwEGY_CLO_ziH5BgqdblRLTKjRBcVX5Y-ZlA7kvKI74 
Meeting ID: 875 7450 1273 
Password: 566206

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
0600 UTC - 1800 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]

Bugs & Fun @Home

2020-06-13T08:29:46Z

Flyingwombats: /* Joomla_4.0.0-beta2-dev-Development-Full_Package */

<noinclude><languages /></noinclude>
[[Image:Bfah.png|225px|right]]

<translate> Bugs and Fun @home is an event where Joomla enthusiasts meet online to improve Joomla. This is not only for improving the code of Joomla but also the documentation and translation. It is an online event for everybody to come, have fun and meet fellow Joomlers.</translate>

<translate>
The idea behind organizing Bugs and Fun @home events is to achieve these goals:
* Reduce the number of open issues
* Get Joomla tested on different environments
* Get more people interested in testing issues at home
* Meet fellow Joomlers online
* Have fun and learn in a friendly environment</translate>

== <translate> Origin</translate> ==
<translate> The idea for Bugs & Fun @home came about when most of Europe was in lockdown during the COVID-19 pandemic. It came out of a discussion in a Production team meeting.</translate>
<translate> The first incarnation was [https://developer.joomla.org/news/808-pizza-bugs-and-fun-without-the-pizza.html Pizza Bugs & Fun without the Pizza]</translate>
<translate>
And the first online meeting Saturday 4th April. It is held weekly every Saturday.
Its name was changed to Bugs & Fun @Home. Details were on a spreadsheet until this article was written.</translate>

== <translate> Meeting rooms</translate> ==
<translate> There are meeting rooms provided every week. The current rooms are here:</translate>

'''Zoom''' 
Zoom Meeting from 6:00 UTC Saturday June 13th 
https://us02web.zoom.us/j/86755700008?pwd=Ujc4c1BQMzFnWVFCNythTVEwYkdJdz09 
Meeting ID: 867 5570 0008 
Password: 216586

'''Google Meet''' 
Google Meet rooms are also available for each BFH if you prefer it to Zoom. 
0600 UTC - 1800 UTC https://meet.google.com/ywv-ncoj-ubk 
Dial-in: (GB) +44 20 3956 9352 PIN: 363 609 351# 
To complete the day, an additional Meet link is also added later in the day.

== <translate> Bugs & Fun Activities List</translate> ==
<translate> The types of activity are split into three levels - Explorer, Adventurer and Conqueror.</translate>
You can access the current list of tasks being looked at in this [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/ Google Sheet].

=== <translate> Explorer</translate> ===
<translate>
'''Writing, reviewing, updating and improving current documents.'''
'''Translating documents into different languages.'''</translate> 
The full list is currently on this sheet
[https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1454163514 Explorer tab]

=== <translate> Adventurer</translate> ===
'''<translate> Testing patches</translate>''' 
This is where we test patches and using the chat feature provided on every Bugs & Fun @Home we can check with others online for help in conducting the tests and collaborate with others to get the second tester needed to fulfil the testing requirements.
At the moment it is still in this spreadsheet tab [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=1748937094 Adventurer tab] We are looking to move this to tags in GitHub

=== <translate> Conqueror</translate> ===
'''<translate> Creating pull requests</translate>''' 
This is where you are encouraged to make your own pull requests.
Others can then help to test the pull request and if it passes it may make it into the core of Joomla.
The list is currently held on this spreadsheet [https://docs.google.com/spreadsheets/d/1TR_-NqoPDSWnUnysT2MRdINVyXCnkzyJteml8-CfFAc/edit#gid=0 Conqueror tab]

==Resources==
The following resources are available to help you to get the various jobs done.

===Joomla Docs===
[[Portal:Joomla!_Code_Contributors|Joomla! Code Contributors]]

===Joomla on GitHub===
[https://github.com/joomla/joomla-cms github.com/joomla/joomla-cms]

===Joomla Issues on GitHub===
[https://github.com/joomla/joomla-cms/issues github.com/joomla/joomla-cms/issues]

===Pizza bugs and fun===
[https://pizza-bugs-fun.com/en/ pizza-bugs-fun.com]

===Issue tracker===
[https://issues.joomla.org/ issues.joomla.org]

===Patch testing article===
[[Testing_Joomla!_patches|Testing Jooma! patches]]

===Patchtester 4 for Joomla 4 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2 github.com/joomla-extensions/patchtester/releases/tag/4.0.0-rc2]

===Patchtester 3 for Joomla 3 download===
[https://github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc github.com/joomla-extensions/patchtester/releases/tag/3.0.0.rc]

===Prebuilt Packages===
[[Testing_Joomla!_patches#Prebuild_packages|Prebuild packages]]

===Joomla Nightly Builds===
[https://developer.joomla.org/nightly-builds.html developer.joomla.org/nightly-builds.html]

===Setting up your J4 Environment===
[[J4.x:Setting_Up_Your_Local_Environment|Setting Up Your Local Environment]]

===Joomla_4.0.0-beta2-dev-Development-Full_Package===
[https://developer.joomla.org/nightlies/Joomla_4.0.0-beta2-dev-Development-Full_Package.zip]

===Next Joomla 3 release candidate===
[https://github.com/joomla/joomla-cms/tree/3.9.19-rc github.com/joomla/joomla-cms/tree/3.9.19-rc]

===Testing sheet for release candidates===
[https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 CMS Release Checksheet (GoogleDocs)]