On Sun, Jul 15, 2018 at 8:46 PM Jacob Rosenthal <[email protected]> wrote: >...
> Does anyone agree? If so does anyone have capacity to help? I feel like it > might be smart to do the backend in golang, since well presumably want to > ingest pkg.yml from git repos we already have a nice codebase that does > that. > To provide the mynewt community with some Apache and Infrastructure perspective, there are a few things to keep in mind here: 1) Pages on mynewt.apache.org must all be static. It is quite easy to (re)generate them as needed and push those updates. A completely dynamic site of third-party data might be overkill, rather than just going with daily updates. 2) Should non-static pages be desired, that would be accomplished via (say) packages.mynewt.apache.org (any name under mynewt.a.o; choose at will) which would point to a community-managed VM that Infra would provide. Every project can have a VM for its use. 3) Relative to point 2, such community-managed resources must be provided as apache.org websites (rather than new domains). Hope that helps! Cheers, -g
