Introducing the 185 Organizations for GSoC 2026

The complete list of Google Summer of Code (GSoC) Mentoring Organizations is now available! 2026 brings us 185 open source communities who are eager to mentor a new group of open source contributors. Now is the time for prospective contributors to start looking for a community to participate with. Visit the full list of 2026 organizations to learn about each community, their project ideas, and read the specific contributor guidance to apply.

Who can apply as a GSoC contributor?
If you are 18 or older and a student or just starting out in open source (less than 2 years of open source experience), GSoC is for you!

Why participate in Google Summer of Code?
GSoC offers a unique opportunity to gain real-world experience and build new skills through open source contributions while being mentored by experienced maintainers and developers.

The application period starts on March 16th at 1800 UTC. Here are some things you can do to get started:

  • Visit our GSoC website and read the FAQ, the Contributor Guide, Advice for people applying for GSoC, Program Rules and the videos for Potential GSoC Contributors to learn the basics about GSoC.
  • Browse the Organization pages—use filters (languages, categories) to narrow down your choices.
  • Look at the Project Ideas for the Orgs you like. Pick one that excites you and reach out to them ASAP to talk about it.
  • Heads up! Each Org has its own application steps and maybe some required pre-tasks. Check their Contributor guidance link in their profile. Chatting and contributing early is HUGE for getting accepted!
  • Write a proposal based on the organization guidelines, also remember that some orgs do not allow the use of AI, be aware of their guidelines.
  • We strongly recommend submitting your proposal on the GSoC site at least 3 days before the hard deadline March 31, 1800 UTC.

Mark your calendars with the upcoming important GSoC 2026 dates!

  • Contributor application period: March 16 - 31 1800 UTC
  • GSoC 2026 Accepted Contributors announced: April 30 1800 UTC
  • Coding Starts: May 25

Thank you for being part of this wonderful community and we wish the best of luck to all the 2026 applicants!

Introducing the 185 Organizations for GSoC 2026

The complete list of Google Summer of Code (GSoC) Mentoring Organizations is now available! 2026 brings us 185 open source communities who are eager to mentor a new group of open source contributors. Now is the time for prospective contributors to start looking for a community to participate with. Visit the full list of 2026 organizations to learn about each community, their project ideas, and read the specific contributor guidance to apply.

Who can apply as a GSoC contributor?
If you are 18 or older and a student or just starting out in open source (less than 2 years of open source experience), GSoC is for you!

Why participate in Google Summer of Code?
GSoC offers a unique opportunity to gain real-world experience and build new skills through open source contributions while being mentored by experienced maintainers and developers.

The application period starts on March 16th at 1800 UTC. Here are some things you can do to get started:

  • Visit our GSoC website and read the FAQ, the Contributor Guide, Advice for people applying for GSoC, Program Rules and the videos for Potential GSoC Contributors to learn the basics about GSoC.
  • Browse the Organization pages—use filters (languages, categories) to narrow down your choices.
  • Look at the Project Ideas for the Orgs you like. Pick one that excites you and reach out to them ASAP to talk about it.
  • Heads up! Each Org has its own application steps and maybe some required pre-tasks. Check their Contributor guidance link in their profile. Chatting and contributing early is HUGE for getting accepted!
  • Write a proposal based on the organization guidelines, also remember that some orgs do not allow the use of AI, be aware of their guidelines.
  • We strongly recommend submitting your proposal on the GSoC site at least 3 days before the hard deadline March 31, 1800 UTC.

Mark your calendars with the upcoming important GSoC 2026 dates!

  • Contributor application period: March 16 - 31 1800 UTC
  • GSoC 2026 Accepted Contributors announced: April 30 1800 UTC
  • Coding Starts: May 25

Thank you for being part of this wonderful community and we wish the best of luck to all the 2026 applicants!

Manage permission to edit group details and changes to groups settings

We’re introducing a new permission in Google Groups: "Who can modify group details." This update allows group owners and managers to grant specific roles the ability to edit a group's name and description.

Previously, the ability to edit a group’s name and description was limited to the owner and manager roles. This meant that if an owner wanted a member to be able to update the name or description, they had to grant that member manager status, which included a broader set of additional permissions.

With this launch, "Who can modify group details" is now a standalone, configurable permission. Group owners and managers can now precisely control who can update these details, choosing from owners, managers, or all members of the group.

Additionally, as part of this launch, all group members will be able to see the groups settings page, however the ability to edit it will continue to depend on the groups permissions and the users role.

The new setting: “Who can modify group details”

Getting started

  • Admins: There is no admin control for this feature.
  • End users: This feature will be set to “Group owners and managers” by default. Visit the Help Center to learn more.

Rollout pace

Availability

  • Available to all Google Workspace customers and users with personal Google accounts

Resources

Educators can now get help drafting personalized guidance on written assignments with AI-suggested feedback in Google Classroom

We’re introducing AI-suggested feedback for written assignments in Google Classroom, a new feature designed to help educators provide high-quality, personalized support to their students more efficiently. Educators can now generate suggestions from Gemini to draft feedback that is specifically tailored to a student's work, grade level, and any specific focus area designated by the educator.

Educators have shared that personalized feedback is critical for closing learning gaps, yet it is often one of the most time-consuming tasks. By using AI to assist in drafting these comments, teachers can:

  • Manage workloads effectively: Get support in significantly reducing the hours spent giving input on written assignments.
  • Enhance student growth: Deliver the timely, specific feedback students need to build stronger self-reflection and evaluation skills.
  • Prioritize personalization efficiency: Use Gemini’s drafts as a starting point to provide high-level, empathetic guidance that might otherwise be difficult to scale across large classes.
When giving feedback in private comments on assignments in Google Classroom, educators can select “Help me write” to have Gemini suggest written feedback for the assignment. Teachers can then review, edit, and refine before sharing with students, ensuring teachers remain in control of the guidance provided while reducing the time spent on writing manual feedback.

By highlighting a student's strengths and identifying specific areas for improvement, this feature empowers educators to do their best work while ensuring every student feels heard and supported.


Additional details
This feature is a part of Gemini in Google Classroom. Gemini in Classroom is only available in English for education users over the age of 18.

Getting started

Rollout pace

Availability

  • Available for Google Workspace for Education Plus and the Teaching and Learning add-on

Resources

New ‘Take notes for me’ configuration in the Admin console for select Gemini Alpha customers

*Note: This update only applies to customers who participate in the Gemini Alpha program for Workspace.

To help users remember to get notes for meetings where it is most valuable, we are developing new settings for ‘Take notes for me’ that lets users and admins pre-configure AI note taking. For organizations in the Gemini Alpha, we will soon begin testing a new setting in Google Meet that will automatically enable Take notes for me for meetings with three or more participants.

This setting will be on by default for organizations in the Gemini Alpha program. Admins can disable it at any time, as soon as they see the new setting in their admin console.


This setting may be visible to customers broadly, but it will only be functionable for customers participating in the Gemini Alpha program.

In addition to this test, we are also introducing more ways hosts and participants can control Take notes for me. Soon, all customers—regardless of whether they are in the Gemini Alpha program—will see the ability to turn off "Take notes for me" directly from the green room before joining a call. See this post for more details on the new controls

Getting started

  • Admins: This new setting will be on by default for organizations in the Gemini Alpha starting no sooner than March 11th. Admins can opt out of this experience starting now by going to the Google Meet Admin Console, going to Gemini settings, and adjusting the value under “Automatic note-taking” to “OFF”.
  • End users: End users in the Gemini Alpha program can opt out of this experience when they see the new setting (no sooner than March 11) by visiting their user settings in Meet (gear icon in top right), clicking “Meeting Records” and adjusting the drop-down to “OFF”. If an admin enables the setting for their organization but a user disables the setting, any meeting set by the individual user will have Take notes for me OFF by default.

Rollout pace

  • Rapid Release and Scheduled Release domains:
    • Admin setting: Gradual rollout (up to 15 days for feature visibility) starting on February 18th, 2026
    • New functionality to Gemini Alpha customers: Gradual rollout (up to 15 days for feature visibility) starting no sooner than March 11th, 2026

Availability

  • Business Standard and Plus
  • Enterprise Standard and Plus
  • Google AI Pro for Education add-on
  • Frontline Starter, Standard, and Plus
*Note: This setting may be visible to customers broadly, but it will only be functionable for customers participating in the Gemini Alpha program.

Resources

New user controls for Take notes for me

We are introducing more ways meeting hosts and participants can view and control “Take notes for me” in Google Meet.

When participants join a call in Google Meet, they are first directed to a green room. In the green room, participants now see a more prominent notice when “Take notes for me” is enabled for a meeting they are about to join.

Additionally, eligible users can now turn off "Take notes for me" and transcription directly from the green room before joining a call that has yet to start. If the call has started, users can still stop or start notes at any time during the call.

Getting started

Rollout pace

Availability

  • Business Standard and Plus
  • Enterprise Standard and Plus
  • Google AI Pro for Education
  • Frontline Plus

Resources

Chrome Beta for Desktop Update

The Beta channel has been updated to 146.0.7680.16 for Windows, Mac and Linux.

A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Chrome Release Team
Google Chrome

Announcing Android Google Mobile Ads SDK 25.0.0

Version 25.0.0 of the Android Google Mobile Ads SDK is now available. We recommend upgrading as soon as possible to take advantage of the latest features, performance improvements, and API updates. This is a major version update that includes several breaking changes, new functionality for optimizing banner ad sizes, and important dependency updates.

