You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(2) |
Feb
(48) |
Mar
(17) |
Apr
(13) |
May
(102) |
Jun
(163) |
Jul
(203) |
Aug
(185) |
Sep
(16) |
Oct
(4) |
Nov
|
Dec
|
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: Scott K. <sc...@ki...> - 2003-06-12 04:12:47
|
On Wed, 2003-06-11 at 18:09, Stefan K=C3=B6hler wrote: > > Defalut install. > >=20 > > As admin user one cannot change the language from All to English when > > you click to edit the poll. Tried to change it and check after each > > attempt and it will not change. > >=20 > > Zoom >=20 > fixed. > Look to modules/NS-Polls/admin.php on line 179 > change "pnVarPrepForStore($planguage)" to "pnVarPrepForStore($alanguage= )" >=20 > The parameter "$planguage" is not used in this function. >=20 > WindMeUp >=20 Excellent! That did the trick. Lemme see what else I can drum up. Zoom |
From: <s.k...@pr...> - 2003-06-11 23:15:29
|
> 1. The top links in the installation panels "FAQ! "Documents" > are pointing to the italian eNvo site is fixed. Look some posts before from TiMax: "Fixed now i changed all links, and put different links to support forum, developement, wiki etc for each support site in each language, also links now are in define language so is easy for users to change it." > 2. (New) Installation without any problems good > 3. First screen of the website (and later all the others): left > zone 10%, middle zone 15% and right zone all over the rest of > the width of the screen I have no such problems with IE, Mozilla and NS on Win2000 > 4. No german translation daily_archive (will be some work for > me) > 6. Some adminlite translations are missing (job for me also) > 8. Some german translations for subjects are missing (job for > me) Yes. Many german translations are missing. > 7. No reactions from ew_filemanager, the adress is pointing to > it, but it looks like the startpage I see no problems with FileManager WindMeUp |
From: <s.k...@pr...> - 2003-06-11 23:08:43
|
> Defalut install. > > As admin user one cannot change the language from All to English when > you click to edit the poll. Tried to change it and check after each > attempt and it will not change. > > Zoom fixed. Look to modules/NS-Polls/admin.php on line 179 change "pnVarPrepForStore($planguage)" to "pnVarPrepForStore($alanguage)" The parameter "$planguage" is not used in this function. WindMeUp |
From: Scott K. <sc...@ki...> - 2003-06-11 22:31:02
|
Defalut install. As admin user one cannot change the language from All to English when you click to edit the poll. Tried to change it and check after each attempt and it will not change. Zoom |
From: <Chr...@t-...> - 2003-06-11 22:21:09
|
Here are my test results on special debian (german installation with mozilla 1.2.1) 1. The top links in the installation panels "FAQ! "Documents" are pointing to the italian eNvo site 2. (New) Installation without any problems 3. First screen of the website (and later all the others): left zone 10%, middle zone 15% and right zone all over the rest of the width of the screen 4. No german translation daily_archive (will be some work for me) 5. Nice welcome article in german translation ;-) (no more pn-forking etc.) 6. Some adminlite translations are missing (job for me also) 7. No reactions from ew_filemanager, the adress is pointing to it, but it looks like the startpage 8. Some german translations for subjects are missing (job for me) I have to stop for today. Where should I do my translations? In CVS? For daily_archive also? Have a lot of fun! gatoNero/Christoph |
From: Scott K. <sc...@ki...> - 2003-06-11 22:09:36
|
/themes/Michelangelo/templates/imgtpl/tit_bullet.gif is missing in the default installation. This is picky but true! I'll let ya know how all else turns out on my test run. Zoom |
From: romeo b. .:Envolution.info:. <ci...@en...> - 2003-06-11 17:59:20
|
Too many time in administration variables are lost when a changes is submitted, and the user come back to main administration or to the index page. Try for example to change the settings for the file manager module... Any ideas to conserve the hidden variables? Romeo |
From: TiMax - E. <web...@en...> - 2003-06-11 17:36:40
|
Very good Sjah ... very nice artcile and tutorial ... Like always ...... excellent work TiMax |
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: Scott K. <sc...@ki...> - 2003-06-11 01:31:23
|
On Tue, 2003-06-10 at 07:05, M Asrul Sani Arifin wrote: > Let=E2=80=99s say I translate that document into my own language (Malay= ), will > that constitute a breach of the license? Is it considered a > modification? Which requires me to get the consent of the original > writer. Just curious. >=20 If you translate it the original author should credit you but the translated doc is still copyright the original author. Zoom |
From: TiMax <ma...@em...> - 2003-06-10 19:31:09
|
Try also that Put compression off or you can also also comment = ob_start("ob_gzhandler"); in pnApi.php go in configuration file manger to change some settings and click= in save you get an header already sent error if compression is on ... no problem TiMax On 09 Jun 2003 20:02:39 -0500, Scott Kindley wrote: > Max can you explain what trouble you are having with the= "compression > option" in 1.2.5? > > You wrote: "we need to check "compression option" sometimes= give some > troubles ...." > > Cause if it's what I'm thinking of servers that have= mod_deflate or > mod_gzip already running and you try to enable PHP's built in > compression you will get garbled output to the screen cause= your double > compressing. > > Is that what you mean? > > Zoom > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of= TotalView, The best > thread debugger on the planet. Designed with thread debugging= features > you've never dreamed of, try TotalView 6 free at= www.etnus.com. > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel |
From: Denver P. Jr. <den...@co...> - 2003-06-10 19:28:45
|
I thought there was a feature freeze until everything is cleaned up in current code base. -----Original Message----- From: env...@li... [mailto:env...@li...] On Behalf Of romeo bandinelli .:Envolution.info:. Sent: Tuesday, June 10, 2003 10:09 AM To: env...@li... Subject: [Envolution-devel] eNvo 1.3 Hi all, and sorry for my absence from this list. I'd like to express my opinion about the features to implement in the eNvo 1.3 or later, after a period of study of the necessities of the enterprise and the users. 1) CMS functionality. I think that more features are necessaries to make envolution usable from the enterprise to publish their information. First a more flexible permissions system for the news module: in the actual schema, only preview and publish is not enough for most of the users. For most of them is absolutely important to know who pulishes a news. It would be also a nice feature to have some template for the news. Another point of interest is the module subject. At the moment is very difficult do manage permission on the pages. I think that subject could be an instrument to let users to delegate specific area to other person, and next features shoud be in that direction. 2) WorkFlow Most enterprise are moving to an integrated managemet of the information and documents. Datawarehouse, document manager and workflow are becoming important point for the enterprise software. Tiki is developing a workflow class, named galaxia, based on the standard of www.openflow.it. I think that development in that directions are important. 3) User management Now is important to make up for the lost time towards postnuke and xaraya and to implement ldap mecanism to login. I this it would be important to implement also pop3, imap and web services login, like xmlrpc. Sorry for my english. In my little, I'm working on a universitary project in developing a workflow framework. I don't know if it will be release on a gpl license, but if someone could work on it, or just make the porting of galaxy on envolution, I can give an help. Thanks Romeo ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Envolution-devel mailing list Env...@li... https://lists.sourceforge.net/lists/listinfo/envolution-devel |
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: TiMax <ma...@em...> - 2003-06-10 18:35:34
|
On Tue, 10 Jun 2003 14:28:30 +0200, Stefan Koehler wrote: > Here are some of my test results: > > Clean Installation in english on Mandrake Linux: > > 1. Navbar not practicable [ Michelangelo::funcs.php ->= navtabs() ]. All links in italian and only off if $buttons_top =3D 0 (default at install. time: 1). Fixed now i changed all links, and put different links to support forum,= developement, wiki etc for each support site in each language, also links now are in define language so is easy= for users to change it. > 2. Ratings missing in Admin-Part. To change the default style= of ratings nothing happened. The style is fixed on "five stars". > Also this module is unregistered in Admin::modules::list Why? why this module is more more under developement, now i= deactivated it for default. > 3. The startup articles are old. They have to rewritten or= actualize. I have rewrite a litte startup article in italian language, maybe= we can use Who is envo document how reference. > 4. Filemanager: "max HDD space.." not set. Must be predefined= (ie. 10.000.000 bytes), otherwise no upload possible. fixed > 5. Filemanager: image viewing not possible. ?? i don't have any trouble > > 6. Some definitions are unset. where ? > 7. Some german definitions are unset or complete missing. Sorry that is your or gatonero work :)) i don't understand german= language also check please english installation we have some german defines > 8. User_Account: allowed images file-type and -size are= missing. This has to be pre-defined at install time (or completly disallowed). fixed > 9. Errore: Can't admin this module. I get blank screen. Is correct, this module is for future implementation redirect etc= ...... > 10. Compression: It is better to ask this setting at= installation time. Because if Apache-compression is set on Webserver and we set internal compression additionaly, it can= produce problems (zoom describes it). Maybe we can also put off for default, but we have some header= problems with compression off ... i need to check more that > 11. TBODY must be set to ON at install. time. fixed > > 12. H1..H6 must be set to ON at install. time. fixed > > 13. Comments: Writing comment we have to add to the= RTE-activation a modification to pre-select "HTML formated" and not "plain text". maybe you can check that better ....... i think you know RTE= :))) > > > This was a quick overview. All other results I will post, when= I recode the upgrade scripts tonight. > > WindMeUp I need to talk with WindMeUp, and after or i prepare new= pre-relase package or i open branch in CVS. TiMax |
From: TiMax <ma...@em...> - 2003-06-10 18:23:30
|
On Tue, 10 Jun 2003 03:01:29 -0500, Sjahrazad Alamsjah wrote: > I made a quick local test using win2000: > > 1. Installation - ok > > 2. Admin page error, the Rating module images folder and= admin.png was not > found. It is also the same with ew_filemanager and subjects. fixed > > 3. Subjects & ew_filemanager great :), the upload file in= filemanager error > and the edit function use the rte. I think it is better not to= use rte for > filemanager, so we can edit any files with htm, txt or php= ext. error upload fixed i add also php extension in filemanger, so now you can edit also= php file with RTE > > 5. rte is working better now. Since rte table use the tbody= tag, its should > be allowed in setting page > > I'll test later on, in redhat linux and win xp > > sjah > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of= TotalView, The best > thread debugger on the planet. Designed with thread debugging= features > you've never dreamed of, try TotalView 6 free at= www.etnus.com. > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel |
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: 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: 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: romeo b. .:Envolution.info:. <ci...@en...> - 2003-06-10 15:10:11
|
Hi all, and sorry for my absence from this list. I'd like to express my opinion about the features to implement in the eNvo 1.3 or later, after a period of study of the necessities of the enterprise and the users. 1) CMS functionality. I think that more features are necessaries to make envolution usable from the enterprise to publish their information. First a more flexible permissions system for the news module: in the actual schema, only preview and publish is not enough for most of the users. For most of them is absolutely important to know who pulishes a news. It would be also a nice feature to have some template for the news. Another point of interest is the module subject. At the moment is very difficult do manage permission on the pages. I think that subject could be an instrument to let users to delegate specific area to other person, and next features shoud be in that direction. 2) WorkFlow Most enterprise are moving to an integrated managemet of the information and documents. Datawarehouse, document manager and workflow are becoming important point for the enterprise software. Tiki is developing a workflow class, named galaxia, based on the standard of www.openflow.it. I think that development in that directions are important. 3) User management Now is important to make up for the lost time towards postnuke and xaraya and to implement ldap mecanism to login. I this it would be important to implement also pop3, imap and web services login, like xmlrpc. Sorry for my english. In my little, I'm working on a universitary project in developing a workflow framework. I don't know if it will be release on a gpl license, but if someone could work on it, or just make the porting of galaxy on envolution, I can give an help. Thanks Romeo |
From: Stefan K. <Ste...@ga...> - 2003-06-10 13:40:10
|
@suman: [...] I had volunteered for English. Let me know if my proposition is accepted = or rejected. suman [...] The published eNDP by capretta is only an overview how it can looks like. Especially the team list and some definitions are not closed. I know that you want to manage the english part. And I think there are no = objections. We need some more days to present a final list of all staff members. WindMeUp |
From: Stefan K. <Ste...@ga...> - 2003-06-10 12:36:58
|
Here are some of my test results: Clean Installation in english on Mandrake Linux: 1. Navbar not practicable [ Michelangelo::funcs.php -> navtabs() ]. All = links in italian and only off if $buttons_top =3D 0 (default at install. = time: 1). 2. Ratings missing in Admin-Part. To change the default style of ratings = nothing happened. The style is fixed on "five stars". Also this module is unregistered in Admin::modules::list Why? 3. The startup articles are old. They have to rewritten or actualize. 4. Filemanager: "max HDD space.." not set. Must be predefined (ie. = 10.000.000 bytes), otherwise no upload possible. 5. Filemanager: image viewing not possible. 6. Some definitions are unset. 7. Some german definitions are unset or complete missing. 8. User_Account: allowed images file-type and -size are missing. This has = to be pre-defined at install time (or completly disallowed). 9. Errore: Can't admin this module. I get blank screen. 10. Compression: It is better to ask this setting at installation time. = Because if Apache-compression is set on Webserver and we set internal = compression additionaly, it can produce problems (zoom describes it). 11. TBODY must be set to ON at install. time. 12. H1..H6 must be set to ON at install. time. 13. Comments: Writing comment we have to add to the RTE-activation a = modification to pre-select "HTML formated" and not "plain text". This was a quick overview. All other results I will post, when I recode = the upgrade scripts tonight. WindMeUp |
From: M A. S. A. <as...@st...> - 2003-06-10 12:36:56
|
Let's say I translate that document into my own language (Malay), will that constitute a breach of the license? Is it considered a modification? Which requires me to get the consent of the original writer. Just curious. -----Original Message----- From: env...@li... [mailto:env...@li...] On Behalf Of gagl Sent: Tuesday, June 10, 2003 6:11 PM 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..... 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: R. S. k. <su...@su...> - 2003-06-10 12:32:44
|
@Gagl & Stephen I had volunteered for English. Let me know if my proposition is accepted or rejected. suman gagl wrote: > > > > > > >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: Stefan K. <Ste...@ga...> - 2003-06-10 11:33:47
|
@capretta: Please talk with naphta. He has begun with a first step for a manual on = his private site with phpWiki. I think we need some rules and guidelines for writers on all local sites. = This is needed because everyone must know the new documentation structure, = ie. chapters, contents, footnotes, etc. I think at first we need a "table of contents" with all chapters and = sub-chapters. The best way to share and public our manual is, to write everything with = phpWiki. This tool is installed on eNvo.de, eNvo.com and eNvo.it I don't know if it = is installed on eNvo.fr These four languages are our premier langs. All others can follows later. The technical documentation will be written (generate) with phpDocumentor. = This tool is very good, but we need some definitions, rules and guidelines = for all developers and coders. phpDocumentor needs some special tags in the comments of the source code. I will define it end of this week on this mailing list. The complete staff list for all positions (managers, local managers, = writers, translators, etc.) will follows also at end of week. I will discuss some details with TiMax (and you) before. It is absolutly necessary if we want to create this document over several = local teams to find a uniform concept and all use the same tools. =20 [...] a.. General Documentation Manager: capretta (who else? Naphta, GatoNero? = Zoom?) [...] No one else. One General Doc Manager is enough. [...] b.. Local Documentation Manager or Localization Director=20 - Italy: capretta - Germany: naphta, gatonero - France: philipc - English: ??? - Other languages: ????? [...] All Local Docu Managers are your right hands. The LDM manage the complete = docu in their primary langs. [...] 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.....) [...] I don't think so. Sure, we need overviewers, but it is not the primary = task. Every LDM work autonom, which means, that I don't want to write ONE = docu in ONE language and then translate it into the others. This makes no sense. [...] 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 [...] I agree if we use an open, public tool like phpWiki. [...] eNPD Vision and Proposition (eNPD Roadmap) [...] I agree with most of them. Some small details can be correct later, if we = have defined the completly staff. [...] Documentation License ... 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 [...] I agree. Your roadmap is perfect and well done. [...] 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. [...] Why CVS? We can also use phpWiki. It included also a versioning system = like CVS. And it is a bit faster, because you can install it as module on = every eNvo site. [...] Other documentation can use both Wiki or HTML sent to translators. [...] Translations are not needed if we organize the Docu team as I describe = above. WindMeUp ciao, capretta |