Re: [aperi-dev] WANTED: Ideas for Aperi

[Chris King <chriskng@xxxxxxxxxx>]

Some ideas for the Aperi documentation/online help:

- Convert source files for the Aperi user's guide and online help to the Darwin Information Typing Architecture (DITA) format. This format will enable committers to more easily make changes to Aperi source documentation and generate their own output formats.

- Convert existing JavaHelp-based help system to an Eclipse-based help system. Performing this conversion will remove Aperi's reliance on jh.jar and better integrate into the RCP framework.

- Develop and document the procedure for contributing documentation to Aperi using XML DITA as source.

DITA is an open-source initiative for creating XML-based documentation. You can find out more about the DITA open-source standard initiative at
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita

_________________

Chris King
IBM Information Development - TPC, Aperi
512.687.5166 / Tie line: 273.5547
chriskng@xxxxxxxxxx
TPC InfoCenter: http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp
TPC website: http://www-03.ibm.com/servers/storage/software/center/index.html
Aperi: http://www.eclipse.org/aperi/index.php

Tom Guinane/San Jose/IBM@IBMUS

Tom Guinane/San Jose/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

08/27/2007 04:41 PM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To	aperi-dev@xxxxxxxxxxx, aperi-news@xxxxxxxxxxx
cc
Subject	[aperi-dev] WANTED: Ideas for Aperi

Hello, 
Just a reminder that we are still taking input in order to update the Aperi road map.  What would you like to see changed/updated in Aperi?  What suggestions for improvement do you have?  This is the time to get your ideas and thoughts into the discussion.  We will start to prioritize what has been submitted so far on Thursday.  So, please create an enhancement Bugzilla or respond to this mailing list with your suggestions for future Aperi work!     

Key links: 
Existing roadmap:                 http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf 
Release planning input:                 http://wiki.eclipse.org/Release_Planning 
Road map update timeline:         http://wiki.eclipse.org/Road_map_update_timeline 
Enter a requirement via Bugzilla: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Aperi&bug_severity=enhancement 
Requirements Process:                 http://wiki.eclipse.org/Requirements_Process 


Cheers,   Tom
___________________________________________
Tom Guinane     Aperi Project Lead     IBM ARC     408-927-2104     guinane@xxxxxxxxxx     http://www.eclipse.org/aperi/ 
----- Forwarded by Tom Guinane/San Jose/IBM on 08/27/2007 02:25 PM -----

Tom Guinane/San Jose/IBM

08/15/2007 11:34 PM

To	aperi-dev@xxxxxxxxxxx, aperi-news@xxxxxxxxxxx
cc
Subject	Requirements processing and road map planning

It has been about a year since we have updated our Aperi Technical Roadmap and we have successfully delivered several point releases based on it.  Now it is time to set our direction for the next year or so.  I would like to start this by collecting requirements from the community so we can build our road map content.  In order to kick this off, I have created a strawman requirements process in our wiki: http://wiki.eclipse.org/Requirements_Process.   
  
At Thursday's Aperi Community meeting, we will be reviewing this process and starting down the path to update the roadmap.  For those of you attending the call, please take a look at this process prior to the meeting.   

Thank you. 

Cheers,   Tom
___________________________________________
Tom Guinane     Aperi Project Lead     IBM ARC     408-927-2104     guinane@xxxxxxxxxx     http://www.eclipse.org/aperi/_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev