[TEAM] Vote on changes to the meeting structure

[Pasi Lallinaho]

Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
mailing list. Here's the proposal again for clarity:


1) Stop running the "Team updates" section

Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those who
can't attend the meeting (which means many people per meeting), can't
paste the updates unless somebody does this for them.

Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.

The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like this
also improves their findability. As I see it, this isn't much different
from what we currently do, or at least what I try to do.

Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...

2) Rename the "Announcements" section to "Updates and Announcements"

This is just semantics, but it should be done to avoid confusion and be
more accurate.


Team members, cast your vote by sending +1, -1 or +/-0 on this list. If
you wish to vote privately, you cand send a mail to Simon or me (you'll
find the emails - or can ask on IRC).

We'll have a week for the votes. The results are gathered and published
after next Friday (or after 21UTC next Friday) when me and Simon crash
on IRC at the same time.

Cheers,
Pasi
--
Pasi Lallinaho (knome) » http://open.knome.fi/
Leader of Shimmer Project » http://shimmerproject.org/
Ubuntu member, Xubuntu Website Lead » http://xubuntu.org/

[Pasi Lallinaho]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those
who can't attend the meeting (which means many people per meeting),
can't paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like
this also improves their findability. As I see it, this isn't much
different from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and
be more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list.
If you wish to vote privately, you cand send a mail to Simon or me
(you'll find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and
published after next Friday (or after 21UTC next Friday) when me and
Simon crash on IRC at the same time.
Cheers,
Pasi

And for even further clarity:
+1 for approving the changes
-1 for keeping as it is

And obviously, my vote is +1 since I'm the one who proposes this.

Cheers,
Pasi
--
Pasi Lallinaho (knome) » http://open.knome.fi/
Leader of Shimmer Project » http://shimmerproject.org/
Ubuntu member, Xubuntu Website Lead » http://xubuntu.org/

[f***@gmx.co.uk]

Post by Pasi Lallinaho

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
[snip]

+1 for approving the changes
-1 for keeping as it is
And obviously, my vote is +1 since I'm the one who proposes this.
Cheers,
Pasi

+1 for approving the changes

[Micah Gersten]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those who
can't attend the meeting (which means many people per meeting), can't
paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like this
also improves their findability. As I see it, this isn't much different
from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and be
more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list. If
you wish to vote privately, you cand send a mail to Simon or me (you'll
find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and published
after next Friday (or after 21UTC next Friday) when me and Simon crash
on IRC at the same time.

+1

[Simon Steinbeiss]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those who
can't attend the meeting (which means many people per meeting), can't
paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like this
also improves their findability. As I see it, this isn't much different
from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and be
more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list. If
you wish to vote privately, you cand send a mail to Simon or me (you'll
find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and published
after next Friday (or after 21UTC next Friday) when me and Simon crash
on IRC at the same time.

+1

--
xubuntu-devel mailing list
xubuntu-***@lists.ubuntu.com
https <https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>://
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>lists.ubuntu.com
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>/
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>mailman
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>/
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>listinfo
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>/
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>xubuntu-devel
<https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel>


+1

[Jack Fromm]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those
who can't attend the meeting (which means many people per meeting),
can't paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like
this also improves their findability. As I see it, this isn't much
different from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and
be more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list.
If you wish to vote privately, you cand send a mail to Simon or me
(you'll find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and
published after next Friday (or after 21UTC next Friday) when me and
Simon crash on IRC at the same time.
Cheers,
Pasi

+1

[f***@gmx.co.uk]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those
who can't attend the meeting (which means many people per meeting),
can't paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like
this also improves their findability. As I see it, this isn't much
different from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and
be more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list.
If you wish to vote privately, you cand send a mail to Simon or me
(you'll find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and
published after next Friday (or after 21UTC next Friday) when me and
Simon crash on IRC at the same time.
Cheers,
Pasi

The other side of this being - how long do we wait as a team for members
of that team to vote?

I see no reason why we'd not be good to expect a response for something
'less important' as no more than a month.

For something that has importance to Xubuntu as a whole I would expect
some response somewhat faster - even if that response was 'foo' caught
me on the phone, I'm not able to vote, my feeling is *this*'

Thus we can take into consideraration people's POV.

example - there are 14 (currently) of us

we have a vote, two of us are awol (ish), team is 14

vote gets taken and stands at 6 +, 6- with 2 to vote, 1 does, the second
does *life* stuff*

at 2 weeks, the vote is now 7+,6- and the vote carries

just thinking aloud here - but how long should a team wait for one of
it's members before making that member's vote null, you have to bear in
mind here the length of a support cycle, at 6 months should we wait for
someone taking 4 months to make a preference?

just a thought, provocative perhaps, but just a thought ;)

[Pasi Lallinaho]

Post by f***@gmx.co.uk

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those
who can't attend the meeting (which means many people per meeting),
can't paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that
could be worth mentioning for people outside the team - or added in
the release notes - should be in the blueprints. Doing the updates
like this also improves their findability. As I see it, this isn't
much different from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and
be more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list.
If you wish to vote privately, you cand send a mail to Simon or me
(you'll find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and
published after next Friday (or after 21UTC next Friday) when me and
Simon crash on IRC at the same time.
Cheers,
Pasi

The other side of this being - how long do we wait as a team for
members of that team to vote?
I see no reason why we'd not be good to expect a response for
something 'less important' as no more than a month.
For something that has importance to Xubuntu as a whole I would expect
some response somewhat faster - even if that response was 'foo' caught
me on the phone, I'm not able to vote, my feeling is *this*'
Thus we can take into consideraration people's POV.
example - there are 14 (currently) of us
we have a vote, two of us are awol (ish), team is 14
vote gets taken and stands at 6 +, 6- with 2 to vote, 1 does, the
second does *life* stuff*
at 2 weeks, the vote is now 7+,6- and the vote carries
just thinking aloud here - but how long should a team wait for one of
it's members before making that member's vote null, you have to bear
in mind here the length of a support cycle, at 6 months should we wait
for someone taking 4 months to make a preference?
just a thought, provocative perhaps, but just a thought ;)

If the vote result was that close, it would most likely warrant further
discussion and not carrying on with whatever was voted on. If it's
important, and several people haven't voted after the set deadline, then
we should consider what would be the best way to either try to get a
hold of them - or resolve the issue without them.

Just my two cents,
Pasi
--
Pasi Lallinaho (knome) » http://open.knome.fi/
Leader of Shimmer Project » http://shimmerproject.org/
Ubuntu member, Xubuntu Website Lead » http://xubuntu.org/

[f***@gmx.co.uk]

Post by Pasi Lallinaho

Post by f***@gmx.co.uk

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have
been around, let's do the voting on the meeting structure changes on
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those
who can't attend the meeting (which means many people per meeting),
can't paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that
could be worth mentioning for people outside the team - or added in
the release notes - should be in the blueprints. Doing the updates
like this also improves their findability. As I see it, this isn't
much different from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to
the blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and
be more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list.
If you wish to vote privately, you cand send a mail to Simon or me
(you'll find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and
published after next Friday (or after 21UTC next Friday) when me and
Simon crash on IRC at the same time.
Cheers,
Pasi

The other side of this being - how long do we wait as a team for
members of that team to vote?
I see no reason why we'd not be good to expect a response for
something 'less important' as no more than a month.
For something that has importance to Xubuntu as a whole I would
expect some response somewhat faster - even if that response was
'foo' caught me on the phone, I'm not able to vote, my feeling is
*this*'
Thus we can take into consideraration people's POV.
example - there are 14 (currently) of us
we have a vote, two of us are awol (ish), team is 14
vote gets taken and stands at 6 +, 6- with 2 to vote, 1 does, the
second does *life* stuff*
at 2 weeks, the vote is now 7+,6- and the vote carries
just thinking aloud here - but how long should a team wait for one of
it's members before making that member's vote null, you have to bear
in mind here the length of a support cycle, at 6 months should we
wait for someone taking 4 months to make a preference?
just a thought, provocative perhaps, but just a thought ;)

If the vote result was that close, it would most likely warrant
further discussion and not carrying on with whatever was voted on. If
it's important, and several people haven't voted after the set
deadline, then we should consider what would be the best way to either
try to get a hold of them - or resolve the issue without them.
Just my two cents,
Pasi

wfm

I'd just be concerned about stagnation is all

[Elizabeth K. Joseph]

Team members, cast your vote by sending +1, -1 or +/-0 on this list. If you
wish to vote privately, you cand send a mail to Simon or me (you'll find the
emails - or can ask on IRC).

+1

Having an updates section was useful for giving us a set agenda item
to bring up our topics, but our meetings are still flexible enough
that it won't prevent any of us from bringing up topics as we need to
so I'm not worried.

[Daniel Kessel]

Post by Elizabeth K. Joseph

Team members, cast your vote by sending +1, -1 or +/-0 on this list. If you
wish to vote privately, you cand send a mail to Simon or me (you'll find the
emails - or can ask on IRC).

+1
Having an updates section was useful for giving us a set agenda item
to bring up our topics, but our meetings are still flexible enough
that it won't prevent any of us from bringing up topics as we need to
so I'm not worried.

+1 from me as well.

[Sean Davis]

+1

Post by Pasi Lallinaho

Post by Elizabeth K. Joseph

Post by Pasi Lallinaho
Team members, cast your vote by sending +1, -1 or +/-0 on this list. If

you

Post by Elizabeth K. Joseph

Post by Pasi Lallinaho
wish to vote privately, you cand send a mail to Simon or me (you'll

find the

Post by Elizabeth K. Joseph

Post by Pasi Lallinaho
emails - or can ask on IRC).

+1
Having an updates section was useful for giving us a set agenda item
to bring up our topics, but our meetings are still flexible enough
that it won't prevent any of us from bringing up topics as we need to
so I'm not worried.

+1 from me as well.
--
xubuntu-devel mailing list
https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel

[David Pires]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the mailing
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those who
can't attend the meeting (which means many people per meeting), can't paste
the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these updates
can be seen live.
The only real change in action contributors would need to take would apply
to work items. Practically this means that everything that could be worth
mentioning for people outside the team - or added in the release notes -
should be in the blueprints. Doing the updates like this also improves
their findability. As I see it, this isn't much different from what we
currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and be
more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list. If
you wish to vote privately, you cand send a mail to Simon or me (you'll
find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and published
after next Friday (or after 21UTC next Friday) when me and Simon crash on
IRC at the same time.
Cheers,
Pasi

+1 from me, also.

David Pires (slickymaster)
https://wiki.ubuntu.com/slickymaster
Xubuntu Documentation Lead

[Pasi Lallinaho]

Post by Pasi Lallinaho
Since the meetings have been far apart, and not many people have been
around, let's do the voting on the meeting structure changes on the
1) Stop running the "Team updates" section
Pasting the updates in a meeting means more work (through having to
memorize/note down items) for contributors. It also means that those
who can't attend the meeting (which means many people per meeting),
can't paste the updates unless somebody does this for them.
Since we now have a timeline tab [2] in the tracker, most of these
updates can be seen live.
The only real change in action contributors would need to take would
apply to work items. Practically this means that everything that could
be worth mentioning for people outside the team - or added in the
release notes - should be in the blueprints. Doing the updates like
this also improves their findability. As I see it, this isn't much
different from what we currently do, or at least what I try to do.
Finally, the updates that aren't worth/important enough to add to the
blueprints could still be shared in the meeting, thus...
2) Rename the "Announcements" section to "Updates and Announcements"
This is just semantics, but it should be done to avoid confusion and
be more accurate.
Team members, cast your vote by sending +1, -1 or +/-0 on this list.
If you wish to vote privately, you cand send a mail to Simon or me
(you'll find the emails - or can ask on IRC).
We'll have a week for the votes. The results are gathered and
published after next Friday (or after 21UTC next Friday) when me and
Simon crash on IRC at the same time.
Cheers,
Pasi

At least one week has passed and the vote results are:
– For: 9 public votes and 1 private vote
– Against: 0 votes

Xubuntu team has 14 members, 8 are needed to reach quorum. Quorum is
met, changes are officially approved.

I'll make the changes to the wikipage next.

Cheers,
Pasi
--
Pasi Lallinaho (knome) » http://open.knome.fi/
Leader of Shimmer Project » http://shimmerproject.org/
Ubuntu member, Xubuntu Website Lead » http://xubuntu.org/