On 11/21/2013 4:43 AM, Thierry Carrez wrote:
The trick is, such coverage requires editors with a deep technical
knowledge, both to be able to determine significant news from marketing
noise *and* to be able to deep dive into a new feature and make an
article out of it that makes a good read for
On Thu, 2013-11-21 at 10:43 +0100, Thierry Carrez wrote:
> Stefano Maffulli wrote:
> > On 11/19/2013 09:33 PM, Boris Pavlovic wrote:
> >> The idea of this proposal is that every OpenStack project should have
> >> "story" wiki page. It means to publish every week one short message that
> >> contains
Stefano Maffulli wrote:
> On 11/19/2013 09:33 PM, Boris Pavlovic wrote:
>> The idea of this proposal is that every OpenStack project should have
>> "story" wiki page. It means to publish every week one short message that
>> contains most interesting updates for the last week, and high level road
>>
Excerpts from Boris Pavlovic's message of 2013-11-21 00:16:04 -0800:
> Clint,
>
> The main idea is to have processed by human history of project.
>
> It is really impossible to aggregate automatically all data from different
> sources:
> IRC (main project chat/dev chat/meetings), Mailing Lists, C
Clint,
The main idea is to have processed by human history of project.
It is really impossible to aggregate automatically all data from different
sources:
IRC (main project chat/dev chat/meetings), Mailing Lists, Code, Reviews,
Summit discussions, using project specific knowledge and history of
Excerpts from Boris Pavlovic's message of 2013-11-19 21:33:08 -0800:
> Hi stackers,
>
>
> Currently what I see is growing amount of interesting projects, that at
> least I would like to track. But reading all mailing lists, and reviewing
> all patches in all interesting projects to get high level
On Wed, Nov 20, 2013 at 6:45 PM, Stefano Maffulli wrote:
> I like the idea.
>
I love this idea.
...
Not sure the wiki is the best place for this sort of stuff (wiki pages
> are awful for anything but quick notes): since we want this content to
> be delivered and produced easily I would suggest
On 11/19/2013 09:33 PM, Boris Pavlovic wrote:
> The idea of this proposal is that every OpenStack project should have
> "story" wiki page. It means to publish every week one short message that
> contains most interesting updates for the last week, and high level road
> map for future week. So readi
Hmm, I was sort of thinking along the same lines after writing my
post-summit summary for keystone:
https://gist.github.com/dolph/7366031
Granted this is the first time I've written such a document, I could see
this evolving into a regularly updated document on the long term direction
that keys
On 11/20/2013 12:33 AM, Boris Pavlovic wrote:
Hi stackers,
Currently what I see is growing amount of interesting projects, that at
least I would like to track. But reading all mailing lists, and
reviewing all patches in all interesting projects to get high level
understanding of what is happing
+1
I'd also love to see a tag or keyword associated with items that (affects
{project x,y,z}) or (possibly affects {project x,y,z} to highlight areas in
need of collaboration between teams. There is so much going on cross-project
these days, that if the project team thinks the change has side
Boris Pavlovic wrote:
> The idea of this proposal is that every OpenStack project should have
> "story" wiki page. It means to publish every week one short message that
> contains most interesting updates for the last week, and high level road
> map for future week. So reading this for 10-15 minute
On 20/11/13 09:33 +0400, Boris Pavlovic wrote:
Hi stackers,
Currently what I see is growing amount of interesting projects, that at least I
would like to track. But reading all mailing lists, and reviewing all patches
in all interesting projects to get high level understanding of what is happin
Agreed I like the idea.
It reminds me of the blog the solum team is setting up. I think I asked then
when they announced that blog if there was plans to make it easy for other
projects to also have there own supported blog.
http://lists.openstack.org/pipermail/openstack-dev/2013-October/017977.
Love the idea Boris - a nice read :)
Regards,
Tom
On 20/11/13 16:45, Michael Bright wrote:
+1
On 20 November 2013 06:33, Boris Pavlovic mailto:bpavlo...@mirantis.com>> wrote:
Hi stackers,
Currently what I see is growing amount of interesting projects, that
at least I would lik
I think the idea in general is very good (I would be a heavy consumer of
such a thing myself). I am not sure how sustainable is to do it manually
though, especially for larger projects.
Maybe there is a reasonable way to automate this.. For example, if we
could generate a 'dashboard' for each p
+1
On 20 November 2013 06:33, Boris Pavlovic wrote:
> Hi stackers,
>
>
> Currently what I see is growing amount of interesting projects, that at
> least I would like to track. But reading all mailing lists, and reviewing
> all patches in all interesting projects to get high level understanding
17 matches
Mail list logo
