[p2pu-dev] disscusion about lernanta's workflow on the irc
Alison Jean Cole
alisonjean.cole at gmail.com
Thu Feb 3 19:46:27 UTC 2011
+1 for P's suggestions
ALISON
p2pu.org/users/alison
On Thu, Feb 3, 2011 at 1:36 AM, Philipp Schmidt <philipp at p2pu.org> wrote:
> I've finally had time to look at some of this in more detail:
>
> https://github.com/p2pu/lernanta/wiki/Lernanta-Workflow
>
> I wonder if it's possible to start with an even simpler design to get
> started. The least complex solution I can imagine.
>
> 1 - I create a group/course
>
> 2 - I manage the process of people joining me (both as co-creators or
> as peer learners) over time
> * anyone can join freely at any time
> * people apply, and i approve/deny them
> * nobody can join
>
> 3 - I collaborate with the people in the group, working through the
> learning structure I created
>
> Everything is always public
>
> I think a lot of the complexity can be managed through good help text
> and design. Adding additional features (fixed start dates that trigger
> certain things to happen, cloning at various stages, public/private
> options) *might* be needed later, but each additional feature creates
> more structure, and it will be hard to design down again once we have
> built the complexity.
>
> P
>
> On 29 January 2011 01:53, zuzel.vp <zuzel.vp at gmail.com> wrote:
> > Hi,
> >
> > I started working on the summary. You can see the first part here:
> > https://github.com/p2pu/lernanta/wiki/Lernanta-Workflow and start
> > improving it. I still have to include the parts about how to run a
> > course, accept participants applications, decide that the course is
> > full, start running the course (full or not), ...
> >
> > Marielle and Nigel:
> >
> > If there is a task you will prefer to work on I will said that you
> > should go ahead (though notice that my vote is small because I am new
> > here :D ). At least if it is a small or simple task it will not cause
> > to many problems to duplicate work, and in fact we will be learning
> > and then be able to review each other work. The ideal result will be
> > that the task will be completed soon, and we will be able to produce
> > the nice solution by seeing each others work.
> >
> > --
> > Thanks,
> > Zuzel
> >
> > On Fri, Jan 28, 2011 at 11:46 AM, Marielle Volz <marielle.volz at gmail.com>
> wrote:
> >> Um. So, nigelp alreadly claimed that exact n00b task on irc, about 15
> >> minutes before I went to claim it on IRC. So I've been letting him
> >> work on it. I think we need a better system.
> >>
> >> On Fri, Jan 28, 2011 at 10:42 AM, Jessy Kate <
> jessy.cowansharp at gmail.com> wrote:
> >>> zuzel, thanks for doing this-- and for offering to do the summary!
> >>>
> >>> On Fri, Jan 28, 2011 at 10:38 AM, zuzel.vp <zuzel.vp at gmail.com> wrote:
> >>>>
> >>>> http://pastie.org/1506054
> >>>>
> >>>> In case you want to read the long version. It will be summarized in
> >>>> the wiki (later today).
> >>>>
> >>>> --
> >>>> Thanks,
> >>>> Zuzel
> >>>> _______________________________________________
> >>>> p2pu-dev mailing list
> >>>> p2pu-dev at lists.p2pu.org
> >>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
> >>>
> >>>
> >>>
> >>> --
> >>> Jessy Cowan-Sharp
> >>> http://jessykate.com
> >>>
> >>>
> >>> _______________________________________________
> >>> p2pu-dev mailing list
> >>> p2pu-dev at lists.p2pu.org
> >>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
> >>>
> >>>
> >> _______________________________________________
> >> p2pu-dev mailing list
> >> p2pu-dev at lists.p2pu.org
> >> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
> >>
> > _______________________________________________
> > p2pu-dev mailing list
> > p2pu-dev at lists.p2pu.org
> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
> >
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110203/b7462062/attachment-0001.html>
More information about the p2pu-dev
mailing list