2015-12-16 - Structure
Minutes
Present: Philip E, Camille C, Kirstin S, Doug W
Apologies: None
Location: Online
[Meeting begins 18:30]
PE: Slack and Trello Guidelines - implement. They’re ready now (DW)
CC: Translating: who’s doing German to Eng and how? Ask Kristijan (PB)
CC: Is Pootle in action and if yes how can people use it? Perhaps not 1st priority as app not even ready yet.
PE(nis): Applicant management: preparing for the storm.
DW: Let’s brainstorm on how we want to structure the wiki - add CC
KS:
Who is the target audience of the wiki? Project team internal or external?
DW: Would suggest most content public: there is the capacity for totally private documents if we wish.
Should each ‘Team’ have a wiki-page?
DW: We can have subpages or separate spaces… different advanteages? Don’t know what though..
Should we have somewhere that the project language is English?
DW: That would be wise, if it’s our policy. Which I think it is.
Maybe consider calling glossary ‚Yunity Glossary‘ ?
DW: Sounds gut ja
KS: Ideas for Wiki:
- Calendar:
- Scheduled/Planned Wuppdays
- DW: Would totally recommend this!! All of Confluence has really finely tunable privacy and permissions.
- Team meetings (Design meetings, CoCo meetings, structure meetings etc. into the main calendar
- Other important events
- Main page:
- Center section
- Team Photo
- Announcements (Signups for upcoming events, decisions, polls, etc.)
- Project Mission &Vision
- Project Team Diagram
- Roadmap
- Right column
- Useful links (Trello, Google docs, etc.)
- Left column
- Page directory (team pages, etc.)
- Team pages
- Ask design to create a ‘logo’ / icon for each team → Open to do (not discussed)
- Calendar:
To the extent possible under law, the yunity wiki contributors have waived all copyright and related or neighboring rights to the content of the yunity wiki. More information...
You have an account but can't edit or create pages? Write us in the open chatroom or in our yunity Slack!