Menu
▾
▴
envolution-devel
|
From: Stefan K. <Ste...@ga...> - 2003-06-06 07:02:23
|
@capretta: First of all I am very happy that you're joining our team as documentation = manager. I agree with all of you write here. Your ideas to structure the new = Documentation team are exactly the same I have had discuss with others = (this mailing-list, TiMax, sjah, naphta, gatonero, etc.). Possible you can collaborate with naphta (I know you talk to him) to find = basic rules and guidelines for all (national and international) writers. Naphta answered me today, that he will be happy to do the job of Locale = Documentation Manager. So we only need to find Locals for french and english now ;) WindMeUp |
|
From: gagl <ca...@fr...> - 2003-06-10 10:39:54
|
hi to evryone by capretta, that's the first proposal on eNDP (eNvolution Documentation Project) .....be eNvolved..... =20 eNvolution Documentation Project (eNDP) This is the Team at this moment: a.. General Documentation Manager: capretta (who else? Naphta, = GatoNero? Zoom?) b.. Local Documentation Manager or Localization Director=20 - Italy: capretta - Germany: naphta, gatonero - France: philipc - English: ??? - Other languages: ????? c.. Staff writers: ?????????? d.. Translators: ???????? We need first of all enghish-speaking overviewers, who only have to = check my bad english grammar... This position controls the texts and = articles before publishing for grammatical and language correction ( I = have to do some english on-line courses.....) This is only a proposal on how to organize and manage the documentation. = Everyone feels free to contribute, discuss and add suggestions. It's a = starting point in the hope others add to the team and fill vacant = positions, so we can start with the project.=20 *************************************************************************= ** eNPD Vision and Proposition (eNPD Roadmap) *************************************************************************= ** eNDP Tasks:=20 taken from the ENISS eNvo Organizational Structure Document of the = Founders a.. General Documentation Manager: This elected position is responsible to the Project Manager and the = Founders. This position will require excellent communication skills and = the ability to write documentation for both technical and non-technical = users. The duties of this officer are, but not limited to: 1)Document creation. 2)FAQ's. 3)Recruits and supervises content writers. 4)Manages all published stories on the Envolution website. 5)How-To and Tutorial creation and publication. This position requires daily interaction with the community and the = Project Manager. This officer will also communicate with other officers = to gain the required information to produce top quality documents for = public consumption. Works directly with the Localization director to = secure translations for the language specific support sites. This person = should speak excellent English and have superior grammatical and = spelling skills. a.. Localization Manager:=20 This position is responsible for researching and implementing new = languages and localizations for the entire project. This position = answers directly to the Project Manager and the Founders (Specifically = TiMax). This officer also tends to multilingual and translation duties = for all project documentation. The officer must be prepared to interact = daily with the community and the Documentation Manager. Duties are, but = not limited to: 1)Language translations. 2)Document translations. 3)Coordinating between various international support sites and the other = officers and Founders of the project. 4)Recruit non-English speaking people to interact with and/or join the = project. 5)Help with coordinating international web sites with the main = Envolution web site. This position requires daily interaction with the community and the = Project Manager as well as language specific support sites. This officer = must be able to speak English and at least one other language. This = officer should also expect to seek out other non-English speaking people = to help with localization issues and support. a.. Translators: every localization has its team of translators from = or into english, that has to be the basic language for the = documentation. Translators fixed positions or occasional positions, = covered for single projects. Technical Documents:=20 Technical briefs are produced on a regular basis and are an invaluable = source of information for you as a supporter of your localized = Envolution Community. The subject matter is varied and covers all = aspects of Envolution architecture, support, customization, features, = announcements, bugs and comments. Documentation Tools and Formats All the official documentation can be produced using CVS (TiMax will = create a directory for it, tell us where....) in HTML format. I = personnaly use OpenOffice.org for it. Contributions and other team documentation could be produced using = collaborative tools like Wiki. Pubblishing will be in PDF or HTML format in zip files for the Download = Section and in HTML for on line versions (with Subjects Module, Content = Express, etc.). Documentation License In our experience on eNvolution.it we learned to not use the Free = Documentation License http://www.gnu.org/copyleft/fdl.html because we = had some problems with irregular appropriation changing few words in the = text. On envolution.it we use the Open Document License = http://www.opencontent.org/openpub/ where evrybody can use or distribute = not for commercial use the document but has to leave original credits = and can't modify without permission of the authors. All the = documentation IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY.=20 Roadmap a.. On line manuals: of the Admin Panel localized in each = /modules/..../lang/ directory as manual.html: some of these has to be = written or updated. I will check which one are missing.... a.. Official Documentation:=20 Based on Zoom's Official eNvolution Manual, but with different = structure and chapters updated or rewritten: for version 1.2.5 or 1.3 - Part 1: Presentation of eNvolution (I have it almost ready in = italian language, to be updated with the newest functions taken from = "Who is envolution") with thumbnails of some representative eNvo sites - Part 2: Installation guide & basic settings : ( I have it also = ready: local & remote installation for Win & Linux, upload to remote = server, backup & dump, manual & script installation, basic configuration = -> Settings in Admin Panel) - Part 3: Building your eNvo site: Layout : Naphta rewrote Sjah's = manual.... - Part 4: Advanced settings: we have to update Zoom's manual for = module settings... some parts could be taken from other existing = contributions. b.. Technical Documentation : most of it is still avaible on most = sites: eNvo API, eNvRender, etc. c.. Localized Documentation : it's documentation produced from the = specific countries to soddisfy internal needs: could be translated for = similar needs of other countries d.. How to...and Tutorials: produced and translated from and for the = whole Network, like modules guides, .... e.. Contributes: sent by eNvo supporters and users: to be translated = if worthy. The first two points has surely priority in the tasks roadmap. On line = manuals need CVS production, for the official manual I propose to use = also CVS. Other documentation can use both Wiki or HTML sent to = translators. ciao, capretta |
|
From: Martin L. <ma...@ar...> - 2003-06-10 15:38:55
|
Hi Capretta
I'm happy to do English grammar/spelling check. Just let me know how you =
want me to do this.
Regards
Em
----- Original Message -----=20
From: gagl=20
To: env...@li...=20
Sent: Tuesday, June 10, 2003 11:11 AM
Subject: [Envolution-devel] eNvolution Documentation Project
hi to evryone by capretta,
that's the first proposal on eNDP (eNvolution Documentation Project)
.....be eNvolved.....
=20
eNvolution Documentation Project (eNDP)
This is the Team at this moment:
a.. General Documentation Manager: capretta (who else? Naphta, =
GatoNero? Zoom?)
b.. Local Documentation Manager or Localization Director=20
- Italy: capretta
- Germany: naphta, gatonero
- France: philipc
- English: ???
- Other languages: ?????
c.. Staff writers: ??????????
d.. Translators: ????????
We need first of all enghish-speaking overviewers, who only have to =
check my bad english grammar... This position controls the texts and =
articles before publishing for grammatical and language correction ( I =
have to do some english on-line courses.....)
This is only a proposal on how to organize and manage the =
documentation. Everyone feels free to contribute, discuss and add =
suggestions. It's a starting point in the hope others add to the team =
and fill vacant positions, so we can start with the project.=20
=
*************************************************************************=
**
eNPD Vision and Proposition (eNPD Roadmap)
=
*************************************************************************=
**
eNDP Tasks:=20
taken from the ENISS eNvo Organizational Structure Document of the =
Founders
a.. General Documentation Manager:
This elected position is responsible to the Project Manager and the =
Founders. This position will require excellent communication skills and =
the ability to write documentation for both technical and non-technical =
users. The duties of this officer are, but not limited to:
1)Document creation.
2)FAQ's.
3)Recruits and supervises content writers.
4)Manages all published stories on the Envolution website.
5)How-To and Tutorial creation and publication.
This position requires daily interaction with the community and the =
Project Manager. This officer will also communicate with other officers =
to gain the required information to produce top quality documents for =
public consumption. Works directly with the Localization director to =
secure translations for the language specific support sites. This person =
should speak excellent English and have superior grammatical and =
spelling skills.
a.. Localization Manager:=20
This position is responsible for researching and implementing new =
languages and localizations for the entire project. This position =
answers directly to the Project Manager and the Founders (Specifically =
TiMax). This officer also tends to multilingual and translation duties =
for all project documentation. The officer must be prepared to interact =
daily with the community and the Documentation Manager. Duties are, but =
not limited to:
1)Language translations.
2)Document translations.
3)Coordinating between various international support sites and the =
other officers and Founders of the project.
4)Recruit non-English speaking people to interact with and/or join the =
project.
5)Help with coordinating international web sites with the main =
Envolution web site.
This position requires daily interaction with the community and the =
Project Manager as well as language specific support sites. This officer =
must be able to speak English and at least one other language. This =
officer should also expect to seek out other non-English speaking people =
to help with localization issues and support.
a.. Translators: every localization has its team of translators from =
or into english, that has to be the basic language for the =
documentation. Translators fixed positions or occasional positions, =
covered for single projects.
Technical Documents:=20
Technical briefs are produced on a regular basis and are an invaluable =
source of information for you as a supporter of your localized =
Envolution Community. The subject matter is varied and covers all =
aspects of Envolution architecture, support, customization, features, =
announcements, bugs and comments.
Documentation Tools and Formats
All the official documentation can be produced using CVS (TiMax will =
create a directory for it, tell us where....) in HTML format. I =
personnaly use OpenOffice.org for it.
Contributions and other team documentation could be produced using =
collaborative tools like Wiki.
Pubblishing will be in PDF or HTML format in zip files for the =
Download Section and in HTML for on line versions (with Subjects Module, =
Content Express, etc.).
Documentation License
In our experience on eNvolution.it we learned to not use the Free =
Documentation License http://www.gnu.org/copyleft/fdl.html because we =
had some problems with irregular appropriation changing few words in the =
text. On envolution.it we use the Open Document License =
http://www.opencontent.org/openpub/ where evrybody can use or distribute =
not for commercial use the document but has to leave original credits =
and can't modify without permission of the authors. All the =
documentation IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY.=20
Roadmap
a.. On line manuals: of the Admin Panel localized in each =
/modules/..../lang/ directory as manual.html: some of these has to be =
written or updated. I will check which one are missing....
a.. Official Documentation:=20
Based on Zoom's Official eNvolution Manual, but with different =
structure and chapters updated or rewritten: for version 1.2.5 or 1.3
- Part 1: Presentation of eNvolution (I have it almost ready in =
italian language, to be updated with the newest functions taken from =
"Who is envolution") with thumbnails of some representative eNvo sites
- Part 2: Installation guide & basic settings : ( I have it also =
ready: local & remote installation for Win & Linux, upload to remote =
server, backup & dump, manual & script installation, basic configuration =
-> Settings in Admin Panel)
- Part 3: Building your eNvo site: Layout : Naphta rewrote Sjah's =
manual....
- Part 4: Advanced settings: we have to update Zoom's manual for =
module settings... some parts could be taken from other existing =
contributions.
b.. Technical Documentation : most of it is still avaible on most =
sites: eNvo API, eNvRender, etc.
c.. Localized Documentation : it's documentation produced from the =
specific countries to soddisfy internal needs: could be translated for =
similar needs of other countries
d.. How to...and Tutorials: produced and translated from and for the =
whole Network, like modules guides, ....
e.. Contributes: sent by eNvo supporters and users: to be translated =
if worthy.
The first two points has surely priority in the tasks roadmap. On line =
manuals need CVS production, for the official manual I propose to use =
also CVS. Other documentation can use both Wiki or HTML sent to =
translators.
ciao,
capretta
|
|
From: Denver P. Jr. <den...@co...> - 2003-06-10 19:27:31
|
I hammered out 20+ english grammer mistakes in the current version if they are still there in sourceforge cvs. I've been away trying to get osCommerce working with a huge mod to no avail. I'll take a break from that and return to my duties in the team. Can someone doing code fix the user.php so that confirmation code is showed on the screen after user/email prompt and adding form results hidden user name to the next screen so all they have to do is enter the confirmation code? I believe once the code has been entered they should be taken to the user login page. The current form is just way to confusing for a user and very tacky to have to hit the back browser just to enter in the confirm code. -----Original Message----- From: env...@li... [mailto:env...@li...] On Behalf Of Martin Luff Sent: Tuesday, June 10, 2003 10:41 AM To: env...@li... Subject: Re: [Envolution-devel] eNvolution Documentation Project Hi Capretta I'm happy to do English grammar/spelling check. Just let me know how you want me to do this. Regards Em ----- Original Message ----- From: gagl <mailto:ca...@fr...> To: env...@li... Sent: Tuesday, June 10, 2003 11:11 AM Subject: [Envolution-devel] eNvolution Documentation Project hi to evryone by capretta, that's the first proposal on eNDP (eNvolution Documentation Project) .....be eNvolved..... eNvolution Documentation Project (eNDP) This is the Team at this moment: * General Documentation Manager: capretta (who else? Naphta, GatoNero? Zoom?) * Local Documentation Manager or Localization Director - Italy: capretta - Germany: naphta, gatonero - France: philipc - English: ??? - Other languages: ????? * Staff writers: ?????????? * Translators: ???????? We need first of all enghish-speaking overviewers, who only have to check my bad english grammar... This position controls the texts and articles before publishing for grammatical and language correction ( I have to do some english on-line courses.....) This is only a proposal on how to organize and manage the documentation. Everyone feels free to contribute, discuss and add suggestions. It's a starting point in the hope others add to the team and fill vacant positions, so we can start with the project. ************************************************************************ *** eNPD Vision and Proposition (eNPD Roadmap) ************************************************************************ *** eNDP Tasks: taken from the ENISS eNvo Organizational Structure Document of the Founders * General Documentation Manager: This elected position is responsible to the Project Manager and the Founders. This position will require excellent communication skills and the ability to write documentation for both technical and non-technical users. The duties of this officer are, but not limited to: 1)Document creation. 2)FAQ's. 3)Recruits and supervises content writers. 4)Manages all published stories on the Envolution website. 5)How-To and Tutorial creation and publication. This position requires daily interaction with the community and the Project Manager. This officer will also communicate with other officers to gain the required information to produce top quality documents for public consumption. Works directly with the Localization director to secure translations for the language specific support sites. This person should speak excellent English and have superior grammatical and spelling skills. * Localization Manager: This position is responsible for researching and implementing new languages and localizations for the entire project. This position answers directly to the Project Manager and the Founders (Specifically TiMax). This officer also tends to multilingual and translation duties for all project documentation. The officer must be prepared to interact daily with the community and the Documentation Manager. Duties are, but not limited to: 1)Language translations. 2)Document translations. 3)Coordinating between various international support sites and the other officers and Founders of the project. 4)Recruit non-English speaking people to interact with and/or join the project. 5)Help with coordinating international web sites with the main Envolution web site. This position requires daily interaction with the community and the Project Manager as well as language specific support sites. This officer must be able to speak English and at least one other language. This officer should also expect to seek out other non-English speaking people to help with localization issues and support. * Translators: every localization has its team of translators from or into english, that has to be the basic language for the documentation. Translators fixed positions or occasional positions, covered for single projects. Technical Documents: Technical briefs are produced on a regular basis and are an invaluable source of information for you as a supporter of your localized Envolution Community. The subject matter is varied and covers all aspects of Envolution architecture, support, customization, features, announcements, bugs and comments. Documentation Tools and Formats All the official documentation can be produced using CVS (TiMax will create a directory for it, tell us where....) in HTML format. I personnaly use OpenOffice.org for it. Contributions and other team documentation could be produced using collaborative tools like Wiki. Pubblishing will be in PDF or HTML format in zip files for the Download Section and in HTML for on line versions (with Subjects Module, Content Express, etc.). Documentation License In our experience on eNvolution.it we learned to not use the Free Documentation License http://www.gnu.org/copyleft/fdl.html because we had some problems with irregular appropriation changing few words in the text. On envolution.it we use the Open Document License http://www.opencontent.org/openpub/ where evrybody can use or distribute not for commercial use the document but has to leave original credits and can't modify without permission of the authors. All the documentation IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY. Roadmap * On line manuals: of the Admin Panel localized in each /modules/..../lang/ directory as manual.html: some of these has to be written or updated. I will check which one are missing.... * Official Documentation: Based on Zoom's Official eNvolution Manual, but with different structure and chapters updated or rewritten: for version 1.2.5 or 1.3 - Part 1: Presentation of eNvolution (I have it almost ready in italian language, to be updated with the newest functions taken from "Who is envolution") with thumbnails of some representative eNvo sites - Part 2: Installation guide & basic settings : ( I have it also ready: local & remote installation for Win & Linux, upload to remote server, backup & dump, manual & script installation, basic configuration -> Settings in Admin Panel) - Part 3: Building your eNvo site: Layout : Naphta rewrote Sjah's manual.... - Part 4: Advanced settings: we have to update Zoom's manual for module settings... some parts could be taken from other existing contributions. * Technical Documentation : most of it is still avaible on most sites: eNvo API, eNvRender, etc. * Localized Documentation : it's documentation produced from the specific countries to soddisfy internal needs: could be translated for similar needs of other countries * How to...and Tutorials: produced and translated from and for the whole Network, like modules guides, .... * Contributes: sent by eNvo supporters and users: to be translated if worthy. The first two points has surely priority in the tasks roadmap. On line manuals need CVS production, for the official manual I propose to use also CVS. Other documentation can use both Wiki or HTML sent to translators. ciao, capretta |
|
From: Theresa A. S. <the...@ea...> - 2003-06-10 15:49:31
|
Hello,
You can put me down for english translation in the document project. My =
screen name is Theresa_Rose or you may use my real name Theresa Sanchez. =
I am still kind of unsure where else I can assist right now, I have =
limited PHP and MySQL skills but a full understanding of HTML and some =
graphic experience with Paint Shop Pro and Adobe Photo Shop. I have =
good support skills, but currently I don't know all the ins and outs of =
the newest eNvolution, going to found out more about it today as I =
finish an installation of it.
Thanks,
Theresa
----- Original Message -----=20
From: gagl=20
To: env...@li...=20
Sent: Tuesday, June 10, 2003 3:11 AM
Subject: [Envolution-devel] eNvolution Documentation Project
hi to evryone by capretta,
that's the first proposal on eNDP (eNvolution Documentation Project)
.....be eNvolved.....
=20
eNvolution Documentation Project (eNDP)
This is the Team at this moment:
a.. General Documentation Manager: capretta (who else? Naphta, =
GatoNero? Zoom?)
b.. Local Documentation Manager or Localization Director=20
- Italy: capretta
- Germany: naphta, gatonero
- France: philipc
- English: ???
- Other languages: ?????
c.. Staff writers: ??????????
d.. Translators: ????????
We need first of all enghish-speaking overviewers, who only have to =
check my bad english grammar... This position controls the texts and =
articles before publishing for grammatical and language correction ( I =
have to do some english on-line courses.....)
This is only a proposal on how to organize and manage the =
documentation. Everyone feels free to contribute, discuss and add =
suggestions. It's a starting point in the hope others add to the team =
and fill vacant positions, so we can start with the project.=20
=
*************************************************************************=
**
eNPD Vision and Proposition (eNPD Roadmap)
=
*************************************************************************=
**
eNDP Tasks:=20
taken from the ENISS eNvo Organizational Structure Document of the =
Founders
a.. General Documentation Manager:
This elected position is responsible to the Project Manager and the =
Founders. This position will require excellent communication skills and =
the ability to write documentation for both technical and non-technical =
users. The duties of this officer are, but not limited to:
1)Document creation.
2)FAQ's.
3)Recruits and supervises content writers.
4)Manages all published stories on the Envolution website.
5)How-To and Tutorial creation and publication.
This position requires daily interaction with the community and the =
Project Manager. This officer will also communicate with other officers =
to gain the required information to produce top quality documents for =
public consumption. Works directly with the Localization director to =
secure translations for the language specific support sites. This person =
should speak excellent English and have superior grammatical and =
spelling skills.
a.. Localization Manager:=20
This position is responsible for researching and implementing new =
languages and localizations for the entire project. This position =
answers directly to the Project Manager and the Founders (Specifically =
TiMax). This officer also tends to multilingual and translation duties =
for all project documentation. The officer must be prepared to interact =
daily with the community and the Documentation Manager. Duties are, but =
not limited to:
1)Language translations.
2)Document translations.
3)Coordinating between various international support sites and the =
other officers and Founders of the project.
4)Recruit non-English speaking people to interact with and/or join the =
project.
5)Help with coordinating international web sites with the main =
Envolution web site.
This position requires daily interaction with the community and the =
Project Manager as well as language specific support sites. This officer =
must be able to speak English and at least one other language. This =
officer should also expect to seek out other non-English speaking people =
to help with localization issues and support.
a.. Translators: every localization has its team of translators from =
or into english, that has to be the basic language for the =
documentation. Translators fixed positions or occasional positions, =
covered for single projects.
Technical Documents:=20
Technical briefs are produced on a regular basis and are an invaluable =
source of information for you as a supporter of your localized =
Envolution Community. The subject matter is varied and covers all =
aspects of Envolution architecture, support, customization, features, =
announcements, bugs and comments.
Documentation Tools and Formats
All the official documentation can be produced using CVS (TiMax will =
create a directory for it, tell us where....) in HTML format. I =
personnaly use OpenOffice.org for it.
Contributions and other team documentation could be produced using =
collaborative tools like Wiki.
Pubblishing will be in PDF or HTML format in zip files for the =
Download Section and in HTML for on line versions (with Subjects Module, =
Content Express, etc.).
Documentation License
In our experience on eNvolution.it we learned to not use the Free =
Documentation License http://www.gnu.org/copyleft/fdl.html because we =
had some problems with irregular appropriation changing few words in the =
text. On envolution.it we use the Open Document License =
http://www.opencontent.org/openpub/ where evrybody can use or distribute =
not for commercial use the document but has to leave original credits =
and can't modify without permission of the authors. All the =
documentation IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY.=20
Roadmap
a.. On line manuals: of the Admin Panel localized in each =
/modules/..../lang/ directory as manual.html: some of these has to be =
written or updated. I will check which one are missing....
a.. Official Documentation:=20
Based on Zoom's Official eNvolution Manual, but with different =
structure and chapters updated or rewritten: for version 1.2.5 or 1.3
- Part 1: Presentation of eNvolution (I have it almost ready in =
italian language, to be updated with the newest functions taken from =
"Who is envolution") with thumbnails of some representative eNvo sites
- Part 2: Installation guide & basic settings : ( I have it also =
ready: local & remote installation for Win & Linux, upload to remote =
server, backup & dump, manual & script installation, basic configuration =
-> Settings in Admin Panel)
- Part 3: Building your eNvo site: Layout : Naphta rewrote Sjah's =
manual....
- Part 4: Advanced settings: we have to update Zoom's manual for =
module settings... some parts could be taken from other existing =
contributions.
b.. Technical Documentation : most of it is still avaible on most =
sites: eNvo API, eNvRender, etc.
c.. Localized Documentation : it's documentation produced from the =
specific countries to soddisfy internal needs: could be translated for =
similar needs of other countries
d.. How to...and Tutorials: produced and translated from and for the =
whole Network, like modules guides, ....
e.. Contributes: sent by eNvo supporters and users: to be translated =
if worthy.
The first two points has surely priority in the tasks roadmap. On line =
manuals need CVS production, for the official manual I propose to use =
also CVS. Other documentation can use both Wiki or HTML sent to =
translators.
ciao,
capretta
|
|
From: <Chr...@t-...> - 2003-06-10 16:07:26
|
I would agree. Am Die, 2003-06-10 um 12.11 schrieb gagl: > hi to evryone by capretta, > that's the first proposal on eNDP (eNvolution Documentation Project) > .....be eNvolved..... > > > eNvolution Documentation Project (eNDP) > > > > > > > > This is the Team at this moment: > > a.. General Documentation Manager: capretta (who else? Naphta, GatoNero? Zoom?) > > b.. Local Documentation Manager or Localization Director > > - Italy: capretta > > - Germany: naphta, gatonero > > - France: philipc > > - English: ??? > > - Other languages: ????? > > c.. Staff writers: ?????????? > > d.. Translators: ???????? > > > We need first of all enghish-speaking overviewers, who only have to check my bad english grammar... This position controls the texts and articles before publishing for grammatical and language correction ( I have to do some english on-line courses.....) > > > > > This is only a proposal on how to organize and manage the documentation. Everyone feels free to contribute, discuss and add suggestions. It's a starting point in the hope others add to the team and fill vacant positions, so we can start with the project. > > *************************************************************************** > > eNPD Vision and Proposition (eNPD Roadmap) > > *************************************************************************** > > > eNDP Tasks: > > taken from the ENISS eNvo Organizational Structure Document of the Founders > > a.. General Documentation Manager: > > This elected position is responsible to the Project Manager and the Founders. This position will require excellent communication skills and the ability to write documentation for both technical and non-technical users. The duties of this officer are, but not limited to: > > 1)Document creation. > > 2)FAQ's. > > 3)Recruits and supervises content writers. > > 4)Manages all published stories on the Envolution website. > > 5)How-To and Tutorial creation and publication. > > This position requires daily interaction with the community and the Project Manager. This officer will also communicate with other officers to gain the required information to produce top quality documents for public consumption. Works directly with the Localization director to secure translations for the language specific support sites. This person should speak excellent English and have superior grammatical and spelling skills. > > a.. Localization Manager: > > This position is responsible for researching and implementing new languages and localizations for the entire project. This position answers directly to the Project Manager and the Founders (Specifically TiMax). This officer also tends to multilingual and translation duties for all project documentation. The officer must be prepared to interact daily with the community and the Documentation Manager. Duties are, but not limited to: > > 1)Language translations. > > 2)Document translations. > > 3)Coordinating between various international support sites and the other officers and Founders of the project. > > 4)Recruit non-English speaking people to interact with and/or join the project. > > 5)Help with coordinating international web sites with the main Envolution web site. > > This position requires daily interaction with the community and the Project Manager as well as language specific support sites. This officer must be able to speak English and at least one other language. This officer should also expect to seek out other non-English speaking people to help with localization issues and support. > > a.. Translators: every localization has its team of translators from or into english, that has to be the basic language for the documentation. Translators fixed positions or occasional positions, covered for single projects. > > > > > > Technical Documents: > > > Technical briefs are produced on a regular basis and are an invaluable source of information for you as a supporter of your localized Envolution Community. The subject matter is varied and covers all aspects of Envolution architecture, support, customization, features, announcements, bugs and comments. > > > > > Documentation Tools and Formats > > > > > All the official documentation can be produced using CVS (TiMax will create a directory for it, tell us where....) in HTML format. I personnaly use OpenOffice.org for it. > > Contributions and other team documentation could be produced using collaborative tools like Wiki. > > Pubblishing will be in PDF or HTML format in zip files for the Download Section and in HTML for on line versions (with Subjects Module, Content Express, etc.). > > > > > Documentation License > > > > > In our experience on eNvolution.it we learned to not use the Free Documentation License http://www.gnu.org/copyleft/fdl.html because we had some problems with irregular appropriation changing few words in the text. On envolution.it we use the Open Document License http://www.opencontent.org/openpub/ where evrybody can use or distribute not for commercial use the document but has to leave original credits and can't modify without permission of the authors. All the documentation IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY. > > > > > > > > Roadmap > > > > > a.. On line manuals: of the Admin Panel localized in each /modules/..../lang/ directory as manual.html: some of these has to be written or updated. I will check which one are missing.... > > a.. Official Documentation: > > Based on Zoom's Official eNvolution Manual, but with different structure and chapters updated or rewritten: for version 1.2.5 or 1.3 > > - Part 1: Presentation of eNvolution (I have it almost ready in italian language, to be updated with the newest functions taken from "Who is envolution") with thumbnails of some representative eNvo sites > > - Part 2: Installation guide & basic settings : ( I have it also ready: local & remote installation for Win & Linux, upload to remote server, backup & dump, manual & script installation, basic configuration -> Settings in Admin Panel) > > - Part 3: Building your eNvo site: Layout : Naphta rewrote Sjah's manual.... > > - Part 4: Advanced settings: we have to update Zoom's manual for module settings... some parts could be taken from other existing contributions. > > b.. Technical Documentation : most of it is still avaible on most sites: eNvo API, eNvRender, etc. > > c.. Localized Documentation : it's documentation produced from the specific countries to soddisfy internal needs: could be translated for similar needs of other countries > > d.. How to...and Tutorials: produced and translated from and for the whole Network, like modules guides, .... > > e.. Contributes: sent by eNvo supporters and users: to be translated if worthy. > > > > > The first two points has surely priority in the tasks roadmap. On line manuals need CVS production, for the official manual I propose to use also CVS. Other documentation can use both Wiki or HTML sent to translators. > > > > > > > > ciao, > capretta > |
|
From: Scott K. <sc...@ki...> - 2003-06-11 10:16:10
|
On Tue, 2003-06-10 at 05:11, gagl wrote: > In our experience on eNvolution.it we learned to not use the Free > Documentation License http://www.gnu.org/copyleft/fdl.html because we > had some problems with irregular appropriation changing few words in > the text. On envolution.it we use the Open Document License > http://www.opencontent.org/openpub/ where evrybody can use or > distribute not for commercial use the document but has to leave > original credits and can't modify without permission of the authors. > All the documentation IS LICENSED FREE OF CHARGE, THERE IS NO > WARRANTY. I would like to challenge this! First and foremost stating that everyone can "use or distribute not for commercial use" is a restriction that doesn't need to be there! In fact by stating this we would be taking the position we are against commercial interests and would seriously hurt the project as whole. The FSF Free Documentation License recognizes this and has protections for the doc author and still allows for commercial publication. So you get freedom and license protection. As for experiences with the FDL I can report nothing but good experiences with it. In fact the Envolution 1.0 manual was written and published uner it...without a problem. I support both FREE software and Open Source software. I realize and fully understand the difference between the two as well. But we simply cannot say in our licensing terms or anything else that you can use our documents "except for commercial use". We should stick to FSF license guidelines, both GPL and FDL Zoom |
|
From: teddy <te...@vo...> - 2003-06-12 08:19:26
|
You did a very fast&nice translation of the Sjah=92s articles! If you need some help to correct the misprints, please ask me! I=92ve noticed a pair of mistakes... =93molti dello staffa=94 3rd line =93l'articolo sui Modelli di Modulo=A0=A0qu=EC =93 fifth line from the = end =93pagoine di Amministrazione=94 in Modelli Modulo Admin =93Step 3: Aginungete una Nuova=94 =20 I speak English and German, good enough to translate to italian. Ciao, Guido(volleyclub). -----Original Message----- From: env...@li... [mailto:env...@li...] On Behalf Of gagl Sent: marted=EC 10 giugno 2003 12.11 To: env...@li... Subject: [Envolution-devel] eNvolution Documentation Project hi to evryone by capretta, that's the first proposal on eNDP (eNvolution Documentation Project) .....be eNvolved..... =A0 =A0=20 eNvolution Documentation Project (eNDP) This is the Team at this moment: =95 General Documentation Manager: capretta (who else? Naphta, = GatoNero?=A0 Zoom?) =95 Local Documentation Manager or Localization Director=20 - Italy: capretta - Germany: naphta, gatonero - France: philipc - English: ??? - Other languages: ????? =95 Staff writers: ?????????? =95 Translators: ???????? We need first of all enghish-speaking overviewers, who only have to check my bad english grammar... This position controls the texts and articles before publishing for grammatical and language correction ( I have to do some english on-line courses.....) This is only a proposal on how to organize and manage the documentation. Everyone feels free to contribute, discuss and add suggestions. It's a starting point in the hope others add to the team and fill vacant positions, so we can start with the project.=20 ************************************************************************ *** eNPD Vision and Proposition (eNPD Roadmap) ************************************************************************ *** eNDP Tasks:=20 taken from the ENISS eNvo Organizational Structure Document of the Founders =95 General Documentation Manager: This elected position is responsible to the Project Manager and the Founders. This position will require excellent communication skills and the ability to write documentation for both technical and non-technical users. The duties of this officer are, but not limited to: 1)Document creation. 2)FAQ's. 3)Recruits and supervises content writers. 4)Manages all published stories on the Envolution website. 5)How-To and Tutorial creation and publication. This position requires daily interaction with the community and the Project Manager. This officer will also communicate with other officers to gain the required information to produce top quality documents for public consumption. Works directly with the Localization director to secure translations for the language specific support sites. This person should speak excellent English and have superior grammatical and spelling skills. =95 Localization Manager:=20 This position is responsible for researching and implementing new languages and localizations for the entire project. This position answers directly to the Project Manager and the Founders (Specifically TiMax). This officer also tends to multilingual and translation duties for all project documentation. The officer must be prepared to interact daily with the community and the Documentation Manager. Duties are, but not limited to: 1)Language translations. 2)Document translations. 3)Coordinating between various international support sites and the other officers and Founders of the project. 4)Recruit non-English speaking people to interact with and/or join the project. 5)Help with coordinating international web sites with the main Envolution web site. This position requires daily interaction with the community and the Project Manager as well as language specific support sites. This officer must be able to speak English and at least one other language. This officer should also expect to seek out other non-English speaking people to help with localization issues and support. =95 Translators: every localization has its team of translators from or into english, that has to be the basic language for the documentation. Translators fixed positions or occasional positions, covered for single projects. Technical Documents:=20 Technical briefs are produced on a regular basis and are an invaluable source of information for you as a supporter of your localized Envolution Community. The subject matter is varied and covers all aspects of Envolution architecture, support, customization, features, announcements, bugs and comments. Documentation Tools and Formats All the official documentation can be produced using CVS (TiMax will create a directory for it, tell us where....) in HTML format. I personnaly use OpenOffice.org for it. Contributions and other team documentation could be produced using collaborative tools like Wiki. Pubblishing will be in PDF or HTML format in zip files for the Download Section and in HTML for on line versions (with Subjects Module, Content Express, etc.). Documentation License In our experience on eNvolution.it we learned to not use the Free Documentation License http://www.gnu.org/copyleft/fdl.html because we had some problems with irregular appropriation changing few words in the text. On envolution.it we use the Open Document License http://www.opencontent.org/openpub/ where evrybody can use or distribute not for commercial use the document but has to leave original credits and can't modify without permission of the authors. All the documentation IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY.=20 Roadmap =95 On line manuals: of the Admin Panel localized in each /modules/..../lang/ directory as manual.html: some of these has to be written or updated. I will check which one are missing.... =95 Official Documentation:=20 Based on Zoom's Official eNvolution Manual, but with different structure and chapters updated or rewritten: for version 1.2.5 or 1.3 - Part 1: Presentation of eNvolution (I have it almost ready in italian language, to be updated with the newest functions taken from =93Who is envolution=94) with thumbnails of some representative eNvo sites - Part 2: Installation guide & basic settings : ( I have it also ready: local & remote installation for Win & Linux, upload to remote server, backup & dump, manual & script installation, basic configuration -> Settings in Admin Panel) - Part 3: Building your eNvo site: Layout : Naphta rewrote Sjah's manual.... - Part 4: Advanced settings: we have to update Zoom's manual for module settings... some parts could be taken from other existing contributions. =95 Technical Documentation : most of it is still avaible on most sites: eNvo API, eNvRender, etc. =95 Localized Documentation : it's documentation produced from the specific countries to soddisfy internal needs: could be translated for similar needs of other countries =95 How to...and Tutorials: produced and translated from and for the = whole Network, like modules guides, .... =95 Contributes: sent by eNvo supporters and users: to be translated if worthy. The first two points has surely priority in the tasks roadmap. On line manuals need CVS production, for the official manual I propose to use also CVS. Other documentation can use both Wiki or HTML sent to translators. ciao, capretta |
|
From: gagl <ca...@fr...> - 2003-06-12 18:14:35
|
ciao, thanks, Guido: you're undertaken for these tasks :-) ciao, capretta |
|
From: <s.k...@pr...> - 2003-06-12 23:32:48
|
@all: TiMax and I have finished the last cosmetics and fixes on eNvo 1.2.5 It seems, that all works perfect and the entire system is ready to use. We are able to release this version in the next 36 hours. This is your last chance for testing (pre-release4.zip) and announce = problems, bugs and notices.=20 TiMax opened a new branch on CVS. He will tell you some details = separately. "envolution_1.2" is history ;) ....... everything else is relative = ......... That's all for now, WindMeUp |
|
From: TiMax <ma...@em...> - 2003-06-13 05:47:22
|
Ok Branch of eNvo 1.2.5 is open in cvs, you can see it with name= envolution_1.2.5 Please to commit only little cosmetics or languages fix in this= branch, it is our stable version, we open new developement branch envolution_1.3 in next days. If you have other or big changements to commit please contact me= or WindMeUp before . Someone can re-write welcome message in english language ? Maybe we need also a better powered logo, someone want to play= with graphics We need also to prepare presentation article for this release,= with features, bla bla bla maybe we can start from my article " who is envo " , anyway if someone have some= suggestions write please. TiMax |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X