[p2pu-dev] New List

Jessy Kate jessy.cowansharp at gmail.com
Thu Jan 27 17:04:41 UTC 2011


yes i'd say it's a bit of triage. i think maybe what's not clear is that
this is actually OSUOSL's mailman instance, so we are not managing it
ourselves. also, the current site is being maintained by essentially a
distinct group with a different skillset/interest set than those building
the new site. the balance between maintaining/improving the current site
(and the time we as a community put into that) while building the new one is
admittedly tricky.

while certain things are definitely higher priority, they will also take a
bit longer. meanwhile, OSUOSL has a lot of these services already running
and so can stand them up for us easily.

FWIW, this particular change actually WAS motivated by user experience,
because with mailman we can generate as many lists as we want, generate them
programmatically (for courses)/interact with them programmatically, control
the archives, etc.

Additionally, mailman is a tool we are considering building into the backend
of the new platform as a way to integrate forums/comments and email, which
(as you point out) would be a huge improvement. So, this is a way we can
start using it more and see how people feel about it.

but, i do agree we could do better at prioritizing, and it's one thing we're
hoping pivotal tracker will help us do by having a clear, authoritative
list.

hope that helps somewhat! additional ideas welcome.
jessy


On Thu, Jan 27, 2011 at 11:54 AM, Alison Jean Cole <
alisonjean.cole at gmail.com> wrote:

> Hi Dan,
>
> It may seem that higher priority tasks may be taking a back seat to less
> important changes. This is not really the case. Because this is volunteer
> driven project and anyone can volunteer to take on different tasks,
> completion of tasks and projects varies greatly. It is the nature of a
> volunteer community.
>
> The changes you identify as crucial are definitely among the dev-list's top
> priorities, but require more time and effort, consensus and usually some
> money if it requires long hours.
>
> John volunteered to make lists.p2pu.org happen and is not necessarily
> working on user experience with the current site.
>
> ALISON
> p2pu.org/users/alison
>
>
>
>
>
> On Thu, Jan 27, 2011 at 8:44 AM, Dan Diebolt <dandiebolt at gmail.com> wrote:
>
>> Just out of curiosity what is the motivation for prioritizing moving the
>> dev list to the domain p2pu.og? It is great to have dev email integrated and
>> under your control in the P2PU domain but now you bear the full burden of
>> keeping this service up 24/7 (cf etherpad uptime). It seems to me that
>> integrating course communications into the platform would be a higher
>> priority and the bigger challenge. Right now there is a fairly high burden
>> put on course organizers to manually create their own Google Groups or other
>> communication channels and get them populated with members who have already
>> gone through one registration with P2PU. What I am finding is that if you
>> use a Google Group a significant number of people want to receive their
>> email via a more convenient gmail account even though they registered with a
>> non-gmail account with P2PU. And the whole process of registering with
>> another service takes a day or to to complete adding unplanned delay and
>> comes with a range of unexpected issues (email spam filters, lost invites,
>> Google imposed limitations, etc).
>>
>> I think there is a very good analogy you can make to considering a member
>> as a packet which has to be routed from  a starting node (registration with
>> P2PU) to a destination node (successfully getting setup and engaged in the
>> selected course). But the key point is that these packets have a very small
>> number of hops before they die (member abandons additional registration
>> steps or actions). The time to live is perhaps as low as one or two hops.
>>
>> I think this is one of the biggest challenges you have to grow: providing
>> a better signup experience and a seamless integration of course
>> communications and resources into the platform.
>>
>>
>>
>> On Thu, Jan 27, 2011 at 11:21 AM, John Britton <public at johndbritton.com>wrote:
>>
>>> I'm already working on moving the archives over. OSUOSL is helping out.
>>>
>>> --
>>> contact info:
>>> http://www.johndbritton.com
>>> @johndbritton - http://twitter.com/johndbritton
>>>
>>>
>>> On Thu, Jan 27, 2011 at 11:01 AM, ॥ स्वक्ष ॥ <vid at svaksha.com> wrote:
>>>
>>>> On Thu, Jan 27, 2011 at 15:39, Stian Håklev <shaklev at gmail.com> wrote:
>>>> > Someone should change the user in tracker.p2pu.org, so new
>>>> notifications
>>>> > also end up on the new dev-list. Not sure if there are other places we
>>>> > should change it.
>>>>
>>>> I updated this page, https://github.com/p2pu/lernanta/wiki
>>>>
>>>> > I guess we should close the old dev-list for contributions, but keep
>>>> it
>>>> > around as an archive.
>>>>
>>>> I'm not aware of Googlegroups archive provisions but if its possible
>>>> to get the archives in an mbox format then all the archives can be
>>>> moved to the mailman list:
>>>> http://wiki.list.org/pages/viewpage.action?pageId=4030624
>>>>
>>>> hth,
>>>> --
>>>> Regards,
>>>> vid ॥ http://svaksha.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
>
>


-- 
Jessy Cowan-Sharp
http://jessykate.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110127/0e55789e/attachment-0001.html>


More information about the p2pu-dev mailing list