We have a few items that have backed up to deal with; please help me make sure that enough of these *decision* items make it on the agenda. Bringing them up on-list means we can work out the details *before the meeting*. This is a new paradigm for FDSCo, but one we have all spoken of following (iirc). ;-)
0. Meeting time -- [LIST DECISION]
1. Elect new chair/project leader [MEETING DECISION] 1.1 Decide if chair is 12 mon. or 6 mon. position? [MEETING DECISION] -- on-list discussion?
2. Meetings on #fedora-docs v. #fedora-meeting [MEETING DECISION]
3. Confirm FDP schedule for F7 [LIST DISCUSSION],[MEETING DECISION]
4. AOB
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karsten Wade schreef:
We have a few items that have backed up to deal with; please help me make sure that enough of these *decision* items make it on the agenda. Bringing them up on-list means we can work out the details *before the meeting*. This is a new paradigm for FDSCo, but one we have all spoken of following (iirc). ;-)
So let's get the on-list decision stuff done then :)
- Meeting time -- [LIST DECISION]
So I've been looking through our previous thread[1] on this very subject and the small consensus seemed to be the three-hour window.
Tue 2100 UTC +3 to Tue 0000 UTC +3 Tue 1800 UTC to Tue 2100 UTC Tue 1300 EST to Tue 1600 EST Tue 1000 PST to Tue 1300 PST
Is this still probable? We should identify specific "full committee" decisions ahead of time, to make sure we have a quorum hanging around. (candidates see below)
- Elect new chair/project leader [MEETING DECISION] 1.1 Decide if chair is 12 mon. or 6 mon. position? [MEETING DECISION] -- on-list discussion?
- -> This would be a candidate
Meetings on #fedora-docs v. #fedora-meeting [MEETING DECISION]
Confirm FDP schedule for F7 [LIST DISCUSSION],[MEETING DECISION]
We should consider L10N workload here, maybe only do a final version of guides on L10N-level.
- AOB
- --Bart
[1]: http://www.redhat.com/archives/fedora-docs-list/2007-February/msg00066.html
- -- Bart couf@fedoraproject.org couf@skynet.be key fingerprint: 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93
On Fri, 2007-03-02 at 19:40 +0100, Bart Couvreur wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karsten Wade schreef:
We have a few items that have backed up to deal with; please help me make sure that enough of these *decision* items make it on the agenda. Bringing them up on-list means we can work out the details *before the meeting*. This is a new paradigm for FDSCo, but one we have all spoken of following (iirc). ;-)
So let's get the on-list decision stuff done then :)
- Meeting time -- [LIST DECISION]
So I've been looking through our previous thread[1] on this very subject and the small consensus seemed to be the three-hour window.
Tue 2100 UTC +3 to Tue 0000 UTC +3 Tue 1800 UTC to Tue 2100 UTC Tue 1300 EST to Tue 1600 EST Tue 1000 PST to Tue 1300 PST
Is this still probable? We should identify specific "full committee" decisions ahead of time, to make sure we have a quorum hanging around. (candidates see below)
I have two problems here, one of them selfishly motivated and the other decidedly not:
1. Selfish reason: That's smack in the middle of my workday, and my $DAYJOB cuts me *ZERO* time for Fedora. That's not to say I don't sneak some in here and there, but Fedora is the first thing that gets eliminated when I have deadlines or priorities to meet. I would REALLY like to be involved in these meetings, but I simply can't commit to it during these hours. :-( Nevertheless, there's always IRC logging and catchup that would make up for it somewhat, and waiting for me to get home automatically pushes our European contingent into very late hours, so I understand.
Is there no one interested in a weekend meeting? (I know, we all need lives.)
2. Unselfish reason: This project has really begun to do a LOT of work on IRC and not on the mailing list. The number of people on IRC is *FAR* fewer than the number of people on the mailing list, and I worry that our opportunities for public collaboration are being stifled in that regard. We have a lot of lurkers who might be drawn in by the right conversation or idea. The 3-hour meeting idea might contribute to this, but I'm not sure. If I'm retreading old ground or reversing myself, mea culpa, I am legion.
- Elect new chair/project leader [MEETING DECISION] 1.1 Decide if chair is 12 mon. or 6 mon. position? [MEETING DECISION] -- on-list discussion?
- -> This would be a candidate
Meetings on #fedora-docs v. #fedora-meeting [MEETING DECISION]
Confirm FDP schedule for F7 [LIST DISCUSSION],[MEETING DECISION]
We should consider L10N workload here, maybe only do a final version of guides on L10N-level.
The benefit of pushing it a couple times is that small changes (which inevitably happen from the last test => final, regardless of whining to the contrary!) can make it into the guides. We've made a lot of progress toward minimizing string changes so I would hope the extra work would be minimal, unlike the release notes situation we landed in last release, which was unintentional and shouldn't recur with our current procedures.
Pushing twice also means that if a translation team puts off one project in favor of the other (relnotes, guides), they have that opportunity without having to accomplish everything at one time on a short deadline. (Yikes!)
On Fri, 2007-03-02 at 15:36 -0500, Paul W. Frields wrote:
Is there no one interested in a weekend meeting? (I know, we all need lives.)
I would be OK with an early Saturday (such as 1600 UTC), perhaps. Unfortunately, I think that is in the middle of John's workday.
I swear, there *is* a day _and_ a time we can all meet. It need only be 30 minutes, especially if we ...
- Unselfish reason: This project has really begun to do a LOT of work
on IRC and not on the mailing list. The number of people on IRC is *FAR* fewer than the number of people on the mailing list, and I worry that our opportunities for public collaboration are being stifled in that regard. We have a lot of lurkers who might be drawn in by the right conversation or idea. The 3-hour meeting idea might contribute to this, but I'm not sure. If I'm retreading old ground or reversing myself, mea culpa, I am legion.
more-list-less-meeting++
We need to take the action of following Bob's advise this time around and do more work on list. Being able to collaborate asynchronously is key to our success.
So, let's continue this search for a 30 minute window we can all do. How early can we go? How late? What days?
- Karsten
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karsten Wade schreef:
On Fri, 2007-03-02 at 15:36 -0500, Paul W. Frields wrote:
Is there no one interested in a weekend meeting? (I know, we all need lives.)
I would be OK with an early Saturday (such as 1600 UTC), perhaps. Unfortunately, I think that is in the middle of John's workday.
Likewise, I'm OK with weekend meetings, if it's not gonna take too long. 1600 UTC is fine for me, but yeah John might have a work-problem.
I swear, there *is* a day _and_ a time we can all meet. It need only be 30 minutes, especially if we ...
- Unselfish reason: This project has really begun to do a LOT of work
on IRC and not on the mailing list. The number of people on IRC is *FAR* fewer than the number of people on the mailing list, and I worry that our opportunities for public collaboration are being stifled in that regard. We have a lot of lurkers who might be drawn in by the right conversation or idea. The 3-hour meeting idea might contribute to this, but I'm not sure. If I'm retreading old ground or reversing myself, mea culpa, I am legion.
more-list-less-meeting++
We need to take the action of following Bob's advise this time around and do more work on list. Being able to collaborate asynchronously is key to our success.
Total agreement
So, let's continue this search for a 30 minute window we can all do. How early can we go? How late? What days?
Earliest for me is 0500 UTC, latest 22OO UTC. A slight preference for weekends (lost of possible hours), weekdays at O5OO, or starting from 17OO UTC.
- Karsten
Bart
- -- Bart couf@fedoraproject.org couf@skynet.be key fingerprint: 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93
On Sat, 2007-03-03 at 19:13 +0100, Bart Couvreur wrote:
So, let's continue this search for a 30 minute window we can all do. How early can we go? How late? What days?
Earliest for me is 0500 UTC, latest 22OO UTC. A slight preference for weekends (lost of possible hours), weekdays at O5OO, or starting from 17OO UTC.
/me has deja vu :-)
Weekdays, 2200 - 0400 UTC I can usually do. (Sorry, long workday, little time windows.) Weekends, just about any time, say: 1300 - 0300 UTC.
On 3/3/07, Karsten Wade kwade@redhat.com wrote:
I would be OK with an early Saturday (such as 1600 UTC), perhaps. Unfortunately, I think that is in the middle of John's workday.
I swear, there *is* a day _and_ a time we can all meet. It need only be 30 minutes, especially if we ...
1600 UTC = 1900 UTC+3 = 7 PM local time for me
on Saturday is fine. :-)
John Babich Volunteer, Fedora Docs Project
On Tue, 2007-02-27 at 22:28 -0800, Karsten Wade wrote:
We have a few items that have backed up to deal with; please help me make sure that enough of these *decision* items make it on the agenda. Bringing them up on-list means we can work out the details *before the meeting*. This is a new paradigm for FDSCo, but one we have all spoken of following (iirc). ;-)
Meeting time -- [LIST DECISION]
Elect new chair/project leader [MEETING DECISION] 1.1 Decide if chair is 12 mon. or 6 mon. position? [MEETING DECISION] -- on-list discussion?
Meetings on #fedora-docs v. #fedora-meeting [MEETING DECISION]
Confirm FDP schedule for F7 [LIST DISCUSSION],[MEETING DECISION]
AOB
4. Decide to keep or retire fedora-dsco-list [MEETING DECISION]
-- fedora-docs-list mailing list fedora-docs-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list