Remaining project infrastructure items

[Luciano Resende <lu...@gmail.com>]

Looks like we are still missing two basic infrastructure items for Marvin-AI

- JIRA

I just requested a JIRA project for MARVIN with notifications being
sent to issues@marvin.apache.org

https://issues.apache.org/jira/projects/MARVIN

- WEBSITE

We should have a basic website that describes the project, point users
to mailing lists, etc. If there isn't one yet, you guys could get
started by forking from:
https://github.com/apache/apache-website-template

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Remaining project infrastructure items

[Daniel Takabayashi <da...@gmail.com>]

I agree that have a new repo is the best choice.

And right now this web site (http://www.marvin-ai.org) is the Marvin
project official website, and it is a git book represented by this repo
https://github.com/marvin-ai/marvin-platform-book ... I think we can use
the same code to create the new one (apache version) and just add some
information about the new cycle of the project.

Em ter, 6 de nov de 2018 às 12:59, Lucas Bonatto Miguel <
lucasbm88@apache.org> escreveu:

> I agree that having a different repo for the website would be better.
>
> I have a list of issues to create once our Jira is working.
> I added a new one to the bottom of the list, which basically will make sure
> we write a good CONTRIBUTING.md file to all repos.
>
>
> On Tue, Nov 6, 2018 at 11:08 AM Wei Chen <we...@gmail.com> wrote:
>
> > I agree that making a different repository will make it cleaner.
> > As long as we have good documentation on how people can go to different
> > repositories to contribute than there should have no problem.
> >
> > On Tue, Nov 6, 2018 at 12:47 PM Luciano Resende <lu...@gmail.com>
> > wrote:
> >
> > > On Tue, Nov 6, 2018 at 9:27 AM Wei Chen <we...@gmail.com>
> wrote:
> > > >
> > > > - Website
> > > > The website can be a branch in our main repository after we set it
> up.
> > > > And we should base our CD on it.
> > > > It will be easier for users to contribute and make changes.
> > > >
> > >
> > > I have seen different approaches. The downside for having the website
> > > together with the project source is that website usually have large
> > > binary artifacts (e.g. images, etc) that then will make your source
> > > code git clone very heavy.  But this is something for the community to
> > > decide.
> > >
> > > Options that I can think are:
> > > 1 - Together with the project source code repository
> > > 2 - Separate repository
> > >
> > > As for publishing:
> > > 1 - gitpubsub (all commits to a specific branch is published as the
> > > live website)
> > > 2 - svnpubsub (all commits to a specific svn repo is published as the
> > > live website)
> > >
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
>

Re: Remaining project infrastructure items

[Lucas Bonatto Miguel <lu...@apache.org>]

I agree that having a different repo for the website would be better.

I have a list of issues to create once our Jira is working.
I added a new one to the bottom of the list, which basically will make sure
we write a good CONTRIBUTING.md file to all repos.


On Tue, Nov 6, 2018 at 11:08 AM Wei Chen <we...@gmail.com> wrote:

> I agree that making a different repository will make it cleaner.
> As long as we have good documentation on how people can go to different
> repositories to contribute than there should have no problem.
>
> On Tue, Nov 6, 2018 at 12:47 PM Luciano Resende <lu...@gmail.com>
> wrote:
>
> > On Tue, Nov 6, 2018 at 9:27 AM Wei Chen <we...@gmail.com> wrote:
> > >
> > > - Website
> > > The website can be a branch in our main repository after we set it up.
> > > And we should base our CD on it.
> > > It will be easier for users to contribute and make changes.
> > >
> >
> > I have seen different approaches. The downside for having the website
> > together with the project source is that website usually have large
> > binary artifacts (e.g. images, etc) that then will make your source
> > code git clone very heavy.  But this is something for the community to
> > decide.
> >
> > Options that I can think are:
> > 1 - Together with the project source code repository
> > 2 - Separate repository
> >
> > As for publishing:
> > 1 - gitpubsub (all commits to a specific branch is published as the
> > live website)
> > 2 - svnpubsub (all commits to a specific svn repo is published as the
> > live website)
> >
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>

Re: Remaining project infrastructure items

[Wei Chen <we...@gmail.com>]

I agree that making a different repository will make it cleaner.
As long as we have good documentation on how people can go to different
repositories to contribute than there should have no problem.

On Tue, Nov 6, 2018 at 12:47 PM Luciano Resende <lu...@gmail.com>
wrote:

> On Tue, Nov 6, 2018 at 9:27 AM Wei Chen <we...@gmail.com> wrote:
> >
> > - Website
> > The website can be a branch in our main repository after we set it up.
> > And we should base our CD on it.
> > It will be easier for users to contribute and make changes.
> >
>
> I have seen different approaches. The downside for having the website
> together with the project source is that website usually have large
> binary artifacts (e.g. images, etc) that then will make your source
> code git clone very heavy.  But this is something for the community to
> decide.
>
> Options that I can think are:
> 1 - Together with the project source code repository
> 2 - Separate repository
>
> As for publishing:
> 1 - gitpubsub (all commits to a specific branch is published as the
> live website)
> 2 - svnpubsub (all commits to a specific svn repo is published as the
> live website)
>
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: Remaining project infrastructure items

[Luciano Resende <lu...@gmail.com>]

On Tue, Nov 6, 2018 at 9:27 AM Wei Chen <we...@gmail.com> wrote:
>
> - Website
> The website can be a branch in our main repository after we set it up.
> And we should base our CD on it.
> It will be easier for users to contribute and make changes.
>

I have seen different approaches. The downside for having the website
together with the project source is that website usually have large
binary artifacts (e.g. images, etc) that then will make your source
code git clone very heavy.  But this is something for the community to
decide.

Options that I can think are:
1 - Together with the project source code repository
2 - Separate repository

As for publishing:
1 - gitpubsub (all commits to a specific branch is published as the
live website)
2 - svnpubsub (all commits to a specific svn repo is published as the
live website)




-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Remaining project infrastructure items

[Wei Chen <we...@gmail.com>]

- Website
The website can be a branch in our main repository after we set it up.
And we should base our CD on it.
It will be easier for users to contribute and make changes.

On Tue, Nov 6, 2018 at 10:39 AM Luciano Resende <lu...@gmail.com>
wrote:

> Looks like we are still missing two basic infrastructure items for
> Marvin-AI
>
> - JIRA
>
> I just requested a JIRA project for MARVIN with notifications being
> sent to issues@marvin.apache.org
>
> https://issues.apache.org/jira/projects/MARVIN
>
> - WEBSITE
>
> We should have a basic website that describes the project, point users
> to mailing lists, etc. If there isn't one yet, you guys could get
> started by forking from:
> https://github.com/apache/apache-website-template
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>