Mailing List Archive

Yes.

Howard

On 27/06/2012 19:17, Craig Woodward wrote:

I think part of the issue is that there are so many channels, and so much info goes through, that it's easy to miss things. That is, in fact, a good reason to have the mailing list, since it seems to catch the attention of everyone on it, being a less "noisy" medium. The CA results were posted to the community blog initially, which creates a TMO item automatically. It was also updated on the wiki, where submissions were being collected, and announced on IRC. It was not properly announced here on the mailing list, which is frankly our bad, it should have been. Understand, we're all human here, and at times forget if we've done something or not. I think the best solution here is to find a way to help prevent this mistake from happening again. Perhaps a nice solution for this would be to subscribe the community mailing list to the Council Blog feed. That allows an automated way for important messages to have one source and propagate to multiple venues in a way that we can't accidentally forget. Currently that gets the occasional announcement for odd events (like CA, CC, etc) and Council meeting minutes. Does that sound reasonable? -Craig _______________________________________________ maemo-community mailing list maemo-community@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-community"]https://lists.maemo.org/mailman/listinfo/maemo-community

Hi,

This was actually my fault. After several hours for processing the submissions, preparing the wiki and the final announcement, I totally forgot about sending it to the mailing list.

Indeed, Woody's proposal seems perfect. Who's actually the administrator for mailing lists?

Regards
On mié, 27 de jun de 2012 20:34:10 WEST, S. Howard <howards@gmx.co.uk> wrote:

> Yes.
>
> Howard
>
> On 27/06/2012 19:17, Craig Woodward wrote:
>
> >
> > I think part of the issue is that there are so many channels, and so
> > much info goes through, that it's easy to miss things.  That is, in
> > fact, a good reason to have the mailing list, since it seems to catch
> > the attention of everyone on it, being a less "noisy" medium.
> >
> > The CA results were posted to the community blog initially, which
> > creates a TMO item automatically.  It was also updated on the wiki,
> > where submissions were being collected, and announced on IRC.  It was
> > not properly announced here on the mailing list, which is frankly our
> > bad, it should have been.  Understand, we're all human here, and at
> > times forget if we've done something or not.
> >
> > I think the best solution here is to find a way to help prevent this
> > mistake from happening again. Perhaps a nice solution for this would
> > be to subscribe the community mailing list to the Council Blog feed.
> > That allows an automated way for important messages to have one source
> > and propagate to multiple venues in a way that we can't accidentally
> > forget.  Currently that gets the occasional announcement for odd
> > events (like CA, CC, etc) and Council meeting minutes.  Does that
> > sound reasonable?
> >
> > -Craig
> > _______________________________________________
> > maemo-community mailing list
> > maemo-community@maemo.org
> > https://lists.maemo.org/mailman/listinfo/maemo-community
>
>

On Wed, Jun 27, 2012 at 2:17 PM, Craig Woodward <woody@rochester.rr.com>wrote:

>
> I think the best solution here is to find a way to help prevent this
> mistake from happening again. Perhaps a nice solution for this would be to
> subscribe the community mailing list to the Council Blog feed. That allows
> an automated way for important messages to have one source and propagate to
> multiple venues in a way that we can't accidentally forget. Currently that
> gets the occasional announcement for odd events (like CA, CC, etc) and
> Council meeting minutes. Does that sound reasonable?
>
> -Craig
>
I certainly think it is reasonable. The consideration is that we probably
turn to X-Fade to do this, and I think he should be prioritized to finish
the cOBS and then other things after that. And then beyond that how many
times will this be used before maemo.org is migrated, and the new community
website will have different infrastructure? So I think we say oops about
this, and move on to the more important tasks.

Rob

Rpb

On 28 June 2012 17:03, robert bauer <nybauer@gmail.com> wrote:
>
> On Wed, Jun 27, 2012 at 2:17 PM, Craig Woodward <woody@rochester.rr.com>
> wrote:
>>
>> I think the best solution here is to find a way to help prevent this
>> mistake from happening again. Perhaps a nice solution for this would be to
>> subscribe the community mailing list to the Council Blog feed.  That allows
>> an automated way for important messages to have one source and propagate to
>> multiple venues in a way that we can't accidentally forget.  Currently that
>> gets the occasional announcement for odd events (like CA, CC, etc) and
>> Council meeting minutes.  Does that sound reasonable?

Yes. Sounds very sensible.

> I certainly think it is reasonable.  The consideration is that we probably
> turn to X-Fade to do this, and I think he should be prioritized to finish
> the cOBS and then other things after that. [...]

Agree with your prioritisation, but I disagree with the assumption
which underlies it :-)

The technical design for this aggregation is:

