Kibo's Phases

Registered by amjjawad 

Kibo for the time being is a business (profit) project. That is Phase #1.

Phase #2 when Kibo can be a company, not just a project but that is too early to talk about and think about at the moment.

This is just to be clear about the vision we have for Kibo.

Blueprint information

Status:
Not started
Approver:
amjjawad 
Priority:
High
Drafter:
amjjawad 
Direction:
Approved
Assignee:
None
Definition:
Review
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None

Related branches

Sprints

Whiteboard

[gsilvapt]

My thoughts on this:

Phase 1:
Implement our website and a twitter account that can start spamming the network about us. This way, we can confirm if Kibo's thoughts can sound appealing to the market.

Phase 2:
Develop our website to a more concrete display, to contain information in regard to ourselves, our mission, vision and purpose and also a small support section.

Phase 3 (applicable if all other do not fail):
Gather enough money from savings - through sales and projects - to create the company.

Besides, vision is what you/we want to achieve. Kibo should have an external vision. Like "we wish to show people that open source technology can be as viable as other offers".
-------------------------------------------------------------------

[amjjawad] Thank you for sharing your thoughts, Gustavo but this is totally off-topic, I'm afraid :(

What you mentioned is more like a plan and not really how this project will survive.

"Informational" blueprints usually require no further action. Yes, comments are more than welcome, for sure.

Let's keep Launchpad for the general guidelines that can be shared publicly and let's keep the planning and strategy somewhere else ;) maybe Terllo? :D
-------------------------------------------------------------------

[gsilvapt]

I understand that although I think we have to plan and put deadlines to ourselves in order to keep work flow in order.
Planing ahead is crucial. Thought this was the right thread.
-------------------------------------------------------------------

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.