Drumbeat/p2pu/courses/wikiwysiwyg: Difference between revisions

(Created page with '= WikiWYSIWYG = == Who Are You? == Jordan McManus == Can you lead this course in September 2010 or is this a general concept? == This is not a course per se. Anyone is invi…')
 
 
(27 intermediate revisions by the same user not shown)
Line 8: Line 8:


This is not a course per se. Anyone is invited to have a look-see and hack away at it.
This is not a course per se. Anyone is invited to have a look-see and hack away at it.
So yes, it is several general concepts:
This is targetted at '''''new users''''' not experienced developers. The goal is to give new users access to high class code (or tools) and and let them create what they want with it.
1. Learning takes the time it takes.
During a course, you need to synchronize your time with your teacher's time, but there aren't any deadlines in the WikiWYSIWYG.
2. Don't be afraid to make mistakes.
You should rush to make your first 100 mistakes (you won't understand much until then) - adapted from a go proverb.


'''ToDO''' - link to The Course Of All Courses on P2PU
'''ToDO''' - link to The Course Of All Courses on P2PU
Line 13: Line 25:
== What's The Major Project? ==
== What's The Major Project? ==


At the moment, WikiWYSIWYG looks like one big soup and I don't really know what it's going to taste like. It's an Open soup, and your feedback is what's going to make this taste good.
The project is WikiWYSIWYG. (I think the following description is too long)


In order to understand this, several things must be considered at the same time.
The word WikiWYSIWYG is a portmanteau for Wiki and WYSIWYG.


1. There is probably not enough space on the server side to accommodate
Wiki = short for wikiwiki which means speedy in Hawaiian (according to Wiktionary)
all user modifications to all projects that will be hosted in the WikiWYSIWYG.


2. We can publish an Open platform that could be run inside a virtual machine on every computer (there is a lot of open source development on VMs).
WYSIWYG = What You See Is What You Get, which is a web paradigm that will be generalized to all aspects of your learning experience (not just web design).


3. This limits the entry point to installing a virtual machine (which we will explain). Or even better we can probably use an existing linux distribution (the virtual machine is only to accommodate everyone without forcing them on a particular platform).
Here, you will be able to learn a new programming (Open Web Development) language via an interactive wiki that has been collaboratively created. (Jason Kealey, personal communication)


4. Anytime a project reaches a milestone, we can publish the VM which will let any user: tinker with it on his own machine using his ever increasing knowledge without fear of breaking anything (in fact, breaking is encouraged)
It is a platform that lets new users give feedback in order to organize knowledge that is not yet understood by them in a way that will make it easy for them to learn. But mostly it's about making your life as easy as possible in order to learn Open Web Concepts.


5. VM's can be downloaded via Metalinks (BitTorrent)
At the moment, WikiWYSIWYG looks like one big soup and I don't really know what it's going to taste like. It's an Open soup, and your feedback is what's going to make this taste good.


6. Lazy downloading. This will probably become huge fast. So we need a mechanism to let users only download what they want/need to play with.
For example, let's say you wanted to build a site like this one (wiki.mozilla.org, but the same goes for WikiWYSIWYG), but you didn't know how to. The goal would be to provide you with step by step instruction on how this site was built. You will be able to see all its details for yourself or make it yourself or learn to compile the programs used to make it or learn what "website" means.


7. There's going to have to be a CVS type module attached also (which will be explained)
In essence, we will be trying to merge all parts of Open Web Development cycles (requirements, documentation, actual code, test cases, tutorials, use cases, etc.) in one interactive medium.


8. Batteries included (new form of releasing that I see in Python projects)
We don't have this yet, because we don't know how you learn and we don't know how to teach this to you (emphasis on "to you", there are plenty of great teachers who know how to teach). This is where the community effort comes in, you tell us how you want to learn this, and we'll try our best to accommodate you.


== What you should know  ==
== What you should know  ==


You reached this place, you know enough.
You reached this place, you know enough (please don't be afraid of big words).
 
No one knows everything.


== What you can expect to learn  ==
== What you can expect to learn  ==


What you want to learn.
What you want/need to learn.


== What you might learn if you work hard  ==
== What you might learn if you work hard  ==
Line 46: Line 59:
What the future has in store for us.
What the future has in store for us.


== Things we won't cover  ==
== Things we will cover  ==


The goal is to cover every possible way a new user can learn Open Web Concepts.
The goal is to cover every possible way a new user can learn Open Web concepts (the WikiWYSIWYG will evolve with the learning experiences).


== What will I build?  ==
== What will I build?  ==
Line 64: Line 77:
== Hey! I need help! ==
== Hey! I need help! ==


I need help. I honestly don't know what I'm doing.
I need help. I honestly don't know what I'm doing nor why I have these ideas...


Please be advised that I "judge" help based on ego (or lack of it). The more ego I smell in your help, the less chance it has of getting in here.
I will start searching the web for open courseware on what is being discussed in the talk page.


[[Drumbeat/p2pu/courses|Back to the Course List]]
[[Drumbeat/p2pu/courses|Back to the Course List]]
111

edits