Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epf-dev] add page in epf wiki 
Onno,
for my client I have a similar use case as you indicated below. We want to use the EPF Wiki for both, the collaborative improvement of the method and to document project specific amendments. So even if I frequently harvest the changes, I will spare the project specific ones as they do not belong in my common method. So yes, I would support the usefulness of updatability of the tree structure.
I addition I think Han Mei only touched the tip of the iceberg. The Wiki by its nature does not enforce integrity of the method. So changes in Resource relationships need to be manually cross-linked, changes/addition in disciplines or any other category need to be manually reflected in overview pages (and possibly the tree structure).
In case you amend the EPF Wiki would it be your plan to simply make the tree structure editable, or would you plan to find means to automatically update the tree? I am not sure if this is even possible, as the tree structure can be customized in the EPF Composer and therefore is method specific. 

Rgds.
GES

Onno van der Straaten wrote:

Hi Han Mei,
That is not possible I'm afraid. My feeling is that to make it effective you should do frequent round-trips between EPF Wiki and Composer as I tried to depict here <http://epf.eclipse.org/images/epfwiki_infra_overview.jpg>. Use the Wiki technology for collaboratively authoring, reviewing, enhancing content with a larger group especially when that groups consists of people that don't have access to EPF composer and/or the process asset library or don't have EPF knowledge/experience.
The moment you realize you need a new content element you could decide to create it in the Wiki first, share it with coworkers and in this way quickly and collaboratively gather, elaborate the content for it but soon after that you also add it to the process asset library using Composer to (re)model relationships, depedencies and then (re)publish.
It depends however on the situation I think. I can imagine situations where you don't need/want round-trips often or at all. For example when a process description (specific Wiki) is to support a specific project. You can use it to add guidance or to make existing guidance/content more specific for the project. At project close down you can then review all changes, additions and then maybe decide to harvest some it. in that case it would be nice to be able to change the navigator links. 

If there is enough interest in such a feature, I'm willing to implement it.
Best Regards,
Onno
On Wed, Jan 12, 2011 at 9:41 AM, 梅韩 <hanmei@xxxxxxxxxxxx <mailto:hanmei@xxxxxxxxxxxx>> wrote: 

    hello Onno,
I successfully installed epfwiki on the server now I wondered is there any way to customize the tree view in epf wiki. 
    I added some pages in the epf wiki, I want them to show in the left bar
    how to do it ?
    thank you !
-- Han, Mei GSegment Space Technologies, Inc. Phone: +86-10-57151257 
     Room 1007, Tower 1, HuiHuangGuoJi Plaza,   Skype: hanmei_gsegment
No.10 Shangdi Street, Haidian District, Email: hanmei@xxxxxxxxxxxx <mailto:hanmei@xxxxxxxxxxxx> Beijing, PR China Web: http://www.GSegment.com <http://www.gsegment.com/> 


    _______________________________________________
    epf-dev mailing list
    epf-dev@xxxxxxxxxxx <mailto: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

Back to the top