[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tdf-discuss] [SC] How to define "Membership" within TDF?
- Subject: Re: [tdf-discuss] [SC] How to define "Membership" within TDF?
- From: Marc Paré <firstname.lastname@example.org>
- Date: Wed, 20 Oct 2010 14:48:44 -0400
- To: email@example.com
Le 2010-10-20 14:10, Drew Jensen a écrit :
On Wed, 2010-10-20 at 13:16 -0400, Drew Jensen wrote:
On Wed, 2010-10-20 at 16:57 +0200, Gianluca Turconi wrote:
Il 20/10/2010 16.36, Mike Dupont ha scritto:
1. what will it cost if you have to rewrite the authors code and all
2. what if you just remove the code
Contributions are not only code. There are a lot of intangibles.
Marketing, lobbying and advocating work are some examples.
Please let us not expand what defines contribution.
Lobbying should not IMO garner admittance.
Advocating should not.
Working on this project(s) should be the only work that counts.
Actually, I would need to amend that last sentence:
Work on the main project or it's accepted sub-projects. For instance
there may be extensions - either directly as Add-ons to the LibreOffice
package, possibly even extensions to desktop packages with features
specifically created to support LibreOffice and the ODF.
So you are proposing that a contributor is someone who has contributed either hard code or plug-in code etc. to the project. The contributions MUST be associated some way to code or ODF code convention.
Presumably then, no one other than a dev or dev-like contributor could become a TDF member.
So, let's take me as an example, I am part of the Canadian Marketing Team which is starting from zero resources and contacts. If I make arrangements for Marcon's in our 12 regions of my country; make arrangements for large city LibO representatives; make arrangements for a national conference with conference facilities for our newly expanded Canadian Marketing Team and then try to find corporate sponsorship for both Canadian Marketing Team and LibO advertising and installfests etc. This according to your criteria would not suffice to award me membership into the TDF.
Would this not, in some way, be considered as a contributor to the TDF?
If not, then how would I be able to make my voice heard to the TDF membership when there was an issue that I would consider important to me or LibO?
If yes, then, what measure could we use, to consider such a person as described, to award membership status. How much would a person have to contribute (I am still taking my example as Canadian Marketing Team member) to be awarded membership status?
For that matter, how about the people providing on the localization projects?
IMHO, I believe you are skipping one major step by establishing membership criteria to the TDF. The hierarchy must be established first and then define membership. The hierarchy is pretty well evident as I has posted my suggestion re: this before and out of coincidence James Walker, in a different way, suggested, on this thread, the same organization of the TDF project as I had. I am sure that we will not be the only ones to define it this way as it is the natural way to organize the groups. (I quote James Walker here for the sake of convenience, below)
I decided I would try to convey my thoughts on this now
First I had a couple of questions
How many member do we envision being on the SC?
How many projects does the SC envision having under the TDF.
Right now I see the need for LibreOffice, and I really do see a need for a
couple other projects. I would love an android app that opens LibreOffice
files. maybe even a BlackBerry app and some other smartphone apps.
If this is the case, I see the SC being made up of those that are currently
on the SC at the present and then Representatives of the Projects that are
under TDF. I feel that the projects should vote on those member that will
become members of the SC. How many from each project should be related to
the size of the project.
The problem as I see it is how do you define the amount of contribution each
person gives, cause in my opinion even the users are contributors to the
project, without the users there would be no need for the project. So does
simple registration make you a member of the project, or do you need to join
one of the group that we will have?
As for TDF, I would not be opposed to the members of TDF deciding who can
join, say you want to join TDF, you send in some kind of resume, and the
current members vote you in, or out, if they feel that needs to be the case,
or they can ask for clarifing information if that is needed. Would I
be opposed to some kind of membership fee to join TDF, no, I have been a
member of several organizations that require a membership fee. TDF needs
some kind of budget and we all enjoy using the software. I see no issue with
later as the project progresses and we get more member of TDF, I see
elections to oppoint members of the SC from the larger TDF membership. Now
keep in mind being a member of one of the projects does not mean you are a
member of TDF. But you would get to vote for the representative to the SC
for your project.
these are just a few of my thoughts, please feel free to comment.
E-mail to firstname.lastname@example.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be deleted
|Re: [tdf-discuss] [SC] How to define "Membership" within TDF?||Drew Jensen <email@example.com>|
- Prev by Date: Re: [tdf-discuss] [SC] How to define "Membership" within TDF?
- Next by Date: Re: [tdf-discuss] Send Messages via Gmane?
- Previous by thread: Re: [tdf-discuss] [SC] How to define "Membership" within TDF?
- Next by thread: Re: [tdf-discuss] [SC] How to define "Membership" within TDF?