Latest revision as of 07:14, 2 November 2016

Reason for this meeting

Have a meeting with the new Kubuntu Council and write down the Kubuntu Vision (Manifesto), and discuss about who we are, where we are going, why are we doing this.

In this meeting we SHOULD NOT DISCUSS:

technical implementation of anything
go into in depth details about how to do a specific task, that involved dev or packaging

In this meeting we MUST DISCUSS:

Community management
Team communication
Project partnerships
Project vision

Agenda

Project Vision

What is a vision?

Why are we doing this?
What do we want to achieve?
Who are we (Kubuntu) in the world?

Team communication

What are our communication channels?
- Between devs
- With our users
Code of conduct
When do we use each communication channel and why?

What to do:

Priority 1: Document the workflow
- General steps at first and then go more in depth

Meeting got split here. Notes so far are here: https://docs.google.com/document/d/10M-hYkzHBLnPihbgk6J-u9QcYVW2y8U-jhnjo3rhq_Y/edit

Priority 2: Document how to setup a machine for development
- Have a ready made VM / container with an init script for personal details
Implement a merge request system and protocol for ANY changes in the tools we use and have control over
- New ideas to be discussed in the merge request or before

Project partnerships

This is meant to be a discussion on how we can benefit from and help other projects work. This way we don't duplicate effort with other projects

what are they doing that we can use, and not do AGAIN ourselves?
what tools do they use that we can reuse?
what workflow do they have that we can inspire from?

Partnerships

Partnership with Ubuntu
Partnership with KDE
Partnership with Debian
Partnership with Neon

Community management

To be noted...

@@ Line 1: / Line 1: @@
-Meeting:
+= Reason for this meeting =
+Have a meeting with the new Kubuntu Council and write down the Kubuntu Vision (Manifesto), and discuss about who we are, where we are going, why are we doing this.
-A) Planning for the Zesty Zapus cycle (Released April 2017, EOL January 2018)
+In this meeting we '''SHOULD NOT DISCUSS''':
-[https://community.kde.org/Schedules/Frameworks '''Frameworks'''] tags on first Sat of the month and release on following Thursday
+* technical implementation of anything
+* go into in depth details about how to do a specific task, that involved dev or packaging
-'''Plasma''' release schedule: [copied from https://community.kde.org/Schedules/Plasma_5; subject to change]
-* 5.8.3 LTS	Bugfix - Tue 2016-11-01
-* 5.8.4 LTS	Bugfix - Tue 2016-11-22
-* 5.8.5 LTS	Bugfix - Tue 2016-12-27
-* 5.9 Repo Freeze - Thu 2016-12-29: Repo freeze, list of tars for release frozen today, no new repositories will be included in release after this.
-* 5.8.95 - Feature freeze and Beta - Thu 2017-01-12	T: Message and feature freeze, Plasma/5.9 branch made
-* 5.9.0 Release	Thu 2017-01-26-Tue 2017-01-31: Final tag, only urgent fixes approved by release dude after tars please
-* 5.9.1 Bugfix	Tue 2017-02-07
-* 5.9.2 Bugfix	Tue 2017-02-14
-* 5.8.6 LTS	Bugfix	Tue 2017-02-21
-* 5.9.3 Bugfix	Tue 2017-02-28
-[https://community.kde.org/Schedules/Applications/16.08_Release_Schedule '''Applications''']:
+In this meeting we '''MUST DISCUSS''':
-* Thursday, October 13, 2016: KDE Applications 16.08.2 release
-* Thursday, November 10, 2016: KDE Applications 16.08.3 release
-B) Redefining or describing our workflow
+* Community management
+* Team communication
+* Project partnerships
+* Project vision
-C) Looking at updates for backports (xenial, yakkety)
+= Agenda =
-Workflow:
+== Project Vision ==
-In recent weeks we have been stepping on toes with uploads and changes that not everyone understands. We need a plan that everyone agrees on and understands. We need follow each other in the same direction not different ones.
+[https://community.kde.org/KDE_Visual_Design_Group/HIG/Vision What is a vision?]
+* Why are we doing this?
+* What do we want to achieve?
+* Who are we (Kubuntu) in the world?
+== Team communication ==
+* What are our communication channels?
+** Between devs
+** With our users
+* Code of conduct
+* When do we use each communication channel and why?
+What to do:
+* Priority 1: Document the workflow
+** General steps at first and then go more in depth
+-----------
+Meeting got split here. Notes so far are here: https://docs.google.com/document/d/10M-hYkzHBLnPihbgk6J-u9QcYVW2y8U-jhnjo3rhq_Y/edit
+-----------
+* Priority 2: Document how to setup a machine for development
+** Have a ready made VM / container with an init script for personal details
+* Implement a merge request system and protocol for '''ANY''' changes in the tools we use and have control over
+** New ideas to be discussed in the merge request or before
+== Project partnerships ==
+This is meant to be a discussion on how we can benefit from and help other projects work. This way we don't duplicate effort with other projects
+* what are they doing that we can use, and not do '''AGAIN''' ourselves?
+* what tools do they use that we can reuse?
+* what workflow do they have that we can inspire from?
+=== Partnerships ===
+* Partnership with Ubuntu
+* Partnership with KDE
+* Partnership with Debian
+* Partnership with Neon
+== Community management ==
+To be noted...