Would it make sense to put these under an "extensions" page, rather than a
"community" page?

On Tue, Oct 16, 2018 at 5:05 PM Sai Boorlagadda <sai.boorlaga...@gmail.com>
wrote:

> Thanks, John for your inputs. I will be adding the page to capture these
> details.
> If there are no objections then I would go ahead and add a new section to
> http://geode.apache.org/community/
>
> Sai
>
> On Thu, Oct 11, 2018 at 12:07 PM John Blum <jb...@pivotal.io> wrote:
>
> > This is a very nice idea Sai.
> >
> > Perhaps a page with a table containing...
> >
> > * Project Name
> > * Project Description (Summary)
> > * Project License
> > * Project URL (to GitHub page, Website, etc, where users can find out
> more
> > information)
> >
> > Food for thought.
> >
> >
> > On Thu, Oct 11, 2018 at 12:04 PM, Sai Boorlagadda <
> > sai.boorlaga...@gmail.com
> > > wrote:
> >
> > > I would like to discuss what's best to capture all the community work
> in
> > > one place. There are some good plugins/extensions that are built by the
> > > community which does not necessarily be merged into the mainstream but
> > > would be a great value for others in the community. Capturing all these
> > at
> > > one place would a great help for someone looking for a solution.
> > >
> > > Also, I would like to capture (if any) requirements (Eg: licenses etc)
> > that
> > > these developers need to adhere to showcase their work. Are there any
> > > Apache guidelines for such work?
> > >
> > > There are many ways to do this. if everyone agrees about the idea of
> > > capturing all at one place then I propose we add a page/section
> capturing
> > > both the requirements and a table of references URLs to those
> open-source
> > > work. That way it easy for someone to update the page and create a PR
> for
> > > the website.
> > >
> > > Sai
> > >
> >
> >
> >
> > --
> > -John
> > john.blum10101 (skype)
> >
>

Reply via email to