[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [epf-dev] EPF Wiki applied fixes
|
I think you mentioned a good point about
the translation.
Once we have the method content translated,
it's a good time to harvest the content in EPF Composer and publish again
- that would be a "alpha" that we can post on the Wiki as new
baseline, then run some tests and do more translation on the process side
as needed.
Ricardo Balduino
Senior Software Engineer
IBM Rational Software (www.ibm.com/rational)
Eclipse Process Framework (www.eclipse.org/epf)
"Straaten, Onno van
der" <onno.van.der.straaten@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
04/17/2007 06:12 AM
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
To
| "Eclipse Process Framework Project
Developers List" <epf-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [epf-dev] EPF Wiki applied fixes |
|
Editing the WBS type pages
(with an expandable tree structure) will not really work, even if you only
change text, the layout will change. I don’t know why this happens yet,
I guess this has to do with the amount of _javascript_/advanced HTML that
is used in those pages. I agree it should be possible to edit texts.
For the translation effort
a two step approach makes sense, I think: first method content then processes.
After the translation of the method content, we could update the plug-in
and establish a new baseline process. This will translate part of the processes
as properties are inherited from the method content? What remains can then
be translated using the Wiki.
Best Regards,
Onno
From: epf-dev-bounces@xxxxxxxxxxx
[mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Ricardo Balduino
Sent: vrijdag 13 april 2007 21:39
To: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] EPF Wiki applied fixes
Onno, thanks for the fixes.
Re: your question about editing process content, there can be text in the
process elements that could be changed, added or translated.
As for editing information in the WBS, if one wants to change the name
of a task descriptor, for example, that should be something allowed. Now
I wonder if other types of authoring are needed on the Wiki, such as selecting
steps on a task descriptor, defining sequencing of activities, drawing
diagrams, etc. I think that is specialized functionality for the type of
tool like EPF Composer... or I am wrong?
What do others think?
Ricardo Balduino
Senior Software Engineer
IBM Rational Software (www.ibm.com/rational)
Eclipse Process Framework (www.eclipse.org/epf)
"Straaten, Onno van
der" <onno.van.der.straaten@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
04/13/2007 06:25 AM
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
To
| "Eclipse Process Framework
Project Developers List" <epf-dev@xxxxxxxxxxx>, <epf-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| [epf-dev] EPF Wiki applied fixes |
|
Hi everyone,
Thanks for all the feedback and pointers for improvements.
I improved FireFox/TinyMCE support:
- checkin, checkout notes: didnt' work because
some conflict with contentpage.js (of EPF) and the TinyMCE library.
- image maps: changed TinyMCE configuration
to the Full XHTML rule set (thanks
to Denis Beskov-Doronin for pointing out
the solution)
- mysterious text appearing at the top of page
after editing: also solved with the TinyMCE config setting.
With
regards to comments in other languages: currently there is no support for
multiple languages. It might be usefull to add this: for instance this
would allow you to post a question, comment and specify the language. And
then, with a user preference, you would be able to specifiy the language
of your choice or none. So I think for now we should allow it, and then
in the future add language support to filter out what you don't want to
see. I have added this to my growing list of features that I like to add.
Another note: editing process content
still doesn't work very well. I think it doesn't make sense to use to edit
processes using the Wiki? In order of 'decreasing' suitability you would
use the edit functionality of the Wiki for:
- authoring method content (including main
elements: tasks, roles, work products)
- adding links
- adding guidance (new method content)
And
never for processes?
Comments are fine anytime, anyplace, I think.
I enabled a feature that allows you to compare
baselines processes. As an example I compared two weekly builds, see http://www.epfwiki.net/difference_analyses/show/1.
If you access the information of a baseline process, it shows the diffs
that apply to that baseline process, see for instance http://www.epfwiki.net/sites/show/8.
You can download the diff in csv format by clicking on csv icon. If you
are Windows it will open in MS Excel. Now that this info is available with
the next revision of the site I will add this info to the info on a page
(edit/info link).
Best Regards,
Onno
Van: epf-dev-bounces@xxxxxxxxxxx
namens Jim Ruehlin
Verzonden: do 12-4-2007 20:01
Aan: epf-dev@xxxxxxxxxxx
Onderwerp: RE: [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net)
I use Firefox 2.0.0.1. The only problem I’ve had is that I can’t add
a comment when I check-in or check-out a page for editing. Otherwise it
seems to work great.
I think baseline changes and full text search would be the most useful
items on the list, although they all look like good things to do. Sending
out an update to epf-dev actually may be the most important, but it looks
like that one’s pretty easy to do.
Thanks,
Jim
____________________
Jim Ruehlin, IBM Rational
RUP Content Developer
Eclipse Process Framework (EPF) Committer www.eclipse.org/epf
email: jruehlin@xxxxxxxxxx
phone: 760.505.3232
fax: 949.369.0720
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ricardo Balduino/Cupertino/IBM
Sent: Thursday, April 12, 2007 10:14 AM
To: epf-dev@xxxxxxxxxxx
Subject: RE: [epf-dev] EPF Wiki and contributing through a Wiki (epfwiki.net)
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" <onno.van.der.straaten@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
04/11/2007 11:28 PM
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
To
| <epf-dev@xxxxxxxxxxx>
|
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
New Comments
New Users
Allan Halme, takai, zalkind, Ronaldo
Luiz, tom weinberger, Paulo Moreira, Calen Legaspi, Aitor, hopeshared,
Onno
Checkouts
Generated on: Wed Apr 11 10:43:05
-0700 2007
Showing changes since: Mon Mar 12 10:43:05 -0700 2007
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
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/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx
04/03/2007 05:00 PM
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
To
| epf-dev@xxxxxxxxxxx
|
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: jruehlin@xxxxxxxxxx
phone: 760.505.3232
fax: 949.369.0720
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ricardo Balduino/Cupertino/IBM
Sent: Tuesday, April 03, 2007 1:51 PM
To: epf-dev@xxxxxxxxxxx
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"
<onno.van.der.straaten@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
04/03/2007 01:40 AM
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
To
| <epf-dev@xxxxxxxxxxx>
|
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 demo@xxxxxxxxxxx
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
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev