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 <weichentai...@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 <luckbr1...@gmail.com> > wrote: > > > On Tue, Nov 6, 2018 at 9:27 AM Wei Chen <weichentai...@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/ > > >
