<font size=2 face="sans-serif">I really like the idea of the shared bookmarking,
but with the ability to upvote more interesting stories and bubble them
up to the top a la Digg.</font>
<br>
<br><font size=2 face="sans-serif">I'm big fan of paper.li as well,
but as you can see from the paper I quickly put together here: </font><a href=http://paper.li/asisin/1367254025><font size=2 face="sans-serif">http://paper.li/asisin/1367254025</font></a><font size=2 face="sans-serif">,
without some degree of curation there is no telling what the content might
look like. <br>
</font><tt><font size=2 color=#4f4f4f><br>
---<br>
Arvind Srinivasan<br>
-----------------------------------------<br>
IBM Cloud Strategy & Technology Standards<br>
Email: </font></tt><a href=mailto:arvindsr@us.ibm.com><tt><font size=2 color=blue><u>arvindsr@us.ibm.com</u></font></tt></a><tt><font size=2 color=#4f4f4f><br>
Phone: +1 919 673 1082<br>
-----------------------------------------<br>
</font></tt>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Dave Neary <dneary@redhat.com></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">Tim Bell <Tim.Bell@cern.ch>, </font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">Stefano Maffulli <stefano@openstack.org>,
"user-committee@lists.openstack.org" <user-committee@lists.openstack.org>,
"Lauren Sell \(lauren@openstack.org\)" <lauren@openstack.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">04/27/2013 11:16 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: [User-committee] Weekly community
newsletter - deployment news</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi,<br>
<br>
Some kind of shared bookmarking solution would be ideal - tag some<br>
tweets/links/articles/blog bosts as "openstack news" and have
them<br>
aggregated and edited once a week.<br>
<br>
paper.li does this automatically for Twitter.<br>
<br>
bit.ly or pinboard.in (or even delicious.com) could work for shared<br>
bookmarks.<br>
<br>
Cheers,<br>
Dave.<br>
<br>
On 04/26/2013 08:43 PM, Tim Bell wrote:<br>
> Stefano,<br>
> <br>
> <br>
> <br>
> How could we do ‘crowd-sourcing’ for this sort of article ? I’m
not sure<br>
> that any of us would be seeing all of the announcements.<br>
> <br>
> <br>
> <br>
> Tim<br>
> <br>
> <br>
> <br>
> *From:*Everett Toews [</font></tt><a href=mailto:everett.toews@RACKSPACE.COM><tt><font size=2>mailto:everett.toews@RACKSPACE.COM</font></tt></a><tt><font size=2>]<br>
> *Sent:* 26 April 2013 15:45<br>
> *To:* Tim Bell<br>
> *Cc:* Stefano Maffulli; user-committee@lists.openstack.org; Lauren
Sell<br>
> (lauren@openstack.org)<br>
> *Subject:* Re: [User-committee] Weekly community newsletter - deployment<br>
> news<br>
> <br>
> <br>
> <br>
> FYI, this is *exactly* what I had in mind for a "Application
News" section.<br>
> <br>
> <br>
> <br>
> </font></tt><a href="http://hortonworks.com/blog/hadoop-perect-app-for-openstack/"><tt><font size=2>http://hortonworks.com/blog/hadoop-perect-app-for-openstack/</font></tt></a><tt><font size=2><br>
> <br>
> <br>
> <br>
> Everett<br>
> <br>
> <br>
> <br>
> On Apr 22, 2013, at 8:44 PM, Everett Toews wrote:<br>
> <br>
> <br>
> <br>
> On Apr 22, 2013, at 11:55 AM, Tim Bell wrote:<br>
> <br>
> <br>
> <br>
> I'm not clear from your reply if you agree
with the proposal to<br>
> add a 'Deployment News' section to the
news letter.<br>
> <br>
> Currently, the survey results are private
to the user committee<br>
> and foundation (even the ones that were
marked as willing to<br>
> share).<br>
> Automating the production of 'declared
this week and marked as<br>
> public' would be a good way to continue
to advertise that the user<br>
> survey should be added to (if people have
forgotten) and also<br>
> give a good call-out for those deployments.<br>
> <br>
> User stories serve a larger need (and
have a much higher cost<br>
> for both the foundation and the organisation
concerned).<br>
> <br>
> <br>
> <br>
> To be clear, I wasn't talking about user stories in
my email. Too<br>
> long and involved. I was thinking more along the lines
of a simple<br>
> blog post by the application developer.<br>
> <br>
> <br>
> <br>
> In the "Deployment News" section what did
you have in mind? I was<br>
> thinking along the lines of this example,<br>
> <br>
> <br>
> <br>
> CompanyX: We deployed OpenStack on 10,000 cores over
2,000 nodes<br>
> running kvm, lvm, etc. etc. and 3 PB of object storage.
Lorem<br>
> ipsum... We did this to support developers building
applications for<br>
> WidgetX.<br>
> <br>
> <br>
> <br>
> My vision for the "Application News" section
was similar. As in the<br>
> example,<br>
> <br>
> <br>
> <br>
> CompanyY: We deployed an application on an OpenStack
cloud with an<br>
> architecture of 1 load balancer, 10 web servers, and
2 DBs. Lorem<br>
> ipsum... This application does AwesomeThing.<br>
> <br>
> <br>
> <br>
> Maybe we'll even get lucky and run into the case where
we see a<br>
> deployment by CompanyZ in "Deployment News"
and then a few months<br>
> later we start seeing applications by CompanyZ appear
in<br>
> "Application News". Either way, I think it
would make for compelling<br>
> stories.<br>
> <br>
> <br>
> <br>
> My original idea was to make the "Deployment News"
and "Application<br>
> News" just one section called "OpenStack Users".
But that might be<br>
> confusing because of the many meanings of users in the
draft charter<br>
> [1]. The application developers I speak of are "consumers"
by that<br>
> definition.<br>
> <br>
> <br>
> <br>
> The real point of all of this is to not forget about
application<br>
> developers. Ultimately it's the application developers
that will<br>
> truly drive forward OpenStack adoption.<br>
> <br>
> <br>
> <br>
> Regards,<br>
> <br>
> Everett<br>
> <br>
> <br>
> <br>
> [1] </font></tt><a href=https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqEToyo/edit><tt><font size=2>https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqEToyo/edit</font></tt></a><tt><font size=2><br>
> <br>
> _______________________________________________<br>
> User-committee mailing list<br>
> User-committee@lists.openstack.org<br>
> <</font></tt><a href="mailto:User-committee@lists.openstack.org"><tt><font size=2>mailto:User-committee@lists.openstack.org</font></tt></a><tt><font size=2>><br>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</font></tt></a><tt><font size=2><br>
> <br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> User-committee mailing list<br>
> User-committee@lists.openstack.org<br>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</font></tt></a><tt><font size=2><br>
> <br>
<br>
-- <br>
Dave Neary - Community Action and Impact<br>
Open Source and Standards, Red Hat - </font></tt><a href=http://community.redhat.com/><tt><font size=2>http://community.redhat.com</font></tt></a><tt><font size=2><br>
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13<br>
<br>
_______________________________________________<br>
User-committee mailing list<br>
User-committee@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</font></tt></a><tt><font size=2><br>
<br>
</font></tt>
<br>
<br>