Onno, I've had some issues with Firefox, as I mentioned to you, but I don't know about others. Maybe I should upgrade to a new version of Firefox.
Text search may be a helpful feature to have. Showing changed pages (as compared to a baseline) may prove to be really useful, specially for the translation effort to keep up with the original Web site evolution. Upload of images is also important, since new and translated content will have to deal with images. The report below seems good in terms of info (who, what, when...). I think we should try sending automatically to epf-dev (maybe weekly?) so everyone has a sense of what has happened and take any actions needed. One question about the comments we put in pages on the translated Web sites: do we need to always put comments in English, or can people use the language subject of translation? Do others care about comments being posted in other languages than English? Or would comments in English make it easier in case a broader discussion is needed? Just a thought. Thanks, Ricardo Balduino Senior Software Engineer IBM Rational Software (www.ibm.com/rational) Eclipse Process Framework (www.eclipse.org/epf) "Straaten, Onno van der" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 04/11/2007 11:28 PM Please respond to Eclipse Process Framework Project Developers List <[EMAIL PROTECTED]> To <[EMAIL PROTECTED]> cc Subject RE: [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net) Ricardo, Jim, I have available some time this week to implement some enhancements, but now I'm not sure about priority, I got the impression that most of us use FireFox; maybe it is better to improve FireFox support first? There are some options for improvements I considered earlier: - fix FireFox issues; - full text search; - baseline changes: show changes (new, removed, changed pages) after baseline update; - upload of images and documents (this functionality was lost with cleanup of code); - and of course: update epf-dev mailing list with Wiki changes; Any other suggestions you might have we can consider too of course. About the information we could extract: most of the information is already in the (daily, weekly, monthly) change report; I copied the contents of the report below as an example. We could show for each Wiki: name and baseline, the contributed pages and versions of pages and comments. For each page and version: title with link to the page, version info and version note. For each comment: text (truncated to 50 chars?), link to comments, page and version info. For each contribution the user (name and ID). Other useful information might be the baseline changes (new, removed, changed pages) in each weekly build of OpenUP. Best Regards, Onno [EPF Wiki] Monthly Change Report - April 2007 Wiki Sites Site Baseline New Versions New Comments Checkouts OpenUP OpenUP_Basic_published-0.9-W-20070406 4 (from 4) 3 (from 3) 1 New! XP XP_published-0.1-20071601 0 (from 0) 0 (from 0) 0 New! OpenUP PT OUP_PT_20070403 22 (from 22) 0 (from 0) 1 New! Scrum SCRUM_20070410 0 (from 0) 0 (from 0) 0 New! OpenUP RU OUP_RU_20070410 0 (from 0) 0 (from 0) 0 New! New Versions Page Version Note Site Created Glossário de Tradução Version 5 Adding more content OpenUP PT about 4 hours ago by Paulo Moreira Concept: Collaborate to align interests and share understanding Version 2 terminado OpenUP PT about 4 hours ago by takai Task: Plan Iteration Version 1 Resolution of BUG 170803 OpenUP about 19 hours ago by Ana Paula Valente Pereira Concept: Collaborate to align interests and share understanding Version 1 Tradução parcial. OpenUP PT about 20 hours ago by takai Concept: Balance competing priorities to maximize stakeholder value Version 2 Acerto da formatação OpenUP PT about 20 hours ago by takai Concept: Balance competing priorities to maximize stakeholder value Version 1 OpenUP PT about 23 hours ago by takai Custom Category Version 4 Correção: alinhas para alinhar. OpenUP PT 1 day ago by takai Guideline: Minimal, Complete, and Extensible Version 2 OpenUP PT 1 day ago by takai Guideline: Minimal, Complete, and Extensible Version 1 OpenUP PT 1 day ago by takai Guideline: OpenUP and OpenUP/Basic Version 1 OpenUP PT 1 day ago by takai Custom Category Version 3 OpenUP PT 1 day ago by takai Custom Category Version 2 OpenUP PT 1 day ago by takai Custom Category Version 1 OpenUP PT 1 day ago by takai Glossário de Tradução Version 4 OpenUP PT 1 day ago by takai Glossário de Tradução Version 3 Including some terms OpenUP PT 1 day ago by Paulo Moreira Custom Category Version 6 Added link to Translation Glossary to top of intro page for easy access. Remove link when we are done with translation, but save page somewhere else. OpenUP PT 1 day ago by Ricardo Balduino Glossário de Tradução Version 2 OpenUP PT 1 day ago by Ricardo Balduino Glossário de Tradução Version 1 Translation glossary created to help translation process. OpenUP PT 1 day ago by Ricardo Balduino Custom Category Version 5 Link added at the bottom of the page didn't work. Making it plain text, so we remember to add the link later. OpenUP PT 1 day ago by Ricardo Balduino Custom Category Version 4 Mudei acentuação e acrescentei um link no final to texto, que foi já adicionado ao OpenUP/Basic original OpenUP PT 1 day ago by Ricardo Balduino Discipline: Architecture Version 1 OpenUP 1 day ago by Jim Ruehlin Guideline: Software Reuse Version 1 OpenUP 1 day ago by Jim Ruehlin Custom Category Version 3 pequena correção: de balanciar para balancear OpenUP PT 5 days ago by zalkind Custom Category Version 2 Some minor changes after review OpenUP PT 5 days ago by Paulo Moreira Custom Category Version 1 First translation to Portuguese OpenUP PT 6 days ago by Paulo Moreira Role: Developer Version 1 I changed the brief description and added a link to the test case in the modifies area. OpenUP 13 days ago by Brian Lyons New Comments Comment Page Site Created I wonder if we want to say ... Role: Developer OpenUP 6 days ago by Jim Ruehlin This discipline has changed... Discipline: Implementation OpenUP 13 days ago by Jim Ruehlin This discipline has changed... Discipline: Analysis & Design OpenUP 13 days ago by Jim Ruehlin New Users Allan Halme, takai, zalkind, Ronaldo Luiz, tom weinberger, Paulo Moreira, Calen Legaspi, Aitor, hopeshared, Onno Checkouts Page Version Site Created Guideline: Minimal, Complete, and Extensible Version 2 OpenUP PT 1 day ago by takai Task: Plan Iteration Version 1 OpenUP about 19 hours ago by Ana Paula Valente Pereira Generated on: Wed Apr 11 10:43:05 -0700 2007 Showing changes since: Mon Mar 12 10:43:05 -0700 2007 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ricardo Balduino Sent: woensdag 4 april 2007 2:43 To: Eclipse Process Framework Project Developers List Subject: RE: [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net) There's a separate thread I'm having with Eclipse legal on this very topic. I'll post to this list when I get an answer from them. Thanks, Ricardo Balduino Senior Software Engineer IBM Rational Software (www.ibm.com/rational) Eclipse Process Framework (www.eclipse.org/epf) Jim Ruehlin/Irvine/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 04/03/2007 05:00 PM Please respond to Eclipse Process Framework Project Developers List <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject RE: [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net) I agree Onno, this is a great idea. Should we have a meeting to figure out the process by which the contributions and comments would work before we check with Eclipse legal? Or can we reference the wiki in epf-dev and newsgroup threads? BTW, the RSS feed for wiki changes is a great feature too! Thanks, Jim ____________________ Jim Ruehlin, IBM Rational RUP Content Developer Eclipse Process Framework (EPF) Committer www.eclipse.org/epf email: [EMAIL PROTECTED] phone: 760.505.3232 fax: 949.369.0720 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ricardo Balduino/Cupertino/IBM Sent: Tuesday, April 03, 2007 1:51 PM To: [EMAIL PROTECTED] Subject: Re: [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net) Onno, I think it is a great idea to periodically send an automatic message to epf-dev with a summary of what has been contributed to the Wiki. We'd need to clear with Eclipse legal that this approach works though. I'd say we start with weekly reports, so we have a sense of the volume of contributions. What information could we automatically extract? It would be interesting to see in this report, as a minimum: - Web site name and version - list of pages contributed/changed, - list of contributors - name or user ID - date of contribution - material contributed (this may be too much, a link to the Wiki page may be more feasible) - any other information? Thanks, Ricardo Balduino Senior Software Engineer IBM Rational Software (www.ibm.com/rational) Eclipse Process Framework (www.eclipse.org/epf) "Straaten, Onno van der" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 04/03/2007 01:40 AM Please respond to Eclipse Process Framework Project Developers List <[EMAIL PROTECTED]> To <[EMAIL PROTECTED]> cc Subject [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net) Hi group, Last week I created a new site http://epfwiki.net with the Wiki technology that was donated by LogicaCMG and that is currently under Eclipse Legal Review. The trigger for creating this site is the translation effort, but of course it can also host regular weekly builds of published sites that can be downloaded from http://www.eclipse.org/epf. I like to consider this site an unofficial EPF community site, sponsored by LogicaCMG, created using software that will eventually be EPF software, after a positive Eclipse Legal Review. There is also a demo site http://demo.epfwiki.net with a demo account [EMAIL PROTECTED] with password demo where you can try out this technology. An interesting was raised by Ricardo while we were discussing use of it for the translation effort: how Wikis can be accepted as a means of contributing as expected by the Eclipse organization. Of course this is an unofficial site but it would be nice if contributions made there would also be recognized by the Eclipse organization, similar to Bugzilla and the official discussions lists. I think there are a number of approaches to this interesting issue. I like to present what I think is a pragmatic approach: send every Wiki contribution to the epf-dev mailing list. We could do this real-time or send a daily, weekly or even monthly report. Do you think this is a viable option, good approach? If we think it is, I like to ask the committers to make a decision on it and maybe put it to a vote? Best Regards, Onno Onno van der Straaten Consultant _________________________________________ LogicaCMG P.O. Box 187 The Netherlands T: +31 (0)70 30 29 302 M: +31 (0)6 481 03 483 www.logicacmg.com This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________ epf-dev mailing list [EMAIL PROTECTED] https://dev.eclipse.org/mailman/listinfo/epf-dev _______________________________________________ epf-dev mailing list [EMAIL PROTECTED] https://dev.eclipse.org/mailman/listinfo/epf-dev _______________________________________________ epf-dev mailing list [EMAIL PROTECTED] https://dev.eclipse.org/mailman/listinfo/epf-dev _______________________________________________ epf-dev mailing list [EMAIL PROTECTED] https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________ epf-dev mailing list [EMAIL PROTECTED] https://dev.eclipse.org/mailman/listinfo/epf-dev
