I (RalfBecker) propose the following guidelines / rules to be listed on http://www.egroupware.org/commercialsupport

1. The listing is FREE for people and their organisations who make substantial contributions to eGroupWare:

• developers actively maintaining an application
• other officials of the eGW project: translation coordinator, webmaster, elected admins, ...
• people contributing NEW (at least 70% complete) translations of eGroupWare or the user manual
• the contribution has to be more then one full week of work in the last 12 month
• the decision to be include in that category is done by the project admins (taking into account these guidelines) and can be disputed like all admin decisions (see the constitution)

2. People / Organisations who supported eGroupWare financially in the last 12 month with at least 500 Euro unconditional or sponsor some feature of their own liking for at least 2000 Euro

3. Order of the listing:

• first listed are the project members named in 1) and ordered by the amount of their contribution
• the "amount of the contribution" is decided by the project admins and can be disputed like all admin decisions (see the constitution)
• in case of similar contributions, the date of the contribution (how long ago) and the order of applying to be listed is taken into account
• organisations employing / representing more then one "project member", are ordered by the sum of the contributions (if they appear only once)
• non-project members (see 2.) are ordered by the financial amount of their contribution (sponsored features counting 25% of unconditional sponsoring) and after that by the date of their application

4. all contributions only count for 12 month: this is true for project members (1.) and sponsors (2.)

5. in the future the listing of non project members might be by country

6. founds raised by unconditional sponsoring in 2. should be used for:

• work on the eGW API, which is not likely to be sponsored (as it is mostly invisible to end-users)
• fixing bugs (not resulted from the latest development!)
• closing long term deficits of eGroupWare

These raised money should be reported (along the money from donations) every quarter to the project public and developers can apply for the money with a planed improvement in the above areas. If more applications exist then founds, the regular eGroupWare decision process (admins and/or votes) will decide how to use them.

Notes, argumentation, others stuff:
- I dont call people named in 1) explicitly project members as we have quite a lot old - not longer active - project members listed on sf.net
- I think the sf.net project members should be fixed soon and all people named in 1) should be listed in one place (including their area of contribution, email and date of last contribution). Only people who need cvs/svn rights should be given them.
- 1. sets a, I think very necessary, minimum contribution, so just a patch or completing an existing translation, is NOT enough. My idea is, it should be at least one full week of work, maybe more.

I propose to have some discussion on these guidelines on the core-list and then putting them (or something like them) into affect by a vote.

---

feel free to add your comments -- RalfBecker

I (RalfBecker) propose the following guidelines / rules to be listed on http://www.egroupware.org/commercialsupport

1. The listing is FREE for people and their organisations who make substantial contributions to eGroupWare:

• developers actively maintaining an application
• other officials of the eGW project: translation coordinator, webmaster, elected admins, ...
• people contributing NEW (at least 70% complete) translations of eGroupWare or the user manual
• the contribution has to be more then one full week of work in the last 12 month
• the decision to be include in that category is done by the project admins (taking into account these guidelines) and can be disputed like all admin decisions (see the constitution)

2. People / Organisations who supported eGroupWare financially in the last 12 month with at least 500 Euro unconditional or sponsor some feature of their own liking for at least 2000 Euro

3. Order of the listing:

• first listed are the project members named in 1) and ordered by the amount of their contribution
• the "amount of the contribution" is decided by the project admins and can be disputed like all admin decisions (see the constitution)
• in case of similar contributions, the date of the contribution (how long ago) and the order of applying to be listed is taken into account
• organisations employing / representing more then one "project member", are ordered by the sum of the contributions (if they appear only once)
• non-project members (see 2.) are ordered by the financial amount of their contribution (sponsored features counting 25% of unconditional sponsoring) and after that by the date of their application

4. all contributions only count for 12 month: this is true for project members (1.) and sponsors (2.)

5. in the future the listing of non project members might be by country

6. founds raised by unconditional sponsoring in 2. should be used for:

• work on the eGW API, which is not likely to be sponsored (as it is mostly invisible to end-users)
• fixing bugs (not resulted from the latest development!)
• closing long term deficits of eGroupWare

These raised money should be reported (along the money from donations) every quarter to the project public and developers can apply for the money with a planed improvement in the above areas. If more applications exist then founds, the regular eGroupWare decision process (admins and/or votes) will decide how to use them.

Notes, argumentation, others stuff:
- I dont call people named in 1) explicitly project members as we have quite a lot old - not longer active - project members listed on sf.net
- I think the sf.net project members should be fixed soon and all people named in 1) should be listed in one place (including their area of contribution, email and date of last contribution). Only people who need cvs/svn rights should be given them.
- 1. sets a, I think very necessary, minimum contribution, so just a patch or completing an existing translation, is NOT enough. My idea is, it should be at least one full week of work, maybe more.

I propose to have some discussion on these guidelines on the core-list and then putting them (or something like them) into affect by a vote.

---

feel free to add your comments -- RalfBecker