[artifactconf] Github for People Who Don't Code

The document provides guidance on creating and maintaining high-quality PHP packages. It discusses defining quality standards, project structure, testing, documentation, releasing packages, and ongoing maintenance. Key aspects include using semantic versioning, writing automated tests, generating documentation, following best practices for code quality, and being responsive to issues and pull requests. The goal is to create packages that are easily installed, well-maintained, and meet community standards.

The document introduces Architect, a module system for JavaScript applications. It discusses problems that arise when codebases grow large, such as duplicated modules, dependency errors, and long startup times. Architect addresses these by defining each piece of functionality as a plugin that can import other plugins. An application is defined as a set of plugins, allowing modularization and loose coupling between components. Plugins are configured through options and communicate through an event bus. This allows features to be swapped out easily for different implementations, improving testability and flexibility.

This document provides an agenda and overview for a class on using Git, GitHub, and VSCode. It introduces command line basics, files and directories, terminal commands, text editors, GitHub, Git basics, and a homework assignment to create a GitHub repository and JavaScript program. Key topics covered include the Git workflow, essential Git commands, using GitHub Pages to host websites, and an introduction to JavaScript programming.

The document discusses the author's experiences with open source software and free/liberal licensing over his career. It provides an overview of his early encounters with FOSS projects, describes some of the companies and technologies he has worked with that utilize open source, and encourages readers to get involved in their own way through activities like coding, testing, documenting or community participation. The author advocates that open source helps with time to market, cost of development and building ecosystems.

This document discusses the challenges of developing packages before and after the introduction of Composer. Before Composer, packages were tightly coupled to specific frameworks and became incompatible as frameworks evolved. This led to duplication of packages across frameworks. Composer addressed this by allowing packages to be decoupled from frameworks via interfaces and drivers. The document encourages developers to design packages that can integrate with multiple frameworks through bridging packages and drivers to strengthen interoperability and productivity.

Many know of the famous quote, "Premature optimization is the root of all evil," but most people do not know the full quote or understand the context in which optimization is considered evil. As with anything in programming optimization is evil, maybe. Stop using excuses for slow code, and start to think about the places and tools that you can use to optimize. Thankfully there are are many different tools like xhprof, Valgrind, and others to help us out and properly optimize our code for those times when we need to dig deep into our code.

This document summarizes a presentation about using Golang to build smart IM bots. It discusses choosing Golang for its fast performance, concurrency, and tooling. It then provides steps to build Line and Facebook bots using Golang and deploying to Heroku. Examples of pet-care bots are shown. The presentation discusses using LUIS for natural language processing and envisions bots communicating directly without APIs in the future to provide customer service. It also discusses building "right brain" bots and job opportunities.

What visually impaired programmers are thinking about Ruby? http://rubykaigi.org/2017/presentations/nishimotz.html

This is a low-level, and philosophical discussion on the act of compiling data out of your PHP applications using Zend\Code: Scanning, Generating, Annotating code in PHP.

Re-using business logic is key to expanding Domino applications beyond the Notes Client. HCL has introduced the Volt MX LotusScript Toolkit and invites the community to collaborate with us in its development. In this webinar HLC will outline the challenges and explain the design considerations. They will demonstrate and deep dive into the prototype code. See the flexibility beyond just Volt MX. Most importantly, learn how you can get involved to help shape the direction of this open source solution. The speakers will be: Paul Withers - HCL Jason Roy Gary - HCL Rocky Oliver - HCL

When OpenNTF began in 2001, source control was little known and sharing of code via the cloud was limited. Fast forward 20 years and GitHub is the dominant sharing site and git the standard technology for source control. In this webinar Paul Withers and Jesse Gallagher will: Demystify git Explain Branching Show what makes a high quality repository How to take advantage of GitHub’s broad functionality Get that coveted "Verified" badge Go from source control zero to GitHub hero!

This document discusses the suitability of Go for web development. It notes that while Go's built-in HTML template engine is basic, the Gorazor template engine provides a more powerful way to mix Go code into HTML templates. Code generation approaches also allow Go to behave more dynamically at runtime. Go's fast compilation and use of interfaces make it well-suited for dynamic web applications and large websites. The document concludes that while other languages may be more mature, Go is suitable for developing large, stable, scalable websites that need to be maintained over time.

If you create Joomla! extensions you have to do some not complicated but time consuming tasks. It is easy to make a mistake and you have to start over again. I'll show how I have setup my environment and how this is integrated in the development process and package creating process. You can learn how a tool like phing can make you life easier.

