Introduction, overview, general approach?

Asked by Jens Koeplinger on 2013-02-17

Hi Max - thanks for getting this forum started. In order for beginning to understand what you are attempting to accomplish, I would be interested in some kind of introduction, overview, or something outlining the general approach you are envisioning. Maybe you want to give a brief presentation or overview in person to a few of us?

Question information

Language:
English Edit question
Status:
Solved
For:
Winterize Edit question
Assignee:
No assignee Edit question
Solved by:
Jens Koeplinger
Solved:
2013-02-19
Last query:
2013-02-19
Last reply:
2013-02-19
Max Polk (maxpolk) said : #1

The project was just started and is very fuzzy until it begins to take shape and have more clear boundaries. Over the course of time specific approaches will be chosen. Until then, there exist mostly hints of the direction.

The first thing is to go through the public archive of the mailing list -- https://lists.launchpad.net/winterize-users/

Then look at the blueprints which are the features that are desired -- https://blueprints.launchpad.net/winterize

Notice the work items at the bottom of each blueprint, the marching orders to fulfill the blueprint in a format Launchpad defines.

One blueprint is the Franklin Street statement which enumerate the core principles of the project (make sure you take the 'Read the full specification' link) to read the original. Some of its work items are thinking about deployment, working with user data, thinking about the finished product and free network services, and so forth. How exactly can these principles materialize in a wiki?

Another blueprint is the toy app server which uses no special setup beyond what a recent Linux distribution (Ubuntu 12.10) provides in the package repository. Getting an early server to toy with during development will be a great help to know what direction will be best for the final choice of application server. Simple servers like Bottle allow spontaneous instances to exist for the life of a meeting where you want to share information, but it can be hooked in as the backend of high-performance web servers that reverse proxy the content. The key work item left is envisioning an extensibility scheme, where the project overview talks about decentralization, answering questions like how one page could refer to another neatly, and what design could possibly make it work.

I could have perhaps waited until I have more to present to everyone, where people can take tasks and start exploring, but I wanted to gain early visibility at the risk of being too nebulous for a few months.

Jens Koeplinger (jens-prisage) said : #2

Ok, thanks for pointing to the references. I'll read and hang tight otherwise.