6:25 a.m.
Most if not all of the subprojects in Fedora follow the guidelines
established by the Board for defining projects, found here:
http://fedoraproject.org/wiki/DefiningProjects
I'm not a big fan of organization just for organization's sake, if it
stops people from being able to get things done.
But steering committees in subprojects are *good* for a number of
reasons, including identifying tasks, getting assignments made, and
tracking progress. A steering committee serves as a central
communication point between all the members of a subproject, other
subprojects, and the Fedora Project Board. It also provides a unified
voice and opportunities for solid decision making, empowering community
leaders the contributors themselves identify and elect.
I encourage the L10N (Translation) Project to start talking about an
L10N Steering Committee. I also encourage interested community members
to step up and serve as committee members to better organize and
communicate about all the great work that's being done in L10N.
Thanks to all contributors here for your hard work and incredible
progress in making Fedora available to users worldwide!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
10:37 p.m.
Paul W. Frields wrote:
Most if not all of the subprojects in Fedora follow the guidelines
established by the Board for defining projects, found here:
http://fedoraproject.org/wiki/DefiningProjects
I see that we are shaping fairly
good project, aren't we?
I'm not a big fan of organization just for organization's sake, if it
stops people from being able to get things done.
But steering committees in subprojects are *good* for a number of
reasons, including identifying tasks, getting assignments made, and
tracking progress. A steering committee serves as a central
communication point between all the members of a subproject, other
subprojects, and the Fedora Project Board. It also provides a unified
voice and opportunities for solid decision making, empowering community
leaders the contributors themselves identify and elect.
I encourage the L10N (Translation) Project to start talking about an
L10N Steering Committee. I also encourage interested community members
to step up and serve as committee members to better organize and
communicate about all the great work that's being done in L10N.
Certainly we
must be in the stage that should have an committee.
So we may need some election/selection scheme.
I am learning the way of sister docs team.
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee
noriko
Thanks to all contributors here for your hard work and incredible
progress in making Fedora available to users worldwide!
------------------------------------------------------------------------
--
Fedora-trans-list mailing list
Fedora-trans-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-trans-list
2:36 p.m.
On Thu, Feb 28, 2008 at 6:37 AM, Noriko Mizumoto <noriko(a)redhat.com> wrote:
Paul W. Frields wrote:
> Most if not all of the subprojects in Fedora follow the guidelines
> established by the Board for defining projects, found here:
>
> http://fedoraproject.org/wiki/DefiningProjects
I see that we are shaping fairly good project, aren't we?
We certainly are! And it feels darn good!
> I'm not a big fan of organization just for
organization's sake, if it
> stops people from being able to get things done.
>
> But steering committees in subprojects are *good* for a number of
> reasons, including identifying tasks, getting assignments made, and
> tracking progress. A steering committee serves as a central
> communication point between all the members of a subproject, other
> subprojects, and the Fedora Project Board. It also provides a unified
> voice and opportunities for solid decision making, empowering community
> leaders the contributors themselves identify and elect.
And if a future FLSCo is half as successful as the Docs Steering
Committe, in achieving the above, I'll be very happy.
> I encourage the L10N (Translation) Project to start talking
about an
> L10N Steering Committee. I also encourage interested community members
> to step up and serve as committee members to better organize and
> communicate about all the great work that's being done in L10N.
Certainly we must be in the stage that should have an committee.
So we may need some election/selection scheme.
I am learning the way of sister docs team.
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee
+1. We've got a good example to follow.
I agree with Bart that it's a good time to get a SCo going and that
having a team of people responsible for the whole project could help
increase the communication and Getting Things Done.
What does it mean for a person to have a seat in SCo? It mens you're
in a position to better drive the FLP to achieve its goals and craft a
long-term strategy. To advocate the Project's needs and positions to
other projects and the Board. To be accountable for aligning the
project's actions to the overall Fedora Project spirit. And to have
one more leadership position in your CV.
If there are no objections, let's get the ball rolling then.
-d
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
1:55 p.m.
Op woensdag 27-02-2008 om 12:25 uur [tijdzone +0000], schreef Paul W.
Frields:
Most if not all of the subprojects in Fedora follow the guidelines
established by the Board for defining projects, found here:
http://fedoraproject.org/wiki/DefiningProjects
Right, and we have been trying that as much as possible (imo).
I'm not a big fan of organization just for organization's
sake, if it
stops people from being able to get things done.
But steering committees in subprojects are *good* for a number of
reasons, including identifying tasks, getting assignments made, and
tracking progress. A steering committee serves as a central
communication point between all the members of a subproject, other
subprojects, and the Fedora Project Board. It also provides a unified
voice and opportunities for solid decision making, empowering community
leaders the contributors themselves identify and elect.
Agreed
I encourage the L10N (Translation) Project to start talking about an
L10N Steering Committee. I also encourage interested community members
to step up and serve as committee members to better organize and
communicate about all the great work that's being done in L10N.
I think we're in the stage that this can really get some traction. We've
been trying to do some sort of regular meeting so that wouldn't be all
that different.
The only drawback I have here is that the L10N project is pretty much
divided into dozens of small parts (the teams), and that the SCo would
mostly be handling infrastructural things. But then again this could
that the different teams start to communicate more in the project, which
is always good. (just my $0.02)
Thanks to all contributors here for your hard work and incredible
progress in making Fedora available to users worldwide!
+1000
But anyway: if we want to form an SCo, let's just do it. People
interested: raise your hand!!
Bart
--
Bart <couf(a)fedoraproject.org> <couf(a)skynet.be>
key fingerprint: 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93
2:47 p.m.
On Fri, 2008-02-29 at 20:55 +0100, Bart Couvreur wrote:
The only drawback I have here is that the L10N project is pretty
much
divided into dozens of small parts (the teams), and that the SCo would
mostly be handling infrastructural things. But then again this could
that the different teams start to communicate more in the project, which
is always good. (just my $0.02)
Actually, this is not too different from any other subproject -- for
instance, there are small pockets of individuals or groups in Docs
working on, say, the Get Involved Guide, or the Desktop User Guide. The
Steering Committee ties everything together and makes sure everyone is
working toward overall goals in a consistent and logical fashion.
> Thanks to all contributors here for your hard work and
incredible
> progress in making Fedora available to users worldwide!
+1000
+1000^1000 ;-)
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
6:27 a.m.
Paul W. Frields wrote:
On Fri, 2008-02-29 at 20:55 +0100, Bart Couvreur wrote:
> The only drawback I have here is that the L10N project is pretty much
> divided into dozens of small parts (the teams), and that the SCo would
> mostly be handling infrastructural things. But then again this could
> that the different teams start to communicate more in the project, which
> is always good. (just my $0.02)
Actually, this is not too different from any other subproject -- for
instance, there are small pockets of individuals or groups in Docs
working on, say, the Get Involved Guide, or the Desktop User Guide. The
Steering Committee ties everything together and makes sure everyone is
working toward overall goals in a consistent and logical fashion.
Can we perhaps have this as a discussion item for the meeting tomorrow (in case we are
having one)?
:-)
cheers
Runa
--
blog: http://runab.livejournal.com
irc:
runa on Red Hat
mishti or runa_b on Freenode, Gimpnet, Mozilla, LinuxChix
5:54 p.m.
Runa Bhattacharjee wrote:
Paul W. Frields wrote:
> On Fri, 2008-02-29 at 20:55 +0100, Bart Couvreur wrote:
>> The only drawback I have here is that the L10N project is pretty much
>> divided into dozens of small parts (the teams), and that the SCo would
>> mostly be handling infrastructural things. But then again this could
>> that the different teams start to communicate more in the project, which
>> is always good. (just my $0.02)
>
> Actually, this is not too different from any other subproject -- for
> instance, there are small pockets of individuals or groups in Docs
> working on, say, the Get Involved Guide, or the Desktop User Guide. The
> Steering Committee ties everything together and makes sure everyone is
> working toward overall goals in a consistent and logical fashion.
Can we perhaps have this as a discussion item for the meeting tomorrow
(in case we are having one)?
+1 meeting.
I will be there at usual time.
:-)
cheers
Runa
8:59 a.m.
On Tue, 2008-03-04 at 09:54 +1000, Noriko Mizumoto wrote:
Runa Bhattacharjee wrote:
> Paul W. Frields wrote:
>> On Fri, 2008-02-29 at 20:55 +0100, Bart Couvreur wrote:
>>> The only drawback I have here is that the L10N project is pretty much
>>> divided into dozens of small parts (the teams), and that the SCo would
>>> mostly be handling infrastructural things. But then again this could
>>> that the different teams start to communicate more in the project, which
>>> is always good. (just my $0.02)
>>
>> Actually, this is not too different from any other subproject -- for
>> instance, there are small pockets of individuals or groups in Docs
>> working on, say, the Get Involved Guide, or the Desktop User Guide. The
>> Steering Committee ties everything together and makes sure everyone is
>> working toward overall goals in a consistent and logical fashion.
>
> Can we perhaps have this as a discussion item for the meeting tomorrow
> (in case we are having one)?
+1 meeting.
I will be there at usual time.
I'll be logging because of the Fedora Board meeting occurring during
that time.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
5894
days inactive
5900
days old
7 comments
5 participants
participants (5)
-
Bart Couvreur -
Dimitris Glezos -
Noriko Mizumoto -
Paul W. Frields -
Runa Bhattacharjee