You've got some awesome code that you've written, which you want to share with the community. Sure, you could simply post it on GitHub and be done with it, but is that the best way to share your work? What are the additional steps needed to share your code in a way that it will actually get used by the larger world? I'll discuss options for hosting , licensing, versioning, packaging, documenting, building, testing and even contributing to your code. All the things that will make someone else say - I want to use this!

Don't be a git - the essentials you should know about git to use it correctly Presentation by Otto Kekäläinen held at Vincit Teatime on Nov 11th 2015 http://www.vincitteatime.fi/

This document provides an overview of Jenkins Pipeline, including what it is, how to get started, best practices, and advanced features. Pipeline allows configuring Jenkins jobs using code instead of the UI. Jobs are defined with Groovy scripts that can leverage features like branches, libraries, variables, and more. The document covers pipeline syntax, working with source control, error handling, testing scripts, and customizing build reporting. It emphasizes code review, simplicity, and avoiding inefficient practices that could impact the master node.

This document provides an agenda and overview for a class on search engine optimization (SEO). It reviews the previous class, discusses upcoming projects that students can choose to work on, and covers the history and mechanics of SEO, including on-page and off-page factors. Students are instructed on using tools like Google Analytics and GitHub for SEO tasks and source code management. Homework involves analyzing and suggesting improvements to a website based on SEO best practices.

The document summarizes the Open Authentication initiative (OATH), which aims to drive adoption of open strong authentication standards. OATH has created standardized authentication algorithms like HOTP and works with members to promote interoperability. Its reference architecture provides guidance for integrating strong authentication into applications while balancing security, usability and choice. OATH also works on credential provisioning standards and certification programs to further authentication adoption.

카카오팬 보안OTP가이드 입니다.

비대면인증 핀테크 쇼케이스

Giuseppe Paternò is a visiting researcher at Trinity College Dublin who discusses creating one time password (OTP) infrastructures using open source software. He describes how the Open Authentication (OATH) Alliance created a common HMAC-Based One Time Password (HOTP) algorithm standard to facilitate two-factor authentication across different implementations. Paternò then demonstrates an OTP infrastructure using the open source OTPD server, FreeRADIUS server, and soft token clients, allowing authentication for systems like wireless networks, VPNs, and web applications through standards like RADIUS and CAS.

Software Engineering 수업을 들으며 과제로 수행해야 하는 핀테크 기업 3종 조사 과제 자료입니다. 트랜스퍼와이즈, 커런시 클라우드, 토스를 조사하였습니다.

3주차 강의

Linux containers are different from Solaris Zones or BSD Jails: they use discrete kernel features like cgroups, namespaces, SELinux, and more. We will describe those mechanisms in depth, as well as demo how to put them together to produce a container. We will also highlight how different container runtimes compare to each other.

I have evidence that using git and GitHub for documentation and community doc techniques can give us 300 doc changes in a month. I’ve bet my career on these methods and I want to share with you.

The document discusses challenges with application lifecycle management (ALM) and recommends adopting agile practices like Scrum and Kanban to improve project predictability, lower costs, and increase team responsiveness. It emphasizes establishing continuous integration using automated testing, version control like Git, and configuration management. Adopting practices like test-driven development, behavior-driven development, and continuous integration can help address typical ALM problems like lack of visibility, ineffective communication, undefined requirements, and inadequate testing.

This document provides an agenda and overview for a class on using Git, GitHub, and VSCode. It introduces command line basics, files and directories, terminal commands, text editors, GitHub, Git basics, and a homework assignment to create a GitHub repository and JavaScript program. Key topics covered include the Git workflow, essential Git commands, using GitHub Pages, and an introduction to JavaScript programming.

This document provides an overview of version control with Git. It explains what version control and Git are, how to install and configure Git, how to perform basic tasks like initializing a repository and making commits, and how to collaborate using features like branching and pushing/pulling from remote repositories. Key points covered include allowing the tracking of changes, maintaining file history, and enabling multiple people to work on the same project simultaneously without conflicts.

This document provides an introduction to using Git and GitHub for version control and collaboration. It discusses problems with traditional version control methods, how Git addresses these problems, and basic Git workflows and commands like add, commit, push, pull, clone and status. GitHub is introduced as the largest host for Git repositories with social and project management features. The document then provides a simplified example of collaboratively writing children's stories using Git and GitHub to demonstrate basic concepts and workflows.

The document provides an overview of Git and GitHub. It discusses that Git keeps track of changes to code, synchronizes code between people, allows testing changes without losing the original, and reverting to old versions. It then covers Git commands like clone, add, commit, push, pull, status, log, reset, branch, and merge. Branching allows creating versions of the repository with their own histories. Pull requests are used to merge branches with the main code.

