[p2pu-dev] p2pu notifications not being sent

Fri Jun 1 07:25:37 UTC 2012

I like the way this conversation is going! We should definitely have a
discussion about the development priorities! As soon as John gets back
we'll schedule a time to talk about it, maybe during the weekly tech
call that happens on Wednesdays at 14:00 UTC?

Maybe we can have a hackathon some time? We can focus on a specific
area of functionality like site notifications, CSS or UX for example.

The grad student idea is also a good idea! Maybe we can also
participate in programs like "Google Summer of Code"?

Cheers
d

On Thu, May 31, 2012 at 6:00 PM, Jessy Kate Schingler
<jessy at jessykate.com> wrote:
> stian we just talked about your exact points on the community call.
>
> it's always a longer conversation to set big high level dev priorities and i
> haven't been involved in that lately myself, but on the call we were
> recognizing that a lot of functionality has been discussed and wished for
> around notifications, that we haven't gotten to yet. and that it would be
> nice to have a time to discuss and think about what dev priorities could be
> around notifications and understand what the competiting priorities are (as
> there are always many).
>
> i don't know how/where dev priorities are currently being set or when jon
> gets back from vacation, but perhaps we could set aside a time to discuss
> this in that context, or on the community call if that is better? thoughts?
>
> on a related note, this also makes me think about what we could do to build
> up a more active developer community around lernanta, since no matter how
> heroic dirk might be, there will always be more than he can do just himself!
> one thing that came to mind is trying to get more researchers and grad
> students contributing, which would get them more involved in creating
> features that work for them, and they could also do research measuring the
> effectiveness of the new features (eg. a paper showing participation metrics
> before and after two-way email integration). just a thought.
>
> jessy
>
>
>
>
>
> On Thu, May 31, 2012 at 8:44 AM, Alison Cole <alison at p2pu.org> wrote:
>>
>> My inbox exploded. I got 79 messages. Today will be a long day of catching
>> up.
>>
>> Thanks Jessy for catching and Dirk for fixing!
>>
>>
>> On Thu, May 31, 2012 at 8:18 AM, Stian Håklev <shaklev at gmail.com> wrote:
>>>
>>> Ah, that's why I suddenly got lots of notifications, I was wondering at
>>> the explosion of activity! :)
>>>
>>> However this raises three other issues, in increasing importance:
>>>
>>> 1. The title of the group is still weirdly formatted: The
>>> Researchers' Homestead
>>>
>>> 2. Could we clean up the formatting? Is there a reason why the person's
>>> name is not in the "from" field instead of "no-reply"? Do we need all the
>>> boiler plate at the top of the message:
>>>
>>> --
>>> The Researchers' Homestead was updated.
>>>
>>>
>>> Jennifer Claro posted a new comment at May 26 - June 1
>>> Compliance-without-pressure techniques for Online Communities.
>>>
>>> Comment:
>>> ---
>>>
>>> 3. Can we prioritize up enabling two-way email integration (ie being able
>>> to reply to messages and have them posted on the forum).
>>>
>>> To my mind, GitHub issues are great examples of something we should
>>> strive towards. They have very nicely formatted subject lines - from the
>>> person sending it (but the from email address is a reply-to at github), the
>>> subject line is simply [project shortname] Topic, and when you open the
>>> message the first thing you see is the actual message, then there are two
>>> lines at the bottom giving you the option of opening the message in GitHub.
>>> And of course you can easily reply to the message directly. And they thread
>>> perfectly in GMail - I have had discussions in GitHub issue messages going
>>> back and forth for 28 messages, most of them sent from GMail, and it works
>>> seemlessly - and is also nicely stored for posterity on GitHub.com.
>>>
>>> I really believe improving on this can have a huge impact on
>>> participation in our discussion-based courses!
>>>
>>> Stian
>>>
>>>
>>>
>>> On Thu, May 31, 2012 at 10:33 AM, Dirk Uys <dirk at p2pu.org> wrote:
>>>>
>>>> When I checked to see if celeryd is running, I noticed that
>>>> /etc/init.d wasn't executable. I don't know how that happened? I fixed
>>>> that, so next time we go down for a reboot everything should be fine.
>>>> I guess we'll see a little later today when Linode do their scheduled
>>>> maintenance.
>>>>
>>>> I'll use the opportunity to make a checklist for system reboot.
>>>>
>>>> On Thu, May 31, 2012 at 1:39 PM, Philipp Schmidt <philipp at p2pu.org>
>>>> wrote:
>>>> > Hm. I suspect it didn't come up when the server rebooted.
>>>> >
>>>> > Can we add it to the init process so that it comes up automatically?
>>>> >
>>>> > (And set up a check list that we verify after each reboot)
>>>> >
>>>> > P
>>>> >
>>>> >
>>>> > On 31 May 2012 10:40, Jos Flores <josmasflores at gmail.com> wrote:
>>>> >>
>>>> >> hahaha, I'm getting batches of mails now :)
>>>> >> thanks for the quick fix!
>>>> >>
>>>> >> José
>>>> >>
>>>> >> On 31 May 2012 09:26, Dirk Uys <dirk at p2pu.org> wrote:
>>>> >> > Problem sorted, celeryd wasn't running. I hope no ones inbox
>>>> >> > explodes
>>>> >> > today :)
>>>> >> >
>>>> >> > Cheers
>>>> >> > d
>>>> >> >
>>>> >> > On Thu, May 31, 2012 at 8:45 AM, Dirk Uys <dirk at p2pu.org> wrote:
>>>> >> >> I'll look into it ASAP!
>>>> >> >>
>>>> >> >> On Thu, May 31, 2012 at 12:34 AM, Jessy Kate Schingler
>>>> >> >> <jessy at jessykate.com> wrote:
>>>> >> >>> hey guys,
>>>> >> >>>
>>>> >> >>> i just noticed i haven't been receiving email alerts for the
>>>> >> >>> researchers'
>>>> >> >>> homestead and then another participant mentioned the same. this
>>>> >> >>> is a
>>>> >> >>> kind of
>>>> >> >>> a big deal since it's the primary way we know if people are
>>>> >> >>> participating
>>>> >> >>> and can reward/engage with them :). any idea what's up? are
>>>> >> >>> others
>>>> >> >>> experiencing this?
>>>> >> >>>
>>>> >> >>> the last notification i received was may 21.
>>>> >> >>> --
>>>> >> >>> Jessy
>>>> >> >>> 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
>>>> >
>>>> _______________________________________________
>>>> p2pu-dev mailing list
>>>> p2pu-dev at lists.p2pu.org
>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>
>>>
>>>
>>>
>>> --
>>> http://reganmian.net/blog -- Random Stuff that Matters
>>>
>>>
>>> _______________________________________________
>>> p2pu-dev mailing list
>>> p2pu-dev at lists.p2pu.org
>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>
>>
>>
>>
>> --
>>
>> Alison
>>
>>
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>
>
>
>
> --
> Jessy
> http://jessykate.com
>
>
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>