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
>From a purely documentation and explanatory standpoint I vote for
"project", if we're going to standardize on one or the other.
On Nov 23, 2013 7:13 AM, "Christopher Yeoh" wrote:
> Hi,
>
> So in the past we've used both tenant and project to refer to the same
> thing and I think its been a sourc
I've put together an etherpad to hopefully get a little discussion going
about what people would like to happen to make it easier for them to
provide more docs related to the code they're providing. (
http://junodesignsummit.sched.org/event/19381e6ad48e05abc9099eb7ff956231#.U20CR3Wx17Q
)
The ethe
> > that supports at least basic markup (e.g., titles,
>> > paragraphs, lists, etc.).
>> > 3. Provide a link to the content (e.g., gist on
>> > github.com, wiki page, blog post, etc.) under the
&g
On Fri, Oct 3, 2014 at 3:07 PM, Stefano Maffulli
wrote:
> hi Nick,
>
> On 09/29/2014 02:06 PM, Nicholas Chase wrote:
> > Because we know that the networking documentation needs particular
> > attention, we're starting there. We have a Networking Guide, from which
> > we will ultimately pull info
On Sun, Oct 5, 2014 at 11:26 PM, Tom Fifield wrote:
> On 04/10/14 04:03, Nick Chase wrote:
> >
> > On Fri, Oct 3, 2014 at 3:07 PM, Stefano Maffulli > <mailto:stef...@openstack.org>> wrote:
> > > 1. Pick an existing topic or create a new
Actually the documentation process is already open to all, and has been.
You can find information on how to contribute here:
https://wiki.openstack.org/wiki/Documentation/HowTo
Thanks!
Nick
On Mon, Oct 6, 2014 at 1:23 AM, Akilesh K wrote:
> Can someone create a Wiki for all the options
On Fri, Oct 3, 2014 at 3:07 PM, Stefano Maffulli
wrote:
>
> > 4. Send e-mail to reviewers network...@openstacknow.com.
>
> Why not use the docs mailing list or other facilities on @openstack.org?
We've now switched over to use the [networking] topic on the openstack-docs
list. So anybody who'
If you have someone to talk to re: licenses and just need someone to do the
legwork, I would be happy to do that.
On Oct 2, 2013 11:36 AM, "Anne Gentle" wrote:
> Hi all,
>
> I'm excited to be going to the Grace Hopper Conference tomorrow, where
> I'll be with over 4500 other women in computing. I
Maybe add a link to the Mistral page from the Convention page?
On Oct 15, 2013 4:22 AM, "Renat Akhmerov" wrote:
> Hey Clint, thanks for your question. I think it's been fully answered by
> this time. You and other people are very welcome to collaborate :)
>
> Joshua, as far as renaming the origin
> Possible ways of remote interaction:
> - direct hangout participation (key people)
> - questions/comments section in etherpad (delay, more difficult to follow
- might need some assistant for tracking them)
I have a realtime browser-based chat app that is normally used in
conjunction with live ev
I am one of those horizontal people (working on docs and basically one of
the people responsible at my organization for keeping a handle on what's
going on) and I'm totally against a split.
Of COURSE we need to maintain the integrated/incubated/proposed spectrum.
Saying that we need to keep all tr
It's definitely broken. We're getting the same messages for people who
haven't submittted ANY talks.
That said, the 3 proposal limit is NOT just for speakers, but also for
SUBMITTERS. So be prepared, unless they broke it trying to change that,
your colleagues are going to have to submit thei
What about using a combination of two word names, and generic names. For
example, you might have
cinder-blockstorage
and
foo-blockstorage
The advantage there is that we don't need to do the thesaurus.com thing,
but also, it enables to specify just
blockstorage
via a registry. The
On Thu, Jul 23, 2015 at 4:05 PM, Matthew Mosesohn
mailto:mmoses...@mirantis.com>> wrote:
Here's a relic of what users used to have to configure by
hand:
https://github.com/stackforge/fuel-library/blob/b015ed975b58dddff3b8da0ce34d9a638c22d032/deployment/puppet/openstack/examples/s
do need to be able to commit to running
meetings once a week or every two weeks, and keeping an eye on reviews.
Of course, I am here to support anyone who chooses to take this on, as well.
Lana
On 03/10/15 04:40, Nick Chase wrote:
I'm actually serious on abdicating here; I'm catching u
This is AWESOME! And I've already found useful resources on the list of
successes. Beautiful job, and fantastic idea!
Nick
On 10/09/2015 05:42 AM, Thierry Carrez wrote:
> Hello everyone,
>
> OpenStack has become quite big, and it's easier than ever to
feel lost,
Does anybody know if a) ATC emails have started to go out yet, and b)
when proposal voting will start?
Thanks
--- Nick
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
ons)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Nick Chase, Head of Technical and Marketing Content, Mirantis
Editor in Chief, OpenStack:Unlocked
<https://www.eventbrite.com/e/openstac
OK, so if you were putting together New Year's Resolutions for OpenStack
development for 2017, what would they be?
--
Nick Chase
Editor in Chief, OpenStack:Unlocked
__
OpenStack Development Mailing List (not for
20 matches
Mail list logo
