Project roadmap... is it required to start? does trello provide this?
I think Trello would cover the roadmap, at least in the early stages. Once the project gets bigger, it might be important to say "This is our plan. We will do this step next and deliver it by this date." But, I don't think that's important right now.
Would you consider the GetMarked project as part of the core of Bitmark? Or is it a separate project/application built on top of the Bitmark technology? If it's not part of the core, I would split it out more on the website. It is weaved very close to the core Bitmark information. I would categorize it under the 3rd party software, or possibly under a new "official software" category. Since I imagine more projects will be built later, I would hate to see the core Bitmark information get lost in the sea of other Bitmark projects.
We will have a more formal project overview and roadmap soon, Medic is working on that.
Your getMarked question is very pertinent and we must make this clear. From the new OP, it is described as follows
Project BitmarkProject Bitmark is an initiative to create an every day use alternative currency.
- A stable and balanced cryptographic currency named Bitmark
- A massive adoption programme under the banner of Marking
Bitmark is the core cryptographic currency, it's primary objectives are to be safe, secure, fast, actively developed, and easy to integrate for services and adopters.
read moreMarking is a novel adoption initiative which enables every day people to use cryptographic currency in every aspect of their lives.
read more
Under the banner of 'Bitmark' comes the standard client, api stuff, block explorers, mining, tools to use the block chain, and all the normal crypto currency things we see.
Under the banner of 'Marking' comes everything to do with wide spread user/service/business adoption and it is our primary focus. I encourage every one who hasn't to read
the Marking document which details every aspect of how we will approach wide spread adoption.
The adoption side feeds requirements back in to Bitmark as time progresses, and Bitmark development will be responsive to the requirements of the varied user base provided by Marking.
I seek to refine and clarify this description further until such a time that it is no longer needed.