Just thinking¶

Many places¶

My public info project¶

I have notes in here:

https://docs.typo3.org/typo3cms/drafts/github/T3DocumentationStarter/Public-Info-001/

T3DocTeam at Work¶

https://docs.typo3.org/typo3cms/Teams/T3DocTeam/

Documentation pull requests¶

https://docs.typo3.org/services/GithubPullRequests/

Emails¶

https://otrs.typo3.org/otrs/index.pl?Action=AgentTicketQueue;QueueID=26;Filter=All

Arrive in the OTRS system.

Identifying team tasks¶

In no special order:

1. provide style guides
2. provide help
3. provide infrastructure
4. handle issues
5. handle pull requests
6. maintain “documentation” at typo3.org
7. organize sprints
8. tweet! (social media)
9. apply for budget
10. produce and publish news!
11. Make sure we highlight our achievement!
12. …

• Maintain documentation page at typo3.org

  

• Provide style guides

  

• Provide help for writing

  

• Be present in the ##t3a-and-teamleaders channel:

  

• Connect to other teams, like the #t3a-content team:

  

Tasks at the sprint¶

• Deal with those long hanging pull requests.

• How do we manage Github issues?

• We have the Google document Team Sprint 2018 #2 : Possible topics

  

• Let’s look at the issues at the team document:

  

• We need to tell at “how we work” that we are using the team document issues!

What I would like to have¶

• A place where we collect the “Done!”s and successes.

Findings about CKEditor plugins here¶

Let’s talk about this as an example.

• Start

  

• Almost forgotten and buried in Slack.

• So let’s remember this:

  

• This is the helpful comment I was looking for:

  

• This leads to Forge ...