* Something monitors the Council blog RSS feed
* If a new article is detected, turn it from HTML into plain text
(using `links' perhaps)
* Send an email with a 'from:' line which is subscribed to maemo-community
to maemo-community@...

The "from" line would, ideally, be council@maemo.org of course.

So, the only thing which requires *any* sort of official involvement
is someone who can subscribe council@maemo.org to maemo-community (so
that the emails from this bot/script won't get caught in moderation).
It could even be subscribed to not receive emails (so the council
don't get double-spammed through their forwarding).

If the council sets it up so that council@maemo.org is subscribed to
the mailing list, ANYONE can then implement a bot to monitor the RSS
feed and turn its posts into emails.

It then needs to be run on a regular basis (e.g. via a cronjob) on any
permanently Internet-connected machine. Ideally, this'd be something
under the Nemein support contract so it's backed-up/maintained; but
deploying it doesn't have to be related to writing it.

Anybody could write it. X-Fade could deploy it within 5 minutes if
it's well written, and if that's problematic, I'd be willing to host
it (if it's well written).

The source should also be in a sensible place, but putting it in the
garage project for the maemo.org source code would seem sensible. But
it wouldn't need to integrate into Midgard or even be written in PHP
(Perl would be what *I* would write it in, if I had time to do so).

Hopefully this'd give enough of a spec for:

a) the council to subscribe the mail alias to the mailing list
b) someone to write the actual script

HTH,

Andrew

--
Andrew Flegg -- mailto:andrew@bleb.org  |  http://www.bleb.org/
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

Unfortunately, the feed service for the site does not offer a self-signup e-mail version. I will instead setup a small feed streamer to check and forward a link when new posts appear, as the infrastructure will likely change and as noted X-Fade has far more important items on his plate. :)


---- robert bauer <nybauer@gmail.com> wrote:

=============
On Wed, Jun 27, 2012 at 2:17 PM, Craig Woodward <woody@rochester.rr.com>wrote:

>
> I think the best solution here is to find a way to help prevent this
> mistake from happening again. Perhaps a nice solution for this would be to
> subscribe the community mailing list to the Council Blog feed. That allows
> an automated way for important messages to have one source and propagate to
> multiple venues in a way that we can't accidentally forget. Currently that
> gets the occasional announcement for odd events (like CA, CC, etc) and
> Council meeting minutes. Does that sound reasonable?
>
> -Craig
>
I certainly think it is reasonable. The consideration is that we probably
turn to X-Fade to do this, and I think he should be prioritized to finish
the cOBS and then other things after that. And then beyond that how many
times will this be used before maemo.org is migrated, and the new community
website will have different infrastructure? So I think we say oops about
this, and move on to the more important tasks.

Rob

Rpb

_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

On 28 June 2012 20:44, Craig Woodward <woody@rochester.rr.com> wrote:
>
> Unfortunately, the feed service for the site does not offer a self-signup e-mail
> version.

1) Subscribe council@maemo.org here:
https://lists.maemo.org/mailman/listinfo/maemo-community

2) Write code to parse RSS here:
http://maemo.org/community/council/rss.xml

3) Write code to send parsed RSS as email:
--------8<--------
From: "Community Council blog" <council@maemo.org>
Subject: [Council] $item->{title}
To: "Maemo Community mailing list" <maemo-community@maemo.org>

$parsedText

-- /* sig sep, note space after two dashes */
This was automatically syndicated from the Maemo Community Council
blog: http://maemo.org/community/council/
For more information on the Maemo Community Council, visit the
homepage: http://wiki.maemo.org/Community_Council
-------->8--------

This'd be a good test for people talking about community
infrastructure. If they can't write a Perl/Python/Ruby/... script to
do this in less than an hour, they're not qualified to be involved ;-)

Cheers,

Andrew

--
Andrew Flegg -- mailto:andrew@bleb.org  |  http://www.bleb.org/
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

On Thursday 28 June 2012 21:18:22 Andrew Flegg wrote:
> This'd be a good test for people talking about community
> infrastructure. If they can't write a Perl/Python/Ruby/... script to
> do this in less than an hour, they're not qualified to be involved ;-)

No script needs to be written: off-the-shelf packages exist. Personally I use
rss2email.

But it does need somewhere to run.
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

for crying out loud, you are arguing about the sex of angels and meanwhile
the castle is going down in flames :mad:

On 29 June 2012 00:15, Graham Cobb <g+770@cobb.uk.net> wrote:

> On Thursday 28 June 2012 21:18:22 Andrew Flegg wrote:
> > This'd be a good test for people talking about community
> > infrastructure. If they can't write a Perl/Python/Ruby/... script to
> > do this in less than an hour, they're not qualified to be involved ;-)
>
> No script needs to be written: off-the-shelf packages exist. Personally I
> use
> rss2email.
>
> But it does need somewhere to run.
> _______________________________________________
> maemo-community mailing list
> maemo-community@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-community
>

AFAIK, we're talking about improving automatic stream of info for
mailing list ;)
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

On 28 June 2012 23:15, Graham Cobb <g+770@cobb.uk.net> wrote:
> On Thursday 28 June 2012 21:18:22 Andrew Flegg wrote:
>> This'd be a good test for people talking about community
>> infrastructure. If they can't write a Perl/Python/Ruby/... script to
>> do this in less than an hour, they're not qualified to be involved ;-)
>
> No script needs to be written: off-the-shelf packages exist.  Personally I use
> rss2email.

Ah, cool. Thought it was likely to exist. And it looks trivial to use:

http://www.allthingsrss.com/rss2email/getting-started-with-rss2email/#unix

> But it does need somewhere to run.

I've just installed it on bleb.org and done:

$ r2e new testemail@bleb.org # This would be maemo-community@maemo.org
$ r2e add http://maemo.org/community/council/rss.xml
$ cat >.rss2email/config.py <<EOC
DEFAULT_FROM = 'council@maemo.org'
DATE_HEADER = 1
SMTP_SERVER = "localhost:25"
FORCE_FROM = 1
EOC
$ r2e run --no-send

Then put a cronjob in place for every 15 minutes to do 'r2e run'.
Seems to work perfectly.

I'm happy to set this going at maemo-community@maemo.org, if someone
on the council can subscribe council@maemo.org to the list.

Cheers,

Andrew

--
Andrew Flegg -- mailto:andrew@bleb.org  |  http://www.bleb.org/
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

Done.

I've registered and set the delivery to disabled for now, since we're all already on the list and don't need duplicates of all the mail (even in a digest form) if avoidable. If that will block incoming mail, let me know and I'll set it to digest w/ the longest digest period possible. :)

And thanks for setting this up. I've been a over-occupied with work & other tasks this week.

-Craig


---- Andrew Flegg <andrew@bleb.org> wrote:

=============
On 28 June 2012 23:15, Graham Cobb <g+770@cobb.uk.net> wrote:
> On Thursday 28 June 2012 21:18:22 Andrew Flegg wrote:
>> This'd be a good test for people talking about community
>> infrastructure. If they can't write a Perl/Python/Ruby/... script to
>> do this in less than an hour, they're not qualified to be involved ;-)
>
> No script needs to be written: off-the-shelf packages exist.  Personally I use
> rss2email.

Ah, cool. Thought it was likely to exist. And it looks trivial to use:

http://www.allthingsrss.com/rss2email/getting-started-with-rss2email/#unix

> But it does need somewhere to run.

I've just installed it on bleb.org and done:

$ r2e new testemail@bleb.org # This would be maemo-community@maemo.org
$ r2e add http://maemo.org/community/council/rss.xml
$ cat >.rss2email/config.py <<EOC
DEFAULT_FROM = 'council@maemo.org'
DATE_HEADER = 1
SMTP_SERVER = "localhost:25"
FORCE_FROM = 1
EOC
$ r2e run --no-send

Then put a cronjob in place for every 15 minutes to do 'r2e run'.
Seems to work perfectly.

I'm happy to set this going at maemo-community@maemo.org, if someone
on the council can subscribe council@maemo.org to the list.

Cheers,

Andrew

--
Andrew Flegg -- mailto:andrew@bleb.org  |  http://www.bleb.org/
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

On 29 June 2012 17:08, Craig Woodward <woody@rochester.rr.com> wrote:
> Done.

Thanks.

> I've registered and set the delivery to disabled for now, since
> we're all already on the list and don't need duplicates of all the
> mail (even in a digest form) if avoidable.  If that will block
> incoming mail, let me know and I'll set it to digest w/ the longest
> digest period possible. :)

It should be fine; being set up to receive shouldn't stop you from posting.

> And thanks for setting this up.  I've been a over-occupied with work &
> other tasks this week.

No probs.

Cheers,

Andrew

--
Andrew Flegg -- mailto:andrew@bleb.org  |  http://www.bleb.org/
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community

On Thursday 28 June 2012 23:22:32 claude bucher wrote:
> for crying out loud, you are arguing about the sex of angels and meanwhile
> the castle is going down in flames :mad:

I think I have made my suggestions for the future of Maemo clear on both this
list and on TMO, but I am happy to re-iterate them if you are interested. I
await news from the council on what they are proposing with great interest.

Meanwhile, I see no reason not to help Andrew out with a software
recommendation.

Graham
_______________________________________________
maemo-community mailing list
maemo-community@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-community