Way2Xnet
From Tribalradix
Contents |
roadmap
to have sucessful roadmap you need to know a lot of diffrent fact. Your Goal, your vehicle and your actual position.
version I
Milestone I
abstract: creating a running instance of xnet for all active espians members
concret:
having a webinterface for issuing tasks userobject with all possible contactdetails pecusystem with a way for issuing and earning pecus reports via irc/jabber/mail
Milestone II
abstract: intergrating the calendar module
concret:
having a webinterface for making dates an importtool for importing dates via caldav/ics
Milestone III
abstract: intergrating the changerulesystem for the constition
concret:
having a website for requesting changerules having a votingsystem via irc/web/jabber/phone binding voting into the quality assurance for task
pecu system
within this timeperiod espians can issue tasks and dedicate pecus to it.
when the period ends is payday
all successful done task will counted as finished
the taskdoer gets the amount of issued pecus.
quality insurance
vote
we have diffrent kinds of votes. mainly we do decisionmaking by the pecu system. we also have some personal deligated voting system. this means that you can deligate your vote or pecus to a entitie / member in a specific context.
protocol view
faq:
Q:How do i create a task? A:You go to the xnet an use the create task service. description of the task is the only necessary field.
Q:What means "TaskIssuer"? A:This is the person that creates a task. He decides mainly about the successful fullfillment of a task, who can lead the fullfillment of the task..
Q:What means "TaskFunders"? A:This is the group of people which spends some pecus on the task.
Q:What means "TaskLeader"? A:Its the person who was accepted by the TaskIssuer to fullfill the task. He can split it down into smaller Tasks. He is repsonsible for the task.
Q:What is an actice or inactive task. A:Active means that already people working on it. There is already a taskleader responsible. Inactive means there is noone taking care of the task.
Q:How can i subscribe myself to a inactive task? A:You add a task to a your personal tasklist. The TaskIssuer and the Taskfunders gets notice about it. If the TaskIssuer agrees that you are a qualified person to do the task then this is active in your personal tasklist and you are the Taskleader. So the responsibility for fullfilling the task lies in your hand.
Q:How can i subscribe myself to a active task? A:You add a task to a your personal tasklist. The Taskleader gets notice about it. If he agrees that you are a qualified person to help him with the task, he can split the task into subtask and make give a subtask. for this he can split pecus which were funded for the maintask into subtask
Q:How is the Quality assured? A:After a task is done all sponsors can vote how a task is done. time, quality, sustainibility, reusability, amount of resources. this result in combination with the amount of issued pesus goes into a quality matrix.
bootstrap process
at the beginning all active espians get a fixed amount (3000pcs) to their issuing account. the first timeperiod starts on ???? an ends at ????
we tried to have a running xnet ontop of our kalati codebase but we failed on that.
our actual status is that we implemented the xnet on pen and paper. and reduced the features rapidly.
we we now have is a writable, some pens, forms, bluetack and some initial content.
the project to manage is 24weeks. which contains of three parts.
1. creating and using the rich mix riva. which is a 200 square meter office space in london and we will transform it into a riva. we want to create a real-world-user-interface-mockup of an espra enabled collaboration nexus. 2. 24weeks.com that should be the door to espra via the internet. at this url we will give access to the espian xnet-instance. 3. create a public instance of xnet at espra.com and create the organisation which is using and promoting this service everywhere and to everywhom who is intrested of using esprasoftware and espraservice for their and our worlds better.
version 2
current stage
goals: I (already involved people): it should give us a base where we can start from. O (other people): giving them the possibilities to get in contact with us and each other
- wiki empty (wiki.espians.com)
- blog not setup
- a shitty static website (24weeks.com)
- photos (gahr.info)
- radio shows (audioblog.c-base.org)
- svn
resources and things to do? questions:
next step
goals:
I (already involved people): we should bring the resources we have so far together and allow ourselves and everybody else to get an overview about our current stage and to increase and comment on it.
O (other people): attract other people by our ideas and concepts and to join / sponsor / invest into the goal of creating the service/software espra
- filling wiki with:
* documents about plexnet and technical architecture * 24weeks * espra business
- pimping wiki with:
* synchroedit? * design esp/24weeks? both?
- using blog
* people should report about their activities in rich mix riva * everyone who has done something about the 24 concepts within the esp context or not should announce it here
- irc
* having again a web interface to chat * pimping the irc logs to remove uninteresting messages * pimping the irc logs to summarise them
- binary
* having a place to store binaries (just ftp?)
next next step
goals: I: enable us to scale effectively without losing speed and overview. I: starting the phase of software development O: showcasing our way of working 0: giving them a smell of "espra"
- creating a simple xnet instance with:
* events (for bookings within rich mix riva) * todos (simple todo list like tadalist or remember the milk) * profiles (data about people and organisations) -- starting point for social networking * binaries (starting point for sharing files along social network) * resource management (wishlist + havelist) starting point for marketplace
this should be developed within the svn: it should take use of the concepts of plexnet according to the TAD therefore it need a lot more description of the way how it works and behaves
next next next step
goals: (IO) being prepared to build "espra"
setting up other instances of xnet and getting them to share information and communicate with each other
migrating the content from
* wiki.espians.com and other resources
last stage
- everyone who wants to create espra and use it is using xnet.
^ (sbp likes these lines, but his proposal will have Teletubbies in it. much better)