New Large Anchored Adaptive Banner Size APIs

Unlock better performance with new banner ad sizes:

To better align with modern mobile devices, we are introducing the Large Adaptive Anchor API (e.g. AdSize.getLargeAnchoredAdaptiveBannerAdSize()). This update focuses solely on the sizing logic within adaptive anchor banners. While individual results may vary, larger ads are designed to increase engagement and revenue potential for publishers. The previous anchored adaptive APIs (e.g. AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize()) are now deprecated in favor of the new large anchored adaptive banner approach.

Old usage (Kotlin):

adView.setAdSize(AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize(this, 360))

New usage (Kotlin):

adView.setAdSize(AdSize.getLargeAnchoredAdaptiveBannerAdSize(this, 360))

Breaking Changes and Removals

Version 25.0.0 is a major version with breaking changes that primarily impact mediation adapters and custom events.

API Removals:

  • The VersionInfo class in the com.google.android.gms.ads.mediation package has been removed. Use com.google.android.gms.ads.VersionInfo instead.
  • The deprecated getConfiguration() method in the RtbSignalData class has been removed. Developers should migrate to using getConfigurations() instead.
  • The deprecated onFailure(String) and onAdFailedToShow(String) methods have been removed from the following callback classes:
    • SignalCallbacks
    • MediationAdLoadCallback
    • MediationInterstitialAdCallback
    • MediationRewardedAdCallback
      The replacement methods are onFailure(AdError) and onAdFailedToShow(AdError).
    • The NativeAdViewHolder class has been removed from the com.google.android.gms.ads.nativead package.

For the full list of changes, please refer to the release notes. We strongly encourage you to review our migration guide to ensure your mobile apps are ready to upgrade.

SDK Deprecation Reminder

Per the deprecation schedule, the release of version 25.0.0 means that:

  • Android Google Mobile Ads SDK versions 23.0.0 - 23.6.0 are officially deprecated.
  • Android versions 22.0.0 - 22.6.0 will sunset on June 30, 2026.

We strongly recommend updating to a supported SDK version to avoid any disruption in ad serving and to benefit from the latest SDK features and fixes.

To comment on this blog post or engage with fellow developers, join the Google Mobile Ads SDK Discord channel and share your thoughts.

Keeping Google Play & Android app ecosystems safe in 2025

The Android ecosystem is a thriving global community built on trust, giving billions of users the confidence to download the latest apps. In order to maintain that trust, we’re focused on ensuring that apps do not cause real-world harm, such as malware, financial fraud, hidden subscriptions, and privacy invasions. As bad actors leverage AI to change their tactics and launch increasingly sophisticated attacks, we’ve deepened our investments in AI and real-time defenses over the last year to maintain the upper hand and stop these threats before they reach users.

Upgrading Google Play’s AI-powered, multi-layered user protections

We’ve seen a clear impact from these safety efforts on Google Play. In 2025, we prevented over 1.75 million policy-violating apps from being published on Google Play and banned more than 80,000 bad developer accounts that attempted to publish harmful apps. These figures demonstrate how our proactive protections and push for a more accountable ecosystem are discouraging bad actors from publishing malicious apps, while our new tools help honest developers build compliant apps more easily. Initiatives like developer verification, mandatory pre-review checks, and testing requirements have raised the bar for the Google Play ecosystem, significantly reducing the paths for bad actors to enter.

User safety is at the core of everything we build. Over the years, we’ve continually introduced ways to help users stay safe and make informed app choices — from parental controls to data safety transparency and app badges. We’re constantly improving our policies and protections to encourage safe, high-quality apps on Google Play and stop bad actors before they cause harm.

Apps on Google Play undergo rigorous reviews for safety and compliance with our policies. Last year, we shared that Google Play runs over 10,000 safety checks on every app we publish, and we continue to check and recheck apps after they’ve been published. In 2025, we continued scaling our defenses even further by:

  • Boosting AI-enhanced app detection: We integrated Google’s latest generative AI models into our review process, helping our human review team continue to find complex malicious patterns faster.
  • Preventing unnecessary access to sensitive data: We prevented over 255,000 apps from getting excessive access to sensitive user data and continued to strengthen our privacy policies. Our commitment to privacy-forward app development, supported by tools like Play Policy Insights in Android Studio and Data safety section, has empowered developers to continue to: minimize privacy-sensitive permission requests, and prioritize the user in their design choices.
  • Blocking spam ratings and reviews: Whether they lead to review inflation or deflation, spam ratings and reviews can negatively impact our users’ trust and our developers’ growth. We’re continually evolving our detection models to help ensure app reviews are accurate. Our anti-spam protections blocked 160 million spam ratings and reviews last year, including inflated and deflated reviews. We also prevented an average 0.5-star rating drop for apps targeted by review bombing, protecting our users and developers from unhelpful reviews.
  • Safeguarding kids and families: Our approach to kids and families is built on the core belief that children deserve a safe, enriching digital environment. Our commitment is to empower parents with robust tools while providing children with access to high-quality, age-appropriate content. Last year, we announced new layers of protection, in addition to our existing safeguards, to prevent younger audiences from discovering or downloading apps involving activities like gambling or dating.

