<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 29/07/2010 17:04, Alex Clark wrote:
<blockquote
cite="mid:AANLkTik17SJJjQ=0HecCjL+ytgP_j+WZLABZuJj=+d9X@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Thu, Jul 29, 2010 at 11:25 AM, Doug
Hellmann <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:doug.hellmann@gmail.com">doug.hellmann@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
On Jul 29, 2010, at 11:12 AM, Aahz wrote:<br>
<br>
> On Thu, Jul 29, 2010, Doug Hellmann wrote:<br>
>> On Jul 28, 2010, at 11:54 PM, Stephan Deibel wrote:<br>
>>><br>
>>> I think people are interested in user groups, but their
interest<br>
>>> is limited to first finding one or a few groups near them
and then<br>
>>> following just those groups. A world-wide feed of all
groups doesn't<br>
>>> seem like an interesting thing to me either, though I may
just not be<br>
>>> getting why I would care what all user groups are doing.<br>
>><br>
>> There would be several benefits to having a single place for
all<br>
>> Python user group news:<br>
>><br>
>> 1. It would celebrate the fact that the community encourages
user<br>
>> groups. Given the recent discussions on the PSF members list
about<br>
>> establishing a federation of regional/international foundations<br>
>> to work with the PSF, local user groups are going to become
more<br>
>> important since they are a likely source of members and
organizers for<br>
>> those new foundations.<br>
><br>
> Perhaps your purposes would be served by broadening your proposal?
We<br>
> could make this an aggregator for "community news". We would
explicitly<br>
> label it as specifically for user group news in addition to e.g.<br>
> conference news, sprints, and so on. The <a
moz-do-not-send="true" href="http://python.org" target="_blank">python.org</a>
news feed could<br>
> then be one of the first sources.<br>
<br>
</div>
That makes a lot of sense. We could pull posts from the blog for the
new sprint project Jesse is organizing and the pyfound blog (maybe
limited to a specific tag, to avoid cross-posting everything).<br>
<br>
Alex, what do you think?<br>
</blockquote>
<div><br>
<br>
Sure, if I understand correctly there is agreement to the idea of a new
planet for "community news", and <a moz-do-not-send="true"
href="http://python.org/news/" target="_blank">http://python.org/news/</a>
would feed to it, as would any UG that wanted to.<br>
<br>
I also pictured this "community news" feed going to <a
moz-do-not-send="true" href="http://planet.python.org/" target="_blank">planet.python.org</a>
at some point, if it proved successful.<br>
<br>
</div>
</div>
</blockquote>
<br>
I would expect several of the news sources to *already* be aggregated
on planet python, so we couldn't just pull in the feed wholesale. It
sounds like there is consensus that a community news feed will have
value on its own - but we should maintain them separately. <br>
<br>
Feeds in the community news planet can be added to the main planet
individually. <br>
<br>
All the best,<br>
<br>
Michael<br>
<br>
<blockquote
cite="mid:AANLkTik17SJJjQ=0HecCjL+ytgP_j+WZLABZuJj=+d9X@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>Feed madness!<br>
<br>
:-)<br>
<br>
Thanks, all for considering. And let me know if I can be of any
assistance in implementing if you decide to move forward.<br>
<br>
<br>
Alex<br>
<br>
<br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font
color="#888888"><br>
Doug<br>
</font>
<div>
<div class="h5"><br>
_______________________________________________<br>
pydotorg-www mailing list<br>
<a moz-do-not-send="true" href="mailto:pydotorg-www@python.org">pydotorg-www@python.org</a><br>
<a moz-do-not-send="true"
href="http://mail.python.org/mailman/listinfo/pydotorg-www"
target="_blank">http://mail.python.org/mailman/listinfo/pydotorg-www</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Alex Clark · <a moz-do-not-send="true" href="http://aclark.net">http://aclark.net</a><br>
Author — Plone 3.3 Site Administration · <a moz-do-not-send="true"
href="http://aclark.net/admin">http://aclark.net/admin</a><br>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
pydotorg-www mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pydotorg-www@python.org">pydotorg-www@python.org</a>
<a class="moz-txt-link-freetext" href="http://mail.python.org/mailman/listinfo/pydotorg-www">http://mail.python.org/mailman/listinfo/pydotorg-www</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.ironpythoninaction.com/">http://www.ironpythoninaction.com/</a>
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/blog">http://www.voidspace.org.uk/blog</a>
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
</pre>
</body>
</html>