[p2pu-dev] [p2pu-community] P2PU to infinity and beyond
Dirk Uys
dirk at p2pu.org
Wed Aug 15 08:35:12 UTC 2012
Hi Ali
Dates are a little difficult, the rabbit hole is always deeper than
anticipated and priorities shift over time :) I don't know how we can
change this?
Cheers
d
On Tue, Aug 14, 2012 at 5:44 PM, Alison Cole <alison at p2pu.org> wrote:
> Hi Dirk,
>
> This all sounds really spot on. I'd love to see dates attached to these
> priorities. Especially the collapsing of courses, which has eluded us for a
> year or so.
>
>
>
> On Mon, Aug 13, 2012 at 8:00 AM, Jessy Kate Schingler <jessy at jessykate.com>
> wrote:
>>
>> a general, wholehearted +1! i'm sure there will be lots of rich
>> discussions about the details, but very excited about this direction.
>>
>> --
>> Jessy Kate Schingler
>> http://jessykate.com
>> Sent with Sparrow
>>
>> On Monday, August 13, 2012 at 2:34 PM, Dirk Uys wrote:
>>
>> Hi everyone.
>>
>> Philipp and I had a chat about where we would like to take our platform
>> (lernanta):
>>
>> Our technology supports people who make learning happen
>>
>> Who are these mysterious folks? Broadly, they create opportunities for
>> others to learn. By the way, this doesn't mean we don't want our technology
>> to support the learners themselves, quite the contrary. We think that making
>> course builders happy is the best way to make learning awesome and everybody
>> happy.
>>
>> Most members of the core P2PU community create courses (consisting of
>> content and a group of people learning together, typically with a
>> facilitator). That model will remain our cornerstone for the foreseeable
>> future.
>>
>> But there are a million other ways that people can learn with each other
>> and we want to enable more of them. In order to do that we partner with
>> people who want to build technology that goes way beyond the course model.
>> We started making our core technology more modular to make it easier for
>> these folks to expand it, and we are planning events and outreach to grow a
>> community of technologists around P2PU.
>>
>> What this means:
>>
>> Homepage
>>
>> We want to more clearly communicate that learning at P2PU happens in many
>> different ways and that there is an amazing community of course builders and
>> innovators building this thing. In addition to featuring courses, we plan to
>> use our home page to better promote lab projects that are ready for use. We
>> will also showcase new ideas coming from the community, and make it easier
>> to get involved. P2PU.org will be your entry point to a variety of learning
>> opportunities and your pathway into the community.
>>
>> Next steps:
>>
>> Prepare a wireframe / proposal for feedback from the community.
>>
>> If you have specific ideas for this, please share them on the list for
>> discussion, or contact dirk at p2pu.org directly.
>>
>>
>> Core platform & apps
>>
>> A set of core features & services that we provide. Currently this
>> includes: Profiles, Courses, Course list, Achievements & Badges, and
>> Schools.
>>
>> Next steps:
>>
>> Improve and simplify the course experience (collapse courses, study
>> groups, challenges into one model that keeps the best features and gets rid
>> of everything else).
>>
>> Modularize the underlying architecture, so that different parts speak to
>> each other through clearly defined interfaces that can be opened up as
>> public APIs in the future.
>>
>>
>> Lab projects
>>
>> This is our space to experiment with new tools. Some built by us. Most
>> built by our awesome community. Things that work, will be more centrally
>> supported and potentially rolled into the platform. The API built by Jose,
>> Alex K's Mentoring at P2PU and the Mechanical MOOC are first examples of great
>> lab projects.
>>
>> Next steps:
>>
>> Make it easier to expand the platform: roll out the API (and expand it),
>> provide a CSS style guide that makes it easier to build lab projects with
>> the P2PU look & feel, etc.
>>
>> Any feedback is welcome!
>>
>> I'm also going through the project pipeline board
>> (https://trello.com/board/project-pipeline/4ec0f020c137ff072a5d8afa), the
>> development
>> board(https://trello.com/board/development/4f3d1ecc3a1fad867ad57e76) and the
>> Challenge Development Sprints board
>> (https://trello.com/board/challenge-development-sprints/4ed8ff4175e6467872117dcc)
>> to align them with what's going on.
>>
>> Cheers
>>
>> Dirk
>>
>> --
>> You received this message because you are subscribed to the "P2PU
>> Community" group. Please stick to the ground rules:
>> http://groups.google.com/group/p2pu-community/web/ground-rules
>>
>> Specific topics such as research, web development and course design are
>> discussed in separate working groups:
>> http://wiki.p2pu.org/mailing-lists
>>
>>
>> --
>> You received this message because you are subscribed to the "P2PU
>> Community" group. Please stick to the ground rules:
>> http://groups.google.com/group/p2pu-community/web/ground-rules
>>
>> Specific topics such as research, web development and course design are
>> discussed in separate working groups:
>> http://wiki.p2pu.org/mailing-lists
>
>
>
>
> --
>
> Alison
>
>
> --
> You received this message because you are subscribed to the "P2PU Community"
> group. Please stick to the ground rules:
> http://groups.google.com/group/p2pu-community/web/ground-rules
>
> Specific topics such as research, web development and course design are
> discussed in separate working groups:
> http://wiki.p2pu.org/mailing-lists
More information about the p2pu-dev
mailing list