communication to community

[Joe Witt <jo...@gmail.com>]

Mentors,

Is this a page I can help keep up to date:
http://incubator.apache.org/projects/nifi.html

Once our CMS / website update problems are sorted:

Should we use that to hose documentation/guides/etc..?  Or should we setup
a wiki?  If that how do we do that?

Thanks
Joe

Re: communication to community

[Joe Witt <jo...@gmail.com>]

Billie,

Thanks - updated the nifi incubator status page.  Will hold off on a wiki.

Thanks
Joe

On Tue, Dec 9, 2014 at 11:38 AM, Billie Rinaldi <bi...@apache.org> wrote:

> Yes, you should be able to edit the nifi status file and are encouraged to
> keep it up to date.  One thing we could add is a link to our recent board
> report.  See: http://incubator.apache.org/guides/website.html
>
> If we want a wiki, we can request that one be created for us by creating an
> INFRA ticket.  This is a matter of project preference.  Accumulo, for
> example, does not have a wiki because we prefer that all of our
> documentation be located in a single place, on the main website.  But some
> projects like having a wiki.  I think the main practical difference is that
> wiki permissions are managed separately from svn permissions.
>
> On Tue, Dec 9, 2014 at 8:20 AM, Joe Witt <jo...@gmail.com> wrote:
>
> > Mentors,
> >
> > Is this a page I can help keep up to date:
> > http://incubator.apache.org/projects/nifi.html
> >
> > Once our CMS / website update problems are sorted:
> >
> > Should we use that to hose documentation/guides/etc..?  Or should we
> setup
> > a wiki?  If that how do we do that?
> >
> > Thanks
> > Joe
> >
>

Re: communication to community

[Billie Rinaldi <bi...@apache.org>]

Yes, you should be able to edit the nifi status file and are encouraged to
keep it up to date.  One thing we could add is a link to our recent board
report.  See: http://incubator.apache.org/guides/website.html

If we want a wiki, we can request that one be created for us by creating an
INFRA ticket.  This is a matter of project preference.  Accumulo, for
example, does not have a wiki because we prefer that all of our
documentation be located in a single place, on the main website.  But some
projects like having a wiki.  I think the main practical difference is that
wiki permissions are managed separately from svn permissions.

On Tue, Dec 9, 2014 at 8:20 AM, Joe Witt <jo...@gmail.com> wrote:

> Mentors,
>
> Is this a page I can help keep up to date:
> http://incubator.apache.org/projects/nifi.html
>
> Once our CMS / website update problems are sorted:
>
> Should we use that to hose documentation/guides/etc..?  Or should we setup
> a wiki?  If that how do we do that?
>
> Thanks
> Joe
>