Hi Matt, I totally agree that documentation needs to be updated.
From my perspective markdown files in the git repository are most suitable for users and accessible to our users. I am very open to accept Pull requests / Patches for docs. Contributors can ask for confluence (cwiki) privileges as well, if we are aligned on what they want to work on. (At least that’s my opinion, not necessary representative for the project) Best Olaf > Am 22.09.2020 um 19:55 schrieb Matt Andruff <[email protected]>: > > This goes back to why we need to update the documentation... I'll update > that soon so it is easier to find. > > Essentially I suggest using the instructions on git to get going: > > https://github.com/apache/bigtop#for-developers-building-a-component-from-git-repository > > For more info on the commands used (on that git page use this helpful gem > (that is buried a bit) > https://cwiki.apache.org/confluence/display/BIGTOP/Quickstart+Guide%3A+Bigtop+Integration+Test+Framework+2.0 > > Whatever you do, please use docker to build it.... It will save you a heap > of dependency issues. Please learn from my pain. > > Hope this helps > > Matt > > > > > On Tue., Sep. 22, 2020, 09:51 Manfred PAUL, <[email protected]> wrote: > >> Hi, >> >> I would like to participate in developing bigtop. For that I am searching >> for some material (doc, wiki, video, etc) to get all the information needed >> to build the bigtop distribution. >> >> All the information I found was for older versions of bigtop (1.1, 1.2 and >> 1.3) but might still be up to date, so I am asking. >> >> Is written that a developer should use the pre-built docker images for >> building the distribution and not set up his or her own toolchain. Or >> should we use only a CI? Is it even possible to build everything on a 16GB >> Macbook Pro? Etc. >> >> Thanks >> >> Manfred >>
