url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://www.atlassian.com/de/software/jira/service-management/features/asset-and-configuration-management | Asset- und Konfigurationsmanagement mit Jira | Atlassian Close Diese Seite in deiner Sprache anzeigen? Alle Sprachen Sprache auswählen 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Kostenlos nutzen Service Collection-Apps Jira Service Management Kundenservicemanagement Assets Service Collection Back Preise Mehr + Weniger - Kostenlos nutzen Back Kostenlos nutzen Asset- und Konfigurationsmanagement Assets bietet einen Überblick über Abhängigkeiten, damit du Assets und Konfigurationselemente problemlos verwalten, Vorfälle schnell beheben und das mit Änderungen verbundene Risiko reduzieren kannst. Jetzt testen Einführung in Assets Video ansehen Der Ort für deine wichtigen Daten Im Gegensatz zu älteren Datenbanken bietet Assets eine flexible und offene Datenstruktur, sodass Teams wichtige Ressourcen verwalten und mit Anfragen, Vorfällen, Änderungen und mehr verknüpfen können. Assets nachverfolgen Von Hardware, Software und Konfigurationselementen bis hin zu Personen, Klavieren und Fischen (wirklich) kannst du alle Assets deines Unternehmens in einer flexiblen Datenbank zusammenführen. Dank vorgefertigter Vorlagen kannst du schnell loslegen. Assets mit Arbeit verbinden Verknüpfe Objekte in Assets mit Support-Tickets, Vorfallsvorgängen, Änderungsanfragen und mehr. Verbessere die Sichtbarkeit und beschleunige die Arbeit für alle Arten von Anwendungsfällen in der IT, in HR, im Gebäudemanagement und darüber hinaus. Bessere Entscheidungen Verschaffe dir volle Transparenz und Kontrolle über Assets, um Risiken zu reduzieren und Betriebsabläufe zu verbessern – jetzt mit neuen, flexiblen Berichten und Dashboards für noch genauere Einblicke und intelligentere, schnellere Entscheidungen. Vollständige, aktuelle und korrekte Daten in Assets bereitstellen Assets Data Manager vereinfacht die Integration, den Abgleich und die Analyse von Daten aus mehreren Quellen und versorgt dich mit zuverlässigen Daten für kluge Entscheidungen. Mehr erfahren Features im Asset- und Konfigurationsmanagement Automatisierung Du musst nicht mehr nach Besitzern suchen oder Tabellen aktualisieren. Automatisiere Eingaben aus Jira-Vorgängen, damit wichtige Infos zu deinen Assets aktuell bleiben. Abfragen Du kannst Abfragen zu Objekten in Assets ausführen, um Audits durchzuführen, die Kosten im Griff zu behalten und den Ursachen von Problemen auf den Grund zu gehen. Vorlagen Mit vordefinierten Schemavorlagen kannst du direkt loslegen, um deine Datenbank für häufige Anwendungsfälle in der IT, im Gebäudemanagement, in HR und mehr zu strukturieren. Discovery Erkenne IP-basierte Assets, extrahiere Informationen über wichtige Attribute und Abhängigkeiten und verfolge alle Änderungen, um auf dem Laufenden zu bleiben. Integrationen Nutze über 30 Adapter, einschließlich Flatfiles und SQL-Datenbanken, um wichtige Daten nahtlos in Assets zu übertragen. Berichtfunktion Erhalte verwertbare Einblicke aus deinen Assets, um den Zustand deiner Assets zu überwachen, Compliance-Lücken und Sicherheitsrisiken zu erkennen und auf wichtige Finanzdaten zuzugreifen. "Assets ist unglaublich wichtig für die Prognostizierbarkeit und die Planung von Softwarelizenzen und Kosten." Damir Prusac VP of Engineering bei Infobip Mehr anzeigen FAQ Worin unterscheiden sich Assets in Jira Service Management Cloud, Data Center und in der Assets-App? In dieser Vergleichstabelle kannst du einen genaueren Blick auf die Assets-Funktionen der jeweiligen Tarife werfen. Kann Assets mit Jira-Bereichen verwendet werden? Ja, Objekte in Assets können mit Jira-Vorgängen verknüpft werden. Du benötigst lediglich eine aktive Lizenz für Service Collection Standard oder höher in derselben Instanz. Warum sollte ich von einem anderen CMDB-/Asset-Management-Tool wechseln? Vorteile der Verschiebung deiner CMDB nach Assets (App in der Service Collection): Du kannst deine Aufgaben optimieren, da alle CMDB- und ITSM-Daten (Anfragen, Vorfälle, Änderungen und Probleme) in einem Tool zu finden sind. Du kannst mehr Kontext für Assets und Konfigurationselemente sowie für Vorfälle und Änderungen bereitstellen. So können deine DevOps-Teams die Problemursache schneller finden, Risiken besser managen und damit für reibungslose Deployments sorgen. Du zahlst weniger, da andere CMDB-Anbieter teuer sind. Erhöhe die Flexibilität, jede Art von Inventar, Asset oder Datensatz zu speichern – ohne Einschränkungen oder Beschränkungen auf reine IT-Anwendungsfälle. Bietet Atlassian ein Tool zur Asset-Erkennung? Ja, wir bieten grundlegende Erkennungsfunktionen, um Assets und Konfigurationselemente zu erkennen, die mit deinem lokalen Netzwerk verbunden sind, und detaillierte Infos zu jedem Asset zu extrahieren. Wir bieten auch Integrationen mit führenden Erkennungslösungen wie Lansweeper und Flexera an, damit du Geräte finden und in die Assets-App importieren kannst. Wie werden Daten in Assets importiert? Bei Assets haben Benutzer die Möglichkeit, Data Manager und seine native Schemaimportfunktion zu nutzen. Hier erfährst du mehr: Weitere Informationen zu Assets Data Manager Weitere Informationen zu Adaptern Einrichtung von Assets Data Manager Verschiebung von Daten nach Data Manager, um Rohdaten zu erstellen Entfernung nicht benötigter Werte, um transformierte Daten zu erstellen Entfernung nicht benötigter Datensätze, um die Daten zu bereinigen Abgleich der Datenquellen, um Data Manager-Objekte zu erstellen Import in ein Assets-Schema, um Schemaobjekte zu erstellen Was kann in Assets gespeichert werden? Alles. Im Ernst. Herkömmliche IT-Assets wie Hardware? ✅ Konfigurationselemente? ✅ Personendaten? ✅ Fische? Wenn es für dich wichtig ist, ist es auch für uns wichtig ✅ Assets passt sich flexibel deinen Bedürfnissen an. Erstelle einfach deine gewünschten Objekttypen und Schemas, und schon bist du auf dem richtigen Weg. Jira Asset-Management: Ressourcen für das Asset- und Konfigurationsmanagement Demo Wie verwalte ich Inventar in Assets? Demo ansehen White Paper Asset- und Konfigurationsmanagement-Handbuch für ITSM Mehr erfahren E-Book The Asset Evolution: ein intelligenterer Ansatz, um geschäftlichen Wert zu schaffen Mehr erfahren Intelligente Entscheidungen beginnen mit zuverlässigen Asset-Daten Kostenlos testen Unternehmen Karriere Veranstaltungen Blogs Investor Relations Atlassian Foundation Presse-Kit Kontakt Produkte Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Alle Produkte anzeigen Resourcen Technischer Support Kauf und Lizenzierung Atlassian Community Wissensdatenbank Marketplace Mein Konto Support-Ticket erstellen Lernen Partner Training und Zertifizierung Dokumentation Ressourcen für Entwickler Enterprise Services Alle Ressourcen anzeigen Copyright © 2025 Atlassian Datenschutzrichtlinie Nutzungsbedingungen Impressum Sprache wählen Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://opensource.google/documentation/guides/security-guides | Security Guides | Google Open Source Skip to main content Events Projects Programs and services Organizations we support Documentation About Blog / Sign in Documentation Overview Reference Guides Policies Publications OSS CNA Events Projects Programs and services More Documentation Overview Reference Guides Policies Publications OSS CNA About Blog Maintainer Guides Security guides Organizations we support Google Open Source Documentation Guides Security Guides Stay organized with collections Save and categorize content based on your preferences. CVD An open source version of Google's guide to coordinated vulnerability disclosure for open source projects, including templates for security policies (security.md) and disclosure notifications, is available at https://github.com/google/oss-vulnerability-guide . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2022-10-21 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2022-10-21 UTC."],[],[]] YouTube X LinkedIn Terms Privacy Manage cookies | 2026-01-13T09:29:40 |
https://www.atlassian.com/ja/software/guard/capabilities | Atlassian Guard - 製品の機能 | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 無料で試す 機能 価格 ガイド デモ その他 + 表示を減らす - 無料で試す Back 無料で試す Guard の実践でアトラシアンのクラウド セキュリティの未来を探る – 限定セッション、カスタマー パネル、ライブ デモ。 今すぐ予約 → 必要なセキュリティのために求める機能 最も貴重なアセットを保護するために Atlassian Guard を導入しましょう 無料で試す データ損失からプロアクティブに保護する プランを比較する 高度な認証が必要 複数のポリシーを設定して、管理対象ユーザーと外部ユーザーのコントロールを強化します。 チームの作業を保護する 分散したチーム全体でシングル サインオンとモバイル アプリ管理を実施します。 ミッションクリティカルなデータを特定 Premium データを分類して、データ損失のリスクを軽減します。 高度な認証が必要 複数のポリシーを設定して、管理対象ユーザーと外部ユーザーのコントロールを強化します。 チームの作業を保護する 分散したチーム全体でシングル サインオンとモバイル アプリ管理を実施します。 ミッションクリティカルなデータを特定 Premium データを分類して、データ損失のリスクを軽減します。 不審なアクティビティやデータの悪用を検知する プランを比較する 異常な行動を発見する 監査ログを使用して、Atlassian クラウド全体のアクティビティを調査します。 シャドー IT リスクを削減する 自動プロダクト ディスカバリー機能で、認可されていないアトラシアン製品を特定します。 リスクの高い脅威を優先する Premium カスタマイズ可能な検出ルールとアラートで、リスクをすばやく把握できます。 異常な行動を発見する 監査ログを使用して、Atlassian クラウド全体のアクティビティを調査します。 シャドー IT リスクを削減する 自動プロダクト ディスカバリー機能で、認可されていないアトラシアン製品を特定します。 リスクの高い脅威を優先する Premium カスタマイズ可能な検出ルールとアラートで、リスクをすばやく把握できます。 異常な行動を発見する 監査ログを使用して、Atlassian クラウド全体のアクティビティを調査します。 シャドー IT リスクを削減する 自動プロダクト ディスカバリー機能で、認可されていないアトラシアン製品を特定します。 リスクの高い脅威を優先する Premium カスタマイズ可能な検出ルールとアラートで、リスクをすばやく把握できます。 脅威がインシデントになる前に対応する プランを比較する アラートを 1 つのビューに一元化 Premium ページのエクスポート、不審なログインなどのユーザー アクションを一元的に表示できます。 インシデント対応を迅速化 Premium SIEM の統合により、潜在的な脅威を数分でセキュリティ チームに通知します。 脅威を効率的に排除する Premium 脅威が検出されたときに、アカウントの一時停止など、提案される修復措置に基づいて対応できます。 アラートを 1 つのビューに一元化 Premium ページのエクスポート、不審なログインなどのユーザー アクションを一元的に表示できます。 インシデント対応を迅速化 Premium SIEM の統合により、潜在的な脅威を数分でセキュリティ チームに通知します。 脅威を効率的に排除する Premium 脅威が検出されたときに、アカウントの一時停止など、提案される解決策に基づいて対応できます。 データ損失からプロアクティブに保護する 高度な認証が必要 複数のポリシーを設定して、管理対象ユーザーと外部ユーザーのコントロールを強化します。 安全なチーム コラボレーション 分散したチーム全体でシングル サインオンとモバイル アプリ管理を実施します。 ミッションクリティカルなデータを特定 データを分類して、データ損失のリスクを軽減します。 プランを比較する 不審なアクティビティを検出して調査する 異常な行動を発見する 監査ログを使用して、アトラシアンのクラウド全体の管理者アクティビティを調査します。 シャドー IT リスクを削減する 自動プロダクト ディスカバリー機能で、認可されていないアトラシアン製品を特定します。 リスクの高い脅威を優先する カスタマイズ可能な検出ルールとアラートで、リスクをすばやく把握できます。 プランを比較する 脅威がインシデントになる前に対応する アラートの可視性を一元化する ページのエクスポート、不審なログインなどのユーザー アクションを一元的に表示できます。 インシデント対応を迅速化 SIEM の統合により、潜在的な脅威を数分でセキュリティ チームに通知します。 脅威を効率的に排除する 脅威が検出されたときに、アカウントの一時停止など、提案される解決策に基づいて対応できます。 プランを比較する Guard を開始する Guard を 30 日間無料でお試しください。 無料トライアルを開始 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://huggingface.co/ahmedsqrd/olmo-7b-hf-step0 | ahmedsqrd/olmo-7b-hf-step0 · Hugging Face Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up ahmedsqrd / olmo-7b-hf-step0 like 0 Text Generation Transformers Safetensors olmo arxiv: 1910.09700 Model card Files Files and versions xet Community Deploy Use this model Model Card for Model ID Model Details Model Description Model Sources [optional] Uses Direct Use Downstream Use [optional] Out-of-Scope Use Bias, Risks, and Limitations Recommendations How to Get Started with the Model Training Details Training Data Training Procedure Evaluation Testing Data, Factors & Metrics Results Model Examination [optional] Environmental Impact Technical Specifications [optional] Model Architecture and Objective Compute Infrastructure Citation [optional] Glossary [optional] More Information [optional] Model Card Authors [optional] Model Card Contact Model Card for Model ID Model Details Model Description This is the model card of a 🤗 transformers model that has been pushed on the Hub. This model card has been automatically generated. Developed by: [More Information Needed] Funded by [optional]: [More Information Needed] Shared by [optional]: [More Information Needed] Model type: [More Information Needed] Language(s) (NLP): [More Information Needed] License: [More Information Needed] Finetuned from model [optional]: [More Information Needed] Model Sources [optional] Repository: [More Information Needed] Paper [optional]: [More Information Needed] Demo [optional]: [More Information Needed] Uses Direct Use [More Information Needed] Downstream Use [optional] [More Information Needed] Out-of-Scope Use [More Information Needed] Bias, Risks, and Limitations [More Information Needed] Recommendations Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations. How to Get Started with the Model Use the code below to get started with the model. [More Information Needed] Training Details Training Data [More Information Needed] Training Procedure Preprocessing [optional] [More Information Needed] Training Hyperparameters Training regime: [More Information Needed] Speeds, Sizes, Times [optional] [More Information Needed] Evaluation Testing Data, Factors & Metrics Testing Data [More Information Needed] Factors [More Information Needed] Metrics [More Information Needed] Results [More Information Needed] Summary Model Examination [optional] [More Information Needed] Environmental Impact Carbon emissions can be estimated using the Machine Learning Impact calculator presented in Lacoste et al. (2019) . Hardware Type: [More Information Needed] Hours used: [More Information Needed] Cloud Provider: [More Information Needed] Compute Region: [More Information Needed] Carbon Emitted: [More Information Needed] Technical Specifications [optional] Model Architecture and Objective [More Information Needed] Compute Infrastructure [More Information Needed] Hardware [More Information Needed] Software [More Information Needed] Citation [optional] BibTeX: [More Information Needed] APA: [More Information Needed] Glossary [optional] [More Information Needed] More Information [optional] [More Information Needed] Model Card Authors [optional] [More Information Needed] Model Card Contact [More Information Needed] Downloads last month 2 Safetensors Model size 7B params Tensor type F32 · Files info Inference Providers NEW Text Generation This model isn't deployed by any Inference Provider. 🙋 Ask for provider support Paper for ahmedsqrd/olmo-7b-hf-step0 Quantifying the Carbon Emissions of Machine Learning Paper • 1910.09700 • Published Oct 21, 2019 • 24 System theme Company TOS Privacy About Careers Website Models Datasets Spaces Pricing Docs | 2026-01-13T09:29:40 |
https://git-scm.com/book/be/v2/Distributed-Git-Summary | Git - Summary About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.4 Distributed Git - Summary Summary You should feel fairly comfortable contributing to a project in Git as well as maintaining your own project or integrating other users' contributions. Congratulations on being an effective Git developer! In the next chapter, you’ll learn about how to use the largest and most popular Git hosting service, GitHub. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://support.microsoft.com/he-il/onenote | עזרה ולימוד של OneNote דלג לתוכן הראשי Microsoft תמיכה תמיכה תמיכה דף הבית Microsoft 365 Office מוצרים Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows עוד... מכשירים Surface אביזרי PC Xbox משחקי מחשב HoloLens Surface Hub כתבי אחריות של חומרה חשבון & וחיוב חשבון חנות Microsoft וחיוב משאבים Install Microsoft 365 Community forums מנהלי מערכת של Microsoft 365 פורטל לעסקים קטנים מפתח חינוך ווח על הונאה בתמיכה בטיחות מוצר עוד קנה את Microsoft 365 כל Microsoft Global Microsoft 365 Teams Copilot Windows Xbox תמיכה תוכנה תוכנה אפליקציות של Windows AI OneDrive Outlook עוברים מ- Skype ל-Teams OneNote Microsoft Teams מחשבים והתקנים מחשבים והתקנים קנה Xbox חומרה בידור בידור Xbox Game Pass Ultimate Xbox משחקי מחשב לעסקים לעסקים האבטחה של Microsoft Azure Dynamics 365 Microsoft 365 לעסקים Microsoft Industry Microsoft Power Platform Windows 365 מפתח ו-IT מפתח ו-IT מפתח של Microsoft Microsoft Learn תמיכה באפליקציות השוק של AI קהילת Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards אחרים אחרים הורדות בחינם ואבטחה חינוך כרטיסי מתנה הצג את מפת האתר חיפוש חיפוש עזרה אין תוצאות ביטול היכנס היכנס דרך Microsoft היכנס או צור חשבון. שלום, בחר חשבון אחר. יש לך חשבונות מרובים בחר את החשבון שברצונך להיכנס באמצעותו. עזרה ולימוד של OneNote התחל בעבודה רשום הערות עיצוב הערות ציור ושרטוט שיתוף וסינכרון שמירה על הסדר פתרון בעיות הגדל את הפרודוקטיביות שלך בעזרת העוצמה של בינה מלאכותית סכם את הערות OneNote שלך באמצעות Microsoft 365 Copilot יצירת רשימת משימות לביצוע ומשימות ב- OneNote באמצעות Copilot יצירת תוכניות פרויקט באמצעות Copilot ב- OneNote קבל תכונות המבוססות על בינה מלאכותית ב- Microsoft 365 קנה את Microsoft 365 סיור ב- OneNote רישום הערות הקלד או כתוב הערות או הקלט הערות שמע ב- OneNote. למד כיצד לרשום הערות ב- OneNote ציור ושרטוט עורר את ההערות שלך לחיים על-ידי ציור ושרטוט ב- OneNote. למד כיצד לצייר ב- OneNote האם אתה עסק קטן? בקר בדף העזרה והלמידה של עסקים קטנים קטן כדי ללמוד כיצד תוכל להשתמש ב- Microsoft 365 בעסק הקטן שלך. בקר במרכז העסקים הקטנים עכשיו התמיכה עבור OneNote 2016 ו- OneNote 2019 הסתיימה למד מה המשמעות של סוף התמיכה וכיצד לשדרג ל- Microsoft 365. קבל פרטים על סיום התמיכה ב- Office 2016 ו- Office 2019 נושאים טרנדיים ב- OneNote ב- Windows מה חדש ב- OneNote תחילת העבודה עם OneNote כתיבת הערות בכתב יד העתקת טקסט מתמונות ומתדפיסי קבצים המרה ופתרון של משוואות מתמטיות סינכרון מחברות הגנה על הערות באמצעות סיסמה קיצורי מקשים קבלת תמיכה צור קשר הצטרף לדיון שאל את הקהילה קנה את Microsoft 365 הצג תוכניות ומחירים מה חדש Copilot לארגונים Copilot לשימוש אישי Microsoft 365 אפליקציות של Windows 11 Microsoft Store פרופיל החשבון מרכז ההורדות החזרות מעקב אחר הזמנות חינוך Microsoft Education מכשירים לחינוך Microsoft Teams בתחום החינוך Microsoft 365 Education Office Education הדרכות ופיתוח למחנכים מבצעים לתלמידים ולהורים Azure לסטודנטים עסק האבטחה של Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams מפתח ו-IT מפתח של Microsoft Microsoft Learn תמיכה באפליקציות השוק של AI קהילת Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio חברה קריירה אודות Microsoft פרטיות ב-Microsoft משקיעים קיימות עברית (ישראל) סמל ביטול הצטרפות מהאפשרויות הפרטיות שלך אפשרויות הפרטיות שלך סמל ביטול הצטרפות מהאפשרויות הפרטיות שלך אפשרויות הפרטיות שלך פרטיות בריאות הצרכן צור קשר עם Microsoft פרטיות ניהול קבצי Cookie תנאי השימוש סימנים מסחריים אודות הפרסומות שלנו נגישות © Microsoft 2026 | 2026-01-13T09:29:40 |
https://www.atlassian.com/br/software/jira/service-management/features/asset-and-configuration-management | Gerenciamento de configuração e recursos com o Jira | Atlassian Close Quer visualizar esta página no seu idioma ? Todos os idiomas Escolha seu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtenha grátis Aplicativos Service Collection Jira Service Management Gestão de atendimento ao cliente Recursos Service Collection Back Preços E mais + Menos - Obtenha grátis Back Obtenha grátis Gerenciamento de configurações e ativos O Recursos oferece visibilidade das dependências para que você possa gerenciar recursos e itens de configuração (CIs), solucionar incidentes com rapidez e reduzir o risco das alterações. Experimente agora Conheça o Recursos Assista ao vídeo O lugar para dados importantes Diferente dos bancos de dados antigos, o Recursos oferece uma estrutura de dados flexível e aberta para que as equipes gerenciem e conectem recursos essenciais a solicitações, incidentes, alterações e muito mais. Acompanhe o que importa De hardware, software e itens de configuração a pessoas, pianos e peixes (é sério), reúna todos os recursos da sua empresa em um banco de dados flexível. Os templates pré-criados ajudam você a começar mais rápido. Conecte os recursos ao trabalho Vincule objetos em Recursos a tickets de suporte, itens de incidente, solicitações de alteração e muito mais. Melhore a visibilidade e acelere o trabalho em todos os tipos de casos de uso em TI, RH, instalações e muito mais. Tome decisões melhores Tenha total visibilidade e controle sobre os recursos para reduzir riscos e melhorar as operações, agora com relatórios e painéis novos e flexíveis para obter insights mais profundos e tomar decisões mais inteligentes e rápidas. Traga dados completos, atuais e corretos para o Recursos O Gerenciador de dados do Recursos simplifica a integração, a reconciliação e a análise de dados de várias fontes, fornecendo dados confiáveis para decisões inteligentes. Saiba mais Funções de gestão de configuração e recursos Automação Diga adeus ao rastreamento de proprietários ou à atualização de planilhas. Automatize a inserção de dados com base em tickets do Jira para manter atualizadas as informações necessárias sobre seus recursos. Consultas Execute consultas em objetos do Recursos para fazer auditorias, gerenciar custos e identificar as causas dos itens. Templates Comece logo com templates de esquema predefinidos para trazer estrutura ao banco de dados para casos de uso comuns em TI, instalações, RH e muito mais. Discovery Detecte recursos habilitados para IP, extraia informações sobre os principais atributos e dependências e acompanhe todas as mudanças para se manter atualizado. Integrações Aproveite mais de 30 adaptadores, incluindo arquivos simples e bancos de dados SQL, para trazer de forma simples dados importantes para o Recursos. Relatórios Obtenha insights acionáveis de seus dados do Recursos para monitorar a integridade dos recursos, detectar lacunas de conformidade e riscos de segurança e acessar dados financeiros importantes. “O Recursos é muito importante para manter a previsibilidade e o planejamento das licenças e dos custos de software.” Damir Prusac Vice-presidente de engenharia, Infobip Leia mais Perguntas mais frequentes Quais são as diferenças entre o Recursos no Jira Service Management Cloud, no Data Center e no App do Recursos? Para entender melhor as funções de cada plano de Recursos, veja esta tabela de comparação . Recursos podem ser usados com espaços do Jira? Sim. Objetos no Recursos podem ser vinculados a tickets do Jira, desde que haja uma licença ativa da Service Collection Standard ou superior na mesma instância. Por que trocar minha ferramenta de CMDB/gestão de recursos? Mover seu CMDB para o Recursos, um aplicativo na Service Collection: Simplifica seu trabalho, pois terá todas as informações de ITSM (solicitações, incidentes, alterações e problemas) e CMDB em uma única ferramenta Dar mais contexto entre recursos e itens de configuração e entre incidentes e alterações para que as equipes de desenvolvimento e operações consigam identificar a origem do problema com mais rapidez e gerenciar os riscos para viabilizar mais implementações sem problemas Reduz custos, já que os outros fornecedores de CMDB são caros Aumentar a flexibilidade para armazenar qualquer tipo de inventário, recurso ou registro, sem restrições ou limites para apenas casos de uso de TI. A Atlassian oferece uma ferramenta de descoberta de recursos? Sim, a gente oferece a funcionalidade de descoberta básica para detectar recursos e itens de configuração conectados à rede local e extrair informações detalhadas sobre cada recurso. A gente também oferece integrações com as principais soluções de descoberta, como Lansweeper e Flexera, para encontrar e importar dispositivos para o aplicativo app do Recursos. Como os dados são importados para Recursos? Com o Recursos, os usuários podem aproveitar o Gerenciador de dados e sua função nativa de importação de esquemas. Saiba mais aqui: Saiba mais sobre o Gerenciador de dados do Recursos Saiba mais sobre adaptadores Configure o Gerenciador de dados do Recursos Mova os dados para o Gerenciador de dados a fim de criar dados brutos Remova valores desnecessários para criar dados transformados Elimine registros desnecessários para criar dados limpos Reconcilie fontes de dados para criar objetos do Gerenciador de dados Importe para um esquema do Recursos a fim de criar objetos de esquema O que pode ser armazenado em Recursos? Qualquer coisa. Sério. Recursos de TI tradicionais, como hardware? ✅ Itens de configuração? ✅ Registros de pessoas? ✅ Peixe? Se é importante para você, é importante para a gente ✅ Recursos é uma ferramenta flexível que se adapta às suas necessidades. Basta criar o tipo de objeto e o esquema certos para você seguir em frente. Características e recursos da gestão de configuração Demonstração Como gerenciar o inventário em Recursos Assista à demonstração Artigo técnico Manual de gestão de configuração e recursos para ITSM Saiba mais ebook A evolução dos recursos: uma abordagem mais inteligente para agregar valor comercial Saiba mais Decisões inteligentes começam com dados de recursos de qualidade Experimente grátis Empresa Carreiras Eventos Blogs Relações com investidores Fundação Atlassian Kit de imprensa Fale conosco produtos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos os produtos Recursos Suporte técnico Compras e licenciamento Comunidade da Atlassian Base de conhecimento Marketplace Minha conta Criar chamado de suporte Saiba mais Parceiros Treinamento e certificação Documentação Recursos de desenvolvedores Serviços corporativos Ver todos os recursos Copyright © 2025 Atlassian Política de privacidade Termos Aviso legal Escolha o Idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fmessenger.com%2F&h=AT1QMJkVVqdF-81E-ddNr3VOH-BvSvgKy3vN2RSS7ma6qDoo7DnRZBZOiBh7q3Tb_3FKM6KkD0GxQFhilMsbstGF5A-xDgXgNo7VNcytPfQOpNgMtIOKG3p6BV_Z43C1O3cWpOt2oI4400am | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:40 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.meta.com%2F&h=AT1QMJkVVqdF-81E-ddNr3VOH-BvSvgKy3vN2RSS7ma6qDoo7DnRZBZOiBh7q3Tb_3FKM6KkD0GxQFhilMsbstGF5A-xDgXgNo7VNcytPfQOpNgMtIOKG3p6BV_Z43C1O3cWpOt2oI4400am | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:40 |
https://www.microsoft.com/ko-kr/ai/energy-resources | 지속 가능한 에너지 솔루션 | Microsoft AI This is the Trace Id: 20aa5a184622ffb4d8a09a1fa1f4139f 주 콘텐츠로 건너뛰기 Microsoft Microsoft AI Microsoft AI Microsoft AI 홈 제품 및 솔루션 조직용 조직용 Microsoft 365 Copilot Microsoft 365 Copilot 앱 다운로드 조직용 Copilot Agent 365 Customize your Copilot Customize your Copilot Copilot Studio Build your own Build your own Microsoft Foundry Foundry Tools Azure AI 솔루션 파트너 제공 파트너 제공 Microsoft Marketplace Intelligent PCs Intelligent PCs Copilot+ PCs 개인용 개인용 Microsoft Copilot Copilot 앱 다운로드 업계 솔루션 소비재 보안 및 인텔리전스 교육 에너지 및 자원 에너지 및 자원 개요 전력 및 유틸리티 석유 및 가스 채광 금융 서비스 금융 서비스 개요 뱅킹 자본 시장 보험 정부 기관 정부 기관 개요 대중교통 및 도시 인프라 공공 금융 공중 보건 및 복지 서비스 공공 안전 및 정의 의료 서비스 및 생명 과학 의료 서비스 및 생명 과학 개요 공급자 Payors 생명과학 제조 제조 개요 산업 혁신 미디어 및 엔터테인먼트 이동성 이동성 개요 자동차 여행 및 교통 소매 통신 비즈니스 리더를 위한 AI AI 사용 사례 신뢰할 수 있는 AI 책임 있는 AI 책임 있는 AI Microsoft 책임 있는 AI 원칙 및 접근 방식 도구 및 사용 지속 가능성 지속 가능성 지속 가능성 강화 보안 유지 보안 유지 AI 보안 강화 데이터 보호 및 개인 정보 알아보기 AI 101 AI 학습 허브 업계 블로그 Microsoft Cloud 블로그 지원 비즈니스 고객을 위한 지원 산업 문서 자세히 산업 Microsoft for energy and resources</h1> "> 에너지 및 자원을 위한 Microsoft 넷 제로를 달성하고, 지속 가능한 미래를 위해 안전하고 신뢰할 수 있는 공평한 에너지를 제공하기 위한 혁신을 가속화하세요. 비디오 보기 개요 개요 섹터 고객 사례 파트너 제품 리소스 개요 Accelerate the energy transition</h2> "> 에너지 전환 가속화 Microsoft의 신뢰할 수 있는 데이터와 AI 솔루션을 사용하여 에너지 및 리소스 업계에서 더 많은 성과를 달성하세요. 에너지 분야 직원의 역량 강화 원활한 협업을 위해 워크플로를 자동화하고 AI 지원 채용, 학습, 교육을 개선합니다. 새로운 에너지 미래를 추구하는 운영 AI를 사용해 공급망, 보안 자산, 전력 에너지 시스템을 최적화하여 생산성을 높입니다. 넷제로 약속 달성 데이터를 활용하여 탄소 배출을 줄이고, 탄소 없는 에너지의 규모를 늘리고, 에너지 가치 사슬에서 탈탄소를 달성합니다. 지속 가능한 AI 기반 비즈니스 성장 기후 혁신, 지속 가능성 진행률, 비즈니스 성장을 가속화하는 명확한 데이터 인사이트를 얻습니다. 섹터 Explore energy solutions by sector</h2> "> 섹터별 에너지 솔루션 살펴보기 전력 및 유틸리티, 석유 및 가스, 채광에 대한 클라우드 및 AI 기반 솔루션을 찾아보세요. 전력 및 유틸리티 그리드를 현대화하고, 고객에게 서비스를 제공하고, 비즈니스 목표를 달성하는 새로운 방법을 살펴보세요. 자세한 정보 석유 및 가스 데이터 기반 솔루션을 사용하여 혁신을 가속화하고, 운영을 최적화하고, 배출을 줄이세요. 자세한 정보 채광 차세대 기술로 미래의 지속 가능한 채광을 활성화하세요. 자세한 정보 고객 사례 Learn how energy organizations are innovating</h2> "> 에너지 조직이 혁신하는 방법 알아보기 이전 슬라이드 다음 슬라이드 "Microsoft 및 디지털 트윈 기술과 연결된 bp 2.0에서 작업을 시작하기 전까지 최고의 기술이 무엇인지 여전히 파악하지 못했습니다." Rob Kelly, VP 디지털 프로덕션, 프로젝트 Azure 사례 읽기 “Microsoft와의 관계를 통해 목표를 달성할 수 있고 지속 가능하고 비용 효율적인 옵션을 제공하는 리더가 될 수 있다는 확신을 갖게 되었습니다.” Emile Das, IT 아키텍처 관리자 제품 Dynamics 365 Dynamics 365 Customer Insights 사례 읽기 “Microsoft Azure Data Manager for Energy는 단순히 데이터를 저장하거나 컴퓨팅을 실행하는 장소 그 이상입니다. 이는 작업을 자동화하는 데 도움이 되는 일련의 상호 연결된 서비스입니다.” James Elgenes, 서브서피스 데이터 및 정보 관리자 250 클라우드 채택을 통해 수년간의 작업 시간 단축 제품 Azure Microsoft Azure Data Manager for Energy 사례 읽기 고객 사례 섹션으로 돌아가기 추천 파트너 앱 Explore energy solutions from our industry-leading partners</h2> "> 업계 최고의 파트너의 에너지 솔루션 살펴보기 Microsoft 파트너 에코시스템에서 에너지 및 리소스 산업 제품을 찾아보세요. (#=appDisplayName#) (#=appTitle#) (#=appDesc#) (#=averageRating#) ((#=ratingCount#)) (#=ratingCount#)명의 사용자가 별점 5점 만점에 (#=ratingAverage#)점을 매겼습니다. (#=appHelpText#) 콘텐츠 로드 중... (#=appDisplayName#) (#=appTitle#) (#=appDesc#) (#=averageRating#) ((#=ratingCount#)) (#=ratingCount#)명의 사용자가 별점 5점 만점에 (#=ratingAverage#)점을 매겼습니다. (#=appHelpText#) 콘텐츠 로드 중... 솔루션 살펴보기 제품 Learn about products for energy</h2> "> 에너지용 제품에 대한 자세한 정보 Microsoft의 신뢰할 수 있는 제품을 사용하여 에너지 및 리소스 산업을 재구상합니다. 이전 슬라이드 다음 슬라이드 Microsoft Power BI 실시간 데이터 기반 인사이트를 사용하여 지속 가능한 에너지 관리 방식을 개선하고 변화시킵니다. 자세한 정보 Microsoft Teams 최전방 인력이 효율적으로 소통하고 공동 작업하는 데 필요한 도구를 제공하세요. 자세한 정보 Dynamics 365 Remote Assist 혼합 현실 기술로 현장 작업자의 역량을 강화하여 더욱 스마트하게 작업할 수 있도록 지원합니다. 자세한 정보 Microsoft Power Platform 모든 팀이 로우코드 도구를 사용하여 솔루션을 개발할 수 있도록 지원하여 비즈니스 전반에서 혁신을 주도하세요. 자세한 정보 Azure Data Manager for Energy 에너지 데이터 관리를 현대화하여 실행 가능한 인사이트를 얻고 운영 효율성을 개선하며 비용을 절감하세요. 자세한 정보 Azure IoT 운영 비용을 줄이면서 에너지 관리를 최적화합니다. 자세한 정보 Azure 에너지 생산에서 지능형 그리드까지 작업을 현대화하는 데 도움이 되는 사용자 지정 에너지 솔루션을 구축합니다. 자세한 정보 Dynamics 365 Field Service 기술자에게 최초 수정을 달성하는 데 필요한 적절한 정보, 도구, 원격 전문가 지원합니다. 자세한 정보 IoT용 Windows 개발자 도구, 장기 지원 및 엔터프라이즈급 보안을 사용하여 인텔리전트 에지 에너지 솔루션을 빌드하세요. 자세한 정보 Dynamics 365 Customer Service 에너지 서비스를 지원하고 모든 채널에서 뛰어난 고객 서비스를 제공합니다. 자세한 정보 Azure Digital Twins 스마트 공간, 건물, 전력망에 재사용 가능하고 확장성이 뛰어난 환경을 구축합니다. 자세한 정보 배출 영향 대시보드 조직에서 지속 가능한 에너지에 대해 데이터 기반 결정을 내리는 데 도움이 되는 중요한 인사이트를 얻으세요. 자세한 정보 제품 섹션으로 돌아가기 Discover valuable resources</h2> "> 유용한 리소스 검색 Navigating NERC CIP compliance in the cloud</h3> "> 전자책 • 2023년 4월 클라우드에서 NERC CIP 규정 준수 탐색 클라우드 채택의 이점과 전력망의 보안 및 안정성에 대한 중요한 요구 사항의 균형을 유지합니다. 전자책 받기 Explore how modern technologies and strategies shape the future of power distribution</h3> "> 개요 • 2023 현대 기술과 전략이 배전의 미래를 어떻게 형성하는지 살펴보기 개요 보기 Drive mining industry transformation with AI solutions</h3> "> 백서 • 2024 AI 솔루션으로 채굴 산업 혁신 추진 백서 받기 Empower the wind industry workforce to achieve more</h3> "> 전자책 • 2023 풍력 산업 인력이 더 많은 성과를 달성할 수 있도록 지원 eBook 읽기 다음 단계 Start achieving more in energy</h2> "> 에너지 분야에서 더 많은 성과 달성 Find your cloud solution</h3> "> 비즈니스 솔루션 허브 클라우드 솔루션 찾기 귀사의 고유한 비즈니스 목표에 적합한 솔루션을 찾으려면 지금 살펴보세요. 모든 솔루션 찾아보기 Build a more sustainable future with AI</h3> "> Microsoft AI AI로 더욱 지속 가능한 미래 구축 AI 기반 솔루션을 통해 에너지 및 리소스 산업을 재창조하고 넷 제로를 달성하세요. 자세한 정보 팔로우하기 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:29:40 |
https://support.microsoft.com/id-id/warranty | Perlindungan, garansi, dan perbaikan perangkat keras Lompati ke konten utama Microsoft Dukungan Dukungan Dukungan Beranda Microsoft 365 Office Produk Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows lainnya... Perangkat Surface Aksesori PC Xbox Permainan PC HoloLens Surface Hub Jaminan perangkat keras Akun & penagihan Akun Microsoft Store & Penagihan Sumber daya Yang baru Forum komunitas Admin Microsoft 365 Portal Bisnis Kecil Pengembang Pendidikan Laporkan penipuan dukungan Keamanan produk Lebih banyak Beli Microsoft 365 Semua Microsoft Global Microsoft 365 Teams Copilot Xbox Dukungan Perangkat Lunak Perangkat Lunak Aplikasi Windows AI OneDrive Outlook Beralih dari Skype ke Teams OneNote Microsoft Teams PC dan perangkat PC dan perangkat Beli Xbox Accessories Hiburan Hiburan Game PC Bisnis Bisnis Microsoft Security Azure Dynamics 365 Microsoft 365 untuk bisnis Microsoft Industry Microsoft Power Platform Windows 365 Pengembang & TI Pengembang & TI Pengembang Microsoft Microsoft Learn Dukungan aplikasi marketplace AI Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Lainnya Lainnya Unduhan & keamanan gratis Pendidikan Licensing Lihat Peta Situs Cari Cari bantuan Tidak ada hasil Batal Masuk Masuk dengan Microsoft Masuk atau buat akun. Halo, Pilih akun lain. Anda memiliki beberapa akun Pilih akun yang ingin Anda gunakan untuk masuk. Perlindungan, garansi, dan perbaikan perangkat keras Garansi perangkat keras Perangkat atau aksesori Microsoft Anda dilengkapi dengan Garansi Perangkat Keras Terbatas Microsoft. Syarat dan ketentuan berbeda-beda di setiap negara atau wilayah. Ketentuan garansi Dapatkan layanan dari Microsoft Untuk mendapatkan layanan untuk perangkat Surface, Anda dapat mengirimkannya untuk mendapatkan layanan berkualitas yang dilakukan oleh pakar Microsoft tepercaya menggunakan bagian bersertifikat. Cara mendapatkan layanan atau perbaikan untuk Surface Mulai pesanan layanan untuk perangkat pribadi Lihat opsi layanan Surface untuk Bisnis dan Pendidikan. Dukungan penyedia layanan resmi Microsoft memiliki mitra yang dapat menyediakan dukungan langsung untuk perangkat Anda sebagai Penyedia Layanan Resmi (ASP). Tidak tersedia di semua negara dan kawasan. Temukan lokasi untuk dukungan langsung Untuk Surface for Business, cari ASP di wilayah Anda Paket Perlindungan Microsoft Tetap terlindungi, untuk waktu yang lebih lama. Lindungi pembelian perangkat Anda dengan opsi untuk perangkat keras yang diperluas dan cakupan kerusakan yang tidak disengaja. Hanya tersedia di pasar tertentu. Pelajari selengkapnya tentang Paket Perlindungan Microsoft Untuk Surface for Business, kunjungi Paket Garansi & Perlindungan Microsoft Surface Layanan garansi habis Jika perangkat Anda tidak lagi ditanggung oleh garansi terbatas Standar atau Microsoft Complete, Anda mungkin memenuhi syarat untuk mendapatkan servis di luar garansi. Biaya layanan Dapatkan servis untuk Surface yang rusak atau habis masa garansi Temukan nomor seri perangkat Anda Ada beberapa cara untuk menemukan nomor seri untuk perangkat atau aksesori Microsoft atau Surface Anda. Menemukan nomor seri Perbaikan mandiri Perbaikan mandiri dan komponen pengganti yang tersedia ditujukan untuk perbaikan di luar garansi oleh teknisi terampil menggunakan rentang pilihan komponen pengganti dan panduan layanan. Panduan Layanan / Komponen Pengganti Informasi garansi dan servis lainnya Informasi garansi Periksa garansi Microsoft Anda Perbarui garansi Anda dengan mencantumkan bukti pembelian Garansi Aksesori PC Microsoft Informasi khusus model tertentu Layar Surface Pro 4 berkedip atau kacau Penarikan kabel daya AC Microsoft untuk perangkat Surface Pro yang memenuhi syarat Layanan dan perbaikan untuk Surface Cara mempersiapkan perangkat untuk diservis Cara mendapatkan layanan atau perbaikan Periksa status pesanan, batalkan pesanan, atau cetak label pengiriman Cara mengonfigurasi perangkat setelah diservis Dokumen hukum lainnya Syarat Lisensi Microsoft Panduan keamanan produk Informasi regulasi Surface Yang Baru Copilot untuk organisasi Copilot untuk penggunaan pribadi Microsoft 365 Microsoft 365 Family Microsoft 365 Personal Windows 11 apps Microsoft Store Profil akun Pusat Unduh Pengembalian Pelacakan pesanan Pendidikan Microsoft Education Perangkat untuk pendidikan Microsoft Teams untuk Pendidikan Microsoft 365 Education Office Education Pelatihan dan pengembangan pengajar Diskon untuk pelajar dan orang tua Azure untuk pelajar Bisnis Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Pengembang & TI Pengembang Microsoft Microsoft Learn Dukungan aplikasi marketplace AI Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Perusahaan Karier Tentang Microsoft Berita perusahaan Privasi di Microsoft Investor Keberlanjutan Indonesia (Indonesia) Ikon Penolakan Pilihan Privasi Anda Pilihan Privasi Anda Ikon Penolakan Pilihan Privasi Anda Pilihan Privasi Anda Privasi Kesehatan Konsumen Hubungi Microsoft Privasi Kelola cookie Persyaratan penggunaan Merek dagang Mengenai iklan kami © Microsoft 2026 | 2026-01-13T09:29:40 |
https://www.nec-labs.com/research/machine-learning/ | Machine Learning | Research | NEC Labs America Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Research Overview Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications News Events Careers Overview Search Careers Intern Program About Overview Christopher White | President Office of the President NEC Corporation NEC Corporation of America NEC Research & Development Follow us on Social Media! Subscribe to our Newsletter Contact Click to open the search input field Click to open the search input field Search Menu Menu Machine Learning We have been at the forefront of machine learning developments, including deep learning, support vector machines, and semantic analysis, for over a decade. Link to: ML Projects PROJECTS Link to: ML People PEOPLE Link to: ML Publications PUBLICATIONS Link to: ML Patents PATENTS As leaders in the industry, we develop innovative technologies integrated into NEC’s products and services. Machine learning is the critical technology for data analytics and artificial intelligence. Recent progress in this field opens opportunities for various new applications. Deep learning will maintain prominence with more robust model architectures, training methods, and optimization techniques. Enhanced interpretability and explainability will be imperative, especially for AI systems in critical domains like healthcare and finance. Addressing bias and ensuring fairness in AI algorithms will be a top priority, leading to the development of tools and guidelines for ethical AI. Federated learning, quantum computing’s potential impact, and the growth of edge computing will diversify ML applications. Natural language processing will continue to advance, driving progress in conversational AI, while healthcare, finance, education, and creative industries will witness profound AI integration. As quantum computing matures, it could revolutionize machine learning, while edge computing and federated learning will expand AI’s reach across various domains. Our machine learning research will produce innovation across industries, including more accurate medical diagnoses, safer autonomous systems, and efficient energy use while enabling personalized education and AI-generated creativity. Want to learn more about our machine learning department? Meet our team of experts , check out our blog posts , or read our latest publications . Join Us Are you interested in joining us? We seek the next generation of thought leaders in machine learning for researcher positions. Outstanding applicants pursuing a career in all areas of machine learning are encouraged to visit our careers page to learn more and to apply for our available positions . Summer 2026 Internship Applications are now available! Exciting internship opportunities for Summer 2026 are now available on our internship page. We are looking for students pursuing advanced degrees in Computer Science and Electrical Engineering. Internships are typically 3 months long during the summer. The benefits of working for us include the opportunity to quickly become part of a project team applying cutting-edge technology to industry-leading concepts. To apply for a Summer Internship, visit our Internship page. Featured Machine Learning Research Projects Link to: Human Collaborative LLM Agent Human Collaborative LLM Agent This research project is at the forefront of integrating advanced Large Language Models (LLMs) into the process of deriving actionable insights from vast and complex document repositories. This initiative focuses on creating a system that allows users to interact with the LLM, guiding its analysis and refining the results based on the user’s expertise and evolving needs. READ MORE Link to: Physics Informed Machine Learning Physics Informed Machine Learning Since 2019, the parameters of large deep learning models have increased by over 300 times every 18 months. However, future ML progress cannot continue simply by using more data or creating larger models because the growing gap between model demand and resource supply is not sustainable. In addition, for many problems in practice, e.g., predicting protein-drug interactions, catalyst discovery, and advanced material design, we don’t have a huge amount of training data to build big models. READ MORE Link to: Healthcare Large Multimodal Models Healthcare Large Multimodal Models We are focused on developing advanced LMMs that integrate explainable reasoning and safe generation to optimize healthcare workflows. These models are designed to process and analyze multiple data modalities—such as text, images, and structured data—enabling them to assist in complex tasks like diagnostics, treatment planning, and patient management with exceptional accuracy. READ MORE See all our Machine Learning Projects Contact Us Princeton Office 4 Independence Way, Suite 200 Princeton, NJ 08540 +1 609-520-1555 San Jose Office 2033 Gateway Place, Suite 200 San Jose, CA 95110 +1 408-863-6007 About Us NEC Laboratories America, Inc. (NEC Labs) is the US-based center for NEC Corporation’s global network of corporate research laboratories. Our diverse research groups collaborate with industry, academia and governments to provide disruptive solutions to complex problems. A leader in the integration of IT and network technologies with more than 100 years of expertise, NEC provides a combination of products and solutions that cross-utilize the company’s experience and global resources to meet the complex and ever-changing needs of its customers. Our Pages Home Research Departments Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Patents Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing News Events About Us Christopher White | President Office of the President NEC Corporation Subscribe to our Newsletter Careers Intern Program Contact Us Recent Publications Quantitative Bounds for Length Generalization in Transformers Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing SlideCraft: Context-aware Slides Generation Agent TalentScout: Multimodal AI-Driven Expert Finding in Organizations AutoScape: Geometry-Consistent Long-Horizon Scene Generation DWIM: Towards Tool-aware Visual Reasoning via Discrepancy-aware Workflow Generation & Instruct-Masking Tuning Mapillary Vistas Validation for Fine-Grained Traffic Signs: A Benchmark Revealing Vision-Language Model Limitations LANGTRAJ: Diffusion Model and Dataset for Language-Conditioned Trajectory Simulation DiscussLLM: Teaching Large Language Models When to Speak Bifröst: Peer-to-peer Load-balancing for Function Execution in Agentic AI Systems Harnessing Vision Models for Time Series Analysis: A Survey Multi-modal Time Series Analysis: A Tutorial and Survey ICeTEA: Mixture of Detectors for Metric-Log Anomaly Detection Roadside Multi-LiDAR Data Fusion for Enhanced Traffic Safety Identifying Combinatorial Regulatory Genes for Cell Fate Decision via Reparameterizable Subset Explanations On Synthesizing Data for Context Attribution in Question Answering Feasibility study on scour monitoring for subsea cables of offshore wind turbines using distributed fiber optic sensors Group Relative Augmentation for Data Efficient Action Detection Uncertainty Propagation on LLM Agent Exploring Multi-Modal Data with Tool-Augmented LLM Agents for Precise Causal Discovery EcoDoc: A Cost-Efficient Multimodal Document Processing System for Enterprises Using LLMs Integration of Fiber Optic Sensing and Sparse Grid Sensors for Accurate Fault Localization in Distribution Systems XPF: Agentic AI System for Business Workflow Automation Quantitative Bounds for Length Generalization in Transformers Re-ranking the Context for Multimodal Retrieval Augmented Generation Beyond the Permutation Symmetry of Transformers: The Role of Rotation for Model Fusion PPDiff: Diffusing in Hybrid Sequence-Structure Space for Protein-Protein Complex Design Pathologist-Read vs AI-Driven Assessment of Tumor-Infiltrating Lymphocytes in Melanoma AutoScape: Geometry-Consistent Long-Horizon Scene Generation Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Kunal Rao presents SlideCraft: Context-Aware Slides Generation Agent at PICom 2025 on October 21st NECLA at ECOC 2025: Advancing Optical Communication and Distributed Sensing News NEC Laboratories America 2025: A Year of Disruptive Innovation Apply for a Summer 2026 Internship NEC Laboratories America: Celebrating 23 Years of Research Innovation! Summer Highlights at NEC Labs America: Teamwork, Innovation, and Fun Graph Neural Networks, Explained: Our Role in the Future of AI Shaping the Future with Responsible AI, Collaboration, and Disruption Top 10 Most Legendary College Pranks of All-Time for April Fools’ Day Introducing the Trustworthy Generative AI Project: Pioneering the Future of Compositional Generation and Reasoning Introducing Our New Project: Time Series Language Model for Explainable AI The Evolution of Disciplines: From Experimental Roots to Theoretical Frameworks Agentic LLMs for AI Orchestration Project: Revolutionizing Complex Workflows Multi-Agent Simulator for Carbon Neutrality: The Technology the World Has Been Waiting For NEC Laboratories Advances Material Design with AI-based MateriAI Platform Unearthing Nature’s Orchestra – How Fiber Optic Cables Can Hear Cicada Secrets © Copyright 2025 NEC Labs America | All Rights Reserved | Privacy Policy | Global Privacy Policy Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Home Research Departments Publications Patents News Events About Us Careers Contact Us Scroll to top Scroll to top Scroll to top | 2026-01-13T09:29:40 |
https://www.drupal.org/user/186334/contribution-records?field_is_sa_value=1 | Contribution Records user listing | Drupal.org Skip to main content Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Search Drupal.org Menu Main menu Discover Drupal Drupal Core The open source framework behind millions of websites Drupal CMS Drupal CMS puts the power of Drupal into the hands of marketers, designers and content creators Drupal AI Open limitless possibilities with Drupal AI Case Studies Powerful stories that show Drupal solutions in the real world Drupal for Government Drupal is the open-source CMS that enables digital transformation of government and increases citizen engagement Drupal for Higher Education See why 70% of the world's leading universities chose Drupal Drupal for Nonprofit See why Drupal is the open-source CMS choice for some of the world’s most influential nonprofits Drupal for eCommerce Natively integrate content and commerce Drupal for FinTech Secure and trustworthy FinTech infrastructure Drupal for Healthcare Drupal powers systems that are secure, patient-centric and engaging Drupal for Enterprise Why enterprise organizations choose Drupal for multi-brand governance and global scale. Drupal for Retail See how Drupal delivers retail experiences across every channel and touchpoint. Drupal for Travel & Tourism Discover how Drupal powers travel across websites, mobile, and onboard experiences. Build with Drupal Download Drupal Download Drupal and the extensions you need Documentation Full knowledgebase including Drupal 7 resources Getting Started Guide to installing Drupal on a server Local Development Guide Guide to installing Drupal locally with Docker and DDEV Developer Resources Step-by-step guide for learning Drupal Drupal CMS User Guide Learn how to set up your site with Drupal CMS Drupal User Guide Learn to build with Drupal API Complete documentation of Drupal Core APIs Modules Extend your project's functionality Themes Change your project's look and feel Distributions Jumpstart your project with a pre-configured install Issues Queue Report issues and contribute improvements Security Advisories Stay on top of the latest security alerts and updates Partners & Services Find a Drupal Certified Partner Connect with the best Drupal agencies around the world Become an Drupal Certified Partner Join an elite network of agencies committed to Drupal excellence and innovation Find a Hosting Provider Find a hosting provider for your Drupal project Find a Migration Partner Get help with your migration to the latest version of Drupal Find Training Upskill your Drupal team Drupal Steward Ensure your website is protected with Drupal Steward Community About the Community Come for the code, stay for the community How to Contribute Get involved in growing and evolving Drupal DrupalCon DrupalCon unites experts from around the globe who create ambitious digital experiences. Network, learn, and be inspired Events Discover local events, meet-ups, and training Jobs / Careers Find opportunities to work in Drupal News & Blogs News and stories about Drupal Forum Got a question about Drupal? Find answers on the Drupal forums Slack Get support and communicate with the global Drupal community Newsletters Sign up for Drupal news and manage your subscriptions Drupal Swag Shop Get your Drupal branded merch! Support Drupal The Drupal Association Learn how we support Drupal's growth and innovation - and how you can help Become a Member Become a Ripplemaker and support the Drupal Association Become a Drupal Certified Partner Join an elite network of agencies committed to Drupal excellence and innovation Donate Make a donation to the nonprofit that supports Drupal User Menu Log in Create account Get Started Try Drupal CMS Try hosting Search Search User menu Log in Create account Secondary menu Get Started Try Drupal CMS Try Hosting Breadcrumb Home jemond Contribution records credited to jemond Project machine name eg: admin_toolbar Last status change - Any - Past year Past 3 months Past 2 months Past month Past 2 weeks Is security advisory - Any - True False No results were found. Drupal.org About Drupal Code of Conduct News Planet Drupal Privacy Policy Signup for Drupal News Terms of Service Web Accessibility facebook instagram linkedin mastodon slack youtube Tag1 provides infrastructure management for Drupal.org Need a Drupal 7 extended support partner? Consider Tag1. Drupal is a registered trademark of Dries Buytaert . Copyright 2026 | 2026-01-13T09:29:40 |
https://www.atlassian.com/ko/software/loom/use-case/support | 고객 지원 서비스에 동영상 메시지 사용 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료 평가판 사용 기능 기능 알아보기 미팅 메모 화면 녹화기 스크린샷 Loom Atlassian Intelligence 편집중 Back 솔루션 팀 사용 사례 회사 규모 팀 영업 마케팅 디자인 지원 제품 관리 엔지니어링 사용 사례 Loom + Jira Loom + Confluence 회사 규모 Enterprise Back 리소스 가격 자세한 내용 + 간략히 보기 - 무료 평가판 사용 Back 무료 평가판 사용 지원 팀을 위한 Loom 동영상 메시지로 고객 서비스 수준 향상 Loom은 규모에 맞게 고객 상호 작용을 개인화하여 팀이 고객을 평생 팬으로 만들 수 있도록 지원합니다. Loom 무료로 받기 동영상으로 고객 관계 구축 고객은 긴 이메일을 읽는 대신 동영상을 보면 됩니다. 구매자를 육성하고 고객 참여를 높일 수 있는 양질의 고객 서비스 콘텐츠를 만드세요. 시기적절한 동영상 개인화된 느낌을 더해 고객의 우려를 해결하여 피드백 루프를 더 빠르게 마무리하세요. 개인화된 동영상 명확한 시각 자료를 포함하여 고객이 제품을 최대한 활용할 수 있도록 돕는 사용자 지정 동영상을 만드세요. 대화형 동영상 동영상 참여도를 추적하고 고객에게 추가 지원이 필요한 시점을 파악하세요. 고객 지원을 위한 기능 손쉬운 녹화 브라우저, 데스크톱 또는 휴대전화에서 화면을 캡처하여 고객의 요구 사항을 해결하세요. 어디서나 공유 다운로드하지 않아도 볼 수 있는 Loom을 이메일, 채팅, 웹 또는 소셜 미디어로 보내세요. 도구 통합 Loom을 Zendesk와 같은 고객 서비스 도구와 연동하여 지원을 간소화하세요. 조회수 검토 고객이 고객 지원 동영상에 참여하는 시기와 방법을 확인하세요. 브랜딩된 지원 회사 로고 및 색상 팔레트를 추가하여 일관된 브랜딩을 유지하세요. 지속적 지원 동영상에서 바로 댓글을 검토하고 추가 지원 서비스를 제공하세요. 사용자 지원 및 고객 만족도 향상 고품질의 고객 서비스 동영상으로 사용자를 지원하세요. 개인화된 경험을 통해 유지율 향상 브랜드에서 개인화된 경험을 한 고객은 다시 구매할 가능성이 더 높습니다. 쉽게 개인화할 수 있는 Loom을 사용하면 고객 평생 가치를 높일 수 있습니다. 동영상 지원으로 고품질 지원 제공 동영상은 고객과 더 생생하게 소통할 수 있는 수단이며 그 중요성 역시 커질 수 있습니다. 예를 들어 고객이 제품 기능의 작동 방법을 직접 보면 사용법을 더 쉽게 익힐 수 있습니다. 개인화로 이탈 방지 브랜드에서 개인화되지 않은 경험을 제공하는 경우 고객의 이탈률은 60%가 넘어갑니다. Loom을 사용하면 고객 이탈률을 줄이고 고객 만족도 메트릭을 개선하는 데 필요한 인간적 감성을 더할 수 있습니다. "한쪽 구석에 조그맣게 뜨는 작은 얼굴 창으로 Loom은 엄청난 반응을 이끌었습니다. 애니메이션 또는 슬라이드 쇼 위에 오디오 트랙이 표시되는 기존 형식보다 훨씬 효과적이기 때문입니다. 구석에 실제 얼굴이 보이니 각자의 개성도 더욱 살고 스토리텔링도 생동감이 넘칩니다." Erica goodell Pearson 고객 성공 고객에게 서비스를 제공하는 기업을 지원하는 Loom AI 명확한 메시지 Loom AI는 자동으로 불필요한 단어를 제거하고 잠시 멈춘 부분을 삭제합니다. 완벽한 마무리 Loom AI를 통해 제목, 요약 및 챕터를 생성하여 참여도 및 명확성을 높입니다. 즉각적인 공유 Loom AI는 세련된 프레젠테이션에 필요한 이메일 초안을 순식간에 작성합니다. Loom AI 무료로 사용해 보기 더 빠른 녹화로 고객에게 집중할 시간 증대 빠르고 정확한 편집 및 간편한 클립 관리를 통해 더 이상 다시 녹화하는 일이 없게 하세요. 이제 비동기식 동영상을 통해 탁월한 고객 서비스를 손쉽게 제공할 수 있습니다. 사용해 보기 Atlassian 블로그에서 비동기식 동영상을 활용하여 고객 지원을 개선하는 방법 고객 지원 프로세스에 동영상이 필요한 4가지 이유 게시물 읽기 고객 지원 전략에 동영상을 활용하는 방법 게시물 읽기 Atlassian 블로그 살펴보기 Loom 사용 방법 살펴보기 엔지니어링 팀을 위한 Loom 자세히 알아보기 영업 팀을 위한 Loom 자세히 알아보기 제품 관리 팀을 위한 Loom 자세히 알아보기 모든 사용 사례 보기 어디에서 작업하시든 Loom은 여러분을 지원합니다 Mac, Windows, iOS, Android용 Loom 무료로 받기 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://support.microsoft.com/id-id/office/apa-itu-jadwal-kerja-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Apa itu Jadwal Kerja? - Dukungan Microsoft Topik terkait × Pelatihan video Microsoft Teams Mulai Cepat Microsoft Teams Apa itu Microsoft Teams? Masuk dan memulai Mengobrol dan berbagi file Kerja sama Pelajari selengkapnya Intro ke Microsoft Teams Memulai dengan Microsoft Teams Mulai menggunakan Obrolan Mulai menggunakan Rapat Mulai menggunakan Aplikasi Buat dan sesuaikan tim Anda Membuat tim dengan templat Bekerja dengan tamu eksternal Mengelola pengaturan tim Kolaborasi dalam tim dan saluran Tips: Mengirim email ke saluran Membuat rencana dengan Planner Bekerja dengan postingan dan pesan Memposting pesan ke beberapa saluran Mencari dan menemukan catatan Mengunggah dan berbagi file Cari dan filter orang dan file Mencari dan memfilter pesan Tips untuk file Teams Memulai obrolan dan panggilan Gambaran umum panggilan Teams Lakukan panggilan Tips untuk panggilan Teams Menyembunyikan obrolan, menghapus pesan Menyiapkan delegasi untuk menerima telepon Anda Mengelola rapat Bergabung dalam rapat Teams Tips untuk rapat Teams Rapat sekarang juga Mengelola rapat Jadwalkan seminar web Menampilkan layar Anda selama rapat berlangsung Menyiapkan dan mengikuti acara langsung Merencanakan dan menjadwalkan acara langsung Membuat acara langsung Menghadiri acara langsung Mengadakan sesi T&J Eksplorasi aplikasi dan alat Menemukan dan menggunakan aplikasi Mengelola jadwal tim dengan Giliran Kerja Apa itu Jadwal Kerja? Membuat jadwal Giliran Kerja Mengelola jadwal Giliran Kerja Membuat persetujuan Apa itu Persetujuan? Buat persetujuan Buat persetujuan dari obrolan Membuat persetujuan tanda tangan elektronik Temukan templat dalam Persetujuan Membuat persetujuan dengan templat Membuat templat skala organisasi Janji temu virtual di Microsoft Bookings Apa itu janji temu virtual? Mengirim pemberitahuan teks SMS ke tamu eksternal Mengadakan janji temu Bergabung dengan janji temu Mengelola umpan aktivitas Anda Mengelola pengaturan pemberitahuan Teams di mana saja Mulai obrolan di mana saja Membuat saluran di mana saja Bergabung ke rapat dari mana saja Umpan Aktivitas di mana saja Lompati ke konten utama Microsoft Dukungan Dukungan Dukungan Beranda Microsoft 365 Office Dukungan Teams Topics Rapat Obrolan Pemberitahuan & Pengaturan Tim & saluran Panggilan & perangkat File Aplikasi & layanan Mulai cepat Obrolan Obrolan grup Pemberitahuan Teams Saluran Panggilan File Aplikasi Komponen Loop Yang baru Sumber daya Pelatihan video Pemecahan masalah Yang terkini di Teams Aksesibilitas Fitur Teams berdasarkan platform Microsoft Teams (gratis) Forum komunitas Blog komunitas teknologi Pelatihan yang dipandu instruktur Untuk admin dan profesional TI Untuk Pendidikan Lebih banyak Beli Microsoft 365 Semua Microsoft Global Microsoft 365 Teams Copilot Xbox Dukungan Perangkat Lunak Perangkat Lunak Aplikasi Windows AI OneDrive Outlook Beralih dari Skype ke Teams OneNote Microsoft Teams PC dan perangkat PC dan perangkat Beli Xbox Accessories Hiburan Hiburan Game PC Bisnis Bisnis Microsoft Security Azure Dynamics 365 Microsoft 365 untuk bisnis Microsoft Industry Microsoft Power Platform Windows 365 Pengembang & TI Pengembang & TI Pengembang Microsoft Microsoft Learn Dukungan aplikasi marketplace AI Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Lainnya Lainnya Unduhan & keamanan gratis Pendidikan Licensing Lihat Peta Situs Cari Cari bantuan Tidak ada hasil Batal Masuk Masuk dengan Microsoft Masuk atau buat akun. Halo, Pilih akun lain. Anda memiliki beberapa akun Pilih akun yang ingin Anda gunakan untuk masuk. Topik terkait Pelatihan video Microsoft Teams Mulai Cepat Microsoft Teams Apa itu Microsoft Teams? Masuk dan memulai Mengobrol dan berbagi file Kerja sama Pelajari selengkapnya Intro ke Microsoft Teams Memulai dengan Microsoft Teams Mulai menggunakan Obrolan Mulai menggunakan Rapat Mulai menggunakan Aplikasi Buat dan sesuaikan tim Anda Membuat tim dengan templat Bekerja dengan tamu eksternal Mengelola pengaturan tim Kolaborasi dalam tim dan saluran Tips: Mengirim email ke saluran Membuat rencana dengan Planner Bekerja dengan postingan dan pesan Memposting pesan ke beberapa saluran Mencari dan menemukan catatan Mengunggah dan berbagi file Cari dan filter orang dan file Mencari dan memfilter pesan Tips untuk file Teams Memulai obrolan dan panggilan Gambaran umum panggilan Teams Lakukan panggilan Tips untuk panggilan Teams Menyembunyikan obrolan, menghapus pesan Menyiapkan delegasi untuk menerima telepon Anda Mengelola rapat Bergabung dalam rapat Teams Tips untuk rapat Teams Rapat sekarang juga Mengelola rapat Jadwalkan seminar web Menampilkan layar Anda selama rapat berlangsung Menyiapkan dan mengikuti acara langsung Merencanakan dan menjadwalkan acara langsung Membuat acara langsung Menghadiri acara langsung Mengadakan sesi T&J Eksplorasi aplikasi dan alat Menemukan dan menggunakan aplikasi Mengelola jadwal tim dengan Giliran Kerja Apa itu Jadwal Kerja? Membuat jadwal Giliran Kerja Mengelola jadwal Giliran Kerja Membuat persetujuan Apa itu Persetujuan? Buat persetujuan Buat persetujuan dari obrolan Membuat persetujuan tanda tangan elektronik Temukan templat dalam Persetujuan Membuat persetujuan dengan templat Membuat templat skala organisasi Janji temu virtual di Microsoft Bookings Apa itu janji temu virtual? Mengirim pemberitahuan teks SMS ke tamu eksternal Mengadakan janji temu Bergabung dengan janji temu Mengelola umpan aktivitas Anda Mengelola pengaturan pemberitahuan Teams di mana saja Mulai obrolan di mana saja Membuat saluran di mana saja Bergabung ke rapat dari mana saja Umpan Aktivitas di mana saja Apa itu Jadwal Kerja? Berlaku Untuk Teams Microsoft Teams Cobalah! Aplikasi Shifts di Microsoft Teams adalah alat manajemen jadwal dan pelacakan waktu yang membantu Anda membuat, memperbarui, dan mengelola jadwal untuk tim Anda. Jadwal - Membuat, mengedit, dan mengelola jadwal untuk tim Anda. Jadwal Shift menampilkan hari di bagian atas, anggota tim muncul di sebelah kiri, dan shift yang ditetapkan muncul di kalender. Pengaturan jadwal - Di pengaturan Shift, tentukan opsi jadwal dan pilih kapabilitas Shifts yang ingin Anda sediakan untuk tim Anda. Grup - Tambahkan grup jadwal untuk menata anggota tim dalam jadwal menurut jenis pekerjaan atau lokasi. Shift - Tetapkan shift ke anggota tim. Buat shift dari awal atau salin yang sudah ada. Buka shift - Setiap grup dalam jadwal memiliki baris Buka shift . Tambahkan shift terbuka ke jadwal Anda yang dapat diminta siapa pun. Jam waktu - Aktifkan Jam waktu di pengaturan Shift untuk memungkinkan tim Anda masuk dan kehabisan shift. Permintaan - Tinjau dan respons permintaan waktu libur, buka shift, shift swap, dan penawaran. Tag - Gunakan tag berbasis shift untuk berkomunikasi dengan cepat dengan siapa pun yang saat ini bergeser. Terbitkan jadwal Anda - Setelah selesai membuat perubahan pada jadwal, bagikan dengan tim Anda sehingga semua orang mendapatkan informasi terbaru. Ingin tahu lebih banyak? Mulai di Shifts Membuat jadwal tim di Shifts Menambahkan shift ke jadwal di Shifts Menerbitkan jadwal di Shifts Mengelola permintaan shift dan waktu libur di Shifts Mengaktifkan tag berbasis shift di Teams BERLANGGANAN FEED RSS Perlu bantuan lainnya? Ingin opsi lainnya? Menemukan Komunitas Jelajahi manfaat langganan, telusuri kursus pelatihan, pelajari cara mengamankan perangkat Anda, dan banyak lagi. Keuntungan langganan Microsoft 365 Pelatihan Microsoft 365 Keamanan Microsoft Pusat aksesibilitas Komunitas membantu Anda bertanya dan menjawab pertanyaan, memberikan umpan balik, dan mendengar dari para ahli yang memiliki pengetahuan yang luas. Tanyakan kepada Microsoft Community Komunitas Teknologi Microsoft Windows Insider Microsoft 365 Insider Apakah informasi ini berguna? Ya Tidak Terima kasih! Ada umpan balik lainnya untuk Microsoft? Dapatkah Anda membantu kami agar lebih baik? (Kirim umpan balik ke Microsoft agar kami dapat membantu.) Seberapa puaskah Anda dengan kualitas bahasanya? Apa yang memengaruhi pengalaman Anda? Masalah saya teratasi Instruksi jelas Mudah diikuti Tidak ada jargon Gambar membantu Kualitas terjemahan Tidak cocok dengan layar saya Instruksi salah Terlalu teknis Informasi tidak mencukupi Gambar tidak mencukupi Kualitas terjemahan Punya umpan balik tambahan? (Opsional) Kirimkan umpan balik Dengan menekan kirim, umpan balik Anda akan digunakan untuk meningkatkan produk dan layanan Microsoft. Admin TI Anda akan dapat mengumpulkan data ini. Pernyataan Privasi. Terima kasih atas umpan balik Anda! × Yang Baru Copilot untuk organisasi Copilot untuk penggunaan pribadi Microsoft 365 Microsoft 365 Family Microsoft 365 Personal Windows 11 apps Microsoft Store Profil akun Pusat Unduh Pengembalian Pelacakan pesanan Pendidikan Microsoft Education Perangkat untuk pendidikan Microsoft Teams untuk Pendidikan Microsoft 365 Education Office Education Pelatihan dan pengembangan pengajar Diskon untuk pelajar dan orang tua Azure untuk pelajar Bisnis Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Pengembang & TI Pengembang Microsoft Microsoft Learn Dukungan aplikasi marketplace AI Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Perusahaan Karier Tentang Microsoft Berita perusahaan Privasi di Microsoft Investor Keberlanjutan Indonesia (Indonesia) Ikon Penolakan Pilihan Privasi Anda Pilihan Privasi Anda Ikon Penolakan Pilihan Privasi Anda Pilihan Privasi Anda Privasi Kesehatan Konsumen Hubungi Microsoft Privasi Kelola cookie Persyaratan penggunaan Merek dagang Mengenai iklan kami © Microsoft 2026 | 2026-01-13T09:29:40 |
https://lwn.net/Articles/896153/ | Making O_TMPFILE atomic (and statx() additions) [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register Making O_TMPFILE atomic (and statx() additions) Did you know...? LWN.net is a subscriber-supported publication; we rely on subscribers to keep the entire operation going. Please help out by buying a subscription and keeping LWN on the net. By Jake Edge May 25, 2022 LSFMM Right on the heels of his previous filesystem session at the 2022 Linux Storage, Filesystem, Memory-management and BPF Summit (LSFMM), Steve French led a session on temporary files and their interaction with network filesystems. The problem is that creating temporary files is not always atomic, so he was proposing changing that, which would eliminate a possible race condition and be more efficient for network filesystems. Since the temporary-file discussion did not fill the 30-minute slot, however, French took the opportunity to discuss some attributes he would like to see get added for the statx() system call. Calling open() with the O_TMPFILE flag creates a unnamed file that, by default, is deleted when it is closed. It is not a feature that was in Linux from the outset; it was added for the 3.11 kernel in 2013. Not all filesystems implement the functionality, but the most widely used ones do. There are two types of filesystems, he said, some that have a two-step process for creating a file and others that do it in one step. In the two-step case, the file is created and then, separately, opened, while the others do both of those things in a single step. When those operations are performed for a network filesystem like SMB, there is a problem. If there are two operations to create the temporary file, the network filesystem has to do something special or the file created will be removed before the open can occur. For some filesystems, the create operation returns an open file, which is normally closed when the create operation completes. But if the file created is a temporary file, the close will, of course, delete the file. In that case, that close operation that would normally be done at the end of the create step has to be deferred so that the open operation can succeed. There is a small possibility of a race between the create and open operations, but it is also inefficient to make two calls across the network when one should suffice, he said. Combining the two operations, similar to what atomic_open() does, would be a better approach. He suggested adding a directory inode operation called atomic_tmpfile() that filesystems could implement if they want to support the feature. David Howells wondered if it made sense to simply use atomic_open() and add code to it for the temporary-file case. French said he looked at that and it is possible to do it that way, but that raises an issue that he would like to discuss at next year's LSFMM. He said that the open and create paths in the virtual filesystem (VFS) code are "kind of ugly" and confusing. Beyond that, there are places where unnecessary stat operations are being performed, which causes a costly network round-trip for network filesystems. So he sees some cleanup that he thinks needs to be done in those code paths. Christian Brauner said that it would be better, if possible, to make the change for atomic temporary files at the VFS level so that all filesystems could benefit without needing to add code. French thought that sounded like a good idea, but Howells was concerned that some filesystems might not be able to support the atomic temporary-file creation, so VFS might not be the right place. Forcing filesystems to open the temporary file at the same time they create it might be problematic for, say, overlayfs, he said. It is worth experimenting with the idea, French said. statx() Since there was time left in the slot, French shifted gears to talk about another idea he would like to see implemented. There are already a number of flags that are returned by statx() , he said, but he can see a need for a few more. He put up a slide listing nine attribute flags that currently can be returned for a file, but there are four additional attributes that "jump out at me" for addition, he said. For example, it is relatively common these days for people to have "local" files that are actually stored in the cloud somewhere, so an "offline" attribute would be useful. On the flipside, a "pinned" attribute could be used to indicate a file that is backed by cloud storage but is hosted locally, so it should not be removed because of the time required to get it back. These are not attributes that network filesystems, such as SMB, would need to handle, they would simply report them. These "seem like no-brainers", he said. The other two are "integrity" and its opposite, to indicate some kind of scratch file where file integrity is not important, which he called "no scrub" on his slides. These would ask the filesystem to either do the best it can in terms of integrity protection or to do nothing in that regard. Chuck Lever questioned whether a single bit is enough to encompass all of the complexity of Linux integrity protection, which has various configuration options and policies. But statx() already has "encrypted" and "compressed" attributes, so French sees "integrity" in the same light; it would be requesting the strongest integrity protection the filesystem can provide. Howells wondered which of these attribute bits would actually be used by applications. Putting them into statx() implies that applications will use them frequently. He can see that "offline" might make sense, since it would provide a useful hint to desktop environments, but the others seem questionable. The filesystem may need to know about them, but it is less clear that applications need them. Ted Ts'o said that he was hearing an assumption that there is a way to set these attributes, but that is not the case. statx() only reports them and there is no Linux system call that would allow an administrator to set them. The attribute flags originated in an ext2-specific ioctl() command, he said, that eventually got adopted by other filesystems and moved into the VFS. But the original 32-bit flag field was the actual on-disk representation for the ext filesystems so there were ext-specific flags that other filesystems were not interested in. statx() came about to report a filesystem-independent set of attributes to user space. But there is no way for someone to change the value of those bits in a filesystem-independent way. There are various mechanisms to set them, using ioctl() commands, but no system call to set, for example, the statx() "integrity" attribute for any filesystem. There was some discussion of what a "setinfo" facility might look like. Kent Overstreet suggested that the extended attribute (xattr) interface could be used; a special namespace would actually refer to these file attributes and statx() would be the fast path to access them. French thought that sounded reasonable, and did not think it was urgent to add the ability to set the values in a generic way. Index entries for this article Kernel Filesystems/statx() Kernel O_TMPFILE Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:40 |
https://www.atlassian.com/nl/software/jira/guides/projects/overview | Jira-projecten: de belangrijkste aspecten en basis | Atlassian Close Deze pagina in jouw taal bekijken? Alle talen Kies je taal 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Ontvang het gratis Functies Alle functies Rovo in Jira Back Oplossingen Teams Usecases Bedrijfsomvang Teams Marketing Engineering Ontwerp Operations IT Usecases Aan de slag Planning Campagnebeheer Agile projectmanagement Programmabeheer Bedrijfsomvang Enterprise Back Producthandleiding Sjablonen Sjablonen Alle sjablonen Softwareontwikkeling Marketing Ontwerp Sales Operations Servicemanagement HR Juridische afdeling IT-activiteiten Finance Jira Service Management-sjablonen Back Prijzen Meer + Minder - Ontvang het gratis Back Ontvang het gratis Aan de slag Introductie tot Jira Jira voor teams 7 stappen om aan de slag te gaan met Jira Projecten Overzicht Tutorials Bronnen Borden Overzicht Tutorials Bronnen Werkitems/issues Overzicht Tutorials Bronnen Workflows Overzicht Tutorials Bronnen Integraties Overzicht Tutorials Bronnen Rapporten en dashboards Overzicht Tutorials Bronnen Inzichten Overzicht Tutorials Bronnen Toegangsrechten Overzicht Tutorials Bronnen JQL Overzicht Tutorials Spiekbriefje Bronnen Navigatie Overview Tutorials Resources Automatisering Overzicht Tutorials Bronnen Tijdlijn Overzicht Tutorials Bronnen Advanced Roadmaps Overzicht Tutorials Bronnen Jira mobile Overzicht Tutorials Bronnen Meer over Jira Versies van Jira Hostingopties Overzicht van Jira-spaces Wat is een Jira-space? Doorgaans kan een space worden gedefinieerd als een collectie taken die moeten worden voltooid om een bepaald resultaat te bereiken. In Jira kun je een space zien als een container die wordt gebruikt om die taken of werkitems voor het hele team te ordenen en te volgen. Een Jira-space is zeer configureerbaar en kan eenvoudig worden aangepast aan de organisatiestructuur, workflow of mate van agile volgroeidheid. Hierdoor is het de enige tool die past bij de unieke manier van werken van elk team. Je team kan een Jira-space gebruiken om bugs op te sporen en op te lossen, een nieuwe functie te lanceren en meer. Je spaces zijn te vinden in de navigatie bovenaan in het vervolgkeuzemenu 'Spaces'. Bekijk de volledige demo Wat zijn de belangrijkste elementen van een Jira-space? Zoals bij elk project zijn er taken die gedaan moeten worden, mensen die dingen mogelijk maken en processen om dat werk in beweging te houden. Werkitems : Jira-spaces zijn grote doelen die zijn opgesplitst in kleine, uitvoerbare werkonderdelen, genaamd werkitems . Mensen : met Jira kunnen teams gemakkelijk werk plannen en volgen, zodat je samen meer kunt bereiken. Nodig gebruikers uit voor je Jira-space om te beginnen met samenwerken. Workflows : Jira-spaces zijn gestructureerd om een proces of workflow te volgen om een werkitem van begin tot eind te leiden. Deze workflows kunnen worden aangemaakt en afgestemd op de unieke manier van werken van je team. Wat zijn sjablonen voor Jira-spaces? Jira biedt verschillende spacesjablonen om teams te helpen snel aan de slag te gaan met projecten die zijn afgestemd op een specifiek team (zoals HR of software) of bepaalde use case. Deze sjablonen bevatten vooraf geconfigureerde werktypen, workflows en andere relevante functies. Twee van onze populairste sjablonen zijn de kanban- en scrumsjablonen. Bezoek de sjabloonbibliotheek van Jira De kanban-sjabloon visualiseert je werk met een krachtig, maar eenvoudig bord. Het is ontworpen voor teams die het werk in uitvoering beperken en zich richten op een continue workflow. Met de kanban-sjabloon in Jira kunnen teams hun workflow eenvoudig ontwerpen, beheren en verbeteren en zorgen voor overzicht terwijl het werk zich verplaatst van 'te doen' naar 'gereed'. Met een scrumsjabloon kunnen teams grote werkonderdelen opsplitsen in beter beheersbare stukken. Het is ontworpen voor teams die regelmatig werken of werken in korte periodes met tijdvakken, genaamd sprints. Het scrumsjabloon stelt teams ook in staat om al het werk op de backlog en het bord te ordenen en te prioriteren, terwijl ze via de roadmap gefocust blijven op het grote geheel. Meer informatie over kanban versus scrum Welke Jira-spacetypen zijn er? Spaces in Jira zullen ofwel een 'teambeheerd' of een 'bedrijfsbeheerd' spacetype zijn. Het grootste verschil tussen de twee spacetypen is hoe ze worden beheerd. Dat wil zeggen of de space wordt beheerd op teamniveau of op bedrijfs-/Jira-beheerniveau. Teambeheerde spaces Overzicht Dit spacetype is voor teams die een vereenvoudigde configuratie en meer controle willen over hun eigen werkprocessen en -praktijken in een zelfstandige space. Teambeheerde spaces worden beheerd door projectbeheerders. Dit betekent dat wijzigingen kunnen worden doorgevoerd zonder de hulp van een Jira-beheerder. Vereenvoudigde configuratie Teambeheerde spaces zijn klaar voor gebruik met vereenvoudigde configuratie. Iedereen in je team kan deze instellen en onderhouden. Teambeheerde spaces worden onafhankelijk geconfigureerd en wijzigingen in de ene space hebben geen invloed op andere spaces. Essentiële functies Een moderne Jira-ervaring voor teams die geen geavanceerde functies nodig hebben. Tijdlijn Geef alleen de werkitems van je space weer op je bord Een actieve sprint Essentieel agile rapporteren Bedrijfsbeheerde spaces Overzicht Dit spacetype is voor teams die in meerdere spaces en met meerdere teams op een meer gestandaardiseerde manier willen werken. Bedrijfsbeheerde spaces worden beheerd door Jira-beheerders die de best practices en processen van organisaties stimuleren en promoten via een gedeelde configuratie. Geavanceerde configuratie Bedrijfsbeheerde spaces geven Jira-beheerders de volledige controle over configuratie, aanpassing en flexibiliteit. Deze spaces worden ingesteld en onderhouden door je Jira-beheerders. De configuratie wordt gedeeld tussen spaces. Geavanceerde functies De kracht en functies waar Jira om bekend staat . Geavanceerde planning (alleen Premium) De mogelijkheid om werkitems van andere spaces op je bord te pullen De mogelijkheid om parallelle sprints uit te voeren Uitgebreide agile rapporten Meer informatie over Jira-spacetypen Bedrijf Vacatures Evenementen Blogs Investeerders Atlassian Foundation Mediapakket Contact producten Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Alle gratis producten bekijken Bronnen Technische ondersteuning Aanschaf en licenties Atlassian Community Kennisdatabase Marketplace Mijn account Ondersteuningsticket maken Leren Partners Training en certificering Documentatie Voor ontwikkelaars Bedrijfsservices Alle bronnen tonen Copyright © 2025 Atlassian Privacybeleid Voorwaarden Impressum Taal kiezen Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://www.atlassian.com/zh/jira/solutions/program-management#tab-def490c4-416a-483f-aabd-8dceed4181ba | 计划管理 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 Jira 为计划管理助力 使用 Jira 简化、精简、交付 了解 Jira 如何帮助您和您的团队将宏伟目标转化为可实现的项目。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行计划管理？ 克服复杂性 无论有多少团队参与其中，即使是最艰巨的战略计划，也要分解成可实现的小步骤。 驾驭依赖关系 在潜在的中断和不确定性影响团队工作之前，提前做好准备。 全面的可见性 查看和组织各团队的工作，以便更好地管理资源配置，做出明智的战略决策。 专为计划管理而设计的模板 适用于各类计划、项目和举措的可定制模板。 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 确定任务的优先次序，管理团队工作量，跟踪工作从规划到完成的整个过程。 开始使用 顶层规划 为您的团队提供清晰、实时的视图，以便进行协作、安排和调整战略目标。 开始使用 流程规划 让您的团队不再重复流程。对各种流程中的步骤进行分类，以便您和您的团队能够快速识别未完成的任务。 开始使用 甘特图 一款强大的可视化工具，用于跟踪工作和避开障碍。概述项目工期，指明里程碑并绘制依赖关系。 开始使用 个人任务跟踪器 跟踪个人任务，如电子邮件分类、会议准备和费用管理。 开始使用 计划和启动项目，全部从 Jira 中进行 规划 需求不断变化？没有关系 分析项目并自信地与利益相关者沟通，明确进度和优先事项。 执行和跟踪 协调工作，简化流程 跟踪项目，映射依赖关系，建立跨团队的审批工作流，并确保目标如期实现。 报告和结果 完善工作流程 有了触手可及的项目摘要，您就能更明智地制定计划，并随时掌握各项举措和项目的进展情况。 计划面板公开测试版 计划或季度规划的新界面 计划面板公开测试版 计划或季度规划的新界面 通过简单的拖放式计划功能，为下个季度规划多个团队的工作。 了解更多 集成您最喜欢的所有工具 将您的工具与 Jira 巧妙地集成，而无需在平台之间进行上下文切换。 查看更多集成 计划管理资源 浏览免费教程、文章和指南以了解更多信息。 敏捷教练 将数十年的敏捷实践提炼成简单易读的课程。 了解更多 项目管理指南 帮助您计划和管理项目的分步说明。 了解更多 协调业务和技术团队 了解如何打破孤岛，开展合作以便创造更好的产品。 阅读博客 转换工作方式 免费获取 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://www.youtube.com/channel/UCBCXCmc8W9hftdAORoysXvQ | NEC Laboratories America - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T09:29:40 |
https://www.atlassian.com/ko/software/loom/use-case/support | 고객 지원 서비스에 동영상 메시지 사용 | Atlassian Close 선택한 언어 로 이 페이지를 보고 계십니까? 모든 언어 언어를 선택합니다. 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 무료 평가판 사용 기능 기능 알아보기 미팅 메모 화면 녹화기 스크린샷 Loom Atlassian Intelligence 편집중 Back 솔루션 팀 사용 사례 회사 규모 팀 영업 마케팅 디자인 지원 제품 관리 엔지니어링 사용 사례 Loom + Jira Loom + Confluence 회사 규모 Enterprise Back 리소스 가격 자세한 내용 + 간략히 보기 - 무료 평가판 사용 Back 무료 평가판 사용 지원 팀을 위한 Loom 동영상 메시지로 고객 서비스 수준 향상 Loom은 규모에 맞게 고객 상호 작용을 개인화하여 팀이 고객을 평생 팬으로 만들 수 있도록 지원합니다. Loom 무료로 받기 동영상으로 고객 관계 구축 고객은 긴 이메일을 읽는 대신 동영상을 보면 됩니다. 구매자를 육성하고 고객 참여를 높일 수 있는 양질의 고객 서비스 콘텐츠를 만드세요. 시기적절한 동영상 개인화된 느낌을 더해 고객의 우려를 해결하여 피드백 루프를 더 빠르게 마무리하세요. 개인화된 동영상 명확한 시각 자료를 포함하여 고객이 제품을 최대한 활용할 수 있도록 돕는 사용자 지정 동영상을 만드세요. 대화형 동영상 동영상 참여도를 추적하고 고객에게 추가 지원이 필요한 시점을 파악하세요. 고객 지원을 위한 기능 손쉬운 녹화 브라우저, 데스크톱 또는 휴대전화에서 화면을 캡처하여 고객의 요구 사항을 해결하세요. 어디서나 공유 다운로드하지 않아도 볼 수 있는 Loom을 이메일, 채팅, 웹 또는 소셜 미디어로 보내세요. 도구 통합 Loom을 Zendesk와 같은 고객 서비스 도구와 연동하여 지원을 간소화하세요. 조회수 검토 고객이 고객 지원 동영상에 참여하는 시기와 방법을 확인하세요. 브랜딩된 지원 회사 로고 및 색상 팔레트를 추가하여 일관된 브랜딩을 유지하세요. 지속적 지원 동영상에서 바로 댓글을 검토하고 추가 지원 서비스를 제공하세요. 사용자 지원 및 고객 만족도 향상 고품질의 고객 서비스 동영상으로 사용자를 지원하세요. 개인화된 경험을 통해 유지율 향상 브랜드에서 개인화된 경험을 한 고객은 다시 구매할 가능성이 더 높습니다. 쉽게 개인화할 수 있는 Loom을 사용하면 고객 평생 가치를 높일 수 있습니다. 동영상 지원으로 고품질 지원 제공 동영상은 고객과 더 생생하게 소통할 수 있는 수단이며 그 중요성 역시 커질 수 있습니다. 예를 들어 고객이 제품 기능의 작동 방법을 직접 보면 사용법을 더 쉽게 익힐 수 있습니다. 개인화로 이탈 방지 브랜드에서 개인화되지 않은 경험을 제공하는 경우 고객의 이탈률은 60%가 넘어갑니다. Loom을 사용하면 고객 이탈률을 줄이고 고객 만족도 메트릭을 개선하는 데 필요한 인간적 감성을 더할 수 있습니다. "한쪽 구석에 조그맣게 뜨는 작은 얼굴 창으로 Loom은 엄청난 반응을 이끌었습니다. 애니메이션 또는 슬라이드 쇼 위에 오디오 트랙이 표시되는 기존 형식보다 훨씬 효과적이기 때문입니다. 구석에 실제 얼굴이 보이니 각자의 개성도 더욱 살고 스토리텔링도 생동감이 넘칩니다." Erica goodell Pearson 고객 성공 고객에게 서비스를 제공하는 기업을 지원하는 Loom AI 명확한 메시지 Loom AI는 자동으로 불필요한 단어를 제거하고 잠시 멈춘 부분을 삭제합니다. 완벽한 마무리 Loom AI를 통해 제목, 요약 및 챕터를 생성하여 참여도 및 명확성을 높입니다. 즉각적인 공유 Loom AI는 세련된 프레젠테이션에 필요한 이메일 초안을 순식간에 작성합니다. Loom AI 무료로 사용해 보기 더 빠른 녹화로 고객에게 집중할 시간 증대 빠르고 정확한 편집 및 간편한 클립 관리를 통해 더 이상 다시 녹화하는 일이 없게 하세요. 이제 비동기식 동영상을 통해 탁월한 고객 서비스를 손쉽게 제공할 수 있습니다. 사용해 보기 Atlassian 블로그에서 비동기식 동영상을 활용하여 고객 지원을 개선하는 방법 고객 지원 프로세스에 동영상이 필요한 4가지 이유 게시물 읽기 고객 지원 전략에 동영상을 활용하는 방법 게시물 읽기 Atlassian 블로그 살펴보기 Loom 사용 방법 살펴보기 엔지니어링 팀을 위한 Loom 자세히 알아보기 영업 팀을 위한 Loom 자세히 알아보기 제품 관리 팀을 위한 Loom 자세히 알아보기 모든 사용 사례 보기 어디에서 작업하시든 Loom은 여러분을 지원합니다 Mac, Windows, iOS, Android용 Loom 무료로 받기 회사 구직 이벤트 블로그 투자자 관계 Atlassian Foundation 보도 자료 문의하기 제품 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 제품 모두 보기 리소스 기술 지원 구매 및 라이선싱 Atlassian 커뮤니티 기술 자료 Marketplace 내 계정 지원 티켓 생성하기 자세히 알아보기 파트너 교육 및 인증 설명서 개발자 리소스 Enterprise 서비스 모든 리소스 보기 Copyright © 2025 Atlassian 개인정보보호 이용 약관 소유권 정보 언어 선택 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://www.atlassian.com/ja/software/loom/use-case/support | ビデオ メッセージを使用したカスタマー サポート サービス | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 無料で試す 機能 機能の紹介 ミーティング議事録 スクリーン レコーダー スクリーンショット Loom AI 編集 Back ソリューション チーム ユースケース 企業規模 チーム 営業 マーケティング デザイン サポート プロダクトマネジメント エンジニアリング ユースケース Loom + Jira Loom + Confluence 企業規模 Enterprise Back リソース 価格 その他 + 表示を減らす - 無料で試す Back 無料で試す Loom によるサポート ビデオ メッセージで顧客サービスを改善 Loom は、顧客との対話を大規模にパーソナライズすることで、チームが顧客を生涯のファンに変える助けとなっています。 Loom を無料で入手 ビデオを使用して顧客との絆を築く 顧客は長いメールを読まずにビデオを視聴できます。購入者への説明の提供や顧客エンゲージメントの向上のために、良質な顧客サービス コンテンツを作成します。 ビデオでタイムリーに 顧客の懸念に対して親身に対応することで、フィードバック ループをより迅速にクローズできます。 ビデオでパーソナライズ 顧客が製品を最大限に活用できるように、鮮明なビジュアルのカスタム ビデオを作成します。 ビデオでインタラクティブに ビデオ エンゲージメントを追跡し、顧客が追加のサポートを必要とするタイミングを特定します。 カスタマー サポートの機能 録画が簡単 顧客のニーズに応じて、ブラウザ、デスクトップ、または電話から画面をキャプチャできます。 どこにいても共有 Loom のビデオをメール、チャット、web、またはソーシャル メディアで送信して、ダウンロードなしで視聴できます。 ツールの統合 Loom は Zendesk のようなカスタマー サービス ツールと連携させて、サポートを簡素化できます。 視聴の確認 顧客がカスタマー サポート ビデオをいつ、どのように視聴しているかを確認できます。 サポートのブランド化 一貫したブランド化のために、会社のロゴとカラー パレットを追加できます。 サポートの継続 コメントを確認して、ビデオから直接追加のサポート サービスを提供できます。 ユーザーをサポートし、顧客満足度を高める 高品質のカスタマー サービス ビデオを通じてユーザーをサポートできます。 パーソナライズした対応で定着率を高める あなたのブランドでパーソナライズされた体験をした顧客は、リピーターになる可能性が高くなります。Loom はパーソナライズを容易にし、顧客生涯価値を高めることができます。 ビデオ サポートで質の高いサポートを提供する ビデオによって、顧客との関わりがよりリアルになり、価値も高まります。たとえば、顧客が製品機能の使い方を実際に見ることができれば、使い方を習得しやすくなります。 パーソナライゼーションで解約を回避する ブランドの体験がパーソナライズされていない場合、顧客の 60% 以上が解約します。Loom なら、人間味のある対応が可能となるため、解約を減らし、顧客満足度指標を向上させることができます。 「隅に小さな顔の吹き出しが出る Loom はとても強力なツールです。オーディオ トラックがアニメーションやスライド ショーの上で再生される従来のフォーマットよりもはるかに効果的です。隅に本物の顔があると、その人の個性が加わり、ストーリーテリングが生き生きと伝わります」 エリカ・グッデル氏 Pearson、カスタマー サクセス 顧客サービス部門をサポートする Loom AI 明確なメッセージ Loom AI はつなぎ言葉や不要な間を自動的に削除します。 最後の仕上げ Loom AI を使ってタイトル、要約、章を生成して、エンゲージメントを高め、内容を明確にできます。 瞬時に共有 Loom AI は、洗練されたプレゼンテーションに関するメールの下書きを瞬時に作成します。 Loom AI を無料で試す 録画時間を短縮して顧客対応時間を確保 迅速かつ正確な編集と容易なクリップ管理により、撮り直しが不要になります。これからは、非同期ビデオを通じて優れた顧客サービスを簡単に提供できます。 試してみる 当社のブログから 非同期ビデオを使用してカスタマー サポートを改善する方法 カスタマー サポート プロセスにビデオが必要な 4 つの理由 記事を読む カスタマー サポート戦略におけるビデオの活用方法 記事を読む 当社のブログを調べる Loom の活用方法を詳しく見る エンジニアリング向け Loom 詳細を見る セールス向け Loom 詳細を見る プロダクト マネジメント向け Loom 詳細を見る すべてのユースケースを見る 場所を問わず Loom を活用 Mac、Windows、iOS、Android 用 Loom を無料で入手 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://git-scm.com/book/ko/v2/%eb%b6%84%ec%82%b0-%ed%99%98%ea%b2%bd%ec%97%90%ec%84%9c%ec%9d%98-Git-%eb%b6%84%ec%82%b0-%ed%99%98%ea%b2%bd%ec%97%90%ec%84%9c%ec%9d%98-%ec%9b%8c%ed%81%ac%ed%94%8c%eb%a1%9c | Git - 분산 환경에서의 워크플로 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 시작하기 1.1 버전 관리란? 1.2 짧게 보는 Git의 역사 1.3 Git 기초 1.4 CLI 1.5 Git 설치 1.6 Git 최초 설정 1.7 도움말 보기 1.8 요약 2. Git의 기초 2.1 Git 저장소 만들기 2.2 수정하고 저장소에 저장하기 2.3 커밋 히스토리 조회하기 2.4 되돌리기 2.5 리모트 저장소 2.6 태그 2.7 Git Alias 2.8 요약 3. Git 브랜치 3.1 브랜치란 무엇인가 3.2 브랜치와 Merge 의 기초 3.3 브랜치 관리 3.4 브랜치 워크플로 3.5 리모트 브랜치 3.6 Rebase 하기 3.7 요약 4. Git 서버 4.1 프로토콜 4.2 서버에 Git 설치하기 4.3 SSH 공개키 만들기 4.4 서버 설정하기 4.5 Git 데몬 4.6 스마트 HTTP 4.7 GitWeb 4.8 GitLab 4.9 또 다른 선택지, 호스팅 4.10 요약 5. 분산 환경에서의 Git 5.1 분산 환경에서의 워크플로 5.2 프로젝트에 기여하기 5.3 프로젝트 관리하기 5.4 요약 6. GitHub 6.1 계정 만들고 설정하기 6.2 GitHub 프로젝트에 기여하기 6.3 GitHub 프로젝트 관리하기 6.4 Organization 관리하기 6.5 GitHub 스크립팅 6.6 요약 7. Git 도구 7.1 리비전 조회하기 7.2 대화형 명령 7.3 Stashing과 Cleaning 7.4 내 작업에 서명하기 7.5 검색 7.6 히스토리 단장하기 7.7 Reset 명확히 알고 가기 7.8 고급 Merge 7.9 Rerere 7.10 Git으로 버그 찾기 7.11 서브모듈 7.12 Bundle 7.13 Replace 7.14 Credential 저장소 7.15 요약 8. Git맞춤 8.1 Git 설정하기 8.2 Git Attributes 8.3 Git Hooks 8.4 정책 구현하기 8.5 요약 9. Git과 여타 버전 관리 시스템 9.1 Git: 범용 Client 9.2 Git으로 옮기기 9.3 요약 10. Git의 내부 10.1 Plumbing 명령과 Porcelain 명령 10.2 Git 개체 10.3 Git Refs 10.4 Packfile 10.5 Refspec 10.6 데이터 전송 프로토콜 10.7 운영 및 데이터 복구 10.8 환경변수 10.9 요약 A1. 부록 A: 다양한 환경에서 Git 사용하기 A1.1 GUI A1.2 Visual Studio A1.3 Eclipse A1.4 Bash A1.5 Zsh A1.6 Git in Powershell A1.7 요약 A2. 부록 B: 애플리케이션에 Git 넣기 A2.1 Git 명령어 A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. 부록 C: Git 명령어 A3.1 설치와 설정 A3.2 프로젝트 가져오기와 생성하기 A3.3 스냅샷 다루기 A3.4 Branch와 Merge A3.5 공유하고 업데이트하기 A3.6 보기와 비교 A3.7 Debugging A3.8 Patch 하기 A3.9 Email A3.10 다른 버전 관리 시스템 A3.11 관리 A3.12 Plumbing 명령어 2nd Edition 5.1 분산 환경에서의 Git - 분산 환경에서의 워크플로 앞 장에서 다른 개발자와 코드를 공유하는 리모트 저장소를 만드는 법을 배웠다. 로컬에서 작업하는 데 필요한 기본적인 명령어에는 어느 정도 익숙해졌다. 이제는 분산 환경에서 Git이 제공하는 기능을 어떻게 효율적으로 사용할지를 배운다. 이번 장에서는 분산 환경에서 Git을 어떻게 사용할 수 있을지 살펴본다. 프로젝트 기여자 입장과 여러 수정사항을 취합하는 관리자 입장에서 두루 살펴본다. 즉, 프로젝트 기여자 또는 관리자로서 작업물을 프로젝트에 어떻게 포함시킬지와 수 많은 개발자가 수행한 일을 취합하고 프로젝트를 운영하는 방법을 배운다. 분산 환경에서의 워크플로 중앙집중형 버전 관리 시스템과는 달리 Git은 분산형이다. Git은 구조가 매우 유연하기 때문에 여러 개발자가 함께 작업하는 방식을 더 다양하게 구성할 수 있다. 중앙집중형 버전 관리 시스템에서 각 개발자는 중앙 저장소를 중심으로 하는 한 노드일 뿐이다. 하지만, Git에서는 각 개발자의 저장소가 하나의 노드이기도 하고 중앙 저장소 같은 역할도 할 수 있다. 즉, 모든 개발자는 다른 개발자의 저장소에 일한 내용을 전송하거나, 다른 개발자들이 참여할 수 있도록 자신이 운영하는 저장소 위치를 공개할 수도 있다. 이런 특징은 프로젝트나 팀이 코드를 운영할 때 다양한 워크플로를 만들 수 있도록 해준다. 이런 유연성을 살려 저장소를 운영하는 몇 가지 방식을 소개한다. 각 방식의 장단점을 살펴보고 그 방식 중 하나를 고르거나 여러 가지를 적절히 섞어 쓰면 된다. 중앙집중식 워크플로 중앙집중식 시스템에서는 보통 중앙집중식 협업 모델이라는 한 가지 방식밖에 없다. 중앙 저장소는 딱 하나 있고 변경 사항은 모두 이 중앙 저장소에 집중된다. 개발자는 이 중앙 저장소를 중심으로 작업한다 그림 54. 중앙집중식 워크플로. 중앙집중식에서 개발자 두 명이 중앙저장소를 Clone 하고 각자 수정하는 상황을 생각해보자. 한 개발자가 자신이 한 일을 커밋하고 나서 아무 문제 없이 서버에 Push 한다. 그러면 다른 개발자는 자신의 일을 커밋하고 Push 하기 전에 첫 번째 개발자가 한 일을 먼저 Merge 해야 한다. Merge를 해야 첫 번째 개발자가 작업한 내용을 덮어쓰지 않는다. 이런 개념은 Subversion과 같은 중앙집중식 버전 관리 시스템에서 사용하는 방식이고 Git에서도 당연히 이런 워크플로를 사용할 수 있다. 팀이 작거나 이미 중앙집중식에 적응한 상황이라면 이 워크플로에 따라 Git을 도입하여 사용할 수 있다. 중앙 저장소를 하나 만들고 개발자 모두에게 Push 권한을 부여한다. 모두에게 Push 권한을 부여해도 Git은 한 개발자가 다른 개발자의 작업 내용을 덮어쓰도록 허용하지 않는다. John과 Jessica가 동시에 같은 부분을 수정하는 상황을 생각해보자. John이 먼저 작업을 끝내고 수정한 내용을 서버로 Push 한다. Jessica도 마찬가지로 작업을 끝내고 수정한 내용을 서버로 Push 하려 하지만 서버가 바로 받아주지 않는다. 서버에는 John이 수정한 내용이 추가되었기 때문에 Push 하기 전에 Fetch로 받아서 Merge 한 후 Push 할 수 있다. 이런 개념은 개발자에게 익숙해서 거부감 없이 도입할 수 있다. 작은 팀만 이렇게 일할 수 있는 것이 아니다. Git이 제공하는 브랜치 관리 모델을 사용하면 수백명의 개발자가 한 프로젝트 안에서 다양한 브랜치를 만들어서 함께 작업하는 것도 쉽다. Integration-Manager 워크플로 Git을 사용하면 리모트 저장소를 여러 개 운영할 수 있다. 다른 개발자는 읽기만 가능하고 자신은 쓰기도 가능한 공개 저장소를 만드는 워크플로도 된다. 이 Workflow에는 보통 프로젝트를 대표하는 공식 저장소가 있다. 기여자는 우선 공식 저장소를 하나 Clone 하고 수정하고 나서 자신의 저장소에 Push 한다. 그 다음에 프로젝트 Integration-Manager에게 새 저장소에서 Pull 하라고 요청한다. 그러면 그 Integration-Manager는 기여자의 저장소를 리모트 저장소로 등록하고, 로컬에서 기여물을 테스트하고, 프로젝트 메인 브랜치에 Merge 하고, 그 내용을 다시 프로젝트 메인 저장소에 Push 한다. 이런 과정은 아래와 같다( Integration-manager workflow. ). 프로젝트 Integration-Manager는 프로젝트 메인 저장소에 Push를 한다. 프로젝트 기여자는 메인 저장소를 Clone 하고 수정한다. 기여자는 자신의 저장소에 Push 하고 Integration-Manager가 접근할 수 있도록 공개해 놓는다. 기여자는 Integration-Manager에게 변경사항을 적용해 줄 것을 이메일로 요청한다. Integration-Manager는 기여자의 저장소를 리모트 저장소로 등록하고 수정사항을 Merge 하여 테스트한다. Integration-Manager는 Merge 한 사항을 메인 저장소에 Push 한다. 그림 55. Integration-manager workflow. 이 방식은 GitHub나 GitLab 같은 Hub 사이트를 통해 주로 사용하는 방식이다. 프로젝트를 Fork 하고 수정사항을 반영하여 다시 모두에게 공개하기 좋은 구조로 돼 있다. 이 방식의 장점은 기여자와 Integration-Manager가 각자의 사정에 맞춰 프로젝트를 유지할 수 있다는 점이다. 기여자는 자신의 저장소와 브랜치에서 수정 작업을 계속해 나갈 수 있고 수정사항이 프로젝트에 반영되도록 기다릴 필요가 없다. 관리자는 여유를 가지고 기여자가 Push 해 놓은 커밋을 적절한 시점에 Merge 한다. Dictator and Lieutenants 워크플로 이 방식은 저장소를 여러개 운영하는 방식을 변형한 구조이다. 보통 수백 명의 개발자가 참여하는 아주 큰 프로젝트를 운영할 때 이 방식을 사용한다. Linux 커널 프로젝트가 대표적이다. 여러 명의 Integration-Manager가 저장소에서 자신이 맡은 부분만을 담당하는데 이들을 Lieutenants 라고 부른다. 모든 Lieutenant는 최종 관리자 아래에 있으며 이 최종 관리자를 Benevolent Dictator 라고 부른다. Benevolent Dictator는 Lieutenant의 저장소를 가져와 공식 저장소에 Push 하고 모든 프로젝트 참여자는 이 공식 저장소에서 반드시 Pull 해야 한다. 이러한 워크플로는 아래와 같다( Benevolent dictator workflow. ). 개발자는 코드를 수정하고 master 브랜치를 기준으로 자신의 토픽 브랜치를 Rebase 한다. 여기서 master 브랜치란 공식 저장소의 브랜치를 말한다. Lieutenant들은 개발자들의 수정사항을 자신이 관리하는 master 브랜치에 Merge 한다. Dictator는 Lieutenant의 master 브랜치를 자신의 master 브랜치로 Merge 한다. Dictator는 자신의 master 브랜치를 Push 하며 다른 모든 개발자는 Dictator의 master 브랜치를 기준으로 Rebase 한다. 그림 56. Benevolent dictator workflow. 이 방식이 일반적이지 않지만 깊은 계층 구조를 가지는 환경이나 규모가 큰 프로젝트에서는 매우 쓸모 있다. 프로젝트 리더가 모든 코드를 통합하기 전에 코드를 부분부분 통합하도록 여러 명의 Lieutenant에게 위임한다. 워크플로 요약 이 세 가지 워크플로가 Git 같은 분산 버전 관리 시스템에서 주로 사용하는 것들이다. 사실 이런 워크플로뿐만 아니라 다양한 변종 워크플로가 실제로 사용된다. 어떤 방식을 선택하고 혹은 조합해야 하는 지 살짝 감이 잡힐 것이다. 앞으로 몇 가지 구체적 사례를 들고 우리가 다양한 환경에서 각 역할을 어떻게 수행하는지 살펴본다. 이어지는 내용에서 프로젝트에 참여하고 기여할 때 작업 패턴이 어떠한지 몇 가지 살펴보기로 한다. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://git-scm.com/book/uk/v2/%d0%a0%d0%be%d0%b7%d0%bf%d0%be%d0%b4%d1%96%d0%bb%d0%b5%d0%bd%d0%b8%d0%b9-Git-%d0%a0%d0%be%d0%b7%d0%bf%d0%be%d0%b4%d1%96%d0%bb%d0%b5%d0%bd%d1%96-%d0%bf%d1%80%d0%be%d1%86%d0%b5%d1%81%d0%b8-%d1%80%d0%be%d0%b1%d0%be%d1%82%d0%b8 | Git - Розподілені процеси роботи About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 5.1 Розподілений Git - Розподілені процеси роботи Тепер, коли ви маєте віддалений Git репозиторій, налаштований як центральне місце, де всі розробники можуть ділитись своїм кодом, та знайомі з базовими командами Git в локальному процесі роботи, ви дізнаєтесь як використовувати деякі розподілені робочі процеси, що Git надає вам. В цьому розділі, ви побачите, як працювати з Git в розподіленому середовищі як учасник та інтегратор. Таким чином, ви дізнаєтесь, як успішно вносити код до проекту та зробити це якомога простішим для вас та супроводжувача, а також, як успішно супроводжувати проект з великою кількістю розробників. Розподілені процеси роботи На відміну від Централізованих Систем Керування Версіями (ЦСКВ), розподілена сутність Git дозволяє вам бути набагато більш гнучким щодо того, як розробники співпрацюють над проектами. У централізованих системах кожен розробник є одним з вузлів, які працюють більш менш на рівних над централізованим розподілювачем (hub). У Git, втім, кожен розробник є потенційно і вузлом, і сервером — тобто, кожен розробник може як надсилати код до інших репозиторіїв, як і супроводжувати публічний репозиторій, на якому інші можуть базувати свою роботу, та до якого вони можуть надсилати зміни. Це відкриває безмежні можливості процесу роботи для вашого проекту та/або вашої команди, отже розглянемо декілька поширених парадигм, щоб скористатись цією гнучкістю. Ми дізнаємось про переваги та можливі недоліки кожного методу; ви можете вибрати якийсь один, або змішати та сумістити елементи кожного. Централізований процес роботи У централізованих системах, взагалі існує єдина модель співпраці — централізований процес роботи. Один центральний розподілювач, або репозиторій , може приймати код, і всі синхронізують свою роботу з ним. Усі розробники є вузлами — споживачами цього розподілювача — та синхронізуються виключно з ним. Рисунок 53. Централізований порядок роботи. Це означає, що, якщо два розробники зроблять клон з розподілювача та обидвоє щось змінять, перший, хто надішле свої зміни назад, зможе це зробити без проблем. Другий розробник змушений зливати роботу першого до надсилання змін, щоб не переписати зміни першого розробника. Ця концепція працює в Git так само, як і в Subversion (чи будь-якій ЦСКВ), і ця модель чудово працює в Git. Якщо ви вже звикли до централізованого процесу роботи в компанії чи команді, то можете безклопітно продовжувати його використовувати з Git. Просто налаштуйте окреме сховище, та надайте всім у вашій команді доступ на запис; Git не дозволить користувачам переписувати один одного. Припустимо, Джон та Джесіка обидвоє починають працювати одночасно. Джон завершує свою зміну та надсилає її до сервера. Потім Джесіка намагається надіслати свої зміни, проте сервер відхиляє їх. Їй повідомляють, що вона намагається надіслати зміни, що не є перемотуванням вперед, та їх не можна надсилати, доки вона не отримає та не зіллє зміни. Цей процес роботи є принадним для багатьох, адже ж ця парадигма багато кому знайома та зручна. Вона також може використовуватись не лише маленькими командами. За допомогою моделі галуження Git, сотні розробників одночасно можуть її використовувати успішно для роботи над одним проектом за допомогою десятків гілок. Процес роботи з менеджером інтеграції Оскільки Git дозволяє вам мати декілька віддалених сховищ, можливо мати процес роботи, в якому кожен розробник має право на запис до власного публічного репозиторія та доступ на читання до репозиторіїв інших розробників. Цей сценарій зазвичай включає канонічне сховище, яке представляє ``офіційний'' проект. Щоб зробити внесок до такого проекту, треба створити власний публічний клон проекту та надіслати зміни до нього. Потім, ви можете надіслати запит до супроводжувача головного проекту, щоб він злив ваші зміни. Супроводжувач тоді може додати ваше сховище як віддалене, перевірити ваші зміни локально, злити їх до своєї гілки, та надіслати до свого репозиторія. Процес працює наступним чином (дивіться Процес роботи з менеджером інтеграції. ): Супроводжувач проекту надсилає зміни до свого власного репозиторія. Розробник клонує цей репозиторій та робить зміни. Розробник надсилає зміни до своєї власної публічної копії. Розробник надсилає супроводжувачу листа, в якому просить злити його зміни. Супроводжувач додає сховище розробника як віддалене та зливає зміни локально. Супроводжувач надсилає злиті зміни до головного репозиторія. Рисунок 54. Процес роботи з менеджером інтеграції. Це дуже поширений процес роботи для інструментів, що базуються на розподілювачах, таких як GitHub та GitLab, в яких дуже легко створити форк проекту та надсилати до нього зміни, які всі можуть бачити. Однією з головних переваг цього підходу є те, що ви можете продовжувати працювати, а супроводжувач головного репозиторія може злити ваші зміни будь-коли. Розробники не змушені чекати на проект, щоб вбудувати свої зміни — кожна сторона може працювати у своєму власному темпі. Процес роботи з диктатором та лейтенантами Це варіація процесу роботи з багатьма репозиторіями. Зазвичай він використовується у величезних проектах з сотнями учасників: одним славетним прикладом є ядро Linux. Різноманітні менеджери інтеграції відповідають за окремі частини репозиторія; їх називають лейтенантами . Всі лейтенанти мають одного менеджера інтеграції, відомого як доброзичливий диктатор. Доброзичливий диктатор надсилає зміни зі свого сховища до зразкового сховища, з якого всі розробники мають отримувати зміни. Процес працює наступним чином (дивіться Процес роботи з доброзичливим диктатором. ): Звичайні розробники працюють у власній тематичній гілці та перебазовують свою роботу поверх master . Тієї взірцевої гілки master , до якої диктатор надсилає зміни. Лейтенанти зливають тематичні гілки розробників до власних гілок master . Диктатор зливає гілки лейтенантів master до гілки диктатора master . Нарешті, диктатор надсилає цю гілку master до зразкового репозиторія, щоб інші розробники могли перебазуватись поверху неї. Рисунок 55. Процес роботи з доброзичливим диктатором. Такий процес роботи не є поширеним, проте може бути корисним у дуже великих проектах, або в дуже ієрархічних середовищах. Він дозволяє керівнику проекту (диктатору) делегувати чимало праці та збирати великі частини коду з декількох місць перед тим, як інтегрувати їх. Підсумок щодо процесів роботи Це деякі широковживані процеси роботи, які можливі в розподілених системах, таких як Git, проте, як ви бачите, існує багато можливостей, щоб влаштувати реальний процес роботи саме для вас. Тепер, коли ви (сподіваємось) можете визначити, яка комбінація процесів роботи спрацює для вас, ми розглянемо більш конкретні приклади того, як досягнути головних ролей, необхідних для різноманітних процесів. У наступній секції ви дізнаєтесь про декілька поширених шаблонів внесення змін до проекту. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://www.nec-labs.com/research/integrated-systems/ | Integrated Systems | NEC Labs America Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Research Overview Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications News Events Careers Overview Search Careers Intern Program About Overview Christopher White | President Office of the President NEC Corporation NEC Corporation of America NEC Research & Development Follow us on Social Media! Subscribe to our Newsletter Contact Click to open the search input field Click to open the search input field Search Menu Menu Integrated Systems We innovate, design, and prototype high-performance intelligent distributed systems, applications, and services on complex, large-scale communication networks. We develop wireless technologies for sensing the world, localizing critical assets, and improving the capacity, coverage, and scalability of communication networks. Link to: IS Projects PROJECTS Link to: IS People PEOPLE Link to: IS Publications PUBLICATIONS Link to: IS Patents PATENTS New application needs have always sparked human innovation. A decade ago, cloud computing enabled high-value enterprise services with a global reach and scale but with several minutes or seconds of delay. Large-scale services like enterprise resource planning (ERP) were a corner-case scenario, often designed as one-off systems. Today, applications like social networks, automated trading, and video streaming have made large-scale services the norm rather than the exception. In the future, advances in 5G networks and an explosion in smart devices, microservices, databases, networking, and computing tiers will make services so complex that humans cannot tune or manage them. The sheer scale, dynamic nature, and concurrency in services on 5G slices will require them to be intelligent and autonomic. They will need to continuously self-assess, learn, and automatically adjust for resource needs, data quality, and service reliability. The need for increased efficiency and reduced latency between measurement and action drives our design of real-time distributed systems for feature extraction, computation, and machine learning on multimodal streaming data. We are conducting extensive research on creating end-to-end solutions using multimodal sensing technologies in the retail, public safety, and transportation domains. Our 5G cellular network research encompasses the development of technologies on the Radio Access Network (RAN), the mobile edge, and the 5G LAN. Within the RAN, we are developing technologies that optimize massive MIMO/MU-MIMO deployments and millimeter-wave access (e.g., transmission at 28 GHz to nomadic/mobile users). At the mobile edge (MEC), we focus on virtualization, scalability, and cloud deployment of appropriate services. Our 5G LAN research extends the benefits of 5G slicing technology to enterprise LANs to position the enterprise as the new MEC. Want to learn more about our integrated systems department? Meet our team of experts , check out our blog posts , or read our latest publications . Join Us Are you interested in joining us? We seek the next generation of thought leaders in integrated systems for researcher positions. Outstanding applicants pursuing a career in all areas of integrated systems are encouraged to visit our careers page to learn more and to apply for our available positions . Summer 2026 Internship Applications will open in Fall 2025! Check back this fall for exciting internship opportunities for Summer 2026. We will be looking for students pursuing advanced degrees in Computer Science and Electrical Engineering. Internships are typically 3 months long during the summer. The benefits of working for us include the opportunity to quickly become part of a project team applying cutting-edge technology to industry-leading concepts. To learn more about our Summer Internships, visit our Internship page. Featured Integrated Systems Research Projects Link to: Self-Optimizing 5G Applications in Network Slices Self-Optimizing 5G Applications in Network Slices A decade ago, large-scale services like enterprise resource planning (ERP) were a corner-case scenario, often designed as one-off systems. Today, applications like social networks, automated trading and video streaming have made large-scale services the norm rather than the exception. READ MORE Link to: Real-Time, Distributed Stream Processing Real-Time, Distributed Stream Processing New application needs have always sparked human innovation. A decade ago, cloud computing enabled high-value enterprise services with a global reach and scale, but with several minutes or seconds of delay. READ MORE Link to: NavigateIO NavigateIO NavigateIO tracks first responders in precarious situations by leveraging the ultra wide-band (UWB) technology, fusing it with inertial sensors to accomplish this objective directly from outside, without relying on access to any indoor infrastructure. READ MORE Contact Us Princeton Office 4 Independence Way, Suite 200 Princeton, NJ 08540 +1 609-520-1555 San Jose Office 2033 Gateway Place, Suite 200 San Jose, CA 95110 +1 408-863-6007 About Us NEC Laboratories America, Inc. (NEC Labs) is the US-based center for NEC Corporation’s global network of corporate research laboratories. Our diverse research groups collaborate with industry, academia and governments to provide disruptive solutions to complex problems. A leader in the integration of IT and network technologies with more than 100 years of expertise, NEC provides a combination of products and solutions that cross-utilize the company’s experience and global resources to meet the complex and ever-changing needs of its customers. Our Pages Home Research Departments Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Patents Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing News Events About Us Christopher White | President Office of the President NEC Corporation Subscribe to our Newsletter Careers Intern Program Contact Us Recent Publications Quantitative Bounds for Length Generalization in Transformers Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing SlideCraft: Context-aware Slides Generation Agent TalentScout: Multimodal AI-Driven Expert Finding in Organizations AutoScape: Geometry-Consistent Long-Horizon Scene Generation DWIM: Towards Tool-aware Visual Reasoning via Discrepancy-aware Workflow Generation & Instruct-Masking Tuning Mapillary Vistas Validation for Fine-Grained Traffic Signs: A Benchmark Revealing Vision-Language Model Limitations LANGTRAJ: Diffusion Model and Dataset for Language-Conditioned Trajectory Simulation DiscussLLM: Teaching Large Language Models When to Speak Bifröst: Peer-to-peer Load-balancing for Function Execution in Agentic AI Systems Harnessing Vision Models for Time Series Analysis: A Survey Multi-modal Time Series Analysis: A Tutorial and Survey ICeTEA: Mixture of Detectors for Metric-Log Anomaly Detection Roadside Multi-LiDAR Data Fusion for Enhanced Traffic Safety Identifying Combinatorial Regulatory Genes for Cell Fate Decision via Reparameterizable Subset Explanations On Synthesizing Data for Context Attribution in Question Answering Feasibility study on scour monitoring for subsea cables of offshore wind turbines using distributed fiber optic sensors Group Relative Augmentation for Data Efficient Action Detection Uncertainty Propagation on LLM Agent Exploring Multi-Modal Data with Tool-Augmented LLM Agents for Precise Causal Discovery EcoDoc: A Cost-Efficient Multimodal Document Processing System for Enterprises Using LLMs Integration of Fiber Optic Sensing and Sparse Grid Sensors for Accurate Fault Localization in Distribution Systems XPF: Agentic AI System for Business Workflow Automation Quantitative Bounds for Length Generalization in Transformers Re-ranking the Context for Multimodal Retrieval Augmented Generation Beyond the Permutation Symmetry of Transformers: The Role of Rotation for Model Fusion PPDiff: Diffusing in Hybrid Sequence-Structure Space for Protein-Protein Complex Design Pathologist-Read vs AI-Driven Assessment of Tumor-Infiltrating Lymphocytes in Melanoma AutoScape: Geometry-Consistent Long-Horizon Scene Generation Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Kunal Rao presents SlideCraft: Context-Aware Slides Generation Agent at PICom 2025 on October 21st NECLA at ECOC 2025: Advancing Optical Communication and Distributed Sensing News NEC Laboratories America 2025: A Year of Disruptive Innovation Apply for a Summer 2026 Internship NEC Laboratories America: Celebrating 23 Years of Research Innovation! Summer Highlights at NEC Labs America: Teamwork, Innovation, and Fun Graph Neural Networks, Explained: Our Role in the Future of AI Shaping the Future with Responsible AI, Collaboration, and Disruption Top 10 Most Legendary College Pranks of All-Time for April Fools’ Day Introducing the Trustworthy Generative AI Project: Pioneering the Future of Compositional Generation and Reasoning Introducing Our New Project: Time Series Language Model for Explainable AI The Evolution of Disciplines: From Experimental Roots to Theoretical Frameworks Agentic LLMs for AI Orchestration Project: Revolutionizing Complex Workflows Multi-Agent Simulator for Carbon Neutrality: The Technology the World Has Been Waiting For NEC Laboratories Advances Material Design with AI-based MateriAI Platform Unearthing Nature’s Orchestra – How Fiber Optic Cables Can Hear Cicada Secrets © Copyright 2025 NEC Labs America | All Rights Reserved | Privacy Policy | Global Privacy Policy Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Home Research Departments Publications Patents News Events About Us Careers Contact Us Scroll to top Scroll to top Scroll to top | 2026-01-13T09:29:40 |
https://support.microsoft.com/fi-fi/microsoft-store-and-billing | Microsoft Store ja laskutusohje Siirry pääsisältöön Microsoft Tuki Tuki Tuki Aloitussivu Microsoft 365 Office Tuotteet Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows lisää ... Laitteet Surface Tietokoneiden lisälaitteet Xbox PC-pelit HoloLens Surface Hub Laitteistotakuut Tili ja laskutus Tili Microsoft Store ja laskutus Resurssit Uudet ominaisuudet Yhteisön keskustelupalstat Microsoft 365 -järjestelmänvalvojat Pienyritysportaali Kehittäjä Koulutus Ilmoita tuen huijauksesta Tuotteen turvallisuus Lisää Osta Microsoft 365 Kaikki Microsoftin tuotteet Global Microsoft 365 Teams Copilot Windows Surface Xbox Erikoistarjoukset Pienyritykset Tuki Ohjelmistot Ohjelmistot Windows-sovellukset Tekoäly OneDrive Outlook Siirtyminen Skypesta Teamsiin OneNote Microsoft Teams Tietokoneet ja laitteet Tietokoneet ja laitteet Osta Xbox-tuotteita Kaikki lisätarvikkeet Viihde Viihde Xbox Game Pass Ultimate Xbox-pelit PC-pelit Yritykset Yritykset Microsoft Security Azure Dynamics 365 Microsoft 365 yrityksille Microsoft Industry Microsoft Power Platform Windows 365 Kehittäjät ja IT Kehittäjät ja IT Microsoft-kehittäjät Microsoft Learn Marketplacen tekoälysovellusten tuki Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Muut Muut Ilmaiset lataukset ja tietoturva Opetus Microsoftin lahjakortit Volyymikäyttöoikeudet Näytä sivustokartta Haku Etsi ohjeita Ei tuloksia Peruuta Kirjaudu sisään Kirjaudu sisään Microsoft-tilillä Kirjaudu sisään tai luo tili. Hei, Käytä toista tiliä. Sinulla on useita tilejä Valitse tili, jolla haluat kirjautua sisään. Microsoft Store ja laskutusohje Hallitse tilauksia Palauttaa & hyvitykset Maksuvaihtoehtoja Tilaushistoria Lahjakortit Asenna Microsoft 365 Microsoft Store Windowsissa Tutustu Microsoft Storen palveluihin Maksuttomasta toimituksesta ja palautuksista 60 päivän hintasuojaukseen autamme sinua tekemään enemmän luokkansa parhaiden laitteiden, ohjelmistojen, pelien ja resurssien kanssa. Tutustu Siihen, mitä Microsoft Store tarjoaa: Ostosten ja ostojen tuki | Tuotteen määrittäminen ja koulutus | Pienyritysten tuki Ostosten ja ostojen tuki Microsoft Storen palvelut eivät ole käytettävissä kaikilla alueilla. Jos haluat nähdä käytettävissä olevat vaihtoehdot, valitse maasi tai alueesi alla olevasta avattavasta luettelosta ja jos sitä ei ole luettelossa, valitse Muut alueet . Valitse alueesi Yhdysvallat Australia Kanada (englanti) Kanada (ranska) Yhdistynyt kuningaskunta Muut alueet Miksi tehdä ostoksia Microsoft Storessa Helppo ja kätevä ostos Ilmainen 2–3 päivän toimitus Ilmaiset 60 päivän palautukset 60 päivän hintasuoja Joustavat maksutavat Käytetyn laitteen käteinen Vaihto ja kierrätys Erikoisalennukset ja tarjoukset Opiskelijoille, vanhemmille ja opettajille Sotilashenkilöstölle Laajennettu laitesuojaus Microsoft Complete Protection -palvelupaketti Autamme sinua löytämään tarvitsemasi Myyntituen ohje Aputoimintojen answer desk Osta ASL-kumppanin kanssa Miksi tehdä ostoksia Microsoft Storessa Helppo ja kätevä ostos Maksuton toimitus Ilmaiset 60 päivän palautukset 60 päivän hintasuoja Käytetyn laitteen käteinen Vaihto ja kierrätys Erikoisalennukset ja tarjoukset Opiskelijoille, vanhemmille ja opettajille Autamme sinua löytämään tarvitsemasi Myyntituen ohje Aputoimintojen answer desk Miksi tehdä ostoksia Microsoft Storessa Helppo ja kätevä ostos Maksuton toimitus Ilmaiset 60 päivän palautukset 60 päivän hintasuoja Käytetyn laitteen käteinen Vaihto ja kierrätys Erikoisalennukset ja tarjoukset Opiskelijoille, vanhemmille ja opettajille Laajennettu laitesuojaus Microsoft Complete Protection -palvelupaketti Autamme sinua löytämään tarvitsemasi Jos sinulla on kysyttävää ennen ostamista, keskustele tuoteasiantuntijan kanssa tai varaa ostostapaaminen. Myyntituen ohje Miksi tehdä ostoksia Microsoft Storessa Helppo ja kätevä ostos Maksuton toimitus Ilmaiset 60 päivän palautukset 60 päivän hintasuoja Käytetyn laitteen käteinen Vaihto ja kierrätys Erikoisalennukset ja tarjoukset Opiskelijoille, vanhemmille ja opettajille Laajennettu laitesuojaus Microsoft Complete Protection -palvelupaketti Miksi tehdä ostoksia Microsoft Storessa Helppo ja kätevä ostos Maksuton toimitus Ilmaiset 60 päivän palautukset 60 päivän hintasuoja Käytetyn laitteen käteinen Vaihto ja kierrätys Erikoisalennukset ja tarjoukset Opiskelijoille, vanhemmille ja opettajille Autamme sinua löytämään tarvitsemasi Myyntituen ohje Aputoimintojen answer desk Miksi tehdä ostoksia Microsoft Storessa Autamme sinua löytämään tarvitsemasi Jos sinulla on kysyttävää ennen ostamista, keskustele tuoteasiantuntijan kanssa. Myyntituen ohje Selaa Microsoft Storea The Microsoft Store Tuotteen määrittäminen ja koulutus Kaikki tässä luetellut Microsoft Store -palvelut eivät ole käytettävissä kaikilla alueilla. Jos haluat nähdä vaihtoehdot, valitse maasi tai alueesi alla olevasta avattavasta luettelosta: Valitse alueesi Yhdysvallat Australia Kanada (englanti) Kanada (ranska) Yhdistynyt kuningaskunta Muut alueet Ohje- ja oppimisresurssit Tutustu tuotetukiresursseihin, joiden avulla löydät tarvitsemasi vastaukset. Surface-laitteet | Xbox Microsoft 365 | Windows Ohje- ja oppimisresurssit Tuotetukiresurssimme auttavat sinua löytämään tarvitsemasi vastaukset. Surface-laitteet | Xbox Microsoft 365 | Windows Ohje- ja oppimisresurssit Tutustu tuotetukiresursseihin, joiden avulla löydät tarvitsemasi vastaukset. Surface-laitteet | Xbox Microsoft 365 | Windows Ohje- ja oppimisresurssit Tutustu tuotetukiresursseihin, joiden avulla löydät tarvitsemasi vastaukset. Surface-laitteet | Xbox Microsoft 365 | Windows Ohje- ja oppimisresurssit Tutustu tuotetukiresursseihin, joiden avulla löydät tarvitsemasi vastaukset. Surface-laitteet | Xbox Microsoft 365 | Windows Ohje- ja oppimisresurssit Tutustu tuotetukiresursseihin, joiden avulla löydät tarvitsemasi vastaukset. Surface-laitteet | Xbox Microsoft 365 | Windows Pienyritysten tuki Jos haluat nähdä, mitä pienyritysten tukivaihtoehtoja alueellasi on käytettävissä, valitse maasi tai alueesi alla olevasta avattavasta luettelosta: Valitse alueesi Yhdysvallat Australia Kanada (englanti) Kanada (ranska) Yhdistynyt kuningaskunta Muut alueet Resursseja pienyrityksellesi Hanki neuvoja, maksutonta koulutusta, tuotteita ja työkaluja, jotka auttavat yritystäsi menestymään. Pienyritysten ohje ja oppiminen Pienyrityksen resurssikeskus Resursseja pienyrityksellesi Hanki neuvoja, maksutonta koulutusta, tuotteita ja työkaluja, jotka auttavat yritystäsi menestymään. Pienyritysten ohje ja oppiminen Pienyrityksen resurssikeskus Resursseja pienyrityksellesi Hanki neuvoja, maksutonta koulutusta, tuotteita ja työkaluja, jotka auttavat yritystäsi menestymään. Pienyritysten ohje ja oppiminen Pienyritysten resurssikeskus Resursseja pienyrityksellesi Yrityksesi tarpeiden arvioimisesta ja asennuksen ja vianmäärityksen avustamisesta olemme täällä auttamassa. Hanki neuvoja, maksutonta koulutusta, tuotteita ja työkaluja, jotka auttavat yritystäsi menestymään. Pienyritysten ohjeet ja koulutus Pienyritysten resurssikeskus Resursseja pienyrityksellesi Hanki neuvoja, maksutonta koulutusta, tuotteita ja työkaluja, jotka auttavat yritystäsi menestymään. Pienyritysten ohje ja oppiminen Pienyrityksen resurssikeskus Resursseja pienyrityksellesi Hanki neuvoja, maksutonta koulutusta, tuotteita ja työkaluja, jotka auttavat yritystäsi menestymään. Pienyritysten ohje ja oppiminen Uutuudet Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot organisaatioille Copilot henkilökohtaiseen käyttöön Microsoft 365 Tutustu Microsoftin tuotteisiin Windows 11 -sovellukset Microsoft Store Tiliprofiili Latauskeskus Microsoft Storen tuki Palautukset Tilausseuranta Kierrätys Kaupalliset takuut Opetus Microsoft Education Laitteet opetukseen Microsoft Teams for Education Microsoft 365 Education Office Education Educator-koulutus ja -kehitys Tarjoukset opiskelijoille ja vanhemmille Azure opiskelijoille Yritykset Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Pienyritykset Kehittäjät ja IT Microsoft-kehittäjät Microsoft Learn Marketplacen tekoälysovellusten tuki Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Yritys Työpaikat Tietoja Microsoftista Yritysuutiset Microsoftin tietosuoja Sijoittajat Kestävyys Suomi (Suomi) Tietosuojavaihtoehtojen kieltäytymiskuvake Tietosuojaa koskevat valintasi Tietosuojavaihtoehtojen kieltäytymiskuvake Tietosuojaa koskevat valintasi Kuluttajien terveystietojen tietosuoja Ota yhteyttä Microsoftiin Tietosuoja Hallitse evästeitä Käyttöluvat Tavaramerkit Tietoja mainoksista EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:40 |
https://support.microsoft.com/fr-fr/office/qu-est-ce-que-shifts-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Qu’est-ce que Shifts? - Support Microsoft Rubriques connexes × Formation vidéo Microsoft Teams Guide de démarrage rapide de Microsoft Teams Qu’est-ce que Microsoft Teams ? Se connecter et commencer Discuter et partager des fichiers Collaborer En savoir plus Présentation de Microsoft Teams Prise en main de Microsoft Teams Prise en main des conversations Démarrer avec les réunions Démarrer avec les applications Configurer et personnaliser votre équipe Créer une équipe avec des modèles Travailler avec des invités externes Gérer les paramètres des équipes Collaborer en équipes et en canaux Conseil : envoyer un e-mail à un canal Créer un plan avec le Planificateur Utiliser les billets et les messages Publier un message sur plusieurs canaux Rechercher et trouver des fichiers Charger et partager des fichiers Rechercher et filtrer des personnes et des fichiers Rechercher et filtrer des messages Conseils pour les fichiers Teams Démarrer des conversations et des appels Vue d’ensemble des appels Teams Passer des appels Conseils pour les appels dans Teams Masquer les conversations, supprimer les messages Configurer un délégué pour gérer vos appels Gérer les réunions Rejoindre une réunion Teams Conseils relais aux réunions Teams Se réunir instantanément Gérer les réunions Planifier un webinaire Afficher votre écran lors d’une réunion Mettre en place et rejoindre des événements en direct Organiser et planifier un événement en direct Produire un événement en direct Participer à un événement en direct Modérer une session de questions et réponses Explorer les applications et les outils Rechercher et utiliser des applications Gérer les plannings d’équipe avec Shifts Qu’est-ce que Shifts ? Créer un planning Shifts Gérer un planning Shifts Créer des autorisations Qu'est-ce que c’est Approvals ? Créer une approbation Créer une approbation à partir de la conversation Créer une approbation de signature électronique Découvrez des modèles dans Approbations Créer des approbations avec des modèles Créer des modèles à l’échelle de l’organisation Rendez-vous virtuels dans Microsoft Bookings Que sont les rendez-vous virtuels ? Envoyer des notifications SMS d’invités externes Mener un rendez-vous Rejoindre un rendez-vous Gérer votre flux d’activité Gérer les paramètres de notification Teams en déplacement Commencer une conversation en déplacement Créer un canal avec l’application mobile Teams Rejoindre une réunion en déplacement Flux d’activités en déplacement Passer directement au contenu principal Microsoft Assistance Assistance Assistance Accueil Microsoft 365 Office Support Teams Rubriques Réunions Conversation Paramètres des& notifications Équipes et canaux Appels & appareils Fichiers Applications & services Démarrage rapide Conversation Conversation de groupe Notifications Teams Canaux Appels Fichiers Applications Composants Loop Nouveautés Ressources Vidéo de formation Résoudre des problèmes Ici dans Teams Accessibilité Fonctionnalités Teams par plate-forme Microsoft Teams (gratuit) Forums de la communauté Blog de la communauté technique Formation dispensée par un instructeur Pour les administrateurs et les informaticiens Pour l’éducation Plus Acheter Microsoft 365 Tout Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Offres spéciales TPE & PME Support technique Logiciels Logiciels Applications Windows IA OneDrive Outlook Passage de Skype à Teams OneNote Microsoft Teams PC et appareils PC et appareils Découvrir la gamme Xbox Accessoires VR et réalité mixte Divertissement Divertissement Xbox Game Pass Ultimate Xbox et jeux Jeux PC Entreprises Entreprises Sécurité Microsoft Azure Dynamics 365 Microsoft 365 pour les entreprises Microsoft Industry Microsoft Power Platform Windows 365 Développeurs & IT Développeurs & IT Développeur Microsoft Microsoft Learn Prise en charge des applications du marketplace d’IA Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Autres Autres Microsoft Rewards Téléchargements gratuits et pour la sécurité Éducation Cartes cadeaux Licences Vue plan de site Rechercher Demander de l’aide Aucun résultat Annuler Se connecter Se connecter avec Microsoft S'identifier ou créer un compte. Bonjour, Sélectionnez un autre compte. Vous avez plusieurs comptes Choisissez le compte avec lequel vous voulez vous connecter. Rubriques connexes Formation vidéo Microsoft Teams Guide de démarrage rapide de Microsoft Teams Qu’est-ce que Microsoft Teams ? Se connecter et commencer Discuter et partager des fichiers Collaborer En savoir plus Présentation de Microsoft Teams Prise en main de Microsoft Teams Prise en main des conversations Démarrer avec les réunions Démarrer avec les applications Configurer et personnaliser votre équipe Créer une équipe avec des modèles Travailler avec des invités externes Gérer les paramètres des équipes Collaborer en équipes et en canaux Conseil : envoyer un e-mail à un canal Créer un plan avec le Planificateur Utiliser les billets et les messages Publier un message sur plusieurs canaux Rechercher et trouver des fichiers Charger et partager des fichiers Rechercher et filtrer des personnes et des fichiers Rechercher et filtrer des messages Conseils pour les fichiers Teams Démarrer des conversations et des appels Vue d’ensemble des appels Teams Passer des appels Conseils pour les appels dans Teams Masquer les conversations, supprimer les messages Configurer un délégué pour gérer vos appels Gérer les réunions Rejoindre une réunion Teams Conseils relais aux réunions Teams Se réunir instantanément Gérer les réunions Planifier un webinaire Afficher votre écran lors d’une réunion Mettre en place et rejoindre des événements en direct Organiser et planifier un événement en direct Produire un événement en direct Participer à un événement en direct Modérer une session de questions et réponses Explorer les applications et les outils Rechercher et utiliser des applications Gérer les plannings d’équipe avec Shifts Qu’est-ce que Shifts ? Créer un planning Shifts Gérer un planning Shifts Créer des autorisations Qu'est-ce que c’est Approvals ? Créer une approbation Créer une approbation à partir de la conversation Créer une approbation de signature électronique Découvrez des modèles dans Approbations Créer des approbations avec des modèles Créer des modèles à l’échelle de l’organisation Rendez-vous virtuels dans Microsoft Bookings Que sont les rendez-vous virtuels ? Envoyer des notifications SMS d’invités externes Mener un rendez-vous Rejoindre un rendez-vous Gérer votre flux d’activité Gérer les paramètres de notification Teams en déplacement Commencer une conversation en déplacement Créer un canal avec l’application mobile Teams Rejoindre une réunion en déplacement Flux d’activités en déplacement Qu’est-ce que Shifts? S’applique à Teams Microsoft Teams Essayez ! L’application Shifts dans Microsoft Teams est un outil de gestion de planification et de suivi du temps qui vous aide à créer, mettre à jour et gérer des planifications pour votre équipe. Planifications : créez, modifiez et gérez une planification pour votre équipe. Une planification Shifts affiche les jours en haut, les membres de l’équipe apparaissent à gauche et les équipes affectées apparaissent dans le calendrier. Paramètres de planification : dans Paramètres shift, définissez les options de planification et choisissez les fonctionnalités Shifts que vous souhaitez mettre à la disposition de votre équipe. Groupes : ajoutez des groupes de planification pour organiser les membres de l’équipe dans la planification par type de travail ou emplacement. Shifts : affectez des shifts aux membres de l’équipe. Créez un décalage à partir de zéro ou copiez-en un existant. Ouvrir les shifts : chaque groupe de la planification a une ligne Ouvrir les shifts . Ajoutez des shifts ouverts à votre planning, disponibles pour tout le monde. Horloge : activez l’horloge horaire dans les paramètres Maj pour permettre à votre équipe d’entrer et de sortir des quarts de travail. Demandes : passez en revue et répondez aux demandes de congé, d’ouverture de quarts de travail, d’échange de quarts de travail et d’offres. Étiquettes : utilisez des étiquettes basées sur les décalages pour communiquer rapidement avec toute personne actuellement sur shift. Publier votre planification : lorsque vous avez terminé d’apporter des modifications à la planification, partagez-la avec votre équipe afin que tout le monde soit à jour. Vous souhaitez en savoir plus ? Prise en main de Shifts Créer une planification d’équipe dans Shifts Ajouter des shifts à la planification dans Shifts Publier une planification dans Shifts Gérer les demandes de shift et les congés dans Shifts Activer les balises basées sur les shifts dans Teams ABONNER LES FLUX RSS Besoin d’aide ? Vous voulez plus d’options ? Découvrir Communauté Explorez les avantages de l’abonnement, parcourez les cours de formation, découvrez comment sécuriser votre appareil, etc. Avantages de l’abonnement Microsoft 365 Formation Microsoft 365 Sécurité Microsoft Centre d’accessibilité Les communautés vous permettent de poser des questions et d'y répondre, de donner vos commentaires et de bénéficier de l'avis d'experts aux connaissances approfondies. Demandez à la Communauté Microsoft Communauté technique Microsoft Windows Insiders Microsoft 365 Insiders Ces informations vous ont-elles été utiles ? Oui Non Merci. Avez-vous d’autres commentaires à partager avec Microsoft ? Pouvez-vous nous aider à nous améliorer ? (Envoyez des commentaires à Microsoft pour que nous puissions vous aider.) Dans quelle mesure êtes-vous satisfait(e) de la qualité de la langue ? Qu’est-ce qui a affecté votre expérience ? J’ai résolu mon problème Instructions claires Les instructions sont faciles à suivre Aucun terme n’est difficile à comprendre Les images sont utiles Qualité de la traduction Les images ne correspondent pas à mon écran Les instructions sont incorrectes Les instructions sont trop techniques Les informations sont insuffisantes Il n’y a pas assez d’images Qualité de la traduction Avez-vous d’autres commentaires ? (Facultatif) Envoyer les commentaires En cliquant sur Envoyer, vos commentaires seront utilisés pour améliorer les produits et services de Microsoft. Votre administrateur informatique sera en mesure de collecter ces données. Déclaration de confidentialité. Nous vous remercions de vos commentaires. × Nouveautés Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot pour les organisations Copilot pour une utilisation personnelle Microsoft 365 Découvrir les produits Microsoft Applications Windows 11 Microsoft Store Profil du compte Centre de téléchargement Support du Microsoft Store Retours Suivi des commandes Recycler Garanties Éducation Microsoft Éducation Appareils pour l’enseignement Microsoft Teams pour l’éducation Microsoft 365 Éducation Office Éducation Formation et développement des enseignants Offres pour étudiants et parents Azure pour les étudiants Entreprises Sécurité Microsoft Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams TPE & PME Développeur et IT Développeur Microsoft Microsoft Learn Prise en charge des applications du marketplace d’IA Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Société Emploi Actualités de la société Confidentialité chez Microsoft Investisseurs Durabilité Français (France) Vos choix en matière de confidentialité – Icône Désactiver Vos choix de confidentialité Vos choix en matière de confidentialité – Icône Désactiver Vos choix de confidentialité Confidentialité de l’intégrité des consommateurs Contacter Microsoft Gérer ou annuler l’abonnement Mentions légales et Informations consommateurs Confidentialité Gérer les cookies Conditions d'utilisation Conditions générales de vente Marques À propos de nos annonces EU Compliance DoCs Accessibilité © Microsoft 2026 | 2026-01-13T09:29:40 |
https://www.nec-labs.com/research/ | Research Departments | NEC Labs America Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Research Overview Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications News Events Careers Overview Search Careers Intern Program About Overview Christopher White | President Office of the President NEC Corporation NEC Corporation of America NEC Research & Development Follow us on Social Media! Subscribe to our Newsletter Contact Click to open the search input field Click to open the search input field Search Menu Menu Research We take a multidisciplinary approach to a broad range of research areas. On joint projects, we leverage complementary research across NEC and partner organizations. Areas of Research We aim to build novel big-data solutions and service platforms to simplify complex systems management. We also develop new information technology that supports innovative applications, from big data analytics to the Internet of Things. We innovate, design, and prototype high-performance intelligent distributed systems, applications, and services on communication networks like 5G and beyond. We develop next-generation wireless technologies for sensing the world and improving communication networks. Machine learning is the key technology for data analytics and artificial intelligence. Recent progress in this field opens opportunities for a wide variety of new applications. As leaders in the industry, we develop innovative technologies which are integrated into NEC’s products and services. We solve fundamental challenges in computer vision, with a focus on understanding and interaction in 3D scenes, representation learning in visual and multimodal data, learning across domains and tasks, as well as responsible AI. In the optical networking and sensing department, we are leading world-class optics research into the next-generation of optical networks and sensing systems that will power ICT-based social solutions for years to come. Contact Us Princeton Office 4 Independence Way, Suite 200 Princeton, NJ 08540 +1 609-520-1555 San Jose Office 2033 Gateway Place, Suite 200 San Jose, CA 95110 +1 408-863-6007 About Us NEC Laboratories America, Inc. (NEC Labs) is the US-based center for NEC Corporation’s global network of corporate research laboratories. Our diverse research groups collaborate with industry, academia and governments to provide disruptive solutions to complex problems. A leader in the integration of IT and network technologies with more than 100 years of expertise, NEC provides a combination of products and solutions that cross-utilize the company’s experience and global resources to meet the complex and ever-changing needs of its customers. Our Pages Home Research Departments Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Patents Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing News Events About Us Christopher White | President Office of the President NEC Corporation Subscribe to our Newsletter Careers Intern Program Contact Us Recent Publications Quantitative Bounds for Length Generalization in Transformers Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing SlideCraft: Context-aware Slides Generation Agent TalentScout: Multimodal AI-Driven Expert Finding in Organizations AutoScape: Geometry-Consistent Long-Horizon Scene Generation DWIM: Towards Tool-aware Visual Reasoning via Discrepancy-aware Workflow Generation & Instruct-Masking Tuning Mapillary Vistas Validation for Fine-Grained Traffic Signs: A Benchmark Revealing Vision-Language Model Limitations LANGTRAJ: Diffusion Model and Dataset for Language-Conditioned Trajectory Simulation DiscussLLM: Teaching Large Language Models When to Speak Bifröst: Peer-to-peer Load-balancing for Function Execution in Agentic AI Systems Harnessing Vision Models for Time Series Analysis: A Survey Multi-modal Time Series Analysis: A Tutorial and Survey ICeTEA: Mixture of Detectors for Metric-Log Anomaly Detection Roadside Multi-LiDAR Data Fusion for Enhanced Traffic Safety Identifying Combinatorial Regulatory Genes for Cell Fate Decision via Reparameterizable Subset Explanations On Synthesizing Data for Context Attribution in Question Answering Feasibility study on scour monitoring for subsea cables of offshore wind turbines using distributed fiber optic sensors Group Relative Augmentation for Data Efficient Action Detection Uncertainty Propagation on LLM Agent Exploring Multi-Modal Data with Tool-Augmented LLM Agents for Precise Causal Discovery EcoDoc: A Cost-Efficient Multimodal Document Processing System for Enterprises Using LLMs Integration of Fiber Optic Sensing and Sparse Grid Sensors for Accurate Fault Localization in Distribution Systems XPF: Agentic AI System for Business Workflow Automation Quantitative Bounds for Length Generalization in Transformers Re-ranking the Context for Multimodal Retrieval Augmented Generation Beyond the Permutation Symmetry of Transformers: The Role of Rotation for Model Fusion PPDiff: Diffusing in Hybrid Sequence-Structure Space for Protein-Protein Complex Design Pathologist-Read vs AI-Driven Assessment of Tumor-Infiltrating Lymphocytes in Melanoma AutoScape: Geometry-Consistent Long-Horizon Scene Generation Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Kunal Rao presents SlideCraft: Context-Aware Slides Generation Agent at PICom 2025 on October 21st NECLA at ECOC 2025: Advancing Optical Communication and Distributed Sensing News NEC Laboratories America 2025: A Year of Disruptive Innovation Apply for a Summer 2026 Internship NEC Laboratories America: Celebrating 23 Years of Research Innovation! Summer Highlights at NEC Labs America: Teamwork, Innovation, and Fun Graph Neural Networks, Explained: Our Role in the Future of AI Shaping the Future with Responsible AI, Collaboration, and Disruption Top 10 Most Legendary College Pranks of All-Time for April Fools’ Day Introducing the Trustworthy Generative AI Project: Pioneering the Future of Compositional Generation and Reasoning Introducing Our New Project: Time Series Language Model for Explainable AI The Evolution of Disciplines: From Experimental Roots to Theoretical Frameworks Agentic LLMs for AI Orchestration Project: Revolutionizing Complex Workflows Multi-Agent Simulator for Carbon Neutrality: The Technology the World Has Been Waiting For NEC Laboratories Advances Material Design with AI-based MateriAI Platform Unearthing Nature’s Orchestra – How Fiber Optic Cables Can Hear Cicada Secrets © Copyright 2025 NEC Labs America | All Rights Reserved | Privacy Policy | Global Privacy Policy Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Home Research Departments Publications Patents News Events About Us Careers Contact Us Scroll to top Scroll to top Scroll to top | 2026-01-13T09:29:40 |
https://git-scm.com/book/gr/v2/%ce%9a%ce%b1%cf%84%ce%b1%ce%bd%ce%b5%ce%bc%ce%b7%ce%bc%ce%ad%ce%bd%ce%bf-Git-%ce%9a%ce%b1%cf%84%ce%b1%ce%bd%ce%b5%ce%bc%ce%b7%ce%bc%ce%ad%ce%bd%ce%b5%cf%82-%cf%81%ce%bf%ce%ad%cf%82-%ce%b5%cf%81%ce%b3%ce%b1%cf%83%ce%af%ce%b1%cf%82 | Git - Κατανεμημένες ροές εργασίας About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 5.1 Κατανεμημένο Git - Κατανεμημένες ροές εργασίας Τώρα που έχετε εγκαταστήσει ένα απομακρυσμένο αποθετήριο Git ως ένα σημείο στο οποίο όλοι οι προγραμματιστές θα μοιράζονται τον κώδικά τους και είστε εξοικειωμένοι με τις βασικές εντολές του Git όσον αφορά σε τοπικές ροές εργασίας, θα εξετάσετε πώς να χρησιμοποιείτε ορισμένες από τις κατανεμημένες ροές εργασίας που σας προσφέρει το Git. Σε αυτό το κεφάλαιο, θα δείτε πώς να συνεργαστείτε με το Git σε ένα κατανεμημένο περιβάλλον ως συνεργάτες και ως υπεύθυνοι ενσωμάτωσης. Δηλαδή, θα μάθετε πώς να συνεισφέρετε με επιτυχία κώδικα σε ένα έργο και πώς να το κάνετε κατά το δυνατό ευκολότερο τόσο για εσάς τους ίδιους όσο και για τον διαχειριστή του έργου και επίσης θα δείτε πώς να διαχειρίζεστε με επιτυχία ένα έργο με πολλούς συνεισφέροντες. Κατανεμημένες ροές εργασίας Σε αντίθεση με τα Συγκεντρωτικά Συστήματα Ελέγχου Έκδοσεων (CVCS), η κατανεμημένη φύση του Git μας επιτρέπει να είμαστε πολύ πιο ευέλικτοι όσον αφορά στη συνεργασία των προγραμματιστών στο πλαίσιο ενός έργου. Στα συγκεντρωτικά συστήματα κάθε προγραμματιστής είναι ένας κόμβος που συνεργάζεται λίγο πολύ εξίσου με έναν κεντρικό κόμβο (hub). Ωστόσο, στο Git, κάθε προγραμματιστής είναι δυνητικά τόσο κόμβος όσο και κεντρικό σημείο — δηλαδή, κάθε προγραμματιστής μπορεί να συνεισφέρει κώδικα σε άλλα αποθετήρια και να διαχειρίζεται ένα δημόσιο αποθετήριο στο οποίο άλλοι μπορούν να βασίσουν τη δική τους εργασία και στο οποίο μπορούν να συνεισφέρουν. Αυτό παρέχει ένα ευρύ φάσμα δυνατοτήτων όσον αφορά στις ροές εργασίας για το έργο μας ή/και την ομάδα μας· θα καλύψουμε μερικά συνηθισμένα μοντέλα που εκμεταλλεύονται αυτή την ευελιξία. Θα αναλύσουμε τα δυνατά σημεία αλλά και τις ενδεχόμενες αδυναμίες κάθε μοντέλου· μπορούμε να επιλέξουμε μόνον ένα από αυτά ή να δανειστούμε λειτουργικότητες από περισσότερα και να τις ταιριάξουμε. Συγκεντρωτική ροή εργασίας Στα συγκεντρωτικά συστήματα υπάρχει γενικά ένα ενιαίο μοντέλο συνεργασίας — η συγκεντρωτική ροή εργασίας. Μόνο ένας κεντρικός κόμβος ή αποθετήριο μπορεί να δεχθεί κώδικα και όλοι συγχρονίζουν το έργασία τους με αυτόν. Οι προγραμματιστές είναι περιφερειακοί κόμβοι — καταναλωτές αυτού του κεντρικού κόμβου — και συγχρονίζονται με αυτή την κεντρική τοποθεσία. Figure 53. Συγκεντρωτική ροή εργασίας Αυτό σημαίνει ότι εάν δύο προγραμματιστές κλωνοποιήσουν από τον κεντρικό κόμβο και κάνουν αλλαγές και οι δύο, ο πρώτος προγραμματιστής που θα ωθήσει τις αλλαγές τους μπορεί να το κάνει χωρίς προβλήματα. Ο δεύτερος προγραμματιστής πρέπει να συγχωνεύσει την εργασία του πρώτου πριν ωθήσει τις δικές του αλλαγές, ώστε να μην αντικαταστήσει τις αλλαγές του πρώτου προγραμματιστή. Αυτό ισχύει και στο Git όπως και στο Subversion (ή οποιοδήποτε CVCS) και αυτό το μοντέλο λειτουργεί απολύτως καλά και στο Git. Εάν είμαστε ήδη εξοικειωμένοι με μια συγκεντρωτική κεντρική ροή εργασίας στην εταιρεία ή την ομάδα μας, μπορούμε εύκολα να συνεχίσουμε να χρησιμοποούμε αυτή τη ροή εργασίας με το Git. Απλά δημιουργούμε ένα μοναδικό αποθετήριο και δίνουμε σε όλα τα μέλη της ομάδας μας δικαίωμα ώθησης (push access)· το Git δεν επιτρέπει στους χρήστες να επανεγγράψουν ο ένας τη δουλειά του άλλου. Ας υποθέσουμε ότι ο Τζον και η Τζέσικα αρχίζουν να εργάζονται την ίδια στιγμή. Ο Τζον ολοκληρώνει την αλλαγή του και την ωθεί στον διακομιστή. Στη συνέχεια η Τζέσικα προσπαθεί να ωθήσει τις αλλαγές της, αλλά ο διακομιστής τις απορρίπτει. Της λέει ότι προσπαθεί να ωθήσει αλλαγές χωρίς ταχυπροώθηση και ότι δεν θα μπορέσει να το κάνει μέχρι να ανακτήσει τις αλλαγές που υπάρχουν ήδη και να τις συγχωνεύσει. Αυτή η ροή εργασίας είναι ελκυστική για πολλούς, επειδή είναι ένα μοντέλο με το οποίο είναι εξοικειωμένοι και έχουν άνεση. Αυτό δεν περιορίζεται μόνο στις μικρές ομάδες. Με το μοντέλο διακλάδωσης του Git είναι δυνατό για εκατοντάδες προγραμματιστές να δουλέψουν με επιτυχία σε ένα μόνο έργο μέσω δεκάδων κλάδων ταυτόχρονα. Ροή εργασίας με διαχειριστή ενσωμάτωσης (integration manager) Επειδή το Git μας επιτρέπει να έχουμε πολλαπλά απομακρυσμένα αποθετήρια, είναι δυνατό να έχουμε μια ροή εργασίας στην οποία κάθε προγραμματιστής έχει δικαίωμα εγγραφής στο δικό του δημόσιο αποθετήριο και δικαίωμα ανάγνωσης σε όλα τα άλλα αποθετήρια. Αυτό το σενάριο περιλαμβάνει συχνά ένα κανονικό (canonical) αποθετήριο που αντιπροσωπεύει το “επίσημο” έργο. Για να συνεισφέρουμε σε αυτό το έργο, δημιουργούμε τον δικό μας δημόσιο κλώνο του έργου και ωθούμε τις αλλαγές μας σε αυτόν. Στη συνέχεια, μπορούμε να στείλουμε ένα αίτημα στον διαχειριστή του κύριου έργου να τραβήξει τις αλλαγές μας. Τότε ο διαχειριστής μπορεί να προσθέσει το αποθετήριό μας ως απομακρυσμένο, να δοκιμάσει τις αλλαγές μας τοπικά, να τις συγχωνεύσει στον κλάδο του και να τις ωθήσει στο αποθετήριό του. Η διαδικασία λειτουργεί ως εξής (βλ. Ροή εργασίας με διαχειριστη ενσωμάτωσης. ): Ο διαχειριστής του έργου ωθεί στο δημόσιο αποθετήριό του. Ένας συνεργάτης κλωνοποιεί αυτό το αποθετήριο και κάνει αλλαγές. Ο συνεργάτης ωθεί στο δικό του δημόσιο αντίγραφο. Ο συνεργάτης αποστέλλει στον διαχειριστή ένα e-mail ζητώντας του να τραβήξει τις αλλαγές. Ο διαχειριστής προσθέτει το αποθετήριο του συνεργάτη ως απομακρυσμένο και συγχωνεύει τοπικά. Ο διαχειριστής ωθεί τις συγχωνευμένες αλλαγές στο κύριο αποθετήριο. Figure 54. Ροή εργασίας με διαχειριστη ενσωμάτωσης. Αυτή είναι μια πολύ συνηθισμένη ροή εργασίας με εργαλεία όπως το GitHub ή το GitLab, που βασίζονται σε κεντρικούς κόμβους και στην οποία είναι εύκολο να κλωνοποιήσουμε ένα έργο και να ωθήσουμε τις αλλαγές μας στον δικό μας κλώνο, όπου μπορούν να τις δουν όλοι. Ένα από τα κύρια πλεονεκτήματα αυτής της προσέγγισης είναι ότι μπορούμε να συνεχίσουμε να εργαζόμαστε και ο διαχειριστής του κύριου αποθετηρίου μπορεί να τραβήξει τις αλλαγές μας όποτε θέλει. Οι συνεργάτες δεν χρειάζεται να περιμένουν το έργο να ενσωματώσει τις αλλαγές τους — ο καθένας μπορεί να εργαστεί με τον δικό του ρυθμό. Ροή εργασίας δικτάτορα και υπαρχηγών Αυτή είναι μια παραλλαγή της ροής εργασίας πολλαπλών αποθετηρίων. Χρησιμοποιείται γενικά από τεράστια έργα με εκατοντάδες συνεργάτες· ένα διάσημο παράδειγμα είναι ο πυρήνας του Linux. Διάφοροι διαχειριστές ενσωμάτωσης είναι υπεύθυνοι για ορισμένα τμήματα του αποθετηρίου· αυτοί ονομάζονται υπαρχηγοί . Όλοι οι υπαρχηγοί έχουν έναν διευθυντή ενσωμάτωσης γνωστό και ως καλόβουλο δικτάτορα. Το αποθετήριο του καλόβουλου δικτάτορα χρησιμεύει ως αποθετήριο αναφοράς από το οποίο όλοι οι συνεργάτες τραβούν αρχεία. Η διαδικασία λειτουργεί ως εξής (βλ. Ροή εργασίας με καλόβουλο δικτάτορα. ): Οι απλοί προγραμματιστές ασχολούνται με τον θεματικό κλάδο τους και επανατοποθετούν (rebase) την εργασία τους στον κλάδο master . Ο κλάδος master ανήκει στο αποθετήριο αναφοράς στο οποίο ωθεί ο δικτάτορας. Οι υπαρχηγοί συγχωνεύουν τους κλάδους των προγραμματιστών ο καθένας στον δικό τους κλάδο master . Ο δικτάτορας συγχωνεύει τους κλάδους master των υπαρχηγών στον κλάδο master του δικτάτορα. Ο δικτάτορας ωθεί τον δικό του κλάδο master στο αποθετήριο αναφοράς, έτσι ώστε οι άλλοι προγραμματιστές να μπορέσουν να επανατοποθετηθούν σε αυτόν. Figure 55. Ροή εργασίας με καλόβουλο δικτάτορα. Αυτό το είδος ροής εργασίας δεν είναι συνηθισμένο, αλλά μπορεί να είναι χρήσιμο σε πολύ μεγάλα έργα ή σε αυστηρά ιεραρχικά περιβάλλοντα. Επιτρέπει στον επικεφαλής του έργου (δικτάτορα) να αναθέσει μεγάλο μέρος της εργασίας και να συλλέξει μεγάλα υποσύνολα κώδικα σε διάφορες χρονικές στιγμές πριν τα ενσωματώσει. Μοτίβα Διαχείριση Πηγαίου Κώδικα σε Κλάδους Note Ο Martin Fowler έχει κάνει έναν οδηγό "Μοτίβα Διαχείριση Πηγαίου Κώδικα σε Κλάδους" ("Patterns for Managing Source Code Branches"). Αυτός ο οδηγός καλύπτει όλες τις κοινές ροές εργασίας του Git, και εξηγεί πως/πότε να τα χρησιμοποιούμε. Υπάρχει κιόλας ένας τομέας σύγκρισης υψηλής και χαμηλής συχνότητας ενσωμάτωσης. https://martinfowler.com/articles/branching-patterns.html Περίληψη ροών εργασίας Αυτές είναι μερικές συνήθεις ροές εργασίας που καθίστανται δυνατές με ένα κατανεμημένο σύστημα όπως το Git, αλλά βλέπετε ότι είναι δυνατές πολλές παραλλαγές οι οποίες ενδεχομένως ταιριάζουν περισσότερο στη δική μας ροή εργασίας. Τώρα που μπορείτε (όπως ελπίζουμε) να προσδιορίσετε ποιος συνδυασμός ροών εργασίας σας βολεύει, θα καλύψουμε μερικά πιο συγκεκριμένα παραδείγματα για το πώς να επιτύχετε τους κύριους ρόλους που συνθέτουν τις διαφορετικές ροές. Στην επόμενη ενότητα, θα μάθουμε μερικά κοινά μοτίβα συνεισφοράς σε ένα έργο. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://lwn.net/Articles/896255/ | ID-mapped mounts [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register ID-mapped mounts Ready to give LWN a try? With a subscription to LWN, you can stay current with what is happening in the Linux and free-software community and take advantage of subscriber-only site features. We are pleased to offer you a free trial subscription , no credit card required, so that you can see for yourself. Please, join us! By Jake Edge May 30, 2022 LSFMM The ID-mapped mounts feature was added to Linux in 5.12, but the general idea behind it goes back a fair bit further. There are a number of different situations where the user and group IDs for files on disk do not match the current human (or process) user of those files, so ID-mapped mounts provide a way to resolve that problem—without changing the files on disk. The developer of the feature, Christian Brauner, led a discussion at the 2022 Linux Storage, Filesystem, Memory-management and BPF Summit (LSFMM) on ID-mapped mounts. He began with an introduction. There are multiple use cases, but he likes to talk about portable home directories first because they are not related to containers, which many think is the sole reason for ID-mapped mounts. A portable home directory would be on some kind of removable media that can be attached to various systems, some of which have a different user and group ID for the user, but, of course, the media has fixed values for those IDs. ID-Mapped mounts allow the device to be mounted on the system with the IDs remapped to those of the user on the local system. Beyond that, of course, are various container use cases, such as sharing a root filesystem with multiple containers, each of which is using its own user namespace with a different mapping for UID 0. Each of the containers needs to be able to access the files as "root", but UID 0 inside the namespace is mapped to some nonzero UID on the host system; an ID-mapped mount would enable that nonzero ID to be mapped to UID 0 for filesystem access. Similarly, sharing data between a host filesystem and one in a user namespace may require remapping the IDs. Some of these cases were handled with expensive recursive chown calls before ID-mapped mounts came along. There are some filesystems that can be used in user-namespace-based containers, most notably overlayfs, but there are still lots of limitations and the main filesystem types, Btrfs, XFS, and ext4, are not really able to be used in that manner. Once all of the use cases were gathered, he said, the most flexible solution turned out to be a per-mount mapping of UIDs and GIDs, which is what ID-mapped mounts provide. The API for the feature uses the mount_setattr() system call, which allows changing the ID mappings as well as other attributes of mounts. Brauner clarified that the feature applies to all virtual filesystem (VFS) mounts, so bind mounts are included. Unlike mount() , mount_setattr() allows changing mount attributes recursively. Using the feature requires passing a flag and a file descriptor to mount_setattr() ; the file descriptor is that of a user namespace that does the ID mapping that should be applied to the mount. The implementation was done in the VFS layer, so individual filesystems "do not need to be really aware of it"; there are APIs available to make it easy on the filesystems, he said. Ted Ts'o asked about a command-line tool for doing an ID-mapped mount; Brauner said that one should be merged soon into util-linux . Amir Goldstein noted that fstests already has a binary tool for testing these mounts. Brauner added that there are 15K lines of code in tests, already upstream in fstests, for ID-mapped mounts that aim to test the feature in all possible combinations. That includes things like access-control lists (ACLs), Linux capabilities, setuid and setgid execution, and so on. Every time a bug or regression is found, a new test is added to the suite. He spent a bit of time demonstrating the tool and the feature, noting that the mapping works in both directions: IDs of files in the mount follow the mapping and files created within the mount have the reverse-mapped IDs outside of it. The feature is already being used by various tools, such as systemd-nspawn and systemd-homed; it has also been added to the runC container specification, so "there is lots of activity going on around this". Currently, ext4, XFS, Btrfs, and several other filesystems support the feature; there is a patch set for overlayfs that is on-track to be merged soon. David Howells asked what filesystems need to do to support ID-mapped mounts. Brauner said that "in principle it is easy" to do so. Network filesystems may have some additional wrinkles, however; he has a patch set for Ceph but it still needs more work. The changes for ext4 and XFS were small, he said, and others are likely to be similar because most filesystems do not really use the IDs directly. The XFS quota-handling code does use the IDs, so it needed a bit more work. There is a long document available and he is willing to help add it to other filesystems. Network filesystems need to determine which ID they want to send to the server, he said. Normally, the mapped ID is the right choice, but that may not be true for all cases. Chuck Lever asked how the ID mapping could be changed for an existing mount and wondered if it could just be remounted to make that change. Brauner said that no changes are allowed once the namespace has been attached to the mount or the mount has been attached to the filesystem. Due to "lifetime issues" with regard to the use of the mapping, it is too complicated to allow changes once the filesystem has been fully mounted. Using the new mount API, a user will create a detached mount, then set the ID mapping on it, then, finally, attach it to the filesystem. Lever also asked about the limits for the number of entries in the mapping; for example, in a system with thousands of users, where each user should be mapped to their own ID in a single mount. Brauner said that user namespaces were originally limited to five mappings, but he raised that limit to 340 in 2015 or 2016. It will be difficult to increase it beyond that, he said, because mapping is done in a hot path; he optimized the data structure for the mappings and increasing it further will have a performance impact. Ts'o wondered if there was any thinking about supporting "project IDs", which are used by some container systems; those IDs are used for project-wide quotas in filesystems. Brauner said that project ID needs to be revisited, since "we have dodged this issue for years". The intended semantics are not clear, so he has been confused when looking into it. While both XFS and ext4 support those IDs, Ts'o said he is confused by the semantics as well, at least with respect to user namespaces. He and Darrick Wong discussed it at one point and it was not clear whether both filesystems worked the same way, though there is an intention to unify their behavior. Brauner said that quota handling is not the same between different filesystems in Linux; each seems to have its own quirks. In the Zoom chat, Jan Kara pointed out that ID-mapping changes had not been made to the VFS quota code, at least yet; that was relayed as time expired on the session, however. Index entries for this article Kernel Filesystems/Mounting Kernel Namespaces/User namespaces Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments ID-mapped mounts Posted May 30, 2022 16:55 UTC (Mon) by jhoblitt (subscriber, #77733) [ Link ] (6 responses) I'm very excited to see this coming to fruition after years of dealing with uid coordination for network filesystems and containers. What capability will calling mount_setattr() require? ID-mapped mounts Posted May 30, 2022 17:07 UTC (Mon) by brauner (subscriber, #109349) [ Link ] In order to create idmapped mounts you will need to have CAP_SYS_ADMIN in the user namespace the filesystem was mounted in and the filesystem needs to support them by raising FS_ALLOW_IDMAP. Since no filesystems that support being mounted unprivileged support them - and probably don't need to - this means you need to be CAP_SYS_ADMIN in the initial user namespace. There are no immediate plans to lower the privilege requirements. ID-mapped mounts Posted Jun 1, 2022 17:18 UTC (Wed) by developer122 (guest, #152928) [ Link ] (4 responses) It's been frustrating to no end that you can't do user mapping in NFS without dragging kerberos into the picture. Despite what some documentation would suggest, it's not possible. Sometimes you just want a simple file of the form: user1@host1.host1.host1.host1 = localuser1 user2@host2.host2.host2.host2 = localuser1 user3@host3.host3.host3.host3 = localuser2 ID-mapped mounts Posted Jun 1, 2022 18:41 UTC (Wed) by ballombe (subscriber, #9523) [ Link ] (1 responses) what happened to rpc.ugidd ? ID-mapped mounts Posted Jun 1, 2022 18:45 UTC (Wed) by jhoblitt (subscriber, #77733) [ Link ] NFS uid/gid mapping is essentially useless if you expect both reads and writes to be remapped. ID-mapped mounts Posted Jun 1, 2022 21:13 UTC (Wed) by jhoblitt (subscriber, #77733) [ Link ] (1 responses) I've never gotten idmapping to work with sec=krb5. Not saying it isn't possible... just I couldn't get it to work. krb5 isn't always practical. I have an application that mounts nfs into k8s pods. krb5 wasn't designed in the era of 100-1000s of "hosts" dynamically coming and going. While it supposedly isn't impossible to get krb5 working in a pod ( https://cloud.redhat.com/blog/kerberos-sidecar-container ), it doesn't look like much fun either. ID-mapped mounts Posted Jun 14, 2022 12:30 UTC (Tue) by cortana (subscriber, #24596) [ Link ] If only RHEL would include the excellent kstart (yes I know it's in EPEL) then that would have been so much simpler. That said, gssproxy is the better option these days, since it only requires an environment variable to be set. But I never figured out how to use it in a pod... ID-mapped mounts Posted May 30, 2022 23:19 UTC (Mon) by dgc (subscriber, #6611) [ Link ] The fundamental issue with user namespaces/mappings and project IDs are that they are not UIDs or GIDs. They are completely independent of UID/GIDs and are directly user controllable. That makes them very different in behaviour - users cannot change UIDs/GIDs as they are effectively owned by the system and fixed, whilst project ID is a property of the user owned file and can be changed at any time. This "user owns project ID" architecture is why mapping project IDs with user namespaces or ID mapping is problematic. Historically speaking, project IDs came from Irix. Irix didn't have group quotas at all. Instead, it had project quotas that allowed users to co-operatively build "project" based data stores without needing the admins to define special groups for those projects and assign users to them. It also allowed users to assign files in the their home directories to projects, such that a project could account for not just all the /data/project/.... files but also all the working files that users might have in /home/fred/project/... IOWs, project ID based quotas exist entirely outside the scope of UIDs and GIDs and strictly defined and owned directory heirarchies. This allows project quotas to do many things that UID/GID based quotas can't do, such as provide directory tree based quotas. For example, in a namespace based container setup, the host may be using project IDs to track space usage and enforce ENOSPC for a container's directory heirarchy. In this case, users inside the container cannot be allowed to modify the project ID as that would allow them to escape the space usage accounting and enforcement mechanism the host is using. This is why we don't allow project IDs to be manipulated inside user namespaces. There's also no limits on what project IDs a user can assign to a file. It's a 32 bit space, and the only two reserved system IDs are 0 (default, no accounting/enforcement) and 0xffffffff (-1) which is used to signal an invalid project ID. Any user can set any project ID they want between those two numbers. That makes it difficult to map ranges usefully to mounts because of the lack of constraints on what users can set. So before anything is implemented, a coherent framework for mapping and sharing project IDs across host and client namespaces and mapped mounts needs to be developed and agreed upon. If project IDs are going to be mapped at the user level, how does that translate to what project quotas store? Do they account based on the user project ID (mapped) or the host project ID (unmapped)? What if two different containers map back to the same host side project ID? There's a heap of unanswered questions here, and I'm not sure there is a single answer that works for every situation. The very flexibility and user control of project based quotas is what works against it here, and constraints will need to be carefully designed so that we don't compromise that flexibility and capability. -Dave. ID-mapped mounts Posted May 31, 2022 7:13 UTC (Tue) by taladar (subscriber, #68407) [ Link ] (2 responses) I wonder if this could also eventually be used to make bindfs unnecessary. We use that rather extensively for the mounting of directories owned by e.g. a vhost user into the chroot of various sftp users. ID-mapped mounts Posted Jun 1, 2022 2:00 UTC (Wed) by ringerc (subscriber, #3071) [ Link ] (1 responses) bindfs looks amazing. Why on earth doesn't Docker / Moby / containerd / runc support that for -v bind mounts, to solve some of the horrifying pain of id mapping in containers? ID-mapped mounts Posted Jun 2, 2022 0:14 UTC (Thu) by rcampos (subscriber, #59737) [ Link ] It is a FUSE fs, you can't get good performance out of it :-( ID-mapped mounts Posted Jun 1, 2022 1:57 UTC (Wed) by ringerc (subscriber, #3071) [ Link ] This will bring some much needed sanity to Docker bind mounts, which are currently an absolute nightmare. ID-mapped mounts Posted Jun 28, 2022 17:37 UTC (Tue) by jengelh (subscriber, #33263) [ Link ] (1 responses) >for example, in a system with thousands of users, where each user should be mapped to their own ID in a single mount. Brauner said that user namespaces were originally limited to five mappings, but he raised that limit to 340 Is that in units of users, or in units of ranges? For a container, a single ranged mapping (i.e. something like [131072:196608]->[0:65536]) might be sufficient while expressing much more than 340 individual users. ID-mapped mounts Posted Jul 7, 2022 3:52 UTC (Thu) by brauner (subscriber, #109349) [ Link ] units of ranges :) Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:40 |
https://lwn.net/Articles/896918/ | Maintainers don't scale [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register Maintainers don't scale LWN.net needs you! Without subscribers, LWN would simply not exist. Please consider signing up for a subscription and helping to keep LWN publishing. By Jake Edge June 6, 2022 LSFMM In something of a grab-bag session, Josef Bacik led a discussion about various challenges that Linux kernel maintainers face, some of which lead to burnout. The session was originally going to be led by Darrick Wong, but he was unable to come to LSFMM , so Bacik gathered some of Wong's concerns and combined them with his own in a joint storage and filesystem session at the 2022 Linux Storage, Filesystem, Memory-management and BPF Summit (LSFMM). As part of the discussion, Bacik presented his view on what the role of a kernel maintainer should be, which seemed to resonate with those present. Fuzzing and CVEs He started by noting that some of the areas that Wong wanted to discuss had already come up in other sessions, including the difficulties in setting up and running fstests and the need for backports of fixes to multiple stable releases . One topic that had not come up, though, was the increasing prevalence of people running fuzzers against filesystems, then filing for CVEs on the resulting problems. The CVE then triggers the kernel security process, which limits the amount of time available to make a fix and also limits which people can be involved in the investigation and bug-fixing process. In Bacik's opinion, a fuzzed filesystem does not constitute a security bug; "I know I'm probably a heretic for saying that". Filesystems can only be mounted by the root user, he said, but that is often countered with the example of a USB drive; "turn off automount" is his answer for that. In any case, the problem Wong described is not one that he has personally experienced, but he asked Ted Ts'o what he knew about it. Ts'o said that companies that want to sell their products into certain markets, such as to the US government, have special requirements with regard to fixing security problems. There are various time frames on how quickly the bugs must be fixed on production systems based on their severity score. If those are not met, then there is an auditing process where arguments like "we're not crazy enough to let random container people mount untrusted filesystems" can be made to explain why the CVE does not apply. But that involves describing the situation to a government bureaucrat, which, unsurprisingly, security teams do not enjoy, he said. The good news is that generally those types of bugs do not have a high severity score because they are not remotely exploitable. Chris Mason said that he did not think the security@kernel.org team was opening CVEs for the reports it receives; Ts'o agreed, but noted that the research labs that find these bugs often have a financial incentive to open CVEs. Luis Chamberlain said that the process followed depends on the subsystem maintainer to a large extent. Some subsystems, such as networking, do not fix bugs behind closed doors, while others do. The problem, of course, is that public fixes can lead to zero-day exploits until the fix is made and rolled out to distributions and into production. Ts'o said that it may also depend on the employer; there may be pressure applied to a particular employee who happens to also be the maintainer of a subsystem. That is not directly "maintainer stress" but is instead targeting an employee, he said. Expectations Bacik said that he wanted to discuss "what we expect from maintainers". Traditionally, the expectation has been that they merge, write, test, review, and backport patches; that is a lot of work for one person. Many maintainers have come up with ad hoc solutions to try to scale that back, such as making sure that the developers for the subsystem are also reviewing patches. Ensuring that there are good testing setups is important to that effort as well. He would like to ensure that maintainers are also actively working on maintaining the community itself. Linux developers are passionate about the work that they do, but that passion sometimes leads to conflicts. "We get a little short with each other", which is not a good thing to maintain good working relationships, he said. Getting together in the same room, for example at LSFMM, is helpful, but he would like to see more done to get out ahead of these kinds of problems. It would be great to resolve these difficulties before they blow up and before they require getting together at a conference to fix them. A maintainer cannot follow all of the email threads, Bacik said, but it is fairly easy to spot "the big stuff that may be contentious". In those cases, he would like to encourage maintainers to either be a mediator, or find someone in the community who is good at mediating, to try to help developers from getting "overly invested in the code; in the end, this is just code". The intent is to find a way to ensure that those who are butting heads do it respectfully and in a way that will allow them to continue working together. If the maintainers could be "a little bit more proactive" about keeping an eye on contentious discussions, it would help head off these kinds of problems. Ts'o said that he has been having weekly ext4 development meetings that have been really helpful in reducing friction for filesystem development. Wong attends those meetings, which allows them to informally discuss things, maintainer to maintainer, that will ultimately need to be resolved on the linux-fsdevel mailing list. Jan Kara and other filesystem developers, who bring other useful perspectives, attend as well. Though Ts'o is sure that no one needs more meetings, he does wonder if some kind of monthly or quarterly gathering of developers could make a difference. Christian Brauner agreed with the idea of periodic meetings; he thought it would be "very useful". He has run into mailing-list conflicts along the way and said that it is only "in very very rare circumstances" when a third party comes along to calm things down on the list. Bacik said that it is important to ensure "that a random person can pop into a conversation" to ask the participants to calm down. That is not necessarily the case currently. It is tempting to suggest that Linus Torvalds (or some other individual) should be the one to step in and calm things down, but depending on a single person is not likely to work. Sometimes people are not paying attention at the right time; Bacik said he did not see the problems Brauner was referring to until well after the fact. Bacik wondered if people who are involved in a conflict of that sort should put out a call for a maintainer or other third party to step in and help calm things down. There are two areas that he would like to see maintainers take more of a lead in: conflict resolution and technical direction. Sometimes there are two developers who are disagreeing about the best way forward; "that's where I really want maintainers to step up more" and point out the direction that the project should take. That will help prevent the developers from continuing to butt heads and allow the project to progress. Ts'o said that he agrees that the main goal should be conflict resolution, but that is in an ideal world. In his experience, a maintainer generally picks up all of the tasks that the rest of the community is unwilling to do. Since no one steps up to do test engineering for ext4, for example, he takes care of it because it needs to be done. He is also spending quite a bit of time in recruiting new people to the ext4 community and in encouraging companies to staff positions for ext4 developers. That includes "working with an unnamed cloud company, not my own" to try to get some of its developers working on ext4 and, hopefully, to join that weekly development call. That is something he suggested other maintainers consider doing; other subsystem developers can also help the maintainer with that effort, which ultimately will help reduce burnout. A big problem is that "we simply do not have enough people on some of the filesystem teams", he said. Bacik said that it is his goal to reduce the number of things that maintainers are doing so that they can focus on the areas where their experience and knowledge are needed. Automation, especially in testing, is a good way to reduce the burden for maintainers. The important jobs for maintainers, conflict resolution and technical direction, cannot be automated; that is the piece that requires a human. Moving faster He concluded the session by saying that he would like to see the development of Btrfs (and, by extension, other parts of the kernel) move more quickly than they do today. In order for that to happen, though, there need to be more and better tests that are being continuously run to detect when bugs are introduced. Testing and test engineering are the kinds of tasks that can be handed off to more junior engineers, he said, though the bar for test quality needs to be maintained. In general, he said that he wants to foster an environment where things move quickly, but mistakes will be made "and that's OK". Developers need to understand that they can make mistakes, those mistakes will be detected early on, and the change will simply be reverted. Then they can try again, That philosophy can be applied to the tests and testing infrastructure, as well as to new features for the kernel. Index entries for this article Kernel Development model/Maintainers Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments Maintainers don't scale Posted Jun 29, 2022 16:22 UTC (Wed) by fratti (guest, #105722) [ Link ] > In Bacik's opinion, a fuzzed filesystem does not constitute a security bug; "I know I'm probably a heretic for saying that". Filesystems can only be mounted by the root user, he said, but that is often countered with the example of a USB drive; "turn off automount" is his answer for that. The root user does not have a crystal ball that tells them whether the filesystem they are about to mount will exploit their kernel. I can empathise with the grumpiness of being flooded with security nothingburgers by companies that run automated systems but this claim really is heresy to me. Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:40 |
https://www.microsoft.com/ko-kr/ai/energy-resources/power-utilities | 에너지 - 전력 및 유틸리티 | Microsoft AI This is the Trace Id: ce5d88b7f34a2850de5192d4ffbf3d42 주 콘텐츠로 건너뛰기 Microsoft Microsoft AI Microsoft AI Microsoft AI 홈 제품 및 솔루션 조직용 조직용 Microsoft 365 Copilot Microsoft 365 Copilot 앱 다운로드 조직용 Copilot Agent 365 Customize your Copilot Customize your Copilot Copilot Studio Build your own Build your own Microsoft Foundry Foundry Tools Azure AI 솔루션 파트너 제공 파트너 제공 Microsoft Marketplace Intelligent PCs Intelligent PCs Copilot+ PCs 개인용 개인용 Microsoft Copilot Copilot 앱 다운로드 업계 솔루션 소비재 보안 및 인텔리전스 교육 에너지 및 자원 에너지 및 자원 개요 전력 및 유틸리티 석유 및 가스 채광 금융 서비스 금융 서비스 개요 뱅킹 자본 시장 보험 정부 기관 정부 기관 개요 대중교통 및 도시 인프라 공공 금융 공중 보건 및 복지 서비스 공공 안전 및 정의 의료 서비스 및 생명 과학 의료 서비스 및 생명 과학 개요 공급자 Payors 생명과학 제조 제조 개요 산업 혁신 미디어 및 엔터테인먼트 이동성 이동성 개요 자동차 여행 및 교통 소매 통신 비즈니스 리더를 위한 AI AI 사용 사례 신뢰할 수 있는 AI 책임 있는 AI 책임 있는 AI Microsoft 책임 있는 AI 원칙 및 접근 방식 도구 및 사용 지속 가능성 지속 가능성 지속 가능성 강화 보안 유지 보안 유지 AI 보안 강화 데이터 보호 및 개인 정보 알아보기 AI 101 AI 학습 허브 업계 블로그 Microsoft Cloud 블로그 지원 비즈니스 고객을 위한 지원 산업 문서 자세히 산업 Microsoft for the power and utilities industry</h1> "> 전력 및 유틸리티 산업을 위한 Microsoft 그리드를 운영하고, 고객에게 서비스를 제공하고, 비즈니스 목표를 달성하는 방법을 다시 정의하세요. 비디오 보기 개요 개요 기능 고객 사례 파트너 제품 리소스 개요 Accelerate the energy transition</h2> "> 에너지 전환 가속화 Microsoft의 신뢰할 수 있는 데이터 및 AI 솔루션을 통해 전력 및 유틸리티 산업에서 더 많은 성과를 달성하세요. 에너지 분야 직원의 역량 강화 원활한 협업을 위해 워크플로를 자동화하고 AI 지원 채용, 학습, 교육을 개선합니다. 새로운 에너지 미래를 추구하는 운영 AI를 사용해 공급망, 보안 자산, 전력 에너지 시스템을 최적화하여 생산성을 높입니다. 넷제로 약속 달성 데이터를 활용하여 탄소 배출을 줄이고, 탄소 없는 에너지의 규모를 늘리고, 에너지 가치 사슬에서 탈탄소를 달성합니다. 지속 가능한 AI 기반 비즈니스 성장 기후 혁신, 지속 가능성 진행률, 비즈니스 성장을 가속화하는 명확한 데이터 인사이트를 얻습니다. 기능 Explore use cases</h2> "> 사용 사례 살펴보기 지속 가능한 미래를 지원하기 위해 설계된 기술 솔루션을 살펴보세요. 참여형의 연결된 현장 서비스 현장 서비스 파견 직원 및 기술자에게 실시간 경고를 제공하고 연결된 모바일 솔루션을 통해 생산성과 협업을 발전시킵니다. 예측 유지 관리 장비 수명 주기를 추적하여 고장을 예측 및 방지하고 장비를 업데이트하기 위한 최적의 시간과 프로세스를 식별하는 데 도움이 되는 인사이트를 얻습니다. 그리드 모니터링 및 최적화 고품질 데이터 및 실시간 탄소 배출 추적을 통해 GHG 배출을 줄이면서 규정 준수 및 환경 모니터링을 개선합니다. E-모빌리티 관리 비용 및 부하에 최적화된 EV 네트워크 및 스마트 충전소의 실시간 모델링을 통해 비용을 줄이고 EV 그리드 안정성을 개선합니다. 고객 사례 Explore innovation in power and utilities</h2> "> 전력 및 유틸리티 분야의 혁신 살펴보기 “이전에는 장비를 잃어버리곤 했습니다. 이제 이 솔루션을 통해 RPA를 활용하고 이를 데스크톱과 모바일 디바이스 모두에서 사용할 수 있게 함으로써 미화 백만 달러 이상을 절감했습니다.” Thomas Bilbo, 주요 제품 소유자 제품 Power Platform Power BI 사례 읽기 고객 사례 섹션으로 돌아가기 파트너 솔루션 Explore more power and utilities solutions</h2> "> 더 많은 전력 및 유틸리티 솔루션 살펴보기 Microsoft 파트너 에코시스템에서 전력 및 유틸리티 산업 제품을 찾아보세요. 솔루션 살펴보기 이전 슬라이드 다음 슬라이드 EcoStruxure DERMS by Schneider Electric</h3> "> 그리드 운영 Schneider Electric의 EcoStruxure DERMS 유틸리티에 맞게 조정된 그리드 인식 솔루션으로 에너지 산업 중단을 극복하세요. 자세한 정보 SAP S/4HANA for Microsoft Teams</h3> "> 협업 SAP S/4HANA for Microsoft Teams Microsoft Teams를 사용하여 SAP S/4HANA Cloud 애플리케이션에서 바로 동료와 협업하세요. 자세한 정보 ABB Ability Solutions</h3> "> 분석 ABB Ability Solutions 보다 안전하고 스마트하며 효율적인 운영을 위해 실시간 데이터를 기반으로 의사 결정을 내리세요. 자세한 정보 파트너 솔루션 섹션으로 이동 제품 Discover products for power and utilities</h2> "> 전력 및 유틸리티 제품 살펴보기 Microsoft의 신뢰할 수 있는 제품을 사용하여 운영을 혁신하고, 고객 서비스를 향상하고, 목표를 달성하세요. 이전 슬라이드 다음 슬라이드 Microsoft Power BI 실시간 데이터 기반 인사이트를 사용하여 지속 가능한 에너지 관리 방식을 개선하고 변화시킵니다. 자세한 정보 Microsoft Teams 최전방 직원이 효율적으로 소통하고 협업하는 데 필요한 도구를 제공합니다. 자세한 정보 Dynamics 365 Remote Assist 혼합 현실 기술로 현장 작업자를 지원하여 작업을 간소화합니다. 자세한 정보 Microsoft Power Platform 모든 팀이 로우코드 도구를 사용하여 솔루션을 개발할 수 있도록 하여 전체 직원의 역량을 강화합니다. 자세한 정보 Azure 에너지 생산에서 지능형 그리드까지 운영을 현대화하는 데 도움이 되는 사용자 지정 솔루션을 구축합니다. 자세한 정보 Dynamics 365 Field Service 기술자에게 최초 문제 해결에 필요한 올바른 정보, 도구, 원격 전문가 지원을 제공합니다. 자세한 정보 에너지 분야의 Azure IoT 혁신을 주도하고 에너지 분배를 최적화하는 동시에 운영 비용을 절감합니다. 자세한 정보 Dynamics 365 Customer Service 에너지 서비스를 지원하고 모든 채널에서 뛰어난 고객 서비스를 제공합니다. 자세한 정보 Azure Digital Twins 스마트 공간, 건물, 전력망에 재사용 가능하고 확장 가능하며 공간 인식적인 환경을 구축합니다. 자세한 정보 Microsoft Cloud for Sustainability 데이터와 AI를 사용하여 환경적 지속성을 이뤄 가는 과정을 모니터링하고 관리합니다. 자세한 정보 Microsoft 배출 영향 대시보드 조직의 클라우드 사용이 탄소 배출에 미치는 영향을 측정하고 추적하여 새로운 효율성을 추진합니다. 자세한 정보 제품 섹션으로 돌아가기 Explore valuable resources</h2> "> 유용한 리소스 살펴보기 Get insights from energy industry leaders on The Short Circuit</h3> "> 팟캐스트 • 2024년 2월 The Short Circuit에서 에너지 산업 리더들로부터 인사이트 얻기 미국 에너지부 부장관 David Turk가 에너지 부문의 현재와 미래에 대해 이야기하는 내용을 들어보세요. 팟캐스트 듣기 Orchestrating the Grid: Tackling Utilities' Opportunities and Challenges</h3> "> 백서 • 2024 전력망 조율: 유틸리티의 기회와 과제 해결 백서 읽기 Navigating NERC CIP compliance in the cloud</h3> "> 백서 • 2024 클라우드에서 NERC CIP 규정 준수 탐색 백서 읽기 How AI empowers the wind industry to achieve more</h3> "> 백서 • 2024 AI를 통해 풍력 발전 산업이 더 많은 성과를 달성할 수 있도록 지원하는 방법 백서 읽기 다음 단계 Achieve more in the energy industry</h2> "> 에너지 산업에서 더 많은 성과 달성하기 Find your cloud solution</h3> "> 비즈니스 솔루션 허브 클라우드 솔루션 찾기 귀사의 고유한 비즈니스 목표에 적합한 솔루션을 찾으려면 지금 살펴보세요. 모든 솔루션 살펴보기 Build a more sustainable future with AI</h3> "> Microsoft AI AI로 더욱 지속 가능한 미래 구축 AI 기반 솔루션을 통해 에너지 및 리소스 산업을 재창조하고 넷 제로를 달성하세요. 자세한 정보 팔로우하기 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:29:40 |
https://huggingface.co/Calvin-Xu | Calvin-Xu (Calvin Xu) Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up 1 Calvin Xu Calvin-Xu Follow tsukumijima's profile picture John6666's profile picture dlwh's profile picture 3 followers · 13 following https://www.pinlinxu.com Calvin-Xu AI & ML interests None yet Recent Activity updated a dataset 4 days ago Calvin-Xu/FLFL-Aozora-Speech-Train liked a model 2 months ago marin-community/marin-32b-base updated a model about 1 year ago Calvin-Xu/FLFL View all activity Organizations None yet models 2 Sort: Recently updated Calvin-Xu/FLFL Text Generation • 1B • Updated Dec 9, 2024 • 5 • 1 Calvin-Xu/FLFL-Adapter Updated Sep 15, 2024 • 2 datasets 5 Sort: Recently updated Calvin-Xu/FLFL-Aozora-Speech-Train Viewer • Updated 4 days ago • 1.96M • 19 • 2 Calvin-Xu/GloVe-wikitext-103 Updated Sep 16, 2024 • 12 Calvin-Xu/Furigana-Aozora-Speech Viewer • Updated Jul 30, 2024 • 2.54M • 64 • 2 Calvin-Xu/Furigana-Aozora Viewer • Updated Jul 28, 2024 • 1.42M • 56 • 2 Calvin-Xu/Furigana-NDLBIB Viewer • Updated Jul 28, 2024 • 15.8M • 35 System theme Company TOS Privacy About Careers Website Models Datasets Spaces Pricing Docs | 2026-01-13T09:29:40 |
https://twitter.com/neclabsamerica | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T09:29:40 |
https://huggingface.co/marin-community/isoflop-6ep19-d3584-L35-B16-dclm-default-0d5691/tree/main | marin-community/isoflop-6ep19-d3584-L35-B16-dclm-default-0d5691 at main Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up ","eos_token":" "}},"createdAt":"2025-10-28T08:50:30.000Z","discussionsDisabled":false,"discussionsSorting":"recently-created","downloads":3,"downloadsAllTime":27,"id":"marin-community/isoflop-6ep19-d3584-L35-B16-dclm-default-0d5691","isLikedByUser":false,"availableInferenceProviders":[],"inference":"","lastModified":"2025-10-28T08:53:45.000Z","likes":0,"librariesOther":[],"trackDownloads":true,"private":false,"repoType":"model","gated":false,"tags":["safetensors","qwen3","region:us"],"tag_objs":[{"id":"safetensors","label":"Safetensors","type":"library"},{"id":"qwen3","label":"qwen3","type":"other","clickable":true},{"type":"region","label":"🇺🇸 Region: US","id":"region:us"}],"safetensors":{"parameters":{"F32":8112833792},"total":8112833792,"sharded":true},"hasBlockedOids":false,"region":"us","isQuantized":false},"discussionsStats":{"closed":0,"open":0,"total":0},"query":{},"inferenceContextData":{"billableEntities":[],"entityName2Providers":{}}}"> marin-community / isoflop-6ep19-d3584-L35-B16-dclm-default-0d5691 like 0 Follow The Marin Project 122 Safetensors qwen3 Model card Files Files and versions xet Community main isoflop-6ep19-d3584-L35-B16-dclm-default-0d5691 32.5 GB 1 contributor History: 2 commits WillHeld Add files using upload-large-folder tool fcf34a6 verified 3 months ago ","eos_token":" "}},"createdAt":"2025-10-28T08:50:30.000Z","discussionsDisabled":false,"discussionsSorting":"recently-created","downloads":3,"downloadsAllTime":27,"id":"marin-community/isoflop-6ep19-d3584-L35-B16-dclm-default-0d5691","isLikedByUser":false,"availableInferenceProviders":[],"inference":"","lastModified":"2025-10-28T08:53:45.000Z","likes":0,"librariesOther":[],"trackDownloads":true,"private":false,"repoType":"model","gated":false,"tags":["safetensors","qwen3","region:us"],"tag_objs":[{"id":"safetensors","label":"Safetensors","type":"library"},{"id":"qwen3","label":"qwen3","type":"other","clickable":true},{"type":"region","label":"🇺🇸 Region: US","id":"region:us"}],"safetensors":{"parameters":{"F32":8112833792},"total":8112833792,"sharded":true},"hasBlockedOids":false,"region":"us","isQuantized":false},"hasGatedAccess":true,"inferenceContextData":{"billableEntities":[],"entityName2Providers":{}}}"> .gitattributes 1.57 kB Add files using upload-large-folder tool 3 months ago README.md 157 Bytes Add files using upload-large-folder tool 3 months ago config.json 2.08 kB Add files using upload-large-folder tool 3 months ago model-00001-of-00004.safetensors 9.87 GB xet Add files using upload-large-folder tool 3 months ago model-00002-of-00004.safetensors 9.87 GB xet Add files using upload-large-folder tool 3 months ago model-00003-of-00004.safetensors 9.04 GB xet Add files using upload-large-folder tool 3 months ago model-00004-of-00004.safetensors 3.68 GB xet Add files using upload-large-folder tool 3 months ago model.safetensors.index.json 30.4 kB Add files using upload-large-folder tool 3 months ago special_tokens_map.json 301 Bytes Add files using upload-large-folder tool 3 months ago tokenizer.json 17.2 MB xet Add files using upload-large-folder tool 3 months ago tokenizer_config.json 50.5 kB Add files using upload-large-folder tool 3 months ago | 2026-01-13T09:29:40 |
https://git-scm.com/book/zh-tw/v2/%e5%88%86%e6%95%a3%e5%bc%8f%e7%9a%84-Git-%e5%88%86%e6%95%a3%e5%bc%8f%e5%b7%a5%e4%bd%9c%e6%b5%81%e7%a8%8b | Git - 分散式工作流程 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 分散式的 Git - 分散式工作流程 Now that you have a remote Git repository set up as a point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. 分散式工作流程 Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally on a central hub. In Git, however, every developer is potentially both a node and a hub – that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This opens a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. 集中式工作流程 In centralized systems, there is generally a single collaboration model–the centralized workflow. One central hub, or repository, can accept code, and everyone synchronizes their work to it. A number of developers are nodes – consumers of that hub – and synchronize to that one place. 圖表 54. Centralized workflow. This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. 整合式管理員工作流程 Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow. ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an email asking them to pull changes. The maintainer adds the contributor’s repo as a remote and merges locally. The maintainer pushes merged changes to the main repository. 圖表 55. Integration-manager workflow. This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes – each party can work at their own pace. 司令官與副官工作流程 This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants. All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator’s repository serves as the reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow. ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the dictator. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. The dictator pushes their master to the reference repository so the other developers can rebase on it. 圖表 56. Benevolent dictator workflow. This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. 工作流程總結 These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://support.microsoft.com/da-dk/office/hvad-er-vagter-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Hvad er Vagter? - Microsoft Support Relaterede emner × Oplæringsvideoer til Microsoft Teams Startvejledning til Microsoft Teams Hvad er Microsoft Teams? Log på, og kom i gang Chat og del filer Samarbejd Få mere at vide Introduktion til Microsoft Teams Kom i gang med Microsoft Teams Kom i gang med chat Kom i gang med Møder Kom i gang med Apps Konfigurer og tilpas dit team Opret et team med skabeloner Samarbejd med eksterne gæster Administrere teamindstillinger Samarbejd i teams og kanaler Tip: Send mail til en kanal Opret en plan med Planner Arbejd med opslag og meddelelser Post en meddelelse på flere kanaler Søg efter og find filer Upload og del filer Søg efter og filtrer personer og filer Søg efter og filtrér meddelelser Tip til Teams-filer Start chatsamtaler og opkald Oversigt over Teams-opkald Foretag opkald Tips til Teams-opkald Skjul chats og slet meddelelser Konfigurer, at en stedfortræder besvarer dine opkald Administrer møder Deltag i et Teams-møde Tips til Teams-møder Mød øjeblikkeligt Administrer møder Planlæg et webinar Vis din skærm under et møde. Opret og deltag i livebegivenheder Planlæg en livebegivenhed Producer en livebegivenhed Deltag i en livebegivenhed Vær moderator i en "spørgsmål og svar"-session Udforsk apps og værktøjer Find og brug apps Administrer teamets tidsplaner med Vagter Hvad er Vagter? Opret en tidsplan for Vagter Administrer en tidsplan for Vagter Opret godkendelser Hvad er godkendelser? Opret en godkendelse Opret en godkendelse fra en chat Opret en godkendelse via e-signatur Find skabeloner i Godkendelser Opret godkendelser med skabeloner Opret skabeloner for hele organisationen Virtuelle aftaler i Microsoft Bookings Hvad er virtuelle aftaler? Send sms-beskeder til eksterne gæster Udfør en aftale Tilmelde sig en aftale. Administrer dit aktivitetsfeed Administrer indstillinger for meddelelser Teams på farten Start en chat på farten Opret en kanal på farten Deltag i et møde på farten Aktivitetsfeed på farten Gå til hovedindholdet Microsoft Support Support Support Hjem Microsoft 365 Office Teams-support Emner Møder Chat Meddelelser og indstillinger Teams og kanaler Opkald og enheder Filer Apps og tjenester Hurtig start Chat Gruppechat Meddelelser Teams Kanaler Opkald Filer Apps Loop-komponenter Nyheder Ressourcer Videokurser Fejlfinding Her i Teams Hjælp til handicappede Teams-funktioner i henhold til platform Microsoft Teams (gratis) Office 365-community-fora Tech community-blog Undervisning med underviser Til administratorer og it-teknikere Til uddannelse Mere Køb Microsoft 365 Kun Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Tilbud Små virksomheder Support Software Software Windows-apps Kunstig intelligens OneDrive Outlook Skift fra Skype til Teams OneNote Microsoft Teams Pc'er og enheder Pc'er og enheder Køb Xbox Alt tilbehør Underholdning Underholdning Xbox Game Pass Ultimate Xbox og spil Pc-spil Til virksomheder Til virksomheder Microsoft Security Azure Dynamics 365 Microsoft 365 til virksomheder Microsoft Industry Microsoft Power Platform Windows 365 Udvikleren & IT Udvikleren & IT Microsoft Udvikler Microsoft Learn Understøttelse af AI-markedspladsapps Microsofts tekniske community Microsoft Marketplace Visual Studio Marketplace Rewards Andet Andet Gratis downloads og sikkerhed Uddannelse Gavekort Licensiering Vis oversigt over websted Søg Søg efter hjælp Ingen resultater Annuller Log på Log på med Microsoft Log på, eller opret en konto. Hej Markér en anden konto. Du har flere konti Vælg den konto, du vil logge på med. Relaterede emner Oplæringsvideoer til Microsoft Teams Startvejledning til Microsoft Teams Hvad er Microsoft Teams? Log på, og kom i gang Chat og del filer Samarbejd Få mere at vide Introduktion til Microsoft Teams Kom i gang med Microsoft Teams Kom i gang med chat Kom i gang med Møder Kom i gang med Apps Konfigurer og tilpas dit team Opret et team med skabeloner Samarbejd med eksterne gæster Administrere teamindstillinger Samarbejd i teams og kanaler Tip: Send mail til en kanal Opret en plan med Planner Arbejd med opslag og meddelelser Post en meddelelse på flere kanaler Søg efter og find filer Upload og del filer Søg efter og filtrer personer og filer Søg efter og filtrér meddelelser Tip til Teams-filer Start chatsamtaler og opkald Oversigt over Teams-opkald Foretag opkald Tips til Teams-opkald Skjul chats og slet meddelelser Konfigurer, at en stedfortræder besvarer dine opkald Administrer møder Deltag i et Teams-møde Tips til Teams-møder Mød øjeblikkeligt Administrer møder Planlæg et webinar Vis din skærm under et møde. Opret og deltag i livebegivenheder Planlæg en livebegivenhed Producer en livebegivenhed Deltag i en livebegivenhed Vær moderator i en "spørgsmål og svar"-session Udforsk apps og værktøjer Find og brug apps Administrer teamets tidsplaner med Vagter Hvad er Vagter? Opret en tidsplan for Vagter Administrer en tidsplan for Vagter Opret godkendelser Hvad er godkendelser? Opret en godkendelse Opret en godkendelse fra en chat Opret en godkendelse via e-signatur Find skabeloner i Godkendelser Opret godkendelser med skabeloner Opret skabeloner for hele organisationen Virtuelle aftaler i Microsoft Bookings Hvad er virtuelle aftaler? Send sms-beskeder til eksterne gæster Udfør en aftale Tilmelde sig en aftale. Administrer dit aktivitetsfeed Administrer indstillinger for meddelelser Teams på farten Start en chat på farten Opret en kanal på farten Deltag i et møde på farten Aktivitetsfeed på farten Hvad er Vagter? Gælder for Teams Microsoft Teams Prøv det! Appen Vagter i Microsoft Teams er et værktøj til administration af tidsplaner og tidsregistrering, der hjælper dig med at oprette, opdatere og administrere tidsplaner for dit team. Tidsplaner – Opret, rediger og administrer en tidsplan for dit team. En vagtplan viser dage øverst, teammedlemmer vises til venstre, og tildelte vagter vises i kalenderen. Indstillinger for tidsplan – I Skift-indstillinger skal du definere indstillingerne for tidsplanen og vælge de Vagter-funktioner, du vil gøre tilgængelige for dit team. Grupper – Tilføj planlægningsgrupper for at organisere teammedlemmer i tidsplanen efter jobtype eller placering. Vagter – Tildel vagter til teammedlemmer. Opret en vagt fra bunden, eller kopiér en eksisterende. Åbne vagter – Hver gruppe i tidsplanen har rækken Åbne vagter . Føj ledige vagter til tidsplanen, som alle kan anmode om. Tidsregistrering – Slå Tidsregistrering til i Skift-indstillinger for at lade dit team gå ind og ud af vagter. Anmodninger – Gennemse og besvar anmodninger om fridage, åbne vagter, vagtbytte og tilbud. Mærker – Brug vagtbaserede mærker til hurtigt at kommunikere med alle, der er på vagt. Publicer din tidsplan – Når du er færdig med at foretage ændringer i tidsplanen, kan du dele den med dit team, så alle er opdateret. Vil du have mere? Kom i gang med Vagter Opret en teamplan i Vagter Føj vagter til tidsplanen i Vagter Publicere en tidsplan i Vagter Administrer vagtanmodninger og fridage i Vagter Slå vagtbaserede tags til i Teams ABONNER PÅ RSS-FEEDS Har du brug for mere hjælp? Vil du have flere indstillinger? Find Community Udforsk abonnementsfordele, gennemse kurser, få mere at vide om, hvordan du sikrer din enhed og meget mere. Microsoft 365-abonnementsfordele Microsoft 365-kurser Microsoft-sikkerhed Center for tilgængelighed Communities hjælper dig med at stille og besvare spørgsmål, give feedback og høre fra eksperter med omfattende viden. Spørg Microsoft Community Microsoft Tech Community Windows Insiders Microsoft 365 Insiders Var disse oplysninger nyttige? Ja Nej Tak! Har du mere feedback til Microsoft? Kan du hjælpe os med at blive bedre? (Send feedback til Microsoft, så vi kan hjælpe.) Hvor tilfreds er du med kvaliteten af sproget? Hvad påvirkede din oplevelse? Løste mit problem Klare instruktioner Let at følge Ingen jargon Billeder hjalp Oversættelseskvalitet Stemte ikke overens med min skærm Forkerte instruktioner For teknisk Der er ikke nok oplysninger Der er ikke nok billeder Oversættelseskvalitet Har du mere feedback? (Valgfrit) Indsend feedback Når du trykker på Send, bliver din feedback brugt til at forbedre Microsoft-produkter og -tjenester. Din it-administrator kan indsamle disse data. Erklæring om beskyttelse af personlige oplysninger. Tak for din feedback! × Nyheder Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot til organisationer Copilot til personlig brug Microsoft 365 Udforsk Microsoft-produkter Windows 11-apps Microsoft Store Kontoprofil Download Center Microsoft Store Support Returneringer Ordreopfølgning Genanvendelse Kommercielle garantier Uddannelse Microsoft Education Enheder til uddannelse Microsoft Teams til uddannelse Microsoft 365 Education Office Education Underviseruddannelse og -udvikling Tilbud til studerende og forældre Azure til studerende Erhverv Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Små virksomheder Udvikler og it Microsoft Udvikler Microsoft Learn Understøttelse af AI-markedspladsapps Microsofts tekniske community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Firma Karriere Om Microsoft Nyheder om virksomheden Beskyttelse af personlige oplysninger hos Microsoft Investorer Bæredygtighed Dansk (Danmark) Ikonet for dine valg for fravalg af beskyttelse af personlige oplysninger Dine valg om beskyttelse af personlige oplysninger Ikonet for dine valg for fravalg af beskyttelse af personlige oplysninger Dine valg om beskyttelse af personlige oplysninger Beskyttelse af personlige oplysninger om forbrugernes sundhed Kontakt Microsoft Beskyttelse af personlige oplysninger Administrer cookies Copyright & rettigheder Varemærker Om vores annoncer EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:40 |
https://www.microsoft.com/ko-kr/power-platform/products/power-bi | Power BI - 데이터 시각화 | Microsoft Power Platform This is the Trace Id: 18ad12485309ad92c80d4f60ca0819b7 주 콘텐츠로 건너뛰기 Microsoft Power Platform Power Platform Power Platform 홈 Power BI Power Platform 정보 무료로 체험하기 AI(인공 지능) 보안 및 거버넌스 Dataverse 커넥터 서식 파일 제품 Power BI Power BI Power BI Desktop Pro Premium Embedded Report Server Power Apps Power Automate Power Pages Copilot Studio 가격 책정 파트너 리소스 Power BI 알아보기 Power BI 알아보기 설명서 비즈니스 인텔리전스 주제 데이터 스토리텔링 Power BI 블로그 Power BI 지원 Power BI 커뮤니티 Power BI 다운로드 지금 구입하기 무료로 시작 로그인 자세히 Microsoft 전체 Global Microsoft 365 Teams Copilot Windows Surface Xbox 세일 지원 소프트웨어 소프트웨어 Windows 앱 AI OneDrive Outlook Skype에서 Teams로 이동 중 OneNote Microsoft Teams PC 및 장치 PC 및 장치 Xbox 쇼핑 주변 기기 엔터테인먼트 엔터테인먼트 Xbox Game Pass Ultimate Xbox 및 게임 PC 게임 기업 고객용 기업 고객용 Microsoft Security Azure Dynamics 365 비즈니스용 Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 개발자 및 IT 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Visual Studio Marketplace Rewards 기타 기타 무료 다운로드 및 보안 교육 볼륨 라이선싱 사이트맵 보기 Power BI </h1> "> Power BI 강력한 인사이트를 파악하고 영향력으로 전환 모든 데이터에 연결하고 시각화하며 매일 사용하는 앱에 시각적 개체를 원활하게 주입합니다. 시작 기능 제품 개요 사용 사례 리서치 및 뉴스 가격 책정 상호 운용성 보안 고객 사례 리소스 로그인 무료로 사용해 보기 로그인 무료로 사용해 보기 제품 개요 Create a data-driven culture with BI for all</h2> "> 모두를 위한 BI로 데이터 기반 문화 조성 Power BI 기능 Power BI를 사용해야 하는 이유 Microsoft Fabric의 Copilot 패브릭의 Power BI Power BI Pro 체험 계정 이전 다음 AI를 사용하여 인사이트 파악 고급 데이터 분석 도구, AI 기능 및 사용자에게 친숙한 보고서 생성 도구를 사용하여 데이터를 시각적 개체로 전환하세요. 둘러보기 기업 내 모든 데이터 활용 모든 원본에서 데이터 세트를 만들고 OneLake 데이터 허브에 추가하여 데이터에 대한 진리의 원본을 만듭니다. 자세한 정보 인사이트를 영향력으로 전환하기 사용자가 매일 사용하는 앱(예: Microsoft 365 앱)에 대한 인사이트를 주입하여 더 나은 결정을 내릴 수 있도록 도와주세요. 자세한 정보 모든 데이터 팀 역량 강화 Power BI 환경에서 Microsoft Fabric을 활성화하여 조직이 데이터에 액세스, 관리 및 동작하는 방식을 재구성하세요. 자세한 정보 필요에 따라 원활하게 크기 조정 수천 명의 사용자에 걸쳐 확장할 수 있는 도구에서 엔터프라이즈급 수집 및 의미 체계 모델링을 사용하여 페타바이트 단위를 변환하세요. 자세한 정보 어디서나 인사이트 공유 Teams, PowerPoint, Excel 및 Power Platform 비롯한 다른 Microsoft 서비스 보고서를 쉽게 포함하고 공유할 수 있습니다. 자세한 정보 AI로 더 많은 작업 수행 데이터에서 패턴을 찾고, 보고서를 즉시 만들고, 답변을 제공하는 등 사용하기 쉬운 AI 기능을 사용하세요. 자세한 정보 데이터 제어 및 보호 Microsoft 거버넌스, 보안 및 규정 준수를 통해 요구 사항을 충족하고 엔드투엔드 가시성을 확보하세요. 자세한 정보 개요 몇 초 만에 보고서를 만들고, DAX 계산을 생성하고, 요약을 만들고, 답변을 얻는 모든 작업을 대화형 언어로 수행할 수 있습니다. 자세한 정보 몇 초 만에 보고서 만들기 원하는 내용을 간단히 설명하거나 데이터에 대해 질문하여 보고서를 빠르게 만들고 맞춤화할 수 있습니다. 데모 보기 데이터를 빠르게 탐색하고 요약 통찰력 있는 텍스트 요약을 추가하여 데이터를 더 빠르게 이해하고, 설명의 톤, 범위 및 스타일을 조정하세요. 데모 보기 DAX 쿼리 작성 탐색 기능을 포함하여 Power BI 환경에서 Copilot을 사용하여 의미 체계 모델을 요약하고 DAX 쿼리 뷰에서 DAX 쿼리를 작성하고 설명합니다. 자세한 정보 개요 유료 라이선스가 없는 사용자가 보고서와 상호 작용하고 나머지 Microsoft Fabric 워크로드에 액세스할 수 있도록 하세요. 자세한 정보 데이터 환경 통합 데이터 엔지니어가 서로 다른 원본의 데이터를 연결하고 큐레이팅할 수 있도록 OneLake를 사용하여 개방형 데이터 허브를 설정하세요. 자세한 정보 데이터 변환 Microsoft Fabric 워크로드 제품군을 사용하여 데이터를 통합, 처리, 분석, 모니터링 및 시각화하세요. 패브릭 시나리오 참조 데이터 거버넌스 통합 데이터 관리자에게 추가 제어를 제공하는 확장성 있는 개방형 솔루션을 사용하여 사람과 데이터를 책임감 있게 연결하세요. 자세한 정보 개요 보고서를 게시하고 콘텐츠를 볼 수 있는 최신 셀프 서비스 분석을 통해 개별 사용자에게 라이선스를 부여하세요. 지금 구입하기 셀프 서비스 BI 사용자가 보고서를 만들고 게시하여 동료와 공유할 수 있도록 하여 셀프 서비스 BI를 촉진할 수 있습니다. 자세한 정보 Microsoft 365 E5 Power BI Pro를 다른 Microsoft 365 앱 및 업계 최고의 Microsoft 보안과 함께 사용자당 저렴한 가격으로 이용하세요. 자세한 정보 무료 계정 만들기 직접 사용할 보고서를 작성하거나 Power BI Premium 또는 Microsoft 패브릭 공유 용량에서 호스트되는 Power BI 콘텐츠를 볼 수 있습니다. 시작하기 Power BI Desktop 무료 앱을 사용하여 사용하기 쉬운 보고서 캔버스와 수백 개의 시각적 개체를 사용하여 데이터를 연결, 모델링 및 시각화할 수 있습니다. 앱 다운로드 무료 평가판 활성화 Microsoft Fabric 무료 평가판에 등록하여 Power BI가 제공하는 모든 것을 포함하여 전체 서비스 제품군을 살펴보세요. 무료로 시작하기 기술 역량 강화 Microsoft 교육 과정을 진행하여 단계별 지침을 얻고 주요 Power BI 기능을 살펴보세요. 자세한 정보 탭으로 돌아가기 사용 사례 See what you can do with Power BI</h2> "> Power BI로 수행할 수 있는 작업 보기 관리되는 신뢰할 수 있는 소스 구축 동일한 환경에서 서로 다른 모든 데이터 원본을 연결하여 모든 데이터에 대한 단일 정보 원본을 설정하세요. 자세히 알아보기 엔터프라이즈 규모 및 셀프 서비스 통합 엔터프라이즈 규모 및 셀프 서비스 BI를 결합하여 조직의 모든 수준에서 인사이트와 혁신을 추진하세요. 자세히 알아보기 어디서나 데이터 환경 사용 사람들이 매일 사용하는 앱과의 업계 최고의 상호 운용을 통해 인사이트와 의사 결정 사이의 격차를 해소하세요. 자세히 알아보기 누구나 데이터로 작업할 수 있도록 지원 모든 사용자가 사용하기 쉬운 인터페이스, 무료 교육 리소스 및 다양한 접근성 기능을 사용하여 데이터를 탐색할 수 있도록 하세요. 자세히 알아보기 즉시 시작하기 사용하기 쉬운 보고서 만들기 환경, AI 생성 보고서 및 수백 개의 보고서 템플릿으로 빠르게 시작하세요. 자세히 알아보기 고객을 위한 BI 보고서 포함 Power BI Embedded를 사용하여 멋진 보고서를 포함함으로써 사용자 고유의 앱에서 유용성과 사용자 참여를 개선하세요. 자세히 알아보기 이전 슬라이드 다음 슬라이드 Establish a governed source of truth</h4> "> 관리되는 신뢰할 수 있는 소스 구축 OneLake에서 데이터를 구성하고, 액세스를 제어하고, 중복을 줄이고, 데이터 메시를 사용하도록 설정하고, 데이터 세트를 보증하고, 검색하세요. 자세한 정보 Unify enterprise scale and self service</h4> "> 엔터프라이즈 규모 및 셀프 서비스 통합 모든 수준에서, 팀 간에 비공식적으로 인사이트와 혁신을 주도하고 IT에서 공식적으로 큐레이팅하고 배포하세요. 자세한 정보 Infuse data experiences everywhere</h4> "> 어디서나 데이터 환경 사용 Microsoft Teams, Microsoft 365 및 Dynamics 365와 같이 사용자가 이미 사용하는 앱과 일치하지 않는 상호 운용성을 확보하세요. 자세한 정보 Empower anyone to work with data</h4> "> 누구나 데이터로 작업할 수 있도록 지원 무료 교육 및 보조 기술을 사용하도록 빌드된 친숙한 인터페이스를 사용하여 데이터 기반 문화를 조성하세요. 교육 리소스 보기 Get started immediately</h4> "> 즉시 시작 끌어서 놓기 캔버스, 보고서를 자동으로 생성할 수 있는 AI 및 수백 개의 템플릿 앱을 사용하여 보고서 작성을 간소화하세요. 앱 찾아보기 Embed BI reports for your customers</h4> "> 고객을 위한 BI 보고서 포함 BI를 사용자 지정, 확장 및 앱에 통합하고 사용자 고유의 브랜드로 브랜딩하여 출시 시간을 단축하세요. 자세한 정보 모달 섹션으로 돌아가기 Power BI + Microsoft 365: Greater productivity</h2> "> Power BI + Microsoft 365: 생산성 향상 Forrester Consulting이 의뢰를 받고 수행한 The Total Economic Impact TM 연구에서 기업이 Power BI와 Microsoft 365를 결합하여 생산성을 높인 방법을 알아보세요. 1 3년간 321%의 투자 수익률 연구 다운로드 <투자금 회수 기간 6개월 연구 다운로드 3년간 총 $38.48M 혜택 연구 다운로드 리서치 및 뉴스 Independent research and news</h2> "> 독립적인 리서치 및 뉴스 이전 탭 다음 탭 2024년 6월 Gartner® Magic Quadrant™ for Analytics and Business Intelligence Platforms 보고서에서 Microsoft가 비전 완성도 및 실행력 항목에서 선두 업체로 선정되었습니다. 2 보고서 읽기 Forrester Consulting의 의뢰를 받은 연구인 The Total Economic Impact™ of Microsoft Fabric에서 379% ROI를 포함한 Microsoft Fabric이 지원하는 비용 절감 및 비즈니스 혜택에 대해 알아보세요. 3 연구 읽기 Microsoft Build에서 발표된 Power BI의 혁신 사항에 대해 알아보세요. 블로그 읽기 탭으로 돌아가기 가격 책정 Plans to suit every need</h2> "> 모든 요구에 맞게 계획 가격 세부 정보 보기 체험 계정 시각적 분석을 갖춘 풍부한 대화형 보고서를 무료로 즉시 만드세요. 무료 무료로 시작하기 시각적 분석을 갖춘 풍부한 대화형 보고서를 무료로 즉시 만드세요. 무료로 시작하기 이 제품은 해당 국가에서는 구매할 수 없습니다. Power BI Pro 공유된 Power BI 보고서에 액세스하고 자체 보고서를 게시하여 더 큰 영향력을 발휘할 수 있습니다. ₩18,900 사용자/월, 연간 결제 가격에는 부가가치세가 포함되어 있지 않습니다. 지금 구매하기 공유된 Power BI 보고서에 액세스하고 자체 보고서를 게시하여 더 큰 영향력을 발휘할 수 있습니다. 가격에는 부가가치세가 포함되어 있지 않습니다. 지금 구매하기 이 제품은 해당 국가에서는 구매할 수 없습니다. 사용자 단위 Power BI Premium 엔터프라이즈 규모 기능을 사용하여 특정 사용자에게 라이선스를 부여하세요. ₩32,400 사용자/월, 연간 결제 가격에는 부가가치세가 포함되어 있지 않습니다. 지금 구매하기 엔터프라이즈 규모 기능을 사용하여 특정 사용자에게 라이선스를 부여하세요. 가격에는 부가가치세가 포함되어 있지 않습니다. 지금 구매하기 이 제품은 해당 국가에서는 구매할 수 없습니다. Microsoft Fabric의 Power BI 유료 라이선스가 없는 사용자와 보고서를 공유하고 단일 용량을 사용하여 Microsoft Fabric 워크로드에 액세스할 수 있습니다. 가변 가격 보기 유료 라이선스가 없는 사용자와 보고서를 공유하고 단일 용량을 사용하여 Microsoft Fabric 워크로드에 액세스할 수 있습니다. 가격 보기 이 제품은 해당 국가에서는 구매할 수 없습니다. 상호 운용성 Powerful alone, better together</h2> "> 단독으로 사용해도 강력하지만, 함께 사용하면 더욱 강력한 성능 이전 슬라이드 다음 슬라이드 Turn ideas into impactful solutions</h3> "> Microsoft Power Platform 효과적인 솔루션 아이디어 구현 모든 사용자가 더 많은 작업을 수행하는 데 도움이 되는 로우 코드 데이터 기반 솔루션을 빌드하기 위해 Power Platform 제품 전체에서 Power BI 인사이트를 포함하세요. 자세한 정보 Connect Power BI across your data estate</h3> "> Microsoft Azure 데이터 자산에서 Power BI 연결 Azure 앱에 Power BI 보고서를 추가하고, Power BI에서 페타바이트 단위의 Azure 데이터를 분석하고, 보고서에 고급 AI 기능 및 인사이트를 적용하세요. 자세한 정보 Get deeper insights in Microsoft 365 apps</h3> "> Microsoft 365 Microsoft 365 앱에서 심층 인사이트 얻기 비즈니스 사용자가 Teams, Excel, PowerPoint, Outlook, SharePoint 등 매일 사용하는 Microsoft 앱에서 데이터를 탐색하고 공유할 수 있도록 지원하세요. 자세한 정보 Manage, govern, and secure your data</h3> "> Microsoft Purview 데이터 관리, 제어 및 보안 Power BI 및 Microsoft Purview를 사용하여 통합 보기에서 손쉬운 데이터 검색, 데이터 카탈로그 및 민감도 레이블 지정을 수행하세요. 자세한 정보 Turn data into impact in business apps</h3> "> Dynamics 365 비즈니스 앱에서 데이터를 영향력으로 전환 Dynamics 365 데이터를 Power BI에 연결하고 비즈니스 애플리케이션에 AI 기반 보고서를 포함하여 사용자가 정보에 입각한 조치를 신속하게 취할 수 있도록 하세요. 자세한 정보 INTEROPERABILITY 섹션으로 돌아가기 보안 Gain visibility into your data estate</h2> "> 데이터 자산에 대한 가시성 확보 기본 제공 보안 기능과 최고의 보안 및 거버넌스 솔루션과의 원활한 상호 운용을 통해 안심할 수 있습니다. 자세히 알아보기 고객 사례 Real customers, real results</h2> "> 고객이 실현한 실제 성과 이전 슬라이드 다음 슬라이드 "우리는 Jacobs가 고객을 위해 수행하는 세계적 수준의 문제에 대해 데이터 기반 문화를 구축하고 있습니다." Alex Mahrou, Jacobs Solutions Inc. 신흥 기술 및 플랫폼 담당 이사 사례 읽기 모든 사례 보기 "이 꿈의 시나리오를 상상해 보세요. 필요한 모든 데이터가 이미 있습니다... 클라이언트 인사이트를 수집하고... 구매자에게 보내세요." Cristian Spuza, Kraft Heinz 고객 개발 책임자 사례 읽기 모든 사례 보기 "모든 데이터를 한 곳에 배치하는 중... 대시보드를 빠르게 빌드할 수 있습니다... 빠르게 인사이트를 얻을 수 있도록 도와줍니다." Anthony Reed, Marks & Spencer 식품 데이터 제품 관리자 사례 읽기 모든 사례 보기 “Power BI는 Microsoft 365 플랫폼과의 상호 운용성 측면에서 다른 도구에 비해 명확한 이점이 있었습니다.” 데이터를 올바른 위치로 가져오는 데 아무런 문제가 없습니다.” Lars Hesse, E.ON Energie Deutschland GmbH의 데이터 분석가 사례 읽기 모든 사례 보기 "분석 관점에서 데이터를 사용하여 진행할 수 있습니다... 데이터 기반 의사 결정의 역량을 강화합니다." Jenny Paulsen, University of South Florida 최고 정보 부책임자 사례 읽기 모든 사례 보기 “Power BI 및 Azure는... 수백 명의 동시 사용자가 수백억 개의 레코드를 처리할 수 있는 성능을 제공했습니다." Jurriaan Amesz, ABN AMRO Bank 수석 제품 소유자 사례 읽기 모든 사례 보기 고객 사례 섹션으로 돌아가기 리소스 Explore everything Power BI has to offer</h2> "> Power BI가 제공하는 모든 항목 살펴보기 시작하기 학습 도움말 이전 다음 이전 슬라이드 다음 슬라이드 Get started with Power BI</h3> "> 평가판 Power BI 시작 데이터 내에서 인사이트를 찾고 풍부한 분석 보고서를 공유하세요. 무료로 체험하기 Get Power BI Desktop</h3> "> 데스크톱 앱 Power BI Desktop 다운로드 시각적 분석을 갖춘 풍부한 대화형 보고서를 즉시 만듭니다. 무료로 다운로드 Get the mobile app</h3> "> 모바일 앱 모바일 앱 다운로드 Windows, iOS, Android용 네이티브 모바일 BI 앱을 사용하여 모든 디바이스에서 라이브 Power BI 대시보드 및 보고서에 안전하게 액세스하고 볼 수 있습니다. 무료로 다운로드 Try Power BI Report Server</h3> "> 온-프레미스 Power BI Report Server 사용해 보기 클라우드로 이동할 수 있는 유연성을 통해 보고용 온-프레미스 솔루션의 평가판을 받으세요. 무료로 사용해 보기 리소스 - 시작 탭 섹션으로 돌아가기 이전 슬라이드 다음 슬라이드 Learn how to use Power BI</h3> "> 과정 Power BI 사용 방법 알아보기 실습 단계별 학습 과정을 통해 목표를 빠르게 충족하고, 확신을 얻고, 원하는 속도로 학습할 수 있습니다. 교육 컬렉션 보기 Read technical documentation</h3> "> 설명서 기술 설명서 읽기 Power BI를 사용하는 방법에 관계없이 요구 사항을 해결하기 위한 전문가 정보 및 답변을 얻으세요. 설명서 보기 Read the Power BI Blog</h3> "> 블로그 Power BI 블로그 읽기 최신 뉴스, 기능 업데이트 및 제품 공지 사항을 확인하세요. 블로그 읽기 리소스로 - 학습 탭 섹션으로 돌아가기 이전 슬라이드 다음 슬라이드 Get Power BI and Microsoft Fabric support</h3> "> 지원 Power BI 및 Microsoft Fabric 지원 받기 Microsoft Fabric에서 서비스 상태를 확인하고 Power BI에 대한 기술 지원을 받으세요. 지원받기 Get expert support and tips</h3> "> 커뮤니티 전문가 지원 및 팁 받기 전 세계 Power BI 커뮤니티 구성원과 연결하여 Power BI 팀이 제공하는 유용한 팁과 조언을 얻으세요. 커뮤니티에 가입 리소스 - 도움말 탭 섹션으로 돌아가기 탭으로 돌아가기 자주 묻는 질문 모두 확장 모두 축소 01/ Power BI란? Power BI는 셀프 서비스 및 엔터프라이즈 BI(비즈니스 인텔리전스)를 위한 확장 가능한 통합 플랫폼입니다. 모든 데이터에 연결하고 시각화하며 매일 사용하는 앱에 시각적 개체를 원활하게 주입하세요. 02/ 조직의 Power BI 라이선스를 선택하려면 어떻게 해야 하나요? Power BI 라이선스는 배타적이지 않으며 플랜과 라이선스를 혼합하고 일치시키는 여러 가지 방법이 있습니다. 예를 들어 가장 인기 있는 보고서를 호스트하기 위해 프리미엄(P-SKU) 또는 Microsoft 패브릭(F-SKU) 용량을 구매한 다음, 보고서를 만들고 게시해야 하는 사용자를 위해 Power BI Pro 라이선스를 구입하거나 Microsoft 365 E5를 통해 얻을 수 있습니다. 자세한 내용은 영업 담당자에게 문의하세요. 영업 팀에 문의 03/ Power BI Embedded란? Microsoft Power BI Embedded는 종량제 Azure PaaS(Platform as a Service) 제품입니다. 이를 통해 앱 개발자는 자체 데이터 시각적 개체 및 컨트롤을 빌드할 필요 없이 앱에 완전한 대화형 보고서를 포함할 수 있습니다. Power BI Embedded 사용해 보기 04/ Microsoft Fabric이란 무엇인가요? Microsoft Fabric은 데이터 이동, 데이터 레이크, 데이터 엔지니어링, 데이터 통합, 데이터 과학, 실시간 분석, 데이터 모니터링 및 비즈니스 인텔리전스를 포함하는 풀서비스 기능을 갖추고 강력한 데이터 보안, 거버넌스 및 규정 준수를 제공하는 공유 플랫폼으로 뒷받침되는 엔드투엔드 분석 솔루션입니다. Microsoft Fabric에 대해 자세히 알아보기 05/ Power BI는 Microsoft Fabric에 어떻게 적합한가요? Power BI는 데이터에서 인사이트를 얻을 수 있는 업계 최고의 BI를 Microsoft Fabric에서 제공합니다. 용량당 Power BI Premium 고객은 간단히 패브릭 테넌트 설정을 켜고 통합 환경에서 나머지 제품에 액세스할 수 있습니다. 또한 통합 용량 모델을 사용하면 모든 Microsoft Fabric 워크로드에 대해 용량당 Power BI Premium을 사용할 수 있습니다. 06/ Power BI Pro 고객인 경우 Microsoft Fabric에 액세스할 수 있나요? Power BI Pro 고객은 Microsoft Fabric 평가판 환경을 통해서만 Fabric 워크로드에 액세스할 수 있습니다. Microsoft Fabric 사용해 보기 07/ 새 F SKU와 이전 P SKU에서 사용할 수 있는 기능은 무엇인가요? 기능 가용성은 SKU 및 용량 수준에 따라 달라집니다. 자세한 내용은 기능 목록 을 참조하세요. Take the next step</h2> "> 다음 단계 수행 무료로 Power BI 사용 시작 Microsoft Fabric에서 무료로 Power BI를 체험하고 데이터 내에서 인사이트를 찾고 풍부한 분석 보고서를 공유하세요. 무료로 체험하기 연락 요청하기 영업일 기준 2일 이내에 Microsoft 전문가 또는 파트너에게 연락 요청을 제출하세요. 요청 보내기 [1] 결과는 인터뷰에 응한 고객을 기반으로 한 복합 조직에 대한 결과입니다. Microsoft를 대신하여 Forrester Consulting에서 수행한 위탁 연구인 Microsoft 365 E5에서 Microsoft Power BI Pro의 Total Economic Impact™, 2023년 7월. 2023년 10월부터 일부 Microsoft 365 및 Office 365 제품군에는 더 이상 Microsoft Teams가 포함되지 않습니다. 해당 플랜 구독자는 Teams 라이선스를 별도로 구매해야 합니다. [2] Gartner, Magic Quadrant for Analytics and Business Intelligence Platforms, Kurt Schlegel, Anirudh Ganeshan, David Pidsley, Julian Sun, Georgia O’Callaghan, Christopher Long, Kevin Quinn, Fay Fei, Edgar Macari, Jamie O’Brien, 2024년 6월 20일. Gartner는 등록 상표 및 서비스 표시이고, Magic Quadrant는 미국 및 국제적으로 Gartner, Inc. 및/또는 그 계열사의 등록 상표이며 허가를 받아 본 문서에 사용되었습니다. All rights reserved. Gartner는 연구 간행물에 등장하는 공급업체, 제품 또는 서비스를 보증하지 않으며, 기술 사용자들에게 점수가 가장 높거나 그 밖의 평가 기준을 갖는 공급업체만 선택하도록 종용하지 않습니다. Gartner 연구 간행물에는 Gartner 연구 조직의 의견이 반영되어 있으며, 이를 사실에 대한 진술로 해석해서는 안 됩니다. Gartner는 본 연구와 관련하여 상업성 또는 특정 목적에의 적합성에 대한 보증을 비롯해 모든 명시적 또는 묵시적 보증을 부인합니다. [3] Microsoft Fabric의 The Total Economic Impact™, Microsof의 위탁으로 실시한 Forrester Consulting Total Economic Impact™ 연구, 2024년 5월. 결과는 인터뷰에 응한 고객을 기반으로 한 복합 조직에 대한 결과입니다. Power BI 팔로우 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 .ow-link-wrapper #chatEngagement{ height: 35px; bottom: 0!important; } .ow-pro-c-body { background-color: #d5d5d5; padding-block-end: 100%; } .ow-pro-c-container-modal { position: fixed; right: 60px; bottom: 50px; z-index: 10040; height: 355px; width: 355px; /* background: #243A5E; */ background-image: linear-gradient(#1278D4 170px, 170px, white 355px 170px); box-shadow: 0px 5px 20px rgba(0, 0, 0, 0.15); } .ow-pro-c-button-container { display: flex; justify-content: flex-end; } .ow-pro-c-close-button { height: 20px; width: 20px; display: flex; margin-block-start: 16px; margin-inline-end: 20px; background: none; border: none; color: #FFFFFF; } .ow-pro-c-h-text, .ow-pro-c-h-text-var-2 { color: #FFFFFF; font-size: 29px; margin-block-start: 0px; text-align: center; } .ow-pro-c-h-text { margin-block-start: 0px; } .ow-pro-c-h-text-var-2 { margin-block-start: 28px; } .ow-pro-c-p-text { color:#FFFFFF; font-size: 16px; margin-block-start: 16px; text-align: center; } .ow-pro-c-image-container { text-align: center; flex-direction: column; } .ow-pro-c-image { height: 75px; width: 75px; margin-block-start: 22px; border-radius: 50%; } button.ow-pro-c-chat-button { margin-block-start: 26px; } .ow-pro-c-button-glyph-container { display: flex; background: none; border: none; margin-block-start: 20px; } .ow-pro-c-no-button { font-size: 16px; font-family: 'Segoe UI'; } .ow-pro-c-no-button.c-glyph { margin-inline-start: 5px; margin-block-start: 2px; } .ow-pro-c-container-modal-var-2 { position: fixed; right: 60px; top: 50%; transform: translateY(-50%); z-index: 10040; height: 355px; width: 355px; background-color: #243A5E; box-shadow: 0px 5px 20px rgba(0, 0, 0, 0.15); } .ow-pro-c-d-flex { display: flex; align-items: center; } .ow-link-wrapper button.ow-pro-c-chat-button-var-2 { background: #ffffff; margin-block-start: 30px; } .ow-link-wrapper button.ow-pro-c-chat-button-var-2:focus:not(.x-hidden-focus) { background: #e5e5e5; } button.c-button.f-primary{ color: #fff!important; background: #0067b8!important; } button.c-button.f-primary:hover{ color: #fff; background: #4e596b; } .ow-pro-c-image-container .c-glyph.glyph-cancel:before{ font-size: 15px; position: relative; top: 1px; } .ow-pro-c-image-container ul {list-style: none; padding-left: 0;} </style> <div class="ow-pro-c-container-modal proactive-chat-hidden" id="proactive-chat-dialog"> <div class="ow-pro-c-button-container"> <button class="ow-pro-c-close-button c-glyph glyph-cancel" aria-label="{{chat-disengagement.aria-label}}" data-bi-cn="Chat_invite_decline" data-bi-bhvr="15" onclick="(window.chatInst.getProactiveChat()).toggle(false)" ></button> </div> <div class="ow-headinghelper-2 ow-pro-c-h-text">{{module.heading}}</div> <div class="c-button f-primary ow-pro-c-p-text"> {{chat-engagement.prompt}} </div> <div class="ow-pro-c-image-container ow-pro-c-d-flex"> <img src="{{module.img-src}}" alt="{{module.img-alt-txt}}" class="ow-pro-c-image" /> <ul data-cta-count="1"> <li class="ow-link-wrapper"> <button id="chatEngagement" aria-label="{{chat-engagement-aria-label}}" class="c-button f-primary ow-pro-c-chat-button" data-bi-cn="Chat_invite_accept" data-bi-bhvr="180" > <span> {{chat-engagement.btn-txt}} </span> </button> </li> </ul> <button id="chatDisengagement" class="ow-pro-c-button-glyph-container ow-pro-c-d-flex" aria-label="{{chat-disengagement.aria-label}}" data-bi-cn="Chat_invite_decline" data-bi-bhvr="15" > <div class="ow-pro-c-no-button">{{chat-disengagement.btn-txt}}</div> <div class="ow-pro-c-no-button c-glyph glyph-cancel"></div> </button> </div> </div>'/> 닫기 구입 전 상담 창구에 문의하기 | 2026-01-13T09:29:40 |
https://www.microsoft.com/ko-kr/ai/energy-resources/mining | 채광 에너지 솔루션 | Microsoft AI This is the Trace Id: 843089a43287c09b25fd2c48f7310ca4 주 콘텐츠로 건너뛰기 Microsoft Microsoft AI Microsoft AI Microsoft AI 홈 제품 및 솔루션 조직용 조직용 Microsoft 365 Copilot Microsoft 365 Copilot 앱 다운로드 조직용 Copilot Agent 365 Customize your Copilot Customize your Copilot Copilot Studio Build your own Build your own Microsoft Foundry Foundry Tools Azure AI 솔루션 파트너 제공 파트너 제공 Microsoft Marketplace Intelligent PCs Intelligent PCs Copilot+ PCs 개인용 개인용 Microsoft Copilot Copilot 앱 다운로드 업계 솔루션 소비재 보안 및 인텔리전스 교육 에너지 및 자원 에너지 및 자원 개요 전력 및 유틸리티 석유 및 가스 채광 금융 서비스 금융 서비스 개요 뱅킹 자본 시장 보험 정부 기관 정부 기관 개요 대중교통 및 도시 인프라 공공 금융 공중 보건 및 복지 서비스 공공 안전 및 정의 의료 서비스 및 생명 과학 의료 서비스 및 생명 과학 개요 공급자 Payors 생명과학 제조 제조 개요 산업 혁신 미디어 및 엔터테인먼트 이동성 이동성 개요 자동차 여행 및 교통 소매 통신 비즈니스 리더를 위한 AI AI 사용 사례 신뢰할 수 있는 AI 책임 있는 AI 책임 있는 AI Microsoft 책임 있는 AI 원칙 및 접근 방식 도구 및 사용 지속 가능성 지속 가능성 지속 가능성 강화 보안 유지 보안 유지 AI 보안 강화 데이터 보호 및 개인 정보 알아보기 AI 101 AI 학습 허브 업계 블로그 Microsoft Cloud 블로그 지원 비즈니스 고객을 위한 지원 산업 문서 자세히 산업 Microsoft for the mining industry</h1> "> 채광 산업을 위한 Microsoft 데이터 기반 디지털 솔루션을 사용하여 혁신을 가속화하고, 프로덕션을 최적화하고, 지속 가능한 채광을 빌드하세요. 비디오 보기 개요 개요 기능 고객 사례 파트너 제품 리소스 개요 Accelerate the energy transition</h2> "> 에너지 전환 가속화 Microsoft의 신뢰할 수 있는 데이터와 AI 솔루션을 사용하여 에너지 및 리소스 업계에서 더 많은 성과를 달성하세요. 에너지 분야 직원의 역량 강화 원활한 협업을 위해 워크플로를 자동화하고 AI 지원 채용, 학습, 교육을 개선합니다. 새로운 에너지 미래를 추구하는 운영 AI를 사용해 공급망, 보안 자산, 전력 에너지 시스템을 최적화하여 생산성을 높입니다. 넷제로 약속 달성 데이터를 활용하여 탄소 배출을 줄이고, 탄소 없는 에너지의 규모를 늘리고, 에너지 가치 사슬에서 탈탄소를 달성합니다. 지속 가능한 AI 기반 비즈니스 성장 기후 혁신, 지속 가능성 진행률, 비즈니스 성장을 가속화하는 명확한 데이터 인사이트를 얻습니다. 기능 Explore use cases</h2> "> 사용 사례 살펴보기 Microsoft의 기술 솔루션을 사용하여 지속 가능한 미래를 구축하세요. 연결된 현장 서비스 일선 작업자가 원격 지원 기능을 통해 모바일 장치 또는 키오스크 및 전문가 지원을 통해 작업 지침을 디지털로 받을 수 있습니다. 디지털 트윈 실제 자산의 현재 상태와 원하는 상태를 비교하는 실시간 디지털 대응을 통해 프로세스 및 의사 결정을 간소화합니다. 실시간 배출 모니터링 목표 대비 배출을 평가하고, 자산 및 프로세스를 조정하고, 운영 동작을 변경하여 지속 가능성 약속을 달성합니다. Computer Vision 거의 실시간으로 비디오를 분석하고, 새로운 운영 인사이트를 생성하고, 안전 및 품질을 향상하고, 영향이 적은 채광 전략을 알릴 수 있습니다. 고객 사례 See how mining leaders are innovating</h2> "> 채광 리더가 혁신하는 방법 보기 이전 슬라이드 다음 슬라이드 “최대한 많은 직원에게 Teams를 제공하고자 합니다. 새로운 정상적이고 더 나은 작업 방식의 일부입니다.” Márcia Binding, 기술 인프라 서비스 임원 제품 Microsoft Teams “Microsoft와 강력한 지속 가능성 솔루션의 도움을 받아 데이터를 더 잘 구성하고 이해할 수 있는 기회를 얻게 되며, 이를 통해 채광 및 시멘트의 지속 가능성을 실현하는 데 도움이 됩니다.” Wouter de Groot, 마케팅 및 지속 가능성 책임자 제품 Microsoft Cloud for Sustainability Microsoft Sustainability Manager 사례 읽기 고객 스토리 섹션으로 돌아가기 파트너 솔루션 Explore more mining solutions</h2> "> 채광 산업 솔루션 살펴보기 Microsoft 파트너 에코시스템에서 채광 산업 솔루션을 살펴보세요. 솔루션 살펴보기 이전 슬라이드 다음 슬라이드 매핑 분석 ArcGIS Pro by Esri 강력한 매핑, 공간 분석 및 데이터 시각화 도구를 가져옵니다. 자세한 정보 분석 Seeq 소프트웨어 산업 회사를 위한 고급 분석 소프트웨어로 공유 인사이트를 사용하도록 설정합니다. 자세한 정보 분석 Sight Machine on Azure 글로벌 제조 조직을 위한 실시간 데이터 기반 분석을 수집합니다. 자세한 정보 업무 환경 안전 Digital Workplace Safety by Stone Three 비디오 장면에서 안전 문제를 식별하고 AI를 사용하여 실시간으로 알림을 생성합니다. 자세한 정보 저장소 분석 GeoSoftware by CGG 더 생산적인 웰을 드릴하고, 현장 개발 계획을 최적화하고, 프로젝트 타임라인을 충족합니다. 자세한 정보 AI & 기계 학습 Cognite Data Fusion 자산이 많은 산업용 업계 최고의 산업용 DataOps 플랫폼을 얻으세요. 자세한 정보 파트너 솔루션 섹션으로 돌아가기 제품 Learn about products for mining</h2> "> 채광 제품에 대해 알아보기 Microsoft의 신뢰할 수 있는 제품으로 채광 회사를 혁신하세요. 이전 슬라이드 다음 슬라이드 Microsoft Power BI 실시간 데이터 기반 인사이트를 사용하여 지속 가능한 에너지 관리 방식을 개선하고 혁신합니다. 자세한 정보 Microsoft Teams 최전방 직원이 효율적으로 소통하고 협업하는 데 필요한 도구를 제공합니다. 자세한 정보 Dynamics 365 Remote Assist 혼합 현실 기술로 현장 작업자의 역량을 강화하여 더욱 스마트하게 작업할 수 있도록 지원합니다. 자세한 정보 Microsoft Power Platform 모든 팀이 로우코드 도구를 사용하여 솔루션을 개발할 수 있도록 지원하여 비즈니스 전반에서 혁신을 주도합니다. 자세한 정보 Azure IoT for Energy 운영 비용을 줄이면서 에너지 관리를 최적화합니다. 자세한 정보 Azure 에너지 생산에서 지능형 그리드까지 작업을 현대화하는 데 도움이 되는 사용자 지정 에너지 솔루션을 구축합니다. 자세한 정보 Dynamics 365 Field Service 기술자에게 최초 문제 해결에 필요한 올바른 정보, 도구, 원격 전문가 지원을 제공합니다. 자세한 정보 IoT용 Windows 개발자 도구, 장기 지원 및 엔터프라이즈급 보안을 사용하여 인텔리전트 에너지 솔루션을 빌드하세요. 자세한 정보 Dynamics 365 Customer Service 에너지 서비스를 지원하고 모든 채널에서 뛰어난 고객 서비스를 제공합니다. 자세한 정보 Azure Digital Twins 스마트 공간, 건물, 전력망에 재사용 가능하고 확장성이 뛰어난 환경을 구축합니다. 자세한 정보 배출 영향 대시보드 조직에서 지속 가능한 에너지에 대해 데이터에 기반한 결정을 내리는 데 도움이 되는 중요한 인사이트를 얻으세요. 자세한 정보 제품 섹션으로 돌아가기 Explore valuable resources</h2> "> 유용한 리소스 살펴보기 Foundations for AI-powered transformation in mining</h3> "> 전자책 • 2025 광산업의 AI 기반 혁신을 위한 기초 AI가 비즈니스의 기존 상태를 어떻게 바꾸고 오늘날 광산업 지도자들에게 어떤 기회를 제공하는지 알아보세요. 전자책 받기 전자책 • 2024 AI 기반 마이닝에서 디지털 혁신의 다음 물결에 참여 전자책 받기 Cloud Migration in the Energy Industry</h3> "> 인포그래픽 • 2023년 4월 에너지 산업의 클라우드 마이그레이션 자세한 정보 Building the mine of the future in the industrial metaverse</h3> "> 전자책 • 2024 산업 메타버스에서 미래의 광산 구축 자세한 정보 다음 단계 Achieve more in the energy industry</h2> "> 에너지 산업에서 더 많은 성과 달성하기 비즈니스 솔루션 허브 클라우드 솔루션 찾기 귀사의 고유한 비즈니스 목표에 적합한 솔루션을 찾으려면 지금 살펴보세요. 모든 솔루션 찾아보기 Microsoft AI AI로 더욱 지속 가능한 미래 구축 AI 기반 솔루션을 통해 에너지 및 리소스 산업을 재창조하고 넷 제로를 달성하세요. 자세한 정보 팔로우하기 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:29:40 |
https://www.atlassian.com/zh/jira/solutions/program-management#tab-def490c4-416a-483f-aabd-8dceed4181ba | 计划管理 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 Jira 为计划管理助力 使用 Jira 简化、精简、交付 了解 Jira 如何帮助您和您的团队将宏伟目标转化为可实现的项目。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行计划管理？ 克服复杂性 无论有多少团队参与其中，即使是最艰巨的战略计划，也要分解成可实现的小步骤。 驾驭依赖关系 在潜在的中断和不确定性影响团队工作之前，提前做好准备。 全面的可见性 查看和组织各团队的工作，以便更好地管理资源配置，做出明智的战略决策。 专为计划管理而设计的模板 适用于各类计划、项目和举措的可定制模板。 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 确定任务的优先次序，管理团队工作量，跟踪工作从规划到完成的整个过程。 开始使用 顶层规划 为您的团队提供清晰、实时的视图，以便进行协作、安排和调整战略目标。 开始使用 流程规划 让您的团队不再重复流程。对各种流程中的步骤进行分类，以便您和您的团队能够快速识别未完成的任务。 开始使用 甘特图 一款强大的可视化工具，用于跟踪工作和避开障碍。概述项目工期，指明里程碑并绘制依赖关系。 开始使用 个人任务跟踪器 跟踪个人任务，如电子邮件分类、会议准备和费用管理。 开始使用 计划和启动项目，全部从 Jira 中进行 规划 需求不断变化？没有关系 分析项目并自信地与利益相关者沟通，明确进度和优先事项。 执行和跟踪 协调工作，简化流程 跟踪项目，映射依赖关系，建立跨团队的审批工作流，并确保目标如期实现。 报告和结果 完善工作流程 有了触手可及的项目摘要，您就能更明智地制定计划，并随时掌握各项举措和项目的进展情况。 计划面板公开测试版 计划或季度规划的新界面 计划面板公开测试版 计划或季度规划的新界面 通过简单的拖放式计划功能，为下个季度规划多个团队的工作。 了解更多 集成您最喜欢的所有工具 将您的工具与 Jira 巧妙地集成，而无需在平台之间进行上下文切换。 查看更多集成 计划管理资源 浏览免费教程、文章和指南以了解更多信息。 敏捷教练 将数十年的敏捷实践提炼成简单易读的课程。 了解更多 项目管理指南 帮助您计划和管理项目的分步说明。 了解更多 协调业务和技术团队 了解如何打破孤岛，开展合作以便创造更好的产品。 阅读博客 转换工作方式 免费获取 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://www.digitalcameraworld.com/buying-guides/the-best-150-600mm-lenses#section-how-we-test-lenses | The best 150-600mm lenses | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Jump to: The quick list 150-600mm lenses Sigma 150-600mm Sports Tamron 150-600mm G2 OM System 150-600mm 150-600mm alternatives Nikon Z 180-600mm Canon RF 100-500mm Sony 200-600mm Tamron 150-500mm Sigma 60-600mm Fuji XF150-600mm Comparisons How to choose How we test lenses FAQS Don't miss these Lenses If I were starting my Pro Sports Photography career again, I’d buy this 180-600mm lens - it's currently got $200 off and under $2,000 Compact Cameras The best full-frame compact cameras – portable powerhouses DSLR Cameras The best DSLR in 2025: Chunky, classic camera designs still loved today Lenses The best lenses for the Canon EOS R50: this camera is a proper little powerhouse and deserves the right lenses Bridge Cameras The best bridge camera: ultra-zoom cameras for far-off subjects Lenses 12 lenses of Christmas: Laowa and Viltrox try to outdo each other for most new lenses in the same month! Lenses The best Nikon Z lenses: the top buys for your Nikon Z-series mirrorless Cameras The best Panasonic Lumix cameras: from Micro Four Thirds to full-frame and bridge cameras Lenses Hands-on Canon RF 45mm f/1.2 STM review: The super-fast glass that's super affordable – and punches way above its price point Lenses The best lenses for the Sony ZV-E10 & ZV-E10 II: smart choices for vlogging and just about any other genre of video and stills photography Lenses The best lenses for the Canon EOS M50 and M50 Mark II: these mini marvels will make the most of your slimline camera Lenses The best Nikon lenses for DSLRs in 2026: brilliant lenses for Nikon F-mount cameras Lenses The best lenses for the Sony A6400: let me help you pick some perfect lenses for your pocket powerhouse Sony body Cameras Best camera for macro photography in 2025: This gear gets great close-up shots! Lenses The best lenses for the Fujifilm X-T5: make the most of all those megapixels Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets Cameras Lenses The best 150-600mm lenses: super-telephoto zooms to get close to the action Buying guides By Matthew Richards Contributions from Lauren Scott last updated 22 December 2025 These are the best 150-600mm lenses to really cover the distance for action, sports and wildlife photography When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . (Image credit: Lauren Scott) Jump to: The quick list 150-600mm lenses Sigma 150-600mm Sports Tamron 150-600mm G2 OM System 150-600mm 150-600mm alternatives Nikon Z 180-600mm Canon RF 100-500mm Sony 200-600mm Tamron 150-500mm Sigma 60-600mm Fuji XF150-600mm Comparisons How to choose How we test lenses FAQS Share Share by: Copy link Facebook X Whatsapp Pinterest Flipboard Share this article Join the conversation Follow us Add us as a preferred source on Google I don’t like to think I’m lazy and I honestly don’t mind ‘zooming with my feet’, but that’s not always possible. To get as close as I’d ideally like, I’d have to jump the barriers at sporting events, sprout my own pair of wings at airshows, and risk getting eaten alive by hungry wildlife. Sometimes discretion is the better part of valor, and a 150-600mm lens can get you close to the action from a respectable (and safe) distance. Originally pioneered by Sigma and adopted by Tamron , 150-600mm lenses used to be a rare breed. Camera manufacturers often didn’t make their own and even if they did, some of the old DSLR examples have now been discontinued. To make this guide as useful as possible, I've included not only ‘150-600mm’ lenses that are currently available, but also a selection of super-telephoto zooms that cover a fairly similar range. The debate on the 'best' zoom range, of course, rages on – many photographers prefer the best 70-200mm lenses or the best 100-400mm lenses as their favorite working distance. However, the 150-600mm outstrips them both in terms of sheer range and raw distance. Matthew Richards Social Links Navigation Lens tester Matthew Richards is a photographer and journalist who has spent years using and reviewing all manner of photo gear. He is Digital Camera World's principal lens reviewer, and as such he has tested more primes and zooms – including plenty of 150-600mm optics – than most people have had hot dinners! The quick list Best mirrorless 1. Sigma 150-600mm f/5-6.3 DG DN OS Sports View at Amazon View at Adorama View at Adorama View at Best Buy Best for mirrorless For Sony E and L-mount mirrorless cameras, this lens is a worthy successor to a DSLR classic. It's got a weather-sealed build and produces pin-sharp imagery. Read more below Best DSLR 2. Tamron SP 150-600mm f/5-6.3 Di VC USD G2 View at Amazon Best for DSLRs Still going strong for Nikon F and Canon EF mounts, Tamron's G2 lens is a refresh of a classic that boasts excellent autofocus and stabilisation. Read more below Best MFT 3. Olympus M.Zuiko 75-300mm f/4.8-6.7 II View at Amazon View at Adorama View at Best Buy Preorder at BHPhoto Best Micro Four Thirds Delivering a 300-1200mm equivalent zoom range thanks to the MFT crop factor, this is an incredibly powerful super-tele zoom that doubles your reach. Read more below Best Nikon Z 4. Nikon Z 180-600mm f/5.6-6.3 VR View at BHPhoto View at Adorama View at Amazon View at Best Buy Best Nikon Z Running very close to the 150-600mm focal range, this lens shaves a bit off the wide end, but still delivers real shooting versatility in a lightweight package. Read more below Best Canon RF 5. Canon RF 100-500mm f/4.5-7.1L IS USM View at Amazon View at Adorama View at Crutchfield View at Target Best Canon RF You lose a little at the tele end but gain a little at the wide end, and Canon's RF 100-500mm delivers brilliant images throughout the whole range. Read more below Best Sony 6. Sony FE 200-600mm F5.6-6.3 G OSS View at Adorama View at Best Buy View at Amazon View at Target Best Sony While Sony users can use Sigma's true 150-600mm, this capable telezoom is a solid Sony-made alternative. The optical stabilisation is highly effective. Read more below Load the next products ↴ Multi-mount mirrorless 7. Tamron 150-500mm f/5-6.7 Di III VC VXD View at KEH Camera View at Adorama View at Amazon View at Best Buy Multi-mount mirrorless Originally just for Sony FE mount, this zoom lens from Tamron has since been made available for Fujifilm X and Nikon Z. It's not quite 600mm, but it's still a great lens. Read more below 10x zoom 8. Sigma 60-600mm f/5-6.3 DG OS HSM | S View at Amazon View at Amazon 10x zoom Need a little more play at the wide end? This Sigma-made lens offers a whopping 10x zoom range for DSLR shooters, and optically it impresses. Read more below Best Fuji 9. Fujifilm XF150-600mm F5.6-8 R LM OIS WR View at Adorama View at Amazon View at Best Buy View at Target Best Fujifilm X Delivering a whopping equivalent zoom range of 229-914mm, this lens certainly provides telephoto reach. It can even be used with 1.4x and 2.0x teleconverters! Read more below Best 150-600mm lenses Why you can trust Digital Camera World Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out how we test. 150-600mm lenses Here are my picks of the best 150-600mm lenses you can buy right now, for both mirrorless and DSLR cameras. Sigma 150-600mm Sports (Image credit: Digital Camera World) 1. Sigma 150-600mm f/5-6.3 DG DN OS Sports The Sports lens finally comes to E-mount and L-mount mirrorless cameras! Our expert review: Specifications Mount: Sony E, Leica L Elements/groups: 25/15 Diaphragm blades: 9 Autofocus: Stepper motor Stabilizer: 4-stops Minimum focus distance: 0.58-2.8m Maximum magnification: 0.34x Filter thread: 95mm Dimensions: 109.4 x 265.6mm Weight: 2,100g Today's Best Deals View at Amazon View at Adorama View at Adorama View at Best Buy Reasons to buy + Superb sharpness + One of few mirrorless options Reasons to avoid - Chunky and heavy - Non-removable tripod collar A retooling of an already excellent DSLR lens, the Sigma 150-600mm f/5-6.3 DG DN OS Sports is the complete package for Sony and Leica L shooters. Pairing superb internal optics with an all-around excellent, weather-sealed build, this heavy-duty zoom lens is a big customer, but is really the only game in town for 150-600mm as far as users of the aforementioned mounts are concerned. Of course, that wouldn't matter if the lens itself was no good. Fortunately, it's excellent. The optical path is a little different from the DSLR version, including 25 elements arranged in 15 groups, and it produces impressive sharpness throughout the entirety of the zoom range. There's some inevitable fall-off in the corners, but not enough to worry about, and it's the sort of thing that will be hidden anyway when you're shooting with a shallow depth of field. The autofocus is excellent, though you'll need to make sure your camera is set up in the optimal way to take advantage of it. The build quality of the lens is also impressive – while no one is going to pretend this is a lightweight lens, it handles well, with tactile zoom and focus rings and a series of on-body controls for functions like AF speed, stabilization intensity, and in a new addition for the mirrorless version, Zoom Torque control to adjust the resistance of the zoom ring. This is an all-around excellent lens that's absolutely worth the money for E-mount and L-mount users. See our full Sigma 150-600mm f/5-6.3 DG DN OS Sports review Image 1 of 4 (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) Swipe to scroll horizontally Features ★★★★★ The lens inherits the high-end features and handling of the older version for DSLRs, in a smaller, lighter package. Design ★★★★★ The design is very refined, while build quality is excellent and includes extensive weather-seals. Performance ★★★★★ Excellent inherent sharpness is further boosted in real terms by highly effective optical stabilization. Value ★★★★★ It’s a pro-grade super-telephoto zoom with a ‘consumer’ price tag, making it standout value. Tamron 150-600mm G2 (Image credit: Future) 2. Tamron SP 150-600mm f/5-6.3 Di VC USD G2 Tamron’s ‘Generation 2’ edition of its 150-600mm lens is seriously revamped Our expert review: Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Mount: Canon EF, Nikon FX, Sony A Elements/groups: 21/13 Diaphragm blades: 9 Autofocus: Ultrasonic (ring-type) Stabilizer: 4.5-stops Minimum focus distance: 2.2m Maximum magnification: 0.16x Filter thread: 95mm Dimensions: 108 x 260mm Weight: 2,010g Today's Best Deals View at Amazon Reasons to buy + Improved autofocus and stabilisation + Good sharpness in long section Reasons to avoid - No optical stabilization in Sony-fit - Sharpness lacking at shorter zoom This G2 (Generation 2) edition of Tamron’s 150-600mm lens is upgraded in pretty much every facet of its features, handling and performance. The LD (Low Dispersion) element count goes from one to three, and BBAR (Broad-Band Anti-Reflection) coatings add to the older lens’s eBAND (Extended Bandwidth and Angular-Dependency) coatings, to further suppress internal reflections. The uprated autofocus system delivers faster performance, better able to track moving subjects and the redesigned VC (Vibration Compensation) system gives class-leading 4.5-stop effectiveness, plus two additional switchable modes. The second mode is for panning and the third applies stabilisation only during exposures, making it easier to track erratically moving objects. However, the optical stabilizer is only featured in the Canon and Nikon mount editions of the lens. With the Sony A-fit edition, you’ll need to rely on in-camera stabilization (note that for Sony mirrorless cameras using the Sony E-mount, you should check out the Tamron 150-500mm f/5-6.7 Di III VC VXD ). Going one better than the Sigma 150-600mm lenses, a new flex zoom lock enables you to lock the zoom at any position, rather than just at settings for which a focal length is marked on the barrel. It also matches the Sigma lenses with compatibility for an optional USB dock, which Tamron calls a ‘TAP-in Console’, for applying customization and firmware upgrades. There’s only a marginal Increase in size and weight over the original Tamron (see below), but the G2 gets superior weather-seals and a fluorine coating on the front element. Overall build quality feels superior. Living up to Tamron’s claims, the G2’s autofocus speed and the effectiveness of its image stabilization are excellent. Image quality is very good overall, but sharpness is a bit of a mixed bag. In our tests, it proved slightly less sharp than the original Tamron lens at short to medium zoom settings, but rather sharper in the 400-600mm sector. It’s a good trade-off, as you’ll usually find yourself using the lens towards the long end of its zoom range. See our full Tamron SP 150-600mm f/5-6.3 Di VC USD G2 review Swipe to scroll horizontally Features ★★★★☆ The ‘Generation 2’ edition of this lens has a strong feature set with upgraded autofocus and stabilization systems. Design ★★★★☆ The design is pretty crafty and I like that this lens is the best part of a kilogram lighter than Sigma’s competing Sports lens for DSLRs. Performance ★★★★☆ Image quality and overall performance are impressive overall but the lens could be sharper at the short end of its zoom range. Value ★★★★☆ The Tamron is keenly priced for a DSLR-focused 150-600mm with high-end specs and handling. OM System 150-600mm (Image credit: James Artaius) 3. OM System M.Zuiko 150-600mm f/5.0-6.3 IS A 150-600mm lens by name, but goes way beyond that in reality Our expert review: Specifications Mount: Micro Four Thirds Elements/groups: 25/15 Diaphragm blades: 9 Autofocus: Yes Stabilizer: Yes (6 stops at 150mm, 5 at 600mm / 7 stops at 150mm, 6 at 600mm with Sync-IS) Minimum focus distance: 0.56-2.8m Maximum magnification: 0.35x (0.7x full frame equivalent) Filter thread: 95mm Dimensions: 264.4x109.4mm (fully extended) Weight: 2,065g Today's Best Deals View at Amazon View at Adorama View at Best Buy Preorder at BHPhoto Reasons to buy + Phenomenal 600-1200mm range + Up to 7 stops of stabilization + IPX1 weather proofing Reasons to avoid - Sharpness is disappointing - A very big and heavy lens - Very expensive The Micro Four Thirds system has a 2x crop factor, relative to a full-frame camera. This means that, although this lens has an advertised 150-600mm focal range, when fitted to an MFT body its field of view will be equivalent to a 300-1200mm full-frame lens. Consequently, this lens offers immense reach for capturing distant subjects, while up to 7 stops of image stabilization helps keep things steady when you're zoomed in to the max. Keen lens nerds may have spotted that this lens looks very similar to the Sigma 150-600mm f/5-6.3 DG DN OS Sports (number 1 on this list). And that's because it is essentially the same lens, adapted for use on Micro Four Thirds bodies. While that has its benefits, as a full-frame lens it does mean the OM System M.Zuiko 150-600mm feels very bulky and heavy compared to more typical MFT optics. During our time reviewing the OM System M.Zuiko 150-600mm , we came away a little disappointed by the lens's overall sharpness, which was significantly down on the performance of the Sigma 150-600mm. But if you must have telescope-rivalling levels of zoom for your Micro Four Thirds camera, this is the only lens to go for. Read our full OM System M.Zuiko 150-600mm f/5.0-6.3 IS review Image 1 of 3 (Image credit: Paul Burrows) (Image credit: Paul Burrows) (Image credit: Paul Burrows) Swipe to scroll horizontally Features ★★★★☆ Top of the features list is the humungous 1200mm maximum ‘effective’ focal length, backed up by as much as 7-stop stabilization. Design ★★★★☆ Build quality is tough, with IPX1 weather-proofing, although it’s big and heavy for a Micro Four Thirds lens. Performance ★★★☆☆ Levels of sharpness are a bit disappointing, especially at longer zoom settings. Value ★★★☆☆ It’s not particularly good value, especially in comparison to the likes of Sigma and Tamron 150-600mm full-frame zooms. 150-600mm alternatives There are a few lenses that give a similar, but slightly different, focal length range to a 150-600mm – and below are some of those which are worth considering: Nikon Z 180-600mm (Image credit: Matthew Richards) 4. Nikon Z 180-600mm f/5.6-6.3 VR A relatively affordable telephoto option for Z-mount mirrorless. Our expert review: Specifications Mount: Nikon Z Elements/groups: 25/17 Diaphragm blades: 9 Autofocus: Linear stepping motor Stabilizer: Yes Min focus distance: 1.3-2.4m Max magnification: 0.25x Filter thread: 95mm Dimensions (WxL): 110x315.5mm Weight: 1955g Today's Best Deals View at BHPhoto View at Adorama View at Amazon View at Best Buy Reasons to buy + Effective 5.5-stop VR + Razor-sharp throughout range + Customisable function buttons Reasons to avoid - Somewhat bulky/heavy - No VR on/off switch This big zoom is as close as Nikon has got to matching the 150-600mm focal length – and it's an outstanding lens. Earning the full five stars in our review, the Nikon Z 180-600mm f/5.6-6.3 VR offers tack-sharp image quality right the way through that zoom range. While it's a relatively hefty lens, it's light enough that you'll be able to use it handheld for a decent chunk of time. We particularly love the four customisable function buttons, which sit just under where the thumb naturally falls. A particular asset of this lens is its optical VR (Vibration Reduction) system, which is rated to provide up to 5.5 stops of effective compensation. This makes the far end of the telephoto much more useable hand-held, and helps you make the most of all that gorgeous sharpness. Great for sports, wildlife and other types of telephoto shooting, the Nikon Z 180-600mm f/5.6-6.3 VR is the best choice for approximating the 150-600mm focal range on Nikon Z cameras. Read our full Nikon Z 180-600mm f/5.6-6.3 VR review Image 1 of 4 (Image credit: Matthew Richards) (Image credit: Matthew Richards) (Image credit: Matthew Richards) (Image credit: Matthew Richards) Swipe to scroll horizontally Features ★★★★★ Compared with Nikon’s F-mount 200-500mm zoom, this one has longer telephoto reach and more effective 5.5-stop optical stabilization. Design ★★★★★ The lens is impeccably built with extensive weather-seals and is noticeably lighter than Nikon’s 200-500mm lens. Performance ★★★★★ Sharpness and clarity are exceptional, even at the longest zoom setting, backed up by super-fast autofocus and highly effective stabilization. Value ★★★★☆ It’s pricier than the F-mount 200-500mm lens but well worth the extra outlay. Canon RF 100-500mm (Image credit: Future) 5. Canon RF 100-500mm f/4.5-7.1L IS USM Not a 150-600mm - but a great option for Canon full-frame mirrorless Our expert review: Specifications Mount: Canon RF Elements/groups: 20/14 Diaphragm blades: 9 Autofocus: Dual Nano USM Stabilizer: Yes Min focus distance: 0.9-1.2m Max magnification: 0.33x Filter thread: 77mm Dimensions (WxL): 93.8x207.6mm Weight: 1530g Today's Best Deals View at Amazon View at Adorama View at Best Buy View at Target Reasons to buy + Lacks the reach of a true 150-600mm + Brilliant image quality Reasons to avoid - Disappointing AF speed on older EOS R bodies - Narrow maximum aperture The Canon RF 100-500mm f/4.5-7.1L IS USM is the first super-telephoto zoom lens for EOS R-system mirrorless cameras. This is a high-quality lens with its L-series build, and even has a heat shield coating for coping with shooting in challenging weather conditions, whether it’s hot or cold. Plus its 5-stop image stabilization will help you deliver sharp shots when shooting handheld with slower shutter speeds and in low light. It lacks the reach of a 150-600mm at its telephoto lens - but compensates for this with its widest tele setting. See our full Canon RF 100-500mm review Image 1 of 2 (Image credit: Matthew Richards/Digital Camera World) (Image credit: Matthew Richards/Digital Camera World) Swipe to scroll horizontally Features ★★★★★ There’s a smorgasbord of features packed into this lens with optical stabilization, dual Nano USM autofocus motors and a very high-end optical path. Design ★★★★★ Flourishes include a zoom ring torque adjustment, carried forward from the EF lens, and robust weather-sealed build quality. Performance ★★★★★ Autofocus performance needs one of the more recent than original EOS R bodies to get the most out of the lens, but image quality is fabulous. Value ★★★★☆ It’s pretty good value for what it is, but this lens will nevertheless make a sizeable dent in your bank balance. Sony 200-600mm (Image credit: Sony) <a href="https://www.digitalcameraworld.com/reviews/sony-fe-200-600mm-f56-63-g-oss-review" data-url="https://www.digitalcameraworld.com/reviews/sony-fe-200-600mm-f56-63-g-oss-review" target="_blank" referrerpolicy="no-referrer | 2026-01-13T09:29:40 |
https://support.microsoft.com/he-il/office/%D7%9E%D7%94-%D7%96%D7%94-%D7%9E%D7%A9%D7%9E%D7%A8%D7%95%D7%AA-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | מה זה 'משמרות'? - תמיכה של Microsoft נושאים קשורים × סרטוני הדרכה בנושא Microsoft Teams התחלה מהירה של Microsoft Teams מהו Microsoft Teams? היכנס והתחל לעבוד נהל שיחת צ‘אט ושתף קבצים שיתוף פעולה מידע נוסף מבוא ל-Microsoft Teams התחל לעבוד עם Microsoft Teams תחילת העבודה עם צ'אט תחילת העבודה עם פגישות התחלת העבודה עם אפליקציות הגדרת הצוות והתאמה אישית שלו יצירת צוות באמצעות תבניות עבודה עם אורחים חיצוניים ניהול הגדרות צוות שיתוף פעולה בצוותים ובערוצים עצה: שליחת הודעת דואר אלקטרוני לערוץ צור תוכנית בעזרת Planner עבוד עם פרסומים והודעות פרסם הודעה בערוצים מרובים חיפוש ואיתור של קבצים העלאה ושיתוף של קבצים חיפוש וסינון של אנשים וקבצים חיפוש וסינון של הודעות עצות עבור קבצי Teams התחלת צ'אטים ושיחות מבט כולל על שיחות Teams ביצוע שיחות עצות עבור שיחות Teams הסתר צ\‘אטים ומחק הודעות הגדרת נציג שיקבל את השיחות שלך ניהול פגישות הצטרף לפגישה של Teams עצות לפגישות Teams היפגש באופן מידי ניהול פגישות קביעת מועד לסמינר מקוון הצג את המסך שלך במהלך פגישה הגדרת אירועים בשידור חי והשתתפות בהם תכנון ותזמון של אירוע בשידור חי הפקת אירוע בשידור חי השתתף באירוע בשידור חי מנחה שאלות ותשובות סיור ביישומים ובכלים חפש אפליקציות והשתמש בהן נהל לוחות זמנים של צוות באמצעות משמרות מה זה 'משמרות'? יצירת לוח זמנים של 'משמרות' ניהול לוח זמנים של 'משמרות' יצירת אישורים מהם אישורים? צור אישור צור אישור מהצ'אט יצירת אישור עם חתימה אלקטרונית גלה תבניות ב-'אישורים' יצירת אישורים באמצעות תבניות יצירת תבניות כלל-ארגוניות פעילויות וירטואליות ב- Microsoft Bookings מהם תורים וירטואליים? שליחת הודעות טקסט SMS של אורחים חיצוניים קבע פגישה הצטרפות לפגישה ניהול הזנת הפעילות שלך ניהול הגדרות הודעה Teams בדרכים התחל צ׳אט מחוץ לבית יצירת ערוץ בדרכים הצטרף לפגישה בעודך בדרכים הזנת פעילות בדרכים דלג לתוכן הראשי Microsoft תמיכה תמיכה תמיכה דף הבית Microsoft 365 Office תמיכה של Teams נושאים פגישות צ'אט הודעות והגדרות צוותים וערוצים שיחות ומכשירים קבצים אפליקציות ושירותים התחלה מהירה צ'אט צ‘אט קבוצתי הודעות Teams ערוצים שיחות קבצים אפליקציות רכיבי Loop מה חדש משאבים הדרכה בווידאו פתרון בעיות כאן ב- Teams נגישות תכונות Teams לפי פלטפורמה Microsoft Teams (חינם) פורומי קהילה בלוג הקהילה הטכנית הדרכה בהנחיית מדריך עבור מנהלי מערכת ומומחי IT למגזר החינוך עוד קנה את Microsoft 365 כל Microsoft Global Microsoft 365 Teams Copilot Windows Xbox תמיכה תוכנה תוכנה אפליקציות של Windows AI OneDrive Outlook עוברים מ- Skype ל-Teams OneNote Microsoft Teams מחשבים והתקנים מחשבים והתקנים קנה Xbox חומרה בידור בידור Xbox Game Pass Ultimate Xbox משחקי מחשב לעסקים לעסקים האבטחה של Microsoft Azure Dynamics 365 Microsoft 365 לעסקים Microsoft Industry Microsoft Power Platform Windows 365 מפתח ו-IT מפתח ו-IT מפתח של Microsoft Microsoft Learn תמיכה באפליקציות השוק של AI קהילת Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards אחרים אחרים הורדות בחינם ואבטחה חינוך כרטיסי מתנה הצג את מפת האתר חיפוש חיפוש עזרה אין תוצאות ביטול היכנס היכנס דרך Microsoft היכנס או צור חשבון. שלום, בחר חשבון אחר. יש לך חשבונות מרובים בחר את החשבון שברצונך להיכנס באמצעותו. נושאים קשורים סרטוני הדרכה בנושא Microsoft Teams התחלה מהירה של Microsoft Teams מהו Microsoft Teams? היכנס והתחל לעבוד נהל שיחת צ‘אט ושתף קבצים שיתוף פעולה מידע נוסף מבוא ל-Microsoft Teams התחל לעבוד עם Microsoft Teams תחילת העבודה עם צ'אט תחילת העבודה עם פגישות התחלת העבודה עם אפליקציות הגדרת הצוות והתאמה אישית שלו יצירת צוות באמצעות תבניות עבודה עם אורחים חיצוניים ניהול הגדרות צוות שיתוף פעולה בצוותים ובערוצים עצה: שליחת הודעת דואר אלקטרוני לערוץ צור תוכנית בעזרת Planner עבוד עם פרסומים והודעות פרסם הודעה בערוצים מרובים חיפוש ואיתור של קבצים העלאה ושיתוף של קבצים חיפוש וסינון של אנשים וקבצים חיפוש וסינון של הודעות עצות עבור קבצי Teams התחלת צ'אטים ושיחות מבט כולל על שיחות Teams ביצוע שיחות עצות עבור שיחות Teams הסתר צ\‘אטים ומחק הודעות הגדרת נציג שיקבל את השיחות שלך ניהול פגישות הצטרף לפגישה של Teams עצות לפגישות Teams היפגש באופן מידי ניהול פגישות קביעת מועד לסמינר מקוון הצג את המסך שלך במהלך פגישה הגדרת אירועים בשידור חי והשתתפות בהם תכנון ותזמון של אירוע בשידור חי הפקת אירוע בשידור חי השתתף באירוע בשידור חי מנחה שאלות ותשובות סיור ביישומים ובכלים חפש אפליקציות והשתמש בהן נהל לוחות זמנים של צוות באמצעות משמרות מה זה 'משמרות'? יצירת לוח זמנים של 'משמרות' ניהול לוח זמנים של 'משמרות' יצירת אישורים מהם אישורים? צור אישור צור אישור מהצ'אט יצירת אישור עם חתימה אלקטרונית גלה תבניות ב-'אישורים' יצירת אישורים באמצעות תבניות יצירת תבניות כלל-ארגוניות פעילויות וירטואליות ב- Microsoft Bookings מהם תורים וירטואליים? שליחת הודעות טקסט SMS של אורחים חיצוניים קבע פגישה הצטרפות לפגישה ניהול הזנת הפעילות שלך ניהול הגדרות הודעה Teams בדרכים התחל צ׳אט מחוץ לבית יצירת ערוץ בדרכים הצטרף לפגישה בעודך בדרכים הזנת פעילות בדרכים מה זה 'משמרות'? חל על Teams Microsoft Teams שווה לנסות! האפליקציה 'משמרות' ב- Microsoft Teams היא כלי לניהול לוחות זמנים ומעקב אחר זמנים, שמסייע לך ליצור, לעדכן ולנהל לוחות זמנים עבור הצוות שלך. לוחות זמנים - צור, ערוך ונהל לוח זמנים עבור הצוות שלך. לוח זמנים של 'משמרות' מציג ימים בחלק העליון, חברי צוות מופיעים בצד ימין, וממשמרת שהוקצתה מופיעה בלוח השנה. הגדרות לוח זמנים - בהגדרות Shift, הגדר את אפשרויות לוח הזמנים ובחר את היכולות של Shifts שברצונך להפוך לזמינים לצוות שלך. קבוצות - הוסף קבוצות תזמון כדי לארגן חברי צוות בלוח הזמנים לפי סוג משימה או מיקום. Shifts - הקצאת משמרות לחברי צוות. צור משמרת מאפס או העתק משמרת קיימת. פתח משמרות - כל קבוצה בלוח הזמנים כוללת שורת 'פתח משמרות '. הוסף משמרות פתוחות ללוח הזמנים שלך שכל אחד יכול לבקש. שעון זמן - הפעל שעון זמן בהגדרות Shift כדי לאפשר לצוות שלך להיכנס ולהוות את המשמרות. בקשות - סקור בקשות וגיב לבקשות עבור זמן קצוב, משמרות פתוחות, החלפת משמרות והצעות. תגיות - השתמש בתגיות מבוססות Shift כדי לקיים תקשורת מהירה עם כל אדם הנמצא כעת במשמרת. פרסם את לוח הזמנים שלך - לאחר שתסיים לבצע שינויים בלוח הזמנים, שתף אותו עם הצוות שלך כדי שכולם יוכלו להיות מעודכנים. מעוניין במידע נוסף? התחל לעבוד עם ‘משמרות‘ יצירת לוח זמנים של צוות ב'משמרות' הוספת משמרות ללוח הזמנים ב'משמרות' פרסום לוח זמנים ב'משמרות' ניהול בקשות משמרת ושעה ב'משמרות' הפעלת תגיות מבוססות Shift ב- Teams הרשמה כמנוי להזנות RSS זקוק לעזרה נוספת? מעוניין באפשרויות נוספות? לגלות קהילה גלה את יתרונות המנוי, עיין בקורסי הדרכה, למד כיצד לאבטח את המכשיר שלך ועוד. הטבות מינוי Microsoft 365 הדרכת Microsoft 365 אבטחת Microsoft מרכז הנגישות קהילות עוזרות לך לשאול שאלות ולהשיב עליהן, לתת משוב ולשמוע ממומחים בעלי ידע עשיר. שאל את Microsoft Community Microsoft Tech Community משתתפי Windows Insider משתתפי Insider של Microsoft 365 האם מידע זה היה שימושי? כן לא תודה! יש לך עוד משוב ל- Microsoft? האם תוכל לעזור לנו להשתפר? (שלח משוב ל- Microsoft כדי שנוכל לעזור.) עד כמה אתם מרוצים מאיכות השפה? מה השפיע על החוויה שלך? הבעיה נפתרה הוראות ברואות קל לעקוב אחרי אין ז'רגון תמונות עזרו איכות תרגום לא מתאים למסך שלי הוראות שגויות טכני מדי אין מספיק מידע אין מספיק תמונות איכות תרגום יש לך משוב נוסף? (אופציונלי) שליחת משוב בלחיצה על 'שלח', אתה מאפשר למשוב שלך לשפר מוצרים ושירותים של Microsoft. מנהל ה-IT שלך יוכל לאסוף נתונים אלה. הצהרת הפרטיות. תודה על המשוב! × מה חדש Copilot לארגונים Copilot לשימוש אישי Microsoft 365 אפליקציות של Windows 11 Microsoft Store פרופיל החשבון מרכז ההורדות החזרות מעקב אחר הזמנות חינוך Microsoft Education מכשירים לחינוך Microsoft Teams בתחום החינוך Microsoft 365 Education Office Education הדרכות ופיתוח למחנכים מבצעים לתלמידים ולהורים Azure לסטודנטים עסק האבטחה של Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams מפתח ו-IT מפתח של Microsoft Microsoft Learn תמיכה באפליקציות השוק של AI קהילת Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio חברה קריירה אודות Microsoft פרטיות ב-Microsoft משקיעים קיימות עברית (ישראל) סמל ביטול הצטרפות מהאפשרויות הפרטיות שלך אפשרויות הפרטיות שלך סמל ביטול הצטרפות מהאפשרויות הפרטיות שלך אפשרויות הפרטיות שלך פרטיות בריאות הצרכן צור קשר עם Microsoft פרטיות ניהול קבצי Cookie תנאי השימוש סימנים מסחריים אודות הפרסומות שלנו נגישות © Microsoft 2026 | 2026-01-13T09:29:40 |
https://support.microsoft.com/cs-cz/microsoft-store-and-billing | Microsoft Store a nápověda k fakturaci Přeskočit na hlavní obsah Microsoft Podpora Podpora Podpora Domů Microsoft 365 Office Produkty Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows a další... Zařízení Surface Počítačové příslušenství Xbox Hraní počítačových her HoloLens Surface Hub Záruky na hardware Účet a fakturace Klient Microsoft Store & fakturace Prostředky Co je nového Komunitní fóra Správci Microsoft 365 Upozornění pro malé firmy Pro vývojáře Vzdělávání Nahlásit podvod při poskytování technické podpory Bezpečnost produktů Více Koupit Microsoft 365 Vše od Microsoftu Global Microsoft 365 Teams Copilot Windows Surface Xbox Nabídky Podpora Software Software Aplikace pro Windows Umělá inteligence OneDrive Outlook Přechod ze Skypu na Teams OneNote Microsoft Teams Počítače a zařízení Počítače a zařízení Koupit Xbox Příslušenství Zábava Zábava Xbox Game Pass Ultimate Konzole Xbox a hry Hry pro PC Nabídky pro firmy Nabídky pro firmy Microsoft Security Azure Dynamics 365 Microsoft 365 pro firmy Microsoft Industry Microsoft Power Platform Windows 365 Vývojáři a IT Vývojáři a IT Microsoft pro vývojáře Microsoft Learn Podpora aplikací s umělou inteligenci v obchodě Marketplace Odborná komunita Microsoft Microsoft Marketplace Visual Studio Marketplace Rewards Další Další Zdarma ke stažení a zabezpečení Vzdělávání Dárkové karty Zobrazit mapu stránek Hledat Hledat nápovědu Žádné výsledky Zrušit Přihlásit se Přihlásit se pomocí účtu Microsoft Přihlaste se nebo si vytvořte účet. Dobrý den, Vyberte jiný účet. Máte více účtů. Zvolte účet, pomocí kterého se chcete přihlásit. Microsoft Store a nápověda k fakturaci Správa předplatných Vrácení & refundace Možnosti platby Historie objednávek Dárkové karty Instalace Microsoftu 365 Microsoft Store ve Windows Prozkoumání služeb Microsoft Storu Od dopravy zdarma a vrácení zboží až po naši 60denní cenovou ochranu jsme tu, abychom vám pomohli dělat více s nejlepšími zařízeními, softwarem, hrami a prostředky ve své třídě. Podívejte se, co nabízí Microsoft Store: Podpora pro nákupy a nákupy | Nastavení a školení produktu | Podpora pro malé firmy Podpora pro nákupy a nákupy Služby Microsoft Store nejsou dostupné ve všech oblastech. Pokud chcete zjistit, jaké možnosti máte k dispozici, vyberte svoji zemi nebo oblast z rozevíracího seznamu níže, a pokud v seznamu nejsou, vyberte Další oblasti . Vyberte oblast. Spojené státy Austrálie Kanada (angličtina) Kanada (francouzština) Spojené království Jiné oblasti Proč nakupovat v Microsoft Storu Snadné a pohodlné nakupování Doprava zdarma 2-3 dny Bezplatné 60denní vrácení 60denní cenová ochrana Flexibilní možnosti platby Hotovost za použité zařízení Obchod a recyklace Speciální slevy a nabídky Pro studenty, rodiče a vyučující Pro vojenský personál Rozšířená ochrana zařízení Plán ochrany Microsoft Complete Pomůžeme vám najít to, co potřebujete Nápověda podpory před nákupem Answer Desk pro osoby se zdravotním postižením Nakupování s přidruženým partnerem ASL Proč nakupovat v Microsoft Storu Snadné a pohodlné nakupování Doprava zdarma Bezplatné 60denní vrácení 60denní cenová ochrana Hotovost za použité zařízení Obchod a recyklace Speciální slevy a nabídky Pro studenty, rodiče a vyučující Pomůžeme vám najít to, co potřebujete Nápověda podpory před nákupem Answer Desk pro osoby se zdravotním postižením Proč nakupovat v Microsoft Storu Snadné a pohodlné nakupování Doprava zdarma Bezplatné 60denní vrácení 60denní cenová ochrana Hotovost za použité zařízení Obchod a recyklace Speciální slevy a nabídky Pro studenty, rodiče a vyučující Rozšířená ochrana zařízení Plán ochrany Microsoft Complete Pomůžeme vám najít to, co potřebujete Pokud máte před nákupem nějaké otázky, pohovte si s odborníkem na produkty nebo si zarezervujte nákupní schůzku. Nápověda podpory před nákupem Proč nakupovat v Microsoft Storu Snadné a pohodlné nakupování Doprava zdarma Bezplatné 60denní vrácení 60denní cenová ochrana Hotovost za použité zařízení Obchod a recyklace Speciální slevy a nabídky Pro studenty, rodiče a vyučující Rozšířená ochrana zařízení Plán ochrany Microsoft Complete Proč nakupovat v Microsoft Storu Snadné a pohodlné nakupování Doprava zdarma Bezplatné 60denní vrácení 60denní cenová ochrana Hotovost za použité zařízení Obchod a recyklace Speciální slevy a nabídky Pro studenty, rodiče a vyučující Pomůžeme vám najít to, co potřebujete Nápověda podpory před nákupem Answer Desk pro osoby se zdravotním postižením Proč nakupovat v Microsoft Storu Pomůžeme vám najít to, co potřebujete Pokud máte před nákupem nějaké otázky, pohovte si s odborníkem na produkt. Nápověda podpory před nákupem Procházet Microsoft Store The Microsoft Store Nastavení a školení produktu Ne všechny služby Microsoft Store uvedené tady jsou dostupné ve všech oblastech. Pokud chcete zobrazit své možnosti, vyberte v rozevíracím seznamu níže svoji zemi nebo oblast: Vyberte oblast. Spojené státy Austrálie Kanada (angličtina) Kanada (francouzština) Spojené království Jiné oblasti Nápověda a výukové materiály Podívejte se na zdroje informací o podpoře produktů, které vám pomůžou najít odpovědi, které potřebujete. Zařízení Surface | Xbox Microsoft 365 | Windows Nápověda a výukové materiály Naše zdroje podpory produktů jsou tady, aby vám pomohly najít odpovědi, které potřebujete. Zařízení Surface | Xbox Microsoft 365 | Windows Nápověda a výukové materiály Podívejte se na zdroje informací o podpoře produktů, které vám pomůžou najít odpovědi, které potřebujete. Zařízení Surface | Xbox Microsoft 365 | Windows Nápověda a výukové materiály Podívejte se na zdroje informací o podpoře produktů, které vám pomůžou najít odpovědi, které potřebujete. Zařízení Surface | Xbox Microsoft 365 | Windows Nápověda a výukové materiály Podívejte se na zdroje informací o podpoře produktů, které vám pomůžou najít odpovědi, které potřebujete. Zařízení Surface | Xbox Microsoft 365 | Windows Nápověda a výukové materiály Podívejte se na zdroje informací o podpoře produktů, které vám pomůžou najít odpovědi, které potřebujete. Zařízení Surface | Xbox Microsoft 365 | Windows Podpora pro malé firmy Pokud chcete zjistit, jaké možnosti podpory pro malé firmy jsou ve vaší oblasti dostupné, vyberte v rozevíracím seznamu níže svoji zemi nebo oblast: Vyberte oblast. Spojené státy Austrálie Kanada (angličtina) Kanada (francouzština) Spojené království Jiné oblasti Prostředky pro vaši malou firmu Získejte rady, bezplatná školení, produkty a nástroje, které vaší firmě pomohou vzkvétat. Nápověda a výuka pro malé firmy Centrum zdrojů pro malé firmy Prostředky pro vaši malou firmu Získejte rady, bezplatná školení, produkty a nástroje, které vaší firmě pomohou vzkvétat. Nápověda a výuka pro malé firmy Centrum zdrojů pro malé firmy Prostředky pro vaši malou firmu Získejte rady, bezplatná školení, produkty a nástroje, které vaší firmě pomohou vzkvétat. Nápověda a výuka pro malé firmy Centrum zdrojů pro malé firmy Prostředky pro vaši malou firmu Jsme tu, abychom vám pomohli, ať už vyhodnocujeme vaše obchodní potřeby, až po pomoc s nastavením a řešením potíží. Získejte rady, bezplatná školení, produkty a nástroje, které vaší firmě pomohou vzkvétat. Nápověda a vzdělávací obsah pro malé firmy Centrum zdrojů pro malé firmy Prostředky pro vaši malou firmu Získejte rady, bezplatná školení, produkty a nástroje, které vaší firmě pomohou vzkvétat. Nápověda a výuka pro malé firmy Centrum zdrojů pro malé firmy Prostředky pro vaši malou firmu Získejte rady, bezplatná školení, produkty a nástroje, které vaší firmě pomohou vzkvétat. Nápověda a výuka pro malé firmy Co je nového Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot pro organizace Copilot pro osobní používání Microsoft 365 Prohlédnout produkty Microsoft Microsoft Store Profil účtu Centrum stahování Podpora pro Microsoft Store Vrácení Sledování objednávky Recyklace Commercial Warranties Vzdělávání Microsoft Education Zařízení pro vzdělávání Microsoft Teams pro vzdělávání Microsoft 365 Education Office Education Vzdělávání a rozvoj pedagogů Akce pro studenty a rodiče Azure pro studenty Firmy Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Vývojáři a IT Microsoft pro vývojáře Microsoft Learn Podpora aplikací s umělou inteligenci v obchodě Marketplace Odborná komunita Microsoft Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Společnost Kariéra Novinky u společnosti Microsoft a ochrana osobních údajů Investoři Udržitelnost Čeština (Česko) Ikona nesouhlasu s volbami ochrany osobních údajů Vaše volby ochrany osobních údajů Ikona nesouhlasu s volbami ochrany osobních údajů Vaše volby ochrany osobních údajů Ochrana osobních údajů spotřebitele ve zdravotnictví Kontaktovat Microsoft Ochrana osobních údajů Spravovat soubory cookie Podmínky používání Ochranné známky O našich reklamách EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:40 |
https://git-scm.com/book/it/v2/Distributed-Git-Distributed-Workflows | Git - Distributed Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distributed Git - Distributed Workflows Now that you have a remote Git repository set up as a point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. Distributed Workflows Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally on a central hub. In Git, however, every developer is potentially both a node and a hub – that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This opens a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model–the centralized workflow. One central hub, or repository, can accept code, and everyone synchronizes their work to it. A number of developers are nodes – consumers of that hub – and synchronize to that one place. Figura 54. Centralized workflow. This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. Integration-Manager Workflow Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow. ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an e-mail asking them to pull changes. The maintainer adds the contributor’s repo as a remote and merges locally. The maintainer pushes merged changes to the main repository. Figura 55. Integration-manager workflow. This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes – each party can work at their own pace. Dictator and Lieutenants Workflow This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants. All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator’s repository serves as the reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow. ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the dictator. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. The dictator pushes their master to the reference repository so the other developers can rebase on it. Figura 56. Benevolent dictator workflow. This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. Workflows Summary These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://marketplace.atlassian.com/apps/1219518/confluence-cloud-for-slack-official?hosting=cloud&tab=overview | Confluence Cloud for Slack (Official) | Atlassian Marketplace For a better experience, update to Internet Explorer 11 or later, or use a different browser. . Your browser is incompatible, so things might not work properly. Skip to: Skip to Main content Marketplace Works with Categories Resources Regulated sectors Sign in Confluence Cloud for Slack (Official) by Atlassian works with Confluence Cloud Discover more Free app More actions OVERALL RATINGS No reviews yet SUPPORT Partner Supported TRUST SIGNALS Cloud Security Participant Showing details for Cloud Overview Reviews Privacy & Security Support Installation Key highlights of the app Have one place to stay up to date on the work that's happening in Confluence straight from your Slack Channel Fine-tuned Slack notifications Ditch the email inbox and get your Confluence notifications in Slack so you never miss important @mentions, comments, or page updates again. Interact with content without leaving Slack Move work forward without ever leaving Slack by liking, watching, starring, and commenting on pages right from notifications and content previews in Slack Meaningful content previews Turn raw Confluence links into meaningful content your team can discuss with automatic previews of pages, blogs, and comments when you share their links in Slack More details The Confluence Cloud app for Slack gives you one place to stay up to date on the work that's happening in Confluence straight from your Slack channel. Keep interactions with your team productive with contextual and actionable notifications. With the app your team can: Customize and receive granular notifications to stay on top of changes across your spaces, pages (even child pages!), and blogs in Confluence See link previews of pages, blogs, and comments when you share them with your team in your channel Take action on content such as replying to a comment or liking a page without ever leaving Slack Resources App documentation Comprehensive set of documentation from the partner on how this app works Privacy and Security Privacy policy Atlassian's privacy policy is applicable to the use of this app. Atlassian privacy policy Security program This app is part of the Marketplace Bug Bounty program. About Bug Bounty program Version information Version 1.0 • for Confluence Cloud Release date Aug 31st 2018 Summary This is the initial release of the Confluence Cloud app for Slack Details The 1.0 release of Confluence Cloud for Slack allows you to easily set up granular notifications for your Slack channels, preview links of Confluence content, and take actions directly from Slack. Payment model Free License type Atlassian Closed-Source Learn and explore What’s Marketplace App installation About Atlassian Atlassian resources Search and ranking Atlassian events Atlassian foundation Connect Get support Partner connect Developer resources Solution partner directory Atlassian communication channels Follow Privacy Policy Terms of Use Copyright © 2026 Atlassian | 2026-01-13T09:29:40 |
https://git-scm.com/book/sv/v2/Distribuerade-Git-Distribuerade-arbetsfl%c3%b6den | Git - Distribuerade arbetsflöden About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Bilaga A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in PowerShell A1.7 Summary A2. Bilaga B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bilaga C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distribuerade Git - Distribuerade arbetsflöden Nu när du har ett fjärrarkiv för Git inställt som en hub för samtliga utvecklare, och du är bekant med grundläggande Git-kommandon lokalt, ska vi titta på hur man använder några av de distribuerade arbetsflöden som Git erbjuder. I det här kapitlet kommer du att lära dig att arbeta med Git i en distribuerad miljö, både som bidragslämnare och förvaltare. Du kommer alltså att lära dig hur du framgångsrikt bidar med kod till ett projekt och gör det så enkelt för dig och den som underhåller projektet som möjligt, samt hur du framgångsrikt förvaltar ett projekt med flera utvecklare som bidrar. Distribuerade arbetsflöden Till skillnad från centraliserade versionshanteringssystem (CVCS) tillåter Gits distribuerade natur mer flexibilitet när utvecklare ska samarbeta. I centraliserade system är varje utvecklare en nod som arbetar mer eller mindre likvärdigt mot ett nav. I Git däremot, kan varje utvecklare både en nod och ett nav samtidigt; varje utvecklare kan parallellt bidra med kod till andras arkiv och själv underhålla ett öppet arkiv som andra kan bidra till. Det öppnar upp för en mängd olika möjligheter att organisera samarbetet i ditt projekt och/eller i ditt team. Vi kommer att titta närmare på några vanliga processer som drar nytta av den här flexibiliteten. Vi går igenom både styrkor och svagheter för varje arbetsprocess; du kan välja att använda en enda eller blanda och matcha de finesser som verkar passa bäst. Centraliserad arbetsprocess Centraliserade system har i stort sett en enda samarbetsmodell — den centraliserade arbetsprocessen. Ett nav, eller arkiv , accepterar kod från utvecklarna, som alla synkroniserar sitt arbete mot det. Utvecklarna är noder till den centrala enheten. Figur 54. Centraliserad arbetsprocess. Det innebär att om två utvecklare klonar navet och gör ändringar, så kan den första utvecklaren som skickar upp sina ändringar göra det utan problem. Den andra utvecklaren måste däremot sammanfoga den första utvecklarens arbete innan den skickar upp sina ändringar, annars kommer de nya ändringarna att skrivas över. Det är likadant i Git som i Subversion (eller något annat CVCS), och i Git fungerar modellen utmärkt. Om du redan är bekväm med en centraliserad arbetsprocess i ditt företag eller team kan du enkelt fortsätta använda den i Git. Det är bara att sätta upp ett enda arkiv och ge alla i teamet skrivbehörighet; Git kommer inte att låta användare skriva över varandras arbeten. Låt oss säga att John och Jessika båda börjar arbeta samtidigt. John avslutar sina ändringar och skickar upp dem till servern. Sen försöker Jessika att skicka upp sina, men servern avvisar dem. Hon får veta att hon försöker skicka upp ändringar som inte kan snabbspolas, och att hon inte kommer att kunna göra det förrän hon först hämtar och sammanfogar incheckade ändringar. Detta arbetsflöde är tilltalande för många eftersom det är ett tillvägagångssätt många är bekanta och bekväma med. Det är heller inte begränsat till små team. Gits grenmodell gör det möjligt för hundratals utvecklare att arbeta framgångsrikt på ett enda projekt genom dussintals grenar på en och samma gång. Integrationsstyrd arbetsprocess Eftersom Git tillåter dig att ha flera fjärrarkiv är det möjligt att med ett arbetsflöde där varje utvecklare har skrivbehörighet till sitt eget öppna arkiv och läsbehörighet till andras. Detta scenario inkluderar ofta ett arkiv som representerar det “officiella” projektet. För att bidra till det projektet gör du en öppen klon av det som du skickar dina ändringar till. Sen kan du skicka en förfrågan till den som förvaltar det officiella projektet att hämta dina ändringar. Förvaltaren kan då lägga till ditt arkiv som ett fjärrarkiv, testa dina ändringar lokalt, sammanfoga dem i sin gren och skicka till det officiella arkivet. Processen ser ut så här (se Integrationssstyrt arbetsflöde. ): Förvaltaren skickar till sitt öppna arkiv. En deltagare klonar arkivet och gör ändringar. Deltagaren skickar sina ändringar till sin egna öppna klon. Deltagaren skickar ett e-postmeddelande till förvaltaren och ber denne att hämta ändringarna. Förvaltaren lägger till deltagarens arkiv som ett fjärrarkiv och slår ihop ändringarna lokalt. Förvaltaren skickar de sammanslagna ändringarna till det officiella arkivet. Figur 55. Integrationssstyrt arbetsflöde. Detta är ett mycket vanligt arbetsflöde som används av verktyg som GitHub eller GitLab, där det är enkelt att förgrena ett projekt och skicka upp sina ändringar. En av de största fördelarna med detta tillvägagångssätt är att du kan fortsätta att arbeta vidare, och den som underhåller det officiella arkivet kan hämta in dina ändringar när som helst. Bidragslämnaren behöver inte vänta på att ändringarna ska slås samman innan hen kan börja på något nytt — varje part kan istället arbeta i sin egen takt. Diktatorns och löjtnanternas arbetsflöde Diktatorns och löjtnanternas arbetsflöde är en variant av ett flerarkivsarbetsflöde. Det används vanligtvis i stora projekt med hundratals medarbetare; ett känt exempel är Linuxkärnan. Där har integrationsansvariga hand om varsin del av arkivet; de kallas löjtnanter . Löjtnanterna har en gemensam integrationsansvarig som kallas den välvillige diktatorn. Den välvillige diktatorn är den enda med skrivrättigheter till det heliga referensarkiv, som alla medverkande hämtar kod från. Flödet fungerar så här (se Den välvillige diktatorns arbetsflöde. ): Utvecklarna arbetar på sina egna funktionsgrenar och ombaserar sitt arbete till toppen av “master”. “Master”-grenen är det referensarkiv som endast diktatorn skickar ändringar till. Löjtnanterna slår samman utvecklarnas funktionsgrenar med sina respektive “master”-grenar. Diktatorn slår samman löjtnanternas “master”-grenar med sin egen “master”-gren. Slutligen skickar diktatorn sin “master”-gren till referensarkivet, så att de andra utvecklarna kan ombasera från den. Figur 56. Den välvillige diktatorns arbetsflöde. Det här arbesflödet är inte så vanligt, men kan vara användbart i mycket stora projekt eller hierarkiska miljöer. Det gör det möjligt för projektledaren (diktatorn) att delegera mycket av arbetet och samla stora kodändringsuppsättningar innan de integreras. Sammanfattning av arbetsflöden Det här är några av de vanligaste arbetsflödena i distribuerade system, som till exempel Git, men det är möjligt att anpassa dem efter specifika omständigheter i ett projekt. Nu när du (förhoppningsvis) kan avgöra vilken kombination av arbetsflöden som kan fungera för dig, kommer vi att gå igenom några mer specifika exempel på hur du kan utföra de huvudsakliga rollerna som ingår i processerna. I näste avsnitt kommer du att lära dig om några vanliga tillvägagångssätt för att bidra till ett projekt. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://git-scm.com/book/uz/v2/Distributed-Git-Distributed-Workflows | Git - Distributed Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Иш бошланиши 1.1 Талқинларни бошқариш ҳақида 1.2 Git нинг қисқача тарихи 1.3 Git асоси 1.4 Командалар сатри 1.5 Git ни ўрнатиш 1.6 Git да биринчи созлашлар 1.7 Қандай ёрдам олиш мумкин? 1.8 Хулосалар 2. Git асослари 2.1 Git омборини яратиш 2.2 Ўзгаришларни омборга ёзиш 2.3 Фиксирлашлар тарихини кўриш 2.4 Ўзгаришларни бекор қилиш 2.5 Узоқ масофадаги омборлар билан ишлаш 2.6 Тамғалаш 2.7 Git да таҳаллуслар 2.8 Хулоса 3. Git да тармоқланиш 3.1 Тармоқланиш ҳақида икки оғиз сўз 3.2 Тармоқланиш ва бирлашиш асослари 3.3 Тармоқларни бошқариш 3.4 Иш жараёнларини тармоқлаш 3.5 Узоқ масофадаги тармоқлар 3.6 Қайта асосланиш 3.7 Хулосалар 4. Git серверда 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Sizning SSH ochiq (public) kalitingizni generatsiyalash 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Хулосалар 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Qism modullar (Submodule) 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distributed Git - Distributed Workflows Now that you have a remote Git repository set up as a point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. Distributed Workflows Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally on a central hub. In Git, however, every developer is potentially both a node and a hub – that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This opens a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model–the centralized workflow. One central hub, or repository, can accept code, and everyone synchronizes their work to it. A number of developers are nodes – consumers of that hub – and synchronize to that one place. Figure 54. Centralized workflow. This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. Integration-Manager Workflow Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow. ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an e-mail asking them to pull changes. The maintainer adds the contributor’s repo as a remote and merges locally. The maintainer pushes merged changes to the main repository. Figure 55. Integration-manager workflow. This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes – each party can work at their own pace. Dictator and Lieutenants Workflow This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants. All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator’s repository serves as the reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow. ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the dictator. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. The dictator pushes their master to the reference repository so the other developers can rebase on it. Figure 56. Benevolent dictator workflow. This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. Workflows Summary These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://git-scm.com/book/id/v2/Distributed-Git-Distributed-Workflows | Git - Distributed Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distributed Git - Distributed Workflows Now that you have a remote Git repository set up as a point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. Distributed Workflows Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally on a central hub. In Git, however, every developer is potentially both a node and a hub – that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This opens a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model–the centralized workflow. One central hub, or repository, can accept code, and everyone synchronizes their work to it. A number of developers are nodes – consumers of that hub – and synchronize to that one place. Figure 54. Centralized workflow. This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. Integration-Manager Workflow Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow. ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an e-mail asking them to pull changes. The maintainer adds the contributor’s repo as a remote and merges locally. The maintainer pushes merged changes to the main repository. Figure 55. Integration-manager workflow. This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes – each party can work at their own pace. Dictator and Lieutenants Workflow This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants. All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator’s repository serves as the reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow. ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the dictator. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. The dictator pushes their master to the reference repository so the other developers can rebase on it. Figure 56. Benevolent dictator workflow. This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. Workflows Summary These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:40 |
https://support.microsoft.com/ro-ro/microsoft-store-and-billing | Ajutor pentru facturare și Microsoft Store Salt la conținutul principal Microsoft Asistență Asistență Asistență Pornire Microsoft 365 Office Produse Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mai multe... Dispozitive Surface Accesorii PC Xbox Jocuri pentru PC HoloLens Surface Hub Garanții pentru hardware Cont și facturare Cont Microsoft Store și facturare Resurse Noutăți Forumurile comunității Administratori Microsoft 365 Portal pentru firme mici Dezvoltator Educație Raportați o înșelătorie de tip asistență tehnică Siguranța produselor Mai mult Cumpărați Microsoft 365 Toate Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Asistență Software-uri Software-uri Aplicații Windows IA OneDrive Outlook Se face trecerea de la Skype la Teams OneNote Microsoft Teams PC-uri şi dispozitive PC-uri şi dispozitive Accesorii Divertisment Divertisment Jocuri PC Afaceri Afaceri Securitate Microsoft Azure Dynamics 365 Microsoft 365 pentru firme Microsoft Industry Microsoft Power Platform Windows 365 Dezvoltator și IT Dezvoltator și IT Dezvoltator Microsoft Documentație Microsoft Learn Comunitatea tehnică Microsoft Microsoft Marketplace Visual Studio Marketplace Rewards Alte Alte Descărcări și securitate gratuite Educație Vizualizare hartă site Căutare Căutați ajutor Niciun rezultat Anulați Conectare Conectați-vă cu Microsoft Conectați-vă sau creați un cont Salut, Selectați un alt cont. Aveți mai multe conturi Alegeți contul cu care doriți să vă conectați. Ajutor pentru facturare și Microsoft Store Gestionați abonamentele Returnează rambursările & Opțiuni de plată Istoricul comenzilor Carduri cadou Instalați Microsoft 365 Microsoft Store în Windows Explorați serviciile Microsoft Store De la livrarea gratuită și retururile la protecția noastră de 60 de zile a prețurilor, suntem aici pentru a vă ajuta să realizați mai multe cu cele mai bune dispozitive, software, jocuri și resurse. Vedeți ce are de oferit Microsoft Store: Asistență pentru cumpărături și achiziții | Configurarea și instruirea produselor | Asistență pentru firme mici Asistență pentru cumpărături și achiziții Serviciile Microsoft Store nu sunt disponibile în toate regiunile. Pentru a vedea ce opțiuni sunt disponibile, selectați țara sau regiunea dvs. din lista verticală de mai jos și, dacă nu este listată, selectați Alte regiuni . Selectați regiunea Statele Unite Australia Canada (engleză) Canada (franceză) Regatul Unit Alte regiuni De ce să cumpărați de la Microsoft Store Cumpărături simple și convenabile Transport gratuit 2-3 zile Returnări gratuite de 60 de zile 60 de zile de protecție a prețurilor Opțiuni de plată flexibile Bani pentru dispozitivul dvs. utilizat Comercializarea și reciclarea Reduceri și oferte speciale Pentru elevi, studenți, părinți și cadre didactice Pentru personalul militar Protecție extinsă a dispozitivelor Plan de protecție Microsoft Complete Vă putem ajuta să găsiți ceea ce vă trebuie Ajutor și asistență pentru vânzări Answer Desk pentru persoane cu dizabilități Cumpărați cu un asociat ASL De ce să cumpărați de la Microsoft Store Cumpărături simple și convenabile Livrare gratuită Returnări gratuite de 60 de zile 60 de zile de protecție a prețurilor Bani pentru dispozitivul dvs. utilizat Comercializarea și reciclarea Reduceri și oferte speciale Pentru elevi, studenți, părinți și cadre didactice Vă putem ajuta să găsiți ceea ce vă trebuie Ajutor și asistență pentru vânzări Answer Desk pentru persoane cu dizabilități De ce să cumpărați de la Microsoft Store Cumpărături simple și convenabile Livrare gratuită Returnări gratuite de 60 de zile 60 de zile de protecție a prețurilor Bani pentru dispozitivul dvs. utilizat Comercializarea și reciclarea Reduceri și oferte speciale Pentru elevi, studenți, părinți și cadre didactice Protecție extinsă a dispozitivelor Plan de protecție Microsoft Complete Vă putem ajuta să găsiți ceea ce vă trebuie Dacă aveți întrebări înainte de a cumpăra, discutați pe chat cu un expert de produs sau rezervați o rezervare la cumpărături. Ajutor și asistență pentru vânzări De ce să cumpărați de la Microsoft Store Cumpărături simple și convenabile Livrare gratuită Returnări gratuite de 60 de zile 60 de zile de protecție a prețurilor Bani pentru dispozitivul dvs. utilizat Comercializarea și reciclarea Reduceri și oferte speciale Pentru elevi, studenți, părinți și cadre didactice Protecție extinsă a dispozitivelor Plan de protecție Microsoft Complete De ce să cumpărați de la Microsoft Store Cumpărături simple și convenabile Livrare gratuită Returnări gratuite de 60 de zile 60 de zile de protecție a prețurilor Bani pentru dispozitivul dvs. utilizat Comercializarea și reciclarea Reduceri și oferte speciale Pentru elevi, studenți, părinți și cadre didactice Vă putem ajuta să găsiți ceea ce vă trebuie Ajutor și asistență pentru vânzări Answer Desk pentru persoane cu dizabilități De ce să cumpărați de la Microsoft Store Vă putem ajuta să găsiți ceea ce vă trebuie Dacă aveți întrebări înainte de a cumpăra, discutați pe chat cu un expert de produs. Ajutor și asistență pentru vânzări Navigați la Microsoft Store The Microsoft Store Configurarea și instruirea produselor Nu toate serviciile Microsoft Store listate aici sunt disponibile în toate regiunile. Pentru a vedea opțiunile, selectați țara sau regiunea dvs. din lista verticală de mai jos: Selectați regiunea Statele Unite Australia Canada (engleză) Canada (franceză) Regatul Unit Alte regiuni Resurse de ajutor și învățare Consultați resursele noastre de asistență pentru produse pentru a vă ajuta să găsiți răspunsurile de care aveți nevoie. Dispozitive Surface | Aplicația Xbox Microsoft 365 | Windows Resurse de ajutor și învățare Resursele noastre de asistență pentru produse sunt aici pentru a vă ajuta să găsiți răspunsurile de care aveți nevoie. Dispozitive Surface | Aplicația Xbox Microsoft 365 | Windows Resurse de ajutor și învățare Consultați resursele noastre de asistență pentru produse pentru a vă ajuta să găsiți răspunsurile de care aveți nevoie. Dispozitive Surface | Aplicația Xbox Microsoft 365 | Windows Resurse de ajutor și învățare Consultați resursele noastre de asistență pentru produse pentru a vă ajuta să găsiți răspunsurile de care aveți nevoie. Dispozitive Surface | Aplicația Xbox Microsoft 365 | Windows Resurse de ajutor și învățare Consultați resursele noastre de asistență pentru produse pentru a vă ajuta să găsiți răspunsurile de care aveți nevoie. Dispozitive Surface | Aplicația Xbox Microsoft 365 | Windows Resurse de ajutor și învățare Consultați resursele noastre de asistență pentru produse pentru a vă ajuta să găsiți răspunsurile de care aveți nevoie. Dispozitive Surface | Aplicația Xbox Microsoft 365 | Windows Asistență pentru firme mici Pentru a vedea ce opțiuni de asistență pentru firme mici sunt disponibile în regiunea dvs., selectați țara sau regiunea dvs. din lista verticală de mai jos: Selectați regiunea Statele Unite Australia Canada (engleză) Canada (franceză) Regatul Unit Alte regiuni Resurse pentru firma dvs. mică Obțineți sfaturi, instruire gratuită, produse și instrumente pentru a vă ajuta afacerea să prospere. Ajutor și învățare pentru firme mici Centrul de resurse pentru firme mici Resurse pentru firma dvs. mică Obțineți sfaturi, instruire gratuită, produse și instrumente pentru a vă ajuta afacerea să prospere. Ajutor și învățare pentru firme mici Centrul de resurse pentru firme mici Resurse pentru firma dvs. mică Obțineți sfaturi, instruire gratuită, produse și instrumente pentru a vă ajuta afacerea să prospere. Ajutor și învățare pentru firme mici Centru de resurse pentru firme mici Resurse pentru firma dvs. mică De la evaluarea necesităților firmei dvs. la asistarea configurării și depanării, suntem aici pentru a vă ajuta. Obțineți sfaturi, instruire gratuită, produse și instrumente pentru a vă ajuta afacerea să prospere. Ajutor și învățare pentru firme mici Centru de resurse pentru firme mici Resurse pentru firma dvs. mică Obțineți sfaturi, instruire gratuită, produse și instrumente pentru a vă ajuta afacerea să prospere. Ajutor și învățare pentru firme mici Centrul de resurse pentru firme mici Resurse pentru firma dvs. mică Obțineți sfaturi, instruire gratuită, produse și instrumente pentru a vă ajuta afacerea să prospere. Ajutor și învățare pentru firme mici Noutăți Copilot pentru organizații Copilot pentru uz personal Microsoft 365 Aplicații Windows 11 Microsoft Store Profil de cont Centrul de descărcare Retururi Urmărire comandă Reciclare Garanții comerciale Educație Microsoft Education Dispozitive pentru educație Microsoft Teams pentru educație Microsoft 365 Education Office Education Instruirea și dezvoltarea educatorilor Promoții pentru studenți și părinți Azure pentru studenți Afaceri Securitate Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Dezvoltator și IT Dezvoltator Microsoft Documentație Microsoft Learn Comunitatea tehnică Microsoft Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Companie Cariere Confidențialitatea în cadrul companiei Microsoft Angajamentul Microsoft privind prevenirea corupției și mitei Investitori Sustenabilitate Română (România) Pictograma Renunțare la opțiunile de confidențialitate Opțiunile dumneavoastră de confidențialitate Pictograma Renunțare la opțiunile de confidențialitate Opțiunile dumneavoastră de confidențialitate Confidențialitatea pentru sănătatea consumatorilor Contactați Microsoft Confidențialitate Gestionare cookie-uri Condiţii de utilizare Mărci comerciale Despre reclamele noastre EU Compliance DoCs Raportare de reglementare © Microsoft 2026 | 2026-01-13T09:29:40 |
https://www.microsoft.com/ko-kr/power-platform/dataverse | Microsoft Dataverse | Microsoft Power Platform This is the Trace Id: f11254f158978cb51edee5ff98729834 주 콘텐츠로 건너뛰기 Microsoft Power Platform Power Platform Power Platform 홈 Power Platform 정보 무료로 체험하기 AI(인공 지능) 보안 및 거버넌스 Dataverse 커넥터 서식 파일 제품 Power BI Power BI Power BI Desktop Pro Premium Embedded Report Server Power Apps Power Automate Power Pages Copilot Studio 가격 책정 리소스 제품별 리소스 Power Platform 알아보기 설명서 Power Platform 항목 무료로 시작 자세히 Microsoft 전체 Global Microsoft 365 Teams Copilot Windows Surface Xbox 세일 지원 소프트웨어 소프트웨어 Windows 앱 AI OneDrive Outlook Skype에서 Teams로 이동 중 OneNote Microsoft Teams PC 및 장치 PC 및 장치 Xbox 쇼핑 주변 기기 엔터테인먼트 엔터테인먼트 Xbox Game Pass Ultimate Xbox 및 게임 PC 게임 기업 고객용 기업 고객용 Microsoft Security Azure Dynamics 365 비즈니스용 Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 개발자 및 IT 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Visual Studio Marketplace Rewards 기타 기타 무료 다운로드 및 보안 교육 볼륨 라이선싱 사이트맵 보기 Dataverse</h1> "> Dataverse Copilot용 엔터프라이즈 데이터 플랫폼인 Microsoft Dataverse를 사용하여 근거 있는 엔터프라이즈 데이터를 추가하고 Copilot을 실행 가능하도록 만드세요. 지금 바로 Microsoft Copilot Studio 평가판을 시작해 보세요. Copilot Studio 사용해 보기 개요 개요 리소스 고객 스토리 개요 Do more with your data</h2> "> 데이터로 더 많은 작업 수행 사용자 역량 강화 엔터프라이즈 애플리케이션 빌드 엔터프라이즈급 보안 이전 다음 Copilot 환경 보강 매일 사용하는 데이터를 통합, 검색 및 작동합니다. 누구나 데이터 솔루션을 빌드할 수 있도록 설정 비즈니스 프로세스에 대한 심층적인 이해를 얻고 생성형 AI를 사용하여 솔루션 개발을 간소화하세요. 데이터 원본 통합 생성형 AI 워크플로 및 Copilot 애플리케이션을 위해 서로 다른 데이터 원본의 데이터 및 메타데이터를 쉽게 활용합니다. AI를 사용하여 데이터 통합 구조화되거나 구조화되지 않은 데이터에 대해 자연어 Q&A를 사용하여 데이터 작업 영역에서 관련성있고 정확한 답변을 생성합니다. AI 기반 프롬프트 빌드 Azure Open AI LLM(대규모 언어 모델)을 사용하여 기반 엔터프라이즈 데이터로 동적 프롬프트를 만들고 외부 데이터 원본에 연결합니다. 사례 번호별로 사례 해결을 요약하는 옵션이 있는 컴퓨터 화면을 보여 주는 그림 사용자 지정 작업 빌드 비즈니스 프로세스에 비즈니스 논리 및 서비스를 패키지하는 사용자 지정 커넥터, 플러그 인 및 사용자 지정 API를 빌드합니다. 완전 관리형, 완전 통합형 Power Platform 에코시스템 전반에서 엔터프라이즈 애플리케이션 수명 주기 관리에 대한 기본 제공 지원을 받으세요. 엔드투엔드 보안 고급 보안 기능 및 Microsoft Sentinel과의 상호 운용을 통해 신뢰를 구축하세요. 다양한 옵션 및 인시던트 세부 정보가 있는 인시던트 관리 인터페이스를 보여 주는 Microsoft Azure Sentinel 대시보드의 스크린샷입니다. 규정 준수 기능 Microsoft Purview를 사용하여 모든 AI 데이터 액세스에 대한 감사 로그를 가져옵니다. 데이터 카탈로그, 검색, 관리 옵션 및 인사이트를 갖춘 Microsoft Purview 인터페이스 자동 관리 데이터 보안 고급 보안 기능을 사용하여 데이터를 평가하고, 조치를 취하고, 사전에 보호하세요. 탭으로 돌아가기 리소스 Learn how to increase your scale and agility</h2> "> 규모와 민첩성을 높이는 방법 알아보기 이전 슬라이드 다음 슬라이드 Learn how to achieve ROI and cut costs</h3> "> 연구 ROI를 달성하고 비용을 절감하는 방법 알아보기 Forrester Consulting에서 실시한 위탁 연구인 The Total Economic Impact™ of Microsoft Power Platform Premium Capabilities에 대해 읽어보세요. 연구 보기 Understand the impact of low code</h3> "> 백서 로우코드의 영향 이해 조직에서 로우코드 앱 개발의 이점을 누리면서 리스크를 완화하는 방법을 알아보세요. 백서 받기 Drive efficiency with low-code development</h3> "> eBook 로우코드 개발을 통해 효율성 향상 IT 리더들이 비용 절감과 민첩성 향상을 위해 로우코드 앱 개발 플랫폼을 사용하는 방법에 대해 알아보세요. 전자책 받기 리소스 섹션으로 돌아가기 고객 사례 See what customers are saying</h2> "> 고객 평가 확인하기 이전 슬라이드 다음 슬라이드 "Dataverse를 사용하면 특정 역할까지 데이터에 대한 액세스를 제어할 수 있습니다." Sebastian Witt, Senior Program Manager Industry 4.0 & Digitalization, Active Safety Division, ZF 42,000+ Dataverse를 기반으로 하는 솔루션 사례 읽기 "Power Platform과 함께 일한 이후로 비즈니스 팀과 IT 팀 간의 협업이 이렇게 활발했던 적은 없었습니다.” Colt Coan, Senior Manager of Rapid Development, Epiq 2,000 매월 저장된 작업 시간 USD$500K 연간 관련 비용 절감 사례 읽기 "Microsoft 에코시스템을 수용하면서 고객과 참여 팀을 지원하는 도구와 기능인 Power Platform도 함께 수용했습니다.” Karen Fraser, Program Operations Lead, PwC 85% 비용 절감 달성 30% 시간 절약 달성 사례 읽기 "커넥터와 함께 Copilot은 판매자의 워크플로에 큰 도움이 됩니다." Ashley Haynes-Gaspar, Lumen Technologies 최고 수익 책임자 사례 읽기 고객 사례 섹션으로 돌아가기 Take the next step with Microsoft Dataverse</h2> "> Microsoft Dataverse를 사용하여 다음 단계 수행 Microsoft 교육 과정 수강 테이블을 만들고 Dataverse 데이터베이스로 데이터를 가져오는 방법을 알아봅니다. 지금 시작 파트너와 상의 Power Apps 파트너의 전문적인 도움을 받아 Microsoft Power Platform에서 Dataverse를 사용하는 방법에 대해 자세히 알아보세요. 파트너 찾기 Power Platform 평가판 시작 로우코드 개발을 통해 혁신을 가속화하는 방법을 직접 알아보세요. 각 제품을 무료로 사용해 보세요 — 신용카드가 필요하지 않습니다. 평가판 시작 사례 번호별로 사례 해결을 요약하는 옵션이 있는 컴퓨터 화면을 보여 주는 그림 다양한 옵션 및 인시던트 세부 정보가 있는 인시던트 관리 인터페이스를 보여 주는 Microsoft Azure Sentinel 대시보드의 스크린샷입니다. 데이터 카탈로그, 검색, 관리 옵션 및 인사이트를 갖춘 Microsoft Purview 인터페이스 Power Platform 팔로우 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 .ow-link-wrapper #chatEngagement{ height: 35px; bottom: 0!important; } .ow-pro-c-body { background-color: #d5d5d5; padding-block-end: 100%; } .ow-pro-c-container-modal { position: fixed; right: 60px; bottom: 50px; z-index: 10040; height: 355px; width: 355px; /* background: #243A5E; */ background-image: linear-gradient(#1278D4 170px, 170px, white 355px 170px); box-shadow: 0px 5px 20px rgba(0, 0, 0, 0.15); } .ow-pro-c-button-container { display: flex; justify-content: flex-end; } .ow-pro-c-close-button { height: 20px; width: 20px; display: flex; margin-block-start: 16px; margin-inline-end: 20px; background: none; border: none; color: #FFFFFF; } .ow-pro-c-h-text, .ow-pro-c-h-text-var-2 { color: #FFFFFF; font-size: 29px; margin-block-start: 0px; text-align: center; } .ow-pro-c-h-text { margin-block-start: 0px; } .ow-pro-c-h-text-var-2 { margin-block-start: 28px; } .ow-pro-c-p-text { color:#FFFFFF; font-size: 16px; margin-block-start: 16px; text-align: center; } .ow-pro-c-image-container { text-align: center; flex-direction: column; } .ow-pro-c-image { height: 75px; width: 75px; margin-block-start: 22px; border-radius: 50%; } button.ow-pro-c-chat-button { margin-block-start: 26px; } .ow-pro-c-button-glyph-container { display: flex; background: none; border: none; margin-block-start: 20px; } .ow-pro-c-no-button { font-size: 16px; font-family: 'Segoe UI'; } .ow-pro-c-no-button.c-glyph { margin-inline-start: 5px; margin-block-start: 2px; } .ow-pro-c-container-modal-var-2 { position: fixed; right: 60px; top: 50%; transform: translateY(-50%); z-index: 10040; height: 355px; width: 355px; background-color: #243A5E; box-shadow: 0px 5px 20px rgba(0, 0, 0, 0.15); } .ow-pro-c-d-flex { display: flex; align-items: center; } .ow-link-wrapper button.ow-pro-c-chat-button-var-2 { background: #ffffff; margin-block-start: 30px; } .ow-link-wrapper button.ow-pro-c-chat-button-var-2:focus:not(.x-hidden-focus) { background: #e5e5e5; } button.c-button.f-primary{ color: #fff!important; background: #0067b8!important; } button.c-button.f-primary:hover{ color: #fff; background: #4e596b; } .ow-pro-c-image-container .c-glyph.glyph-cancel:before{ font-size: 15px; position: relative; top: 1px; } .ow-pro-c-image-container ul {list-style: none; padding-left: 0;} </style> <div class="ow-pro-c-container-modal proactive-chat-hidden" id="proactive-chat-dialog"> <div class="ow-pro-c-button-container"> <button class="ow-pro-c-close-button c-glyph glyph-cancel" aria-label="{{chat-disengagement.aria-label}}" data-bi-cn="Chat_invite_decline" data-bi-bhvr="15" onclick="(window.chatInst.getProactiveChat()).toggle(false)" ></button> </div> <div class="ow-headinghelper-2 ow-pro-c-h-text">{{module.heading}}</div> <div class="c-button f-primary ow-pro-c-p-text"> {{chat-engagement.prompt}} </div> <div class="ow-pro-c-image-container ow-pro-c-d-flex"> <img src="{{module.img-src}}" alt="{{module.img-alt-txt}}" class="ow-pro-c-image" /> <ul data-cta-count="1"> <li class="ow-link-wrapper"> <button id="chatEngagement" aria-label="{{chat-engagement-aria-label}}" class="c-button f-primary ow-pro-c-chat-button" data-bi-cn="Chat_invite_accept" data-bi-bhvr="180" > <span> {{chat-engagement.btn-txt}} </span> </button> </li> </ul> <button id="chatDisengagement" class="ow-pro-c-button-glyph-container ow-pro-c-d-flex" aria-label="{{chat-disengagement.aria-label}}" data-bi-cn="Chat_invite_decline" data-bi-bhvr="15" > <div class="ow-pro-c-no-button">{{chat-disengagement.btn-txt}}</div> <div class="ow-pro-c-no-button c-glyph glyph-cancel"></div> </button> </div> </div>'/> 닫기 구입 전 상담 창구에 문의하기 | 2026-01-13T09:29:40 |
https://www.nec-labs.com/research/data-science-system-security/ | Data Science & System Security | Research | NEC Labs America Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Research Overview Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications News Events Careers Overview Search Careers Intern Program About Overview Christopher White | President Office of the President NEC Corporation NEC Corporation of America NEC Research & Development Follow us on Social Media! Subscribe to our Newsletter Contact Click to open the search input field Click to open the search input field Search Menu Menu Data Science & System Security We aim to build novel big-data solutions and service platforms to simplify complex systems management. We develop new information technology that supports innovative applications, from big data analytics to the Internet of Things. Link to: DS Projects PROJECTS Link to: DS People PEOPLE Link to: DS Publications PUBLICATIONS Link to: DS Patents PATENTS Our experimental and theoretical research includes many data science and systems research domains. These include but are not limited to time series mining, deep learning, NLP and large language models, graph mining, signal processing, and cloud computing. Our research aims to fully understand the dynamics of big data from complex systems, retrieve patterns to profile them and build innovative solutions to help the end user manage those systems. We have built several analytic engines and system solutions to process and analyze big data and support various detection, prediction, and optimization applications. Our research has led to award-winning NEC products and publications in top conferences. Data science research is poised to transform substantially. First and foremost, there will be a continued emphasis on the ethical and responsible use of data. As data-driven decision-making becomes more pervasive across industries, organizations must prioritize data privacy, security, and transparency. Secondly, the field of data science will witness advancements in automation and AI-driven analytics. Our team will remain vigilant in ensuring responsible data usage while harnessing the potential of these cutting-edge data science tools to fuel innovation for our clients, partners and collaborators. Join Us Are you interested in joining us? We seek the next generation of thought leaders in data science and system security for researcher positions. Outstanding applicants pursuing a career in all areas of data science are encouraged to visit our careers page to learn more and to apply for our available positions . Learn More Want to learn more about our data science and system security department? Meet our team of experts , check out our blog posts , or read our latest publications . Summer 2026 Internship Applications are now available! Exciting internship opportunities for Summer 2026 are now available on our internship page. We are looking for students pursuing advanced degrees in Computer Science and Electrical Engineering. Internships are typically 3 months long during the summer. The benefits of working for us include the opportunity to quickly become part of a project team applying cutting-edge technology to industry-leading concepts. To apply for a Summer Internship, visit our Internship page. Featured Data Science & System Security Research Projects Link to: Time Series Language Model for Explainable AI Time Series Language Model for Explainable AI We are developing an advanced multi-modal forecasting system that utilizes both time series data and textual data, such as news articles, to predict future trends and events. READ MORE Link to: Complex System Modeling and Optimization Complex System Modeling and Optimization With ubiquitous sensing and networking capability, traditional complex physical systems have been undergoing revolutionary changes in their ICT capabilities. READ MORE Link to: AI for Space AI for Space Our AI-powered monitoring solution will perform intricate checks to ensure the spacecraft and satellites operate correctly during the production and operation phases. READ MORE Contact Us Princeton Office 4 Independence Way, Suite 200 Princeton, NJ 08540 +1 609-520-1555 San Jose Office 2033 Gateway Place, Suite 200 San Jose, CA 95110 +1 408-863-6007 About Us NEC Laboratories America, Inc. (NEC Labs) is the US-based center for NEC Corporation’s global network of corporate research laboratories. Our diverse research groups collaborate with industry, academia and governments to provide disruptive solutions to complex problems. A leader in the integration of IT and network technologies with more than 100 years of expertise, NEC provides a combination of products and solutions that cross-utilize the company’s experience and global resources to meet the complex and ever-changing needs of its customers. Our Pages Home Research Departments Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Patents Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing News Events About Us Christopher White | President Office of the President NEC Corporation Subscribe to our Newsletter Careers Intern Program Contact Us Recent Publications Quantitative Bounds for Length Generalization in Transformers Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing SlideCraft: Context-aware Slides Generation Agent TalentScout: Multimodal AI-Driven Expert Finding in Organizations AutoScape: Geometry-Consistent Long-Horizon Scene Generation DWIM: Towards Tool-aware Visual Reasoning via Discrepancy-aware Workflow Generation & Instruct-Masking Tuning Mapillary Vistas Validation for Fine-Grained Traffic Signs: A Benchmark Revealing Vision-Language Model Limitations LANGTRAJ: Diffusion Model and Dataset for Language-Conditioned Trajectory Simulation DiscussLLM: Teaching Large Language Models When to Speak Bifröst: Peer-to-peer Load-balancing for Function Execution in Agentic AI Systems Harnessing Vision Models for Time Series Analysis: A Survey Multi-modal Time Series Analysis: A Tutorial and Survey ICeTEA: Mixture of Detectors for Metric-Log Anomaly Detection Roadside Multi-LiDAR Data Fusion for Enhanced Traffic Safety Identifying Combinatorial Regulatory Genes for Cell Fate Decision via Reparameterizable Subset Explanations On Synthesizing Data for Context Attribution in Question Answering Feasibility study on scour monitoring for subsea cables of offshore wind turbines using distributed fiber optic sensors Group Relative Augmentation for Data Efficient Action Detection Uncertainty Propagation on LLM Agent Exploring Multi-Modal Data with Tool-Augmented LLM Agents for Precise Causal Discovery EcoDoc: A Cost-Efficient Multimodal Document Processing System for Enterprises Using LLMs Integration of Fiber Optic Sensing and Sparse Grid Sensors for Accurate Fault Localization in Distribution Systems XPF: Agentic AI System for Business Workflow Automation Quantitative Bounds for Length Generalization in Transformers Re-ranking the Context for Multimodal Retrieval Augmented Generation Beyond the Permutation Symmetry of Transformers: The Role of Rotation for Model Fusion PPDiff: Diffusing in Hybrid Sequence-Structure Space for Protein-Protein Complex Design Pathologist-Read vs AI-Driven Assessment of Tumor-Infiltrating Lymphocytes in Melanoma AutoScape: Geometry-Consistent Long-Horizon Scene Generation Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Kunal Rao presents SlideCraft: Context-Aware Slides Generation Agent at PICom 2025 on October 21st NECLA at ECOC 2025: Advancing Optical Communication and Distributed Sensing News NEC Laboratories America 2025: A Year of Disruptive Innovation Apply for a Summer 2026 Internship NEC Laboratories America: Celebrating 23 Years of Research Innovation! Summer Highlights at NEC Labs America: Teamwork, Innovation, and Fun Graph Neural Networks, Explained: Our Role in the Future of AI Shaping the Future with Responsible AI, Collaboration, and Disruption Top 10 Most Legendary College Pranks of All-Time for April Fools’ Day Introducing the Trustworthy Generative AI Project: Pioneering the Future of Compositional Generation and Reasoning Introducing Our New Project: Time Series Language Model for Explainable AI The Evolution of Disciplines: From Experimental Roots to Theoretical Frameworks Agentic LLMs for AI Orchestration Project: Revolutionizing Complex Workflows Multi-Agent Simulator for Carbon Neutrality: The Technology the World Has Been Waiting For NEC Laboratories Advances Material Design with AI-based MateriAI Platform Unearthing Nature’s Orchestra – How Fiber Optic Cables Can Hear Cicada Secrets © Copyright 2025 NEC Labs America | All Rights Reserved | Privacy Policy | Global Privacy Policy Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Home Research Departments Publications Patents News Events About Us Careers Contact Us Scroll to top Scroll to top Scroll to top | 2026-01-13T09:29:40 |
https://www.atlassian.com/br/software/jira/service-management/features/asset-and-configuration-management | Gerenciamento de configuração e recursos com o Jira | Atlassian Close Quer visualizar esta página no seu idioma ? Todos os idiomas Escolha seu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtenha grátis Aplicativos Service Collection Jira Service Management Gestão de atendimento ao cliente Recursos Service Collection Back Preços E mais + Menos - Obtenha grátis Back Obtenha grátis Gerenciamento de configurações e ativos O Recursos oferece visibilidade das dependências para que você possa gerenciar recursos e itens de configuração (CIs), solucionar incidentes com rapidez e reduzir o risco das alterações. Experimente agora Conheça o Recursos Assista ao vídeo O lugar para dados importantes Diferente dos bancos de dados antigos, o Recursos oferece uma estrutura de dados flexível e aberta para que as equipes gerenciem e conectem recursos essenciais a solicitações, incidentes, alterações e muito mais. Acompanhe o que importa De hardware, software e itens de configuração a pessoas, pianos e peixes (é sério), reúna todos os recursos da sua empresa em um banco de dados flexível. Os templates pré-criados ajudam você a começar mais rápido. Conecte os recursos ao trabalho Vincule objetos em Recursos a tickets de suporte, itens de incidente, solicitações de alteração e muito mais. Melhore a visibilidade e acelere o trabalho em todos os tipos de casos de uso em TI, RH, instalações e muito mais. Tome decisões melhores Tenha total visibilidade e controle sobre os recursos para reduzir riscos e melhorar as operações, agora com relatórios e painéis novos e flexíveis para obter insights mais profundos e tomar decisões mais inteligentes e rápidas. Traga dados completos, atuais e corretos para o Recursos O Gerenciador de dados do Recursos simplifica a integração, a reconciliação e a análise de dados de várias fontes, fornecendo dados confiáveis para decisões inteligentes. Saiba mais Funções de gestão de configuração e recursos Automação Diga adeus ao rastreamento de proprietários ou à atualização de planilhas. Automatize a inserção de dados com base em tickets do Jira para manter atualizadas as informações necessárias sobre seus recursos. Consultas Execute consultas em objetos do Recursos para fazer auditorias, gerenciar custos e identificar as causas dos itens. Templates Comece logo com templates de esquema predefinidos para trazer estrutura ao banco de dados para casos de uso comuns em TI, instalações, RH e muito mais. Discovery Detecte recursos habilitados para IP, extraia informações sobre os principais atributos e dependências e acompanhe todas as mudanças para se manter atualizado. Integrações Aproveite mais de 30 adaptadores, incluindo arquivos simples e bancos de dados SQL, para trazer de forma simples dados importantes para o Recursos. Relatórios Obtenha insights acionáveis de seus dados do Recursos para monitorar a integridade dos recursos, detectar lacunas de conformidade e riscos de segurança e acessar dados financeiros importantes. “O Recursos é muito importante para manter a previsibilidade e o planejamento das licenças e dos custos de software.” Damir Prusac Vice-presidente de engenharia, Infobip Leia mais Perguntas mais frequentes Quais são as diferenças entre o Recursos no Jira Service Management Cloud, no Data Center e no App do Recursos? Para entender melhor as funções de cada plano de Recursos, veja esta tabela de comparação . Recursos podem ser usados com espaços do Jira? Sim. Objetos no Recursos podem ser vinculados a tickets do Jira, desde que haja uma licença ativa da Service Collection Standard ou superior na mesma instância. Por que trocar minha ferramenta de CMDB/gestão de recursos? Mover seu CMDB para o Recursos, um aplicativo na Service Collection: Simplifica seu trabalho, pois terá todas as informações de ITSM (solicitações, incidentes, alterações e problemas) e CMDB em uma única ferramenta Dar mais contexto entre recursos e itens de configuração e entre incidentes e alterações para que as equipes de desenvolvimento e operações consigam identificar a origem do problema com mais rapidez e gerenciar os riscos para viabilizar mais implementações sem problemas Reduz custos, já que os outros fornecedores de CMDB são caros Aumentar a flexibilidade para armazenar qualquer tipo de inventário, recurso ou registro, sem restrições ou limites para apenas casos de uso de TI. A Atlassian oferece uma ferramenta de descoberta de recursos? Sim, a gente oferece a funcionalidade de descoberta básica para detectar recursos e itens de configuração conectados à rede local e extrair informações detalhadas sobre cada recurso. A gente também oferece integrações com as principais soluções de descoberta, como Lansweeper e Flexera, para encontrar e importar dispositivos para o aplicativo app do Recursos. Como os dados são importados para Recursos? Com o Recursos, os usuários podem aproveitar o Gerenciador de dados e sua função nativa de importação de esquemas. Saiba mais aqui: Saiba mais sobre o Gerenciador de dados do Recursos Saiba mais sobre adaptadores Configure o Gerenciador de dados do Recursos Mova os dados para o Gerenciador de dados a fim de criar dados brutos Remova valores desnecessários para criar dados transformados Elimine registros desnecessários para criar dados limpos Reconcilie fontes de dados para criar objetos do Gerenciador de dados Importe para um esquema do Recursos a fim de criar objetos de esquema O que pode ser armazenado em Recursos? Qualquer coisa. Sério. Recursos de TI tradicionais, como hardware? ✅ Itens de configuração? ✅ Registros de pessoas? ✅ Peixe? Se é importante para você, é importante para a gente ✅ Recursos é uma ferramenta flexível que se adapta às suas necessidades. Basta criar o tipo de objeto e o esquema certos para você seguir em frente. Características e recursos da gestão de configuração Demonstração Como gerenciar o inventário em Recursos Assista à demonstração Artigo técnico Manual de gestão de configuração e recursos para ITSM Saiba mais ebook A evolução dos recursos: uma abordagem mais inteligente para agregar valor comercial Saiba mais Decisões inteligentes começam com dados de recursos de qualidade Experimente grátis Empresa Carreiras Eventos Blogs Relações com investidores Fundação Atlassian Kit de imprensa Fale conosco produtos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos os produtos Recursos Suporte técnico Compras e licenciamento Comunidade da Atlassian Base de conhecimento Marketplace Minha conta Criar chamado de suporte Saiba mais Parceiros Treinamento e certificação Documentação Recursos de desenvolvedores Serviços corporativos Ver todos os recursos Copyright © 2025 Atlassian Política de privacidade Termos Aviso legal Escolha o Idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:40 |
https://www.atlassian.com/es/software/jira/guides/projects/overview | Proyectos de Jira: elementos clave y aspectos esenciales | Atlassian Close ¿Quieres ver esta página en tu idioma ? Todos los idiomas Elige tu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtener gratis Funciones Todas las funciones Rovo en Jira Back Soluciones Equipos Casos prácticos Tamaño de la empresa Equipos Marketing Ingeniería Diseño Operaciones TI Casos prácticos Inicio Planificación Gestión de campañas Gestión ágil de proyectos Gestión de programas Tamaño de la empresa Enterprise Back Guía del producto Plantillas Plantillas Todas las plantillas Desarrollo de software Marketing Diseño Ventas Operaciones Gestión de asistencia RR. HH. Legal Operaciones de TI Finanzas Plantillas de Jira Service Management Back Precios Más + Menos - Obtener gratis Back Obtener gratis Inicio Introducción a Jira Jira para equipos 7 pasos para ponerse en marcha con Jira Proyectos Presentación Tutoriales Recursos Paneles Presentación Tutoriales Recursos Actividades/incidencias Presentación Tutoriales Recursos Flujos de trabajo Presentación Tutoriales Recursos Integraciones Presentación Tutoriales Recursos Informes y cuadros de mandos Presentación Tutoriales Recursos Información Presentación Tutoriales Recursos Permisos Presentación Tutoriales Recursos JQL Presentación Tutoriales Chuleta Recursos Navegación Overview Tutorials Resources Automatización Presentación Tutoriales Recursos "Timeline" (Cronograma) Presentación Tutoriales Recursos Advanced Roadmaps Presentación Tutoriales Recursos Jira para móviles Presentación Tutoriales Recursos Más información sobre Jira Ediciones de Jira Opciones de alojamiento Descripción general de los espacios de Jira ¿Qué es un espacio de Jira? Normalmente, un espacio se puede definir como un conjunto de tareas que deben completarse para alcanzar un resultado determinado. En Jira, un espacio se puede considerar como un contenedor que sirve para organizar y supervisar esas tareas o actividades en todo el equipo. Un espacio de Jira es altamente configurable y se puede personalizar fácilmente para adaptarse a la estructura organizativa, al flujo de trabajo o al nivel de madurez en metodología ágil, lo que lo convierte en la única herramienta que se adapta a la forma de trabajar única de cualquier equipo. Tu equipo puede usar un espacio de Jira para supervisar y resolver errores, lanzar una nueva función y mucho más. Puedes encontrar tus espacios en la barra de navegación superior, en el menú desplegable "Espacios". Ver la demostración completa ¿Cuáles son los elementos clave de un espacio de Jira? Como en cualquier proyecto, hay tareas que se deben realizar, personas que hacen las cosas realidad y procesos que ayudan a que el trabajo avance. Actividades: los espacios de Jira son metas ambiciosas que se dividen en pequeñas tareas denominadas "actividades" . Personas: Jira facilita a los equipos la planificación y la supervisión del trabajo para que puedan conseguir más cosas, juntos. Invita a los usuarios a tu espacio de Jira para empezar a colaborar. Flujos de trabajo: los espacios de Jira se estructuran de modo que siguen un proceso o flujo de trabajo, para que una actividad vaya de la creación a la finalización. Estos flujos de trabajo se pueden crear para que se adapten a la forma de trabajar única de tu equipo. ¿Qué son las plantillas de espacio de Jira? Jira ofrece varias plantillas de espacio para ayudar a los equipos a ponerse en marcha rápidamente y crear proyectos adaptados a un equipo (por ejemplo, de recursos humanos o software) o un caso práctico. Estas plantillas incluyen tipos de actividades preconfigurados, flujos de trabajo y otras funciones relevantes. Dos de nuestras plantillas más populares son las plantillas de kanban y scrum. Visita la biblioteca de plantillas de Jira . La plantilla de kanban da visibilidad a tu trabajo con un tablero potente y sencillo. Ha sido diseñada para equipos que limitan el trabajo en curso y se centran en un flujo de trabajo continuo. La plantilla de kanban de Jira ayuda a los equipos a diseñar, gestionar y optimizar fácilmente su flujo de trabajo, al tiempo que proporciona transparencia a medida que el trabajo se va realizando. La plantilla de scrum permite a los equipos dividir trabajos grandes en partes más manejables. Ha sido diseñada para equipos que realizan su trabajo con un ritmo periódico o que trabajan en períodos de tiempo breves y delimitados llamados "sprints". La plantilla de scrum también permite a los equipos organizar y clasificar el trabajo del backlog y del tablero, todo ello sin perder de vista el panorama general gracias a la hoja de ruta. Más información sobre kanban en comparación con scrum ¿Cuáles son los tipos de espacios de Jira? Los espacios de Jira pueden ser "gestionados por el equipo" o "gestionados por la empresa". La diferencia fundamental entre los dos tipos es cómo se gestionan: si se hace a nivel de equipo o a nivel de empresa/administrador de Jira. Espacios gestionados por el equipo Descripción general Este tipo de espacio es para equipos que buscan una configuración simplificada y un mayor control sobre sus propios procesos y prácticas de trabajo en un espacio independiente. Los espacios gestionados por el equipo los gestionan los administradores del proyecto, lo que significa que los cambios se pueden implementar sin la intervención de un administrador de Jira. Configuración simplificada Los espacios gestionados por el equipo vienen listos para usar con una configuración simplificada. Cualquier miembro de tu equipo puede configurarlos y mantenerlos. Los espacios gestionados por el equipo se configuran de forma independiente y los cambios de configuración de un espacio no afectan a otros espacios. Funciones básicas Una experiencia moderna de Jira para los equipos que no necesitan funciones avanzadas. Cronograma En tu tablero solo se muestran las actividades de tus espacios Sprint activo único Creación de informes esenciales con metodología ágil Espacios gestionados por la empresa Descripción general Este tipo de espacio es para equipos que quieren trabajar en varios espacios y con varios equipos de una forma más estandarizada. Los espacios gestionados por la empresa los gestionan los administradores de Jira, quienes fomentan y promueven las prácticas recomendadas y los procesos de la organización mediante una configuración común. Configuración de los expertos Los espacios gestionados por la empresa proporcionan a los administradores de Jira un control total sobre la configuración, la personalización y la flexibilidad. Estos espacios los configuran y mantienen los administradores de Jira. La configuración se comparte entre los espacios. Funciones avanzadas El rendimiento y las funciones por las que todo el mundo conoce Jira. Planificación avanzada (solo Premium) Capacidad de incorporar actividades de otros espacios a tu tablero Capacidad de ejecutar sprints paralelos Creación de informes exhaustivos con metodología ágil Más información sobre los tipos de espacios de Jira Compañía Resumen Eventos Blogs Relaciones con los inversores Atlassian Foundation Kit de prensa Ponte en contacto con nosotros. Productos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos los productos Recursos Servicio técnico Compra y licencia Comunidad de Atlassian Base de conocimientos Marketplace Mi cuenta Crear tique de asistencia Tutorial Socios Formación y certificación Documentación Recursos para desarrolladores Servicios empresariales Ver todos los recursos Copyright © 2025 Atlassian Política de privacidad Términos Impressum Selecciona un idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://lwn.net/Articles/897263/ | Zoned storage [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register Zoned storage Please consider subscribing to LWN Subscriptions are the lifeblood of LWN.net. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Please visit this page to join up and keep LWN on the net. By Jake Edge June 14, 2022 LSFMM Zoned storage is a form of storage that offers higher capacities by making tradeoffs in the kinds of writes that are allowed to the device. It was the topic of a storage and filesystem session led by Luis Chamberlain at the 2022 Linux Storage, Filesystem, Memory-management and BPF Summit (LSFMM). Over the years, zoned storage has been a frequent topic at LSFMM, going back to LSFMM 2013 , where support for shingled magnetic recording (SMR) devices, which were the starting point for zoned storage, was discussed. Chamberlain began with the news that a zoned storage microconference had been accepted for this year's Linux Plumbers Conference (LPC). He encouraged attendees to submit topics and hoped it was an opportunity to introduce more user-space developers to zoned-storage concepts. LPC will be held September 12-14 in Dublin, Ireland. In a "really fast intro" to zoned storage, he quoted from the zoned-storage home page linked above: it is " a class of storage devices that enables host and storage devices to cooperate to achieve higher storage capacities, increased throughput, and lower latencies ". It comes in different form factors, including SMR and "the latest and trendiest one", which is based on SSDs using NVMe zoned namespaces (ZNS). The storage device is divided into zones; "sequential zones" are those where all writes in a zone must be sequential and the only way to overwrite the zone is to reset its write pointer to the beginning. Both SMR and ZNS devices can optionally also have "conventional zones" (or namespaces) that support random writes. There can be drives that only have sequential zones, however, which is something that filesystem developers need to keep in mind, he said. There are some "ecosystem considerations" to also keep in mind. For one, replacing a zoned-storage device can only be done with another device that has the same zone sizes. Also, ZNS requires manually switching the kernel I/O scheduler to mq-deadline. That is only true for some filesystems, though, an audience member said. Damien Le Moal said that the underlying issue is that the order of writes needs to be guaranteed and the scheduler was the easiest place to ensure that. Ted Ts'o said there is a philosophical question on whether the kernel should be tracking the write pointers for the zones or whether user space should be doing that. At Google, there is an out-of-tree patch set that hacks the CFQ scheduler so that it will not merge requests and gives user space the responsibility to track write pointer, but he knows that this out-of-tree approach is not sustainable long term. It was generally agreed that there is much to discuss around these topics at LPC. Moving on, Chamberlain noted that the patches for supporting zone sizes that are not powers of two (npo2) had been posted and that more revisions should be coming soon (v6 was posted on May 25). He also said that btrfs check currently does not work for image dumps of any zoned storage, probably due to a lack of zone information on the disk. There are also some questions about how to write the superblocks for Btrfs on not-power-of-2 devices. Hearkening back to an earlier session , Chamberlain said that the lack of support for ioctl() and direct I/O (i.e. O_DIRECT ) in Java causes problems for using it with zonefs , which requires direct I/O. Le Moal said that the long-term goal is to remove the direct I/O requirement, but it is currently needed to maintain the write-order guarantees. After Chamberlain asked about the status of bcachefs , Kent Overstreet said that it already has native zoned-device support. The allocation mechanism for bcachefs has always been bucket-based, going back to bcache , which is a good match to zoned storage. Those devices will work just as well as regular block devices for bcachefs, he said. Chamberlain said he has been using kdevops to "test the hell out of zoned-storage devices" with both fstests and blktests. There are two modes of testing that can be done, either with real hardware or using QEMU virtual devices. There are some problems, currently, with the QEMU driver for ZNS devices, Le Moal said. Bart Van Assche wondered if there was a need to keep an eye on the standards committees because it seems like there is a gap between the feature sets offered by SCSI and NVMe. Today the zoned-device code is shared for SCSI and NVMe in the kernel, but he worries that may have to change. In particular, filesystems might be forced to choose which of the two types they support. Le Moal said that there are features in ZNS that are not available for SCSI; Btrfs has been trying to adapt to those differences, for example. Van Assche is working on Android devices with zoned storage. The devices are currently SCSI, but will eventually be NVMe-based; he is concerned that the filesystem being used will have to change because of that. Le Moal said that the goal is that the filesystems should not have to care about the type of the underlying device. Several others said that because the underlying storage technology is quite different, though, the kernel may end up with two APIs for zoned storage. To a certain extent, the differences in the I/O scheduler reflect that, one attendee said. Josef Bacik said that there should be only minimal differences that filesystems need to be aware of in order to support zoned storage. There are already changes in Btrfs to support the idea of zones, but that is about as far as things should go; anything further should be pushed out to user space, he said. Ts'o said that the block layer is the right place to handle these extra features and to do so in a way that hides the underlying differences from filesystems. He noted that features like discard are used by filesystems through the block-layer interface, which hides the device differences. If there are new features that can provide a large benefit, storage-device developers should have a conversation with the filesystem community about them, Ts'o said. If, for example, providing a hint that some data is for a journal, such as for a filesystem or database, would make a big performance difference, there may be a way to change the filesystems and applications to take advantage of it. But the benefit needs to be large and the interface to the feature needs to be stable. "It would probably be an ioctl() ", he said to chuckles, but he could imagine adding a feature of that sort. Index entries for this article Kernel Block layer/Zoned devices Kernel Filesystems Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments Zoned storage Posted Jun 15, 2022 12:12 UTC (Wed) by developer122 (guest, #152928) [ Link ] yeah, I can see one form of hiding being bad for journaling: caching random writes to a zone so they can all be written out at once caching like that could potentially wreak havoc with a journalling system, but flushing the right areas at the right times may be fraut with misunderstanding due to the difference between journal and zone sizes Storage: it can only evolve to more diversity Posted Jun 19, 2022 16:12 UTC (Sun) by abufrejoval (guest, #100159) [ Link ] Currently SLC vs. MLC/TLC/QLC is mostly a decision made by the SSD, slight chance it will ever by an optimal choice for the user, who will only know over time, sometimes long after the first write (and the initial decision), which speed vs. storage effiency is best for a given bit of data. The hardware in all likelyhood only needs to be told how an erase block needs to be handled, but can't quite expose that yet at this level of granularity. And when there is an order of magnitude in difference, not even the OS may be in a good position to make that decision: you'll have to ask the data owner via the application or service. I think the Linux community should concentrate less on stopgap attempts to follow the technical evolution and plan ahead to a much greater evolution of diverse storage technologies, because without proper abstractions, taking advantage of them will be difficult. And there perhaps one thing needs a bit more attention: Zoning decisions for a bit of data will only ever be optimal for a given point in time, so the ability to change them with measurable effort/value is key. Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:41 |
https://support.microsoft.com/en-us/microsoft-store-and-billing | Microsoft Store & billing help Skip to main content Microsoft Support Support Support Home Microsoft 365 Office Products Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows more ... Devices Surface PC Accessories Xbox PC Gaming HoloLens Surface Hub Hardware warranties Account & billing Account Microsoft Store & billing Resources What's new Community forums Microsoft 365 Admins Small Business Portal Developer Education Report a support scam Product safety More Buy Microsoft 365 All Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Deals Small Business Support Software Software Windows Apps AI Outlook OneDrive Microsoft Teams OneNote Microsoft Edge Moving from Skype to Teams PCs & Devices PCs & Devices Computers Shop Xbox Accessories VR & mixed reality Certified Refurbished Trade-in for cash Entertainment Entertainment Xbox Game Pass Ultimate PC Game Pass Xbox games PC games Business Business Microsoft Security Dynamics 365 Microsoft 365 for business Microsoft Power Platform Windows 365 Microsoft Industry Small Business Developer & IT Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Other Other Microsoft Rewards Free downloads & security Education Gift cards Licensing Unlocked stories View Sitemap Search Search for help No results Cancel Sign in Sign in with Microsoft Sign in or create an account. Hello, Select a different account. You have multiple accounts Choose the account you want to sign in with. Microsoft Store & billing help Manage subscriptions Returns & refunds Payment options Order history Gift cards Install Microsoft 365 Microsoft Store on Windows Explore Microsoft Store services From free shipping and returns to our 60-day price protection, we're here to help you do more with best-in-class devices, software, games, and resources. Check out what the Microsoft Store has to offer: Shopping and purchase support | Product setup and training | Small business support Shopping and purchase support Microsoft Store services aren't available in all regions. To see what options are available to you, select your country or region from the dropdown list below and if it's not listed, select Other regions . Select your region United States Australia Canada (English) Canada (French) United Kingdom Other regions Why shop at Microsoft Store Easy, convenient shopping Free 2-3 day shipping Free 60-day returns 60-day price protection Flexible payment options Cash for your used device Trade-in and recycling Special discounts and offers For students, parents, and educators For military personnel Extended device protection Microsoft Complete protection plan We can help you find what you need Sales support help Disability answer desk Shop with an ASL associate Why shop at Microsoft Store Easy, convenient shopping Free shipping Free 60-day returns 60-day price protection Cash for your used device Trade-in and recycling Special discounts and offers For students, parents, and educators We can help you find what you need Sales support help Disability answer desk Why shop at Microsoft Store Easy, convenient shopping Free shipping Free 60-day returns 60-day price protection Cash for your used device Trade-in and recycling Special discounts and offers For students, parents, and educators Extended device protection Microsoft Complete protection plan We can help you find what you need If you have questions before you buy, chat with a product expert or book a shopping appointment. Sales support help Why shop at Microsoft Store Easy, convenient shopping Free shipping Free 60-day returns 60-day price protection Cash for your used device Trade-in and recycling Special discounts and offers For students, parents, and educators Extended device protection Microsoft Complete protection plan Why shop at Microsoft Store Easy, convenient shopping Free shipping Free 60-day returns 60-day price protection Cash for your used device Trade-in and recycling Special discounts and offers For students, parents, and educators We can help you find what you need Sales support help Disability answer desk Why shop at Microsoft Store We can help you find what you need If you have questions before you buy, chat with a product expert. Sales support help Browse the Microsoft Store The Microsoft Store Product setup and training Not all Microsoft Store services listed here are available in all regions. To see your options, select your country or region from the dropdown list below: Select your region United States Australia Canada (English) Canada (French) United Kingdom Other regions Help and learning resources Check out our product support resources to help you find the answers you need. Surface devices | Xbox Microsoft 365 | Windows Help and learning resources Our product support resources are here to help you find the answers you need. Surface devices | Xbox Microsoft 365 | Windows Help and learning resources Check out our product support resources to help you find the answers you need. Surface devices | Xbox Microsoft 365 | Windows Help and learning resources Check out our product support resources to help you find the answers you need. Surface devices | Xbox Microsoft 365 | Windows Help and learning resources Check out our product support resources to help you find the answers you need. Surface devices | Xbox Microsoft 365 | Windows Help and learning resources Check out our product support resources to help you find the answers you need. Surface devices | Xbox Microsoft 365 | Windows Small business support To see what small business support options are available in your region, select your country or region from the dropdown list below: Select your region United States Australia Canada (English) Canada (French) United Kingdom Other regions Resources for your small business Get advice, free training, products, and tools to help your business thrive. Small business help and learning Small business Resource Center Resources for your small business Get advice, free training, products, and tools to help your business thrive. Small business help and learning Small business Resource Center Resources for your small business Get advice, free training, products, and tools to help your business thrive. Small business help and learning Small business resource centre Resources for your small business From assessing your business needs to assisting with setup and troubleshooting, we're here to help. Get advice, free training, products, and tools to help your business thrive. Small business help and learning Small business resource centre Resources for your small business Get advice, free training, products, and tools to help your business thrive. Small business help and learning Small business Resource Center Resources for your small business Get advice, free training, products, and tools to help your business thrive. Small business help and learning What's new Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organizations Copilot for personal use AI in Windows Explore Microsoft products Windows 11 apps Microsoft Store Account profile Download Center Microsoft Store support Returns Order tracking Certified Refurbished Microsoft Store Promise Flexible Payments Education Microsoft in education Devices for education Microsoft Teams for Education Microsoft 365 Education How to buy for your school Educator training and development Deals for students and parents AI for education Business Microsoft Security Dynamics 365 Microsoft 365 Microsoft Power Platform Microsoft Teams Microsoft 365 Copilot Small Business Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Company Careers About Microsoft Company news Privacy at Microsoft Investors Diversity and inclusion Accessibility Sustainability English (United States) Your Privacy Choices Opt-Out Icon Your Privacy Choices Your Privacy Choices Opt-Out Icon Your Privacy Choices Consumer Health Privacy Sitemap Contact Microsoft Privacy Manage cookies Terms of use Trademarks Safety & eco Recycling About our ads © Microsoft 2026 | 2026-01-13T09:29:41 |
https://t.me/s/xdadevelopershub/7 | XDA-Hub – Telegram XDA-Hub @xdadevelopershub 10.7K subscribers 1 link Find your Telegram group here! Download Telegram About Blog Apps Platform Join XDA-Hub 10.7K subscribers XDA-Hub Channel created 16:02 XDA-Hub Welcome to the official XDA-Developers Telegram chat hub. Here you will find links to all official XDA Telegram chat groups. The XDA-Developers Telegram chats are run by members of XDA Management with help from various trusted community members. Please read the rules pinned in each chat before posting! 187K views edited 17:29 XDA-Hub XDA-Hub pinned « Welcome to the official XDA-Developers Telegram chat hub. Here you will find links to all official XDA Telegram chat groups. The XDA-Developers Telegram chats are run by members of XDA Management with help from various trusted community members. Please read… » 17:30 XDA-Hub Here are links to all OFFICIAL XDA Telegram groups. General Discussion : https://t.me/joinchat/KXmvpgeIr7JiNGEx XDA News Channel : https://t.me/xdanews ASUS Device Discussion: https://t.me/joinchat/Q2YJFoMvRKQ4N2Yx Chromebook Device Discussion: https://t.me/joinchat/Sgs0zFM3_rm8p2Fd Google Device Discussion: https://t.me/joinchat/Tn0_X8lKl40KN1zW Huawei/Honor Device Discussion: https://t.me/joinchat/TJUpgEQQmqF_FTOZ HTC Device Discussion: https://t.me/+QG1-8P5LmkISsoS9 LG Device Discussion: https://t.me/joinchat/UdSdaMIeGGgRIZ2S Motorola Device Discussion: https://t.me/joinchat/R89sWWCROAakfper Nokia Device Discussion: https://t.me/joinchat/Go8k90PsqGgzNDZh OnePlus Device Discussion: https://t.me/joinchat/a5VD_V82uL8zYjJh Realme Device Discussion: https://t.me/joinchat/VvxL8IUXpgY0EtJ9 Samsung Device Discussion: https://t.me/joinchat/Uw71PrO_bkDW_qVb Sony Device Discussion: https://t.me/joinchat/PFwD82Mkf7ZhZDcx Xiaomi Device Discussion: https://t.me/joinchat/RTgVtz1K-1BScRZd Telegram XDA-General The official general discussion group for members of XDA-Developers. 73.2K views edited 18:30 XDA-Hub XDA Developers was founded on the simple principle that SHARING IS GOOD and when many people SHARE what they know, EVERYONE benefits. We exist upon this ethos. We RESPECT each other, we SHARE with each other, we do not judge one another, and we HELP all who ask. 72.7K views 18:30 XDA-Hub Channel photo updated 03:49 | 2026-01-13T09:29:41 |
https://www.linkedin.com/products/categories/ai-powered-coaching-software?trk=organization_guest_main_product_card_category_link | Best AI-Powered Coaching Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Head of Human Resources (7) Chief Executive Officer (6) Human Resources Manager (4) Salesperson (4) Human Resources Specialist (3) See all products Find top products in AI-Powered Coaching Software category Software used to improve skills using guidance enabled by artificial intelligence. - Receive daily and on-demand recommendations, tips, and support - Engage in AI-led conversation and use platform to track analytics and progress - Combine traditional coaching with continuous feedback from automated analysis - Access information and solutions with better personalization and customization over time 112 results LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software by LinkedIn LinkedIn Learning combines AI-powered coaching with realistic role play scenarios, giving job seekers and learners a safe, supportive space to practice interviews and workplace conversations. With AI-powered coaching, you can ask questions like “How do I prepare for an interview?” or “How can I change careers?” and get instant, personalized advice drawn from LinkedIn Learning’s entire expert-led course library. With role play, you can rehearse conversations by text or voice, receive real-time feedback on tone and delivery, and get tailored course recommendations to close skill gaps. Whether you’re interviewing, changing careers, or building confidence for tough conversations, LinkedIn Learning helps you practice, grow, and achieve your goals. View product LinkedIn Interview Prep AI AI-Powered Coaching Software by LinkedIn With LinkedIn Premium, you get access to Interview Prep AI, built on the power of LinkedIn’s job marketplace. Practice mock interviews with personalized questions specifically for the roles you’re applying to, so your prep matches the opportunities you care about most. Role play live with an AI interviewer that asks realistic follow-ups and get tailored feedback on your strengths and areas to improve. Only on LinkedIn can your job search and your interview prep come together in one place, helping you walk into interviews with confidence and stand out for your next opportunity. View product AI Resume Builder AI-Powered Coaching Software by HubbedIn HubbedIn's Resume Builder is an AI-powered tool designed to simplify the resume creation process. It assists job seekers in crafting professional resumes effortlessly, offering personalized suggestions and rephrasing sentences to meet specific job requirements. Our AI tool aims to elevate job seekers' applications by ensuring your resumes stand out and accurately reflect your achievements and skills. View product CoachHub - The digital coaching platform AI-Powered Coaching Software by CoachHub - The digital coaching platform CoachHub is the global leader in digital coaching. We enable organizations to deliver personalized, scalable coaching programs that drive measurable business impact across the workforce. Coaching Solutions Designed for Scale ✔️CoachHub Individual: Support long-term growth by giving employees access to world-class business coaches. ✔️CoachHub Executive™: Help senior leaders turn complexity into clarity and vision into results. ✔️CoachHub Collective: Build stronger teams through expert-led group coaching that accelerates collaboration and problem-solving. ✔️AIMY™: Our pioneering AI coach makes coaching scalable, measurable and accessible across the organization. The Business Impact ✔️Companies that partner with CoachHub see: ✔️Higher employee engagement and retention ✔️Measurable improvements in productivity and performance ✔️Stronger leadership pipelines and employer brand View product MOBILITY AI-Powered Coaching Software by Office Solution AI Labs Being able to do business “on the go” with mobile apps matters now more than ever for the customers and your workforce. As the whole world is getting hyper-connected, enterprises are moving towards mobile apps. If you want to automate your business operations and manage your entire business model easily, we at MS Office Solution can help you. We design and develop mobility solutions for your enterprise that simplify your challenging tasks and address all your business concerns. Mobile analytics captures data from the mobile apps, websites, and the web apps’ visitors to identify unique users, tracking their visits to the site, record their behavior, and prepare reports on the application performance. Capturing analytics from mobility and deriving useful insights from it is one of the major trends followed by the businesses. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Exponent Practice AI-Powered Coaching Software by Exponent Interview Prep Ace tech interviews with AI-powered feedback and peer mocks. Join thousands of tech candidates practicing interviews to land jobs. Practice real questions over video chat in a collaborative environment with personalized AI feedback and rubric evaluation. View product Yoodli AI Roleplays AI-Powered Coaching Software by Yoodli AI Roleplays Trusted by Fortune 100 companies, Yoodli helps teams ramp faster, win more deals, and communicate with confidence in their most critical conversations. As an AI-powered roleplay simulator, Yoodli supports training across sales, leadership, and customer engagement—delivering private, real-time, judgment-free coaching at scale. Teams can rehearse discovery calls, objection handling, negotiations, presentations, interviews, or feedback conversations anytime, anywhere. Yoodli provides instant feedback on clarity, confidence, and delivery, plus progress tracking to measure growth across teams. Leaders gain scalable, data-driven insights to identify strengths and coach where it matters most—ensuring practice translates into measurable results. View product Find a Hiring Manager AI-Powered Coaching Software by HubbedIn Our "Find Hiring Manager" tool is designed to significantly enhance your job search. We leverage AI to connect you directly with hiring managers, giving you the edge you need to stand out. By providing access to the email and LinkedIn profiles of hiring managers, we help you reach the right people faster. Our platform also crafts personalized messages by analyzing your resume and the job details, increasing your chances of getting hired. Plus, with our resume builder's tracker feature, you can stay informed about your resume's performance. View product UP AI Growth Companion AI-Powered Coaching Software by UP School Meet Your AI-Powered Growth Catalyst UP transforms everyday moments into breakthrough performance through personalized micro-learning that adapts to each employee's role, learning style, and growth goals. Our 30+ specialized AI coaches deliver just-in-time learning when and where your people need it most. How UP works differently: - 3-5 minute daily sessions that fit seamlessly into busy schedules - AI powered personalization that adapts to individual learning patterns and company culture - Safe practice environments for high-stakes scenarios like difficult conversations and presentations - Spaced repetition technology that ensures skills stick long-term Every day your team isn't using UP is a day of missed growth potential. Book a demo to discover. View product Artificial Intelligence for Business AI-Powered Coaching Software by Ateliware Seamlessly integrate the potential of artificial intelligence into your processes, boosting productivity and efficiency with tailored solutions. > AI Discovery: Want to implement AI but not sure where to start? We help you explore and identify the best opportunities for your business. > Proof of Concept: Know what you want but unsure if it's feasible? We create a quick PoC to test the solution's viability, discover costs, models, and the services you may need. > AI MVP: Already validated your idea and ready to launch an initial version? We develop the MVP using artificial intelligence to accelerate your go-to-market process. > Integration: Need to integrate an existing solution or add AI functionalities to your product? We handle the development. We work closely with your team to adapt the development process to your company’s specific needs, ensuring secure and customized integration. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/jira/solutions/program-management#tab-fae153b6-ac8c-441f-9852-bd0146ca7166 | 计划管理 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 Jira 为计划管理助力 使用 Jira 简化、精简、交付 了解 Jira 如何帮助您和您的团队将宏伟目标转化为可实现的项目。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行计划管理？ 克服复杂性 无论有多少团队参与其中，即使是最艰巨的战略计划，也要分解成可实现的小步骤。 驾驭依赖关系 在潜在的中断和不确定性影响团队工作之前，提前做好准备。 全面的可见性 查看和组织各团队的工作，以便更好地管理资源配置，做出明智的战略决策。 专为计划管理而设计的模板 适用于各类计划、项目和举措的可定制模板。 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 确定任务的优先次序，管理团队工作量，跟踪工作从规划到完成的整个过程。 开始使用 顶层规划 为您的团队提供清晰、实时的视图，以便进行协作、安排和调整战略目标。 开始使用 流程规划 让您的团队不再重复流程。对各种流程中的步骤进行分类，以便您和您的团队能够快速识别未完成的任务。 开始使用 甘特图 一款强大的可视化工具，用于跟踪工作和避开障碍。概述项目工期，指明里程碑并绘制依赖关系。 开始使用 个人任务跟踪器 跟踪个人任务，如电子邮件分类、会议准备和费用管理。 开始使用 计划和启动项目，全部从 Jira 中进行 规划 需求不断变化？没有关系 分析项目并自信地与利益相关者沟通，明确进度和优先事项。 执行和跟踪 协调工作，简化流程 跟踪项目，映射依赖关系，建立跨团队的审批工作流，并确保目标如期实现。 报告和结果 完善工作流程 有了触手可及的项目摘要，您就能更明智地制定计划，并随时掌握各项举措和项目的进展情况。 计划面板公开测试版 计划或季度规划的新界面 计划面板公开测试版 计划或季度规划的新界面 通过简单的拖放式计划功能，为下个季度规划多个团队的工作。 了解更多 集成您最喜欢的所有工具 将您的工具与 Jira 巧妙地集成，而无需在平台之间进行上下文切换。 查看更多集成 计划管理资源 浏览免费教程、文章和指南以了解更多信息。 敏捷教练 将数十年的敏捷实践提炼成简单易读的课程。 了解更多 项目管理指南 帮助您计划和管理项目的分步说明。 了解更多 协调业务和技术团队 了解如何打破孤岛，开展合作以便创造更好的产品。 阅读博客 转换工作方式 免费获取 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://accounts.google.com/ServiceLogin?hl=pt-BR&passive=true&continue=https://www.google.com/imghp%3Fhl%3Dpt-BR%26tab%3Dwi&ec=GAZAAg | :root{--gm3-sys-color-on-surface-rgb:31,31,31}@media screen and (prefers-color-scheme:dark){:root{--gm3-sys-color-on-surface-rgb:227,227,227}}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.q4Wquf,.nfoC7c{display:block;height:25vh;position:relative}@media (min-width:600px){.q4Wquf,.nfoC7c{height:150px}}.q4Wquf.Irjbwb{height:auto}@media screen and (prefers-color-scheme:dark){.q4Wquf:not(.GtvzYd){display:none}}.nfoC7c{margin:0;overflow:hidden}.PwpMUe,.lVUmD{display:block;height:100%;margin:0 auto;width:100%}.St9mde{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.St9mde{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.PwpMUe,.lVUmD,.St9mde{-o-object-fit:contain;object-fit:contain}.wsArZ[data-ss-mode="1"] .q4Wquf,.wsArZ[data-ss-mode="1"] .St9mde{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .St9mde{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .q4Wquf,.NQ5OL .St9mde{height:auto;width:100%}.NQ5OL .St9mde{max-width:400px}}.q4Wquf.NWba7e,.q4Wquf.NWba7e .St9mde{height:auto}.q4Wquf.NWba7e .St9mde{height:auto;max-width:312px;width:100%}.q4Wquf.NWba7e.zpCp3 .St9mde{max-width:unset}.q4Wquf.IiQozc .St9mde{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.q4Wquf.Irjbwb .St9mde{height:auto;width:100%}.q4Wquf.EEeaqf .St9mde{max-height:144px;max-width:144px}.SnAaEd{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.SnAaEd{display:none}}.SnAaEd::after,.SnAaEd::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.SnAaEd::after,.SnAaEd::before{width:150px}}.SnAaEd::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.SnAaEd::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .SnAaEd~.St9mde{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .SnAaEd~.St9mde{width:auto}}.RHNWk .St9mde{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .RHNWk .St9mde{width:115px}}.cf660d .St9mde{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.tUhwwc .St9mde{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.Jkvqxd .St9mde{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.onc8Ic .St9mde{-webkit-transform:translate(var( --c-ps-s,24px ),0);-ms-transform:translate(var( --c-ps-s,24px ),0);transform:translate(var( --c-ps-s,24px ),0)}.WA89Yb .St9mde{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .XEN8Yb .St9mde{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .XEN8Yb .St9mde{max-width:115px}}@media (min-width:1240px) and (orientation:landscape),all and (min-width:1600px){.KyPKed .NQ5OL .XEN8Yb .St9mde{max-width:115px}}.IsSr6b .St9mde{max-width:300px}.mmskdd .St9mde{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@-webkit-keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@-webkit-keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@-webkit-keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}:root{--wf-tfs:calc(var(--c-tfs,32)/16*1rem);--wf-tfs-bp2:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp3:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp5:calc(var(--c-tfs,44)/16*1rem);--wf-stfs:calc(var(--c-stfs,16)/16*1rem);--wf-stfs-bp5:calc(var(--c-stfs,16)/16*1rem)}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.Dzz9Db,.GpMPBe{display:block;height:25vh;position:relative}@media (min-width:600px){.Dzz9Db,.GpMPBe{height:150px}}@media screen and (prefers-color-scheme:dark){.Dzz9Db:not(.GtvzYd){display:none}}.Dzz9Db.Irjbwb{height:auto}.GpMPBe{margin:0;overflow:hidden}.UFQPDd,.JNOvdd{display:block;height:100%;margin:0 auto;-o-object-fit:contain;object-fit:contain;width:100%}.f4ZpM{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.f4ZpM{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.wsArZ[data-ss-mode="1"] .Dzz9Db,.wsArZ[data-ss-mode="1"] .f4ZpM{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .f4ZpM{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .Dzz9Db,.NQ5OL .f4ZpM{height:auto;width:100%}.NQ5OL .f4ZpM{max-width:400px}}.Dzz9Db.utFBGf,.Dzz9Db.utFBGf .f4ZpM{height:auto}.Dzz9Db.utFBGf .f4ZpM{height:auto;max-width:312px;width:100%}.Dzz9Db.utFBGf.zpCp3 .f4ZpM{max-width:unset}.Dzz9Db.IiQozc .f4ZpM{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.Dzz9Db.Irjbwb .f4ZpM{height:auto;width:100%}.Dzz9Db.EEeaqf .f4ZpM{max-height:144px;max-width:144px}.nPt1pc{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.nPt1pc{display:none}}.nPt1pc::after,.nPt1pc::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.nPt1pc::after,.nPt1pc::before{width:150px}}.nPt1pc::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.nPt1pc::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .nPt1pc~.f4ZpM{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .nPt1pc~.f4ZpM{width:auto}}.ZS7CGc .f4ZpM{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .ZS7CGc .f4ZpM{width:115px}}.qiRZ5e .f4ZpM{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.vIv7Gf .f4ZpM{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.nvYXVd .f4ZpM{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.uOhnzd .f4ZpM{-webkit-transform:translate(24px,0);-ms-transform:translate(24px,0);transform:translate(24px,0)}.MsYMaf .f4ZpM{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .YIi9qf .f4ZpM{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .YIi9qf .f4ZpM{max-width:115px}}.QG3Xbe .f4ZpM{max-width:300px}.F6gtje .f4ZpM{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe{font-size:24px;width:48px;height:48px;padding:12px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-Jh9lGc{width:40px;height:40px;margin-top:4px;margin-bottom:4px;margin-right:4px;margin-left:4px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-J1Ukfc-LhBDec{max-height:40px;max-width:40px}.VfPpkd-Bz112c-LgbsSe:disabled{color:rgba(0,0,0,.38);color:var(--mdc-theme-text-disabled-on-light,rgba(0,0,0,.38))}.VfPpkd-Bz112c-LgbsSe svg,.VfPpkd-Bz112c-LgbsSe img{width:24px;height:24px}.VfPpkd-Bz112c-LgbsSe{display:inline-block;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border:none;outline:none;background-color:transparent;fill:currentColor;color:inherit;text-decoration:none;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;z-index:0;overflow:visible}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-RLmnJb{position:absolute;top:50%;height:48px;left:50%;width:48px;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-J1Ukfc-LhBDec,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-J1Ukfc-LhBDec{display:block}}.VfPpkd-Bz112c-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-Bz112c-LgbsSe[hidden]{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-KVuj8d-Q3DXx{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center}.VfPpkd-Bz112c-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:100%;width:100%;display:none}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{border-color:CanvasText}}.VfPpkd-Bz112c-kBDsod{display:inline-block}.VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd,.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd{display:inline-block}.VfPpkd-Bz112c-mRLv6{height:100%;left:0;outline:none;position:absolute;top:0;width:100%}.VfPpkd-Bz112c-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;width:100%;height:100%}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-Bz112c-LgbsSe:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe:disabled:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc{height:100%;left:0;pointer-events:none;position:absolute;top:0;width:100%;z-index:-1}.VfPpkd-dgl2Hf-ppHlrf-sM5MNb{display:inline}.VfPpkd-LgbsSe{position:relative;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:64px;border:none;outline:none;line-height:inherit;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-appearance:none;overflow:visible;vertical-align:middle;background:transparent}.VfPpkd-LgbsSe .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}.VfPpkd-LgbsSe::-moz-focus-inner{padding:0;border:0}.VfPpkd-LgbsSe:active{outline:none}.VfPpkd-LgbsSe:hover{cursor:pointer}.VfPpkd-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-LgbsSe[hidden]{display:none}.VfPpkd-LgbsSe .VfPpkd-kBDsod{margin-left:0;margin-right:8px;display:inline-block;position:relative;vertical-align:top}[dir=rtl] .VfPpkd-LgbsSe .VfPpkd-kBDsod,.VfPpkd-LgbsSe .VfPpkd-kBDsod[dir=rtl]{margin-left:8px;margin-right:0}.VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge{font-size:0;position:absolute;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);top:50%;left:50%;line-height:normal}.VfPpkd-LgbsSe .VfPpkd-vQzf8d{position:relative}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px);display:none}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-color:CanvasText}}@media screen and (forced-colors:active){.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-J1Ukfc-LhBDec,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-J1Ukfc-LhBDec{display:block}}.VfPpkd-LgbsSe .VfPpkd-RLmnJb{position:absolute;top:50%;height:48px;left:0;right:0;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%)}.VfPpkd-vQzf8d+.VfPpkd-kBDsod{margin-left:8px;margin-right:0}[dir=rtl] .VfPpkd-vQzf8d+.VfPpkd-kBDsod,.VfPpkd-vQzf8d+.VfPpkd-kBDsod[dir=rtl]{margin-left:0;margin-right:8px}svg.VfPpkd-kBDsod{fill:currentColor}.VfPpkd-LgbsSe-OWXEXe-dgl2Hf{margin-top:6px;margin-bottom:6px}.VfPpkd-LgbsSe{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;text-decoration:none}.VfPpkd-LgbsSe{padding:0 8px 0 8px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-INsAgc{border-style:solid;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-style:solid;border-color:transparent}.VfPpkd-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{z-index:0}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Jh9lGc{position:absolute;-webkit-box-sizing:content-box;box-sizing:content-box;overflow:hidden;z-index:0;top:0;left:0;bottom:0;right:0}.VfPpkd-LgbsSe{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-text-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-filled-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;-webkit-box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-protected-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled):active{-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{-webkit-box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12);box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;padding:0 15px 0 15px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-outlined-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 11px 0 15px}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 15px 0 11px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{top:-1px;left:-1px;bottom:-1px;right:-1px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-RLmnJb{left:-1px;width:calc(100% + 2px)}.nCP5yc{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.nCP5yc .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.nCP5yc:not(:disabled){background-color:rgb(26,115,232);background-color:var(--gm-fillbutton-container-color,rgb(26,115,232))}.nCP5yc:not(:disabled){color:#fff;color:var(--gm-fillbutton-ink-color,#fff)}.nCP5yc:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-fillbutton-disabled-container-color,rgba(60,64,67,.12))}.nCP5yc:disabled{color:rgba(60,64,67,.38);color:var(--gm-fillbutton-disabled-ink-color,rgba(60,64,67,.38))}.nCP5yc .VfPpkd-Jh9lGc::before,.nCP5yc .VfPpkd-Jh9lGc::after{background-color:rgb(32,33,36);background-color:var(--gm-fillbutton-state-color,rgb(32,33,36))}.nCP5yc:hover .VfPpkd-Jh9lGc::before,.nCP5yc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.16;opacity:var(--mdc-ripple-hover-opacity,.16)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24;opacity:var(--mdc-ripple-focus-opacity,.24)}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.2;opacity:var(--mdc-ripple-press-opacity,.2)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.2)}.nCP5yc .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:#fff}@media (-ms-high-contrast:active),screen and (forced-colors:active){.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.nCP5yc:hover{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:hover .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:active{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:active .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:disabled{-webkit-box-shadow:none;box-shadow:none}.nCP5yc:disabled:hover .VfPpkd-Jh9lGc::before,.nCP5yc:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.Rj2Mlf .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.Rj2Mlf:not(:disabled){color:rgb(26,115,232);color:var(--gm-hairlinebutton-ink-color,rgb(26,115,232))}.Rj2Mlf:not(:disabled){border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled):hover{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled).VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.Rj2Mlf:not(:disabled):not(.VfPpkd-ksKsZd-mWPk3d):focus{border-color:rgb(23,78,166);border-color:var(--gm-hairlinebutton-outline-color--stateful,rgb(23,78,166))}.Rj2Mlf:not(:disabled):active,.Rj2Mlf:not(:disabled):focus:active{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:disabled{color:rgba(60,64,67,.38);color:var(--gm-hairlinebutton-disabled-ink-color,rgba(60,64,67,.38))}.Rj2Mlf:disabled{border-color:rgba(60,64,67,.12);border-color:var(--gm-hairlinebutton-disabled-outline-color,rgba(60,64,67,.12))}.Rj2Mlf:hover:not(:disabled),.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.Rj2Mlf:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-hairlinebutton-ink-color--stateful,rgb(23,78,166))}.Rj2Mlf .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.Rj2Mlf .VfPpkd-Jh9lGc::before,.Rj2Mlf .VfPpkd-Jh9lGc::after{background-color:rgb(26,115,232);background-color:var(--gm-hairlinebutton-state-color,rgb(26,115,232))}.Rj2Mlf:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Rj2Mlf:disabled:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.b9hyVd{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);border-width:0;-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15))}.b9hyVd .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.b9hyVd:not(:disabled){background-color:#fff;background-color:var(--gm-protectedbutton-container-color,#fff)}.b9hyVd:not(:disabled){color:rgb(26,115,232);color:var(--gm-protectedbutton-ink-color,rgb(26,115,232))}.b9hyVd:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-protectedbutton-disabled-container-color,rgba(60,64,67,.12))}.b9hyVd:disabled{color:rgba(60,64,67,.38);color:var(--gm-protectedbutton-disabled-ink-color,rgba(60,64,67,.38))}.b9hyVd:hover:not(:disabled),.b9hyVd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.b9hyVd:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.b9hyVd:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-protectedbutton-ink-color--stateful,rgb(23,78,166))}.b9hyVd .VfPpkd-BFbNVe-bF1uUb{opacity:0}.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-B | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/software/jira/free?templateId=com.atlassian.jira-core-project-templates:jira-work-management-personal-task-planner | Jira Free：免费获取 Jira Software | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/regex/ | Index of /old-gnu/regex Index of /old-gnu/regex Name Last modified Size Description Parent Directory - README 2001-05-09 09:05 155 regex-0.12.tar.gz 1993-04-03 03:00 291K Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://opensource.google/documentation/reference?hl=es-419#main-content | Google Open Source Skip to main content Events Projects Programs and services Organizations we support Documentation About Blog / Sign in Documentation Overview Reference Guides Policies Publications OSS CNA Events Projects Programs and services More Documentation Overview Reference Guides Policies Publications OSS CNA About Blog Organizations we support Google Open Source Documentation Stay organized with collections Save and categorize content based on your preferences. Open source is about more than just code. It's also about the planning that happens before the code is written, the process of how that code is used by others, and fostering a welcoming environment where a community can grow. In the spirit of openness, we are publishing our internal documentation for how we do open source at Google. We invite you to take a look behind the scenes at how we use, release, and support open source projects and communities. What is included This is a copy of our internal open source documentation, with a few exceptions. For a number of reasons, we can't share everything, so you might find places where a link is missing or some content had to be removed. Aside from those few cases, this is the same documentation seen by Google employees. As a result, there is some Google lingo throughout, as well as references to internal tools and systems. See the glossary for definitions of some of the most common ones. There are three primary sections of the docs: Creating covers how Googlers release code that they've written, either in the form of a new standalone project or as a patch to an external project. The same process is used for small 20% projects and full blown Google projects. Using explains how we bring open source code into the company and use it to help build great products. We carefully catalog thousands of packages to help us maintain license compliance. Growing describes some of the programs we run inside and outside the company to support open source communities. Who this is for For other companies that are releasing or using open source software, we want to share the lessons we've learned from many years of experience. By being as transparent as we can about how we do open source, we hope to help others do the same. However, many of the things we do are unique to how Google operates and our engineering culture, so these should not be read as "how-to" guides. To hear from more companies deeply involved in open source, we recommend checking out the TODO Group . For individuals or project maintainers, if you've ever contributed to Google open source projects, or received a patch from a Googler, you've been exposed to how we do things. We hope that these documents provide useful insight into how we approach open source and answer questions you may have. Googlers should continue to use the internal copy of these docs at go/opensource. Really? Yes, we really do publish our internal documentation for all the world to see! One of the goals of the site is to expose (where appropriate) our internal processes related to open source so that other companies have the opportunity to learn from them. We carefully review all content before it's published externally, using automated tooling (go/cleanr) to rewrite internal URLs, file paths, and certain project code names. We also perform a human review of all changes before they're published. In general, we don't consider go/ links to be sensitive since they aren't accessible by non-Googlers and typically have generic names. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-06-10 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-10 UTC."],[],[]] YouTube X LinkedIn Terms Privacy Manage cookies | 2026-01-13T09:29:41 |
https://support.microsoft.com/et-ee/office/mis-on-funktsioon-vahetused-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Mis on funktsioon Vahetused? - Microsofti tugiteenus Seotud teemad × Microsoft Teamsi videokoolitus Microsoft Teamsi lühijuhend Mis on Microsoft Teams? Sisselogimine ja alustamine Vestlus ja failide ühiskasutus Koostöö Lisateave Microsoft Teamsi sissejuhatus Microsoft Teamsi kasutamise alustamine Vestluse kasutuselevõtt Koosolekute kasutuselevõtt Rakenduste kasutuselevõtt Töörühma häälestamine ja kohandamine Mallidega töörühma loomine Töö väliste külalistega Töörühma sätete haldamine Koostöö töörühmades ja kanalites Nõuanne: meilisõnumi saatmine kanalisse Plaani loomine Planneriga Töö postituste ja sõnumitega Sõnumi postitamine mitmesse kanalisse Failide otsimine Failide üleslaadimine ja jagamine Inimeste ja failide otsimine ja filtreerimine Meilisõnumite otsimine ja filtreerimine Teamsi failide näpunäited Vestluste alustamine ja helistamine Teamsi kõnede ülevaade Helistamine Teamsi kõnede näpunäited Vestluste peitmine ja sõnumite kustutamine Volitatud esindaja häälestamine kõnede vastuvõtmiseks Koosolekute haldamine Teamsi koosolekuga liitumine Teamsi koosolekute näpunäited Välkkoosolek Koosolekute haldamine Veebiseminari ajastamine Kuva jagamine koosoleku ajal Otseedastussündmuste häälestamine ja osavõtt Otseedastussündmuse kavandamine ja ajastamine Otseedastussündmuse produtseerimine Reaalajas sündmusel osalemine Küsimuste ja vastuste modereerimine Rakenduste ja tööriistadega tutvumine Rakenduste otsimine ja kasutamine Meeskonna ajakavade haldamine funktsiooniga Vahetused Mis on funktsioon Vahetused? Funktsiooni Vahetused graafiku loomine Funktsiooni Vahetused graafiku haldamine Kinnituste loomine Mis on kinnitused? Kinnituse loomine Vestlusest kinnituse loomine Elektroonilise allkirja kinnituse loomine Leia mallid kinnituste alt Mallidega kinnituste loomine Organisatsiooniüleste mallide loomine Virtuaalsed kohtumised Microsoft Bookingsis Mis on virtuaalsed kohtumised? Väliste külaliste SMS-tekstsõnumite saatmine Kohtumise korraldamine Kohtumisega liitumine Tegevuste voo haldamine Teatisesätete haldamine Teamsi kasutamine liikvel olles Vestluse alustamine liikvel olles Kanali loomine liikvel olles Liikvel olles koosolekuga liitumine Kanali Tegevus kasutamine liikvel olles Põhisisu juurde Microsoft Tugi Tugi Tugi Avaleht Microsoft 365 Office Teamsi tugi Teemad Koosolekud Vestlus Teatised ja toimingud Töörühmad ja kanalid Kõned ja seadmed Failid Rakendused ja teenused Kiirkäivitus Vestlus Rühmavestlus Teatised Teams Kanalid Kõned Failid Rakendused Loopi komponendid Mis on uut? Ressursid Videokoolitus Tõrkeotsing Siin Teamsis Hõlbustatus Teamsi funktsioonid platvormi järgi Microsoft Teams (tasuta) Kogukonnafoorumid Tehnoloogiakogukonna ajaveeb Juhendaja juhendatav koolitus Administraatoritele ja IT-spetsialistidele Haridusasutustele Rohkem Osta Microsoft 365 Kogu Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Tugi Tarkvara Tarkvara Windowsi rakendused AI OneDrive Outlook Üleminek Skype'ilt Teamsile OneNote Microsoft Teams Arvutid ja seadmed Arvutid ja seadmed Accessories Meelelahutus Meelelahutus PC-mängud Äri Äri Microsofti turve Azure Dynamics 365 Microsoft 365 ettevõtteversioon Microsoft Industry Microsoft Power Platform Windows 365 Arendaja ja IT Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Visual Studio Marketplace Rewards Muud Muud Tasuta allalaadimised ja turve Kuva saidikaart Otsing Spikri otsing Tulemid puuduvad Loobu Logi sisse Logige sisse Microsofti kontoga Logige sisse või looge konto. Tere! Valige mõni muu konto. Teil on mitu kontot Valige konto, millega soovite sisse logida. Seotud teemad Microsoft Teamsi videokoolitus Microsoft Teamsi lühijuhend Mis on Microsoft Teams? Sisselogimine ja alustamine Vestlus ja failide ühiskasutus Koostöö Lisateave Microsoft Teamsi sissejuhatus Microsoft Teamsi kasutamise alustamine Vestluse kasutuselevõtt Koosolekute kasutuselevõtt Rakenduste kasutuselevõtt Töörühma häälestamine ja kohandamine Mallidega töörühma loomine Töö väliste külalistega Töörühma sätete haldamine Koostöö töörühmades ja kanalites Nõuanne: meilisõnumi saatmine kanalisse Plaani loomine Planneriga Töö postituste ja sõnumitega Sõnumi postitamine mitmesse kanalisse Failide otsimine Failide üleslaadimine ja jagamine Inimeste ja failide otsimine ja filtreerimine Meilisõnumite otsimine ja filtreerimine Teamsi failide näpunäited Vestluste alustamine ja helistamine Teamsi kõnede ülevaade Helistamine Teamsi kõnede näpunäited Vestluste peitmine ja sõnumite kustutamine Volitatud esindaja häälestamine kõnede vastuvõtmiseks Koosolekute haldamine Teamsi koosolekuga liitumine Teamsi koosolekute näpunäited Välkkoosolek Koosolekute haldamine Veebiseminari ajastamine Kuva jagamine koosoleku ajal Otseedastussündmuste häälestamine ja osavõtt Otseedastussündmuse kavandamine ja ajastamine Otseedastussündmuse produtseerimine Reaalajas sündmusel osalemine Küsimuste ja vastuste modereerimine Rakenduste ja tööriistadega tutvumine Rakenduste otsimine ja kasutamine Meeskonna ajakavade haldamine funktsiooniga Vahetused Mis on funktsioon Vahetused? Funktsiooni Vahetused graafiku loomine Funktsiooni Vahetused graafiku haldamine Kinnituste loomine Mis on kinnitused? Kinnituse loomine Vestlusest kinnituse loomine Elektroonilise allkirja kinnituse loomine Leia mallid kinnituste alt Mallidega kinnituste loomine Organisatsiooniüleste mallide loomine Virtuaalsed kohtumised Microsoft Bookingsis Mis on virtuaalsed kohtumised? Väliste külaliste SMS-tekstsõnumite saatmine Kohtumise korraldamine Kohtumisega liitumine Tegevuste voo haldamine Teatisesätete haldamine Teamsi kasutamine liikvel olles Vestluse alustamine liikvel olles Kanali loomine liikvel olles Liikvel olles koosolekuga liitumine Kanali Tegevus kasutamine liikvel olles Mis on funktsioon Vahetused? Rakenduskoht Teams Microsoft Teams Proovige järele! Microsoft Teamsi rakendus Shifts on ajakavade haldamise ja ajajälituse tööriist, mis aitab teil luua, värskendada ja hallata oma meeskonna ajakavasid. Ajakavad – saate luua, redigeerida ja hallata oma meeskonna ajakava. Ajakava Vahetused kuvab päevad üleval, meeskonnaliikmed vasakul ja määratud vahetused kuvatakse kalendris. Ajastamissätted – määratlege tõstuklahvi (Shift) sätetes ajakava suvandid ja valige võimalused, mille soovite oma meeskonnale kättesaadavaks teha. Rühmad – saate lisada ajakavarühmi, et korraldada ajakavas olevaid meeskonnaliikmeid töö tüübi või asukoha järgi. Shifts – määrake vahetused meeskonna liikmetele. Saate nullist vahetuse luua või olemasoleva kopeerida. Avatud vahetused – igal ajakava rühmal on rida Ava vahetused . Lisage ajakavale avatud vahetused, mida igaüks saab taotleda. Kellaaeg – lülitage sisse ajakell vahetuse sätetes, et lubada meeskonnakell vahetustesse ja vahetustest välja lülitada. Taotlused – saate vaadata eemaldumisaega, avatud vahetusi, vahetuste vahetusi ja pakkumisi ning neile vastata. Sildid . Kasutage vahetustel põhinevaid silte, et kiiresti suhelda kõigiga, kes on praegu vahetuses. Ajakava avaldamine – kui olete ajakavas muudatuste tegemise lõpetanud, jagage seda oma meeskonnaga, et kõik oleks ajakohane. Kas soovite lisateavet? Rakenduse vahetused kasutamise alustamine Meeskonna ajakava loomine tõstuklahviga Shifts Ajakavale vahetuste lisamine funktsioonis Vahetused Ajakava avaldamine vahetustes Vahetuse taotluste ja eemal olekuaja haldamine vahetustes Teamsis vahetustel põhinevate siltide sisselülitamine TELLIGE RSS-KANALID Kas vajate veel abi? Kas soovite rohkem valikuvariante? Tutvustus Kogukonnafoorum Siin saate tutvuda tellimusega kaasnevate eelistega, sirvida koolituskursusi, õppida seadet kaitsma ja teha veel palju muud. Microsoft 365 tellimuse eelised Microsoft 365 koolitus Microsofti turbeteenus Hõlbustuskeskus Kogukonnad aitavad teil küsimusi esitada ja neile vastuseid saada, anda tagasisidet ja saada nõu rikkalike teadmistega asjatundjatelt. Nõu küsimine Microsofti kogukonnafoorumis Microsofti spetsialistide kogukonnafoorum Windows Insideri programmis osalejad Microsoft 365 Insideri programmis osalejad Kas sellest teabest oli abi? Jah Ei Aitäh! Veel tagasisidet Microsoftile? Kas saaksite aidata meil teenust paremaks muuta? (Saatke Microsoftile tagasisidet, et saaksime aidata.) Kui rahul te keelekvaliteediga olete? Mis mõjutas teie hinnangut? Leidsin oma probleemile lahenduse Juhised olid selged Tekstist oli lihtne aru saada Tekstis pole žargooni Piltidest oli abi Tõlkekvaliteet Tekst ei vastanud minu ekraanipildile Valed juhised Liiga tehniline Pole piisavalt teavet Pole piisavalt pilte Tõlkekvaliteet Kas soovite anda veel tagasisidet? (Valikuline) Saada tagasiside Kui klõpsate nuppu Edasta, kasutatakse teie tagasisidet Microsofti toodete ja teenuste täiustamiseks. IT-administraator saab neid andmeid koguda. Privaatsusavaldus. Täname tagasiside eest! × Mis on uut? Copilot organisatsioonidele Copilot isiklikuks kasutuseks Microsoft 365 Windows 11 rakendused Microsoft Store Konto profiil Allalaadimiskeskus Tagastused Tellimuse jälgimine Ringlussevõtt Commercial Warranties Haridus Microsoft Education Haridusseadmed Microsoft Teams haridusasutustele Microsoft 365 Education Office Education Haridustöötajate koolitus ja arendus Pakkumised õpilastele ja vanematele Azure õpilastele Äri Microsofti turve Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamsi jaoks Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Ettevõte Töökohad Teave Microsofti kohta Privaatsus Microsoftis Investorid Jätkusuutlikkus Eesti (Eesti) Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Tarbijaseisundi privaatsus Võtke Microsoftiga ühendust Privaatsus Halda küpsiseid Kasutustingimused Kaubamärgid Reklaamide kohta EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/ru/v2/%d0%a0%d0%b0%d1%81%d0%bf%d1%80%d0%b5%d0%b4%d0%b5%d0%bb%d1%91%d0%bd%d0%bd%d1%8b%d0%b9-Git-%d0%a0%d0%b0%d1%81%d0%bf%d1%80%d0%b5%d0%b4%d0%b5%d0%bb%d1%91%d0%bd%d0%bd%d1%8b%d0%b9-%d1%80%d0%b0%d0%b1%d0%be%d1%87%d0%b8%d0%b9-%d0%bf%d1%80%d0%be%d1%86%d0%b5%d1%81%d1%81 | Git - Распределённый рабочий процесс About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 5.1 Распределённый Git - Распределённый рабочий процесс Теперь, когда вы обзавелись настроенным удалённым Git-репозиторием, т. е. местом, где разработчики могут обмениваться своим кодом, а также познакомились с основными командами Git для локальной работы, мы рассмотрим, как задействовать некоторые распределённые рабочие процессы, предлагаемые Git. В этой главе мы рассмотрим работу с Git в распределённой среде как в роли рядового разработчика, так и в роли системного интегратора. То есть вы научитесь успешно вносить свой код в проект, делая это как можно более просто и для вас, и для владельца проекта, а также научитесь тому, как сопровождать проекты, в которых участвует множество разработчиков. Распределённый рабочий процесс В отличие от централизованных систем контроля версий, распределённая природа Git позволяет более гибко взаимодействовать разработчикам в рамках проекта. В централизованных системах каждый разработчик представляет собой узел, который более или менее одинаково взаимодействует с центральным хабом. Однако, в Git каждый разработчик это и узел и хаб, то есть каждый разработчик может как отправлять код в другие репозитории, так и поддерживать публичный репозиторий, в который другие разработчики смогут отправлять свой код, взяв его за основу. Это предоставляет огромное количество вариаций для организации рабочего процесса над проектом и/или для команды, поэтому мы расскажем об основных парадигмах, отражающих преимущество гибкости Git. Так же мы рассмотрим сильные и слабые стороны каждой из них; вы сможете выбрать наиболее подходящую или позаимствовать необходимые функции сразу из нескольких. Централизованная работа В централизованных системах, как правило, присутствует только одна модель взаимодействия — централизованный рабочий процесс. Центральный хаб или репозиторий может принимать код, а все остальные синхронизируют свою работу с ним. Все разработчики являются узлами (пользователями хаба) и синхронизируются только с ним. Рисунок 53. Централизованный рабочий процесс Это означает, что если два разработчика клонируют репозиторий и каждый внесёт изменения, то первый из них сможет отправить свои изменения в репозиторий без проблем. Второй разработчик должен слить изменения, сделанные первым разработчиком, чтобы избежать их перезаписи во время отправки на сервер. Эта концепция верна как для Git, так и для Subversion (или любой другой централизованной системы контроля версий), и прекрасно работает в Git. Если в вашей организации или команде уже используется централизованный рабочий процесс, то вам ничего не нужно менять для работы с Git. Достаточно создать один репозиторий и предоставить каждому члену команды push-доступ; Git не позволит перезаписать изменения, сделанные другими. Предположим, Джон и Джессика начинают работать над проектом одновременно. Джон вносит изменения и отправляет их на сервер. Затем Джессика пытается отправить свои изменения, но сервер их отклоняет. Ей говорят, что она пытается отправить изменения, для которых невозможно выполнить быструю перемотку и она не сможет это сделать пока не получит все новые для неё изменения и не сольёт их. Такой рабочий процесс привлекает большинство людей, так как реализует парадигму, с которой они уже знакомы. Такой подход применим не только к небольшим командам. Используя модель ветвления Git, сотни разработчиков могут одновременно работать над одним проектом, используя при этом десятки веток. Диспетчер интеграции Так как Git допускает использование нескольких удалённых репозиториев, то становится возможным организация рабочего процесса, где каждый разработчик имеет доступ на запись в свой публичный репозиторий и доступ на чтение ко всем остальным. При таком сценарии обычно существует канонический репозиторий, который представляет собой «официальный» проект. Для отправки своих наработок в этот проект следует создать его клон и отправить изменения в него. Затем вы отправляете запрос на слияние ваших изменений сопровождающему основного проекта. В свою очередь он может добавить ваш репозиторий как удалённый, протестировать ваши изменения локально, слить их в соответствующую ветку и отправить в основной репозиторий. Процесс работает в следующей последовательности (смотри Рабочий процесс с менеджером по интеграции ): Сопровождающий проекта отправляет изменения в свой публичный репозиторий. Участник клонирует этот репозиторий и вносит изменения. Участник отправляет свои изменения в свой публичный репозиторий. Участник отправляет письмо сопровождающему с запросом на слияние изменений. Сопровождающий добавляет репозиторий участника как удалённый и сливает изменения локально. Сопровождающий отправляет слитые изменения в основной репозиторий. Рисунок 54. Рабочий процесс с менеджером по интеграции Это достаточно распространённый вид организации рабочего процесса, в котором используются хабы, такие как GitHub или GitLab, где легко создать свой репозиторий как ответвление проекта (fork) и отправить туда свои изменения. Одним из основных преимуществ этого подхода является то, что вы можете продолжать работать, а сопровождающий основного репозитория может слить ваши изменения в любое время. Участники не должны ждать пока основной проект примет их изменения — каждый может работать в своём темпе. Диктатор и помощники Это вариант организации рабочего процесса с использованием нескольких репозиториев. В основном такой подход используется на огромных проектах, насчитывающих сотни участников; самый известный пример — ядро Linux. Помощники (lieutenants) — это интеграционные менеджеры, которые отвечают за отдельные части репозитория. Над ними главенствует один диспетчер интеграции, которого называют великодушным диктатором. Репозиторий доброжелательного диктатора выступает как эталонный (blessed), откуда все участники процесса должны получать изменения. Процесс работает следующим образом (смотри Рабочий процесс с великодушным диктатором ): Обычные разработчики работают в своих тематических ветках и перебазируют свою работу относительно ветки master . Ветка master — это ветка эталонного репозитория в которую имеет доступ только диктатор. Помощники сливают тематические ветки разработчиков в свои ветки master . Диктатор сливает ветки master помощников в свою ветку master . Наконец, диктатор отправляет свою ветку master в эталонный репозиторий, чтобы все остальные могли перебазировать свою работу на основании неё. Рисунок 55. Рабочий процесс с великодушным диктатором Такой вид организации рабочего процесса не является обычным, но может быть применён к очень большим проектам или в сильно иерархической среде. Это позволяет лидеру проекта (диктатору) делегировать бóльшую часть работы и собирать большие подмножества кода в различных точках до того как они будут интегрированы. Шаблоны для управления ветками исходного кода Примечание Мартин Фаулер сделал руководство «Шаблоны для управления ветками исходного кода». Это руководство охватывает все стандартные рабочие процессы Git и объясняет, как и когда их использовать. Также есть раздел, в котором сравнивается высокая и низкая частота слияния. https://martinfowler.com/articles/branching-patterns.html Заключение Это наиболее часто используемые подходы в организации рабочего процесса на основании распределённых систем, таких как Git. Но, как вы можете видеть, существует множество различных решений для организации рабочего процесса в реальных проектах. Теперь, когда вы определились с комбинацией рабочих процессов, мы рассмотрим ряд более конкретных примеров как использовать основные роли в различных процессах. В следующем разделе вы узнаете о некоторых основных моделях, описывающих процесс участия в проекте. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/be/v2/Distributed-Git-Distributed-Workflows | Git - Distributed Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distributed Git - Distributed Workflows Now that you have a remote Git repository set up as a focal point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. Distributed Workflows In contrast with Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally with a central hub. In Git, however, every developer is potentially both a node and a hub; that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This presents a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model — the centralized workflow. One central hub, or repository , can accept code, and everyone synchronizes their work with it. A number of developers are nodes — consumers of that hub — and synchronize with that centralized location. Малюнак 53. Centralized workflow This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. Integration-Manager Workflow Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an email asking them to pull changes. The maintainer adds the contributor’s repository as a remote and merges locally. The maintainer pushes merged changes to the main repository. Малюнак 54. Integration-manager workflow This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes — each party can work at their own pace. Dictator and Lieutenants Workflow This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants . All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator pushes from their directory to a reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the reference repository to which the dictator pushes. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. Finally, the dictator pushes that master branch to the reference repository so the other developers can rebase on it. Малюнак 55. Benevolent dictator workflow This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. Patterns for Managing Source Code Branches Заўвага Martin Fowler has made a guide "Patterns for Managing Source Code Branches". This guide covers all the common Git workflows, and explains how/when to use them. There’s also a section comparing high and low integration frequencies. https://martinfowler.com/articles/branching-patterns.html Workflows Summary These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://support.microsoft.com/en-us/topic/viva-learning-overview-01bfed12-c327-41e0-a68f-7fa527dcc98a | Viva Learning Overview - Microsoft Support Related topics × Viva Learning Get started Viva Learning Viva Learning mobile app Social learning Discover learning content Personal learning Recommend and manage content Take action Progress tracking in Viva Learning Archive in-progress courses Archive recommended courses Learning content Add link to content Create a Learning Collection Accessibility in Viva Learning Privacy in Viva Learning Security in Viva Learning Service terms Skip to main content Microsoft Support Support Support Home Microsoft 365 Office Products Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows more ... Devices Surface PC Accessories Xbox PC Gaming HoloLens Surface Hub Hardware warranties Account & billing Account Microsoft Store & billing Resources What's new Community forums Microsoft 365 Admins Small Business Portal Developer Education Report a support scam Product safety More Buy Microsoft 365 All Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Deals Small Business Support Software Software Windows Apps AI Outlook OneDrive Microsoft Teams OneNote Microsoft Edge Moving from Skype to Teams PCs & Devices PCs & Devices Computers Shop Xbox Accessories VR & mixed reality Certified Refurbished Trade-in for cash Entertainment Entertainment Xbox Game Pass Ultimate PC Game Pass Xbox games PC games Business Business Microsoft Security Dynamics 365 Microsoft 365 for business Microsoft Power Platform Windows 365 Microsoft Industry Small Business Developer & IT Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Other Other Microsoft Rewards Free downloads & security Education Gift cards Licensing Unlocked stories View Sitemap Search Search for help No results Cancel Sign in Sign in with Microsoft Sign in or create an account. Hello, Select a different account. You have multiple accounts Choose the account you want to sign in with. Related topics Viva Learning Get started Viva Learning Viva Learning mobile app Social learning Discover learning content Personal learning Recommend and manage content Take action Progress tracking in Viva Learning Archive in-progress courses Archive recommended courses Learning content Add link to content Create a Learning Collection Accessibility in Viva Learning Privacy in Viva Learning Security in Viva Learning Service terms Viva Learning Overview Microsoft Viva Learning Microsoft Viva Learning is your central hub for learning in Teams where you can share, recommend, and learn from content libraries across an organization to empower teams and individuals to make learning a natural part of your day. This includes access to content libraries from LinkedIn Learning, Microsoft Learn, Microsoft 365 Training, and third-party content providers and learning management systems, as well as content your company adds to Viva Learning. Viva Learning in Teams, on the web, on your mobile device Viva Learning in Teams Launch Teams on your desktop device. Select More (...) from the bottom right corner, then select Viva Learning . Viva Learning on the web Viva Learning is accessible at https://aka.ms/VivaLearningWeb. This web endpoint provides all the features available in the Viva Learning app for Teams. The web app auto signs you into your Viva Learning account and personalizes the experience by adapting to preferred theme and language settings. The web app is currently compatible with Microsoft Edge, Google Chrome and in preview in Safari. Viva Learning mobile app Viva Learning mobile app lets you make learning a part of your day, even when you are on the go. Download Teams for your iOS or Android device. Open Teams mobile. Tap More (...) from the bottom right corner, then select Viva Learning . Note: If you don't see Viva Learning in Microsoft Teams, it might be disabled by your organization. Contact your admin for more information. Start using Viva Learning See how to start using the Viva Learning app and learn about key features by watching the tour that launches when you open the app for the first time. You'll see pop-up text bubbles (or “coach marks”) like the one below each time you visit a Viva Learning page the first time. These coach marks will help you learn about different features to get the most value out of the Viva Learning app. Select < or > to navigate through the coach marks. If you want to take the tour later, select the ellipses ( ... ) in the upper right corner of the app. Then choose Show me around to access the tour at any time. Connect and learn from experts and peers Join the discussion and see the latest events in the Viva Learning Community . Learn more Social learning Personal learning Recommend and manage content Search for learning content Need more help? Want more options? Discover Community Explore subscription benefits, browse training courses, learn how to secure your device, and more. Microsoft 365 subscription benefits Microsoft 365 training Microsoft security Accessibility center Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge. Ask the Microsoft Community Microsoft Tech Community Windows Insiders Microsoft 365 Insiders Was this information helpful? Yes No Thank you! Any more feedback for Microsoft? Can you help us improve? (Send feedback to Microsoft so we can help.) What affected your experience? Resolved my issue Clear instructions Easy to follow No jargon Pictures helped Other Didn't match my screen Incorrect instructions Too technical Not enough information Not enough pictures Other Any additional feedback? (Optional) Submit feedback By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement. Thank you for your feedback! × What's new Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organizations Copilot for personal use AI in Windows Explore Microsoft products Windows 11 apps Microsoft Store Account profile Download Center Microsoft Store support Returns Order tracking Certified Refurbished Microsoft Store Promise Flexible Payments Education Microsoft in education Devices for education Microsoft Teams for Education Microsoft 365 Education How to buy for your school Educator training and development Deals for students and parents AI for education Business Microsoft Security Dynamics 365 Microsoft 365 Microsoft Power Platform Microsoft Teams Microsoft 365 Copilot Small Business Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Company Careers About Microsoft Company news Privacy at Microsoft Investors Diversity and inclusion Accessibility Sustainability English (United States) Your Privacy Choices Opt-Out Icon Your Privacy Choices Your Privacy Choices Opt-Out Icon Your Privacy Choices Consumer Health Privacy Sitemap Contact Microsoft Privacy Manage cookies Terms of use Trademarks Safety & eco Recycling About our ads © Microsoft 2026 | 2026-01-13T09:29:41 |
https://support.microsoft.com/lt-lt/office/kas-yra-pamainos-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Kas yra Pamainos? - „Microsoft“ palaikymas Susijusios temos × „Microsoft Teams“ vaizdo mokymai „Microsoft Teams“ komandų greitas pasirengimas darbui Kas yra „Microsoft Teams“? Prisijungimas ir darbo pradžia Pokalbiai ir failų bendrinimas Bendradarbiavimas Sužinokite daugiau Įvadas į „Microsoft Teams“ Pradėkite naudoti „Microsoft Teams“ Darbo su pokalbiais pradžia Darbo su susitikimais pradžia Darbo su programomis pradžia Komandos nustatymas ir tinkinimas Komandos su maketais kūrimas Darbas su išoriniais svečiais Komandos parametrų valdymas Bendradarbiavimas komandose ir kanaluose Patarimas: išsiųskite el. laišką į kanalą Plano kūrimas naudojant „Planner“ Darbas su pranešimais ir žinutėmis Skelbti pranešimą keliuose kanaluose Failų ieška ir radimas Failų nusiuntimas ir bendrinimas Žmonių ir failų ieška ir filtravimas El. laiškų ieška ir filtravimas „Teams" failų patarimai Pokalbių pradėjimas ir skambinimas „Teams“ skambučių apžvalga Skambinti „Teams“ skambučių patarimai Slėpti pokalbius ir naikinti pranešimus Atstovo, priimančio jūsų skambučius, nustatymas Susitikimų valdymas Prisijungimas prie „Teams“ susitikimo „Teams“ susitikimų patarimai Iškart susitikite Susitikimų valdymas Internetinio seminaro planavimas Rodykite savo ekraną, kol esate susitikime. Tiesioginių įvykių nustatymas ir dalyvavimas juose Tiesioginio įvykio planavimas Tiesioginio įvykio kūrimas Dalyvavimas tiesioginiame įvykyje Klausimų ir atsakymų moderavimas Plačiau apie programas ir įrankius Programų radimas ir naudojimas Komandų grafikų valdymas su „Shifts“ Kas yra Pamainos? Pamainų tvarkaraščių kūrimas Pamainų tvarkaraščių valdymas Patvirtinimų kūrimas Kas yra patvirtinimai? Patvirtinimo kūrimas Patvirtinimo kūrimas iš pokalbio Patvirtinimo el. parašu kūrimas Atraskite šablonus patvirtinimuose Kurkite patvirtinimus naudodami šablonus Organizacijos šablonų kūrimas Virtualūs susitikimai programoje „Microsoft Bookings“ Kas yra virtualūs susitikimai? Siųskite išoriniams svečiams SMS teksto pranešimus Susitikimo vykdymas Prisijungti prie susitikimo Veiklos informacijos santraukos tvarkymas Pranešimų parametrų tvarkymas „Teams“ keliaujant Pradėkite pokalbį keliaudami Sukurkite kanalą keliaujant Prisijungimas prie susitikimo išvykus Veiklos informacijos santrauka išvykus Pereiti prie pagrindinio turinio Microsoft Palaikymas Palaikymas Palaikymas Pagrindinis Microsoft 365 Office „Teams“ palaikymas Temos Susitikimai Pokalbis Pranešimai & parametrai Teams“ ir kanalai Skambučiai & įrenginiai Failai Programos & paslaugos Sparčioji pradžia Pokalbis Grupės pokalbis Pranešimai Teams Kanalai Skambučiai Failai Programos „Loop“ komponentai Kas nauja Ištekliai Mokomasis vaizdo įrašas Trikčių šalinimas Čia, „Teams“ Pritaikymas neįgaliesiems „Teams“ funkcijos pagal platformą „Microsoft Teams“ (nemokama versija) Bendruomenės forumai Technologijų bendruomenės tinklaraštis Instruktoriaus vedamasis mokymas Administratoriams ir IT specialistams Švietimui Daugiau Įsigyti „Microsoft 365“ Viskas „Microsoft“ Global Microsoft 365 Teams Copilot Windows Surface Xbox Palaikymas Programinė įranga Programinė įranga „Windows“ programėlės DI „OneDrive“ Outlook „OneNote“ „Microsoft Teams“ Kompiuteriai ir įrenginiai Kompiuteriai ir įrenginiai Accessories Pramogos Pramogos Kompiuteriniai žaidimai Verslui Verslui „Microsoft“ sauga „Azure” „Dynamics 365“ „Microsoft 365“ verslui „Microsoft“ pramonei „Microsoft Power Platform“ Windows 365 Kūrėjas ir IT Kūrėjas ir IT „Microsoft“ kūrėjas „Microsoft Learn“ DI parduotuvės programų palaikymas „Microsoft“ techninės pagalbos bendruomenė Microsoft Marketplace „Visual Studio“ Marketplace Rewards Kiti Kiti Nemokami atsisiuntimai ir sauga Rodyti svetainės struktūrą Ieškoti Ieškoti žinyno Rezultatų nėra Atšaukti Prisijungti Prisijunkite prie „Microsoft“ Prisijunkite arba sukurkite paskyrą. Sveiki, Pasirinkti kitą paskyrą. Turite kelias paskyras Pasirinkite paskyrą, kurią naudodami norite prisijungti. Susijusios temos „Microsoft Teams“ vaizdo mokymai „Microsoft Teams“ komandų greitas pasirengimas darbui Kas yra „Microsoft Teams“? Prisijungimas ir darbo pradžia Pokalbiai ir failų bendrinimas Bendradarbiavimas Sužinokite daugiau Įvadas į „Microsoft Teams“ Pradėkite naudoti „Microsoft Teams“ Darbo su pokalbiais pradžia Darbo su susitikimais pradžia Darbo su programomis pradžia Komandos nustatymas ir tinkinimas Komandos su maketais kūrimas Darbas su išoriniais svečiais Komandos parametrų valdymas Bendradarbiavimas komandose ir kanaluose Patarimas: išsiųskite el. laišką į kanalą Plano kūrimas naudojant „Planner“ Darbas su pranešimais ir žinutėmis Skelbti pranešimą keliuose kanaluose Failų ieška ir radimas Failų nusiuntimas ir bendrinimas Žmonių ir failų ieška ir filtravimas El. laiškų ieška ir filtravimas „Teams" failų patarimai Pokalbių pradėjimas ir skambinimas „Teams“ skambučių apžvalga Skambinti „Teams“ skambučių patarimai Slėpti pokalbius ir naikinti pranešimus Atstovo, priimančio jūsų skambučius, nustatymas Susitikimų valdymas Prisijungimas prie „Teams“ susitikimo „Teams“ susitikimų patarimai Iškart susitikite Susitikimų valdymas Internetinio seminaro planavimas Rodykite savo ekraną, kol esate susitikime. Tiesioginių įvykių nustatymas ir dalyvavimas juose Tiesioginio įvykio planavimas Tiesioginio įvykio kūrimas Dalyvavimas tiesioginiame įvykyje Klausimų ir atsakymų moderavimas Plačiau apie programas ir įrankius Programų radimas ir naudojimas Komandų grafikų valdymas su „Shifts“ Kas yra Pamainos? Pamainų tvarkaraščių kūrimas Pamainų tvarkaraščių valdymas Patvirtinimų kūrimas Kas yra patvirtinimai? Patvirtinimo kūrimas Patvirtinimo kūrimas iš pokalbio Patvirtinimo el. parašu kūrimas Atraskite šablonus patvirtinimuose Kurkite patvirtinimus naudodami šablonus Organizacijos šablonų kūrimas Virtualūs susitikimai programoje „Microsoft Bookings“ Kas yra virtualūs susitikimai? Siųskite išoriniams svečiams SMS teksto pranešimus Susitikimo vykdymas Prisijungti prie susitikimo Veiklos informacijos santraukos tvarkymas Pranešimų parametrų tvarkymas „Teams“ keliaujant Pradėkite pokalbį keliaudami Sukurkite kanalą keliaujant Prisijungimas prie susitikimo išvykus Veiklos informacijos santrauka išvykus Kas yra Pamainos? Taikoma Teams Microsoft Teams Išbandykite! "Microsoft Teams" programa Pamainos yra tvarkaraščių valdymo ir laiko sekimo įrankis, padedantis kurti, naujinti ir valdyti komandos tvarkaraščius. Tvarkaraščiai – kurkite, redaguokite ir valdykite komandos tvarkaraštį. Pamainų tvarkaraštis rodo dienas viršuje, komandos nariai rodomi kairėje, o priskirtos pamainos rodomos kalendoriuje. Tvarkaraščio parametrai – "Shift" parametruose apibrėžkite tvarkaraščio parinktis ir pasirinkite pamainų galimybes, kurias norite padaryti pasiekiamas komandai. Grupės – įtraukite tvarkaraščio grupes, kad tvarkytumėte komandos narius pagal užduoties tipą arba vietą. Pamainos – priskirti pamainas komandos nariams. Kurti pamainą nuo pradžių arba kopijuoti esamą. Atidaryti pamainas – kiekvienoje tvarkaraščio grupėje yra eilutė Atidaryti pamainos . Įtraukite atidarytus pamainas į savo tvarkaraštį, kad kiekvienas galėtų pateikti užklausą. Laiko laikrodis – įjunkite laiko laikrodį "Shift" parametruose, kad komanda galėtų įjungti ir išjungti pamainas. Užklausos – peržiūrėkite ir atsakykite į prašymus dėl išjungimo, atvirų pamainų, pamainų sukeitimų ir pasiūlymų. Žymės – naudokite permainomis pagrįstas žymes, kad greitai susisiektumėte su bet kuo, kas šiuo metu pamainoje. Publikuokite tvarkaraštį – kai baigsite keisti tvarkaraštį, bendrinkite jį su savo komanda, kad visi būtų atnaujinti. Norite daugiau? Pradėkite naudoti Pamainos Komandos tvarkaraščio kūrimas naudojant pamainas Pamainų įtraukimas į tvarkaraštį naudojant pamainas Publikuoti tvarkaraštį naudojant pamainas Valdyti pamainų užklausas ir išjungimo laiką pamainose Permainomis pagrįstų žymių įjungimas programoje "Teams" UŽSISAKYTI RSS INFORMACIJOS SANTRAUKAS Reikia daugiau pagalbos? Norite daugiau parinkčių? Galimos funkcijos Bendruomenė Sužinokite apie prenumeratos pranašumus, peržiūrėkite mokymo kursus, sužinokite, kaip apsaugoti savo įrenginį ir kt. „Microsoft 365“ prenumeratos pranašumai „Microsoft 365“ mokymas „Microsoft“ sauga Pritaikymo neįgaliesiems centras Bendruomenės padeda užduoti klausimus ir į juos atsakyti, pateikti atsiliepimų ir išgirsti iš ekspertų, turinčių daug žinių. Klauskite „Microsoft“ bendruomenės „Microsoft“ technologijų bendruomenė „Windows Insider Preview“ programos dalyviai „Microsoft 365“ „Insider“ programos dalyviai Ar ši informacija buvo naudinga? Taip Ne Ačiū! Turite daugiau atsiliepimų apie „Microsoft“? Ar galite padėti mums tobulėti? (Siųskite atsiliepimą „Microsoft“, kad galėtume jums padėti.) Ar esate patenkinti kalbos kokybe? Kas turėjo įtakos jūsų įspūdžiams? Išsprendė mano problemą Valyti instrukcijas Lengva vykdyti Nėra žargono Nuotraukos padėjo Vertimo kokybė Neatitiko mano ekrano Neteisingos instrukcijos Per daug techniška Nepakanka informacijos Nepakanka paveikslėlių Vertimo kokybė Turite daugiau atsiliepimų? (Pasirinktinai) Pateikti atsiliepimą Paspaudus mygtuką Pateikti, jūsų atsiliepimai bus naudojami tobulinant „Microsoft“ produktus ir paslaugas. Jūsų IT administratorius galės rinkti šiuos duomenis. Privatumo patvirtinimas. Dėkojame už jūsų atsiliepimą! × Kas nauja Organizacijoms skirtas „Copilot“ Asmeniniam naudojimui skirtas „Copilot“ Microsoft 365 „Windows 11“ programos Microsoft Store Abonento profilis Atsisiuntimo centras Grąžinimas Užsakymo sekimas Perdirbimas Komercinės garantijos Švietimas „Microsoft Education“ Įrenginiai švietimo įstaigoms „Microsoft Teams“ švietimui „Microsoft 365 Education“ „Office Education“ Pedagogų mokymai ir tobulėjimas Pasiūlymai studentams ir tėvams „Azure“ studentams Verslas „Microsoft“ sauga „Azure” „Dynamics 365“ „Microsoft 365“ „Microsoft Advertising“ Microsoft 365 Copilot „Microsoft Teams“ Kūrėjas ir IT „Microsoft“ kūrėjas „Microsoft Learn“ DI parduotuvės programų palaikymas „Microsoft“ techninės pagalbos bendruomenė Microsoft Marketplace „Microsoft Power Platform“ Marketplace Rewards „Visual Studio“ Įmonė Karjera Apie „Microsoft“ „Microsoft“ privatumas Investuotojai Tvarumas Lietuvių (Lietuva) Jūsų privatumo pasirinkimų atsisakymo piktograma Jūsų privatumo pasirinkimai Jūsų privatumo pasirinkimų atsisakymo piktograma Jūsų privatumo pasirinkimai Vartotojų sveikatos privatumas Susisiekti su „Microsoft“ Privatumas Slapukų valdymas Naudojimosi sąlygos Prekių ženklai Apie mūsų reklamą EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/es/v2/Ramificaciones-en-Git-Flujos-de-Trabajo-Ramificados | Git - Flujos de Trabajo Ramificados About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 3.4 Ramificaciones en Git - Flujos de Trabajo Ramificados Flujos de Trabajo Ramificados Ahora que ya has visto los procedimientos básicos de ramificación y fusión, ¿qué puedes o qué debes hacer con ellos? En este apartado vamos a ver algunos de los flujos de trabajo más comunes, de tal forma que puedas decidir si te gustaría incorporar alguno de ellos a tu ciclo de desarrollo. Ramas de Largo Recorrido Por la sencillez de la fusión a tres bandas de Git, el fusionar una rama a otra varias veces a lo largo del tiempo es fácil de hacer. Esto te posibilita tener varias ramas siempre abiertas, e irlas usando en diferentes etapas del ciclo de desarrollo; realizando fusiones frecuentes entre ellas. Muchos desarrolladores que usan Git llevan un flujo de trabajo de esta naturaleza, manteniendo en la rama master únicamente el código totalmente estable (el código que ha sido o que va a ser liberado) y teniendo otras ramas paralelas denominadas desarrollo o siguiente , en las que trabajan y realizan pruebas. Estas ramas paralelas no suelen estar siempre en un estado estable; pero cada vez que sí lo están, pueden ser fusionadas con la rama master . También es habitual el incorporarle (pull) ramas puntuales (ramas temporales, como la rama iss53 del ejemplo anterior) cuando las completamos y estamos seguros de que no van a introducir errores. En realidad, en todo momento estamos hablando simplemente de apuntadores moviéndose por la línea temporal de confirmaciones de cambio (commit history). Las ramas estables apuntan hacia posiciones más antiguas en el historial de confirmaciones, mientras que las ramas avanzadas, las que van abriendo camino, apuntan hacia posiciones más recientes. Figura 26. Una vista lineal del ramificado progresivo estable Podría ser más sencillo pensar en las ramas como si fueran silos de almacenamiento, donde grupos de confirmaciones de cambio (commits) van siendo promocionados hacia silos más estables a medida que son probados y depurados. Figura 27. Una vista tipo “silo” del ramificado progresivo estable Este sistema de trabajo se puede ampliar para diversos grados de estabilidad. Algunos proyectos muy grandes suelen tener una rama denominada propuestas o pu (del inglés “proposed updates”, propuesta de actualización), donde suele estar todo aquello que es integrado desde otras ramas, pero que aún no está listo para ser incorporado a las ramas siguiente o master . La idea es mantener siempre diversas ramas en diversos grados de estabilidad; pero cuando alguna alcanza un estado más estable, la fusionamos con la rama inmediatamente superior a ella. Aunque no es obligatorio el trabajar con ramas de larga duración, realmente es práctico y útil, sobre todo en proyectos largos o complejos. Ramas Puntuales Las ramas puntuales, en cambio, son útiles en proyectos de cualquier tamaño. Una rama puntual es aquella rama de corta duración que abres para un tema o para una funcionalidad determinada. Es algo que nunca habrías hecho en otro sistema VCS, debido a los altos costos de crear y fusionar ramas en esos sistemas. Pero en Git, por el contrario, es muy habitual el crear, trabajar con, fusionar y eliminar ramas varias veces al día. Tal y como has visto con las ramas iss53 y hotfix que has creado en la sección anterior. Has hecho algunas confirmaciones de cambio en ellas, y luego las has borrado tras fusionarlas con la rama principal. Esta técnica te posibilita realizar cambios de contexto rápidos y completos y, debido a que el trabajo está claramente separado en silos, con todos los cambios de cada tema en su propia rama, te será mucho más sencillo revisar el código y seguir su evolución. Puedes mantener los cambios ahí durante minutos, días o meses; y fusionarlos cuando realmente estén listos, sin importar el orden en el que fueron creados o en el que comenzaste a trabajar en ellos. Por ejemplo, puedes realizar cierto trabajo en la rama master , ramificar para un problema concreto (rama iss91 ), trabajar en él un rato, ramificar una segunda vez para probar otra manera de resolverlo (rama iss92v2 ), volver a la rama master y trabajar un poco más, y, por último, ramificar temporalmente para probar algo de lo que no estás seguro (rama dumbidea ). El historial de confirmaciones (commit history) será algo parecido esto: Figura 28. Múltiples ramas puntuales En este momento, supongamos que te decides por la segunda solución al problema (rama iss92v2 ); y que, tras mostrar la rama dumbidea a tus compañeros, resulta que les parece una idea genial. Puedes descartar la rama iss91 (perdiendo las confirmaciones C5 y C6), y fusionar las otras dos. El historial será algo parecido a esto: Figura 29. El historial tras fusionar dumbidea e iss91v2 Hablaremos un poco más sobre los distintos flujos de trabajo de tu proyecto Git en Git en entornos distribuidos , así que antes de decidir qué estilo de ramificación usará tu próximo proyecto, asegúrate de haber leído ese capítulo. Es importante recordar que, mientras estás haciendo todo esto, todas las ramas son completamente locales. Cuando ramificas y fusionas, todo se realiza en tu propio repositorio Git. No hay ningún tipo de comunicación con ningún servidor. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/fa/v2/%d8%a7%d9%86%d8%b4%d8%b9%d8%a7%d8%a8%e2%80%8c%da%af%db%8c%d8%b1%db%8c-%d8%af%d8%b1-%da%af%db%8c%d8%aa-Git-Branching-%d8%b1%d9%88%d9%86%d8%af%d9%87%d8%a7%db%8c-%da%a9%d8%a7%d8%b1%db%8c-%d8%b4%d8%a7%d8%ae%d9%87%e2%80%8c%d9%87%d8%a7-Branching-Workflows | Git - روندهای کاری شاخهها (Branching Workflows) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 3.4 انشعابگیری در گیت (Git Branching) - روندهای کاری شاخهها (Branching Workflows) روندهای کاری شاخهها (Branching Workflows) حالا که اصول پایهای شاخهزنی و ادغام را یاد گرفتهاید، چه کارهایی میتوانید یا باید با آنها انجام دهید؟ در این بخش، به برخی جریانهای کاری رایجی که این شاخهزنی سبکوزن امکانپذیر میکند، میپردازیم تا بتوانید تصمیم بگیرید آیا مایلید آنها را در چرخه توسعه خود به کار ببرید یا خیر. شاخههای بلندمدت (Long-Running Branches) از آنجا که گیت از ادغام سهطرفه ساده استفاده میکند، ادغام مکرر از یک شاخه به شاخهای دیگر در طول زمان معمولاً کار آسانی است. این بدین معناست که میتوانید چندین شاخه همیشه باز داشته باشید که برای مراحل مختلف چرخه توسعه خود از آنها استفاده میکنید؛ میتوانید بهطور مرتب از برخی شاخهها به شاخههای دیگر ادغام انجام دهید. بسیاری از توسعهدهندگان گیت دارای جریانی کاری هستند که این رویکرد را در بر میگیرد، مثلاً شاخه master آنها فقط شامل کدی است که کاملاً پایدار است — احتمالاً تنها کدی که منتشر شده یا قرار است منتشر شود. آنها شاخه موازی دیگری به نام develop یا next دارند که از آنجا کار میکنند یا برای تست پایداری استفاده میکنند — لزوماً همیشه پایدار نیست، اما هرگاه به وضعیت پایداری برسد، میتوان آن را به master ادغام کرد. این شاخه برای جذب شاخههای موضوعی (شاخههای کوتاهمدت، مانند شاخه iss53 شما در گذشته) وقتی آماده هستند، استفاده میشود تا اطمینان حاصل شود که همه تستها را پاس میکنند و خطا وارد نمیکنند. در واقع، ما درباره اشارهگرهایی صحبت میکنیم که در خط کامیتهایی که ایجاد میکنید، به جلو حرکت میکنند. شاخههای پایدار در تاریخچه کامیتهای شما عقبتر هستند و شاخههای پیشرفتهتر در بالاتر تاریخچه قرار دارند. نمودار 26. A linear view of progressive-stability branching بهطور کلی، راحتتر است که آنها را به عنوان انبارهای کاری در نظر بگیرید، جایی که مجموعهای از کامیتها وقتی کاملاً تست میشوند، به انبار پایدارتر منتقل میشوند. نمودار 27. A “silo” view of progressive-stability branching میتوانید این روند را برای چندین سطح پایداری ادامه دهید. برخی پروژههای بزرگتر همچنین شاخهای به نام proposed یا pu (بهروزرسانیهای پیشنهادی) دارند که شاخههای ادغام شدهای در آن قرار دارد که ممکن است برای وارد شدن به شاخههای next یا master هنوز آماده نباشند. ایده این است که شاخههای شما در سطوح مختلفی از پایداری قرار دارند؛ هنگامی که به سطح پایداری بالاتری رسیدند، به شاخه بالاتر خود ادغام میشوند. دوباره، داشتن چند شاخه بلندمدت ضروری نیست، اما اغلب مفید است، بهویژه وقتی با پروژههای بسیار بزرگ یا پیچیده سر و کار دارید. شاخههای موضوعی (Topic Branches) با این حال، شاخههای موضوعی در پروژههایی با هر اندازهای مفید هستند. شاخه موضوعی یک شاخه کوتاهمدت است که شما برای یک ویژگی خاص یا کار مرتبط ایجاد و استفاده میکنید. این کاری است که احتمالاً قبلاً با یک سیستم کنترل نسخه انجام ندادهاید، زیرا معمولاً ایجاد و ادغام شاخهها هزینهبر است. اما در گیت، ایجاد، کار روی، ادغام و حذف شاخهها چندین بار در روز امری معمول است. شما این موضوع را در بخش قبلی با شاخههای iss53 و hotfix که ایجاد کردید دیدید. چند کامیت روی آنها انجام دادید و بلافاصله پس از ادغام آنها در شاخه اصلی، آنها را حذف کردید. این تکنیک به شما امکان میدهد سریع و کامل بین زمینهها جابجا شوید — چون کار شما به بخشهای جداگانهای تقسیم شده که همه تغییرات آن شاخه مربوط به همان موضوع است، دیدن آنچه در بازبینی کد اتفاق افتاده آسانتر است. شما میتوانید تغییرات را برای چند دقیقه، روز یا ماه نگه دارید و وقتی آماده شدند، آنها را ادغام کنید، بدون توجه به ترتیب ایجاد یا کار روی آنها. برای مثال، فرض کنید روی شاخه master کار میکنید، سپس برای یک مسئله شاخهای به نام iss91 ایجاد میکنید، کمی روی آن کار میکنید، سپس شاخه دوم iss91v2 را برای امتحان راه دیگری در همان مسئله ایجاد میکنید، به شاخه master بازمیگردید و مدتی روی آن کار میکنید، سپس شاخهای به نام dumbidea ایجاد میکنید برای کاری که مطمئن نیستید ایده خوبی باشد. تاریخچه کامیتهای شما چیزی شبیه به این خواهد بود: نمودار 28. Multiple topic branches حالا فرض کنید تصمیم میگیرید راهحل دوم برای مسئله (شاخه iss91v2 ) را بیشتر میپسندید؛ و شاخه dumbidea را به همکارانتان نشان میدهید و معلوم میشود ایدهای نابغهوار است. میتوانید شاخه اصلی iss91 را کنار بگذارید (و کامیتهای C5 و C6 را از دست بدهید) و دو شاخه دیگر را ادغام کنید. تاریخچه شما در آن صورت چنین خواهد بود: نمودار 29. History after merging dumbidea and iss91v2 ما در بخش گیت توزیعشده (Distributed git) به جزئیات بیشتری درباره جریانهای کاری مختلف پروژه گیت شما خواهیم پرداخت، پس قبل از اینکه تصمیم بگیرید کدام طرح شاخهبندی را برای پروژه بعدی خود استفاده کنید، حتماً آن فصل را مطالعه نمایید. مهم است که هنگام انجام همه این کارها به خاطر داشته باشید که این شاخهها کاملاً محلی هستند. وقتی شاخه میزنید و ادغام میکنید، همه کارها فقط در مخزن گیت شما انجام میشود — هیچ ارتباطی با سرور برقرار نمیشود. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/sl/v2/Porazdeljeni-Git-Porazdeljeni-poteki-dela | Git - Porazdeljeni poteki dela About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 5.1 Porazdeljeni Git - Porazdeljeni poteki dela Sedaj, ko imate oddaljeni repozitorij Git nastavljen kot točko za vse razvijalce, da delijo svojo kodo, in so vam poznani osnovni ukazi Git v lokalnem poteku dela, boste pogledali, kako uporabiti nekaj porazdeljenih potekov dela, ki vam jih ponuja Git. V tem poglavju boste spoznali, kako delati z Gitom v porazdeljenem okolju kot sodelavec in povezovalec. To pomeni, da se boste naučili, kako uspešno prispevati kodo projektu in to narediti, kar se da enostavno za vas in vzdrževalca projekta, ter kako uspešno vzdrževati projekt s številnimi razvijalci, ki prispevajo. Porazdeljeni poteki dela Z razliko od centraliziranih sistemov za nadzor različic (CVCS-ji), vam narava porazdelitve Gita omogoča, da ste veliko bolj prilagodljivi v tem, kako razvijalci sodelujejo na projektih. V centraliziranih sistemih je vsak razvijalec vozlišče, ki deluje več ali manj enako z osrednjim razdelilnikom. Vendar v Gitu je vsak razvijalec potencialno tako vozlišče kot razdelilnik; to pomeni, da lahko vsak razvijalec tako prispeva kodo k drugim repozitorijem, kot tudi vzdržuje javen repozitorij, na katerem lahko drugi osnujejo svoje delo in h kateremu lahko prispevajo. To odpira širok spekter zmožnosti poteka dela za vaš projekt in/ali vašo ekipo, torej bomo pokrili nekaj pogostih paradigem, ki izkoriščajo to prilagodljivost. Šli bomo skozi prednosti in možne slabosti vsakega modela; za uporabo lahko izberete kateregakoli ali pa jih mešate in vzamete lastnosti iz vsakega. Centraliziran potek dela V centraliziranih sistemih je v splošnem en model sodelovanja — centralizirani potek dela. En osrednji razdelilnik ali repozitorij lahko sprejme kodo in vsakdo sinhronizira svoje delo z njim. Število razvijalcev so vozlišča — uporabniki tega razdelilnika — in sinhronizirajo s to osrednjo lokacijo. Slika 53. Centralizirani potek dela To pomeni, da če dva razvijalca klonirata iz razdelilnika in oba naredita spremembe, bo prvi razvijalec, ki potisne svoje spremembe nazaj gor, lahko to naredil brez težav. Drugi razvijalec mora združiti delo prvega, preden potisne spremembe gor, tako da ne prepiše sprememb prvega razvijalca. Ta zasnova je veljavna tako v Gitu kot tudi v Subversionu (ali kateremkoli drugem CVCS-ju) in ta model deluje v Gitu odlično. Če ste že domači s centraliziranim potekom dela v svojem podjetju ali ekipi, lahko enostavno nadaljujete z uporabo tega poteka dela v Gitu. Enostavno nastavite repozitorij in daste vsakomur v svoji ekipi dostop potiskanja; Git ne bo dovolil uporabnikom prepisati drug drugega. Recimo, da John in Jessica oba začneta delati istočasno. John konča svoje spremembe in jih potisne na strežnik. Nato poskuša Jessica potisniti svoje spremembe, vendar jih strežnik zavrne. Povedano ji je, da poskuša potisniti t. i. spremembe »brez hitrega previjanja naprej« (angl. non-fast-forward ) in da tega ne bo mogla napraviti, dokler ne prenese in združi. Ta potek dela je zanimiv za veliko ljudi, ker je paradigma, s katero so mnogi seznanjeni in domači. To tudi ni omejeno na majhne ekipe. Z modelom razvejanja Git je možno, da na stotine razvijalcev uspešno dela na istem projektu skozi ducat vej istočasno. Potek dela s povezovalnim upraviteljem Ker vam Git omogoča imeti več oddaljenih repozitorijev, je možno imeti potek dela, kjer ima vsak razvijalec dostop za pisanje na svojem lastnem javnem repozitoriju in dostop za branje na vseh ostalih. Ta scenarij pogostokrat vključuje kanonični repozitorij, ki predstavlja »uradni« projekt. Da prispevate temu projektu, ustvarite svoj lastni javni klon projekta in vanj potisnete svoje spremembe. Nato lahko vzdrževalcu glavnega projekta pošljete zahtevek, da povleče vaše spremembe. Vzdrževalec lahko nato doda vaš repozitorij kot daljavo, testira vaše spremembe lokalno, jih združi v svojo vejo in potisne nazaj v svoj repozitorij. Proces deluje naslednje (glejte sliko Potek dela s povezovalnim upraviteljem ): Vzdrževalec projekta potisne v svoj javni repozitorij. Sodelavec klonira ta repozitorij in naredi spremembe. Sodelavec potisne v svojo lastno kopijo. Sodelavec pošlje vzdrževalcu e-pošto, kjer ga prosi, da povleče spremembe. Vzdrževalec doda repozitorij sodelavca kot daljavo in združi lokalno. Vzdrževalec potisne združene spremembe v glavni repozitorij. Slika 54. Potek dela s povezovalnim upraviteljem To je zelo pogost potek dela z orodji, ki so osnovana na razdelilnikih, kot sta GitHub ali GitLab, kjer je enostavno razvejiti (angl. fork ) projekt in potisniti vaše spremembe v vašo razvejitev, da jih vsakdo vidi. Ena glavnih prednosti tega pristopa je, da lahko nadaljujete delo in vzdrževalec glavnega repozitorija lahko kadarkoli povleče vaše spremembe. Sodelavcem ni treba čakati, da projekt vključi njihove spremembe — vsaka stran lahko dela po svojem lastnem ritmu. Potek dela z diktatorji in poročniki To je različica poteka dela z več repozitoriji. V splošnem je uporabljena na velikih projektih s stotinami sodelavcev; eden znanih primerov je jedro Linux. Različni upravitelji integracij so zadolženi za določene dele repozitorija; imenujejo se poročniki . Vsi poročniki imajo enega upravitelja integracije znanega kot dobronamerni diktator. Dobronamerni diktator potisne iz svojega direktorija na referenčni repozitorij, iz katerega morajo vsi sodelavci povleči. Proces deluje takole (glejte sliko Potek dela z dobronamernim diktatorjem ): Splošni razvijalci delajo na svojih tematskih vejah in ponovno bazirajo svoje delo glede na master . Veja master je veja referenčnega repozitorija, na katerega diktator potiska. Poročniki združijo razvijalčeve tematske veje v svojo vejo master . Diktator združi poročnikove veje master v diktatorjevo vejo master . Diktator potisne to vejo master v referenčni repozitorij, da lahko ostali razvijalci ponovno bazirajo na njem. Slika 55. Potek dela z dobronamernim diktatorjem Taka vrsta poteka dela ni pogosta, vendar je lahko uporabna v zelo velikih projektih ali v visoko hierarhičnih okoljih. Vodji projekta (diktatorju) omogoča delegirati večino dela in zbrati velike skupke kode na več točkah, preden jih integrira. Vzorci za upravljanje vej izvorne kode Opomba Martin Fowler je ustvaril vodnik »Patterns for Managing Source Code Branches«. Ta vodnik pokriva vse pogoste poteke dela Git in jih razloži, kako in kdaj jih uporabiti. Na voljo je tudi razdelek, ki primerja integracije visoke in nizke frekvence. https://martinfowler.com/articles/branching-patterns.html Povzetek potekov dela To so nekateri pogosto uporabljeni poteki dela, ki so možni v porazdeljenih sistemih, kot je Git, vendar vidite lahko, da so možne mnoge različice, ki ustrezajo vašemu določenemu resničnemu poteku dela. Sedaj, ko lahko (upajmo) določite, katera kombinacija poteka dela lahko deluje za vas, bomo pokrili nekaj določenih primerov, kako doseči glavne vloge, ki naredijo različne poteke. V naslednjem razdelku se boste naučili o nekaterih pogostih vzorcih prispevanja projektu. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://citl.illinois.edu/explore-develop-and-pilot-new-strategies | Explore, Develop, and Pilot New Strategies | Center for Innovation in Teaching & Learning Skip to main content University of Illinois Urbana-Champaign Center for Innovation in Teaching & Learning Search About Who We Are Row Wrapper Column Overview Current Events Special Events Careers Column CITL Directory CITL Fellows How We Can Help How We Can Help Row Wrapper Column Overview Search by Audience & Service Enrich Your Teaching Enhance Your Teaching Skills Promote Student Engagement Universal Design for Learning Make Your Course Accessible (MYCA) Foster Inclusion Graduate Academy for College Teaching Student Resources Achieve Academic Success Take Care of Your Wellbeing Internships Column Create Online Courses Develop a New Program with CITL Develop a New Course with CITL Update an Existing Course Access Self-Service Kits Instructional Support Broadcast & Record Events Exam Scoring Services Slate CRM Systems Column Collect & Analyze Data Finding Data Survey Research Consulting & Training I-STEM Placement & Proficiency Current Cutoffs P&P FAQs Ask a Question Explore Our Spaces Explore Our Spaces Row Wrapper Column Overview Innovation Studio X3 Studio CITL IDEASpace Media Recording Spaces Innovate With Us Innovate With Us Row Wrapper Column Overview Explore, Develop, and Pilot New Strategies Learn and Apply AI & XR Solutions Generative Artificial Intelligence Immersive Technology Teaching Evaluation Teaching Evaluation Row Wrapper Column Overview Campus Teaching Evaluation System Self Evaluation Feedback on the Learning Experience (FLEX) Column Longitudinal Teaching Profiles Share Your Experience Share Your Experience Row Wrapper Column Overview CITL Podcast Instructor Voices Student Voices Newsletter Archive Ask a Question Explore, Develop, and Pilot New Strategies Home Explore, Develop, and Pilot New Strategies CITL helps instructors develop innovative projects and empowers them to harness the transformative potential of technology in education. Discover the cutting-edge technologies and collaborative opportunities that are revolutionizing teaching and learning within CITL. For all experience levels, join us in our endeavors of groundbreaking education solutions and success stories. Discover the cutting-edge technologies and collaborative opportunities Chiara Vincenzi: Fashion Design, VR, AI, & 3D – Oh, My! Chiara Vincenzi is an Italian fashion designer, textile artist, and educator. Before moving to the United States, she worked as a fashion designer, product designer, and graphic designer at multiple world-class fashion companies in Italy, where she gained extensive experience in the fashion design field. After moving to the United States, she continued her professional practice as designer consultant for fashion start-ups, focusing her work on the development of sustainable and ethical apparel lines. In 2017 she joined the School of Art + Design at the University of Illinois Urbana-Champaign, where she currently holds a position as clinical assistant professor. Chiara has worked with CITL’s Innovation Studio staff on numerous projects over the years, but the most high-profile projects involve virtual reality fashion illustration using Open Brush, fashion design ideation using generative AI tools like Midjourney and Adobe Firefly, and sustainable fashion design using CLO3D. Fashion Illustration in Virtual Reality Students in the fashion illustration class learn to communicate their ideas through concept boards, collection plates, and garment drawings, starting with traditional techniques and progressing to digital methods using industry-standard software. In 2019, a new two-week Fashion Project was introduced, allowing students to explore virtual garment design using Tilt Brush (later replaced by Open Brush), a virtual reality software developed by Google. This project includes three three-hour, small group, hands-on sessions dedicated to designing a high couture dress and culminates in a critique phase, where students receive feedback on their virtual creations. The Innovation Studio has served as a collaborative space where students can experiment with digital modeling and fashion design throughout the years. Generative Artificial Intelligence as a Co-Designer In 2024, the VR Fashion Course did a generative artificial intelligence (GenAI) experimental session where students engaged in a variety of tools as a group. They experimented with design, color, texture, shape, accessories, proportion, and more. Introducing students to new technologies, modeling best practices when using GenAI tools, and being playful while doing so is essential in potential adoption as a new tool that they may use in the future. Digital Fashion Design: Teaching and Learning for a Sustainable Future Chiara’s project "Digital Fashion Design: Teaching and Learning for a Sustainable Future” received final approval from the Institute for Sustainability, Energy, and Environment (iSEE), and the Vice Chancellor for Student Affairs in Spring 2024. The project, slated for a 2025 start, aims to enhance the learning experience for students at Illinois by integrating CLO 3D, cutting-edge 3D fashion design software, into our university’s Fashion Concentration in Studio Art. The introduction of this tool will provide a transformative opportunity in our educational offerings, exposing students to emerging tools that emphasize design solutions prioritizing sustainable design from the very inception of fashion creation. This initiative will cultivate a dynamic environment of creativity, learning, and collaboration in partnership with the School of Art and Design, the Center for Innovation in Teaching & Learning (CITL), and the Siebel Center for Design. The incorporation of CLO 3D will extend its benefits to the College of Fine Arts (FAA) and beyond. In addition to enhancing courses with innovative tools, we envision developing and offering “Zero Waste” workshops to engage students in collaborative projects centered around responsible design and waste reduction in fashion. The classes and workshops are designed to involve both students and faculty, promoting education on sustainable design approaches and fostering cross-disciplinary collaboration across the campus. John Toenjes: Exploring dance in VR with Expertise from the Past John Toenjes is Professor, Music Director, and Co-Director of Undergraduate Education at the University of Illinois Department of Dance, and past President of the International Guild of Musicians in Dance. He has written over 30 scores for choreographers, including Lucas Hoving and Joe Goode. Since 2004, he has focused on producing computer-assisted interactive dances such as Inventions Suite (2008 Cleveland Ingenuity Festival), telematic dances such as Timings: An Internet Dance with dancers in Tokyo connected to live avatars, and smartphone-enhanced works such as Kama Begata Nihilum, featuring dancers carrying networked iPads and an audience AR app. In 2014 he established the Laboratory for Audience Interactive Technologies which has designed an app system for live performance called “Mosho.” Dances that integrate Mosho include Critical Mass (2017), and Alternate Reality (2018). He now researches game structures for dance, creating works such as SoundWave Surfing (2020), a dance that pits teams of dancers against each other in an improvisation battle, and a new VR dance adventure game called “Master Dancer.” John Toenjes, a Department of Dance Professor, is working on an innovative project integrating contemporary dance with virtual reality (VR). His research focuses on enhancing dance performances through technological advancements, including motion capture and VR. The multi-year project, funded by a grant from the Campus Research Board, is named "Master Dancer" and aims to combine dance with gaming elements to create a ground-breaking VR dance adventure experience. Exploring dance in VR with Expertise from the Past Toenjes' project explores the use of VR to teach dance creatively, inspired by the historical figure Loïe Fuller, known for her pioneering work in theatrical lighting and dance. He is also interested in incorporating Rudolf von Laban's movement analysis into the VR experience to teach dance concepts. The project has faced challenges, including the need for a skilled team, and adapting to rapidly evolving technology, ultimately involving many researchers and experts from the CITL and various university departments. The current version of the project includes a VR game where users learn dance skills to help restore the virtual presence of Loïe Fuller. Toenjes emphasizes the need for continuous updates and improvements, noting that advancements in VR and AI are transforming the development process. Fulfilling one of CITL’s central missions, this project creates a dynamic and educational experience that blends historical and contemporary dance with cutting-edge technology. Pioneering in its scope and application, it presents both students and instructors with a platform for enhanced learning engagement, serving as an excellent model of intellectual, technological, and artistic pursuits CITL is known for. Bob Pahre: Virtual Reality Transforms Environmental Politics Education Dr. Robert Pahre is a professor and the current Department Head of Political Science at the University of Illinois at Urbana-Champaign. His academic journey includes positions at the University of Rochester and the University of Michigan’s Political Science Department and School of Public Policy (now the Ford School). He earned his PhD in Political Science from UCLA and his BA in International Relations and German Studies from Stanford University, where he also played saxophone for the Leland Stanford Junior University Marching Band. Dr. Pahre's research spans political economy, environmental issues, and the politics of culture and heritage, with a continuing focus on the European Union. He has served as Director of the European Union Center at Illinois. His teaching includes a summer course on the politics of national parks, alternating between various U.S. locations, and an online course on the “Politics of Yellowstone,” which is open to all. In his free time, Dr. Pahre enjoys hiking, backpacking, and photography, often focusing on outdoor and national park scenes. His work and travel publications can be explored on his research page, while his outdoor photography is showcased on Flickr. As environmental issues increasingly arise in remote locations, bridging the gap between classroom learning and real-world experiences has been a challenge. Traditional field trips, while effective, are often impractical for distant destinations like the Greater Yellowstone Ecosystem, which can be expensive and difficult to access for many students, especially those with physical limitations. To help alleviate those challenges, a team of University of Illinois educators led by Robert Pahre, professor of Political Science, aims to provide students with a virtual immersion into the Greater Yellowstone Area (GYA), helping them to develop a deeper understanding and emotional connection to this iconic environment. This innovative project utilizes Virtual Reality (VR) and 360° videography to enhance prof. Pahre’s environmental education. Winter in the Greater Yellowstone The initiative began with "Winter in the Greater Yellowstone," a VR experience featuring a mix of still images and video, which was introduced during the pandemic. Initially available only to students with personal VR headsets, this program succeeded in creating a meaningful sense of place. Today, the project includes around twenty VR videos and interactive panoramas, integrated into the online course “Yellowstone Online.” Students also benefit from live VR presentations in the campus VR Lab. These sessions, ranging from 20 to 90 minutes, cover topics such as recreational impacts, virtual backpacking trips, and wilderness assessments. These interactive experiences allow students to engage directly with instructors and peers. Early findings suggest that "hosted" VR tours, where an instructor guides the virtual experience, offer the strongest emotional connection and sense of place. However, this approach is less scalable as it relies heavily on the presenter's expertise. The project also emphasizes the importance of managing group dynamics within the VR space to ensure a cohesive learning experience. The VR experience has impressed participants with its high-resolution visuals and realistic soundscapes, including nature sounds like running water and bird songs. Future plans include enhancing these auditory elements further to enrich the virtual environment. The project has received significant support from the Center for Innovation in Teaching and Learning (CITL) and the Department of Political Science at the University of Illinois, marking a significant step forward in the integration of innovative technology into environmental education. Tony Zhang: New AI Teaching Assistant Revolutionizes University Learning Dr. Qingquan (Tony) Zhang is an Associate Professor of Finance at Gies College of Business, University of Illinois Urbana-Champaign. His academic focus centers on corporate finance, financial economics, and empirical finance. Dr. Zhang's research interests delve into corporate governance, risk management, and the implications of financial policy on firm behavior and market efficiency. He holds a Ph.D. in Finance from the University of Michigan, as well as a Master's Degree in Economics from the University of Chicago and a Bachelor's Degree in Finance from Fudan University. Before joining Gies College of Business, Dr. Zhang gained valuable experience as a researcher and educator at various esteemed institutions. Dr. Zhang's work has been published in top-tier academic journals and has contributed to the understanding of financial dynamics within firms and markets. His expertise is sought after for insights into financial regulation, corporate decision-making, and the broader economic impacts of financial strategies. At Gies College of Business, Dr. Zhang is known for his commitment to student development and his engaging teaching style. His courses offer students a deep dive into complex financial concepts, preparing them for successful careers in finance and related fields. AristAI Dr. Tony Zhang has co-founded AristAI, a groundbreaking startup poised to transform university education. AristAI is developing advanced AI teaching assistants designed to provide around-the-clock support to students. Zhang, who pivoted from AI applications in cryptocurrency to focus on virtual teaching assistants, has recognized the potential of AI to assist overburdened instructors and shifted his focus accordingly. The result is AI assistants capable of answering course-related questions, directing students to specific lecture content, and generating insightful analytical reports to help instructors refine their teaching approaches. The AristAI team, which includes students from top universities such as Michigan, UCLA, and Harvard, has been testing the AI tool with several Illinois instructors and is integrating the technology with campus platforms like Canvas and MediaSpace. The technology is presently commercially available through the company webpage. Zhang highlights the critical need for proper guidance on AI use, emphasizing that as AI becomes increasingly integral to education, students must learn to use these tools effectively. AristAI’s flexible design allows it to adapt to various teaching methodologies, ensuring that it supports both learning and teaching in a dynamic educational landscape. Got a Vision? We'll help you make it happen. Get in touch Center for Innovation in Teaching & Learning 505 Armory Avenue | Champaign, IL 61820 Phone: 217.333.1462 Email: citl-info@illinois.edu CITL About How We Can Help Innovate With Us Teaching Evaluation Calendar Contact Us Programs Illinois Online Illinois Remote Explore Campus University Admissions Careers at Illinois University News Visit Campus Connect with Illinois University Alumni Giving at Illinois University Calendars University Directory Access University Resources Emergency Services McKinley Health Center Connie Frank CARE Center University Library About Cookies Privacy Policy Copyright Accessibility | 2026-01-13T09:29:41 |
https://support.microsoft.com/el-gr/office/%CF%84%CE%B9-%CE%B5%CE%AF%CE%BD%CE%B1%CE%B9-%CE%B7-%CE%B5%CF%86%CE%B1%CF%81%CE%BC%CE%BF%CE%B3%CE%AE-shifts-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Τι είναι η εφαρμογή Shifts; - Υποστήριξη της Microsoft Σχετικά θέματα × Εκπαιδευτικό βίντεο του Microsoft Teams Γρήγορη εκκίνηση του Microsoft Teams Τι είναι το Microsoft Teams; Πραγματοποιήστε είσοδο και ξεκινήστε Συνομιλία και κοινή χρήση αρχείων Συνεργασία Μάθετε περισσότερα Εισαγωγή στο Microsoft Teams Γρήγορα αποτελέσματα με το Microsoft Teams Γρήγορα αποτελέσματα με τη Συνομιλία Γρήγορα αποτελέσματα με τις Συσκέψεις Γρήγορα αποτελέσματα με τις Εφαρμογές Ρύθμιση και προσαρμογή της ομάδας σας Δημιουργήστε ομάδα με πρότυπα Εργασία με εξωτερικούς επισκέπτες Διαχείριση ρυθμίσεων ομάδας Συνεργασία σε ομάδες και κανάλια Συμβουλή: Στείλτε email σε ένα κανάλι Δημιουργία σχεδίου με το Planner Εργασία με δημοσιεύσεις και μηνύματα Δημοσίευση μηνύματος σε πολλά κανάλια Αναζήτηση και εύρεση αρχείων Ανέβασμα και κοινή χρήση αρχείων Αναζήτηση και φιλτράρισμα ατόμων και αρχείων Αναζήτηση και φιλτράρισμα μηνυμάτων Συμβουλές για αρχεία του Teams Έναρξη συνομιλιών και κλήσεων Επισκόπηση κλήσεων του Teams Πραγματοποίηση κλήσεων Συμβουλές για τις κλήσεις του Teams Απόκρυψη συνομιλιών και διαγραφή μηνυμάτων Ορίστε έναν πληρεξούσιο για να απαντάει τα τηλέφωνά σας Διαχείριση συσκέψεων Συμμετοχή σε σύσκεψη του Teams Συμβουλές για τις συσκέψεις Teams Άμεση σύσκεψη Διαχείριση συσκέψεων Προγραμματισμός ενός webinar Εμφάνιση οθόνης κατά τη διάρκεια σύσκεψης Ρύθμιση ζωντανών συμβάντων και συμμετοχή σε ζωντανά συμβάντα Σχεδίαση και προγραμματισμός ζωντανού συμβάντος Παραγωγή ζωντανού συμβάντος Συμμετοχή σε ζωντανό συμβάν Συντονισμός ερωτήσεων και απαντήσεων Εξερεύνηση εφαρμογών και εργαλείων Εύρεση και χρήση εφαρμογών Διαχείριση χρονοδιαγραμμάτων ομάδας με το Shifts Τι είναι το Shifts; Δημιουργία χρονοδιαγράμματος Shifts Διαχείριση χρονοδιαγράμματος Shifts Δημιουργία εγκρίσεων Τι είναι οι Εγκρίσεις; Δημιουργία έγκρισης Δημιουργία έγκρισης από μια συνομιλία Δημιουργία έγκρισης με ηλεκτρονική υπογραφή Ανακαλύψτε πρότυπα στις Εγκρίσεις Δημιουργία εγκρίσεων με πρότυπα Δημιουργία προτύπων σε επίπεδο οργανισμού Εικονικές συναντήσεις στο Microsoft Bookings Τι είναι οι εικονικές συναντήσεις; Αποστολή ειδοποιήσεων κειμένου SMS εξωτερικών επισκεπτών Διεξαγωγή συνάντησης Συμμετοχή σε συνάντηση Διαχείριση της τροφοδοσίας δραστηριότητας Διαχείριση των ρυθμίσεων ειδοποιήσεων Teams εν κινήσει Έναρξη συνομιλίας εν κινήσει Δημιουργήστε ένα κανάλι εν κινήσει Συμμετοχή σε σύσκεψη εν κινήσει Τροφοδοσία δραστηριότητας εν κινήσει Μετάβαση στο κύριο περιεχόμενο Microsoft Υποστήριξη Υποστήριξη Υποστήριξη Αρχική Microsoft 365 Office Υποστήριξη του Teams Θέματα Συσκέψεις Συνομιλία Ειδοποιήσεις και ρυθμίσεις Teams & κανάλια Κλήσεις και συσκευές Αρχεία Εφαρμογές & υπηρεσίες Γρήγορο ξεκίνημα Συνομιλία Ομαδική συνομιλία Ειδοποιήσεις Teams Κανάλια Κλήσεις Αρχεία Εφαρμογές Στοιχεία Loop Τι νέο υπάρχει Πόροι Εκπαίδευση μέσω βίντεο Αντιμετώπιση προβλημάτων Εδώ στο Teams Προσβασιμότητα Δυνατότητες του Teams ανά πλατφόρμα Microsoft Teams (δωρεάν) Φόρουμ κοινότητας Ιστολόγιο κοινότητας τεχνολογίας Εκπαίδευση εκπαιδευτή-επικεφαλή Για διαχειριστές και επαγγελματίες τεχνολογίας της πληροφορίας Για εκπαίδευση Περισσότερα Αγορά του Microsoft 365 Όλη η Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Υποστήριξη Λογισμικό Λογισμικό Εφαρμογές Windows Τεχνητή νοημοσύνη OneDrive Outlook Μετάβαση από το Skype στο Teams OneNote Microsoft Teams Υπολογιστές και συσκευές Υπολογιστές και συσκευές Αξεσουάρ υπολογιστή Ψυχαγωγία Ψυχαγωγία Xbox Game Pass Ultimate Xbox Game Pass Essential Xbox και παιχνίδια Παιχνίδια για υπολογιστή Επαγγελματίες Επαγγελματίες Ασφάλεια Microsoft Azure Dynamics 365 Microsoft 365 για Επιχειρήσεις Microsoft Industry Microsoft Power Platform Windows 365 Προγραμματιστής και IT Προγραμματιστής και IT Πρόγραμμα για προγραμματιστές της Microsoft Microsoft Learn Υποστήριξη για εφαρμογές αγοράς AI Τεχνολογική κοινότητα της Microsoft Microsoft Marketplace Visual Studio Marketplace Rewards Άλλα Άλλα Δωρεάν στοιχεία λήψης και ασφάλεια Εκπαίδευση Δωροκάρτες Προβολή χάρτη τοποθεσίας Αναζήτηση Αναζήτηση βοήθειας Δεν υπάρχουν αποτελέσματα Άκυρο Είσοδος Είσοδος με Microsoft Είσοδος ή δημιουργία λογαριασμού. Γεια σας, Επιλέξτε διαφορετικό λογαριασμό. Έχετε πολλούς λογαριασμούς Επιλέξτε τον λογαριασμό με τον οποίο θέλετε να εισέλθετε. Σχετικά θέματα Εκπαιδευτικό βίντεο του Microsoft Teams Γρήγορη εκκίνηση του Microsoft Teams Τι είναι το Microsoft Teams; Πραγματοποιήστε είσοδο και ξεκινήστε Συνομιλία και κοινή χρήση αρχείων Συνεργασία Μάθετε περισσότερα Εισαγωγή στο Microsoft Teams Γρήγορα αποτελέσματα με το Microsoft Teams Γρήγορα αποτελέσματα με τη Συνομιλία Γρήγορα αποτελέσματα με τις Συσκέψεις Γρήγορα αποτελέσματα με τις Εφαρμογές Ρύθμιση και προσαρμογή της ομάδας σας Δημιουργήστε ομάδα με πρότυπα Εργασία με εξωτερικούς επισκέπτες Διαχείριση ρυθμίσεων ομάδας Συνεργασία σε ομάδες και κανάλια Συμβουλή: Στείλτε email σε ένα κανάλι Δημιουργία σχεδίου με το Planner Εργασία με δημοσιεύσεις και μηνύματα Δημοσίευση μηνύματος σε πολλά κανάλια Αναζήτηση και εύρεση αρχείων Ανέβασμα και κοινή χρήση αρχείων Αναζήτηση και φιλτράρισμα ατόμων και αρχείων Αναζήτηση και φιλτράρισμα μηνυμάτων Συμβουλές για αρχεία του Teams Έναρξη συνομιλιών και κλήσεων Επισκόπηση κλήσεων του Teams Πραγματοποίηση κλήσεων Συμβουλές για τις κλήσεις του Teams Απόκρυψη συνομιλιών και διαγραφή μηνυμάτων Ορίστε έναν πληρεξούσιο για να απαντάει τα τηλέφωνά σας Διαχείριση συσκέψεων Συμμετοχή σε σύσκεψη του Teams Συμβουλές για τις συσκέψεις Teams Άμεση σύσκεψη Διαχείριση συσκέψεων Προγραμματισμός ενός webinar Εμφάνιση οθόνης κατά τη διάρκεια σύσκεψης Ρύθμιση ζωντανών συμβάντων και συμμετοχή σε ζωντανά συμβάντα Σχεδίαση και προγραμματισμός ζωντανού συμβάντος Παραγωγή ζωντανού συμβάντος Συμμετοχή σε ζωντανό συμβάν Συντονισμός ερωτήσεων και απαντήσεων Εξερεύνηση εφαρμογών και εργαλείων Εύρεση και χρήση εφαρμογών Διαχείριση χρονοδιαγραμμάτων ομάδας με το Shifts Τι είναι το Shifts; Δημιουργία χρονοδιαγράμματος Shifts Διαχείριση χρονοδιαγράμματος Shifts Δημιουργία εγκρίσεων Τι είναι οι Εγκρίσεις; Δημιουργία έγκρισης Δημιουργία έγκρισης από μια συνομιλία Δημιουργία έγκρισης με ηλεκτρονική υπογραφή Ανακαλύψτε πρότυπα στις Εγκρίσεις Δημιουργία εγκρίσεων με πρότυπα Δημιουργία προτύπων σε επίπεδο οργανισμού Εικονικές συναντήσεις στο Microsoft Bookings Τι είναι οι εικονικές συναντήσεις; Αποστολή ειδοποιήσεων κειμένου SMS εξωτερικών επισκεπτών Διεξαγωγή συνάντησης Συμμετοχή σε συνάντηση Διαχείριση της τροφοδοσίας δραστηριότητας Διαχείριση των ρυθμίσεων ειδοποιήσεων Teams εν κινήσει Έναρξη συνομιλίας εν κινήσει Δημιουργήστε ένα κανάλι εν κινήσει Συμμετοχή σε σύσκεψη εν κινήσει Τροφοδοσία δραστηριότητας εν κινήσει Τι είναι η εφαρμογή Shifts; Ισχύει για Teams Microsoft Teams Δοκιμάστε το! Η εφαρμογή Βάρδιες στο Microsoft Teams είναι ένα εργαλείο διαχείρισης χρονοδιαγράμματος και παρακολούθησης χρόνου που σας βοηθά να δημιουργείτε, να ενημερώνετε και να διαχειρίζεστε χρονοδιαγράμματα για την ομάδα σας. Χρονοδιαγράμματα - Δημιουργήστε, επεξεργαστείτε και διαχειριστείτε ένα χρονοδιάγραμμα για την ομάδα σας. Το χρονοδιάγραμμα βάρδιες εμφανίζει τις ημέρες στο επάνω μέρος, τα μέλη της ομάδας εμφανίζονται στα αριστερά και οι αντιστοιχισμένες βάρδιες εμφανίζονται στο ημερολόγιο. Ρυθμίσεις χρονοδιαγράμματος - Στις ρυθμίσεις Shift, καθορίστε τις επιλογές χρονοδιαγράμματος και επιλέξτε τις δυνατότητες shifts που θέλετε να είναι διαθέσιμες στην ομάδα σας. Ομάδες - Προσθέστε ομάδες χρονοδιαγράμματος για να οργανώσετε τα μέλη της ομάδας στο χρονοδιάγραμμα κατά τύπο εργασίας ή θέση. Βάρδιες - Εκχωρήστε βάρδιες στα μέλη της ομάδας. Δημιουργήστε μια βάρδια από την αρχή ή αντιγράψτε μια υπάρχουσα. Άνοιγμα βαρδιών - Κάθε ομάδα στο χρονοδιάγραμμα έχει μια γραμμή Άνοιγμα βαρδιών . Προσθέστε ανοικτές βάρδιες στο χρονοδιάγραμμά σας, τις οποίες μπορεί να ζητήσει οποιοσδήποτε. Ρολόι χρόνου - Ενεργοποιήστε την επιλογή Ώρα ώρας στις ρυθμίσεις Shift, για να επιτρέψετε στην ομάδα σας να πραγματοποιεί είσοδο και έξοδο από τις βάρδιες. Αιτήσεις - Εξετάστε και απαντήστε σε αιτήσεις για άδεια, ανοίξτε βάρδιες, αλλαγές βάρδιας και προσφορές. Ετικέτες - Χρησιμοποιήστε ετικέτες βάσει shift για να επικοινωνήσετε γρήγορα με οποιονδήποτε βρίσκεται τη δεδομένη στιγμή σε βάρδια. Δημοσιεύστε το χρονοδιάγραμμά σας - Όταν ολοκληρώσετε τις αλλαγές στο χρονοδιάγραμμα, μοιραστείτε το με την ομάδα σας, ώστε όλοι οι χρήστες να είναι ενημερωμένοι. Θέλετε περισσότερα; Έναρξη με τις Βάρδιες Δημιουργία χρονοδιαγράμματος ομάδας στις Βάρδιες Προσθήκη βαρδιών στο χρονοδιάγραμμα στις Βάρδιες Δημοσίευση χρονοδιαγράμματος στις Βάρδιες Διαχείριση αιτήσεων βάρδιας και άδειας στις Βάρδιες Ενεργοποίηση ετικετών που βασίζονται σε βάρδιες στο Teams ΕΓΓΡΑΦΗ ΣΤΙΣ ΤΡΟΦΟΔΟΣΙΕΣ RSS Χρειάζεστε περισσότερη βοήθεια; Θέλετε περισσότερες επιλογές; Ανακαλύψτε Κοινότητα Εξερευνήστε τα πλεονεκτήματα της συνδρομής, περιηγηθείτε σε εκπαιδευτικά σεμινάρια, μάθετε πώς μπορείτε να προστατεύσετε τη συσκευή σας και πολλά άλλα. Πλεονεκτήματα συνδρομής Microsoft 365 Εκπαίδευση Microsoft 365 Ασφάλεια της Microsoft Κέντρο προσβασιμότητας Οι κοινότητες σάς βοηθούν να κάνετε και να απαντάτε σε ερωτήσεις, να δίνετε σχόλια και να ακούτε από ειδικούς με πλούσια γνώση. Ρωτήστε την κοινότητα της Microsoft Τεχνική Κοινότητα Microsoft Windows Insiders Microsoft 365 Insiders Σας βοήθησαν αυτές οι πληροφορίες; Ναι Όχι Ευχαριστούμε! Έχετε άλλα σχόλια για τη Microsoft; Μπορείτε να μας βοηθήσετε να βελτιωθούμε; (Στείλτε σχόλια στη Microsoft, ώστε να μπορέσουμε να βοηθήσουμε.) Πόσο ικανοποιημένοι είστε με τη γλωσσική ποιότητα; Τι επηρέασε την εμπειρία σας; Το ζήτημά μου επιλύθηκε Απαλοιφή οδηγιών Ευνόητο Χωρίς τεχνική ορολογία Οι εικόνες βοήθησαν Ποιότητα μετάφρασης Δεν συμφωνούσε με την οθόνη μου Εσφαλμένες οδηγίες Πολύ τεχνικό Ανεπαρκείς πληροφορίες Δεν υπάρχουν αρκετές εικόνες Ποιότητα μετάφρασης Έχετε πρόσθετα σχόλια; (Προαιρετικό) Υποβολή σχολίων Πατώντας "Υποβολή" τα σχόλια σας θα χρησιμοποιηθούν για τη βελτίωση των προϊόντων και των υπηρεσιών της Microsoft. Ο διαχειριστής IT θα έχει τη δυνατότητα να συλλέξει αυτά τα δεδομένα. Δήλωση προστασίας προσωπικών δεδομένων. Σας ευχαριστούμε για τα σχόλιά σας! × Τι νέο υπάρχει Copilot για οργανισμούς Copilot για προσωπική χρήση Microsoft 365 Εφαρμογές των Windows 11 Microsoft Store Προφίλ λογαριασμού Κέντρο λήψης Επιστροφές Παρακολούθηση παραγγελίας Ανακύκλωση Commercial Warranties Εκπαίδευση Microsoft για εκπαιδευτικά ιδρύματα Συσκευές για εκπαιδευτικά ιδρύματα Microsoft Teams για εκπαιδευτικά ιδρύματα Microsoft 365 για εκπαιδευτικά ιδρύματα Office για εκπαιδευτικά ιδρύματα Εκπαίδευση και ανάπτυξη εκπαιδευτικών Προσφορές για σπουδαστές και γονείς Azure για σπουδαστές Επιχειρήσεις Ασφάλεια Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Προγραμματιστής και IT Πρόγραμμα για προγραμματιστές της Microsoft Microsoft Learn Υποστήριξη για εφαρμογές αγοράς AI Τεχνολογική κοινότητα της Microsoft Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Εταιρεία Σταδιοδρομίες Εταιρικά νέα Προστασία προσωπικών δεδομένων στη Microsoft Επενδυτές Βιωσιμότητα Ελληνικά (Ελλάδα) Εικονίδιο εξαίρεσης σχετικά με τις επιλογές προστασίας προσωπικών δεδομένων σας Οι επιλογές προστασίας προσωπικών δεδομένων σας Εικονίδιο εξαίρεσης σχετικά με τις επιλογές προστασίας προσωπικών δεδομένων σας Οι επιλογές προστασίας προσωπικών δεδομένων σας Προστασία προσωπικών δεδομένων για την υγεία των καταναλωτών Επικοινωνήστε με τη Microsoft Προστασία δεδομένων Διαχείριση cookies Όροι χρήσης Εμπορικά σήματα Σχετικά με τις διαφημίσεις μας EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/ms/v2/Distributed-Git-Distributed-Workflows | Git - Distributed Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distributed Git - Distributed Workflows Now that you have a remote Git repository set up as a focal point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. Distributed Workflows In contrast with Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally with a central hub. In Git, however, every developer is potentially both a node and a hub; that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This presents a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model — the centralized workflow. One central hub, or repository , can accept code, and everyone synchronizes their work with it. A number of developers are nodes — consumers of that hub — and synchronize with that centralized location. Figure 53. Centralized workflow This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. Integration-Manager Workflow Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an email asking them to pull changes. The maintainer adds the contributor’s repository as a remote and merges locally. The maintainer pushes merged changes to the main repository. Figure 54. Integration-manager workflow This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes — each party can work at their own pace. Dictator and Lieutenants Workflow This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants . All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator pushes from their directory to a reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the reference repository to which the dictator pushes. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. Finally, the dictator pushes that master branch to the reference repository so the other developers can rebase on it. Figure 55. Benevolent dictator workflow This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. Patterns for Managing Source Code Branches Note Martin Fowler has made a guide "Patterns for Managing Source Code Branches". This guide covers all the common Git workflows, and explains how/when to use them. There’s also a section comparing high and low integration frequencies. https://martinfowler.com/articles/branching-patterns.html Workflows Summary These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://support.microsoft.com/zh-hk/microsoft-store-and-billing | Microsoft Store 與計費說明 跳到主要內容 Microsoft 支持 支持 支持 Home Microsoft 365 Office 產品 Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows 更多信息 ... 设备 Surface PC Accessories Xbox PC Gaming HoloLens Surface Hub 硬件保修 Account & billing Account Microsoft Store & billing 资源 新功能 社区论坛 Microsoft 365 管理员 小型企业门户 开发人员 教育 上报支持欺诈 Product safety More Buy Microsoft 365 Microsoft 所有 Global Microsoft 365 Teams Windows Surface Xbox 支援 軟件 軟件 Windows Apps 人工智能 OneDrive Outlook 從 Skype 轉用 Teams Microsoft Teams PC 及 裝置 PC 及 裝置 PC 與平板電腦 配件 娛樂 娛樂 Xbox Game Pass Ultimate Xbox Live 金會員 電腦遊戲 企業 企業 Microsoft 安全性 Azure Dynamics 365 商務用 Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 開發人員與資訊科技人員 開發人員與資訊科技人員 Microsoft 開發人員 Microsoft 學習 AI 市集 App 支援 Microsoft 科技社群 Microsoft Marketplace Visual Studio Marketplace Rewards 其他 其他 Microsoft Rewards 免費下載項目與安全性 教育 查看網站地圖 搜尋 Search for help 沒有結果 Cancel 登入 Sign in with Microsoft Sign in or create an account. Hello, Select a different account. You have multiple accounts Choose the account you want to sign in with. Microsoft Store 與計費說明 管理訂閱 傳回 & 退款 付款選項 訂購記錄 禮品卡 安裝 Microsoft 365 Windows 上的 Microsoft 市集] 探索Microsoft市集服務 從免費運送和退貨到我們 60 天的價格保護，我們在這裡協助您使用一流的裝置、軟體、遊戲和資源來完成更多工作。 查看 Microsoft Store 提供哪些功能： 購物和購買支援 | 產品設定和訓練 | 小型企業支援 購物和購買支援 Microsoft市集服務並非在所有地區都有提供。 若要查看哪些選項可供您使用，請從下方的下拉式清單中選取您的國家或地區，如果未列出，請選取 其他地區 . 選取您的地區 美國 澳大利亞 加拿大 (英文) 加拿大 (法文) 英國 其他地區 為什麼要在 Microsoft Store 購物 輕鬆、方便的購物 免費運送 2-3 天 免費 60 天退貨 60 天價格保護 彈性付款選項 用於您使用之裝置的現金 交易與回收 特殊折扣和優惠 適用於學生、家長和授課者 針對軍事人員 延伸裝置保護 Microsoft完成保護計劃 我們可以協助您找到所需的專案 銷售支援說明 身心障礙人士 answer desk 與 ASL 關聯人員一起購物 為什麼要在 Microsoft Store 購物 輕鬆、方便的購物 免運費 免費 60 天退貨 60 天價格保護 用於您使用之裝置的現金 交易與回收 特殊折扣和優惠 適用於學生、家長和授課者 我們可以協助您找到所需的專案 銷售支援說明 身心障礙人士 answer desk 為什麼要在 Microsoft Store 購物 輕鬆、方便的購物 免運費 免費 60 天退貨 60 天價格保護 用於您使用之裝置的現金 交易與回收 特殊折扣和優惠 適用於學生、家長和授課者 延伸裝置保護 Microsoft完成保護計劃 我們可以協助您找到所需的專案 如果您在購買之前有問題，請與產品專家聊天或預約購物約會。 銷售支援說明 為什麼要在 Microsoft Store 購物 輕鬆、方便的購物 免運費 免費 60 天退貨 60 天價格保護 用於您使用之裝置的現金 交易與回收 特殊折扣和優惠 適用於學生、家長和授課者 延伸裝置保護 Microsoft完成保護計劃 為什麼要在 Microsoft Store 購物 輕鬆、方便的購物 免運費 免費 60 天退貨 60 天價格保護 用於您使用之裝置的現金 交易與回收 特殊折扣和優惠 適用於學生、家長和授課者 我們可以協助您找到所需的專案 銷售支援說明 身心障礙人士 answer desk 為什麼要在 Microsoft Store 購物 我們可以協助您找到所需的專案 如果您在購買之前有問題，請與產品專家聊天。 銷售支援說明 流覽 Microsoft Store The Microsoft Store 產品設定和訓練 這裡所列的Microsoft市集服務並非在所有地區都有提供。 若要查看您的選項，請從下方的下拉式清單中選取您的國家或地區： 選取您的地區 美國 澳大利亞 加拿大 (英文) 加拿大 (法文) 英國 其他地區 說明與學習資源 查看我們的產品支援資源，協助您找到所需的解答。 Surface 裝置 | Xbox Microsoft 365 | 窗戶 說明與學習資源 我們的產品支援資源可協助您找到所需的解答。 Surface 裝置 | Xbox Microsoft 365 | 窗戶 說明與學習資源 查看我們的產品支援資源，協助您找到所需的解答。 Surface 裝置 | Xbox Microsoft 365 | 窗戶 說明與學習資源 查看我們的產品支援資源，協助您找到所需的解答。 Surface 裝置 | Xbox Microsoft 365 | 窗戶 說明與學習資源 查看我們的產品支援資源，協助您找到所需的解答。 Surface 裝置 | Xbox Microsoft 365 | 窗戶 說明與學習資源 查看我們的產品支援資源，協助您找到所需的解答。 Surface 裝置 | Xbox Microsoft 365 | 窗戶 小型企業支援 若要查看您所在地區提供哪些小型企業支援選項，請從下方的下拉式清單中選取您的國家或地區： 選取您的地區 美國 澳大利亞 加拿大 (英文) 加拿大 (法文) 英國 其他地區 小型企業的資源 取得建議、免費訓練、產品和工具，協助您的企業發展。 小型企業說明與學習 小型企業資源中心 小型企業的資源 取得建議、免費訓練、產品和工具，協助您的企業發展。 小型企業說明與學習 小型企業資源中心 小型企業的資源 取得建議、免費訓練、產品和工具，協助您的企業發展。 小型企業說明與學習 小型企業資源中心 小型企業的資源 從評估您的業務需求到協助設定和疑難解答，我們在這裡提供協助。 取得建議、免費訓練、產品和工具，協助您的企業發展。 小型企業說明與學習 小型企業資源中心 小型企業的資源 取得建議、免費訓練、產品和工具，協助您的企業發展。 小型企業說明與學習 小型企業資源中心 小型企業的資源 取得建議、免費訓練、產品和工具，協助您的企業發展。 小型企業說明與學習 最新消息 Surface Pro Surface Laptop Copilot 機構版 Copilot 個人版 AI 登陸 Windows Microsoft 365 探索 Microsoft 產品 Windows 11 Apps Microsoft Store 帳戶個人檔案 下載中心 訂單追蹤 教育 Microsoft 教學版 教學裝置 Microsoft Teams 教學版 Microsoft 365 教學版 Office 教學版 教職員培訓與發展 學生與家長尊享優惠 Azure 學生版 企業 Microsoft 安全性 Azure Dynamics 365 Microsoft 365 Microsoft 廣告 Microsoft 365 Copilot Microsoft Teams 開發人員與資訊科技人員 Microsoft 開發人員 Microsoft 學習 AI 市集 App 支援 Microsoft 科技社群 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 公司 招聘 公司新聞 Microsoft 私隱權 投資者 可持續發展 中文(香港特別行政區) Your Privacy Choices Opt-Out Icon 您在加州的隱私選擇 Your Privacy Choices Opt-Out Icon 您在加州的隱私選擇 Consumer Health Privacy 聯絡 Microsoft 私隱權 管理 Cookie 使用協議條款 商標 關於我們的廣告 © Microsoft 2026 | 2026-01-13T09:29:41 |
https://www.drupal.org/user/186334/contribution-records?field_is_sa_value=0 | Contribution Records user listing | Drupal.org Skip to main content Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Search Drupal.org Menu Main menu Discover Drupal Drupal Core The open source framework behind millions of websites Drupal CMS Drupal CMS puts the power of Drupal into the hands of marketers, designers and content creators Drupal AI Open limitless possibilities with Drupal AI Case Studies Powerful stories that show Drupal solutions in the real world Drupal for Government Drupal is the open-source CMS that enables digital transformation of government and increases citizen engagement Drupal for Higher Education See why 70% of the world's leading universities chose Drupal Drupal for Nonprofit See why Drupal is the open-source CMS choice for some of the world’s most influential nonprofits Drupal for eCommerce Natively integrate content and commerce Drupal for FinTech Secure and trustworthy FinTech infrastructure Drupal for Healthcare Drupal powers systems that are secure, patient-centric and engaging Drupal for Enterprise Why enterprise organizations choose Drupal for multi-brand governance and global scale. Drupal for Retail See how Drupal delivers retail experiences across every channel and touchpoint. Drupal for Travel & Tourism Discover how Drupal powers travel across websites, mobile, and onboard experiences. Build with Drupal Download Drupal Download Drupal and the extensions you need Documentation Full knowledgebase including Drupal 7 resources Getting Started Guide to installing Drupal on a server Local Development Guide Guide to installing Drupal locally with Docker and DDEV Developer Resources Step-by-step guide for learning Drupal Drupal CMS User Guide Learn how to set up your site with Drupal CMS Drupal User Guide Learn to build with Drupal API Complete documentation of Drupal Core APIs Modules Extend your project's functionality Themes Change your project's look and feel Distributions Jumpstart your project with a pre-configured install Issues Queue Report issues and contribute improvements Security Advisories Stay on top of the latest security alerts and updates Partners & Services Find a Drupal Certified Partner Connect with the best Drupal agencies around the world Become an Drupal Certified Partner Join an elite network of agencies committed to Drupal excellence and innovation Find a Hosting Provider Find a hosting provider for your Drupal project Find a Migration Partner Get help with your migration to the latest version of Drupal Find Training Upskill your Drupal team Drupal Steward Ensure your website is protected with Drupal Steward Community About the Community Come for the code, stay for the community How to Contribute Get involved in growing and evolving Drupal DrupalCon DrupalCon unites experts from around the globe who create ambitious digital experiences. Network, learn, and be inspired Events Discover local events, meet-ups, and training Jobs / Careers Find opportunities to work in Drupal News & Blogs News and stories about Drupal Forum Got a question about Drupal? Find answers on the Drupal forums Slack Get support and communicate with the global Drupal community Newsletters Sign up for Drupal news and manage your subscriptions Drupal Swag Shop Get your Drupal branded merch! Support Drupal The Drupal Association Learn how we support Drupal's growth and innovation - and how you can help Become a Member Become a Ripplemaker and support the Drupal Association Become a Drupal Certified Partner Join an elite network of agencies committed to Drupal excellence and innovation Donate Make a donation to the nonprofit that supports Drupal User Menu Log in Create account Get Started Try Drupal CMS Try hosting Search Search User menu Log in Create account Secondary menu Get Started Try Drupal CMS Try Hosting Breadcrumb Home jemond Contribution records credited to jemond Displaying 1 - 5 of 5 Project machine name eg: admin_toolbar Last status change - Any - Past year Past 3 months Past 2 months Past month Past 2 weeks Is security advisory - Any - True False CDN CDN and SEO Mon, 03/01/2021 - 12:51 DrupalCon Global 2020 Session Speaker Mon, 08/17/2020 - 23:09 DrupalCon Portland 2022 DC POR 22: Speakers Sat, 05/14/2022 - 22:54 Force Password Change Exclude AJAX requests from redirection Thu, 12/22/2016 - 01:54 Link Provide formatter to remove http:// or https:// from URL Thu, 02/08/2018 - 13:39 Drupal.org About Drupal Code of Conduct News Planet Drupal Privacy Policy Signup for Drupal News Terms of Service Web Accessibility facebook instagram linkedin mastodon slack youtube Tag1 provides infrastructure management for Drupal.org Need a Drupal 7 extended support partner? Consider Tag1. Drupal is a registered trademark of Dries Buytaert . Copyright 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/fr/v2/Git-distribu%c3%a9-D%c3%a9veloppements-distribu%c3%a9s | Git - Développements distribués About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Démarrage rapide 1.1 À propos de la gestion de version 1.2 Une rapide histoire de Git 1.3 Rudiments de Git 1.4 La ligne de commande 1.5 Installation de Git 1.6 Paramétrage à la première utilisation de Git 1.7 Obtenir de l’aide 1.8 Résumé 2. Les bases de Git 2.1 Démarrer un dépôt Git 2.2 Enregistrer des modifications dans le dépôt 2.3 Visualiser l’historique des validations 2.4 Annuler des actions 2.5 Travailler avec des dépôts distants 2.6 Étiquetage 2.7 Les alias Git 2.8 Résumé 3. Les branches avec Git 3.1 Les branches en bref 3.2 Branches et fusions : les bases 3.3 Gestion des branches 3.4 Travailler avec les branches 3.5 Branches de suivi à distance 3.6 Rebaser (Rebasing) 3.7 Résumé 4. Git sur le serveur 4.1 Protocoles 4.2 Installation de Git sur un serveur 4.3 Génération des clés publiques SSH 4.4 Mise en place du serveur 4.5 Démon (Daemon) Git 4.6 HTTP intelligent 4.7 GitWeb 4.8 GitLab 4.9 Git hébergé 4.10 Résumé 5. Git distribué 5.1 Développements distribués 5.2 Contribution à un projet 5.3 Maintenance d’un projet 5.4 Résumé 6. GitHub 6.1 Configuration et paramétrage d’un compte 6.2 Contribution à un projet 6.3 Maintenance d’un projet 6.4 Gestion d’un regroupement 6.5 Écriture de scripts pour GitHub 6.6 Résumé 7. Utilitaires Git 7.1 Sélection des versions 7.2 Indexation interactive 7.3 Remisage et nettoyage 7.4 Signer votre travail 7.5 Recherche 7.6 Réécrire l’historique 7.7 Reset démystifié 7.8 Fusion avancée 7.9 Rerere 7.10 Déboguer avec Git 7.11 Sous-modules 7.12 Empaquetage (bundling) 7.13 Replace 7.14 Stockage des identifiants 7.15 Résumé 8. Personnalisation de Git 8.1 Configuration de Git 8.2 Attributs Git 8.3 Crochets Git 8.4 Exemple de politique gérée par Git 8.5 Résumé 9. Git et les autres systèmes 9.1 Git comme client 9.2 Migration vers Git 9.3 Résumé 10. Les tripes de Git 10.1 Plomberie et porcelaine 10.2 Les objets de Git 10.3 Références Git 10.4 Fichiers groupés 10.5 La refspec 10.6 Les protocoles de transfert 10.7 Maintenance et récupération de données 10.8 Les variables d’environnement 10.9 Résumé A1. Annexe A: Git dans d’autres environnements A1.1 Interfaces graphiques A1.2 Git dans Visual Studio A1.3 Git dans Visual Studio Code A1.4 Git dans IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git dans Sublime Text A1.6 Git dans Bash A1.7 Git dans Zsh A1.8 Git dans PowerShell A1.9 Résumé A2. Annexe B: Embarquer Git dans vos applications A2.1 Git en ligne de commande A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Commandes Git A3.1 Installation et configuration A3.2 Obtention et création des projets A3.3 Capture d’instantané basique A3.4 Création de branches et fusion A3.5 Partage et mise à jour de projets A3.6 Inspection et comparaison A3.7 Débogage A3.8 Patchs A3.9 Courriel A3.10 Systèmes externes A3.11 Administration A3.12 Commandes de plomberie 2nd Edition 5.1 Git distribué - Développements distribués Avec un dépôt distant Git mis en place pour permettre à tous les développeurs de partager leur code, et la connaissance des commandes de base de Git pour une gestion locale, abordons les méthodes de gestion distribuée que Git nous offre. Dans ce chapitre, vous découvrirez comment travailler dans un environnement distribué avec Git en tant que contributeur ou comme intégrateur. Cela recouvre la manière de contribuer efficacement à un projet et de rendre la vie plus facile au mainteneur du projet ainsi qu’à vous-même, mais aussi en tant que mainteneur, de gérer un projet avec de nombreux contributeurs. Développements distribués À la différence des systèmes de gestion de version centralisés (CVCS), la nature distribuée de Git permet une bien plus grande flexibilité dans la manière dont les développeurs collaborent sur un projet. Dans les systèmes centralisés, tout développeur est un nœud travaillant de manière plus ou moins égale sur un concentrateur central. Dans Git par contre, tout développeur est potentiellement un nœud et un concentrateur, c’est-à-dire que chaque développeur peut à la fois contribuer du code vers les autres dépôts et maintenir un dépôt public sur lequel d’autres vont baser leur travail et auquel ils vont contribuer. Cette capacité ouvre une perspective de modes de développement pour votre projet ou votre équipe dont certains archétypes tirant parti de cette flexibilité seront traités dans les sections qui suivent. Les avantages et inconvénients éventuels de chaque mode seront traités. Vous pouvez choisir d’en utiliser un seul ou de mélanger les fonctions de chacun. Gestion Centralisée Dans les systèmes centralisés, il n’y a généralement qu’un seul modèle de collaboration, la gestion centralisée. Un concentrateur ou dépôt central accepte le code et tout le monde doit synchroniser son travail avec. Les développeurs sont des nœuds, des consommateurs du concentrateur, seul endroit où ils se synchronisent. Figure 53. Gestion centralisée. Cela signifie que si deux développeurs clonent depuis le concentrateur et qu’ils introduisent tous les deux des modifications, le premier à pousser ses modifications le fera sans encombre. Le second développeur doit fusionner les modifications du premier dans son dépôt local avant de pousser ses modifications pour ne pas écraser les modifications du premier. Ce concept reste aussi vrai avec Git qu’il l’est avec Subversion (ou tout autre CVCS) et le modèle fonctionne parfaitement dans Git. Si vous êtes déjà habitué à une gestion centralisée dans votre société ou votre équipe, vous pouvez simplement continuer à utiliser cette méthode avec Git. Mettez en place un dépôt unique et donnez à tous l’accès en poussée. Git empêchera les utilisateurs d’écraser le travail des autres. Supposons que John et Jessica commencent en même temps une tâche. John la termine et pousse ses modifications sur le serveur. Puis Jessica essaie de pousser ses modifications, mais le serveur les rejette. Il lui indique qu’elle tente de pousser des modifications sans avance rapide et qu’elle ne pourra le faire tant qu’elle n’aura pas récupéré et fusionné les nouvelles modifications depuis le serveur. Cette méthode est très intéressante pour de nombreuses personnes car c’est un paradigme avec lequel beaucoup sont familiarisés et à l’aise. Ce modèle n’est pas limité aux petites équipes. Avec le modèle de branchement de Git, des centaines de développeurs peuvent travailler harmonieusement sur un unique projet au travers de dizaines de branches simultanées. Mode du gestionnaire d’intégration Comme Git permet une multiplicité de dépôts distants, il est possible d’envisager un mode de fonctionnement où chaque développeur a un accès en écriture à son propre dépôt public et en lecture à tous ceux des autres. Ce scénario inclut souvent un dépôt canonique qui représente le projet « officiel ». Pour commencer à contribuer au projet, vous créez votre propre clone public du projet et poussez vos modifications dessus. Après, il suffit d’envoyer une demande au mainteneur de projet pour qu’il tire vos modifications dans le dépôt canonique. Il peut ajouter votre dépôt comme dépôt distant, tester vos modifications localement, les fusionner dans sa branche et les pousser vers le dépôt public. Le processus se passe comme ceci (voir Le mode du gestionnaire d’intégration. ) : Le mainteneur du projet pousse vers son dépôt public. Un contributeur clone ce dépôt et introduit des modifications. Le contributeur pousse son travail sur son dépôt public. Le contributeur envoie au mainteneur un e-mail de demande pour tirer ses modifications depuis son dépôt. Le mainteneur ajoute le dépôt du contributeur comme dépôt distant et fusionne les modifications localement. Le mainteneur pousse les modifications fusionnées sur le dépôt principal. Figure 54. Le mode du gestionnaire d’intégration. C’est une gestion très commune sur des sites « échangeurs » tels que GitHub ou GitLab où il est aisé de dupliquer un projet et de pousser ses modifications pour les rendre publiques. Un avantage distinctif de cette approche est qu’il devient possible de continuer à travailler et que le mainteneur du dépôt principal peut tirer les modifications à tout moment. Les contributeurs n’ont pas à attendre le bon vouloir du mainteneur pour incorporer leurs modifications. Chaque acteur peut travailler à son rythme. Mode dictateur et ses lieutenants C’est une variante de la gestion multi-dépôt. En général, ce mode est utilisé sur des projets immenses comprenant des centaines de collaborateurs. Un exemple célèbre est le noyau Linux. Des gestionnaires d’intégration gèrent certaines parties du projet. Ce sont les lieutenants. Tous les lieutenants ont un unique gestionnaire d’intégration, le dictateur bienveillant. Le dépôt du dictateur sert de dépôt de référence à partir duquel tous les collaborateurs doivent tirer. Le processus se déroule comme suit (voir Le processus du dictateur bienveillant. ) : Les simples développeurs travaillent sur la branche thématique et rebasent leur travail sur master. La branche master est celle du dictateur. Les lieutenants fusionnent les branches thématiques des développeurs dans leur propre branche master . Le dictateur fusionne les branches master de ses lieutenants dans sa propre branche master . Le dictateur pousse sa branche master sur le dépôt de référence pour que les développeurs se rebasent dessus. Figure 55. Le processus du dictateur bienveillant. Ce schéma de processus n’est pas très utilisé mais s’avère utile dans des projets très gros ou pour lesquels un ordre hiérarchique existe, car il permet au chef de projet (le dictateur) de déléguer une grande partie du travail et de collecter de grands sous-ensembles de codes à différents points avant de les intégrer. Schémas pour gérer des branches de code source Note Martin Fowler a écrit un guide "Patterns for Managing Source Code Branches". Ce guide couvre tous les flux de travail communs avec Git et explique comment/quand les utiliser. Il y a aussi une section comparant les fréquences d’intégration faible et hautes. https://martinfowler.com/articles/branching-patterns.html Résumé Voilà donc quelques-uns des flux de travail les plus utilisés avec un système distribué tel que Git, mais on voit que de nombreuses variations sont possibles pour mieux correspondre à un mode de gestion réel. À présent que vous avez pu déterminer le mode de gestion qui s’adapte à votre cas, nous allons traiter des exemples spécifiques détaillant comment remplir les rôles principaux constituant chaque mode. Dans le chapitre suivant, nous traiterons de quelques modèles d’activité pour la contribution à un projet. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.drupal.org/user/register?destination=node/3266412 | Sign in to Drupal.org Drupal.org * Required fields Register to Drupal.org Username * Password * Confirm password * Email * First or given name Last name or surname « Back to Login Keycloak Identity and Access Management provided by Cloud-IAM. Cloud-IAM Trouble logging in? Email help@drupal.org with details. | 2026-01-13T09:29:41 |
https://www.drupal.org/user/register?destination=node/3463414/4 | Sign in to Drupal.org Drupal.org * Required fields Register to Drupal.org Username * Password * Confirm password * Email * First or given name Last name or surname « Back to Login Keycloak Identity and Access Management provided by Cloud-IAM. Cloud-IAM Trouble logging in? Email help@drupal.org with details. | 2026-01-13T09:29:41 |
https://www.lastpass.com/de/features/saas-monitoring | Herausforderungen bei der Zugriffsverwaltung - LastPass Zum Inhalt springen Blog Ressourcencenter Fallstudien Webinare Produktdemos Veranstaltungen Alle Ressourcen Trust Center Compliance Center Sicherheitsarchitektur LastPass University Produktdemos On-Demand-Demos von LastPass Business Report Mit aktueller Threat Intelligence immer einen Schritt voraus Support Hilfe Supportcenter Self-Service-Bibliothek mit Ressourcen und Leitfäden für alle LastPass-Produkte. Community-Forum Systemstatus Support kontaktieren Persönlicher Support für alle Kunden mit LastPass-Abonnement. LastPass-Apps herunterladen LastPass funktioniert auf allen Geräten. Vertrieb kontaktieren Anfrage an Vertrieb Mit dem Vertrieb chatten Demo anfordern Partner finden Anmelden DE English Español Deutsch Français Italiano Nederlands Português Gratis testen Warum LastPass? Überblick Warum LastPass? Sichere Passwörter erstellen und speichern – für Sie selbst, Ihr Team oder Unternehmen. Funktionsweise von LastPass (Englisch) Sich weniger Passwörter merken müssen und schnellere Logins – mit unserer Browsererweiterung. Sicherheitsarchitektur Dank Zero-Knowledge-Konzept bleiben Ihre Daten stets vertraulich – auch LastPass sieht sie nicht. LastPass vergleichen LastPass-Alternativen, LastPass-Abos, LastPass-Funktionen: alles Wichtige auf einen Blick Wichtige Funktionen Passwort-Management Speichern und automatisches Ausfüllen Passwortgenerator Passwortfreigabe Passkeys Neu Darkweb-Überwachung Sicherheits-Dashboard Alle Funktionen Personal kostenlos testen Kostenlose Testversion von LastPass Premium, keine Kreditkarte erforderlich. Business kostenlos testen Kostenlose Testversion von LastPass Business, keine Kreditkarte erforderlich. Vertrieb kontaktieren Unsere Experten beraten zu LastPass und unterstützen Sie bei der Einführung. LastPass-Apps herunterladen LastPass funktioniert auf allen Geräten. Privatanwender Abos für Privatanwender Privatanwender Passwörter auf allen Geräten synchronisieren, Passwortsicherheit und Datenschutzverletzungen überwachen und mehr. Families Premium-Passwortmanagement für Familien oder Gruppen mit bis zu 6 Personen. Abos vergleichen Für Einzelanwender Passwort-Vault Speichern und automatisches Ausfüllen Passkeys Neu Automatische Gerätesynchronisierung Notfallzugriff Freigabe privat genutzter Passwörter Alle persönlichen Funktionen Personal kostenlos testen Kostenlose 30-Tage-Testversion von LastPass Premium, keine Kreditkarte erforderlich. Families kostenlos nutzen Kostenlose 30-Tage-Testversion von LastPass Families, keine Kreditkarte erforderlich. Mit LastPass Free starten Basisfunktionen für das Passwort-Management, Nutzung auf einen Gerätetyp beschränkt. Business Business-Abos Business Für Unternehmen jeder Größe vom Start-up bis zum Großunternehmen. Business Max Einfacherer sicherer Zugriff und umfassende Admin-Kontrolle direkt vom Browser aus. Teams Für Teams, die zum ersten Mal einen Passwort-Manager einführen. MSP Sicherheit und Schutz für die Zugangsdaten Ihrer Kunden. Abos vergleichen Für Administratoren Benutzerverwaltung SaaS Monitoring SaaS Protect Neu Passkeys Neu Freigabe im Unternehmen Multifaktor-Authentifizierung Integrationen Single Sign-On Identitätsverwaltung Alle Business-Funktionen Lösungen nach Rolle Marketing Recht HR Geschäftsführung IT-Administratoren Alle Lösungen nach Rolle Business kostenlos testen Kostenlose Testversion von LastPass Business, keine Kreditkarte erforderlich. E-Book Wie LastPass die Compliance mit ASD Essential Eight unterstützt Produktupdate Mehr Kontrolle für Administratoren: LastPass stellt SaaS Protect vor Preise Partner LastPass-Partnerprogramm Überblick Partnerprogramm Treten Sie dem LastPass-Partnerprogramm bei, um Ihren Kunden einen größeren Mehrwert zu bieten. Managed-Service-Anbieter Wiederverkäufer Cloud-Marketplaces Technology-Alliance-Partner Anmeldung für Partner Kostenlose MSP-Testversion starten Erschließen Sie sich neue Einkommensquellen, indem Sie Sicherheitsdienste für Kunden in Ihr Portfolio aufnehmen. Partnerteam kontaktieren Sie brauchen Hilfe oder möchten LastPass-Partner werden? Sprechen Sie mit unserem Partnerteam. Partner finden Finden Sie zuverlässige LastPass-Partner für die Umsetzung Ihrer Sicherheitsinitiativen. Blog Ressourcencenter Fallstudien Webinare Produktdemos Veranstaltungen Alle Ressourcen Trust Center Compliance Center Sicherheitsarchitektur LastPass University Produktdemos On-Demand-Demos von LastPass Business Report Mit aktueller Threat Intelligence immer einen Schritt voraus Support Hilfe Supportcenter Self-Service-Bibliothek mit Ressourcen und Leitfäden für alle LastPass-Produkte. Community-Forum Systemstatus Support kontaktieren Persönlicher Support für alle Kunden mit LastPass-Abonnement. LastPass-Apps herunterladen LastPass funktioniert auf allen Geräten. Gratis testen Vertrieb kontaktieren Anfrage an Vertrieb Mit dem Vertrieb chatten Demo anfordern Partner finden Anmelden DE English Español Deutsch Français Italiano Nederlands Português Blog Ressourcencenter Fallstudien Webinare Produktdemos Veranstaltungen Alle Ressourcen Trust Center Compliance Center Sicherheitsarchitektur LastPass University Produktdemos On-Demand-Demos von LastPass Business Report Mit aktueller Threat Intelligence immer einen Schritt voraus Support Hilfe Supportcenter Self-Service-Bibliothek mit Ressourcen und Leitfäden für alle LastPass-Produkte. Community-Forum Systemstatus Support kontaktieren Persönlicher Support für alle Kunden mit LastPass-Abonnement. LastPass-Apps herunterladen LastPass funktioniert auf allen Geräten. LastPass kostenlos herunterladen Vertrieb kontaktieren Anfrage an Vertrieb Mit dem Vertrieb chatten Demo anfordern Partner finden Anmelden Administratorfunktionen Hochgradige App-Transparenz. Kontrolle auf allen Ebenen. Mit SaaS-Überwachung können Sie Sicherheitslücken schließen und Technologiekosten optimieren, da Sie umfassende Transparenz und Kontrolle über die gesamte SaaS-Nutzung Ihres Unternehmens erhalten. LastPass kostenlos testen Vertrieb kontaktieren Für den Test ist keine Kreditkarte erforderlich. Nach dem Testzeitraum kostet der Tarif „Business Max“ 9 US-Dollar/Monat. Ihr SaaS-Stack ist größer, als Sie denken Wenn die Technologie eines Unternehmens nicht von der IT verwaltet wird, kommt es zu einer unkontrollierten Verbreitung von SaaS-Lösungen, die Ihr Unternehmen Sicherheits- und Compliance-Risiken aussetzen und höhere Kosten verursachen. 62 % der Technologie wird von der IT verwaltet, der Rest sind nicht genehmigte Anwendungen und unkontrollierte KI-Agenten. > 4 Mio. USD betragen die durchschnittlichen Kosten eines Cyberangriffs im Zusammenhang mit Schatten-IT. > 50 % der Budgets werden von Unternehmen ohne Wissen der offiziellen IT-Abteilungen ausgegeben. Kontrolle über Ihre SaaS-Anwendungen Identifizierung nicht überprüfter Anwendungen Verschaffen Sie sich einen Überblick über versteckte IT/KI, indem Sie alle SaaS-Tools in Ihrem Tech-Stack erfassen – unabhängig davon, ob sie genehmigt sind oder nicht. Durchsetzung von Richtlinien Überwachen Sie App-Nutzung und Benutzeraktivitäten, um die Einhaltung von Sicherheitsrichtlinien sicherzustellen. Kostensenkung und Maximierung des App-Werts Identifizieren Sie doppelte, ungenutzte oder übermäßig bereitgestellte Apps. Einhaltung von Vorschriften Befolgen Sie gesetzliche und vertragliche Vorgaben, um Daten zu schützen, Geschäftsbeziehungen zu wahren und mögliche Bußgelder zu vermeiden. Absicherung gegen Ausfälle Ermitteln Sie alle SaaS-Apps für die Kontinuitätsplanung und verhindern Sie Datenverluste, indem Sie riskante Verhaltensweisen erkennen. LastPass kostenlos testen Demo ansehen Sichere SaaS-Apps? Transparenz ist der Schlüssel. SaaS Monitoring von LastPass erkennt, welche Apps Ihre Mitarbeiter im Unternehmen nutzen – auch nicht genehmigte Schatten-SaaS. SaaS Protect verwandelt diese Transparenz in Kontrolle. Sie können damit riskante Apps blockieren, Zugriffsrichtlinien durchsetzen und für den sicheren Zugriff auf die wirklich wichtigen Unternehmens-Apps sorgen. SaaS Protect erkunden SaaS-Überwachung Schritt für Schritt SaaS-Überwachung muss weder kompliziert noch kostspielig sein. Durch die Integration in die LastPass-Browsererweiterung erhalten Sie sofortigen Einblick in die App-Nutzung – ohne zusätzliche Software oder komplexe Implementierung. So funktioniert es: Aktivieren Sie die SaaS-Überwachung in wenigen Sekunden. Die Browser-Erweiterung verfolgt App-Anmeldungen. Sie sehen die unternehmensweite und individuelle App-Nutzung. LastPass kostenlos testen Vertrieb kontaktieren MEINUNGEN VON BRANCHENEXPERTEN Die Lösung für unkontrollierte Ausbreitung von SaaS und Schatten-IT Die Branchenexperten Todd Thieman von der Enterprise Strategy Group und Don McLennan, Chief Product Officer bei LastPass, erläutern die Herausforderungen der ungebremsten Ausbreitung von SaaS, deren Auswirkungen auf die Sicherheit und Möglichkeiten für Unternehmen, mit App-Überwachung wieder die Kontrolle zu erlangen. „SaaS-Anwendungen verbessern die Effizienz, werden jedoch häufig ohne IT-Überwachung eingeführt und können Sicherheitsrisiken bergen.“ - Todd Thiemann, Senior Analyst, Enterprise Strategy Group Mehr zu SaaS-Monitoring erfahren Video So gut wie SaaS-Monitoring ist nicht einmal Mr. Note-It-All.
Jetzt ansehen Report Volle Kontrolle über SaaS-Apps und mehr Sicherheit für KMUs Bericht herunterladen Datenblatt Alle Funktionen von SaaS-Monitoring ansehen Datenblatt ansehen Alle Ressourcen anzeigen Häufig gestellte Fragen Werden bei der SaaS-Überwachung alle von Mitarbeitern verwendeten Anwendungen überprüft? Nein, LastPass erfasst nicht alle von Mitarbeitern verwendeten Anwendungen. In den Berichten zur SaaS-Überwachung werden nur Anmeldungen bei SaaS-Anwendungen aufgeführt, die in der LastPass-Bibliothek für SaaS-Anwendungen enthalten sind. Persönliche Anmeldevorgänge von Mitarbeitern werden nicht aufgezeichnet. Wie funktioniert die SaaS-Überwachung? Im Backend erstellt LastPass eine Bibliothek mit SaaS-Anwendungen. Wenn ein Administrator eine zugehörige Richtlinie aktiviert und ein Mitarbeiter ein Formular ausfüllt oder sich bei einer Website anmeldet, erstellt LastPass ein Ereignis, sofern eine Übereinstimmung gefunden wird. Handelt es sich nicht um eine SaaS-Anwendung, wird kein Ereignis aufgezeichnet. Bei der SaaS-Überwachung wird also kein Ereignis erfasst, wenn ein Mitarbeiter tagsüber lediglich auf Facebook zugreift. Aus Sicht des Endbenutzers werden diese Daten über die LastPass-Browsererweiterung gesammelt, die bereits für alle Mitarbeiter installiert ist. Für die Erfassung von SaaS-Anwendungen ist also keine zusätzliche Agentensoftware erforderlich. Da Agenten unter Umständen schwer zu implementieren sind und Geräte verlangsamen, ist die LastPass-Erweiterung eine einfache und effiziente Möglichkeit, diese Daten zu erheben. Welche Berichte sind in der SaaS-Überwachung verfügbar? Die SaaS-Anwendungsüberwachung bietet Ihnen zwei grundlegende Berichtsperspektiven: Dashboard zur Erkennung von Anwendungen In diesem Dashboard können Sie alle Anwendungen, auf die in Ihrem Unternehmen zugegriffen wird, auf einen Blick sehen: Sie erfahren, um welche Art von Apps es sich handelt und wie darauf zugegriffen wird (SSO, Kennwörter), und erhalten Einblicke in Nutzungsraten, ungenutzte Apps, neue Apps und andere Risiken. Über dieses Dashboard können Administratoren Apps blockieren, einschränken oder genehmigen. Dashboard für App-Benutzer Sie können sofort alle Mitarbeiterkonten in Ihrem Unternehmen und die damit verbundenen Anwendungen einsehen, einschließlich einer Aufschlüsselung der Gesamtzahl der Anwendungen, der mit einzelnen Personen verbundenen Sicherheitsprobleme und der letzten Anmeldeaktionen. Diese Benutzerdaten können Sie anschließend nutzen, um Sicherheits- und Zweckfragen im Zusammenhang mit den einzelnen Apps zu klären. Bei welchen LastPass-Tarifen ist die SaaS-Überwachung enthalten? Die Funktion und Richtlinie für die SaaS-Überwachung ist im Business Max -Tarif von LastPass verfügbar. Sie stehen auch während des 14-tägigen Testzeitraums für Business zur Verfügung. Ihre Frage ist nicht dabei? Besuchen Sie das Supportcenter . Erste Schritte mit LastPass Business LastPass kostenlos testen Vertrieb kontaktieren Für die 14-tägige Testversion ist keine Kreditkarte erforderlich. Produkte Startseite Was ist ein Passwort-Manager? Warum LastPass? Wie sorgt LastPass für Sicherheit? So funktioniert LastPass Preise Für Unternehmen Für Teams Für Familien Für Einzelanwender Für MSPs LastPass vergleichen Sicherheitsfunktionen Alle Funktionen Lösungen SaaS Protect Neu Passwortfreigabe Sicherer Zugriff Authentifizierung Integrationen Für große Unternehmen Für kleine Unternehmen Für Marketingteams Für die Rechtsbranche Für HR-Teams Für Finanzdienstleister Für Professional Services Für Bildungseinrichtungen Alle Lösungen Ressourcen Ressourcencenter Fallstudien Veranstaltungen Webinare On-Demand-Demos Trust Center Compliance Center LastPass University Passwortgenerator Benutzernamengenerator LastPass Authenticator Artikel zu Cybersicherheit Alle Blogartikel Support Supportcenter Reddit-Community Community-Forum Dienststatus Mein Konto Meldung von Sicherheitslücken Vault-Login Login für Administratoren Support kontaktieren LastPass herunterladen Kostenlose Testversion starten Google Play App Store Browsererweiterungen Unternehmen Über uns Neue Stellenangebote! Führungsebene Newsroom Legal Center Compliance Kontakt Partner Überblick Partnerprogramm MSP Wiederverkäufer Partner finden Anmeldung für Partner Affiliate-Partner Vertrieb kontaktieren Chatten mit einem Vertriebsexperten Vertrieb kontaktieren Erweiterung installieren Download © 2026 LastPass US LP. Alle Rechte vorbehalten. Datenschutzhinweis Nutzungsbedingungen Impressum Cookie-Einstellungen Ihre Datenschutzoptionen Deutsch English Español Deutsch Français Italiano Nederlands Português | 2026-01-13T09:29:41 |
https://citl.illinois.edu/explore-our-spaces | Explore Our Spaces | Center for Innovation in Teaching & Learning Skip to main content University of Illinois Urbana-Champaign Center for Innovation in Teaching & Learning Search About Who We Are Row Wrapper Column Overview Current Events Special Events Careers Column CITL Directory CITL Fellows How We Can Help How We Can Help Row Wrapper Column Overview Search by Audience & Service Enrich Your Teaching Enhance Your Teaching Skills Promote Student Engagement Universal Design for Learning Make Your Course Accessible (MYCA) Foster Inclusion Graduate Academy for College Teaching Student Resources Achieve Academic Success Take Care of Your Wellbeing Internships Column Create Online Courses Develop a New Program with CITL Develop a New Course with CITL Update an Existing Course Access Self-Service Kits Instructional Support Broadcast & Record Events Exam Scoring Services Slate CRM Systems Column Collect & Analyze Data Finding Data Survey Research Consulting & Training I-STEM Placement & Proficiency Current Cutoffs P&P FAQs Ask a Question Explore Our Spaces Explore Our Spaces Row Wrapper Column Overview Innovation Studio X3 Studio CITL IDEASpace Media Recording Spaces Innovate With Us Innovate With Us Row Wrapper Column Overview Explore, Develop, and Pilot New Strategies Learn and Apply AI & XR Solutions Generative Artificial Intelligence Immersive Technology Teaching Evaluation Teaching Evaluation Row Wrapper Column Overview Campus Teaching Evaluation System Self Evaluation Feedback on the Learning Experience (FLEX) Column Longitudinal Teaching Profiles Share Your Experience Share Your Experience Row Wrapper Column Overview CITL Podcast Instructor Voices Student Voices Newsletter Archive Ask a Question Column Overview Innovation Studio X3 Studio CITL IDEASpace Media Recording Spaces Interrupt Smarter The Center for Innovation in Teaching and Learning (CITL) offers dynamic, tech-forward spaces that empower educators and students to explore, create, and transform learning experiences. Whether you're new to educational technology or an experienced innovator, CITL’s Innovation Spaces provide the tools and support to bring your ideas to life. Facilities include the Innovation Studio , featuring VR headsets, gaming computers, 3D printers, and AI tools; the Virtual Reality Lab for extended reality research; and Catalyst Classroom , where instructors experiment with new teaching methods. The Media Hub supports course design and media skill development, while the Podcast Recording Studio and Instructor Recording Studio offer professional environments for content creation. The Lightboard Studio enables engaging micro-lecture production with a chalkboard-style interface. Each space is supported by CITL experts, fostering creativity, collaboration, and pedagogical advancement. Spaces for every discipline Innovation Studio Visit the Innovation Studio , a premier campus space for introductory hands-on exploration of the latest technologies impacting teaching and learning including generative AI, virtual and augmented reality, 3D printing, 360 photography, gaming, and more. Learn More about the Innovation Studio X3 Studio (Experience, Explore, and Excel) A small research and design lab, where people can reserve time, space, and computing to work on virtual and extended reality research and projects. It also houses a green screen and streaming station for broadcasting and photography. Learn More about the X3 Studio Exam Scoring Services Instructors can use our machine-scannable answer sheets and have them scored and analyzed at no cost. We offer three analyses: the Total Report, the Item Analysis, and the Error Report. Located in 151A Armory Building, on the north side of the building, Exam Scoring Services is available from 8:30 am-12 pm and 1-5 pm Monday through Friday. Learn More about Exam Scoring Services CITL IDEASpace Where bold teaching ideas take shape and grow. Learn More about the CITL IDEASpace Media Hub Learn new skills in our multi-use space—including media hardware that maximizes your online presence (without breaking the bank)—and develop, design or redesign a course with assistance from CITL teaching and learning experts. Learn More about the Media Hub Instructor Studio The perfect space to learn the basics and record on your own. Available to all University faculty, instructors, TAs, and teaching staff, this smaller space is equipped with two setups: stage lighting and desk recording. Learn More about the Instructor Studio Lightboard Studio A dedicated studio for producing instructional video micro-lectures, the CITL’s Lightboard Studio enables instructors comfortable with chalkboard instruction to produce videos with a similar style. We’ll help set up any projected presentation aids, prepare overview graphics, and turn it around quickly. Learn More about the Lightboard Studio Got a Vision? We'll help you make it happen. Get in touch Center for Innovation in Teaching & Learning 505 Armory Avenue | Champaign, IL 61820 Phone: 217.333.1462 Email: citl-info@illinois.edu CITL About How We Can Help Innovate With Us Teaching Evaluation Calendar Contact Us Programs Illinois Online Illinois Remote Explore Campus University Admissions Careers at Illinois University News Visit Campus Connect with Illinois University Alumni Giving at Illinois University Calendars University Directory Access University Resources Emergency Services McKinley Health Center Connie Frank CARE Center University Library About Cookies Privacy Policy Copyright Accessibility | 2026-01-13T09:29:41 |
https://lwn.net/Articles/lsfmm2022/#t | The 2022 Linux Storage, Filesystem, Memory-Management, and BPF Summit [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register The 2022 Linux Storage, Filesystem, Memory-Management, and BPF Summit Did you know...? LWN.net is a subscriber-supported publication; we rely on subscribers to keep the entire operation going. Please help out by buying a subscription and keeping LWN on the net. By Jonathan Corbet May 4, 2022 The Linux Storage, Filesystem, Memory-Management, and BPF Summit (LSFMM) has long been one of the key events for many core kernel developers. The last LSFMM event, though, was held in the innocent, pre-pandemic days of early 2019. After three years, it finally was possible to hold an in-person gathering at beginning of May 2022 in Palm Springs, California, USA. As usual, LWN was there. Plenary sessions There were no truly plenary sessions at LSFMM 2022, since the BPF group was always on its own schedule. The sessions listed below covered the storage, filesystem, and memory-management tracks. A memory-folio update : the current status and future direction of the folio project. Remote participation at LSFMM : a discussion with the remote participants on what worked—and didn't—for them. Joint filesystem/memory-management sessions Coping with hardware-poisoned page-cache pages : What should the kernel do when memory errors corrupt a page in the page cache? Dealing with negative dentries : how the kernel can manage the cache of file-name lookup failures better. Recent RCU changes : a quick overview of read-copy-update (RCU) followed by descriptions of some of the bigger changes that have gone into it over the last few years. Page pinning and filesystems : this year's discussion on how to solve the problems with get_user_pages() . Sharing memory for shared file extents : exploring a way to stop wasting memory with extents that are shared between multiple files. Joint storage/filesystem sessions Unique identifiers for NFS : how to create and manage unique IDs needed by NFS. Challenges with fstests and blktests : testing for filesystems and the block layer is an area that needs more work—and collaboration. Adding an in-kernel TLS handshake : what is the best way to add support for initiating a TLS handshake from the kernel? Maintainers don't scale : a discussion on some of the challenges faced by Linux kernel maintainers. Best practices for fstests : how to collaborate on better testing infrastructure for filesystems. ioctl() forever? : a session looking at some of the problems with using the ioctl() system call along with a few alternatives to it. Zoned storage : the challenges with supporting zoned storage and sequential-write-only zones in particular. A discussion on readahead : how much data should the kernel be speculatively reading ahead into the page cache? Memory-management sessions Ways to reclaim unused page-table pages : a lot of the memory used to hold page tables is not needed in that role and could be put to better uses. The ongoing search for mmap_lock scalability : the 2022 version of the perennial page-fault scalability topic, perhaps with some solutions on the horizon this time. Improving memory-management documentation : how to capture some of the "tribal knowledge" behind memory management and make it available to more developers. The state of memory-management development : Andrew Morton describes some changes to how memory-management patches are handled. Seeking an API for protection keys supervisor : protection keys can help to harden the kernel, but the best way of managing them is still unclear. Better tools for out-of-memory debugging : understanding out-of-memory problems is not easy; what can be done to improve the situation? Solutions for direct-map fragmentation : a number of new technologies need to carve pages out of the kernel's direct map; how can that functionality be supported without hurting performance? CXL 1: Management and tiering : the first three sessions on the Compute Express Link and how it should be managed by the Linux kernel. Proactive reclaim : there are reasons to want to reclaim memory in a more proactive manner, but it is not clear how any such feature should be controlled. Merging the multi-generational LRU : an extended discussion concluded that the time has come to merge this huge change, but some open questions remain. Sharing page tables with mshare() : page tables are not normally shared between processes, which can lead to massive overhead in situations where memory is highly shared. This session discussed a proposal for a new system call to enable page-table sharing between cooperating processes. CXL 2: Pooling, sharing, and I/O-memory resources : CXL memory can be highly dynamic, making it hard to support in the kernel. Cleaning up dying control groups, 2022 edition : progress has been made with regard to getting dying memory control groups out of the way, but the problem is not yet fully solved. get_user_pages() and COW, 2022 edition : the long slog toward making page pinning work properly in the kernel. Fixing a race in hugetlbfs : using hugetlbfs can save a lot of page-table overhead for massively shared regions, but the implementation currently has an unpleasant and difficult-to-fix bug. Preserving guest memory across kexec : a proposed mechanism to allow a host kernel to be updated while minimally disturbing guest virtual machines. Filesystem sessions Changing filesystem resize patterns : filesystems that are created small, but continually resized to be much larger, are causing some headaches. The netfslib helper library : a relatively new library to collect up common operations for network filesystems. Dynamically allocated pseudo-filesystems : a discussion on the right path for adding a general facility that would allow pseudo-filesystems (e.g. tracefs, debugfs) to reduce their memory footprint by allocating inodes and directory entries only when needed. Bringing bcachefs to the mainline : The bcachefs filesystem may be getting close to ready for merging. Snapshots, inodes, and filesystem identifiers : Filesystems that support snapshots, thus duplicate inode numbers, can be problematic. Change notifications for network filesystems : how to allow Linux clients to monitor additions, deletions, and other changes in network filesystems. Making O_TMPFILE atomic (and statx() additions) : two half-sessions looking at features that could be added for filesystems. ID-mapped mounts : a discussion on the relatively new ID-mapped mounts feature for Linux filesystems. Filesystems, testing, and stable trees : the stable and, especially, LTS trees need more filesystem testing, but it is currently hard to do. Retrieving kernel attributes : a discussion on a proposed interface for getting information out of the kernel using the extended-attribute API. Disabling an extent optimization : filesystems do not necessarily maintain holes in files as holes , rather than just regions with zeroes, which can lead to some problems. Other resources Christoph Hellwig has posted a summary of the action items from the BPF-track session on standardization. The obligatory group photo We would like to thank LWN subscribers for supporting our travel to and reporting from LSFMM 2022. Index entries for this article Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:41 |
https://git-scm.com/book/tr/v2/Da%c4%9f%c4%b1t%c4%b1k-Git-Da%c4%9f%c4%b1t%c4%b1k-%c4%b0%c5%9f-Ak%c4%b1%c5%9flar%c4%b1 | Git - Dağıtık İş Akışları About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Başlangıç 1.1 Sürüm Denetimi 1.2 Git’in Kısa Tarihçesi 1.3 Git Nedir? 1.4 Komut Satırı 1.5 Git’i Yüklemek 1.6 Git’i İlk Defa Kurmak 1.7 Yardım Almak 1.8 Özet 2. Git Temelleri 2.1 Bir Git Reposu Oluşturma/Kopyalama 2.2 Değişikliklerin Repoya Kaydedilmesi 2.3 Katkı Geçmişini Görüntüleme 2.4 Değişiklikleri Geri Alma 2.5 Uzak Repo ile Çalışmak 2.6 Etiketleme 2.7 Komut Kısayolu (Alias) Ayarlama 2.8 Özet 3. Git Dalları 3.1 Dallar 3.2 Kısaca Dallandırma ve Birleştirme Temelleri 3.3 Dal Yönetimi 3.4 İş Akışı Dallandırması 3.5 Uzak Dallar 3.6 Yeniden Temelleme (rebase) 3.7 Özet 4. Bir Sunucuda Git Kurma 4.1 İletişim Kuralları (Protocols) 4.2 Bir Sunucuda Git Kurma 4.3 SSH Ortak Anahtarınızı Oluşturma 4.4 Sunucu Kurma 4.5 Git Cini (Daemon) 4.6 Akıllı HTTP 4.7 GitWeb 4.8 GitLab 4.9 Üçüncü Taraf Barındırma (Hosting) Seçenekleri 4.10 Özet 5. Dağıtık Git 5.1 Dağıtık İş Akışları 5.2 Projenin Gelişiminde Rol Almak 5.3 Bir Projeyi Yürütme 5.4 Özet 6. GitHub 6.1 Bir Projeye Katkıda Bulunmak 6.2 Proje Bakımı 6.3 Kurumsal Yönetim 6.4 GitHub’ı otomatikleştirme 6.5 Özet 7. Git Araçları 7.1 Düzeltme Seçimi 7.2 Etkileşimli İzlemleme (Staging) 7.3 Saklama ve Silme 7.4 Çalışmanızı İmzalama 7.5 Arama 7.6 Geçmişi Yeniden Yazma 7.7 Reset Komutunun Gizemleri 7.8 İleri Seviye Birleştirme 7.9 Rerere 7.10 Git’le Hata Ayıklama 7.11 Alt Modüller 7.12 Demetleme (Bundling) 7.13 Git Nesnesini Değiştirme 7.14 Kimlik Bilgisi Depolama 7.15 Özet 8. Git’i Özelleştirmek 8.1 Git Yapılandırması 8.2 Git Nitelikleri 8.3 Git Kancaları (Hooks) 8.4 Bir Örnek: Mecburi Git Politikası 8.5 Özet 9. Git ve Diğer Sistemler 9.1 İstemci Olarak Git 9.2 Git’e Geçiş 9.3 Özet 10. Dahili Git Ögeleri 10.1 Tesisat ve Döşeme (Plumbing ve Porcelain) 10.2 Git Nesneleri 10.3 Git Referansları 10.4 Packfiles 10.5 Refspec 10.6 Transfer Protokolleri 10.7 Bakım ve Veri Kurtarma 10.8 Ortam Değişkenleri 10.9 Özet A1. Ek bölüm A: Diğer Ortamlarda Git A1.1 Görsel Arayüzler A1.2 Visual Studio ile Git A1.3 Visual Studio Code ile Git A1.4 Eclipse ile Git A1.5 Sublime Text ile Git A1.6 Bash ile Git A1.7 Zsh ile Git A1.8 PowerShell ile Git A1.9 Özet A2. Ek bölüm B: Git’i Uygulamalarınıza Gömmek A2.1 Git Komut Satırı A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Ek bölüm C: Git Komutları A3.1 Kurulum ve Yapılandırma Komutları A3.2 Proje Oluşturma Komutları A3.3 Kısaca Poz (Snapshot) Alma A3.4 Dallandırma ve Birleştirme Komutları A3.5 Projeleri Paylaşma ve Güncelleme Komutları A3.6 İnceleme ve Karşılaştırma Komutları A3.7 Hata Ayıklama (Debugging) Komutları A3.8 Yamalama (Patching) A3.9 E-Posta Komutları A3.10 Harici Sistemler A3.11 Yönetim A3.12 Tesisat (Plumbing) Komutları 2nd Edition 5.1 Dağıtık Git - Dağıtık İş Akışları Artık diğer geliştiricilerle ortak bir proje üzerinde çalışırken kodlarınızı paylaşmak üzere kurulmuş bir uzak Git deposuna sahipsiniz ve yerel bir iş akışında temel Git komutlarına aşina olduğunuz için, Git’in size sunduğu dağıtık iş akışlarını nasıl kullanacağınıza bakacaksınız. Bu bölümde, dağıtık bir ortamda bir katkı sağlayıcı ve proje yöneticisi olarak Git ile nasıl çalışılacağını göreceksiniz. Yani, bir projeye başarılı bir şekilde kod eklemeyi ve hem siz hem de proje yürütücüsü için sürecin mümkün olduğunca kolay olmasını sağlamayı öğreneceksiniz. Ayrıca birçok geliştiricinin katkıda bulunduğu bir projeyi başarılı bir şekilde sürdürmeyi de öğreneceksiniz. Dağıtık İş Akışları Merkezi Sürüm Denetim Sistemleri (CVCS) ile karşılaştırıldığında, Git’in dağıtık yapısı, geliştiricilerin projelerde nasıl işbirliği yapacakları konusunda çok daha esnek olmalarını sağlar. Merkezi sistemlerde, her geliştirici merkezi bir dağıtım göbeğiyle (hub) neredeyse eşit olarak çalışan bir düğümdür (node). Ancak, Git’te her geliştirici potansiyel olarak hem bir düğüm hem de bir göbektir: yani, her geliştirici hem diğer repolara kod katkısında bulunabilir, hem de diğerlerinin çalışmalarını temel alabilecekleri ve katkıda bulunabilecekleri bir açık repoyu yürütebilir. Bu, projeniz ve/veya ekibiniz için geniş bir olası iş akışı yelpazesi sunar, bu esneklikten faydalanabileceğiniz birkaç yaygın paradigmayı ele alacağız. Her tasarımın güçlü yanlarını ve olası zayıflıklarını inceleyeceğiz. Kullanım amacıyla bunlardan tek birini seçebilir veya her birinden özellikleri bazı özellikleri alarak bir karma elde edebilirsiniz. Merkezi İş Akışları Merkezi sistemlerde genellikle tek bir işbirliği modeli bulunur: merkezi iş akışı. Merkezi bir dağıtım göbeği veya repo , kodları kabul edebilir ve herkes çalışmalarını onunla eşitler. Geliştiriciler (o göbeğin tüketicileri olan) düğümlerdir ve işlerini bu merkezi konumla eşitlerler. Görsel 54. Merkezi iş akışı. Bunun anlamı, iki geliştiricinin göbekten (hub/repo) kopyaladığı ve her ikisinin de değişiklikler yaptığı durumda, değişikliklerini ilk gönderen birinci geliştiricinin bunu herhangi bir sorun yaşamadan yapabileceğidir. İkinci geliştirici değişiklikleri göndermeden önce, birinci geliştiricinin çalışmasını birleştirmelidir. Böylece birinci geliştiricinin değişikliklerini üzerine yazmamış olur. Bu kavram, Subversion (veya herhangi bir başka CVCS) gibi Git’te de geçerlidir ve bu model Git’te mükemmel bir şekilde çalışır. Şirketiniz veya ekibinizde merkezi iş akışından zaten memnunsanız, Git’i kullanarak bu iş akışını kolayca sürdürebilirsiniz. Tek bir repo kurun ve ekibinizdeki herkese itme erişimi verin. Git kullanıcıların birbirlerinin üstüne yazmasına izin vermez. Ahmet ve Mehmet’in aynı anda çalışmaya başladıklarını varsayalım. Ahmet değişikliğini tamamlar ve onu sunucuya iter. Sonra Mehmet değişikliklerini iterlemeye çalışır, ancak sunucu bunları reddeder. Ona, ileri alınmayan değişikliklerini iterlemeye çalıştığı ve bunu yapamayacağı söylenir, çünkü önce çekme ve birleştirme yapması gerekmektedir. Bu iş akış modeli, birçok insanın aşina olduğu ve rahat hissettiği bir kavram olduğu için çoğu kişiye çekici gelir. Bu sadece küçük ekiplerle sınırlı değildir. Git’in dallanma modeliyle, yüzlerce geliştiricinin aynı anda onlarca dal üzerinde başarılı bir şekilde çalışması mümkündür. Birleşme Yöneticisi İş Akışı Çünkü Git, birden çok uzak repoya sahip olmanıza izin verir ve her geliştiricinin kendi açık reposuna yazma erişimi ve diğer herkesin okuma erişiminin olduğu bir iş akışına sahip olmanız mümkündür. Bu senaryo genellikle, "resmi" projeyi temsil eden kanonik bir repo içerir. Bu projeye katkıda bulunmak için, projenin kendi açık kopyanızı oluşturur ve değişikliklerinizi ona itersiniz. Daha sonra, ana projenin bakıcısına değişikliklerinizi çekmesi için bir istek gönderebilirsiniz. Proje yürütücüsü daha sonra; reponuzu bir uzak repo olarak ekleyebilir, değişikliklerinizi yerel olarak test edebilir, bunları kendi dalına birleştirebilir ve reposuna geri itebilir. İşlem şu şekilde çalışır: Süreç şöyle ilerler (bkz Birleşme yöneticisi iş akışı. ): Proje yürütücüsü kendi acık reposuna iter. Bir katkılayıcı bu repoyu kopyalar ve değişiklikler yapar. Katkılayıcı bunu kendi açık kopyasına iter. Katkılayıcı yürütücüye değişiklikleri çekmesi için bir e-posta gönderir. Yürütücü katkıcının reposunu bir uzak repo olarak ekler ve yerel olarak birleştirir. Yürütücü birleştirilen değişiklikleri ana repoya iter. Görsel 55. Birleşme yöneticisi iş akışı. Bu, GitHub veya GitLab gibi dağıtım-göbeği tabanlı araçlarla çok yaygın bir iş akışıdır. Burada bir projeyi çatallamak (dal açmak) ve değişikliklerinizi herkesin görebilmesi için dalınıza itmek çok kolaydır. Bu yaklaşımın başlıca avantajlarından biri, ana repo yürütücüsünün herhangi bir zamanda değişikliklerinizi alabilmesidir. Katkılayıcılar değişikliklerinin projeye dahil edilmesini beklemek zorunda değillerdir: her taraf kendi hızında çalışabilir. Diktatör ve Yardımcılar İş Akışı Bu, çoklu repo iş akışının bir türüdür. Genellikle, Linux çekirdeği gibi, yüzlerce katılımcısı olan büyük projeler tarafından kullanılır. Çeşitli birleşim yöneticileri belirli repo parçalarından sorumludur ve bunlara yardımcılar denir. Tüm yardımcılar, "benevolent dictator" (yardımsever diktatör) olarak bilinen bir birleşim yöneticisine sahiptir. Tüm yardımcıların bu yardımsever diktatörün kendi dizininden referans repoya ittiği kodu çekmesi gereklidir. Süreç şöyle işler (bkz. Yardımsever diktatör iş akışı. ): Normal geliştiriciler tematik dallarda çalışır ve çalışmalarını master üzerine temeller. master dalı yöneticinin ittiği referans reposunun dalıdır. Yardımcılar, geliştiricilerin konu dallarını kendi master dallarına birleştirir. Diktatör, yardımcıların master dallarını kendi master dalına birleştirir. Son olarak, diktatör bu master dalını referans reposuna iter, böylece diğer geliştiriciler bunun üzerine temelleme yapabilir. Görsel 56. Yardımsever diktatör iş akışı. Bu tür bir iş akışı yaygın değildir, ancak çok büyük projelerde veya yüksek derecede hiyerarşik ortamlarda faydalı olabilir. Proje liderine (diktatöre) projenin büyük kısmını devretmesine ve bunları birleştirmeden önce bir çok noktada geniş kod altkümeleri toplamasına olanak tanır. İş Akışı Özeti Bunlar, Git gibi bir dağıtılmış sistemle mümkün olan bazı yaygın olarak kullanılan iş akışlarıdır, ancak gördüğünüz gibi, gerçek dünya iş akışınıza uyacak şekilde birçok değişiklik yapılabilir. Umarım artık sizin için hangi iş akışı karmasının daha uygun olduğunu belirleyebilirsiniz. Bir sonraki bölümde bir projeye katkıda bulunmanın ana örüntüleri hakkında daha fazla bilgi sahibi olacak ve farklı iş akışları oluşturmak için ana rollerini nasıl gerçekleştireceğiniz hakkında daha belirgin örnekler göreceksiniz. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://policies.google.com/terms?hl=pt-BR | Termos de Serviço do Google – Privacidade & Termos – Google Privacidade & Termos Privacidade & Termos Pular para o conteúdo principal Fazer login Visão geral Política de Privacidade Termos de Serviço Tecnologias Perguntas frequentes Privacidade & Termos Visão geral Política de Privacidade Termos de Serviço Atualizações Definições Lista de serviços e termos adicionais específicos do serviço Como o Google lida com solicitações governamentais de informações de usuários 위치정보서비스 및 위치기반서비스 이용약관 Tecnologias Perguntas frequentes Privacidade & Termos Privacidade & Termos Privacidade & Termos Visão geral Política de Privacidade Termos de Serviço Tecnologias Perguntas frequentes Conta do Google Termos Introdução Seu relacionamento com o Google Usando os serviços do Google Conteúdo nos serviços do Google Software nos serviços do Google Em caso de problemas ou discordâncias Sobre estes termos Atualizações Definições Lista de serviços e termos adicionais específicos do serviço Como o Google lida com solicitações governamentais de informações de usuários 위치정보서비스 및 위치기반서비스 이용약관 Termos de Serviço do Google Em vigor a partir de 22 de maio de 2024 | Versões arquivadas | Fazer o download do PDF Versão específica: Coreia do Sul O que estes termos cobrem Sabemos que é tentador pular estes Termos de Serviço, mas é importante estabelecer o que você pode esperar de nós ao usar os serviços do Google e o que esperamos de você. Estes Termos de Serviço refletem a maneira como os negócios do Google funcionam , as leis que se aplicam à nossa empresa e determinados pontos em que sempre acreditamos . Como resultado, estes termos ajudam a definir a relação do Google com você na medida da sua interação com os nossos serviços. Por exemplo, estes termos incluem as seguintes seções: O que você pode esperar de nós , que descreve o modo como fornecemos e desenvolvemos nossos serviços. O que esperamos de você , que estabelece certas regras para usar nossos serviços. Conteúdo nos serviços do Google , que descreve os direitos de propriedade intelectual com relação ao conteúdo que você encontra nos nossos serviços, seja ele pertencente a você, ao Google ou a outras pessoas. Em caso de problemas ou discordâncias , que descreve outros direitos legais que você tem e o que esperar caso estes termos sejam violados Entender estes termos é importante porque, ao acessar ou usar nossos serviços, você está concordando com eles. Além destes termos, também publicamos uma Política de Privacidade . Embora ela não faça parte destes termos, recomendamos que você a leia para entender melhor como pode atualizar, gerenciar e excluir suas informações . Termos Provedora de serviços Os serviços do Google que você pode contratar são fornecidos por: Google LLC organizada de acordo com as leis do estado de Delaware, EUA, e operada de acordo com as leis dos EUA 1600 Amphitheatre Parkway Mountain View, Califórnia 94043 EUA Restrições de idade Se você está abaixo da idade exigida para gerenciar sua própria Conta do Google , é necessário ter a permissão do seu pai/mãe ou responsável legal para usar uma conta. Peça para seu pai/mãe ou responsável legal ler estes termos com você. Se você é um responsável legal ou pai/mãe e permite que uma criança use os serviços , estes termos se aplicam a você e você é responsável pelas atividades dessa criança nos serviços. Alguns serviços do Google têm restrições de idade complementares, de acordo com o descrito nos termos adicionais específicos do serviço e nas políticas deles. Índice Introdução Seu relacionamento com o Google Usando os serviços do Google Conteúdo nos serviços do Google Software nos serviços do Google Em caso de problemas ou discordâncias Sobre estes termos Seu relacionamento com o Google Estes termos ajudam a definir o relacionamento entre você e o Google. Quando falamos de "Google", "nós", "nosso" ou "nossa", estamos nos referindo à Google LLC e às afiliadas dela . De modo geral, permitimos que você acesse e use nossos serviços quando concorda em seguir estes termos, que refletem o modo como as empresas do Google funcionam e como nós ganhamos dinheiro . O que você pode esperar de nós Fornecimento de uma grande variedade de serviços úteis Fornecemos uma grande variedade de serviços que estão sujeitos a estes termos, incluindo: apps e sites, como a Pesquisa e o Maps; plataformas, como o Google Shopping; serviços integrados, como o Maps incorporado em apps ou sites de outras empresas; dispositivos, como o Google Nest e Pixel. Muitos desses serviços também incluem conteúdo que pode ser visto por streaming ou com o qual você pode interagir. Nossos serviços são feitos para operar em conjunto, facilitando a alternância entre atividades. Por exemplo, se um evento no Google Agenda inclui um endereço, você pode clicar no endereço para que o Maps mostre como chegar até ele. Desenvolvimento, melhorias e atualizações dos serviços do Google Estamos sempre desenvolvendo novos recursos e tecnologias para melhorar nossos serviços. Por exemplo, usamos inteligência artificial e aprendizado de máquina para oferecer traduções simultâneas, além de melhorar a detecção e o bloqueio de spam e malware. Como parte dessa melhoria contínua, às vezes adicionamos ou removemos recursos e funcionalidades, aumentamos ou diminuímos limites para nossos serviços e começamos a oferecer novos serviços ou deixamos de oferecer os antigos. Quando um serviço exigir ou incluir um software disponível para download ou pré-carregado, esse software poderá ser atualizado automaticamente no seu dispositivo se uma nova versão ou recurso estiver disponível. Alguns serviços permitem que você ajuste suas configurações de atualização automática. Mantemos um rigoroso programa de pesquisa de produtos. Por isso, antes de mudarmos um serviço ou pararmos de oferecê-lo, consideramos cuidadosamente seus interesses como usuário, suas expectativas razoáveis e o possível impacto sobre você e sobre outras pessoas. Só mudamos serviços ou deixamos de oferecê-los por razões legítimas, como para melhorar o desempenho ou a segurança, para obedecer à lei, para evitar atividades ilegais ou abusos, para refletir desenvolvimentos técnicos ou porque um recurso ou serviço já não é tão usado ou econômico o suficiente para ser oferecido. Se fizermos mudanças que impactem negativamente seu uso dos nossos serviços ou se pararmos de oferecer um serviço, enviaremos um aviso com certa antecedência, salvo em situações urgentes, como para evitar abusos, responder a requisitos legais ou resolver problemas técnicos ou de segurança. Também daremos a você a oportunidade, sujeita à legislação e às políticas aplicáveis, de exportar seu conteúdo da Conta do Google usando o Google Takeout . O que esperamos de você Cumprimento destes termos e dos termos adicionais específicos do serviço A permissão que concedemos a você para acessar e usar nossos Serviços permanecerá enquanto você obedecer: a estes termos; aos termos adicionais específicos do serviço , o que pode, por exemplo, incluir restrições de idade complementares. Também disponibilizamos várias políticas, Centrais de Ajuda e outros recursos para responder a perguntas comuns e definir expectativas sobre o uso dos nossos serviços. Esses recursos incluem nossa Política de Privacidade , a Central de Ajuda de direitos autorais , a Central de segurança , a Central de Transparência e outras páginas que podem ser acessadas pelo nosso site de políticas . Também podemos fornecer instruções e avisos específicos nos nossos serviços, como caixas de diálogo que alertam você sobre informações importantes. Apesar de darmos a você permissão para usar nossos serviços, mantemos todos os direitos de propriedade intelectual que detemos sobre eles. Respeito às outras pessoas Queremos manter um ambiente respeitável para todo mundo. Isso significa que você precisa seguir estas regras básicas de conduta: Obedecer às leis aplicáveis, incluindo controle de exportação, sanções e tráfico humano Respeitar os direitos de terceiros, incluindo direitos de privacidade e de propriedade intelectual Não prejudicar nem abusar de outras pessoas ou de si mesmo (nem ameaçar ou incentivar abuso ou danos), por exemplo, enganando, fraudando, falsificando ilegalmente uma identidade, difamando ou praticando bullying, assédio ou perseguição contra outras pessoas Nossos termos e políticas adicionais específicos do serviço , como a Política de uso proibido da IA generativa , fornecem mais detalhes sobre a conduta apropriada que todos que usam os serviços devem seguir. Se você encontrar outras pessoas que não estejam seguindo essas regras, muitos dos nossos serviços permitem que você denuncie casos de abuso . Se tomarmos providências com relação a uma denúncia de abuso, também forneceremos o processo descrito na seção Tomando providências em caso de problemas . Não abuse dos nossos serviços A maioria das pessoas que acessa ou usa nossos serviços entende as regras gerais que mantêm a Internet segura e aberta. Infelizmente, um pequeno número de pessoas não respeita essas regras. Por isso, elas estão descritas aqui para proteger nossos serviços e usuários contra abusos. Com isso em mente: Não é permitido abusar, prejudicar, interferir ou interromper nossos serviços ou sistemas, por exemplo: introduzindo malware; enviando spam, invadindo ou burlando nossos sistemas ou medidas de proteção; executando jailbreak, comandos maliciosos ou injeções de comando, exceto como parte dos nossos programas de teste de segurança e bugs ; acessando ou usando nossos serviços ou conteúdo de maneira fraudulenta ou formas enganosas, como para: phishing; criação de contas ou conteúdo falsos, incluindo avaliações falsas; indução de pessoas a pensar que conteúdo de IA generativa foi criado por uma pessoa; fornecimento de serviços que parecem vir de você (ou de outra pessoa) quando, na verdade, são nossos, oferecendo serviços que parecem vir de nós quando, na verdade, não vêm; usando nossos serviços (incluindo o conteúdo que eles fornecem) para violar os direitos legais de qualquer pessoa, como propriedade intelectual ou direitos de privacidade; fazendo engenharia reversa dos nossos serviços ou tecnologia subjacente, como nossos modelos de aprendizado de máquina, para extrair segredos comerciais ou outras informações reservadas, exceto conforme permitido pela legislação aplicável; usando meios automatizados para acessar o conteúdo de qualquer um dos nossos serviços que viole as instruções legíveis por máquina em nossas páginas da Web (por exemplo, arquivos robots.txt que não permitem rastreamento, treinamento ou outras atividades); usando conteúdo gerado por IA dos nossos serviços para desenvolver modelos de aprendizado de máquina ou tecnologias de IA relacionadas; ocultando ou deturpando sua identidade para violar estes termos; oferecendo serviços que incentivam outras pessoas a violar estes termos. Permissão para usar seu conteúdo Alguns dos nossos serviços são feitos para permitir que você faça upload, encaminhe, armazene, envie, receba ou compartilhe seu conteúdo . Você não tem obrigação de fornecer qualquer conteúdo aos nossos serviços e é livre para escolher o conteúdo que quer fornecer. Se você escolher fazer upload de um conteúdo ou compartilhá-lo, você precisa ter os direitos necessários para fazer isso, e esse conteúdo precisa ser lícito. Licença Seu conteúdo continua sendo seu, o que significa que você retém todos os direitos de propriedade intelectual relacionados a ele. Por exemplo, você tem direitos de propriedade intelectual com relação ao conteúdo criativo de sua autoria, como avaliações que você escreve. Ou você pode ter o direito de compartilhar o conteúdo criativo de outra pessoa, se ela permitir. Precisaremos da sua permissão se seus direitos de propriedade intelectual restringirem nosso uso do conteúdo. Você concede essa permissão ao Google por meio desta licença. O que é coberto Esta licença cobre seu conteúdo se ele for protegido por direitos de propriedade intelectual. O que não é coberto Esta licença não afeta seus direitos de privacidade. Ela trata apenas dos seus direitos de propriedade intelectual. Esta licença não cobre estes tipos de conteúdo: Informações factuais disponíveis para o público fornecidas por você, como correções do endereço de uma empresa local. Essas informações não precisam de uma licença, porque são consideradas conhecimento comum que todos estão livres para usar. Feedback dado por você, como sugestões para melhorar nossos serviços. O feedback é tratado na seção Comunicações relacionados a serviços , disponível abaixo. Escopo Esta licença é: global, o que significa que ela é válida em qualquer lugar do mundo; não exclusiva, o que significa que você pode licenciar seu conteúdo para outras pessoas; livre de royalties, o que significa que não há taxas monetárias relacionadas a ela. Direitos Esta licença permite que o Google: hospede, reproduza, distribua, comunique e use seu conteúdo, por exemplo, para salvá-lo nos nossos sistemas e torná-lo acessível em qualquer lugar; publique, apresente ou exiba publicamente seu conteúdo, se ele tiver sido deixado visível para as outras pessoas; modifique ou crie obras derivadas do seu conteúdo, por exemplo, reformatando ou traduzindo-o; sublicencie esses direitos para: outros usuários de modo a permitir que os serviços funcionem como planejado, por exemplo, ao ativar o compartilhamento de fotos com as pessoas que você escolher; nossos prestadores de serviço que assinaram contratos conosco de acordo com estes termos, apenas para os fins descritos na seção Finalidade , disponível abaixo. Finalidade Esta licença é destinada aos fins restritos de: operar e melhorar os serviços , o que significa permitir que eles funcionem de acordo com o planejado e criar novos recursos e funcionalidades. Isso inclui usar sistemas automatizados e algoritmos com o objetivo de analisar seu conteúdo para: buscar spams, malware e conteúdo ilegal; reconhecer padrões nos dados, como determinar quando sugerir um novo álbum no Google Fotos para manter as fotos relacionadas juntas; personalizar nossos serviços para você, como o fornecimento de recomendações, resultados de pesquisa, conteúdo e anúncios personalizados, o que você pode mudar ou desativar nas Configurações de anúncios . Essa análise ocorre à medida que o conteúdo é enviado e recebido, e quando ele é armazenado. usar o conteúdo que você compartilhou publicamente para promover os serviços . Por exemplo, para promover um app do Google, podemos citar uma avaliação que você escreveu. Ou, para promover o Google Play, podemos exibir uma captura de tela de um app que você oferece na Play Store; Duração Esta licença dura enquanto seu conteúdo estiver protegido por direitos de propriedade intelectual. Se você remover dos nossos serviços qualquer conteúdo que seja coberto por esta licença, nossos sistemas farão com que esse conteúdo deixe de estar disponível publicamente em um prazo razoável. Há duas exceções: Se você já compartilhou seu conteúdo com outras pessoas antes de removê-lo. Por exemplo, se você compartilhou uma foto com um amigo que fez uma cópia dela ou a compartilhou novamente, essa foto poderá continuar aparecendo na Conta do Google do seu amigo mesmo depois que você removê-la da sua Conta do Google. Se você disponibiliza seu conteúdo por meio serviços de outras empresas, é possível que os mecanismos de pesquisa, incluindo a Pesquisa Google, continuem encontrando e exibindo seu conteúdo como parte dos resultados deles. Usando os serviços do Google Sua Conta do Google Se você atende às restrições de idade , pode criar uma Conta do Google para sua conveniência. Alguns serviços exigem que você tenha uma Conta do Google para que eles funcionem. Por exemplo, para usar o Gmail, é necessário ter uma Conta do Google para que você possa enviar e receber seus e-mails. Você é responsável por tudo o que faz com sua Conta do Google, incluindo tomar as medidas necessárias para manter sua conta segura, e nós recomendamos o uso regular da Verificação de segurança . Usando os serviços do Google em nome de uma organização ou empresa Muitas organizações , como empresas, organizações sem fins lucrativos e escolas, beneficiam-se dos nossos serviços . Para usar nossos serviços em nome de uma organização: um representante autorizado dessa organização precisa concordar com estes termos; o administrador da sua organização pode atribuir uma Conta do Google a você. Esse administrador poderá exigir que você siga outras regras e talvez consiga acessar ou desativar sua Conta do Google. Comunicações relacionadas a serviços Para oferecer a você nossos serviços, às vezes enviamos avisos sobre o serviço e outras informações. Para saber mais sobre como nos comunicamos com você, acesse a Política de Privacidade do Google. Se você optar por nos dar feedback, como sugestões para melhorar nossos serviços, poderemos agir de acordo com essa informação sem qualquer compromisso com você. Conteúdo nos serviços do Google Seu conteúdo Alguns dos nossos serviços permitem que você gere conteúdo original. O Google não vai reivindicar a propriedade desse conteúdo. Alguns dos nossos serviços permitem que você deixe seu conteúdo disponível publicamente. Por exemplo, é possível postar uma avaliação de restaurante ou produto ou fazer upload de uma postagem em um blog que você criou. Consulte a seção Permissão para usar seu conteúdo para ver mais informações sobre os direitos relacionados ao seu conteúdo e sobre como ele é usado nos nossos serviços. Consulte a seção Remover seu conteúdo para saber como e por que podemos remover conteúdo gerado pelo usuário dos nossos serviços. Se você acredita que alguém está violando seus direitos de propriedade intelectual , pode nos enviar um aviso sobre a violação para tomarmos as providências necessárias. Por exemplo, suspendemos ou encerramos as Contas do Google de violadores de direitos autorais reincidentes, conforme descrito na nossa Central de Ajuda de direitos autorais . Conteúdo do Google Alguns dos nossos serviços incluem conteúdo que pertence ao Google, como, por exemplo, várias das ilustrações visuais vistas no Google Maps. Você pode usar esse conteúdo do Google de acordo com o permitido nestes termos ou em qualquer um dos termos adicionais específicos do serviço , mas nós retemos todos os direitos de propriedade intelectual relacionados ao nosso conteúdo. Não remova, oculte ou mude nenhum dos nossos logotipos, marcas ou avisos legais. Se você quiser usar nossos logotipos ou marcas, consulte a página Permissões relacionadas à marca do Google (link em inglês). Outros conteúdos Por fim, alguns dos nossos serviços dão a você acesso a conteúdos que pertencem a outras pessoas ou organizações (por exemplo, a descrição do proprietário de uma loja sobre a própria empresa ou um artigo de jornal que aparece no Google Notícias). Não use esse conteúdo sem a permissão dessa pessoa ou organização, ou de alguma forma que não seja permitida por lei. As opiniões expressas no conteúdo de outras pessoas ou organizações não refletem necessariamente as opiniões do Google. Software nos serviços do Google Alguns dos nossos serviços incluem software para download ou pré-carregado. Nós damos a você permissão para usar esses softwares como parte dos serviços. A licença que concedemos a você é: global, o que significa que ela é válida em qualquer lugar do mundo; não exclusiva, o que significa que podemos licenciar o software para outras pessoas; livre de royalties, o que significa que não há taxas monetárias relacionadas a ela; pessoal, o que significa que ela não pode ser estendida para mais ninguém; intransferível, o que significa que não é possível transferi-la para mais ninguém. Alguns dos nossos serviços incluem softwares oferecidos de acordo com os termos da licença de código aberto que nós disponibilizamos para você. Às vezes, há disposições na licença de código aberto que prevalecem sobre partes destes termos, então leia com atenção. Não copie, modifique, distribua, venda ou alugue qualquer parte dos nossos serviços ou softwares. Em caso de problemas ou discordâncias A legislação e estes termos concedem a você o direito a (1) determinada qualidade de serviço e (2) maneiras de resolver problemas se algo der errado. Garantia Fornecemos nossos serviços usando um nível razoável de habilidade e cuidado. Se não alcançarmos o nível de qualidade descrito nesta garantia , você concorda em nos informar para que possamos trabalhar juntos de modo a resolver o problema. Exonerações de responsabilidade Os únicos compromissos que assumimos com relação aos nossos serviços , incluindo o conteúdo deles, as funções específicas ou a confiabilidade, disponibilidade ou possibilidade de atender às suas necessidades são fornecidos (1) na seção Garantia , (2) nos termos adicionais específicos do serviço e (3) nas leis que não podem ser limitadas por estes termos. Não confie nos serviços para aconselhamento médico, jurídico, financeiro ou outra assistência profissional. Todo conteúdo sobre esses assuntos é fornecido somente para fins informativos e não substitui a orientação de um profissional qualificado. Responsabilidades Para todos os usuários Tanto a legislação quanto estes termos buscam alcançar um equilíbrio quanto ao que você e o Google podem reivindicar em caso de problemas. Por isso, a legislação exige que todos tenham responsabilidades específicas e limitadas de acordo com estes termos. Estes termos só limitam nossas responsabilidades de acordo com o permitido pela legislação aplicável. Estes termos não limitam a responsabilidade por: fraude ou declaração falsa; morte ou danos pessoais causados por negligência; negligência grave; má conduta intencional. Salvo as responsabilidades descritas acima, o Google será responsável apenas pelas próprias violações destes termos ou dos termos adicionais específicos do serviço , sujeitas à legislação aplicável. Somente para usuários comerciais e organizações Se você é um usuário comercial ou uma organização : Na medida permitida por lei, você indenizará o Google e os diretores, executivos, funcionários e prestadores de serviço dele por qualquer processo judicial de terceiros (incluindo ações de órgãos do governo) decorrentes ou relacionados ao uso ilegal dos serviços , a violações destes termos ou dos termos adicionais específicos do serviço . Essa indenização cobre qualquer responsabilidade ou despesa decorrente de ações judiciais, perdas, danos, julgamentos, multas, custos de litígios e honorários advocatícios, exceto se a responsabilidade ou despesa for causada por violação, negligência ou má conduta intencional do Google. Se você for passível de isenção legal de certas responsabilidades, incluindo indenização , essas responsabilidades não se aplicarão a você de acordo com estes termos. Por exemplo, a ONU goza de certas imunidades para com obrigações legais, e estes termos não modificam essas imunidades. o Google não será responsável por responsabilidades : Perda de lucros, receitas, oportunidades de negócios, clientela ou economias previstas Perda indireta ou emergente Danos punitivos Exceto conforme indicado na seção Para todos os usuários acima, a responsabilidade total do Google decorrente destes termos ou relacionada a eles é limitada ao valor de (1) US$ 500 ou (2) 125% das taxas pagas por você para usar os serviços relevantes nos 12 meses anteriores à violação. Tomando providências em caso de problemas Antes de tomar as providências descritas abaixo, vamos enviar, com antecedência e sempre que possível, um aviso descrevendo o motivo da nossa ação e daremos a você a oportunidade de esclarecer e resolver o problema, a menos que haja motivos razoáveis para acreditarmos que fazer isso: acarretaria em dano ou responsabilidade para um usuário, terceiros ou ao Google; violaria a legislação ou determinação emanada de uma autoridade; comprometeria uma investigação; comprometeria a operação, integridade ou segurança dos nossos serviços . Remover seu conteúdo Se tivermos razões concretas para acreditar que qualquer conteúdo seu (1) viola estes termos, os termos adicionais específicos do serviço ou as políticas , (2) viola a legislação aplicável, ou (3) pode prejudicar nossos usuários, terceiros ou o Google, reservamos o direito de remover parte ou a totalidade desse conteúdo de acordo com a legislação aplicável. Alguns exemplos são pornografia infantil, conteúdo que facilita o assédio ou tráfico de pessoas, conteúdo terrorista e conteúdo que viola os direitos de propriedade intelectual de outra pessoa. Suspender ou encerrar seu acesso aos serviços do Google Sem limitar qualquer um dos nossos outros direitos, o Google poderá suspender ou rescindir seu acesso aos serviços ou excluir sua Conta do Google se uma destas situações acontecer: Você violar estes termos, os termos adicionais específicos do serviço ou as políticas de forma relevante ou recorrente. Se precisarmos fazer isso para obedecer a um requisito legal ou uma ordem judicial. Se tivermos razões concretas para acreditar que sua conduta causa danos ou responsabilidade a um usuário, a terceiros ou ao Google, por exemplo, por meio de hacking, phishing, assédio, prática de spam, ludibriação de outras pessoas ou cópia de conteúdo que não pertença a você. Para mais informações sobre os motivos pelos quais desativamos contas e o que acontece nesses casos, acesse a página da Central de Ajuda . Se você acredita que sua Conta do Google foi suspensa ou encerrada por engano, é possível contestar . Obviamente, você pode parar de usar nossos serviços a qualquer momento. Se você parar de usar um serviço, gostaríamos de saber o motivo para que possamos melhorar. Soluções de disputas, legislação aplicável e tribunais Para obter informações sobre como entrar em contato com o Google, por favor visite nossa página de contato . As leis da Califórnia vão reger todas as disputas que surgirem com relação a qualquer um destes termos, dos termos adicionais específicos do serviço ou qualquer serviço relacionado, mesmo se houver conflito nas regras das leis. Essas disputas serão resolvidas exclusivamente nos tribunais federais ou estaduais do condado de Santa Clara, Califórnia, EUA, e você e o Google concordam com a jurisdição pessoal nesses tribunais. Se a legislação local aplicável impedir que determinadas disputas sejam resolvidas em um tribunal da Califórnia, você poderá encaminhá-las para os tribunais locais. Da mesma forma, se a legislação local aplicável impedir que o tribunal local aplique a lei da Califórnia para resolver essas disputas, elas serão regidas pelas leis do seu país, estado ou outro local de residência. Sobre estes termos Por lei, você tem certos direitos que não podem ser limitados por um contrato como estes Termos de Serviço. Estes termos não têm, de forma alguma, o objetivo de restringir esses direitos. Estes termos descrevem a relação entre você e o Google. Eles não geram nenhum direito legal para outras pessoas ou organizações , mesmo que elas se beneficiem desse relacionamento sob estes termos. Queremos que estes termos sejam fáceis de entender, por isso, usamos exemplos baseados nos nossos serviços . No entanto, é possível que nem todos os serviços estejam disponíveis no seu país. Se estes termos entrarem em conflito com os termos adicionais específicos do serviço , os termos adicionais prevalecerão para esse serviço. Se um termo específico não for aplicável, isso não afetará os outros termos. Se você não seguir estes termos ou os termos adicionais específicos do serviço , e não tomarmos as medidas cabíveis imediatamente, isso não significa que estamos desistindo de quaisquer direitos que possamos ter, como tomar as medidas cabíveis futuramente. Podemos atualizar estes termos e os termos adicionais específicos do serviço (1) para refletir mudanças nos nossos serviços ou na maneira como fazemos negócios, por exemplo, quando adicionamos serviços, recursos, tecnologias, preços ou benefícios novos (ou removemos os antigos), (2) por motivos jurídicos, regulatórios ou de segurança ou (3) para evitar abusos ou danos. Se mudarmos estes termos ou os outros termos específicos do serviço , vamos enviar um aviso com 30 dias de antecedência e daremos a você a oportunidade de analisar as mudanças, exceto (1) quando lançarmos um novo serviço ou recurso que seja favorável aos usuários ou (2) em situações urgentes, como para evitar abusos atuais ou responder a exigências legais. Se não concordar com os novos Termos, você vai precisar remover seu conteúdo e parar de usar os serviços. Você também pode finalizar seu relacionamento conosco a qualquer momento encerrando sua Conta do Google . Definições afiliada Uma entidade que pertence ao grupo de empresas Google, ou seja, a Google LLC e as subsidiárias dela, incluindo as empresas a seguir, que fornecem serviços ao consumidor na UE: Google Ireland Limited, Google Commerce Limited e Google Dialer Inc. consumidor Um indivíduo que utiliza os serviços do Google para fins pessoais e não comerciais, fora do âmbito do comércio, negócio, ofício ou profissão dele. Consulte "usuário comercial". direitos autorais Um direito que permite que o criador de uma obra original, como uma postagem em um blog, uma foto ou um vídeo, decida se e como essa obra será usada por outras pessoas, sujeito a determinadas limitações e exceções, como "uso aceitável" e "tratamento aceitável". direitos de propriedade intelectual (direitos de PI) Direitos sobre as criações intelectuais individuais, como invenções (direitos de patente); obras literárias e artísticas (direitos autorais); designs (direitos de design); e símbolos, nomes e imagens usados no comércio (marcas registradas). Os direitos de propriedade intelectual podem pertencer a você, a outro indivíduo ou a uma organização. exoneração de responsabilidade Uma declaração que limita as responsabilidades legais de alguém. garantia Uma declaração de que um produto ou serviço terá um desempenho de acordo com um determinado padrão. indenização ou reparação A obrigação contratual de um indivíduo ou organização de compensar as perdas sofridas por outro indivíduo ou organização devido a procedimentos legais, como ações judiciais. marca registrada Símbolos, nomes e imagens usados no comércio e que podem distinguir os produtos ou serviços de um indivíduo ou uma organização dos de outro. organização Uma pessoa jurídica (como uma corporação, organização sem fins lucrativos ou escola), e não uma física. responsabilidade Perdas por qualquer tipo de ação judicial, seja ela baseada em um contrato, reparação por ato ilícito extracontratual (incluindo negligência) ou outro motivo, e se essas perdas poderiam ou não ser antecipadas ou previstas de maneira razoável. serviços Os Serviços do Google sujeitos a estes termos são os produtos e serviços listados em https://policies.google.com/terms/service-specific , incluindo: Apps e sites, como a Pesquisa e o Google Maps Plataformas, como o Google Shopping Serviços integrados, como o Maps incorporado em apps ou sites de outras empresas Dispositivos e outros produtos, como o Google Nest Muitos desses serviços também incluem conteúdo que pode ser visto por streaming ou com o qual você pode interagir. seu conteúdo Aquilo que você cria, faz upload, armazena, envia, recebe ou compartilha usando nossos serviços, como: Documentos, Planilhas e Apresentações que você cria Postagens de blog que você cria pelo Blogger Avaliações que você envia pelo Google Maps Vídeos que você armazena no Google Drive E-mails que você envia e recebe pelo Gmail Imagens que você compartilha com amigos pelo Google Fotos Itinerários de viagem que você compartilha com o Google usuário comercial Um indivíduo ou entidade que não é consumidor (consulte "consumidor"). versão específica Se você tem uma Conta do Google, ela é associada a um país (ou território) para que possamos determinar: o afiliado do Google que fornece os serviços a você e processa suas informações enquanto você os utiliza; a versão dos termos que regem nossa relação. Quando a conta não está conectada, a versão específica é determinada pelo local em que você está usando os Serviços do Google. Se você tem uma conta, faça login e abra estes termos para ver o país associado a ela. close Abre em uma nova guia (abre uma nota de rodapé) Google Sobre o Google Política de Privacidade Termos Central de Transparência Português (Brasil) Afrikaans Bahasa Indonesia Bahasa Melayu Català Čeština Dansk Deutsch Eesti English English (India) English (United Kingdom) Español Español (Latinoamérica) Euskara Filipino Français Français (Canada) Gaeilge Galego Hrvatski Isizulu Íslenska Italiano Kiswahili Latviešu Lietuvių Magyar Malti Nederlands Norsk Polski Português (Brasil) Português (Portugal) Română Slovenčina Slovenščina Srpski Suomi Svenska Tiếng Việt Türkçe অসমীয়া Ελληνικά Български ଓଡିଆ Русский Српски Українська עברית اردو العربية فارسی አማርኛ मराठी हिन्दी বাংলা ગુજરાતી தமிழ் తెలుగు ಕನ್ನಡ മലയാളം ไทย 한국어 中文 (香港) 中文（简体中文） 中文（繁體中文） 日本語 Google Apps Menu principal | 2026-01-13T09:29:41 |
https://www.nec-labs.com/blog/giovanni-milione-presents-mobile-orbital-domains-addressing-dynamic-topology-challenges-in-satellite-networks-at-fio-ls-conference-on-october-29th/ | Giovanni Milione presents Mobile Orbital Domains at FiO LS Conference on October 29th Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Research Overview Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications News Events Careers Overview Search Careers Intern Program About Overview Christopher White | President Office of the President NEC Corporation NEC Corporation of America NEC Research & Development Follow us on Social Media! Subscribe to our Newsletter Contact Click to open the search input field Click to open the search input field Search Menu Menu You are here: Home 1 / Blog 2 / Events 3 / Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology... Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th October 24, 2025 | by NEC Labs America | in Events | tags andrea d'amico , frontiers in optics , giovanni milione , mobile orbital domains , optical networks , satellite networks Our Giovanni Milione will present Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks (JW4A.47) in Joint Poster Session III at the Frontiers in Optics + Laser Science (FiO LS) conference in Denver, CO, on October 29, 2025, 11:30 AM to 1:00 PM. We analyze satellite trajectories and identify satellite backbone networks with stable inter-satellite connections. We propose organizing satellites into mobile orbital domains to reduce the complexity of control and management caused by satellite movement and dynamic network topology. Co-authors: Zilong Ye, NEC Labs America; Philip Ji , NEC Labs America; and Ting Wang , NEC Labs America. Frontiers in Optics + Laser Science (FiO LS) Conference The FiO LS conference offers both in-person (October 26–30) and virtual (October 22) formats, with all sessions available on demand for 60 days. Organized around key themes that connect scientific breakthroughs to real-world applications, the technical program features visionary talks and expert panels exploring emerging innovations. Distinguished speakers from across and beyond the optics and photonics community share forward-looking insights into the field’s future. Complementing the sessions, the Science + Industry Showcase includes an exhibition, live demos, and more than 500 research posters, providing a dynamic forum for collaboration between academia and industry. Past Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 November 19, 2025 NEC Laboratories America is heading to San Diego for NeurIPS 2025, where our researchers will present cutting-edge work spanning optimization, AI systems, language modeling, and trustworthy machine learning. This year’s lineup highlights breakthroughs in areas like multi-agent coordination, scalable training, efficient inference, and techniques for detecting LLM-generated text. Together, these contributions reflect our commitment to advancing fundamental science while building real-world solutions that strengthen industry and society. We’re excited to join the global AI community in San Diego from November 30 to December 5 to share our latest innovations. Read more https://www.nec-labs.com/wp-content/uploads/2025/11/NEURIPS-2025-2.jpg 628 1200 NEC Labs America https://www.nec-labs.com/wp-content/uploads/2025/08/NEC-Laboratories-America-Logo-Aug-2025-2.jpg NEC Labs America 2025-11-19 17:44:03 2025-12-12 14:09:23 NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th November 6, 2025 Eric Blow of NEC Labs will address how machine-learning methods applied to distributed acoustic-sensing data can monitor facility perimeters and detect intrusion via walk, dig, or drive events over buried optical fibre—for example achieving ~90% classification accuracy. Later in the week he will explore neuromorphic photonic RF sensing combining silicon photonics with FPGA-based recurrent neural networks, and his intern Yuxin Wang will present a finalist paper on scalable photonic neurons for automatic modulation classification. Read more https://www.nec-labs.com/wp-content/uploads/2025/11/Eric-Blow-IPC2025-Monday.jpg 628 1200 NEC Labs America https://www.nec-labs.com/wp-content/uploads/2025/08/NEC-Laboratories-America-Logo-Aug-2025-2.jpg NEC Labs America 2025-11-06 08:55:41 2025-11-06 09:41:10 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th October 24, 2025 Our Giovanni Milione will present Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks (JW4A.47) in Joint Poster Session III at the Frontiers in Optics + Laser Science (FiO LS) conference in Denver, CO, on October 29, 2025, 11:30 AM to 1:00 PM. We analyze satellite trajectories and identify satellite backbone networks with stable inter-satellite connections. Read more https://www.nec-labs.com/wp-content/uploads/2025/10/FiOLS2025-Giovanni.jpg 628 1200 NEC Labs America https://www.nec-labs.com/wp-content/uploads/2025/08/NEC-Laboratories-America-Logo-Aug-2025-2.jpg NEC Labs America 2025-10-24 11:05:04 2025-10-24 11:30:33 Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th October 23, 2025 Join our Andrea D’Amico as he presents Open and Disaggregated Optical Networks: From Vision to Reality (FW6E.1) at part of the Next-Generation Optical Fiber Transmission Systems and Networks Session at the Frontiers in Optics + Laser Science (FiO LS) conference in Denver, CO, on October 29, 2025, 3:30 PM to 4:00 PM. Open and disaggregated optical networks can potentially reshape the telecom landscape. Read more https://www.nec-labs.com/wp-content/uploads/2025/10/FiOLS-2025-Andrea.jpg 628 1200 NEC Labs America https://www.nec-labs.com/wp-content/uploads/2025/08/NEC-Laboratories-America-Logo-Aug-2025-2.jpg NEC Labs America 2025-10-23 16:09:07 2025-10-24 11:31:13 Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st October 17, 2025 Murugan Sankaradas (presenting virtually) will present “TalentScout: Multimodal AI-Driven Expert Finding in Organizations” at the IEEE International Conference on Pervasive Intelligence and Computing (PICom2025) on Tuesday, October 21 (10:30am–12pm JST) | Monday, October 20 (9:30–11pm ET) in Hokkaido, Japan. Read more https://www.nec-labs.com/wp-content/uploads/2025/10/PICOM25-Murugan.jpg 628 1200 NEC Labs America https://www.nec-labs.com/wp-content/uploads/2025/08/NEC-Laboratories-America-Logo-Aug-2025-2.jpg NEC Labs America 2025-10-17 14:08:12 2025-10-17 14:08:12 Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 October 16, 2025 We are proud to share that our Abhishek Aich is serving as one of the organizers of the Anomaly Detection with Foundation Models Workshop, held in conjunction with the International Conference on Computer Vision, October 20, 2025, 08:55 AM – 12:15 PM HST in Room 314 at theHawaii Convention Center, Honolulu, HI. Read more https://www.nec-labs.com/wp-content/uploads/2025/10/ADFM2025.jpg 628 1200 NEC Labs America https://www.nec-labs.com/wp-content/uploads/2025/08/NEC-Laboratories-America-Logo-Aug-2025-2.jpg NEC Labs America 2025-10-16 13:42:06 2025-10-28 17:52:51 Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Page 1 of 4 1 2 3 4 Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Kunal Rao presents SlideCraft: Context-Aware Slides Generation Agent at PICom 2025 on October 21st NECLA at ECOC 2025: Advancing Optical Communication and Distributed Sensing Blog Posts NEC Laboratories America 2025: A Year of Disruptive Innovation Apply for a Summer 2026 Internship NEC Laboratories America: Celebrating 23 Years of Research Innovation! Summer Highlights at NEC Labs America: Teamwork, Innovation, and Fun Graph Neural Networks, Explained: Our Role in the Future of AI Shaping the Future with Responsible AI, Collaboration, and Disruption Top 10 Most Legendary College Pranks of All-Time for April Fools’ Day Introducing the Trustworthy Generative AI Project: Pioneering the Future of Compositional Generation and Reasoning Introducing Our New Project: Time Series Language Model for Explainable AI The Evolution of Disciplines: From Experimental Roots to Theoretical Frameworks Agentic LLMs for AI Orchestration Project: Revolutionizing Complex Workflows Multi-Agent Simulator for Carbon Neutrality: The Technology the World Has Been Waiting For NEC Laboratories Advances Material Design with AI-based MateriAI Platform Unearthing Nature’s Orchestra – How Fiber Optic Cables Can Hear Cicada Secrets Search Search Contact Us Princeton Office 4 Independence Way, Suite 200 Princeton, NJ 08540 +1 609-520-1555 San Jose Office 2033 Gateway Place, Suite 200 San Jose, CA 95110 +1 408-863-6007 About Us NEC Laboratories America, Inc. (NEC Labs) is the US-based center for NEC Corporation’s global network of corporate research laboratories. Our diverse research groups collaborate with industry, academia and governments to provide disruptive solutions to complex problems. A leader in the integration of IT and network technologies with more than 100 years of expertise, NEC provides a combination of products and solutions that cross-utilize the company’s experience and global resources to meet the complex and ever-changing needs of its customers. Our Pages Home Research Departments Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Publications Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing Patents Data Science & System Security Integrated Systems Machine Learning Media Analytics Optical Networking & Sensing News Events About Us Christopher White | President Office of the President NEC Corporation Subscribe to our Newsletter Careers Intern Program Contact Us Recent Publications Quantitative Bounds for Length Generalization in Transformers Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing SlideCraft: Context-aware Slides Generation Agent TalentScout: Multimodal AI-Driven Expert Finding in Organizations AutoScape: Geometry-Consistent Long-Horizon Scene Generation DWIM: Towards Tool-aware Visual Reasoning via Discrepancy-aware Workflow Generation & Instruct-Masking Tuning Mapillary Vistas Validation for Fine-Grained Traffic Signs: A Benchmark Revealing Vision-Language Model Limitations LANGTRAJ: Diffusion Model and Dataset for Language-Conditioned Trajectory Simulation DiscussLLM: Teaching Large Language Models When to Speak Bifröst: Peer-to-peer Load-balancing for Function Execution in Agentic AI Systems Harnessing Vision Models for Time Series Analysis: A Survey Multi-modal Time Series Analysis: A Tutorial and Survey ICeTEA: Mixture of Detectors for Metric-Log Anomaly Detection Roadside Multi-LiDAR Data Fusion for Enhanced Traffic Safety Identifying Combinatorial Regulatory Genes for Cell Fate Decision via Reparameterizable Subset Explanations On Synthesizing Data for Context Attribution in Question Answering Feasibility study on scour monitoring for subsea cables of offshore wind turbines using distributed fiber optic sensors Group Relative Augmentation for Data Efficient Action Detection Uncertainty Propagation on LLM Agent Exploring Multi-Modal Data with Tool-Augmented LLM Agents for Precise Causal Discovery EcoDoc: A Cost-Efficient Multimodal Document Processing System for Enterprises Using LLMs Integration of Fiber Optic Sensing and Sparse Grid Sensors for Accurate Fault Localization in Distribution Systems XPF: Agentic AI System for Business Workflow Automation Quantitative Bounds for Length Generalization in Transformers Re-ranking the Context for Multimodal Retrieval Augmented Generation Beyond the Permutation Symmetry of Transformers: The Role of Rotation for Model Fusion PPDiff: Diffusing in Hybrid Sequence-Structure Space for Protein-Protein Complex Design Pathologist-Read vs AI-Driven Assessment of Tumor-Infiltrating Lymphocytes in Melanoma AutoScape: Geometry-Consistent Long-Horizon Scene Generation Events NeurIPS 2025 in San Diego from November 30th to December 5th, 2025 Eric Blow Presents at the IEEE Photonics Conference Singapore on November 10th & 13th Giovanni Milione presents Mobile Orbital Domains: Addressing Dynamic Topology Challenges in Satellite Networks at FiO LS Conference on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Murugan Sankaradas presents TalentScout: Multimodal AI-Driven Expert Finding in Organizations at PICom2025 on October 21st Abhishek Aich is Organizing the Anomaly Detection with Foundation Models Workshop, held in conjunction with ICCV 2025 Kunal Rao presents SlideCraft: Context-Aware Slides Generation Agent at PICom 2025 on October 21st NECLA at ECOC 2025: Advancing Optical Communication and Distributed Sensing News NEC Laboratories America 2025: A Year of Disruptive Innovation Apply for a Summer 2026 Internship NEC Laboratories America: Celebrating 23 Years of Research Innovation! Summer Highlights at NEC Labs America: Teamwork, Innovation, and Fun Graph Neural Networks, Explained: Our Role in the Future of AI Shaping the Future with Responsible AI, Collaboration, and Disruption Top 10 Most Legendary College Pranks of All-Time for April Fools’ Day Introducing the Trustworthy Generative AI Project: Pioneering the Future of Compositional Generation and Reasoning Introducing Our New Project: Time Series Language Model for Explainable AI The Evolution of Disciplines: From Experimental Roots to Theoretical Frameworks Agentic LLMs for AI Orchestration Project: Revolutionizing Complex Workflows Multi-Agent Simulator for Carbon Neutrality: The Technology the World Has Been Waiting For NEC Laboratories Advances Material Design with AI-based MateriAI Platform Unearthing Nature’s Orchestra – How Fiber Optic Cables Can Hear Cicada Secrets © Copyright 2025 NEC Labs America | All Rights Reserved | Privacy Policy | Global Privacy Policy Link to X Link to LinkedIn Link to Facebook Link to Youtube Link to Instagram Link to Rss this site Home Research Departments Publications Patents News Events About Us Careers Contact Us Link to: Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Link to: Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision to Reality at FiO LS on October 29th Andrea D’Amico Presents Open and Disaggregated Optical Networks: From Vision... Link to: Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing Link to: Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic Sensing Sound Event Classification meets Data Assimilation with Distributed Fiber-Optic... Scroll to top Scroll to top Scroll to top | 2026-01-13T09:29:41 |
https://lwn.net/Articles/897786/ | A discussion on readahead [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register A discussion on readahead This article brought to you by LWN subscribers Subscribers to LWN.net made this article — and everything that surrounds it — possible. If you appreciate our content, please buy a subscription and make the next set of articles possible. By Jake Edge June 15, 2022 LSFMM Readahead is an I/O optimization that causes the system to read more data than has been requested by an application—in the belief that the extra data will be requested soon thereafter. At the 2022 Linux Storage, Filesystem, Memory-management and BPF Summit (LSFMM), Matthew Wilcox led a session to discuss readahead, especially as it relates to network filesystems, with assistance from Steve French and David Howells. The latency of the underlying storage needs to factor into the calculation of how much data to read in advance, but it is not entirely clear how to do so. Wilcox began by describing readahead a bit. If user space is reading a file one byte at a time, Linux does not actually read the data that way; instead, it issues reads for a bigger chunk, say 64KB, which gets stored in the page cache. There is a certain amount of latency between the time a page is requested from the storage and when it appears in the page cache; that latency varies greatly over the wide variety of storage types that Linux supports. For network storage, those types can range from locally stored data on multi-gigabit Ethernet to data stored halfway around the world over decidedly slower links. Similarly, for local storage it can range from a 5GB-per-second NVMe SSD to some "crappy USB key picked up from a vendor at a trade show". There is "a lot of stuff to contend with there". In his experience, block-layer developers tend to do all of their testing using direct I/O; they think that "the page cache sucks" so they avoid it in their testing. James Bottomley said they are often trying to exclude the effects of the page cache from their testing in order to eliminate variables outside of their control. Wilcox said that it was unfortunate, since the performance including the page cache is "what the users are actually seeing"; it would be nice to notice problems where either too much or too little readahead is affecting the performance—before users do. He said that he has a KernelNewbies wiki page where he is collecting his thoughts about readahead and the page cache in general. The page cache "is awesome in some ways, in other ways it's terrible", but it would be good to fix the problems that it has. The Android developers encountered a problem with readahead, but "they worked around it in the worst way possible". They changed a setting for readahead, moving it from 256KB to several hundred megabytes, he said, in order to shave "some fraction of a second" from application startup time. That has other effects, of course; when they tried to upstream the patches, the memory-management developers said "no". Howells suggested that the Android developers should be using fadvise() (or, he amended, madvise() ) to indicate that the file should have more aggressive readahead. But Wilcox did not agree: "can we stop trying to pretend that user space knows what it is doing?" Android is a specialized environment, Bottomley said; it uses a log-structured filesystem, so the workaround may actually make sense. Wilcox expressed some skepticism on that score. Overall, there are a bunch of readahead problems to solve. "I'm going to say the 'f' word; folios play into this a bit." The use of larger folios is driven by readahead, currently; the larger the readahead data gets, the larger the folios to hold it get. That is useful for testing. Filesystems that support larger folios, which is only XFS for now (though AFS and v9fs patches are queued), will allocate four-page (i.e. order-2) folios. Wilcox said that French made him aware that Windows does huge reads for readahead on CIFS. French agreed with that, noting that because of the expected network latency, Windows can readahead up to 16MB, though that seems to degrade performance. He tested with a number of different sizes (256KB, 512KB, 1MB, 4MB) and found better performance with each of those, the most dramatic being seen when going to 512KB. On the Azure cloud, the value was set to 1MB because there were performance decreases for some workloads at 4MB. The Linux CIFS server defaults to 4MB, he said, based on the results of his testing. It is clear that anything less than 1MB performs worse unless there is a fast network in between. The problem he sees is how this value can get changed sanely, throttled or raised as appropriate. Sometimes the page cache knows more than the filesystem, or the reverse can be true, and the network layer needs to factor in as well. It is not clear to him how that can all be resolved. There is a mechanism to communicate this kind of information from the filesystem to the virtual filesystem (VFS) layer and page cache using the BDI ( struct backing_dev_info ), Wilcox said. That is where the VFS looks to find out the performance characteristics of the underlying storage. It may not currently have all of the right information, he said, but that's the place to put it. When user space is reading a file one byte at a time, a 64KB read is issued instead; a "was this readahead useful" marker is placed around 20KB into the buffer and when it is reached, another 64KB read is issued. The intent is that the second read completes before user space consumes the rest of the 44KB, but the filesystem has no idea of what the latency is for the read. One could imagine measuring how long it takes to do the read and comparing it with the user-space consumption rate to better determine when to schedule the next read, he said, but that is not done. That second 64KB read has its marker placed right at the beginning of the buffer; when that marker is reached, it decides to grow the readahead buffer and reads 128KB. It will increase once more (to 256KB), but not any further, though it should probably go up from there. The 256KB limit has been that way for 20 years and "I/O has hardly changed at all in that time", Wilcox said sarcastically; increasing that limit is many years overdue at this point. Josef Bacik read a chat comment from Jan Kara that said SUSE has had a limit of 512KB for years. Given that, Wilcox thought an immediate move to a 1MB maximum was in order. But, rather than increasing the size of the read directly, Wilcox would rather issue multiple 256KB reads back to back because that will help the page cache track if the data that is read ahead is actually being used. French said that would be preferable for CIFS, as multiple smaller reads are better performance-wise. Jeff Layton came in via Zoom to say that he thought a single, larger read would be better for NFS and was surprised to hear that smaller reads were better for CIFS. Howells said that which of the options is better is totally filesystem-dependent. Ted Ts'o said that it will also depend on the underlying storage; increasing the readahead size on memory-constrained devices may also be problematic. There is not going to be a single "magic readahead formula" that can be used in all situations. He suggested making it possible to experiment with different algorithms using BPF; that way a grad student, for example, could easily try out different ideas to see which worked best. Wilcox said that he had wanted to argue with that idea but then decided he liked it because it would make it someone else's problem, which was met with much laughter. Chuck Lever said that he thought the readahead situation was being greatly oversimplified in the discussion. In the original example of a program reading a byte at a time, there is no reason to increase beyond 64KB, since that will keep up with the program just fine. There are problems with requesting too much data and filling the page cache with pages that are not actually going to be read. Another problem is that queueing up a 1MB read, for example, on a network filesystem will hold up other smaller requests, like metadata updates, while the read is ongoing. He agrees with the need for experimentation and thinks that should take precedence over any immediate increase in the kernel's readahead size. There is a need for testing with a lot of different workloads, filesystems, and so forth to determine what the overall systemic effects of that kind of change would be. Index entries for this article Kernel Readahead Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments A discussion on readahead Posted Jun 15, 2022 16:05 UTC (Wed) by GauntletWizard (subscriber, #110285) [ Link ] There was a trick built into the Java "runtime" in Google; essentially, the script that started the JVM was prefixed by `cat $JARFILE > /dev/null` . This sped up start-up times immensely, because it assured that the entire jar file was in the block cache before the Java process started to load classes from it, which was often in terrible order (partially because JAR files are PKZIP, with their "header" at the end of the file). This is likely where the Android example of insane readahead "got it". A discussion on readahead Posted Jun 15, 2022 16:21 UTC (Wed) by adobriyan (subscriber, #30858) [ Link ] (2 responses) ELF loader for sure doesn't need to readahead those debuginfo sections at the end of the file. A discussion on readahead Posted Jun 29, 2022 5:28 UTC (Wed) by jengelh (subscriber, #33263) [ Link ] ld.so would normally just mmap the file and then read the parts it wants (and skipping debuginfo in that sense). I don't see any madvise call in glibc to that end, so if there is any gratuitous readahead, it's being done by the kernel, which makes it "someone else's problem" as far as glibc is concerned ;-) A discussion on readahead Posted Jun 29, 2022 5:39 UTC (Wed) by jengelh (subscriber, #33263) [ Link ] Some Linux distros use split debuginfo, whereby those sections are objcopy'd into files separate files in /usr/lib/debug and then stripped off the original executable. This makes it possible to install both pieces separately depending on what's needed. It so conveniently happens to also stop excess (file descriptor based) readahead, though that surely was not the motivation. A discussion on readahead Posted Jun 15, 2022 18:42 UTC (Wed) by zblaxell (subscriber, #26385) [ Link ] (1 responses) It sounds like some people are about to try to reinvent TCP's last few decades of bandwidth-delay-product optimizations for packet-switching networks with highly variable and unknown performance characteristics. To be fair, the state of the art in networking probably doesn't apply directly to a filesystem + block device stack, so someone will have to do some adaptation; however, it's not like a lot of people haven't been studying a very similar problem domain for a very long time. A discussion on readahead Posted Jun 18, 2022 17:22 UTC (Sat) by willy (subscriber, #9762) [ Link ] I am Very Much Not looking to invent my own algorithm. I'm quite aware that we're often in a Long Fat Pipe situation with storage (particularly multi-spindle devices). Our existing readahead algorithm is shoddy, and its heuristics are laughable. One purpose of this session was to gather feedback from filesystem people about their requirements... which turned out to be contradictory. I think I have a pretty good handle on the performance characteristics of block storage (from floppies to CD-ROMs to laptop HDs to RAID arrays to USB sticks to SSDs), but I'm pretty clueless about the performance characteristics of network servers, so that was where I was looking to learn. Multiple smaller reads vs one larger one Posted Jun 15, 2022 19:34 UTC (Wed) by mbligh (subscriber, #7720) [ Link ] (5 responses) If userspace issues a request for 1 byte, is the latency substantially higher for them to get the result if we issue 1x 1MB read rather than 4x 256KB ones? Or are we smart enough to return immediately on any partial read completing? Multiple smaller reads vs one larger one Posted Jun 15, 2022 23:04 UTC (Wed) by Paf (subscriber, #91811) [ Link ] (4 responses) Depends on the file system and storage details of course but in general as soon as the needed page is in cache the read will return. The question is how did we get it there, so how much faster did the first page arrive than the very last… etc Multiple smaller reads vs one larger one Posted Jun 15, 2022 23:06 UTC (Wed) by Paf (subscriber, #91811) [ Link ] Oh and also: to what extent the reading occurs in another thread, duh. Networked file systems often have daemons, local ones probably don’t, so they’ll just finish it all before returning. Multiple smaller reads vs one larger one Posted Jun 18, 2022 17:07 UTC (Sat) by willy (subscriber, #9762) [ Link ] (2 responses) Alas, not as true as you'd like it to be. The read will return as soon as the relevant page in the cache is marked Uptodate and unlocked. Typically that happens at the end of the I/O in the bio completion routine (... or the networking equivalent). So while the data arrives earlier (probably -- some transports can send data out of order), we're only notified when the entire I/O completes. It's a standard latency vs bandwidth tradeoff. If we were notified for each page, we'd spend much more CPU processing completions, but reads would complete faster. We've chosen a model that readahead should always be in advance of the application, so we don't need to spend the extra CPU to track at that granularity. Multiple smaller reads vs one larger one Posted Jun 23, 2022 17:04 UTC (Thu) by mrugiero (guest, #153040) [ Link ] (1 responses) Is there a way to restrict it to two notifications only, one for the range requested and one for the whole thing? I'm guessing no but I'm not well versed on this so I'd rather ask. Multiple smaller reads vs one larger one Posted Jun 23, 2022 17:13 UTC (Thu) by willy (subscriber, #9762) [ Link ] Sure! We could submit two bio's, one for the range that's needed right now, and one for the range that's speculatively needed. But generally all of the range is brought in speculatively, so this probably won't help many workloads. If you try to implement this, I'd love to see the results. Fairness and limited I/O bandwidth Posted Jun 15, 2022 20:34 UTC (Wed) by epa (subscriber, #39769) [ Link ] How does this impact fairness calculations? On a heavily loaded system, where there is contention for filesystem reads (either because of bandwidth, or seek time), suppose a process is parsimoniously reading just the first hundred bytes of a file. But the kernel's readahead slurps the whole first megabyte. Will the I/O scheduler penalize that process for the whole I/O performed, or does the accounting work only on what was requested? A discussion on readahead Posted Jun 15, 2022 22:16 UTC (Wed) by MattBBaker (guest, #28651) [ Link ] (1 responses) It really feels like what is actually needed is to separate readahead into two separate concepts. One that exposes performance characteristics based on fixed parameters such as FS type, device type, and link type, and then another optimizer that can look at those parameters, get a feel for what kind of insane things the user is doing, and start making smarter choices based on that. That way the system can behave differently when the user is doing one big read off of a well designed local filesystem and small reads off a remote and slow filesystem. A discussion on readahead Posted Jun 18, 2022 17:23 UTC (Sat) by willy (subscriber, #9762) [ Link ] If you'd like to work on this, send me an email and we can discuss! A discussion on readahead Posted Jun 16, 2022 12:13 UTC (Thu) by jgh (guest, #92451) [ Link ] If bulk-data NFS ops blocking tiny-ops is an issue, separation to a pair of TCP connections seems obvious. Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/jira/solutions/program-management#tab-e7093dda-4de9-4723-a218-5c3ebe4c52b7 | 计划管理 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 Jira 为计划管理助力 使用 Jira 简化、精简、交付 了解 Jira 如何帮助您和您的团队将宏伟目标转化为可实现的项目。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行计划管理？ 克服复杂性 无论有多少团队参与其中，即使是最艰巨的战略计划，也要分解成可实现的小步骤。 驾驭依赖关系 在潜在的中断和不确定性影响团队工作之前，提前做好准备。 全面的可见性 查看和组织各团队的工作，以便更好地管理资源配置，做出明智的战略决策。 专为计划管理而设计的模板 适用于各类计划、项目和举措的可定制模板。 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 确定任务的优先次序，管理团队工作量，跟踪工作从规划到完成的整个过程。 开始使用 顶层规划 为您的团队提供清晰、实时的视图，以便进行协作、安排和调整战略目标。 开始使用 流程规划 让您的团队不再重复流程。对各种流程中的步骤进行分类，以便您和您的团队能够快速识别未完成的任务。 开始使用 甘特图 一款强大的可视化工具，用于跟踪工作和避开障碍。概述项目工期，指明里程碑并绘制依赖关系。 开始使用 个人任务跟踪器 跟踪个人任务，如电子邮件分类、会议准备和费用管理。 开始使用 计划和启动项目，全部从 Jira 中进行 规划 需求不断变化？没有关系 分析项目并自信地与利益相关者沟通，明确进度和优先事项。 执行和跟踪 协调工作，简化流程 跟踪项目，映射依赖关系，建立跨团队的审批工作流，并确保目标如期实现。 报告和结果 完善工作流程 有了触手可及的项目摘要，您就能更明智地制定计划，并随时掌握各项举措和项目的进展情况。 计划面板公开测试版 计划或季度规划的新界面 计划面板公开测试版 计划或季度规划的新界面 通过简单的拖放式计划功能，为下个季度规划多个团队的工作。 了解更多 集成您最喜欢的所有工具 将您的工具与 Jira 巧妙地集成，而无需在平台之间进行上下文切换。 查看更多集成 计划管理资源 浏览免费教程、文章和指南以了解更多信息。 敏捷教练 将数十年的敏捷实践提炼成简单易读的课程。 了解更多 项目管理指南 帮助您计划和管理项目的分步说明。 了解更多 协调业务和技术团队 了解如何打破孤岛，开展合作以便创造更好的产品。 阅读博客 转换工作方式 免费获取 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://aws.amazon.com/pt/products/networking/ | Redes e entrega de conteúdo na AWS – Amazon Web Services Pular para o conteúdo principal Filter: Todos English Entre em contato conosco AWS Marketplace Suporte Minha conta Pesquisar Filter: Todos Faça login no console Criar conta Redes e entrega de conteúdo Visão geral Áreas de solução Parceiros Produtos › Redes e entrega de conteúdo na AWS Redes e entrega de conteúdo na AWS Execute todas as workloads em uma rede global confiável e segura Visão geral Obtenha o conjunto mais amplo e profundo de serviços de rede e de entrega de conteúdo do mundo com a AWS. Execute aplicações com o mais alto nível de confiabilidade, segurança e performance na nuvem. Reproduzir Benefícios Mais segurança Conheça os requisitos mais rigorosos de segurança do mundo com os recursos de rede da AWS. Garanta a confidencialidade, a integridade e a disponibilidade dos seus dados por meio de monitoramento de infraestrutura 24 horas por dia, 7 dias por semana. Maior disponibilidade de rede Mantenha os níveis mais elevados de disponibilidade para suas workloads de missão crítica usando o modelo de zona de disponibilidade (AZ)/regiões da AWS. Os analistas do setor reconhecem o modelo de AZ como a abordagem recomendada para executar aplicações corporativas que exigem alta disponibilidade. Performance consistentemente elevada Execute suas workloads usando a rede na nuvem com mais elevada taxa de transferência e a mais baixa latência. Use a rede da AWS para fornecer aplicações aos seus clientes com taxas de resposta mais rápidas. Maior cobertura global Forneça aplicações e conteúdo a qualquer lugar do mundo por uma rede com propósito específico. A AWS oferece a infraestrutura com a maior presença global comparado a qualquer outro provedor. Maximize a eficiência e reduza os custos migrando para a AWS A empresa de análise Enterprise Strategy Group confirmou que as organizações reduziram os custos de rede, computação e armazenamento em até 66% ao migrar para a AWS. Leia o relatório Serviços de redes e entrega de conteúdo da AWS Fundamentos de rede Personalize e controle seu ambiente de rede com a Amazon Virtual Private Cloud (VPC) Saiba mais AWS Transit Gateway Simplifique sua rede com VPCs e redes on-premises conectadas a um único gateway Saiba mais AWS PrivateLink Estabeleça conectividade privada entre VPCs e serviços da AWS e on-premises Saiba mais Redes para aplicações Amazon VPC Lattice Simplifique a conectividade, a segurança e o monitoramento serviço a serviço Saiba mais AWS AppMesh Conecte contêineres e microsserviços com rede ao nível de aplicações Saiba mais AWS API Gateway Crie, mantenha e proteja APIs em qualquer escala Saiba mais AWS Cloud Map Descubra e acesse os recursos de serviço mais atualizados Saiba mais Elastic Load Balancing Distribua o tráfego de rede para aprimorar a escalabilidade da aplicação Saiba mais Redes de borda Amazon CloudFront Entregue dados, vídeos, aplicações e APIs com velocidades de transferência elevadas e baixa latência Saiba mais Amazon Route 53 Direcione os usuários finais para aplicações da internet com um Sistema de Nomes de Domínio (DNS) de baixo custo e gerenciado Saiba mais AWS Global Accelerator Otimize o tráfego de usuários para a sua aplicação Saiba mais Conectividade AWS Direct Connect Estabeleça uma conexão privada dedicada entre a AWS e o seu datacenter, escritório ou ambiente de colocalização Saiba mais AWS Site-to-Site VPN Crie uma conexão criptografada entre sua rede e seus Amazon VPCs ou AWS Transit Gateways Saiba mais AWS Client VPN Conecte seu quadro de funcionários remotos à AWS ou on-premises com uma rede privada virtual (VPN) Saiba mais AWS Cloud WAN Crie, gerencie e monitore facilmente redes globais de longa distância Saiba mais AWS Interconnect multinuvem (prévia) Conexões privadas simples, resilientes e de alta velocidade com outros provedores de serviços em nuvem Saiba mais AWS Interconnect última milha (prévia fechada) Conecte seus locais remotos à AWS com apenas alguns cliques Saiba mais Segurança de rede AWS Shield Proteja suas aplicações da AWS contra ataques de negação de serviço distribuída (DDoS) Saiba mais AWS WAF Proteja suas aplicações Web contra explorações comuns na Web Saiba mais AWS Network Firewall Implante segurança de rede nas suas VPCs da Amazon Saiba mais AWS Firewall Manager Configure e gerencie regras de firewall de maneira centralizada Saiba mais Áreas de solução Crie fundamentos sólidos de rede Controle seu tráfego de rede complexo com fundamentos de rede da AWS. Simplifique o lançamento de recursos, o gerenciamento de rede, a conectividade e o monitoramento de tráfego com serviços como Amazon VPC, AWS Transit Gateway, AWS PrivateLink, Amazon VPC Flow Logs e VPC Traffic Mirroring. Saiba mais Conecte a infraestrutura híbrida Conecte os serviços executados na AWS e no seu local com comunicação de rede eficiente e segura. As soluções de conectividade híbrida da AWS fornecem uma gama de tipos de conexões e serviços para criar redes híbridas que funcionam de forma transparente na nuvem, on-premises e até na borda da rede. Saiba mais Entregue aplicações mais rápidas e mais seguras com redes de borda Entregue aplicações e dados de usuários com maior segurança e baixa latência usando redes de borda. Mova o tráfego para fora da internet e para a rede na nuvem mais segura e com melhor performance do mundo. Amazon CloudFront, AWS Global Accelerator e Amazon Route 53 entregam seus dados com segurança, baixa latência e alto throughput. Saiba mais Simplifique as redes para aplicações Simplifique e aprimore sua arquitetura de rede de aplicações com as redes para aplicações da AWS. Elastic Load Balancing (ELB), AWS Global Accelerator (AGA) e AWS App Mesh funcionam em conjunto para fornecer melhor segurança, disponibilidade, performance e capacidades de monitoramento simplificadas. Saiba mais Soluções em destaque na AWS Descubra serviços específicos, soluções da AWS, soluções de parceiros e orientações para abordar rapidamente casos de uso comercial e técnico. Network Orchestration for AWS Transit Gateway Automatize o processo de configurar e gerenciar redes de trânsito em ambientes distribuídos da AWS. Visualize e monitore sua rede global em um único painel no Console da AWS para que você possa controlar, auditar e aprovar alterações na rede (trânsito). Comece a usar Automação de firewall para tráfego de rede na AWS Implante uma solução que automatize o processo de provisionamento de um AWS Network Firewall centralizado para inspecionar o tráfego entre suas Amazon VPCs. Comece a usar AWS Summit 2025 em Hamburgo: experimente hoje a nuvem de amanhã Junte-se a pioneiros do setor e especialistas em nuvem para um dia de aprendizado prático e oportunidades de networking que transformarão a jornada da sua empresa para a nuvem. Inscreva-se agora Crie uma conta da AWS Aprenda O que é a AWS? O que é a computação em nuvem? O que é a IA agêntica? Hub de conceitos de computação em nuvem Segurança na Nuvem AWS Novidades Blogs Comunicados à imprensa Recursos Conceitos básicos Treinamento Centro de Confiança da AWS Biblioteca de Soluções da AWS Centro de arquitetura Perguntas frequentes sobre produtos e tópicos técnicos Relatórios de analistas Parceiros da AWS Desenvolvedores Builder Center SDKs e ferramentas .NET na AWS Python na AWS Java na AWS PHP na AWS JavaScript na AWS Ajuda Entre em contato conosco Crie um tíquete de suporte AWS re:Post Centro de Conhecimento Visão geral do AWS Support Obtenha ajuda especializada Acessibilidade da AWS Jurídico English Voltar ao início A Amazon é uma empresa empregadora orientada pelos fundamentos de igualdade de oportunidades e ações afirmativas, que não faz distinção entre minorias, mulheres, portadores de deficiência, veteranos, identidade de gênero, orientação sexual nem idade. x facebook linkedin instagram twitch youtube podcasts email Privacidade Termos do site Preferências de cookies © 2026, Amazon Web Services, Inc. ou suas afiliadas. Todos os direitos reservados. | 2026-01-13T09:29:41 |
https://www.atlassian.com/pl/software/jira/guides/projects/overview | Projekty Jira: najważniejsze elementy i podstawy | Atlassian Close Czy wyświetlić tę stronę w Twoim języku ? Wszystkie języki Wybierz swój język 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Zacznij korzystać za darmo Funkcje Wszystkie funkcje Rovo w Jirze Back Rozwiązania Zespoły Przypadki użycia Rozmiar firmy Zespoły Marketing Inżynieria Projekt Eksploatacja IT Przypadki użycia Wprowadzenie Planowanie Zarządzanie kampanią Zwinne zarządzanie projektami Zarządzanie programem Rozmiar firmy Enterprise Back Przewodnik po produktach Szablony Szablony Wszystkie szablony Tworzenie oprogramowania Marketing Projekt Sprzedaż Eksploatacja Zarządzanie usługami HR Prawo Operacje IT Finanse Szablony w Jira Service Management Back Ceny Więcej + Mniej - Zacznij korzystać za darmo Back Zacznij korzystać za darmo Wprowadzenie Wprowadzenie do Jira System Jira dla zespołów 7 kroków, aby rozpocząć pracę w Jira Projekty Informacje ogólne Samouczki Zasoby Tablice Informacje ogólne Samouczki Zasoby Zgłoszenia Informacje ogólne Samouczki Zasoby Przepływy pracy Informacje ogólne Samouczki Zasoby Narzędzia Integracji Informacje ogólne Samouczki Zasoby Raporty i pulpity nawigacyjne Informacje ogólne Samouczki Zasoby Analizy Informacje ogólne Samouczki Zasoby Uprawnienia Informacje ogólne Samouczki Zasoby JQL Informacje ogólne Samouczki Ściągawka Zasoby Nawigacja Overview Tutorials Resources Automatyzacja Informacje ogólne Samouczki Zasoby Oś czasu Informacje ogólne Samouczki Zasoby Advanced Roadmaps Informacje ogólne Samouczki Zasoby Jira mobile Informacje ogólne Samouczki Zasoby Więcej informacji o systemie Jira Wersje systemu Jira Opcje hostingu Przegląd przestrzeni Jira Czym jest przestrzeń Jira? Zazwyczaj przestrzeń można zdefiniować jako zbiór zadań, które należy wykonać, aby osiągnąć określony wynik. W Jirze przestrzeń można traktować jako kontener przeznaczony do porządkowania i śledzenia tych zadań (lub zgłoszeń ) w całym zespole. Przestrzeń Jira jest wysoce konfigurowalna i można ją łatwo dostosować, aby odzwierciedlała strukturę organizacyjną, przepływ pracy lub poziom dojrzałości w zakresie metodyk Agile, co sprawia, że jest jedynym narzędziem, które można dopasować do unikatowego sposobu pracy zespołu. Zespół może wykorzystać przestrzeń Jira m.in. do śledzenia i usuwania błędów oraz uruchomienia nowej funkcji. Swoje przestrzenie można znaleźć na górnym pasku nawigacji w menu rozwijanym „Przestrzenie”. Obejrzyj pełną demonstrację Jakie są kluczowe elementy przestrzeni Jira? Jak w przypadku każdego projektu, istnieją zadania, które trzeba wykonać, ludzie, dzięki którym wszystko się dzieje, i procesy pomagające w realizacji tych prac. Zgłoszenia — przestrzenie Jira to ogólne cele, które podzielono na małe, łatwe do zrealizowania elementy prac nazywane zgłoszeniami . Ludzie — Jira ułatwia zespołom planowanie i śledzenie pracy, dzięki czemu mogą razem osiągnąć więcej. Zaproś użytkowników do swojej przestrzeni Jira, aby rozpocząć współpracę. Przepływy pracy — przestrzenie Jira są skonstruowane tak, aby odpowiadały procesowi (lub przepływowi pracy), który pozwoli zrealizować zgłoszenie od momentu jego utworzenia aż do ukończenia. Te przepływy pracy można tworzyć tak, aby pasowały do unikatowego sposobu pracy danego zespołu. Czym są szablony przestrzeni Jira? Jira oferuje kilka szablonów przestrzeni, które pomagają zespołom szybko rozpocząć pracę przy użyciu projektów dostosowanych do konkretnego zespołu (np. HR lub programistycznego) bądź przykładu zastosowania. Te szablony obejmują wstępnie skonfigurowane typy zgłoszeń, przepływy pracy oraz inne odpowiednie funkcje. Dwa z naszych najpopularniejszych szablonów to szablony Kanban i Scrum. Przejdź do biblioteki szablonów Jira Szablon Kanban pozwala zwizualizować pracę za pomocą zaawansowanej, a jednocześnie prostej w obsłudze tablicy. Jest przeznaczony dla zespołów, które ograniczają ilość prac w toku i koncentrują się na ciągłości przepływu pracy. Szablon Kanban w Jira ułatwia zespołom projektowanie i usprawnianie przepływu pracy oraz zarządzanie nim, zapewniając jednocześnie przejrzystość w miarę postępów prac. Szablon Scrum umożliwia zespołom dzielenie dużych prac na łatwiejsze w zarządzaniu fragmenty. Jest przeznaczony dla zespołów, które dostarczają prace z regularną częstotliwością lub dzielą prace na krótkie, ograniczone czasowo okresy nazywane sprintami. Szablon Scrum umożliwia zespołom także porządkowanie prac i ustalanie ich priorytetów w backlogu i na tablicy, a jednocześnie skoncentrowanie się na szerszej perspektywie dzięki harmonogramowi. Dowiedz się więcej o różnicach i podobieństwach metod Kanban i Scrum Jakie są typy przestrzeni Jira? W Jirze dostępne są dwa typy przestrzeni: zarządzane przez zespół i zarządzane przez firmę. Podstawową różnicą między tymi typami przestrzeni jest sposób administrowania nimi: przestrzeń może być zarządzana na poziomie zespołu lub na poziomie firmy / administratora Jiry. Przestrzenie zarządzane przez zespół Ogólny opis Ten typ przestrzeni jest przeznaczony dla zespołów, które potrzebują uproszczonej konfiguracji i większej kontroli nad ich własnymi procesami i praktykami roboczymi w niezależnej przestrzeni. Za zarządzanie przestrzeniami zarządzanymi przez zespół odpowiadają administratorzy projektów, co oznacza, że zmiany można wprowadzać bez konieczności korzystania z pomocy administratora Jiry. Uproszczona konfiguracja Przestrzenie zarządzane przez zespół mają domyślnie uproszczoną konfigurację. Dowolny członek zespołu może je konfigurować i obsługiwać. Przestrzenie zarządzane przez zespół są konfigurowane niezależnie, a zmiany ustawień jednej przestrzeni nie mają wpływu na inne przestrzenie. Podstawowe funkcje Nowoczesny sposób korzystania z Jiry dla zespołów, które nie potrzebują zaawansowanych funkcji. Oś czasu Wyświetlanie na tablicy tylko zgłoszeń ze swojej przestrzeni Pojedynczy aktywny sprint Podstawowe raporty Agile Przestrzenie zarządzane przez firmę Ogólny opis Ten typ projektu jest przeznaczony dla zespołów, które chcą pracować przy wielu przestrzeniach i współpracować z wieloma zespołami w bardziej znormalizowany sposób. Przestrzenie zarządzane przez firmę są zarządzane przez administratorów Jiry, którzy promują najlepsze praktyki i procesy organizacyjne, stosując wspólną konfigurację. Specjalistyczna konfiguracja Przestrzenie zarządzane przez firmę zapewniają administratorom Jiry pełną kontrolę nad konfiguracją, dostosowywaniem i elastycznością. Te przestrzenie są konfigurowane i utrzymywane przez administratorów Jiry. Konfiguracja jest współdzielona w różnych przestrzeniach. Zaawansowane funkcje Wszystkie zalety i funkcje, z których słynie Jira. Zaawansowane planowanie (tylko plan Premium) Możliwość pobierania zgłoszeń z innych przestrzeni na tablicy Możliwość uruchamiania równoległych sprintów Kompleksowe raporty Agile Dowiedz się więcej o typach przestrzeni Jira Firma Kariera Wydarzenia Blogi Relacje z inwestorami Fundacja Atlassian Materiały prasowe Skontaktuj się z nami produkty Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Zobacz wszystkie produkty Zasoby Pomoc techniczna Zakup licencji Atlassian Community Baza wiedzy Marketplace Moje konto Utwórz zgłoszenie do pomocy technicznej Poznawanie Partnerzy Szkolenia i certyfikaty Dokumentacja Zasoby dla programistów Usługi Enterprise Zobacz wszystkie zasoby Copyright © 2025 Atlassian Polityka prywatności Warunki Nota prawna Wybierz język Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://huggingface.co/models?other=qwen3 | Models – Hugging Face Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up 500B","label":"> 500B","type":"num_parameters"}]}},"orderedInferenceProviders":["groq","novita","nebius","cerebras","sambanova","nscale","fal-ai","hyperbolic","together","fireworks-ai","featherless-ai","zai-org","replicate","cohere","scaleway","publicai","baseten","black-forest-labs","clarifai","ovhcloud","hf-inference","wavespeed"]}"> Edit Models filters Main Tasks Libraries Languages Licenses Other 1 Apps llama.cpp LM Studio Jan Draw Things DiffusionBee Jellybox JoyFusion LocalAI vLLM Ollama TGI MLX LM Docker Model Runner Lemonade Inference Providers Select all Groq Novita Nebius AI Cerebras SambaNova Nscale fal Hyperbolic Together AI Fireworks Featherless AI Zai Replicate Cohere Scaleway Public AI OVHcloud AI Endpoints HF Inference API WaveSpeed Misc Reset Misc qwen3 Inference Endpoints text-generation-inference Eval Results Merge 4-bit precision custom_code 8-bit precision text-embeddings-inference Mixture of Experts Carbon Emissions Apply filters Models 35,754 Full-text search Inference Available Edit filters Sort: Trending Active filters: qwen3 Clear all NousResearch/NousCoder-14B Text Generation • 15B • Updated 7 days ago • 946 • 127 openbmb/AgentCPM-Explore 4B • Updated 1 day ago • 14 • 51 byteshape/Qwen3-30B-A3B-Instruct-2507-GGUF Text Generation • 31B • Updated 1 day ago • 9.49k • 38 ekwek/Soprano-80M Text-to-Speech • 79.7M • Updated 22 days ago • 6.91k • 278 FutureMa/Qwen3-4B-Evasion Text Classification • 4B • Updated 5 days ago • 223 • 50 nvidia/Nemotron-Orchestrator-8B Text Generation • 8B • Updated Dec 2, 2025 • 24.3k • 494 FutureMa/Eva-4B Text Generation • 4B • Updated about 19 hours ago • 34 • 21 Qwen/Qwen3-0.6B Text Generation • 0.8B • Updated Jul 26, 2025 • 8.05M • • 967 Qwen/Qwen3-4B-Instruct-2507 Text Generation • 4B • Updated Sep 17, 2025 • 2.32M • • 634 Qwen/Qwen3-Embedding-8B Feature Extraction • 8B • Updated Jul 7, 2025 • 1.35M • • 526 z-lab/Qwen3-8B-DFlash-b16 Text Generation • 1B • Updated 7 days ago • 2.24k • 14 Qwen/Qwen3-8B Text Generation • 8B • Updated Jul 26, 2025 • 3.92M • • 854 nvidia/Nemotron-Cascade-14B-Thinking Text Generation • 15B • Updated 12 days ago • 3.39k • 57 BennyDaBall/qwen3-4b-Z-Image-Engineer 4B • Updated 25 days ago • 23.2k • 137 z-lab/Qwen3-4B-DFlash-b16 Text Generation • 0.5B • Updated 7 days ago • 2.42k • 11 Qwen/Qwen3-4B Text Generation • 4B • Updated Jul 26, 2025 • 3.55M • • 522 Qwen/Qwen3-Embedding-4B Feature Extraction • 4B • Updated Jun 20, 2025 • 447k • 203 Qwen/Qwen3-4B-Thinking-2507 Text Generation • 4B • Updated Aug 6, 2025 • 376k • • 517 pnnbao-ump/VieNeu-TTS-0.3B Text-to-Speech • 0.3B • Updated 5 days ago • 2.06k • 10 Qwen/Qwen3-Embedding-0.6B Feature Extraction • 0.6B • Updated Jun 20, 2025 • 2.76M • • 821 byteshape/Qwen3-4B-Instruct-2507-GGUF Text Generation • 4B • Updated Dec 12, 2025 • 4.42k • 30 tencent/TCAndon-Router Text Generation • 4B • Updated 1 day ago • 38 • 9 unsloth/Qwen3-4B-GGUF Text Generation • 4B • Updated Jun 8, 2025 • 79.3k • 170 nikhilchandak/OpenForecaster-8B Text Generation • 8B • Updated 6 days ago • 410 • 15 Qwen/Qwen3-Reranker-8B Text Ranking • 8B • Updated Jun 9, 2025 • 489k • 207 unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF Text Generation • 31B • Updated Aug 8, 2025 • 107k • 384 nvidia/Nemotron-Cascade-8B Text Generation • 8B • Updated 12 days ago • 5.6k • 51 Qwen/Qwen3-14B Text Generation • 15B • Updated Jul 26, 2025 • 772k • • 343 deepseek-ai/DeepSeek-R1-0528-Qwen3-8B Text Generation • 8B • Updated May 29, 2025 • 40.9k • • 1.02k unsloth/DeepSeek-R1-0528-Qwen3-8B-GGUF Text Generation • 8B • Updated Jun 16, 2025 • 38.2k • 356 Previous 1 2 3 ... 100 Next System theme Company TOS Privacy About Careers Website Models Datasets Spaces Pricing Docs | 2026-01-13T09:29:41 |
https://drive.google.com/?tab=io | :root{--gm3-sys-color-on-surface-rgb:31,31,31}@media screen and (prefers-color-scheme:dark){:root{--gm3-sys-color-on-surface-rgb:227,227,227}}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.q4Wquf,.nfoC7c{display:block;height:25vh;position:relative}@media (min-width:600px){.q4Wquf,.nfoC7c{height:150px}}.q4Wquf.Irjbwb{height:auto}@media screen and (prefers-color-scheme:dark){.q4Wquf:not(.GtvzYd){display:none}}.nfoC7c{margin:0;overflow:hidden}.PwpMUe,.lVUmD{display:block;height:100%;margin:0 auto;width:100%}.St9mde{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.St9mde{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.PwpMUe,.lVUmD,.St9mde{-o-object-fit:contain;object-fit:contain}.wsArZ[data-ss-mode="1"] .q4Wquf,.wsArZ[data-ss-mode="1"] .St9mde{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .St9mde{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .q4Wquf,.NQ5OL .St9mde{height:auto;width:100%}.NQ5OL .St9mde{max-width:400px}}.q4Wquf.NWba7e,.q4Wquf.NWba7e .St9mde{height:auto}.q4Wquf.NWba7e .St9mde{height:auto;max-width:312px;width:100%}.q4Wquf.NWba7e.zpCp3 .St9mde{max-width:unset}.q4Wquf.IiQozc .St9mde{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.q4Wquf.Irjbwb .St9mde{height:auto;width:100%}.q4Wquf.EEeaqf .St9mde{max-height:144px;max-width:144px}.SnAaEd{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.SnAaEd{display:none}}.SnAaEd::after,.SnAaEd::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.SnAaEd::after,.SnAaEd::before{width:150px}}.SnAaEd::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.SnAaEd::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .SnAaEd~.St9mde{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .SnAaEd~.St9mde{width:auto}}.RHNWk .St9mde{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .RHNWk .St9mde{width:115px}}.cf660d .St9mde{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.tUhwwc .St9mde{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.Jkvqxd .St9mde{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.onc8Ic .St9mde{-webkit-transform:translate(var( --c-ps-s,24px ),0);-ms-transform:translate(var( --c-ps-s,24px ),0);transform:translate(var( --c-ps-s,24px ),0)}.WA89Yb .St9mde{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .XEN8Yb .St9mde{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .XEN8Yb .St9mde{max-width:115px}}@media (min-width:1240px) and (orientation:landscape),all and (min-width:1600px){.KyPKed .NQ5OL .XEN8Yb .St9mde{max-width:115px}}.IsSr6b .St9mde{max-width:300px}.mmskdd .St9mde{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@-webkit-keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@-webkit-keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@-webkit-keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}:root{--wf-tfs:calc(var(--c-tfs,32)/16*1rem);--wf-tfs-bp2:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp3:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp5:calc(var(--c-tfs,44)/16*1rem);--wf-stfs:calc(var(--c-stfs,16)/16*1rem);--wf-stfs-bp5:calc(var(--c-stfs,16)/16*1rem)}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.Dzz9Db,.GpMPBe{display:block;height:25vh;position:relative}@media (min-width:600px){.Dzz9Db,.GpMPBe{height:150px}}@media screen and (prefers-color-scheme:dark){.Dzz9Db:not(.GtvzYd){display:none}}.Dzz9Db.Irjbwb{height:auto}.GpMPBe{margin:0;overflow:hidden}.UFQPDd,.JNOvdd{display:block;height:100%;margin:0 auto;-o-object-fit:contain;object-fit:contain;width:100%}.f4ZpM{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.f4ZpM{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.wsArZ[data-ss-mode="1"] .Dzz9Db,.wsArZ[data-ss-mode="1"] .f4ZpM{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .f4ZpM{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .Dzz9Db,.NQ5OL .f4ZpM{height:auto;width:100%}.NQ5OL .f4ZpM{max-width:400px}}.Dzz9Db.utFBGf,.Dzz9Db.utFBGf .f4ZpM{height:auto}.Dzz9Db.utFBGf .f4ZpM{height:auto;max-width:312px;width:100%}.Dzz9Db.utFBGf.zpCp3 .f4ZpM{max-width:unset}.Dzz9Db.IiQozc .f4ZpM{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.Dzz9Db.Irjbwb .f4ZpM{height:auto;width:100%}.Dzz9Db.EEeaqf .f4ZpM{max-height:144px;max-width:144px}.nPt1pc{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.nPt1pc{display:none}}.nPt1pc::after,.nPt1pc::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.nPt1pc::after,.nPt1pc::before{width:150px}}.nPt1pc::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.nPt1pc::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .nPt1pc~.f4ZpM{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .nPt1pc~.f4ZpM{width:auto}}.ZS7CGc .f4ZpM{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .ZS7CGc .f4ZpM{width:115px}}.qiRZ5e .f4ZpM{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.vIv7Gf .f4ZpM{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.nvYXVd .f4ZpM{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.uOhnzd .f4ZpM{-webkit-transform:translate(24px,0);-ms-transform:translate(24px,0);transform:translate(24px,0)}.MsYMaf .f4ZpM{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .YIi9qf .f4ZpM{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .YIi9qf .f4ZpM{max-width:115px}}.QG3Xbe .f4ZpM{max-width:300px}.F6gtje .f4ZpM{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe{font-size:24px;width:48px;height:48px;padding:12px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-Jh9lGc{width:40px;height:40px;margin-top:4px;margin-bottom:4px;margin-right:4px;margin-left:4px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-J1Ukfc-LhBDec{max-height:40px;max-width:40px}.VfPpkd-Bz112c-LgbsSe:disabled{color:rgba(0,0,0,.38);color:var(--mdc-theme-text-disabled-on-light,rgba(0,0,0,.38))}.VfPpkd-Bz112c-LgbsSe svg,.VfPpkd-Bz112c-LgbsSe img{width:24px;height:24px}.VfPpkd-Bz112c-LgbsSe{display:inline-block;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border:none;outline:none;background-color:transparent;fill:currentColor;color:inherit;text-decoration:none;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;z-index:0;overflow:visible}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-RLmnJb{position:absolute;top:50%;height:48px;left:50%;width:48px;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-J1Ukfc-LhBDec,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-J1Ukfc-LhBDec{display:block}}.VfPpkd-Bz112c-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-Bz112c-LgbsSe[hidden]{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-KVuj8d-Q3DXx{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center}.VfPpkd-Bz112c-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:100%;width:100%;display:none}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{border-color:CanvasText}}.VfPpkd-Bz112c-kBDsod{display:inline-block}.VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd,.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd{display:inline-block}.VfPpkd-Bz112c-mRLv6{height:100%;left:0;outline:none;position:absolute;top:0;width:100%}.VfPpkd-Bz112c-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;width:100%;height:100%}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-Bz112c-LgbsSe:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe:disabled:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc{height:100%;left:0;pointer-events:none;position:absolute;top:0;width:100%;z-index:-1}.VfPpkd-dgl2Hf-ppHlrf-sM5MNb{display:inline}.VfPpkd-LgbsSe{position:relative;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:64px;border:none;outline:none;line-height:inherit;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-appearance:none;overflow:visible;vertical-align:middle;background:transparent}.VfPpkd-LgbsSe .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}.VfPpkd-LgbsSe::-moz-focus-inner{padding:0;border:0}.VfPpkd-LgbsSe:active{outline:none}.VfPpkd-LgbsSe:hover{cursor:pointer}.VfPpkd-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-LgbsSe[hidden]{display:none}.VfPpkd-LgbsSe .VfPpkd-kBDsod{margin-left:0;margin-right:8px;display:inline-block;position:relative;vertical-align:top}[dir=rtl] .VfPpkd-LgbsSe .VfPpkd-kBDsod,.VfPpkd-LgbsSe .VfPpkd-kBDsod[dir=rtl]{margin-left:8px;margin-right:0}.VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge{font-size:0;position:absolute;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);top:50%;left:50%;line-height:normal}.VfPpkd-LgbsSe .VfPpkd-vQzf8d{position:relative}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px);display:none}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-color:CanvasText}}@media screen and (forced-colors:active){.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-J1Ukfc-LhBDec,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-J1Ukfc-LhBDec{display:block}}.VfPpkd-LgbsSe .VfPpkd-RLmnJb{position:absolute;top:50%;height:48px;left:0;right:0;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%)}.VfPpkd-vQzf8d+.VfPpkd-kBDsod{margin-left:8px;margin-right:0}[dir=rtl] .VfPpkd-vQzf8d+.VfPpkd-kBDsod,.VfPpkd-vQzf8d+.VfPpkd-kBDsod[dir=rtl]{margin-left:0;margin-right:8px}svg.VfPpkd-kBDsod{fill:currentColor}.VfPpkd-LgbsSe-OWXEXe-dgl2Hf{margin-top:6px;margin-bottom:6px}.VfPpkd-LgbsSe{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;text-decoration:none}.VfPpkd-LgbsSe{padding:0 8px 0 8px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-INsAgc{border-style:solid;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-style:solid;border-color:transparent}.VfPpkd-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{z-index:0}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Jh9lGc{position:absolute;-webkit-box-sizing:content-box;box-sizing:content-box;overflow:hidden;z-index:0;top:0;left:0;bottom:0;right:0}.VfPpkd-LgbsSe{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-text-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-filled-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;-webkit-box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-protected-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled):active{-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{-webkit-box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12);box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;padding:0 15px 0 15px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-outlined-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 11px 0 15px}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 15px 0 11px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{top:-1px;left:-1px;bottom:-1px;right:-1px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-RLmnJb{left:-1px;width:calc(100% + 2px)}.nCP5yc{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.nCP5yc .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.nCP5yc:not(:disabled){background-color:rgb(26,115,232);background-color:var(--gm-fillbutton-container-color,rgb(26,115,232))}.nCP5yc:not(:disabled){color:#fff;color:var(--gm-fillbutton-ink-color,#fff)}.nCP5yc:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-fillbutton-disabled-container-color,rgba(60,64,67,.12))}.nCP5yc:disabled{color:rgba(60,64,67,.38);color:var(--gm-fillbutton-disabled-ink-color,rgba(60,64,67,.38))}.nCP5yc .VfPpkd-Jh9lGc::before,.nCP5yc .VfPpkd-Jh9lGc::after{background-color:rgb(32,33,36);background-color:var(--gm-fillbutton-state-color,rgb(32,33,36))}.nCP5yc:hover .VfPpkd-Jh9lGc::before,.nCP5yc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.16;opacity:var(--mdc-ripple-hover-opacity,.16)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24;opacity:var(--mdc-ripple-focus-opacity,.24)}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.2;opacity:var(--mdc-ripple-press-opacity,.2)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.2)}.nCP5yc .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:#fff}@media (-ms-high-contrast:active),screen and (forced-colors:active){.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.nCP5yc:hover{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:hover .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:active{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:active .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:disabled{-webkit-box-shadow:none;box-shadow:none}.nCP5yc:disabled:hover .VfPpkd-Jh9lGc::before,.nCP5yc:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.Rj2Mlf .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.Rj2Mlf:not(:disabled){color:rgb(26,115,232);color:var(--gm-hairlinebutton-ink-color,rgb(26,115,232))}.Rj2Mlf:not(:disabled){border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled):hover{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled).VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.Rj2Mlf:not(:disabled):not(.VfPpkd-ksKsZd-mWPk3d):focus{border-color:rgb(23,78,166);border-color:var(--gm-hairlinebutton-outline-color--stateful,rgb(23,78,166))}.Rj2Mlf:not(:disabled):active,.Rj2Mlf:not(:disabled):focus:active{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:disabled{color:rgba(60,64,67,.38);color:var(--gm-hairlinebutton-disabled-ink-color,rgba(60,64,67,.38))}.Rj2Mlf:disabled{border-color:rgba(60,64,67,.12);border-color:var(--gm-hairlinebutton-disabled-outline-color,rgba(60,64,67,.12))}.Rj2Mlf:hover:not(:disabled),.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.Rj2Mlf:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-hairlinebutton-ink-color--stateful,rgb(23,78,166))}.Rj2Mlf .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.Rj2Mlf .VfPpkd-Jh9lGc::before,.Rj2Mlf .VfPpkd-Jh9lGc::after{background-color:rgb(26,115,232);background-color:var(--gm-hairlinebutton-state-color,rgb(26,115,232))}.Rj2Mlf:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Rj2Mlf:disabled:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.b9hyVd{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);border-width:0;-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15))}.b9hyVd .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.b9hyVd:not(:disabled){background-color:#fff;background-color:var(--gm-protectedbutton-container-color,#fff)}.b9hyVd:not(:disabled){color:rgb(26,115,232);color:var(--gm-protectedbutton-ink-color,rgb(26,115,232))}.b9hyVd:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-protectedbutton-disabled-container-color,rgba(60,64,67,.12))}.b9hyVd:disabled{color:rgba(60,64,67,.38);color:var(--gm-protectedbutton-disabled-ink-color,rgba(60,64,67,.38))}.b9hyVd:hover:not(:disabled),.b9hyVd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.b9hyVd:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.b9hyVd:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-protectedbutton-ink-color--stateful,rgb(23,78,166))}.b9hyVd .VfPpkd-BFbNVe-bF1uUb{opacity:0}.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-B | 2026-01-13T09:29:41 |
https://www.drupal.org/node/3202049 | DrupalCamp speaker | Drupal.org Skip to main content Skip to search Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Drupal.org home Discover Drupal Drupal Core Drupal CMS Drupal AI Case Studies Drupal for Government Drupal for Higher Education Drupal for Nonprofit Drupal for eCommerce Drupal for FinTech Drupal for Healthcare Drupal for Enterprise Drupal for Retail Drupal for Travel & Tourism Build with Drupal Download Drupal Documentation Getting started Local Development Guide Developer Resources Drupal CMS User Guide Drupal User Guide API Modules Themes Distributions Issue queues Security Advisories Partners & Services Find a Drupal Certified Partner Become a Drupal Certified Partner Find a Hosting Provider Find a Migration Partner Find Training Drupal Steward Community About the Community How to Contribute DrupalCon Events Jobs / Careers News & Blogs Forum Slack Newsletters Drupal Swag Shop Support Drupal The Drupal Association Donate Become a Partner Become a Ripple Maker Become an Organization Member Drupal Swag Shop Get Started Try Drupal CMS Try Hosting Return to content Search form Search Log in Create account Community Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options. Migration Resource Center Contributor guide Find your role DrupalCamp speaker DrupalCamp speakers possess expertise, knowledge, and experience in various aspects of Drupal. This may involve having a deep understanding of Drupal's core functionalities, contributing to the Drupal community, showcasing innovative projects, or sharing insights into best practices and emerging trends within the Drupal ecosystem. Aspiring speakers should have a compelling and engaging presentation style, capable of delivering informative, relevant, and inspiring content to the audience. Impact: Having speakers at Drupal conferences is essential for several reasons. Firstly, they provide a platform for disseminating valuable information, insights, and knowledge. Speakers often share their expertise, experiences, and solutions to common challenges, benefiting attendees by offering practical guidance, innovative ideas, and industry insights. Additionally, these sessions foster networking opportunities, enabling attendees to connect with experts, share thoughts, and collaborate on potential projects or initiatives. Furthermore, speakers contribute to the vibrancy and diversity of discussions at conferences, ensuring a well-rounded event that caters to different interests and levels of expertise within the Drupal community. Overall, speakers play a vital role in driving knowledge-sharing, community engagement, and the overall success of Drupal conferences. Accountable for: Sharing knowledge and expertise Preparing content that is well-researched, informative, and relevant Delivering a presentation that is clear and engaging Answering questions Fostering constructive discussions and handling diverse perspectives Being professional, respectful, and inclusive How to get started: Answer questions from other community members at your local Drupal meetup. Offer to present a topic at your local Drupal meetup. Prepare a presentation on a topic of interest to the Drupal community, and present it at a DrupalCamp event. Skills required: Public speaking Duration: 1 hour Skills optionally used: Accessibility CSS coding Decoupled web programming Drupal site building Drupal theming / theme building JavaScript coding/programming Local development environment installation PHP coding/programming Search Engine Optimization (SEO) Site architecture Software testing (quality assurance, or QA) Teaching/Training Twig coding Web site performance Web site security Writing automated tests Spending time in this role might lead to: Mentor Contribution areas Knowledge sharing Contribute by sharing your knowledge. Read more about contributing to this area . Help improve this page Create an issue describing the problem. Need help deciding how to contribute? Visit the Community landing page to learn more about the Drupal community, or start at the top of the Contributor Guide to find roles and tasks organized by skills and community areas. Need help completing a task? Check out the Getting help with contributing section. News items News Planet Drupal Social media Sign up for Drupal news Security advisories Jobs Our community Community Services , Training & Hosting Contributor guide Groups & meetups DrupalCon Code of conduct Documentation Documentation Drupal Guide Drupal User Guide Developer docs API.Drupal.org Drupal code base Download & Extend Drupal core Modules Themes Distributions Governance of community About Web accessibility Drupal Association About Drupal.org Terms of service Privacy policy Drupal is a registered trademark of Dries Buytaert . | 2026-01-13T09:29:41 |
https://aws.amazon.com/free | Free Cloud Computing Services - AWS Free Tier Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Free Tier Overview Free Tier Categories Featured Offers for Business Terms and Conditions More AWS › AWS Free Tier Did you create an AWS account before July 15th, 2025? Access the Legacy Free Tier AWS Free Tier Gain free, hands-on experience with AWS products and services Create a Free Account New customers get up to $200 in credits New AWS customers can get started at no cost with the AWS Free Tier. Gain $100 USD credits at sign-up and up to $100 USD more to earn as you explore key AWS services. Test drive AWS services with the Free Plan for up to 6 months. You won't be charged unless you choose the Paid Plan, which allows you to scale your operations and gain access to over 150 AWS services. Free Plan Experience AWS for up to 6 months without cost or commitment ✔ Receive up to $200 USD in credits ✔ Includes free usage of select services ✔ No charges incurred unless you switch to the Paid Plan ✖ Workloads scale beyond credit thresholds ✖ Access to all AWS services and features Paid Plan Develop production-ready workloads with access to over 150 AWS services ✔ Receive up to $200 USD in credits ✔ Includes free usage of select services ✔ Pay beyond credit thresholds ✔ Workloads scale beyond credit thresholds ✔ Access to all AWS services and features Explore our offers Loading Loading Loading Loading Loading Learn more about our offers Free plan Start your AWS journey with up to $200 in Free Tier credits. Gain access to 30+ always free service. Explore and experiment with AWS services at no cost for up to 6 months. Paid plan Access our complete portfolio of 150+ AWS services with pay-as-you-go pricing, plus take advantage of 30+ Always Free services. Build and scale your solutions with confidence. Short-term trial Experience select AWS services through limited free trials. Begin your trial when you start using the service, and utilize any eligible credits for usage beyond trial limits. Always free Leverage perpetually free service offerings with specified monthly limits. When customers exceed these free usage limits or access features not included in the free tier, credits are automatically applied to cover the additional costs. Get started Getting started Sign up for an AWS account Gain instant access to the AWS Free Tier. Create an AWS account Console Start building in the console Build your production solution quickly and easily once you're ready Learn More FAQs Have more questions? Learn more with our Frequently Asked Questions. Learn More Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages. Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:41 |
https://git-scm.com/book/fa/v2/%da%af%db%8c%d8%aa-%d8%aa%d9%88%d8%b2%db%8c%d8%b9%e2%80%8c%d8%b4%d8%af%d9%87-Distributed-git-%d8%ac%d8%b1%db%8c%d8%a7%d9%86%e2%80%8c%d9%87%d8%a7%db%8c-%da%a9%d8%a7%d8%b1%db%8c-%d8%aa%d9%88%d8%b2%db%8c%d8%b9%e2%80%8c%d8%b4%d8%af%d9%87-Distributed-Workflows | Git - جریانهای کاری توزیعشده (Distributed Workflows) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 5.1 گیت توزیعشده (Distributed git) - جریانهای کاری توزیعشده (Distributed Workflows) حال که یک مخزن ریموت گیت راهاندازی شده به عنوان کانونی برای تمام توسعهدهندگان دارید تا کدهایشان را روی آن به اشتراک بگذارند و شما با دستورات پایهٔ گیت در یک روند کاری محلی آشنایی دارید، به اینکه چگونه از گیت در جهت روندهای کاری توزیعشدهای که گیت در خدمت شما قرار میدهد استفاده کنید، میپردازیم. در این فصل خواهید دید که چگونه به عنوان یک مشارکتکننده و یکپارچهساز از گیت در یک محیط توزیعشده استفاده کنید. در این مباحث، خواهید آموخت که چگونه در کد یک پروژه مشارکت موفقیتآمیز کنید و این کار را برای خود و نگهدارندهٔ پروژه تا حد امکان آسان کنید؛ همچنین اینکه چگونه میتوان یک پروژه با تعدادی توسعهدهنده را به طور موفقیتآمیز نگهداری کنید. جریانهای کاری توزیعشده (Distributed Workflows) برخلاف سیستمهای کنترل نسخه متمرکز (CVCSها)، ماهیت توزیعشده گیت به شما اجازه میدهد که در همکاری توسعهدهندگان روی پروژهها بسیار انعطافپذیرتر عمل کنید. در سیستمهای متمرکز، هر توسعهدهنده یک گره است که به طور مساوی با یک هاب مرکزی کار میکند. اما در گیت، هر توسعهدهنده میتواند هم گره باشد و هم هاب؛ یعنی هر توسعهدهنده میتواند هم به مخازن دیگر کد بدهد و هم یک مخزن عمومی نگهداری کند که دیگران بتوانند روی آن کار کنند و به آن مشارکت دهند. این موضوع امکانهای گستردهای از جریانهای کاری را برای پروژه و/یا تیم شما فراهم میکند، بنابراین ما چند الگوی رایج که از این انعطافپذیری بهره میبرند را بررسی خواهیم کرد. ما نقاط قوت و ضعف احتمالی هر طراحی را مرور میکنیم؛ شما میتوانید یکی از آنها را برای استفاده انتخاب کنید یا ویژگیهای مختلف را ترکیب کنید. جریان کاری متمرکز (Centralized Workflow) در سیستمهای متمرکز معمولاً یک مدل همکاری وجود دارد — جریان کاری متمرکز. یک هاب مرکزی یا مخزن وجود دارد که کد را میپذیرد و همه کارهای خود را با آن همگامسازی میکنند. تعدادی توسعهدهنده به عنوان گره — مصرفکنندگان آن هاب — کار میکنند و با آن مکان مرکزی همگام میشوند. نمودار 53. Centralized workflow این بدان معناست که اگر دو توسعهدهنده از هاب کلون کنند و هر دو تغییراتی ایجاد کنند، اولین توسعهدهندهای که تغییراتش را به سرور ارسال کند، بدون مشکل میتواند این کار را انجام دهد. توسعهدهنده دوم باید قبل از ارسال تغییرات خود، کار توسعهدهنده اول را با تغییرات خود ادغام کند تا تغییرات توسعهدهنده اول بازنویسی نشود. این مفهوم در گیت همانقدر درست است که در سابورژن (یا هر CVCS دیگری) درست است، و این مدل در گیت به خوبی کار میکند. اگر شما قبلاً با جریان کاری متمرکز در شرکت یا تیم خود راحت هستید، میتوانید به راحتی با گیت نیز از همین مدل استفاده کنید. فقط کافی است یک مخزن راهاندازی کنید و به همه اعضای تیم دسترسی ارسال (push) بدهید؛ گیت اجازه نمیدهد کاربران تغییرات همدیگر را بازنویسی کنند. فرض کنیم جان و جسیکا هر دو همزمان شروع به کار میکنند. جان تغییراتش را تکمیل میکند و آنها را به سرور ارسال میکند. سپس جسیکا تلاش میکند تغییراتش را ارسال کند اما سرور آن را رد میکند. به او گفته میشود که در تلاش برای ارسال تغییرات غیرپیشرو (non-fast-forward) است و نمیتواند این کار را انجام دهد مگر اینکه تغییرات را بگیرد (fetch) و ادغام (merge) کند. این جریان کاری برای بسیاری جذاب است چون الگویی است که بسیاری با آن آشنا و راحت هستند. این مدل محدود به تیمهای کوچک نیست. با مدل شاخهبندی گیت، صدها توسعهدهنده میتوانند به طور همزمان از طریق دهها شاخه روی یک پروژه کار کنند. جریان کاری مدیر ادغام (Integration-Manager Workflow) چون گیت به شما اجازه میدهد چند مخزن راه دور داشته باشید، امکان استفاده از جریانی وجود دارد که هر توسعهدهنده به مخزن عمومی خودش دسترسی نوشتن دارد و به مخازن دیگران دسترسی خواندن. این حالت معمولاً شامل یک مخزن مرجع است که نمایانگر پروژه “رسمی” است. برای مشارکت در آن پروژه، شما یک کلون عمومی از پروژه ایجاد میکنید و تغییرات خود را به آن ارسال میکنید. سپس میتوانید درخواست دهید که نگهدارنده پروژه اصلی تغییرات شما را دریافت کند. نگهدارنده میتواند مخزن شما را به عنوان یک مخزن راه دور اضافه کند، تغییرات شما را به صورت محلی تست و ادغام کند، و سپس به مخزن خودش ارسال کند. فرآیند به این صورت است (نگاه کنید به Integration-manager workflow ): نگهدارنده پروژه تغییرات را به مخزن عمومی خودش ارسال میکند. یک مشارکتکننده آن مخزن را کلون میکند و تغییراتی ایجاد میکند. مشارکتکننده تغییراتش را به نسخه عمومی خودش ارسال میکند. مشارکتکننده ایمیلی به نگهدارنده میفرستد و درخواست میکند تغییرات را دریافت کند. نگهدارنده مخزن مشارکتکننده را به عنوان مخزن راه دور اضافه میکند و تغییرات را به صورت محلی ادغام میکند. نگهدارنده تغییرات ادغام شده را به مخزن اصلی ارسال میکند. نمودار 54. Integration-manager workflow این یک جریان کاری بسیار رایج با ابزارهای مبتنی بر هاب مانند GitHub یا GitLab است که در آن به راحتی میتوان پروژه را فورک کرد و تغییرات را در فورک خود به اشتراک گذاشت. یکی از مزایای اصلی این روش این است که شما میتوانید به کار خود ادامه دهید و نگهدارنده مخزن اصلی هر زمان که بخواهد تغییرات شما را دریافت کند. مشارکتکنندگان نیازی ندارند منتظر بمانند تا پروژه تغییراتشان را بپذیرد — هر طرف میتواند با سرعت خودش کار کند. جریان کاری دیکتاتور و معاونان (Dictator and Lieutenants Workflow) این یک زیرمجموعه از جریان کاری چند مخزنه است. معمولاً در پروژههای بسیار بزرگ با صدها همکار استفاده میشود؛ یک مثال مشهور کرنل لینوکس است. چند مدیر ادغام مسئول بخشهایی از مخزن هستند؛ به آنها معاونان گفته میشود. تمام معاونان یک مدیر ادغام دارند که به او دیکتاتور خیرخواه گفته میشود. دیکتاتور خیرخواه از شاخه خودش به مخزن مرجع که همه همکاران باید از آن بگیرند، ارسال میکند. فرآیند به این صورت است (نگاه کنید به Benevolent dictator workflow ): توسعهدهندگان معمولی روی شاخه موضوعی خود کار میکنند و کارشان را روی شاخه master بازپایه (rebase) میکنند. شاخه master متعلق به مخزن مرجعی است که دیکتاتور به آن ارسال میکند. معاونان شاخههای موضوعی توسعهدهندگان را در شاخه master خود ادغام میکنند. دیکتاتور شاخههای master معاونان را در شاخه master خودش ادغام میکند. در نهایت دیکتاتور آن شاخه master را به مخزن مرجع ارسال میکند تا سایر توسعهدهندگان بتوانند روی آن بازپایه کنند. نمودار 55. Benevolent dictator workflow این نوع جریان کاری رایج نیست، اما در پروژههای بسیار بزرگ یا محیطهای سلسلهمراتبی بسیار مفید است. این امکان را به رهبر پروژه (دیکتاتور) میدهد که بخش زیادی از کار را واگذار کند و مجموعههای بزرگی از کد را در چند مرحله جمعآوری و سپس ادغام کند. الگوهایی برای مدیریت شاخههای کد منبع (Patterns for Managing Source Code Branches) یادداشت مارتین فاولر راهنمایی به نام "الگوهایی برای مدیریت شاخههای کد منبع" تهیه کرده است. این راهنما تمام جریانهای کاری رایج گیت را پوشش میدهد و توضیح میدهد که چگونه و چه زمانی از آنها استفاده کنیم. بخشی نیز دارد که فرکانسهای بالای ادغام و پایین را مقایسه میکند. https://martinfowler.com/articles/branching-patterns.html خلاصه جریانهای کاری (Workflows Summary) اینها برخی جریانهای کاری رایج هستند که با یک سیستم توزیعشده مانند گیت امکانپذیرند، اما میبینید که تنوع زیادی برای تطبیق با جریان کاری واقعی شما وجود دارد. اکنون که (امیدواریم) بتوانید ترکیب مناسبی از جریانهای کاری را برای خود مشخص کنید، به بررسی مثالهای مشخصتری از چگونگی انجام نقشهای اصلی در جریانهای مختلف میپردازیم. در بخش بعد، با چند الگوی رایج برای مشارکت در یک پروژه آشنا خواهید شد. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://novaukraine.org/ | Nova Ukraine | Heal, Build, Empower, Advocate Skip to content About Open sub-menu About Us Reports In The Press Awards Our News Events FAQ Contact Shop Donate Team Open sub-menu Board of Directors Senior Leadership Team Volunteers Staff Ambassadors Partners Careers Projects Open sub-menu Medical Aid Delivery Education Advocacy Refugees in the US Humanitarian Demining Reconstruction First Responders Internally Displaced People See All Current Projects » Giving Season 2025 Get Involved Refugee Portal Donate Search Search Search Mobile Menu Donate Magnifying Glass Show More Generic selectors Exact matches only Search in title Search in content Post Type Selectors Close search results United For Impact #StandWithUkraine LEARN MORE Donate now to support PayPal Credit Card Check & Wire Stocks Who We Are Nova Ukraine is a nonprofit organization dedicated to providing humanitarian aid to the people of Ukraine and raising awareness about Ukraine in the United States and throughout the world. Thanks to your generous donations, we fund a variety of projects to help the people of Ukraine and to strengthen Ukraine’s democratic society. The Nova Ukraine team and volunteers have been working tirelessly to help those in need. We greatly appreciate the overwhelming support from the community. For more details on our mission and vision, please visit About Us . Our Impact So Far Since 2014, Nova Ukraine has run a variety of successful humanitarian projects in Ukraine. Since 2022 to date, we have raised over $180 million and have helped over 12 million Ukrainians with an operating expense percentage in single digits. READ OUR LATEST IMPACT REPORT The Impact of Your Donations Read the Reports $142,6M+ Aid Delivered as of October 2025 $98,3M Spent on Projects $44,3M In-kind Donations * Medical Equipment People Services Life Saving First Aid Other Projects 14,23% Basic Needs Other Projects Other Medical Critical Services & Repairs 9,6% 6,76% 12,72% 16,16% 19,59% 20,94% Our Impact in Numbers as of December 2025 13,192,420+ People Helped 23,809,913+ Kilograms of Aid Delivered 165,440+ People and Animals Evacuated $1,504,034+ Fuel cards, provided to partners 3,517+ Volunteers in Ukraine 3,668,335+ Meals Served * In-kind Donations — includes goods donated directly to Nova Ukraine, as well as donations to third-parties that Nova Ukraine helped transport. Our Partners Ongoing Projects Medical Aid Delivery to Ukraine Hospitals lack medical supplies and are regularly targeted by the Russians in violation of the Geneva Convention. Access to basic medical and surgical supplies determine whether a patient lives or… Learn More Empowering Ukraine through Alternative Energy Sources Our goal is to raise funds for building renewable solar power solutions for critically hit and damaged schools in Ukraine. This will help them operate through Ukraine’s energy crisis due… Learn More Support Educational Development in Ukraine Nova Ukraine supports development of the accessible Ukrainian education during the war. We work to ensure the access to quality and safe education to orphans, children from large families, low-income… Learn More Zmistovno Learning Centers The “Nova Ukraine” Foundation has opened 50 extracurricular learning centers in Ukraine, which provide children with opportunities to engage in various educational programs, leisure activities, and peer socialization. We also… Learn More Humanitarian Demining Covering an extensive 30% of Ukraine’s territory, the danger of landmines poses a significant threat. To combat this, Nova Ukraine has stepped forward with the Humanitarian Demining Project, a targeted… Learn More Support Ukrainian Refugees in the US – Emergency Housing and Resettlement Assistance Over 271,000 Ukrainian refugees have arrived in the U.S. since the onset of Putin’s full-scale invasion, and they continue to seek safety and refuge. Displaced by the war, they are… Learn More Supporting First Responders in Ukraine Nova Ukraine is supporting first responders in different regions of Ukraine. With each missile strike or shell that hits a Ukrainian city, a brave team of first responders arrives on… Learn More Helping Internally Displaced People in Ukraine Thousands of families have been forced to leave their homes with little to no possibility to return. For many, their homes were blown up to smithereens by Russian rockets, or… Learn More Rebuilding in Ukraine The damage caused by Russian troops has already been severe, and the road to rebuild will be a long one. But with your support, our partners in Ukraine are up… Learn More More Featured Projects by NU Learn about initiatives and projects that Nova Ukraine is involved in… View More Latest News Nova Ukraine Statement Regarding the Turkey Evacuation Program of Ukrainian Children December 8, 2025 Nova Ukraine is deeply concerned by the recent media reporting on the treatment of Ukrainian children housed in facilities operated by the Ruslan Shostak Foundation in Turkey. The findings described READ MORE Керівник Офісу Президента України йде у відставку на тлі антикорупційного розслідування November 28, 2025 Під час цього масованого нападу один із медичних складів Nova Ukraine у Львові був знищений. Жоден співробітник Nova Ukraine не постраждав. На складі зберігалися медичні засоби, гуманітарні пожертви та ключове медичне обладнання, призначене для підтримки лікарень та клінік по всій Україні. READ MORE President Zelenskyy’s Chief of Staff Steps Down Following Anti-Corruption Investigation November 28, 2025 Today, President Zelenskyy’s chief of staff Andriy Yermak has resigned following an anti-corruption investigation by NABU and SAPO. Nova Ukraine hails this development as proof that the country’s post-Maidan anti-corruption READ MORE View All Updates from Facebook Nova Ukraine 1 day ago 🇺🇦 Elina Svitolina wins the ASB Classic in New Zealand and claims her 19th career WTA singles title to begin the 2026 season 🎾 Ukrainian tennis player Elina Svitolina started the year strong in Auckland, taking the WTA 250 ASB Classic after a win against Wang Xinyu of China and adding another trophy to her career collection. From all of us at Nova Ukraine, congratulations to Elina. We are excited to celebrate her achievements on and off the court! 57 2 2 View on Facebook Nova Ukraine 2 days ago In the Bay Area last month, the Nova Ukraine community got together for Vechornytsi, the annual gala celebration rooted in Ukrainian heritage and reimagined for today 💙💛 Thank you to everyone who joined for a night of music, art, and food and celebrated Ukrainian traditions that continue to live and grow far from home! 305 15 15 View on Facebook Nova Ukraine 3 days ago A wave of overnight attacks hit several regions across Ukraine. Russia launched a large strike on January 9, firing hundreds of drones and dozens of missiles toward cities across the country, including Kyiv and western regions. Explosions and fires were reported in multiple districts of the capital. At least four people were killed and more than twenty injured, including responders working at damaged sites. Residential buildings, industrial facilities, and infrastructure were hit during the assault, which continued for several hours. A hypersonic missile struck western Ukraine, damaging civilian and energy infrastructure at the impact location. The attack caused electricity and heating disruptions across affected areas. Nova Ukraine is closely monitoring the situation and coordinating with partners on the ground to support emergency response for communities affected by ongoing attacks. 165 29 15 View on Facebook Nova Ukraine 4 days ago Russia continues to weaponize winter. During the last two days, southern and eastern regions of Ukraine were under heavy attack. The main targets were energy facilities, which has led to massive power outages. The critical situation is in Dnipro, Kryvyi Rig, and Zaporizhzhia. Communities are losing access to electricity, heat, and water for long stretches of time, which forces people to adjust daily routines around outage schedules in the middle of freezing winter weather. Nova Ukraine's Points of Invincibility are supporting communities in regions affected by these disruptions. These centers are equipped with heating, reliable light, charging stations, and internet access so people can stay connected when the grid goes down. Many Points of Invincibility now offer additional services that support wider needs. Families can access clean drinking water. Children’s areas provide safe places to rest and unwind. Trained specialists offer psychological support in person, online, and by phone. In total, there are 56 centers that Nova Ukraine supports in partnership with Ukrainian Railways and Howard G. Buffet Foundation. By late 2025, more than 5 million of Ukrainians had used these hubs to stay warm, stay connected, and endure long periods without power in harsh winter conditions. + 2 128 4 4 View on Facebook Nova Ukraine 4 days ago Russia’s continued strikes on Ukraine’s energy infrastructure have caused widespread power outages across southeastern and central regions this week, plunging homes, streets, and public services into darkness in the deep of winter. In Dnipropetrovsk and Zaporizhzhia regions, electricity supplies were shut down nearly entirely, forcing many areas onto backup power and generators and stretching those limited resources to keep essential services running. In Dnipro, a strike on a power plant this week disrupted electricity, water, communications, and parts of the transport system. Apartment buildings are without reliable power, and families are relying on backup options. Without steady electricity, heating systems are strained and water access becomes unreliable. Across affected regions, daily routines are shifting. Schools and workplaces are adjusting hours, transit is slowing, and essential services are running on reserve power. Even simple tasks like reaching loved ones or checking the news are now tied to whether phones and networks stay online long enough to connect. Winter in Ukraine is long and harsh, and living without dependable electricity, heat, or water places immense pressure on communities in the midst of war. Our thoughts are with everyone facing these conditions. Nova Ukraine is closely monitoring the situation and coordinating with partners on the ground to support emergency response for communities affected by ongoing attacks. 403 22 37 View on Facebook Nova Ukraine 5 days ago Reliable delivery keeps essential support moving across Ukraine at a time when every shipment matters. With help from Nova Poshta (Нова пошта) our logistics partner in Ukraine, Nova Ukraine team shipped 65 parcels in November and December, weighing more than 2 tons. They transport everything from small parcels to large equipment to reach communities across the country. This support and dependable logistics help save lives every day and strengthen people and communities across Ukraine. 121 2 4 View on Facebook Follow Our Impact Facebook Instagram X LinkedIn YouTube Threads Stay Updated! Join our Nova Ukraine community: Sign up for our newsletter to stay informed and empowered in making a difference together! Leave this field empty if you're human: About Us Reports In the Press Awards Events FAQ Privacy Policy Team Board of Directors Leadership Volunteers Staff Ambassadors Partners Careers About Nova Ukraine Nova Ukraine is a 501(c)(3) registered non-profit organization (EIN 465335435) dedicated to raising awareness about Ukraine in the US and throughout the world and providing humanitarian aid to Ukraine. Nova Ukraine | 228 Hamilton Avenue, Floor 3, PMB 475, Palo Alto, CA 94301 PayPal, Credit or Debit Other Donation Options Save a Life Today Your donation, which is 100% tax-deductible, helps Nova Ukraine provide nutrition, water, protection, education, and life-saving health care to those affected by the ongoing war. Thanks to donors like you, we are able to rush emergency supplies to people who need them most so that Ukrainians not only survive, but thrive. Your Help Makes a Direct Impact Together. . . We make all the difference! Can I receive a tax receipt for my donation? Yes, we will provide you with a tax receipt for your donation. If you haven’t received it yet, please do not hesitate to contact us at [email protected] . What percentage of donated funds goes to actual aid? We are a volunteer-based organization, and our operational expenses are in the single-digit percent of the revenue we accumulate, meaning that the remainder is used to directly help Ukrainians. What else can I do to help support Ukraine? Learn more about how to get involved . PayPal, Credit or Debit Other Donation Options Mail => Mail-in donation to support Ukrainians through Nova Ukraine Mail check or money order to: Nova Ukraine 3277 S. White Road, PMB 8475 San Jose, CA, 95148, USA Mailing a check typically does not involve processing fees, ensuring the full amount of your donation supports our cause. Note: We cannot accept foreign (outside the United States) checks less than $250 – please donate via PayPal or wire transfer if donating from abroad. Facebook => Facebook is a convenient tool for donors to designate their donations to a chosen cause. Many fundraisers are running on Facebook to support Nova Ukraine. You can donate to an existing fundraiser or create your own. Bank Deposit, Wire, or ACH => Make a direct bank transfer to support Ukraine relief ACH Transfers (U.S. only) Bank: Chase Routing Number: 322271627 (for Direct Deposits & Electronic Payments) Account Number: 953571036 Type: Checking Bank Address: 270 Park Avenue, New York, NY Domestic Wire Transfers (U.S.) Bank: Chase Routing Number: 021000021 (for Direct Deposits & Electronic Payments) Account Number: 953571036 Type: Checking Bank Address: 270 Park Avenue, New York, NY Beneficiary: Nova Ukraine Address: 228 Hamilton Avenue, Floor 3, PMB 475, Palo Alto, CA 94301 International Wire Transfers Bank: Chase SWIFT Code: CHASUS33 Account Number: 953571036 Type: Checking Bank Address: 270 Park Avenue, New York, NY Beneficiary: Nova Ukraine Address: 228 Hamilton Avenue, Floor 3, PMB 475, Palo Alto, CA 94301 Note to our non-US donors: US banks do not use IBANs. To wire from outside the US, please use SWIFT and the account number instead. Donate Stocks or Bonds => Support humanitarian relief in Ukraine with a stock or bond donation. We are happy to receive your donation of stocks or bonds. To start the transfer, ask your stockbroker to obtain a “Letter of Authorization” from your bank. The information below is for completing your Letter of Authorization. Charitable Organization: Nova Ukraine Receiving Institution Account Number: 9458-5828 Account Title: Nova Ukraine Receiver Federal Tax ID: 46-5335435 Contact Name at Charitable Organization: Donor Operations Name of Receiving Institution: CHARLES SCHWAB & CO., INC DTC Number: 0164, Code 40 (Charles Schwab) After sending your letter of authorization to your stockbroker, we humbly request that you inform us of the donation by also forwarding the letter to [email protected] . Corporate Matching => You can double or even triple the value of your donation to Nova Ukraine through employee donation match programs. Check with your employee if donations can be matched. Find out whether your employer has a donation match program Make a donation online or using your company’s donation match portal, such as Benevity, YourCause, Deed, or CyberGrants Follow your company’s process to submit your donation receipt and request the matching contribution. If you have any questions about corporate matching—such as whether your company offers this benefit—please reach out to us at [email protected] . Our team will be happy to help you navigate this process. DAF Direct => If you have Donor Advised Fund, you can initiate a grant using the DAF Direct Link. Donate using DAF Direct Link Cryptocurrency => Nova Ukraine accepts crypto donations to help Ukraine. We support cryptocurrency donations via various wallets: Coinbase Endowment Fund Contact Us About a Donation To contact us about a donation, please reach out to [email protected] or leave a voicemail at (408) 673-4292. A volunteer will get back to you as soon as possible. Please be patient as responses may take several days. Stay Updated! Join our Nova Ukraine community: Sign up for our newsletter to stay informed and empowered in making a difference together! Leave this field empty if you’re human: X Donate PayPal Credit Card Check & Wire Stocks Donate About Open sub-menu About Us Reports In The Press Awards Our News Events FAQ Contact Shop Donate Team Open sub-menu Board of Directors Senior Leadership Team Volunteers Staff Ambassadors Partners Careers Projects Open sub-menu Medical Aid Delivery Education Advocacy Refugees in the US Humanitarian Demining Reconstruction First Responders Internally Displaced People See All Current Projects » Giving Season 2025 Get Involved Refugee Portal Donate Search We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it. Ok | 2026-01-13T09:29:41 |
https://www.atlassian.com/ru/software/jira/automation-template-library | Библиотека шаблонов Jira Automation | Atlassian Close Хотите открыть эту страницу на своем языке ? Все языки Выберите язык 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Получить бесплатно Функции Все возможности Rovo в Jira Back Решения команды Примеры использования Размер компании команды Маркетинг Разработка Дизайн Операции ИТ Примеры использования Начало работы Планирование Управление кампаниями Управление проектами по гибкой методологии Agile Управление программами Размер компании Enterprise Back Руководство по продукту Шаблоны Шаблоны Все шаблоны Разработка программного обеспечения Маркетинг Дизайн Отдел продаж Операции Управление услугами HR Юриспруденция ИТ-операции Финансовый отдел Шаблоны Jira Service Management Back Цены Дополнительно + Меньше - Получить бесплатно Back Получить бесплатно Библиотека шаблонов Jira Automation Сосредоточьтесь на самом важном. Все остальное сделает автоматизация. С сотнями шаблонов Jira Automation вам никогда не придется начинать работу с нуля. Что такое Jira Automation? Автоматизируйте любое задание или процесс парой щелчков мышью. Доступно для всех клиентов Jira Cloud: достаточно подобрать нужный шаблон — и можно экономить время, меньше отвлекаться от главного и объединять используемые инструменты. Смотреть короткое видео Популярные категории Самые популярные автоматизации Перейти к шаблонам Jira + Slack/MS Teams Перейти к шаблонам Jira + Bitbucket, GitHub или GitLab Перейти к шаблонам Jira Automation для команд разработчиков Перейти к шаблонам Jira Automation для бизнеса Перейти к шаблонам Автоматизация в Jira Service Management Перейти к шаблонам Популярные шаблоны ITSM Автоматическая публикация разбора инцидента в связанном разделе Confluence Новое При создании инцидента это правило автоматически создает страницу Confluence для разбора инцидента. Подробнее Назначение задач Автоматическое назначение задач Если задача создана без указания исполнителя, автоматически назначить ее автору. Подробнее Синхронизация задач Синхронизация работы Когда эпик завершен, переведите и все его истории в статус Done (Готово). Подробнее Уведомления Сводка за день в Slack Ежедневно отправлять в Slack сообщение со списком открытых задач в спринте. Подробнее Гибкая методология agile Суммирование оценок сложности При создании новой подзадачи суммируйте ее оценку сложности с оценкой сложности родительской задачи. Подробнее DevOps Подключение Jira и Bitbucket, GitHub или GitLab Менять статус задач в Jira при выполнении слияния запросов pull в Bitbucket, GitHub или GitLab. Подробнее «Песочница» Automation Это безопасная тестовая среда, где можно опробовать сотни шаблонов автоматизации и увидеть принцип их работы. Фильтруйте правила по меткам слева или значению в строке поиска. Быстрый старт Подключите свои инструменты Система Automation отлично работает с Jira, но если применить ее ко всем используемым продуктам, станет еще лучше. Другие ресурсы Подробнее О том, как начать работу с автоматизацией, см. в руководстве для начинающих. Смотреть руководство Присоединяйтесь к сообществу Задавайте вопросы и обменивайтесь опытом автоматизации с коллегами в разделе сообщества Jira Automation. Перейти в сообщество Перейдите на Premium Начните бесплатный пробный период Jira Premium, чтобы увеличить лимиты на автоматизацию, получить доступ к расширенному планированию и другим возможностям. Попробовать Jira Premium Компания Вакансии События Блоги Связи с инвесторами Atlassian Foundation Материалы для СМИ Свяжитесь с нами продукты Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Посмотреть все продукты Ресурсы Техническая поддержка Покупка и лицензирование Сообщество Atlassian База знаний Marketplace Мой аккаунт Заявка в поддержку Обучение Партнеры Обучение и сертификация Документация Ресурсы для разработчиков Сервисы Enterprise Смотреть все ресурсы © Atlassian, 2025 г. Политика конфиденциальности Условия использования Impressum Выберите язык Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://git-scm.com/book/pt-br/v2/Come%c3%a7ando-Pedindo-Ajuda | Git - Pedindo Ajuda About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Resumo A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 1.7 Começando - Pedindo Ajuda Pedindo Ajuda Se você precisar de ajuda para usar o Git, há três formas de acessar a página do manual de ajuda ( manpage ) para qualquer um dos comandos Git: $ git help <verb> $ git <verb> --help $ man git-<verb> Por exemplo, você pode ver a manpage do commando config rodando $ git help config Estes comandos podem ser acessados de qualquer lugar, mesmo desconectado. Se as manpages e este livro não forem suficientes e você precisar de ajuda personalizada, você pode tentar os canais #git ou #github no servidor IRC Freenode (irc.freenode.net). Estes canais estão sempre cheios com centenas de pessoas que são bem versadas com o Git e dispostas a ajudar. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/bg/v2/%d0%9a%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5-%d0%b2-Git-%d0%a1%d1%82%d1%80%d0%b0%d1%82%d0%b5%d0%b3%d0%b8%d0%b8-%d0%b7%d0%b0-%d1%80%d0%b0%d0%b1%d0%be%d1%82%d0%b0-%d1%81-%d0%ba%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5-%d0%ba%d0%be%d0%b4 | Git - Стратегии за работа с клонове код About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 3.4 Клонове в Git - Стратегии за работа с клонове код Стратегии за работа с клонове код След като вече имате основните познания за разклоняване и сливане на код, нека видим какво можете и следва да правите с тях. Тук ще разгледаме някои стандартни стратегии за работа с клонове код, които стават възможни благодарение на лекотата, с която Git управлява разклоненията. Може да решите да използвате някои от тях във вашия цикъл на разработки. Дълго използвани клонове Понеже Git използва просто трипосочно сливане, сливането на един клон с друг много пъти в продължение на дълъг период от време, е много лесно. Това означава, че можете да имате множество клонове, които са винаги отворени и които можете да ползвате за различни етапи на вашия цикъл от разработки и редовно да правите сливания на промените от един клон в друг. Много разработчици, които ползват Git, следват подобна тактика - в master клона държат само напълно стабилния код, който е вече публикуван или ще бъде публикуван. Те имат отделен паралелен клон наречен develop или next , от който работят или тестват за стабилност — този код не е непременно стабилен, но щом стане такъв, може да се слее в master клона. Той се използва за създаването на допълнителни topic branches (клонове с кратък живот, подобни на вашия iss53 ) когато са готови, за да е сигурно, че те преминават всички тестове и не предизвикват грешки. В действителност, говорим за указатели, които се преместват по линията на къмитите, които правим. Стабилните клонове са в долния край на линията на историята на къмитите, а най-новите - в горния край. Фигура 26. Линеен изглед на progressive-stability разклоняване За улеснение, можем да мислим за тях като за работни помещения, където множествата къмити преминават към "по-стабилно" помещение, когато се изтестват напълно. Фигура 27. Дървовиден изглед на progressive-stability разклоняване Можете да правите това за различни нива на стабилност. Някои по-големи проекти също така имат proposed или pu (proposed updates) клон интегриращ други такива, които може да не са готови да отидат в next или master клона. Идеята е, че клоновете код са с различни нива на стабилност и когато достигнат по-стабилен статус - се сливат с клона над тях. Да припомним отново - поддържането на long-running клонове не е необходимо, но често е полезно, особено когато си имате работа с много големи и сложни проекти. Topic клонове Topic клоновете обаче, са полезни за проекти от всякакъв мащаб. Topic клонът е клон с кратък живот, който създавате за въвеждането на единична функционалност или свързана с нея работа. Това е нещо, което най-вероятно никога не сте правили с други VCS преди Git, защото в общи линии е скъп процес с тях. Но в Git е много лесно да създавате, работите, сливате и изтривате клонове по няколко пъти на ден. Видяхте това в последната секция с клоновете iss53 и hotfix . Направихте няколко къмита в тях и ги изтрихте директно след като ги сляхте с master клона. Тази техника позволява да превключвате към различни контексти в проекта ви бързо и изцяло — понеже работата ви е изолирана в собствени клонове фокусирани в специфични задачи е по-лесно да преглеждате какво е ставало по време на специфичната разработка по даден проблем на проекта. Можете да си пазите промените там за минути, дни или месеци и да ги слеете, когато сте готови — без значение на последователността, в която са създавани или променяни. Представете си пример - работите по проект в основния клон, създавате клон за решаване на възникнал проблем ( iss91 ), работите в него известно време, създавате още един клон за да изпробвате втори начин за решаване на възникналия проблем ( iss91v2 ), връщате се отново в master клона и работите по него дълго време. В един момент ви хрумва идея, за която не сте сигурни, че е толкова добра, но за да я изпробвате, създавате клон за нея (да го наречем dumbidea ). Историята на къмитите ви би могла да изглежда така: Фигура 28. Множество topic клонове Сега нека кажем, че решавате да изберете второто решение на проблема като най-добро ( iss91v2 ) и същевременно сте показали dumbidea клона на вашите колеги и той се е оказал гениално хрумване. Можете да захвърлите клона iss91 (губейки къмитите C5 и C6 ) и да слеете в master останалите два. Тогава историята ще изглежда така: Фигура 29. Историята след сливането на dumbidea и iss91v2 Ще обърнем повече внимание на различните работни стратегии в главата [ch05-distributed-git] , така че преди да се спрете на конкретна схема за разклоняване за следващия ви проект, уверете се че сте я прочели. Важно е просто да помните, че когато правите всичко това - тези клонове са изцяло локални. Когато разклонявате и сливате, всичко се прави единствено във вашето Git хранилище - не се извършва никаква мрежова комуникация. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fcoachhub--the-digital-coaching-platform%2F&fromSignIn=true&trk=products_details_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://dsf.berkeley.edu/papers/?C=N;O=D | Index of /papers Index of /papers Name Last modified Size Description Parent Directory - www5-docs/ 1998-01-22 22:15 - www5-docs.ps.Z 1996-03-31 00:24 200K www5-docs.pdf 1997-04-12 00:27 146K worlds04-infoplane.pdf 2005-05-16 01:32 56K vldbj96.ps.Z 1997-04-11 21:49 121K vldbj96.pdf 1997-04-12 00:27 169K vldb99-gist.ps.gz 1999-06-08 09:18 87K vldb99-gist.pdf 1999-06-08 09:19 88K vldb96-reord.ps.Z 1996-09-21 21:04 132K vldb96-reord.pdf 1997-04-12 00:27 260K vldb96-cube.ps.Z 1996-09-21 21:02 147K vldb96-cube.pdf 1997-04-12 00:27 332K vldb95-tert.ps.Z 1995-10-09 18:59 83K vldb95-tert.pdf 1997-04-12 00:27 217K vldb95-rtree.ps.Z 1995-09-06 22:57 60K vldb95-rtree.pdf 1997-04-12 00:27 121K vldb95-gist.ps.Z 1995-09-06 22:56 93K vldb95-gist.pdf 1997-04-12 00:27 197K vldb93-tioga.ps.Z 1998-04-20 15:25 95K vldb93-tioga.pdf 1998-04-20 15:50 219K vldb14-hats.pdf 2013-12-26 12:25 285K vldb14-edelweiss.pdf 2014-01-06 23:39 219K vldb12-pbs.pdf 2012-09-04 21:22 719K vldb10-qpie.pdf 2010-07-12 20:05 3.9M vldb09-madskills.pdf 2009-07-06 09:43 274K vldb08-evita.pdf 2008-06-23 11:06 351K vldb08-bayesstore.pdf 2008-07-12 13:00 766K vldb06-histogram.pdpdf 2006-07-05 21:01 893K vldb06-histogram.pdf 2006-07-04 20:12 893K vldb04-stairs.pdf 2004-06-12 20:32 222K vldb04-precision.pdf 2004-06-22 01:40 225K vldb04-piersearch.pdf 2004-06-11 18:14 293K vldb04-model.pdf 2004-06-14 11:33 453K vldb03-pier.pdf 2003-06-15 23:47 168K vl98-viqing.ps.Z 1998-11-03 02:01 193K vl98-viqing.pdf 1998-11-03 02:00 110K vl98-viqing.msword.ps.Z 1998-11-03 01:59 305K vl94-zooming.ps.Z 1997-11-03 01:54 30K vl94-zooming.pdf 1997-04-12 00:27 22K vl94-zooming.msword.ps.Z 1995-06-04 03:06 61K visual99-blobworld.ps.gz 1999-08-16 18:57 135K vis95-tioga2.ps.Z 1996-03-08 19:19 315K vis95-tioga2.pdf 1997-04-12 00:27 591K vis93-tioga.ps.Z 1998-04-20 15:24 54K vis93-tioga.pdf 1998-04-20 15:50 150K vdb95-navcoord.ps.Z 1997-11-03 01:53 328K vdb95-navcoord.pdf 1997-04-12 00:27 99K vdb95-navcoord.msword.ps.Z 1995-06-04 03:12 222K vast12-interview.pdf 2012-10-23 11:44 229K vast12-XXXX/ 2012-10-23 11:48 - unpubl-perf.ps.Z 1997-08-04 16:46 79K unpubl-perf.pdf 1997-11-30 01:32 80K uist98-cid.ps.Z 1998-11-03 01:49 222K uist98-cid.pdf 1998-10-01 02:49 151K uist98-cid.msword.ps.Z 1998-09-04 02:37 401K uist12-dataplay.pdf 2012-10-15 02:11 785K uist11-wrangler.pdf 2011-08-19 09:51 289K uist10-entry.pdf 2010-07-26 23:39 1.3M uidis99-amdb.ps.gz 1999-06-26 13:16 124K uidis99-amdb.pdf 1999-06-26 13:21 124K tse88-rulemgr.ps.Z 1995-06-03 23:19 55K tse88-rulemgr.pdf 1997-04-12 00:27 68K tods98-xfunc.ps.Z 1997-11-05 16:59 208K tods98-xfunc.pdf 1997-11-05 16:59 448K tods05-tinydb.pdf 2004-11-07 19:16 2.2M stonebraker.bib 1998-11-02 16:41 41K ssdbm99.pdf 2008-08-07 14:12 90K spots06-sdlib.pdf 2006-02-28 22:12 826K spdt98-nowsort.ps 1999-08-16 19:07 152K sosp05-p2.pdf 2005-08-20 22:05 658K socc13-consistency.pdf 2013-09-16 23:23 138K socc12-explicit.pdf 2012-10-15 01:00 132K socc12-blooml.pdf 2012-10-15 00:54 295K sigrec10-declimperative.pdf 2010-11-21 17:38 198K sigmodr98-idisk.ps.Z 1998-08-25 00:36 113K sigmodr98-idisk.pdf 1998-08-25 00:37 110K sigmodr94-industry.ps.Z 1995-06-04 03:39 55K sigmodr94-industry.pdf 1997-04-12 00:27 141K sigmodr90-ucb.ps.Z 1995-06-04 02:53 31K sigmodr90-ucb.pdf 1997-04-12 00:27 32K sigmodr87-selec.ps.Z 1995-06-03 23:08 28K sigmodr87-selec.pdf 1997-04-12 00:27 32K sigmodr01-javatele.pdf 2002-03-12 13:41 167K sigmod98-ds.ps.Z 1998-08-12 00:32 134K sigmod98-ds.pdf 1998-08-12 00:32 70K sigmod98-ds.msword.ps.Z 1998-08-12 00:48 250K sigmod98-control.ps.Z 1998-08-12 00:47 204K sigmod98-control.pdf 1998-08-12 00:44 73K sigmod98-control.msword.ps.Z 1998-08-12 00:43 141K sigmod98-amdb.ps.Z 1998-08-12 00:38 12K sigmod98-amdb.pdf 1998-08-12 00:45 22K sigmod97-online.ps.Z 1997-02-14 10:55 224K sigmod97-online.pdf 1997-04-12 00:27 359K sigmod97-nowsort.ps.Z 1997-04-11 20:23 82K sigmod97-nowsort.pdf 1997-04-12 00:27 182K sigmod97-gist.ps.Z 1997-02-23 16:19 119K sigmod97-gist.pdf 1997-04-12 00:27 140K sigmod96-magic.ps.Z 1996-03-14 16:15 93K sigmod96-magic.pdf 1997-04-12 00:27 213K sigmod96-caching.pdf 2009-09-21 00:32 1.5M sigmod93-predmig.ps.Z 1995-06-04 04:11 68K sigmod93-predmig.pdf 1997-04-12 00:27 135K sigmod91-multilevel.ps.Z 1994-02-17 19:15 52K sigmod91-multilevel.pdf 1997-04-12 00:27 60K sigmod83-adt.pdf 1999-08-19 19:24 1.2M sigmod81-views.ps.Z 1997-07-22 22:52 24K sigmod81-views.pdf 1997-11-30 01:31 32K sigmod74-indep.pdf 1999-08-19 18:46 1.2M sigmod13-bolton.pdf 2013-09-16 23:26 352K sigmod11-hybridinference.pdf 2011-04-04 05:51 1.6M sigmod07-aggshare.pdf 2007-04-05 20:53 524K sigmod06-declar.pdf 2006-03-30 00:59 332K sigmod04-fluxft.pdf 2004-03-22 17:19 175K sigmod03-acqp.pdf 2003-04-28 23:41 425K sigmod02-partial.pdf 2002-03-12 13:32 423K sigmod02-cacq.pdf 2002-03-13 03:50 483K sigmod00-eddy.ps 2000-03-01 00:47 2.6M sigmod00-eddy.pdf 2000-03-01 01:02 709K sigirf91-index.ps.Z 1994-03-18 20:12 42K sigirf91-index.pdf 1997-04-12 00:27 43K sigfidet72-index.pdf 1999-08-19 18:12 1.0M sigda75-geo.ps.Z 1999-02-09 16:48 4.3M sigda75-geo.pdf 1999-02-09 16:57 3.8M sigcomm05-placelab.pdf 2005-05-11 16:55 494K sigcomm05-declarenet.pdf 2005-06-21 21:47 341K sensys07-dsn.pdf 2007-08-31 13:27 361K sec21C-privatematch.pdf 2005-04-04 23:14 185K pods97-index.ps.Z 1997-02-20 15:05 64K pods97-index.pdf 1997-04-12 00:27 185K pods13-learning.pdf 2013-08-06 20:17 1.6M podc04-pht.pdf 2005-05-16 01:32 112K pdis94-mariposa.ps.Z 1995-05-09 15:30 54K pdis94-mariposa.pdf 1997-04-12 00:27 57K pacific75-storage.pdf 1999-08-19 19:52 1.2M pacific75-model.pdf 1999-08-19 19:48 1.3M pacific75-eval.pdf 1999-08-19 19:43 702K pacific75-cupid.pdf 1999-08-19 19:39 661K osdi02-tag.pdf 2005-12-05 00:25 571K nsdi11-fate-destini.pdf 2011-03-08 22:12 516K nsdi10-hop.pdf 2010-03-11 07:41 631K ngits97-control.ps.Z 1997-08-24 21:49 63K ngits97-control.pdf 1997-11-30 01:31 134K netdb09-idodeclare.pdf 2009-08-30 22:17 222K ndss06-maelstrom.pdf 2006-02-25 20:45 373K ndss05-maelstrom.pdf 2005-11-21 10:25 371K mss95-tert.ps.Z 1995-12-22 23:07 59K mss95-tert.pdf 1997-04-12 00:27 143K mobi02-madden.pdf 2005-12-05 00:27 217K kms85-trigger.pdf 1999-08-19 19:37 1.6M jacm02-indexability.pdf 2002-10-15 20:26 177K iwoodb86-proc.pdf 1999-08-19 19:28 1.1M iptps04-hybridsearch.pdf 2004-02-16 10:30 145K iptps03-feasibility.ps 2003-04-28 22:58 103K iptps03-feasability.pdf 2003-02-10 01:05 69K iptps02-dhtquery.pdf 2002-03-12 13:45 124K ipsn09-sensorsummaries.pdf 2009-04-19 14:04 537K ipsn09-rendezvousproxy.pdf 2009-02-26 17:13 1.7M ipsn06-tours.pdf 2006-07-04 20:09 175K ipsn03-beyondavg.pdf 2003-04-28 22:42 667K iopads99-river.ps 1999-08-16 19:00 229K infocom07-pca.pdf 2007-03-05 15:02 316K index.html.old 1999-08-14 16:36 84K icod82-rules.pdf 1999-08-19 18:58 1.0M icde98-search.ps.Z 1997-11-30 01:10 79K icde98-search.pdf 1997-11-30 01:12 130K icde97-dl.ps.Z 1997-04-11 20:37 215K icde97-dl.pdf 1997-04-12 00:27 179K icde96-tioga2.ps.Z 1995-12-22 23:15 280K icde96-tioga2.pdf 1997-04-12 00:27 487K icde96-repl.ps.Z 1995-12-22 23:18 104K icde96-repl.pdf 1997-04-12 00:27 270K icde94-mariposa.ps.Z 1994-05-21 04:25 71K icde94-mariposa.pdf 1997-04-12 00:27 73K icde94-calendar.ps.Z 1995-06-04 03:41 149K icde94-calendar.pdf 1997-04-12 00:27 260K icde94-arrays.ps.Z 1994-02-17 17:38 74K icde94-arrays.pdf 1997-04-12 00:27 192K icde92-nobtree.ps.Z 1994-02-17 19:15 49K icde92-nobtree.pdf 1997-04-12 00:27 56K icde14-blazes.pdf 2013-12-26 12:28 449K icde10-usher.pdf 2009-10-20 22:24 777K icde10-ie.pdf 2010-03-11 15:37 520K icde07-proofsketch.pdf 2006-12-15 03:04 284K icde06-triage.pdf 2006-07-04 20:38 726K icde06-ken.pdf 2006-07-04 20:45 1.9M icde03-stems.pdf 2003-05-01 23:06 329K icde03-fluxlb.pdf 2003-04-28 22:53 167K icde02-fjords.pdf 2002-03-12 13:39 517K icde02-decoupled.pdf 2002-03-13 03:55 126K hpts85-nothing.ps.Z 1997-07-22 23:00 18K hpts85-nothing.pdf 1997-11-30 01:31 19K hpca98-io.ps.Z 1997-12-04 16:50 109K hpca98-io.pdf 1997-12-04 16:51 217K hotnets2005-components.pdf 2006-02-25 20:51 212K hotnets04-wakeup.pdf 2004-11-03 10:17 129K hotnets04-routing.pdf 2004-11-02 15:00 159K hotdep10-fts-dts.ps 2010-09-06 11:27 1.5M hotdep10-fts-dts.pdf 2010-09-06 11:27 257K fntdb07-architecture.pdf 2007-12-11 00:16 910K expertdb88-future.ps.Z 1995-06-03 23:18 31K expertdb88-future.pdf 1997-04-12 00:27 34K ewsn05-task.pdf 2004-12-23 14:40 1.6M eurosys10-boom.pdf 2010-02-19 13:42 302K dune07.pdf 2007-11-10 21:08 261K dtj95-s2k.ps.Z 1997-04-11 20:28 262K dtj95-s2k.pdf 1997-04-12 00:27 224K dtj95-repo.ps.Z 1997-04-11 20:29 455K dtj95-repo.pdf 1997-04-12 00:27 386K dmsn04-reduction.pdf 2004-08-06 18:09 6.3M dev12-shreddr.pdf 2012-02-15 16:22 1.4M debull98-vti.ps.Z 1998-11-02 16:51 65K debull98-vti.pdf 1998-11-02 16:52 53K debull97-reduction.ps.Z 1997-12-04 16:37 336K debull97-reduction.pdf 1997-12-04 16:42 590K debull97-online.ps.Z 1997-11-05 04:51 233K debull97-online.pdf 1997-11-30 01:31 251K debull96-ordbms.ps.Z 1997-05-09 19:21 80K debull96-ordbms.pdf 1997-05-10 18:21 131K debull96-chabot.ps.Z 1997-05-09 19:22 911K debull96-chabot.pdf 1997-05-10 18:21 438K debull93-s2k.ps.Z 1997-05-10 18:21 79K debull93-s2k.pdf 1997-05-10 18:24 113K dbtest12-bloom.pdf 2012-06-05 16:53 174K datalog2012-confluence.pdf 2012-09-04 23:41 134K datalog2011-dedalus.pdf 2012-03-05 00:03 255K data_triage_icde_2006.pdf 2006-04-11 20:48 726K compcon86-object.ps.Z 1995-06-04 03:04 30K compcon86-object.pdf 1997-04-12 00:27 34K comp95-chabot.ps.Z 1995-06-04 04:54 65K comp95-chabot.pdf 1997-04-12 00:27 88K cidr11-firstmile.pdf 2010-12-15 10:55 432K cidr11-bloom.pdf 2010-12-15 08:23 261K cidr07-phi.pdf 2006-12-15 03:09 139K cidr05-pier.pdf 2004-11-23 13:21 199K cidr03-tcq.pdf 2003-01-09 17:46 310K chiie98-info.ps.Z 1998-08-05 21:40 129K chiie98-info.pdf 1998-08-05 21:41 50K chi98-zoom.ps.Z 1998-02-21 03:27 37K chi98-zoom.pdf 1998-02-21 03:27 22K chi11-wrangler.pdf 2011-01-24 20:56 1.9M chi11-commentspace.pdf 2011-02-04 07:15 7.0M avi98-density.ps.Z 1998-01-26 01:01 244K avi98-density.pdf 1998-01-26 01:01 150K amdb.ps.gz 1999-10-18 16:26 206K amdb.pdf 1999-10-18 16:26 233K amdb-framework.ps.gz 1999-08-25 00:24 214K amdb-framework.ps.Z.old 1999-02-07 20:46 404K amdb-framework.pdf.old 1999-02-07 20:47 1.6M amdb-framework.pdf 1999-08-25 00:24 209K UW-CS-TR-1274.ps.Z 1997-05-12 17:03 157K UW-CS-TR-1274.pdf 1997-05-12 17:15 379K UW-CS-TR-1252.ps.Z 1995-06-04 04:12 41K UW-CS-TR-1252.pdf 1997-04-12 00:27 47K UCB-lattice-tr.pdf 2012-06-22 13:27 360K UCB-dedalus-semantics-tr.pdf 2011-11-29 10:32 659K UCB-PhD-woodruff.ps.Z 1999-02-11 21:08 1.7M UCB-PhD-woodruff.pdf 1999-02-11 21:08 1.0M UCB-PhD-sunita.ps.Z 1997-04-12 00:46 413K UCB-PhD-sunita.pdf 1997-05-04 23:10 784K UCB-PhD-olken.ps.Z 1997-05-04 23:01 448K UCB-PhD-olken.pdf 1997-05-04 23:08 1.0M UCB-PhD-jsidell.doc 1998-04-22 13:38 1.0M UCB-MS-zfong.ps.Z 1994-03-29 14:02 107K UCB-MS-zfong.pdf 1997-04-12 00:27 155K UCB-MS-sunita.tar.Z 1995-06-04 04:35 111K UCB-MS-plai.ps.Z 1995-06-03 23:29 61K UCB-MS-plai.pdf 1997-04-12 00:27 86K UCB-MS-paxson.tar 1995-06-04 04:38 170K UCB-MS-mao.ps.Z 1994-02-17 19:16 98K UCB-MS-mao.pdf 1997-04-12 00:27 149K UCB-MS-jtkohl.ps.Z 1994-05-21 04:15 99K UCB-MS-jtkohl.pdf 1997-04-12 00:27 194K UCB-MS-ginger.ps.Z 1995-06-04 04:48 11K UCB-MS-ginger.pdf 1997-04-12 00:27 4.2K UCB-MS-devine.tar 1995-06-04 04:43 150K UCB-MS-aoki.ps.Z 1995-06-03 23:32 62K UCB-MS-aoki.pdf 1997-04-12 00:27 93K SSDBM07-tcqfastbit.pdf 2007-04-10 23:11 378K S2K-95-66.ps.Z 1995-08-26 22:18 86K S2K-95-66.pdf 1997-04-12 00:27 91K S2K-95-65.ps.Z 1995-08-26 22:18 50K S2K-95-65.pdf 1997-04-12 00:27 52K S2K-95-64.ps.Z 1995-08-26 22:18 316K S2K-95-64.pdf 1997-04-12 00:27 587K S2K-95-63.ps.Z 1995-08-26 22:18 116K S2K-95-63.pdf 1997-04-12 00:27 131K S2K-95-62.ps.Z 1995-08-26 22:18 106K S2K-95-62.pdf 1997-04-12 00:27 284K S2K-95-60.ps.Z 1997-11-03 01:52 124K S2K-95-60.pdf 1997-04-12 00:27 107K S2K-95-60.msword.ps.Z 1995-10-18 02:35 219K S2K-94-59.ps.Z 1995-06-04 00:38 54K S2K-94-59.pdf 1997-04-12 00:27 154K S2K-94-58.ps.Z 1994-12-10 16:17 50K S2K-94-58.pdf 1997-04-12 00:27 55K S2K-94-56.ps.Z 1995-06-04 00:40 77K S2K-94-56.pdf 1997-04-12 00:27 194K S2K-94-50.ps.Z 1995-06-04 02:07 63K S2K-94-50.pdf 1997-04-12 00:27 167K S2K-94-49.ps.Z 1995-06-04 00:03 69K S2K-94-49.pdf 1997-04-12 00:27 84K S2K-94-48.ps.Z 1995-06-04 03:03 85K S2K-94-48.pdf 1997-04-12 00:27 102K S2K-94-45.ps.Z 1995-06-04 00:45 82K S2K-94-45.pdf 1997-04-12 00:27 207K S2K-94-41.ps.Z 1994-03-31 12:14 151K S2K-94-41.pdf 1997-04-12 00:58 68K S2K-93-38.ps.Z 1995-06-04 00:56 90K S2K-93-38.pdf 1997-04-12 00:27 99K S2K-93-32.ps.Z 1995-06-03 23:59 77K S2K-93-32.pdf 1997-04-12 00:27 202K S2K-93-31.ps.Z 1995-06-03 23:59 82K S2K-93-31.pdf 1997-04-12 00:27 91K S2K-93-30.ps.Z 1994-02-17 19:15 39K S2K-93-30.pdf 1997-04-12 00:27 44K S2K-93-29.ps.Z 1995-06-04 00:54 96K S2K-93-29.pdf 1997-04-12 00:27 210K S2K-93-28.ps.Z 1994-02-17 19:15 69K S2K-93-28.pdf 1997-04-12 00:27 78K S2K-93-25.ps.Z 1995-10-17 20:17 279K S2K-93-25.pdf 1997-04-12 00:27 211K S2K-93-23.ps.Z 1997-07-08 23:16 74K S2K-93-23.pdf 1997-11-30 01:31 186K S2K-92-20.ps.Z 1995-06-04 00:50 93K S2K-92-20.pdf 1997-04-12 00:27 217K S2K-92-16.ps.Z 1995-06-04 00:50 84K S2K-92-16.pdf 1997-04-12 00:27 140K S2K-92-13.ps.Z 1995-06-04 00:48 95K S2K-92-13.pdf 1997-04-12 00:27 170K S2K-92-12.ps.Z 1993-06-30 10:06 51K S2K-92-12.pdf 1997-05-12 17:11 59K S2K-91-05.ps.Z 1997-07-08 23:14 41K S2K-91-05.pdf 1997-11-30 01:30 43K S2K-91-04.ps.Z 1995-06-04 00:47 36K S2K-91-04.pdf 1997-04-12 00:27 38K S2K-91-01.ps.Z 1997-07-08 23:14 96K S2K-91-01.pdf 1997-11-30 01:27 115K LBL-TR-34229.ps.Z 1995-06-04 03:43 144K LBL-TR-34229.pdf 1997-11-30 01:25 265K Informix/ 1997-11-16 19:36 - GlobeCom2008.pdf 2010-07-27 18:31 2.5M FIND-NO-PDF 1997-11-30 01:30 212 ERL/ 2001-12-01 17:46 - ERL-M518.pdf 1999-08-13 15:16 2.9M ERL-M93-28.ps.Z 1994-04-12 12:11 381K ERL-M93-28.pdf 1997-04-12 00:27 618K ERL-M93-25.ps.Z 1995-06-03 23:35 41K ERL-M93-25.pdf 1997-04-12 00:27 50K ERL-M93-05.ps.Z 1994-05-21 04:02 424K ERL-M93-05.pdf 1997-04-12 00:27 811K ERL-M93-01.ps.Z 1994-05-21 04:13 384K ERL-M93-01.pdf 1997-04-12 00:27 651K ERL-M92-02.ps.Z 1994-05-21 04:17 71K ERL-M92-02.pdf 1997-04-12 00:27 92K ERL-M91-62.ps.Z 1994-03-18 19:43 63K ERL-M91-62.pdf 1997-04-12 00:27 80K ERL-M91-56.ps.Z 1994-02-17 19:16 51K ERL-M91-56.pdf 1997-04-12 00:27 60K ERL-M90-36.ps.Z 1994-02-17 19:15 50K ERL-M90-36.pdf 1997-04-12 00:27 61K ERL-M90-34.ps.Z 1994-02-17 19:15 88K ERL-M90-34.pdf 1997-04-12 00:27 113K ERL-M90-28.ps.Z 1995-06-04 01:51 55K ERL-M90-28.pdf 1997-04-12 00:27 74K ERL-M89-82.ps.Z 1995-06-03 23:21 30K ERL-M89-82.pdf 1997-04-12 00:27 32K ERL-M89-56.ps.Z 1995-06-04 01:24 54K ERL-M89-56.pdf 1997-04-12 00:27 71K ERL-M89-17.ps.Z 1995-06-03 22:57 34K ERL-M89-17.pdf 1997-04-12 00:27 34K ERL-M89-16.ps.Z 1995-06-03 22:47 38K ERL-M89-16.pdf 1997-04-12 00:27 45K ERL-M88-19.ps.Z 1995-06-03 23:16 56K ERL-M88-19.pdf 1997-04-12 00:27 65K ERL-M88-07.ps.Z 1994-02-17 19:15 65K ERL-M88-07.pdf 1997-04-12 00:27 73K ERL-M87-15.ps.Z 1995-06-03 23:10 45K ERL-M87-15.pdf 1997-04-12 00:27 54K ERL-M87-13.ps.Z 1994-02-17 19:15 54K ERL-M87-13.pdf 1997-04-12 00:27 70K ERL-M87-06.ps.Z 1994-02-17 19:16 60K ERL-M87-06.pdf 1997-04-12 00:27 69K ERL-M86-85.pdf 1999-08-09 14:10 15M ERL-M86-59.ps.Z 1995-06-03 23:15 34K ERL-M86-59.pdf 1997-04-12 00:27 40K ERL-M86-40.ps.Z 1994-02-17 19:16 53K ERL-M86-40.pdf 1997-04-12 00:27 69K ERL-M86-06.ps.Z 1995-06-04 02:00 43K ERL-M86-06.pdf 1997-04-12 00:27 56K ERL-M85-95.ps.Z 1994-02-17 19:15 80K ERL-M85-95.pdf 1997-04-12 00:27 97K ERL-M85-67.ps.Z 1994-02-17 19:15 47K ERL-M85-67.pdf 1997-04-12 00:27 54K ERL-M85-59.ps.Z 1994-02-17 19:15 73K ERL-M85-59.pdf 1997-04-12 00:27 88K ERL-M84-87.ps.Z 1997-07-22 22:56 18K ERL-M84-87.pdf 1997-11-30 01:28 21K ERL-M84-58.ps.Z 1997-07-22 22:57 32K ERL-M84-58.pdf 1997-11-30 01:28 37K ERL-M83-74.ps.Z 1997-07-22 22:55 24K ERL-M83-74.pdf 1997-11-30 01:28 27K CSD-98-1021.ps.Z 1998-11-02 16:32 159K CSD-98-1021.pdf 1998-11-02 16:35 230K CSD-98-1013.ps.Z 1998-10-05 22:53 102K CSD-98-1013.pdf 1998-10-05 22:52 224K CSD-98-1012.ps.Z 1998-10-05 22:54 334K CSD-98-1012.pdf 1998-10-05 22:54 273K CSD-98-1004.ps.Z 1998-08-11 14:46 106K CSD-98-1004.pdf 1998-08-11 14:46 231K CSD-97-968.ps.Z 1997-11-29 07:51 410K CSD-97-968.pdf 1997-11-29 07:51 213K CSD-97-950.ps.Z 1997-06-25 18:42 115K CSD-97-950.pdf 1997-06-10 15:23 225K CSD-97-932.ps.Z 1997-04-11 20:26 255K CSD-97-932.pdf 1997-04-12 00:27 212K CSD-96-908.ps.Z 1997-04-11 20:29 170K CSD-96-908.pdf 1997-04-12 00:27 68K CSD-95-876.ps.Z 1996-03-16 19:05 77K CSD-95-876.pdf 1997-04-12 00:27 196K CSD-83-144.ps.Z 1997-07-22 22:54 23K CSD-83-144.pdf 1997-11-30 01:30 30K COPYRIGHT 1995-06-17 20:55 952 Asilomar_Final.htm 1998-10-26 17:05 33K Asilomar_Final.doc 1998-10-26 17:05 61K | 2026-01-13T09:29:41 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Fcoachhub--the-digital-coaching-platform%3FviewConnections%3Dtrue&trk=products_details_guest_face-pile-cta | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://lwn.net/Articles/lsfmm2022/#t | The 2022 Linux Storage, Filesystem, Memory-Management, and BPF Summit [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register The 2022 Linux Storage, Filesystem, Memory-Management, and BPF Summit Please consider subscribing to LWN Subscriptions are the lifeblood of LWN.net. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Please visit this page to join up and keep LWN on the net. By Jonathan Corbet May 4, 2022 The Linux Storage, Filesystem, Memory-Management, and BPF Summit (LSFMM) has long been one of the key events for many core kernel developers. The last LSFMM event, though, was held in the innocent, pre-pandemic days of early 2019. After three years, it finally was possible to hold an in-person gathering at beginning of May 2022 in Palm Springs, California, USA. As usual, LWN was there. Plenary sessions There were no truly plenary sessions at LSFMM 2022, since the BPF group was always on its own schedule. The sessions listed below covered the storage, filesystem, and memory-management tracks. A memory-folio update : the current status and future direction of the folio project. Remote participation at LSFMM : a discussion with the remote participants on what worked—and didn't—for them. Joint filesystem/memory-management sessions Coping with hardware-poisoned page-cache pages : What should the kernel do when memory errors corrupt a page in the page cache? Dealing with negative dentries : how the kernel can manage the cache of file-name lookup failures better. Recent RCU changes : a quick overview of read-copy-update (RCU) followed by descriptions of some of the bigger changes that have gone into it over the last few years. Page pinning and filesystems : this year's discussion on how to solve the problems with get_user_pages() . Sharing memory for shared file extents : exploring a way to stop wasting memory with extents that are shared between multiple files. Joint storage/filesystem sessions Unique identifiers for NFS : how to create and manage unique IDs needed by NFS. Challenges with fstests and blktests : testing for filesystems and the block layer is an area that needs more work—and collaboration. Adding an in-kernel TLS handshake : what is the best way to add support for initiating a TLS handshake from the kernel? Maintainers don't scale : a discussion on some of the challenges faced by Linux kernel maintainers. Best practices for fstests : how to collaborate on better testing infrastructure for filesystems. ioctl() forever? : a session looking at some of the problems with using the ioctl() system call along with a few alternatives to it. Zoned storage : the challenges with supporting zoned storage and sequential-write-only zones in particular. A discussion on readahead : how much data should the kernel be speculatively reading ahead into the page cache? Memory-management sessions Ways to reclaim unused page-table pages : a lot of the memory used to hold page tables is not needed in that role and could be put to better uses. The ongoing search for mmap_lock scalability : the 2022 version of the perennial page-fault scalability topic, perhaps with some solutions on the horizon this time. Improving memory-management documentation : how to capture some of the "tribal knowledge" behind memory management and make it available to more developers. The state of memory-management development : Andrew Morton describes some changes to how memory-management patches are handled. Seeking an API for protection keys supervisor : protection keys can help to harden the kernel, but the best way of managing them is still unclear. Better tools for out-of-memory debugging : understanding out-of-memory problems is not easy; what can be done to improve the situation? Solutions for direct-map fragmentation : a number of new technologies need to carve pages out of the kernel's direct map; how can that functionality be supported without hurting performance? CXL 1: Management and tiering : the first three sessions on the Compute Express Link and how it should be managed by the Linux kernel. Proactive reclaim : there are reasons to want to reclaim memory in a more proactive manner, but it is not clear how any such feature should be controlled. Merging the multi-generational LRU : an extended discussion concluded that the time has come to merge this huge change, but some open questions remain. Sharing page tables with mshare() : page tables are not normally shared between processes, which can lead to massive overhead in situations where memory is highly shared. This session discussed a proposal for a new system call to enable page-table sharing between cooperating processes. CXL 2: Pooling, sharing, and I/O-memory resources : CXL memory can be highly dynamic, making it hard to support in the kernel. Cleaning up dying control groups, 2022 edition : progress has been made with regard to getting dying memory control groups out of the way, but the problem is not yet fully solved. get_user_pages() and COW, 2022 edition : the long slog toward making page pinning work properly in the kernel. Fixing a race in hugetlbfs : using hugetlbfs can save a lot of page-table overhead for massively shared regions, but the implementation currently has an unpleasant and difficult-to-fix bug. Preserving guest memory across kexec : a proposed mechanism to allow a host kernel to be updated while minimally disturbing guest virtual machines. Filesystem sessions Changing filesystem resize patterns : filesystems that are created small, but continually resized to be much larger, are causing some headaches. The netfslib helper library : a relatively new library to collect up common operations for network filesystems. Dynamically allocated pseudo-filesystems : a discussion on the right path for adding a general facility that would allow pseudo-filesystems (e.g. tracefs, debugfs) to reduce their memory footprint by allocating inodes and directory entries only when needed. Bringing bcachefs to the mainline : The bcachefs filesystem may be getting close to ready for merging. Snapshots, inodes, and filesystem identifiers : Filesystems that support snapshots, thus duplicate inode numbers, can be problematic. Change notifications for network filesystems : how to allow Linux clients to monitor additions, deletions, and other changes in network filesystems. Making O_TMPFILE atomic (and statx() additions) : two half-sessions looking at features that could be added for filesystems. ID-mapped mounts : a discussion on the relatively new ID-mapped mounts feature for Linux filesystems. Filesystems, testing, and stable trees : the stable and, especially, LTS trees need more filesystem testing, but it is currently hard to do. Retrieving kernel attributes : a discussion on a proposed interface for getting information out of the kernel using the extended-attribute API. Disabling an extent optimization : filesystems do not necessarily maintain holes in files as holes , rather than just regions with zeroes, which can lead to some problems. Other resources Christoph Hellwig has posted a summary of the action items from the BPF-track session on standardization. The obligatory group photo We would like to thank LWN subscribers for supporting our travel to and reporting from LSFMM 2022. Index entries for this article Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:41 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.