o3de/community issues and pull requests

#81 - added notes

Pull Request - State: closed - Opened by erickson-doug over 3 years ago

#80 - update to agenda for time

Pull Request - State: closed - Opened by erickson-doug over 3 years ago

#79 - changed file names and added reading list

Pull Request - State: closed - Opened by erickson-doug over 3 years ago

#78 - iniital checkin of agenda for 9/23

Pull Request - State: closed - Opened by erickson-doug over 3 years ago

#77 - Updated README with early Marketing committee details

Pull Request - State: closed - Opened by erickson-doug over 3 years ago

#76 - Clarify reviewer/maintainer requests

Pull Request - State: closed - Opened by NicholasVanSickle over 3 years ago

#75 - Add proposed agenda for first D&I committee meeting

Pull Request - State: closed - Opened by amelia-gm over 3 years ago

#74 - Adding community-membership.md

Pull Request - State: closed - Opened by tjmichaels over 3 years ago

#68 - List O3DE SIGs

Issue - State: closed - Opened by caniszczyk over 3 years ago - 1 comment

#67 - Run election process for TSC

Issue - State: closed - Opened by caniszczyk over 3 years ago - 1 comment

#66 - Add CHARTER.md

Issue - State: closed - Opened by caniszczyk over 3 years ago - 1 comment

#65 - List TSC members

Issue - State: closed - Opened by caniszczyk over 3 years ago - 2 comments

#64 - contributor-cheatsheet file/link is broken in CONTRIBUTING.md

Issue - State: closed - Opened by jeff-luszcz over 3 years ago - 3 comments

#63 - Proposed SIG-Core meeting agenda for JUNE-10-2021

Issue - State: closed - Opened by OBWANDO over 3 years ago - 2 comments
Labels: mtg-agenda, sig/core

#62 - Proposed SIG-Platform meeting agenda for JUN-10-2021

Issue - State: closed - Opened by OBWANDO over 3 years ago
Labels: mtg-agenda, sig/platform

#61 - Update SIG Core Charter.md

Pull Request - State: closed - Opened by amzn-pratikpa over 3 years ago

#60 - Update SIG Platform Charter.md

Pull Request - State: closed - Opened by amzn-pratikpa over 3 years ago

#59 - Need comments on community Tenets and values

Issue - State: closed - Opened by OBWANDO over 3 years ago - 4 comments
Labels: help wanted, Community

#58 - FIrst Outreach Committee Meeting

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#57 - First TAC Meeting (potentially F2F at GDC)

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#56 - First Governing Board Meeting (potentially F2F at GDC)

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#55 - LF Analytics go-live for developer, community, ecosystem insights

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#54 - Announcement Date (GDC / July 19-23, 2021)

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#53 - Pre-briefings

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#52 - Deadline for Signed Participation Agreements

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#51 - Press Release - Member Quote deadline

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#50 - Establish and populate Foundation mailing list structure

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#49 - Create White papers / End user stories

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#48 - Website draft ready

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#47 - Draft Press Release circulated for review and comment

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#46 - Develop community facing story

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#45 - Final push for submission of signed Participation Agreements

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#44 - Finalize refined messaging

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#43 - Develop enterprise facing story of benefits

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#42 - Business Development meetings at Member Summit

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#41 - Identify and begin development of training course(s)

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#40 - Hackathon event for members

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#39 - "Intent to Launch" Announcement at OSLS / LFMS

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#38 - Finalize mission statement and overarching story

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#37 - Starting push for launch partners to written agreements

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#36 - Migrate development to GitHub

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#35 - Migrate forums to be ready for use

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#34 - Web development and content begins (split project vs foundation)

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#33 - Initial technical formation workstream begins; overview

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#32 - Initial resource planning and budget overview with formation workstream

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#31 - Initial Messaging Workshop with Story change Culture

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#30 - Define layout and content to be used (o3de.org)

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Marketing

#29 - Migrate technical docs from confluence/jira to positions on open site

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#28 - Establish technical contacts list for technical workstream kick-off

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#27 - Governance docs deep-dive for formation workstream

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#26 - Determine if Discourse go forward or migrate to Github Discussions

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Technical

#25 - Initial formation workstream meeting

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#24 - Distro invite for November 10th kick-off with pitch deck

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#23 - Reserve social media handles

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#22 - Import first pass of launch schedule tasks

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#21 - Create list of initial formation invitees

Issue - State: closed - Opened by OBWANDO over 4 years ago
Labels: Business

#20 - Create training materials at launch (intro to O3DE on edX.org)

Issue - State: closed - Opened by caniszczyk over 4 years ago

#19 - Create SECURITY.md (security policy)

Issue - State: closed - Opened by caniszczyk over 4 years ago

#18 - Create project GOVERNANCE.md

Issue - State: closed - Opened by caniszczyk over 4 years ago

#17 - Create and finalize press release

Issue - State: closed - Opened by caniszczyk over 4 years ago
Labels: pr

#16 - Create SIGs

Issue - State: closed - Opened by caniszczyk over 4 years ago
Labels: tsc

#15 - Create website

Issue - State: closed - Opened by caniszczyk over 4 years ago

#14 - Host first GB meeting and setup cadence

Issue - State: closed - Opened by caniszczyk over 4 years ago

#13 - Form TSC

Issue - State: closed - Opened by caniszczyk over 4 years ago
Labels: tsc

#12 - Host first TSC meeting and set meeting cadence

Issue - State: closed - Opened by caniszczyk over 4 years ago
Labels: tsc

#11 - Is there something we can do that we're not currently doing or slated to do (probably because we're unaware of) that can help the project succeed as an open source project?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 2 comments

#10 - Will Lumberyard have write access to the LF GitHub repo?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 5 comments

#9 - How does LF deal with crash reporting or metrics gathering?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 3 comments

#8 - What are other LF projects can we reference for examples of best practices?

Issue - State: closed - Opened by OBWANDO over 4 years ago

#7 - Is there a document that outlines the specific limitations of the Github enterprise account we have access to and can we get access to that?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 1 comment

#6 - What limitations exist regarding the number and sizes of repositories we create? We're expecting to host sample projects and possibly gems, tools and 3rd party modifications in their own repositories

Issue - State: closed - Opened by OBWANDO over 4 years ago - 1 comment

#5 - What limitations exist regarding the number and sizes of our release packages?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 1 comment

#4 - Assuming we have no knowledge of other LF projects, what kind of workflow is commonplace for LF maintainers in regards to PRs and contributions?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 1 comment

#3 - If we have to host some resources outside Github because of Github rules or limitations can we use an AWS account that the foundation has access to?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 1 comment

#2 - Does LF prefer to use on-prem or cloud technologies for hosting source data, such as large binaries?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 1 comment

#1 - What CI/CD technologies are preferred by LF?

Issue - State: closed - Opened by OBWANDO over 4 years ago - 2 comments

GitHub / o3de/community issues and pull requests