Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add a roadmap to the wiki #533

Closed
phaidon opened this Issue Oct 12, 2012 · 14 comments

Comments

Projects
None yet
4 participants
Contributor

phaidon commented Oct 12, 2012

It would be great to have a road map in the github wiki of this project.

@Drak

Contributor

phaidon commented Oct 12, 2012

But can we add this documents or at least the links to github

Contributor

phaidon commented Oct 16, 2012

Can I add the documents to the wiki?

@ghost

ghost commented Oct 16, 2012

It might be better to just have it in the wiki, or just gdocs.

Contributor

hvorragend commented Oct 16, 2012

+1 for the wiki

----- (Sent via mobile phone) -----

Am 16.10.2012 um 19:42 schrieb Drak notifications@github.com:

It might be better to just have it in the wiki, or just gdocs.


Reply to this email directly or view it on
GitHubhttps://github.com/zikula/core/issues/533#issuecomment-9499417.

Contributor

espaan commented Oct 17, 2012

Wiki also +1

the google docs link does not show anything ?

Contributor

phaidon commented Oct 17, 2012

The google docs link link does not work for me as well. I really would like to see the roadmaps here in the github project wiki. Should I add it?

@ghost

ghost commented Oct 17, 2012

I would like to agree a roadmap first discussed in a Google Doc, then publish it.

Contributor

phaidon commented Oct 17, 2012

That sounds reasonable.

But can we publish the old roadmaps (1.2, 1.3) and this points which are already clear (doctrine2, remove dbutil, jquery, twig, ...). It helps the people to understand the direction of the project a lot.

Contributor

phaidon commented Oct 17, 2012

So what should we do?

Add the content of this document to the project wiki or add this link to the project wiki?

The roadmap seems to be very outdated. For example I think we already made the decision about twig or is still unclear?

@ghost

ghost commented Oct 17, 2012

That's my point. We should first draft and agree this in the Google Doc,
then it can be transferred to the wiki.

Owner

craigh commented Nov 23, 2012

And.... Nothing.

@ghost

ghost commented Nov 23, 2012

And I'm tempted to suggest, roadmaps are not something we really need to spend time on away from other things. For me the ticket system is quite enough, so it's really not a priority for me. Jusuff is making jQuery conversion for 1.4.0 and we can release 1.3.5 any time, soon since lots and lots of work has been done since: commit list

Now we have a 1.4 branch we can freeze any further feature commits into 1.3 and leave them for 1.4.

Historically, we've taken more to doing tickets organised by roadmap than by following a separate roadmap.

@ghost

ghost commented Sep 8, 2013

This was already added.

@ghost ghost closed this Sep 8, 2013

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment