[
https://issues.apache.org/jira/browse/COR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288704#comment-14288704
]
Dennis E. Hamilton commented on COR-17:
---------------------------------------
Maybe instead of a roadmap, we need a desired state. That is, what is the
architectural structure for Corinthia components that accounts for all of the
major pieces and any interactions/interdependencies and the boundaries (where
are the seams and interfaces).
Then these get developed out and added two (i.e., more formats, more
functionality in the common form, etc.).
I am infatuated with the Kivi documentation at the moment, and that is
influencing my reaction here. http://kivy.org/docs/
> Looking for a Roadmap
> ---------------------
>
> Key: COR-17
> URL: https://issues.apache.org/jira/browse/COR-17
> Project: Corinthia
> Issue Type: Wish
> Components: Wiki
> Environment: wiki, documentation
> Reporter: jan iversen
> Priority: Critical
>
> I think a roadmap for this project is needed. I think it belongs on the wiki
> for now, but would move to a project wiki once incubating starts. The
> milestones are mystery meat when handled on this bulletin-board style issue
> database. It will be important as context for newcomers, especially as the
> project expands
> Thoughts
> It is kind of amusing once I caught on that this GitHub issues database is
> being used as a job-jar and design notes and a way of tracking them. There is
> a lot of tacit understanding and context involved. It might be good to start
> writing these as if being addressed to strangers, so that more context is
> provided. (I may have failed that here.)
> Also, some of this is memorialized better on a Wiki, since history is handled
> better and open/closed is a pretty heavy treatment for thinking-out-loud.
> Some of these will be pretty long-lived and the milestone scheme here will
> probably need to be replaced with something more nuanced with some sort of
> living roadmap. Actually, I would give pretty high priority to a roadmap,
> however tentative it might be. One target would be toward a 1.0 release, and
> there are probably several 0.xx before that. It can be rough but a nice
> feature is that it can be a hyper-text with all the drill-down one can have
> as there is more shape to the project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