Git is a version control system that allows developers to track changes to files over time. It is distributed, meaning developers have their own local copy of the code repository. This allows working offline and merging changes. Common Git commands include git add to stage changes, git commit to save changes locally, and git push to upload changes to the remote repository. Tagging specific versions with git tag allows easy deployment of code.

This document provides an introduction to using Git. It discusses key Git concepts like commits, branches, repositories, cloning, pushing and pulling. It recommends always using the command line for hands-on practice. It also provides examples of common Git commands and best practices for commits, branching strategies, and release strategies.

Git is a version control system that allows developers to have multiple versions of codebases and easily revert changes. Github is a website that hosts git repositories on remote servers, facilitating code sharing among teams through a graphical user interface. The document provides instructions on configuring git and connecting it to Github repositories, as well as describing basic workflows for branching, merging, rebasing, and resolving conflicts when integrating changes.

Git is a version control system that allows developers to have multiple versions of codebases and easily revert changes. Github is a website that hosts git repositories on remote servers, facilitating code sharing among teams through a graphical user interface. The document provides instructions on configuring git and connecting it to Github repositories, as well as describing basic workflows for branching, merging, rebasing, and resolving conflicts when integrating changes.

The iOS team at The Washington Post needed to grow quickly and maintain sanity (and shipping quality). Here are some of the key workflow tools that we used.

Git and GitHub are tools that software engineers use to collaborate on code and track changes over time. While primarily for software development, GitHub can also be used as a project management tool for any team. Key terms used in GitHub include repositories (folders for projects), branches (versions of code), commits (changes to code), and pull requests (requests to merge changes). As a non-technical professional, understanding these basic GitHub concepts and being able to engage teams there will help facilitate communication and progress on shared work. The document recommends following specific repositories at the company to stay informed on relevant projects.

An introductory course to Git and GitHub that I presented as a 2.5 hour class for Girls Develop IT Ottawa on April 12, 2012

The document provides instructions on how to use Git and GitHub for version control and collaboration. It begins with an example scenario that illustrates issues with sharing code between developers without proper version control. It then introduces Git as a version control system that allows tracking changes to code through branches and commits. The document walks through setting up GitHub accounts and repositories, making commits locally and pushing them to a remote repository, and collaborating through pull requests. It also demonstrates common Git commands like cloning, branching, adding/committing, and pushing.

Slides from a lightning talk at WordPress Melbourne User Group. The business end was a simple demonstration of SourceTree, no commandline :)

A revised/minimized version of Nick Quaranto's (http://www.slideshare.net/qrush ) presentation on the same topic. This revised version was used to present Git to a group of students at ECPI who were not yet familiar with the concepts of version control or Git.

Git is a mystery to many of us, but with a few techniques you can transform how you use it, making the best of working in teams or in open source projects.

In one of our weekly training, we’ve talked about Git. Here is a quick overview of the main concepts, basic commands and branching strategy, how to work with Git, how to contribute to an OSS project, …

This document discusses how to use GitHub to organize projects. It explains that GitHub is a distributed version control system and hosting service that allows users to track changes, collaborate on projects, and manage workflows. The document provides an overview of basic Git commands like add, commit, push, and pull and demonstrates uploading a local folder to a GitHub repository. It recommends GitHub as a way to solve common development pain points like organization and project management.

In this talk, Teehan+Lax developer Ash Furrow will guide designers through the basics of GitHub. He’ll discuss why GitHub is important and teach you the high-level concepts that will get you started with GitHub today.

This document discusses best practices for using color in web design to ensure accessibility and avoid accessibility issues related to color contrast. It provides an overview of color theory terms, different color schemes, and examples of how top companies use color on their websites. It also reviews guidelines for sufficient color contrast from the WCAG and tools for checking color contrast. The key recommendations are to use color thoughtfully following principles of contrast and accessibility, apply sufficient contrast ratios to all elements, and proactively test color accessibility.

Smartphones and tablets not only contain more computing power and better browsers than the computers that started the Internet economy. They also have better displays, which demands more of us when we use images. This session will work through tips and tricks to develop future friendly images in our sites and apps.

The document discusses adaptive images and responsive web design. It covers using srcset and sizes attributes, the <picture> element, and feature testing versus browser sniffing to determine the best image to display based on factors like screen width, resolution, and bandwidth. It also discusses workarounds like background-size, SVG, and font-based solutions for responsive images.

The web doesn't stop at the desktop anymore. Our image assets need to do more than look good in one context. In this talk, I look at how images like JPEG, GIFs, SVG, Icons, Unicode, and more can be used in a multi-device environment.

The document summarizes Christopher Schmitt's presentation at RWD Summit 2014 on adaptive images in responsive web design. It discusses using feature testing over browser sniffing to determine screen resolution and bandwidth. It presents techniques like srcset, picture, and JavaScript solutions to serve appropriately sized images. It also covers workarounds like background-size, SVG, and font-based solutions when native techniques are not supported. The focus is on building responsive images that scale with the device and load quickly.

This document summarizes Christopher Schmitt's presentation on adaptive images in responsive web design. The presentation covered: 1. Using the browser width, screen resolution, and bandwidth to determine the appropriate image to serve through feature testing rather than browser sniffing. 2. Techniques for serving responsive images including using .htaccess files, the <picture> element, and JavaScript libraries like HiSRC that select images based on various tests. 3. Workarounds for older browsers including using background-size: 100%, SVG images, and font-based solutions.

This document discusses responsive images and various techniques for implementing responsive images, including: 1. Using .htaccess files to serve different image sizes based on screen resolution. 2. Implementing the <picture> element and srcset attribute to serve different image sources based on media queries. 3. Using JavaScript solutions like HiSRC to programmatically swap image sources based on screen properties like pixel density and connection speed. 4. Various workarounds and tricks for responsive images, including using background-size: 100% for images, optimizing images as SVGs, and using font-based solutions.

This document summarizes Christopher Schmitt's presentation on adaptive images in responsive web design. The presentation discusses: 1) Using feature testing and media queries to determine screen width and resolution instead of browser sniffing 2) Techniques for serving adaptive images, including .htaccess redirects, srcset, picture, and JavaScript libraries 3) Workarounds like background-size: 100% and SVG when native image solutions don't work

This document summarizes Christopher Schmitt's presentation on adaptive images in responsive web design. It discusses using feature testing versus browser sniffing to determine the appropriate image to serve, including testing browser width, screen resolution, and bandwidth. It then covers various techniques for serving adaptive images, such as using .htaccess files, the <picture> element, srcset attributes, and JavaScript libraries. It emphasizes using a mobile-first approach and progressive enhancement to provide the best experience for all devices.

This document discusses techniques for responsive images on the web. It begins by explaining how to use browser width, screen resolution, and bandwidth detection to serve appropriately sized images. It then discusses .htaccess and JavaScript solutions like Filament Group's responsive images and HiSRC. It argues that CSS media queries are best for layout, while these techniques focus on images. Background-size, SVG, and Modernizr checks are presented as workarounds. Overall, the document provides an overview of different responsive image implementation strategies.

The document discusses adaptive images in responsive web design. It covers using the browser's user agent string and feature testing to determine screen resolution and bandwidth instead of browser sniffing. Methods presented include using viewport width with JavaScript, jQuery, and CSS media queries; checking screen resolution directly and considering retina displays; and avoiding bandwidth speed tests. Workarounds discussed are using background-size: 100% with images, SVG, and a "Clown Car" SVG technique loading different image files via CSS media queries.

Christopher Schmitt presented on adaptive images in responsive web design. He discussed using browser features like width, resolution and bandwidth to determine the best image to serve rather than browser sniffing. Feature testing methods included JavaScript, jQuery and CSS media queries. Workarounds for older browsers included background images, SVGs and font-based solutions. Compressed JPEG images were also suggested to reduce file sizes.

The document discusses adaptive images in responsive web design. It covers techniques like using the browser width and screen resolution to determine the appropriate image size via JavaScript or media queries. It also discusses checking bandwidth and using techniques like picture, srcset, .htaccess rewriting, and single pixel GIFs to serve the right image. The document recommends using CSS media queries for design and covers workaround techniques like background-size, SVG, and font-based solutions.

The document discusses how GitHub can be used by non-technical people. It provides an overview of version control and Git basics such as forking a repository, making commits, and merging changes. It also covers how to set up Git on your local machine and connect to GitHub to share code. GitHub features like issues, milestones, apps and Pages are mentioned. An example is given of its use on President Obama's 2012 reelection campaign with 240 code repositories.

This document discusses adaptive images in responsive web design. It begins by introducing the speaker, Christopher Schmitt, and his credentials. It then explores using the browser's user agent string and feature detection to determine screen resolution and bandwidth rather than browser sniffing. The document discusses using CSS media queries, jQuery, and the picture element to serve adaptive images. It also proposes some workaround techniques like background sizing and SVG to improve responsive images.

1. The document discusses various techniques for implementing adaptive images in responsive web design, including using the browser's user agent string, feature testing dimensions with JavaScript, and CSS media queries. 2. It describes approaches like modifying .htaccess files and using the <picture> element to serve different image sizes, as well as libraries that simplify the process like HiSRC. 3. Workarounds discussed include using background images, SVG images, font-based solutions, and compressed JPEG files to improve performance on different devices.

This document discusses various techniques for responsive images in web design, including browser sniffing versus feature testing, image sizes for different screen resolutions and bandwidths, and different implementation methods like .htaccess files, the <picture> element, and JavaScript libraries. It covers topics like using the browser width to determine layouts, screen resolution detection, and bandwidth testing. Workarounds discussed include using background images, SVGs, icon fonts, and compressed JPEGs. The document advocates a mobile-first approach and using CSS media queries to adapt designs based on screen size.

The document appears to be a presentation about designing web and mobile graphics. It discusses using different sized image assets and the <picture> element to serve the optimal image based on screen size. It shows examples of image sizes for different screen densities and dimensions. It also discusses compressing images to reduce file size while maintaining quality.

This document discusses HTML5 and CSS3 and whether they are ready for mainstream use. It provides an overview of the new HTML5 elements like <header>, <nav>, <section>, <article>, <aside>, and <footer>. It also covers HTML5 video and audio capabilities and supporting different video codecs. The document recommends tools for encoding video files into supported formats and discusses using text tracks for basic captioning support.

Slides from my talk at HTML5tx 2013. Thanks to all the staff and volunteers at HTML5tx for putting on the event!

Everything that I found interesting last month about the irresponsible use of machine intelligence

Profile portofolio

In the modern digital era, social media platforms have become integral to our daily lives. These platforms, including Facebook, Instagram, WhatsApp, and Snapchat, offer countless ways to connect, share, and communicate.

Widya Salim and Victor Ma will outline the causal impact analysis, framework, and key learnings used to quantify the impact of reducing Twitter's network latency.

Manual Method of Product Research | Helium10 | MBS RETRIEVER

Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data. The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs. Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution! Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.

Is your patent a vanity piece of paper for your office wall? Or is it a reliable, defendable, assertable, property right? The difference is often quality. Is your patent simply a transactional cost and a large pile of legal bills for your startup? Or is it a leverageable asset worthy of attracting precious investment dollars, worth its cost in multiples of valuation? The difference is often quality. Is your patent application only good enough to get through the examination process? Or has it been crafted to stand the tests of time and varied audiences if you later need to assert that document against an infringer, find yourself litigating with it in an Article 3 Court at the hands of a judge and jury, God forbid, end up having to defend its validity at the PTAB, or even needing to use it to block pirated imports at the International Trade Commission? The difference is often quality. Quality will be our focus for a good chunk of the remainder of this season. What goes into a quality patent, and where possible, how do you get it without breaking the bank? ** Episode Overview ** In this first episode of our quality series, Kristen Hansen and the panel discuss: ⦿ What do we mean when we say patent quality? ⦿ Why is patent quality important? ⦿ How to balance quality and budget ⦿ The importance of searching, continuations, and draftsperson domain expertise ⦿ Very practical tips, tricks, examples, and Kristen’s Musts for drafting quality applications https://www.aurorapatents.com/patently-strategic-podcast.html

Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)

This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator. Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/ Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.

Revolutionize your transportation processes with our cutting-edge RPA software. Automate repetitive tasks, reduce costs, and enhance efficiency in the logistics sector with our advanced solutions.

Java Servlet programs

Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023 https://arxiv.org/abs/2307.12980

Presented at Gartner Data & Analytics, London Maty 2024. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Join this session to hear their story, the lessons they learned along the way and how their future innovation plans include the exploration of uses of EKG + Generative AI.

Everything that I found interesting about engineering leadership last month

Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.

Support en anglais diffusé lors de l'événement 100% IA organisé dans les locaux parisiens d'Iguane Solutions, le mardi 2 juillet 2024 : - Présentation de notre plateforme IA plug and play : ses fonctionnalités avancées, telles que son interface utilisateur intuitive, son copilot puissant et des outils de monitoring performants. - REX client : Cyril Janssens, CTO d’ easybourse, partage son expérience d’utilisation de notre plateforme IA plug & play.

An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)

Everything that I found interesting about machines behaving intelligently during June 2024

Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge. You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter. The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.

Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk. What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year? Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year. This webinar will review: - Key changes to privacy regulations in 2024 - Key themes in privacy and data governance in 2024 - How to maximize your privacy program in the second half of 2024