Enhancing Google Play Protect to help keep the entire Android ecosystem safe

We also continued to improve our protections for the broader Android ecosystem, by expanding Google Play Protect and real-time security measures like in-call scam protections to help keep users safe from scams, fraud, and other threats.

As Android’s built-in defense against malware and unwanted software, Google Play Protect now scans over 350 billion Android apps daily. This proactive protection constantly checks both Play apps and those from other sources to ensure they are not potentially harmful. And, last year, its real-time scanning capability identified more than 27 million new malicious apps from outside Google Play, warning users or blocking the app to neutralize the threat. To benefit from these protections, we recommend that users always keep Google Play Protect on.

While fraudsters are constantly evolving their tactics, Google Play Protect is evolving faster. Last year, we expanded:

  • Enhanced fraud protection: Google Play Protect’s enhanced fraud protection analyzes and automatically blocks the installation of apps that may abuse sensitive permissions to commit financial fraud. This protection is triggered when a user attempts to install an app from an "Internet-sideloading source" — such as a web browser or messaging app — that requests a sensitive permission. Building on the success of our initial pilot in Singapore, we expanded enhanced fraud protection to 185 markets, now covering more than 2.8 billion Android devices. In 2025, we blocked 266 million risky installation attempts and helped protect users from 872,000 unique, high-risk applications.
  • In-call scam protection: We also introduced new protections to combat social engineering attacks during phone calls. This feature preemptively disables the ability to turn off Google Play Protect during phone calls, stopping bad actors from being able to trick users into disabling their device's built-in defenses to download a malicious app while on a call.

Partnering with developers for a more secure, privacy-friendly future

Keeping Android and Google Play safe requires deep collaboration. We want to thank our global developer community for their partnership and for sharing their feedback on the tools and support they need to succeed.

In 2025, we focused on reducing friction for developers and providing them with tools to safeguard their businesses:

  • Building safer apps more easily: We’re helping developers streamline their work by bringing insights directly into their natural workflows. It starts with Play Policy Insights in Android Studio, which gives developers real-time feedback as they code. We focused first on permissions and APIs that grant deeper system access or handle personal data, like location or photos. This gives developers a head start on policy requirements, including prominent disclosures or usage declarations, while they’re still building. When developers move to Play Console to prepare their apps for submission, our expanded pre-review checks help catch common reasons for rejection, like improper usage of credentials or permissions and broken privacy policy links, ensuring smoother, faster reviews.
  • Stronger threat detection with Play Integrity API: Every day, apps and games make over 20 billion checks with Play Integrity API to protect against abuse and unauthorized access. In 2025, we added hardware-backed signals to make it even harder for bad actors to spoof devices and introduced new in-app prompts that let users fix common issues like network errors without leaving the app. We also launched device recall in beta to help developers identify repeat bad actors even after a device has been reset, all while protecting user privacy.
  • Building trust through developer verification: We’ve seen how effective developer verification is on Google Play, and now we’re applying those lessons to the broader Android ecosystem. By ensuring there is a real, accountable identity behind every app, verification helps legitimize authentic developers and prevents bad actors from hiding behind anonymity to repeatedly cause harm. After gathering feedback during our early access period, we’ll open up verification to all developers this year. We’ve also added a dedicated account type for students and hobbyists, which will allow them to distribute these apps to a limited number of devices without the full verification requirements.
  • Greater security with every Android release: In Android 16, developers can protect users’ most private information, like bank logins, with just one line of code. We’ve integrated this feature automatically to certain apps for an instant security boost against “tapjacking,” a trick where bad apps use hidden layers to steal clicks for ad fraud.

Looking ahead

Our top priority remains making Google Play and Android the most trusted app ecosystems for everyone. This year, we’ll continue to invest in AI-driven defenses to stay ahead of emerging threats and equip Android developers with the tools they need to build apps safely. To empower developers who distribute their apps on Google Play, we’ll maintain our focus on embedding checks to help build apps that are compliant by design, while providing guidance to help proactively avoid policy violations before an app is published. We’ll also roll out Android developer verifications to hold bad actors accountable and prevent them from hiding behind anonymity to cause repeated harm.

Thank you for being part of the Google Play and Android community as we work together to build a safer app ecosystem.