Ok thanks Dave. "The selection of these logo displays must be Vendor Neutral."?
On Tue, Jun 25, 2019 at 12:23 PM Dave Fisher <[email protected]> wrote: > Hi - > > > On Jun 25, 2019, at 9:32 AM, Josh Fischer <[email protected]> wrote: > > > > Hi All, > > > > I'm almost done with the static doc framework migration. I have a couple > > of questions. > > > > 1. Do we want to have a place in the page to display companies using > Heron? > > Can/Should we do this? > > Yes you can. It should not be the main page and somewhere it should be > possible for people and companies using Heron to ask to be added. The > selection of these logo displays must be Vendor Neutral. > > > 2. Do we want to have a place for a Blog on the site? I assume this > would > > be release notes and what not. > > > > > > On Wed, May 22, 2019 at 6:14 PM Josh Fischer <[email protected]> > wrote: > > > >> I went ahead and moved forward on using Docusarus for our docs. I > opened > >> a PR for feedback as I go. It can be found here -> > >> https://github.com/apache/incubator-heron/pull/3270. Out of the box > >> Docusarus comes with a template to do blog posts and show companies that > >> are using the software. I think both would be cool to have, but I'm not > >> sure how this works with Apache. > >> > >> To recap: My questions are: > >> 1. Do we want to have a place in the page to display companies using > >> Heron? Can/Should we do this? > >> 2. Do we want to have a place for a Blog on the site? > >> > >> - Josh > >> > >> On Tue, May 21, 2019 at 2:11 PM Josh Fischer <[email protected]> > wrote: > >> > >>> Hey All, > >>> > >>> Did a little more looking at this. I did a little more looking into > >>> Docusarus. My quick scan of the web page was incorrect.. I think > >>> Docusarus would replace the current framework that our site is built > with > >>> (Hugo). So. While versioning the site with Docusaurus would be fairly > >>> simple. It would be a bit of an undertaking to convert our site from > one > >>> framework to another. After a quick search on website versioning with > Hugo > >>> I didn't come up with anything that stuck out to me. I'll take some > time > >>> to look over the Hugo docs more closely to understand what complexity > we > >>> would have to deal with when it comes to site versioning. Any > thoughts, > >>> suggestions or comments? > >>> > >>> On Tue, May 21, 2019 at 7:54 AM Simon Weng <[email protected]> > wrote: > >>> > >>>> Certainly I don’t know much about documentation tooling, but I heard > good > >>>> things about Docusarus, and also Gitbook. > >>>> > >>>> On Tue, May 21, 2019 at 8:16 AM Josh Fischer <[email protected]> > >>>> wrote: > >>>> > >>>>> Ok sounds good. Thanks. > >>>>> > >>>>> On Tue, May 21, 2019 at 2:37 AM Ning Wang <[email protected]> > >>>> wrote: > >>>>> > >>>>>> Looks good~ > >>>>>> > >>>>>> For the move, I think we don't really need to wait for the release. > >>>>>> Especially we may need to have a "master" version and other versions > >>>> for > >>>>>> different releases. > >>>>>> > >>>>>> How far back might depends on how easy it is to generate web pages. > >>>> :) > >>>>> It > >>>>>> might be good enough to start having the pages after moving to > Apache > >>>>>> package name (0.20.0) so it is only one version back. > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Mon, May 20, 2019 at 8:24 PM Josh Fischer <[email protected]> > >>>>> wrote: > >>>>>> > >>>>>>> Good Evening, > >>>>>>> > >>>>>>> I've been looking around the Pulsar repo to see how they version > >>>> their > >>>>>>> docs.. It looks like they are using > >>>>>>> Docusarus -> https://docusaurus.io/docs/en/versioning. This > >>>> looks > >>>>>> like a > >>>>>>> nice little tool that could handle the versioning for us. > >>>>>>> > >>>>>>> A question I still have.. Is it more important to move where the > >>>> static > >>>>>>> pages are served from with the added Apache information and then > >>>> work > >>>>> on > >>>>>>> versioning the docs? I imagine we would have to manually trigger > >>>> this > >>>>>> page > >>>>>>> deployment only once to get it moved. Or should wait to move the > >>>> site > >>>>>> once > >>>>>>> a new release is created and add in all the automation before hand? > >>>>>>> > >>>>>>> Finally, how far back to do we go to try and match the > >>>> documentation to > >>>>>> the > >>>>>>> version? > >>>>>>> > >>>>>>> On Fri, May 17, 2019 at 11:04 PM Ning Wang <[email protected]> > >>>>> wrote: > >>>>>>> > >>>>>>>> got it. that is small enough then :) thx > >>>>>>>> > >>>>>>>> On Fri, May 17, 2019 at 7:33 PM Josh Fischer < > >>>> [email protected]> > >>>>>>> wrote: > >>>>>>>> > >>>>>>>>> I just built the static site on my local. The zip file of the > >>>>>> website > >>>>>>> is > >>>>>>>>> 15.1 MB. > >>>>>>>>> > >>>>>>>>> On Fri, May 17, 2019 at 6:03 PM Ning Wang < > >>>> [email protected]> > >>>>>>> wrote: > >>>>>>>>> > >>>>>>>>>> I think it makes sense for each release to have a separated > >>>>>>>> doc/website. > >>>>>>>>> It > >>>>>>>>>> might be a question though if the website should be included > >>>> in > >>>>> the > >>>>>>>>>> release. I am also curious how big the zip file of the > >>>> website > >>>>> is? > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Fri, May 17, 2019 at 6:48 AM Josh Fischer < > >>>>> [email protected]> > >>>>>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> My responses are Inlined > >>>>>>>>>>> > >>>>>>>>>>> On Wed, May 15, 2019 at 1:37 PM Dave Fisher < > >>>>>> [email protected] > >>>>>>>> > >>>>>>>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>>> A few thoughts about the website. There are two parts to > >>>>>>> consider. > >>>>>>>>>>>> > >>>>>>>>>>>> (1) The constant part that talks about the Heron project, > >>>>> where > >>>>>>>>>> resources > >>>>>>>>>>>> are and how to contribute to it. This part includes > >>>> linkages > >>>>> to > >>>>>>> ASF > >>>>>>>>>>>> resources and also the proper download pages etc. > >>>>>>>>>>>> > >>>>>>>>>>>> This part should be published at any time and I suggest > >>>> that > >>>>>> the > >>>>>>>>>> Jenkins > >>>>>>>>>>>> build be triggered by changes to the repository. This is > >>>> why > >>>>>> many > >>>>>>>>>>> projects > >>>>>>>>>>>> have a separate repository for the website. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> *** I do have a fair amount of this merged into master. I > >>>>> looked > >>>>>>> at > >>>>>>>>>>> another incubating project and reused a lot of what they > >>>> have > >>>>>> done. > >>>>>>>>> The > >>>>>>>>>>> static site just hasn’t been updated yet. If think this > >>>>> should > >>>>>> go > >>>>>>>> out > >>>>>>>>>>> before we move where the site is served from I think we can > >>>>> make > >>>>>>> that > >>>>>>>>>>> happen. Please advise. > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> See the following for missing issues: > >>>>>>>>>>>> https://whimsy.apache.org/pods/project/heron - go to > >>>>>>>>>>>> https://whimsy.apache.org/pods/project to find another > >>>>> podling > >>>>>>> for > >>>>>>>>>>>> comparison. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> *** see above > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> (2) Heron docs ought to be tied together with product > >>>>> releases > >>>>>>>> along > >>>>>>>>>> with > >>>>>>>>>>>> master. It makes sense for a releases docs to be part of > >>>> a > >>>>>>> release > >>>>>>>>>> build. > >>>>>>>>>>>> Some projects even include release docs with a binary > >>>>>> convenience > >>>>>>>>>>> release. > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> *** ok would have to think about this approach a little > >>>> more. > >>>>> I > >>>>>>>> think > >>>>>>>>> I > >>>>>>>>>>> misunderstood the reasoning behind separating the website > >>>> from > >>>>>> the > >>>>>>>>>> code. I > >>>>>>>>>>> do this would be an easier to manage workflow. I believe > >>>> the > >>>>>>>> current > >>>>>>>>>> set > >>>>>>>>>>> up builds all static content and Java/Py docs from the same > >>>>>>> command. > >>>>>>>>> We > >>>>>>>>>>> may have to do a little more work to separate the two. > >>>>>>>>>>> > >>>>>>>>>>> *** Any one else have any thoughts? Did I miss anything? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>> Regards, > >>>>>>>>>>>> Dave > >>>>>>>>>>>> > >>>>>>>>>>>>> On May 10, 2019, at 9:14 AM, Josh Fischer < > >>>>>> [email protected] > >>>>>>>> > >>>>>>>>>> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>> Hey All, > >>>>>>>>>>>>> > >>>>>>>>>>>>> With the "build asf site" scripts merged into master we > >>>>>> should > >>>>>>>>> decide > >>>>>>>>>>>> which > >>>>>>>>>>>>> of the existing Heron Jenkins builds that we want to > >>>>> trigger > >>>>>>>> them. > >>>>>>>>>>> Ning > >>>>>>>>>>>>> brought up a good idea to have differences instances > >>>> of the > >>>>>>>> static > >>>>>>>>>> site > >>>>>>>>>>>>> running for the different versions of Heron. I agree > >>>> that > >>>>>> this > >>>>>>>> is > >>>>>>>>> a > >>>>>>>>>>> good > >>>>>>>>>>>>> idea. While I don't think that easily possible today, > >>>> we > >>>>> can > >>>>>>>> start > >>>>>>>>>> to > >>>>>>>>>>>>> design our release process to work with this idea. We > >>>>> could > >>>>>>>> create > >>>>>>>>>> new > >>>>>>>>>>>>> docs to be published for each successful release as > >>>> opposed > >>>>>> to > >>>>>>> a > >>>>>>>>>>>> scheduled > >>>>>>>>>>>>> cron job? Thoughts? > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Fri, Apr 26, 2019 at 11:03 AM Dave Fisher < > >>>>>>>>> [email protected]> > >>>>>>>>>>>> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Hi Josh, > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> I responded to your more recent email. In order to > >>>> create > >>>>>> and > >>>>>>>>> manage > >>>>>>>>>>>>>> Jenkins jobs ids need to be added to the > >>>> hudson-jobadmin > >>>>>> LDAP > >>>>>>>>> group > >>>>>>>>>>> by > >>>>>>>>>>>> a > >>>>>>>>>>>>>> PMC Chair. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Looking for that now. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Regards, > >>>>>>>>>>>>>> Dave > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Apr 24, 2019, at 4:09 PM, Josh Fischer < > >>>>>>> [email protected] > >>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Sending this again. I think the apache servers > >>>> stripped > >>>>>> out > >>>>>>>> the > >>>>>>>>>>> image > >>>>>>>>>>>> on > >>>>>>>>>>>>>>> the last email I sent. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Here is my original message: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> I was looking around the site > >>>>>>>>>>>>>> https://builds.apache.org/view/Heron%20Jobs/ . > >>>>>>>>>>>>>>> I've logged in, but I don't see a way to create a > >>>>> freestyle > >>>>>>>>>>>>>>> project/pipeline/anything in the UI. Am I missing > >>>>>> something > >>>>>>>>>>> obvious? > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Please see the google drive link below for the image > >>>> I > >>>>> was > >>>>>>>> trying > >>>>>>>>>> to > >>>>>>>>>>>>>> share > >>>>>>>>>>>>>>> before. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > https://drive.google.com/file/d/1BGjltTiRNZRfBaT5d2heTKEfKfUe0Irz/view?usp=sharing > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Tue, Apr 23, 2019 at 9:34 PM Josh Fischer < > >>>>>>>>> [email protected]> > >>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Hey All, > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> I was looking around the site > >>>>>>>>>>>>>> https://builds.apache.org/view/Heron%20Jobs/ . > >>>>>>>>>>>>>>>> I've logged in, but I don't see a way to create a > >>>>>> freestyle > >>>>>>>>>>>>>>>> project/pipeline/anything in the UI.. See attached > >>>>> image. > >>>>>>>> Am I > >>>>>>>>>>>> missing > >>>>>>>>>>>>>>>> something? > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Mon, Apr 22, 2019 at 1:09 PM Ning Wang < > >>>>>>>> [email protected] > >>>>>>>>>> > >>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Cool. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> On Mon, Apr 22, 2019 at 10:31 AM Josh Fischer < > >>>>>>>>>> [email protected] > >>>>>>>>>>>> > >>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I do too. I’ll resend the email and try to move > >>>>> forward > >>>>>>>> this > >>>>>>>>>>> week. > >>>>>>>>>>>>>>>>> Ning, > >>>>>>>>>>>>>>>>>> If I get stuck Ill Let you know. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> On Mon, Apr 22, 2019 at 12:02 PM Ning Wang < > >>>>>>>>>> [email protected]> > >>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Nice! I have access to Jenkins. Please let me > >>>> know if > >>>>>> you > >>>>>>>>> need > >>>>>>>>>>>> helps > >>>>>>>>>>>>>>>>> from > >>>>>>>>>>>>>>>>>>> me. > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> On Mon, Apr 22, 2019 at 9:40 AM Josh Fischer < > >>>>>>>>>>> [email protected]> > >>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Just an update on the heron doc website. The > >>>> actual > >>>>>>>> website > >>>>>>>>>>> build > >>>>>>>>>>>>>>>>> has > >>>>>>>>>>>>>>>>>>> been > >>>>>>>>>>>>>>>>>>>> fixed. I sent an email out to [email protected] > >>>>>> asking > >>>>>>>>> about > >>>>>>>>>>> how > >>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>> implement the process and describing what we > >>>> would > >>>>>> need > >>>>>>> in > >>>>>>>>> the > >>>>>>>>>>>>>>>>> server > >>>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>> build about a week ago. I didn’t get a reply > >>>> back, > >>>>> I > >>>>>>> will > >>>>>>>>> try > >>>>>>>>>>>> again > >>>>>>>>>>>>>>>>>> this > >>>>>>>>>>>>>>>>>>>> week. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> On Wed, Apr 3, 2019 at 9:08 PM Ning Wang < > >>>>>>>>>> [email protected]> > >>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> Great! > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> On Wed, Apr 3, 2019 at 4:25 PM Josh Fischer < > >>>>>>>>>>> [email protected] > >>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> Yes I think I am all set up now. Thank you for > >>>>> your > >>>>>>>> help. > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> - Josh > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 3, 2019 at 3:48 PM Dave Fisher < > >>>>>>>>>>>>>>>>> [email protected]> > >>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Hi Josh, > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> I see you in the group. Are you all set? > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Regards, > >>>>>>>>>>>>>>>>>>>>>>> Dave > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> On Apr 3, 2019, at 12:02 PM, Dave Fisher < > >>>>>>>>>>>>>>>>>> [email protected]> > >>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> Email stripped the image out. Please send it > >>>>>>> directly. > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> On Apr 3, 2019, at 11:54 AM, Josh Fischer < > >>>>>>>>>>>>>>>>>> [email protected]> > >>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> Ok went to that link and nothing and authed > >>>>> with > >>>>>>>>> apache, > >>>>>>>>>>>>>>>>> GH, > >>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>> saw > >>>>>>>>>>>>>>>>>>>>>>> confirmation of repos. Still no access via > >>>> UI or > >>>>>>> CLI. > >>>>>>>>>>>>>>>>>>>>>>>>> Image attached. > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 3, 2019 at 1:46 PM Dave Fisher > >>>> < > >>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>> Infra has a question: > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> Could you please have him submit a > >>>> screenshot > >>>>> of > >>>>>>> what > >>>>>>>>>>>>>>>>>>>>>>> https://gitbox.apache.org/setup/ < > >>>>>>>>>>>>>>>>>> https://gitbox.apache.org/setup/ > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> says > >>>>>>>>>>>>>>>>>>>>>>> after he has authed? He may need to reset his > >>>>>> github > >>>>>>>>>> linking > >>>>>>>>>>>>>>>>>> (reset > >>>>>>>>>>>>>>>>>>>>> link > >>>>>>>>>>>>>>>>>>>>>> in > >>>>>>>>>>>>>>>>>>>>>>> the middle box of the setup page.) > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> Regards, > >>>>>>>>>>>>>>>>>>>>>>>>> Dave > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> On Apr 3, 2019, at 11:19 AM, Dave Fisher < > >>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> It looks like you are missing from the > >>>> heron > >>>>>>>>> committers > >>>>>>>>>>>>>>>>> group > >>>>>>>>>>>>>>>>>>> on > >>>>>>>>>>>>>>>>>>>>> Git > >>>>>>>>>>>>>>>>>>>>>>> Hub. I’m asking Infra why on Slack. If no > >>>> answer > >>>>>> soon > >>>>>>>>> then > >>>>>>>>>>>>>>>>> I’ll > >>>>>>>>>>>>>>>>>>> file > >>>>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>>> JIRA. > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> Anyone else having issues? > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>> On Apr 3, 2019, at 11:03 AM, Josh > >>>> Fischer < > >>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>> I do have 2FA enabled. I've also tried > >>>> to > >>>>> log > >>>>>>> in/ > >>>>>>>>> log > >>>>>>>>>>>>>>>>> out. > >>>>>>>>>>>>>>>>>>> No > >>>>>>>>>>>>>>>>>>>>>>> success. > >>>>>>>>>>>>>>>>>>>>>>>>>>> Any suggestions on who I should contact > >>>> to > >>>>> help > >>>>>>>>>> diagnose > >>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>> fix? > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 3, 2019 at 12:58 PM Dave > >>>> Fisher < > >>>>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Apr 3, 2019, at 10:49 AM, Josh > >>>> Fischer < > >>>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for the info Dave. I have a > >>>> couple > >>>>> of > >>>>>>>>>>>>>>>>> responses to > >>>>>>>>>>>>>>>>>>>> your > >>>>>>>>>>>>>>>>>>>>>>>>>>>> questions. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> (1) Does the project wish to create > >>>>>>> documentation > >>>>>>>>> in > >>>>>>>>>> a > >>>>>>>>>>>>>>>>> new > >>>>>>>>>>>>>>>>>>>>>>> repository - > >>>>>>>>>>>>>>>>>>>>>>>>>>>> say > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> apache/incubator-heron-site > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Or should the build use an asf-site > >>>>> branch > >>>>>> in > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> apache/incubator-heron which just > >>>> keeps the > >>>>>>>>> deployed > >>>>>>>>>>>>>>>>>>> content. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> ** The site build is currently > >>>> dependent on > >>>>>>> Bazel > >>>>>>>>> to > >>>>>>>>>>>>>>>>>>> generate > >>>>>>>>>>>>>>>>>>>>>>> Javadocs. > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> think we should just have a "asf-site" > >>>>> branch > >>>>>>>> that > >>>>>>>>> is > >>>>>>>>>>>>>>>>> used > >>>>>>>>>>>>>>>>>>>>> within > >>>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> current repo to serve static files > >>>> from as > >>>>> it > >>>>>>>> would > >>>>>>>>>>>>>>>>>> require > >>>>>>>>>>>>>>>>>>>> less > >>>>>>>>>>>>>>>>>>>>>>> moving > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> parts. Not sure if that would cause > >>>> any > >>>>>> issues > >>>>>>>>> with > >>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>> current > >>>>>>>>>>>>>>>>>>>>>>> setup > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> though. I was asking Ning a similar > >>>>> question > >>>>>>> on > >>>>>>>>> how > >>>>>>>>>> to > >>>>>>>>>>>>>>>>>> set > >>>>>>>>>>>>>>>>>>>> this > >>>>>>>>>>>>>>>>>>>>>> up > >>>>>>>>>>>>>>>>>>>>>>>>>>>> since I > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> don't have write access to the repo > >>>> yet.Hi > >>>>> - > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Really? - Have you enabled 2FA on > >>>> GitHub for > >>>>>>> your > >>>>>>>>>>>>>>>>>>>> joshfischer1108 > >>>>>>>>>>>>>>>>>>>>>>> username? > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I recommend that you get access fixed > >>>> and > >>>>> then > >>>>>>>> work > >>>>>>>>> on > >>>>>>>>>>>>>>>>>> doing > >>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>> build > >>>>>>>>>>>>>>>>>>>>>>>>>>>> locally. Once you have that we can work > >>>> on > >>>>> the > >>>>>>>>> Jenkins > >>>>>>>>>>>>>>>>>> build > >>>>>>>>>>>>>>>>>>>> with > >>>>>>>>>>>>>>>>>>>>>>> triggers. > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> (2) Does the website Jenkins box > >>>> already > >>>>>>> support > >>>>>>>>> the > >>>>>>>>>>>>>>>>> build > >>>>>>>>>>>>>>>>>>>>>>> requirements. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> ** I will look into this. > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Ask on the-asf.slack.com < > >>>>>>>> http://the-asf.slack.com/ > >>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> #asfinfra - > >>>>>>>>>>>>>>>>>>>>>>> tell them it is for a gitpubsub > >>>>>>>>>>>>>>>>>>>>>>>>>>>> website build. > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Regards, > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Dave > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 3, 2019 at 10:43 AM Dave > >>>>> Fisher < > >>>>>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi - > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> TL:DR - The project should definitely > >>>> use > >>>>>>>>> gitpubsub > >>>>>>>>>>>>>>>>>>> approach. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mar 28, 2019, at 7:08 PM, Josh > >>>>> Fischer < > >>>>>>>>>>>>>>>>>>>>> [email protected] > >>>>>>>>>>>>>>>>>>>>>>> <mailto:[email protected]>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> How does everyone want to manage > >>>>> publishing > >>>>>>> the > >>>>>>>>>> site? > >>>>>>>>>>>>>>>>>>> After > >>>>>>>>>>>>>>>>>>>>>>> looking at > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> docs it seems there are 3 options. > >>>> Being > >>>>>>> that > >>>>>>>> we > >>>>>>>>>> are > >>>>>>>>>>>>>>>>>>> using > >>>>>>>>>>>>>>>>>>>>>> git, I > >>>>>>>>>>>>>>>>>>>>>>>>>>>> would > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> thing that gitsubpub would be the > >>>> path of > >>>>>>> least > >>>>>>>>>>>>>>>>>>>> resistance?... > >>>>>>>>>>>>>>>>>>>>>>> But I > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> can't > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> find much on how to create the > >>>> jenkins > >>>>> job. > >>>>>>>>> Maybe > >>>>>>>>>>>>>>>>> this > >>>>>>>>>>>>>>>>>> is > >>>>>>>>>>>>>>>>>>>>>> listed > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> somewhere > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> else in the documentation? Does > >>>> anyone > >>>>>> have > >>>>>>>>> other > >>>>>>>>>>>>>>>>>>>> suggestions > >>>>>>>>>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>>>>>>>>>>>>> ideas? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Here is link to the guidelines -> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>> http://www.apache.org/dev/project-site.html > >>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> http://www.apache.org/dev/project-site.html>. > >>>> I > >>>>>> copy > >>>>>>>> and > >>>>>>>>>>>>>>>>> pasted > >>>>>>>>>>>>>>>>>>> some > >>>>>>>>>>>>>>>>>>>>>>>>>>>> info > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> below on the different methods of > >>>> website > >>>>>>>>>> publishing > >>>>>>>>>>>>>>>>> for > >>>>>>>>>>>>>>>>>>>> quick > >>>>>>>>>>>>>>>>>>>>>>>>>>>> reference. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Apache CMS, which provides a simple > >>>>>>>>> browser-based > >>>>>>>>>>>>>>>>> user > >>>>>>>>>>>>>>>>>>>>>>> interface for > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> editing, staging and publishing site > >>>>>> content > >>>>>>> in > >>>>>>>>>>>>>>>>>> Markdown, > >>>>>>>>>>>>>>>>>>>> HTML > >>>>>>>>>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>>>>>>>> any > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> other > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> source format for which support has > >>>> been > >>>>>>> added. > >>>>>>>>> See > >>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>> CMS > >>>>>>>>>>>>>>>>>>>>>>> reference > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <https://www.apache.org/dev/cmsref < > >>>>>>>>>>>>>>>>>>>>>>> https://www.apache.org/dev/cmsref>> and > >>>> adoption > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> < > >>>> https://www.apache.org/dev/cmsadoption > >>>>> < > >>>>>>>>>>>>>>>>>>>>>>> https://www.apache.org/dev/cmsadoption>> for > >>>>> more > >>>>>>>>> details. > >>>>>>>>>>>>>>>>> The > >>>>>>>>>>>>>>>>>>>> Apache > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> CMS uses svnpubsub as the underlying > >>>>>>> mechanism > >>>>>>>>> for > >>>>>>>>>>>>>>>>>>>> publishing > >>>>>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>>>> site. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> While this was home grown in Apache > >>>> and > >>>>> all > >>>>>>> the > >>>>>>>>> rage > >>>>>>>>>>>>>>>>> 7-8 > >>>>>>>>>>>>>>>>>>>> years > >>>>>>>>>>>>>>>>>>>>>> ago > >>>>>>>>>>>>>>>>>>>>>>> when > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> used this to port over OpenOffice.org > >>>>> with a > >>>>>>>>> reskin. > >>>>>>>>>>>>>>>>> This > >>>>>>>>>>>>>>>>>>>>> should > >>>>>>>>>>>>>>>>>>>>>>> not be > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> used. Infra wants people to stop and > >>>> there > >>>>>> are > >>>>>>>>>>>>>>>>> occasional > >>>>>>>>>>>>>>>>>>>>>>> publishing > >>>>>>>>>>>>>>>>>>>>>>>>>>>> issues. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - svnpubsub, which allows the static > >>>>>> contents > >>>>>>>> of > >>>>>>>>> a > >>>>>>>>>>>>>>>>>>>> designated > >>>>>>>>>>>>>>>>>>>>>> svn > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> folder > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (example < > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>> http://svn.apache.org/repos/asf/ant/site/ant/production/ > >>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>> http://svn.apache.org/repos/asf/ant/site/ant/production/ > >>>>>>>>>>>> ) > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> automatically published as the > >>>> project > >>>>> web > >>>>>>> site > >>>>>>>>> at > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://project.apache.org/ < > >>>>>>>>>>>>>>>>> http://project.apache.org/ > >>>>>>>>>>>>>>>>>>> . > >>>>>>>>>>>>>>>>>>>> The > >>>>>>>>>>>>>>>>>>>>>>> project team can use any site build > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> mechanism it wants as long as the > >>>> above > >>>>>>>>>> requirements > >>>>>>>>>>>>>>>>> are > >>>>>>>>>>>>>>>>>>>> met. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The CMS also uses svnpubsub. Not many > >>>> new > >>>>>>>> projects > >>>>>>>>>> or > >>>>>>>>>>>>>>>>>>>> podlings > >>>>>>>>>>>>>>>>>>>>>> are > >>>>>>>>>>>>>>>>>>>>>>> using > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Subversion other than as required for > >>>>>>> releases. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - gitpubsub, which allows the static > >>>>>> contents > >>>>>>>> of > >>>>>>>>> a > >>>>>>>>>>>>>>>>>>>> designated > >>>>>>>>>>>>>>>>>>>>>> git > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> repository to be served as the > >>>> website > >>>>> for > >>>>>> a > >>>>>>>>>> project. > >>>>>>>>>>>>>>>>>> git > >>>>>>>>>>>>>>>>>>>>> based > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> websites > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> are typically maintained in a > >>>> asf-site > >>>>>> branch > >>>>>>>> to > >>>>>>>>> be > >>>>>>>>>>>>>>>>>>>> published > >>>>>>>>>>>>>>>>>>>>> as > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://project.apache.org < > >>>>>>>>>>>>>>>>> https://project.apache.org/ > >>>>>>>>>>>>>>>>>>> . > >>>>>>>>>>>>>>>>>>>>> They > >>>>>>>>>>>>>>>>>>>>>>> can be hosted from your primary > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> project > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> repo. Typically these will be built > >>>> as a > >>>>>>>> jenkins > >>>>>>>>>> job > >>>>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>>> buildbot > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> job. It > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is recommended that you only have a > >>>>> single > >>>>>>>> writer > >>>>>>>>>> to > >>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>> asf-site > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> branch to > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid potential conflicts. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I’ve just revised the Incubator’s site > >>>>> build > >>>>>>>> since > >>>>>>>>>> we > >>>>>>>>>>>>>>>>>> have > >>>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>> mix > >>>>>>>>>>>>>>>>>>>>>>> of svn > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> legacy, current analysis and git > >>>> static > >>>>>>> content. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> See > >>>> https://github.com/apache/incubator < > >>>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/incubator> and the > >>>>>>>> README.md. > >>>>>>>>>> This > >>>>>>>>>>>>>>>>> is > >>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> jBake site with two Jenkins build > >>>> steps. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This should be the approach. Two > >>>> areas for > >>>>>>>> further > >>>>>>>>>>>>>>>>>>>> discussion. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (1) Does the project wish to create > >>>>>>>> documentation > >>>>>>>>>> in a > >>>>>>>>>>>>>>>>>> new > >>>>>>>>>>>>>>>>>>>>>>> repository - > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> say apache/incubator-heron-site > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Or should the build use an asf-site > >>>>> branch > >>>>>>> in > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> apache/incubator-heron which just > >>>> keeps > >>>>> the > >>>>>>>>> deployed > >>>>>>>>>>>>>>>>>>> content. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (2) Does the website Jenkins box > >>>> already > >>>>>>> support > >>>>>>>>> the > >>>>>>>>>>>>>>>>>> build > >>>>>>>>>>>>>>>>>>>>>>> requirements. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hugo --- Static site generator > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> GulpJS --- Build tool for static > >>>> assets > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Twitter Bootstrap --- Sass/CSS and > >>>>>>> JavaScript > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Documentation Setup > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Running the Heron documentation > >>>> locally > >>>>>>>> requires > >>>>>>>>>>>>>>>>> that > >>>>>>>>>>>>>>>>>> you > >>>>>>>>>>>>>>>>>>>>> have > >>>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> following installed: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Make > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Node.js > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> npm > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> pip - install PyYAML>=3.12 > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Go (make sure that your GOPATH and > >>>>> GOROOT > >>>>>>> are > >>>>>>>>> set) > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> What versions of the above and we can > >>>>> check > >>>>>>> with > >>>>>>>>>> Infra > >>>>>>>>>>>>>>>>>>>> through > >>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [email protected] <mailto: > >>>>> [email protected] > >>>>>>> > >>>>>>>>> email. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Regards, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Dave > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Fri, Mar 22, 2019 at 10:50 AM > >>>> Josh > >>>>>>> Fischer > >>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> [email protected] <mailto: > >>>> [email protected] > >>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I have some time free over the next > >>>>>> week, I > >>>>>>>> can > >>>>>>>>>>>>>>>>> look > >>>>>>>>>>>>>>>>>>> into > >>>>>>>>>>>>>>>>>>>>>>> fixing the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> build.. However, I think we should > >>>>> figure > >>>>>>> out > >>>>>>>>> the > >>>>>>>>>>>>>>>>> repo > >>>>>>>>>>>>>>>>>>>>>> situation > >>>>>>>>>>>>>>>>>>>>>>>>>>>> first > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> with > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the submodule that is tied to the > >>>>>>>>> documentation. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> My responses are in *bold. * > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Fri, Mar 22, 2019 at 12:26 PM > >>>> Dave > >>>>>>> Fisher > >>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> [email protected] <mailto: > >>>>>> [email protected] > >>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi - > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for asking. This has been > >>>> on my > >>>>>>> list > >>>>>>>> to > >>>>>>>>>>>>>>>>>> discuss > >>>>>>>>>>>>>>>>>>>> with > >>>>>>>>>>>>>>>>>>>>>> the > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Heron > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> community. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The website is seriously > >>>>> non-compliant. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mar 22, 2019, at 9:38 AM, Josh > >>>>>>> Fischer < > >>>>>>>>>>>>>>>>>>>>>>> [email protected] <mailto: > >>>> [email protected] > >>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hey All, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> With the heavy lifting behind us > >>>> on > >>>>> the > >>>>>>>> Bazel > >>>>>>>>>>>>>>>>>>> upgrade, I > >>>>>>>>>>>>>>>>>>>>>>> think the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> next > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> task we should tackle is fixing > >>>> the > >>>>>>> public > >>>>>>>>>> docs. > >>>>>>>>>>>>>>>>> I > >>>>>>>>>>>>>>>>>>> have > >>>>>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>>>>>> few > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> questions > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> about them. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. Are they still to be served > >>>> from > >>>>> GH > >>>>>>>> pages? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> No. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. If not where do they need to > >>>> live? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It should be on Apache servers as > >>>>>>>>>>>>>>>>> heron.apache.org < > >>>>>>>>>>>>>>>>>>>>>>> http://heron.apache.org/> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://heron.apache.org/ < > >>>>>>>>>>>>>>>>> http://heron.apache.org/>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Many projects build through > >>>> Jenkins. > >>>>>> There > >>>>>>>> are > >>>>>>>>>>>>>>>>>>>> requirements > >>>>>>>>>>>>>>>>>>>>>>> for the > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> site > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> which are scanned. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> There is a page here (needs some > >>>>>> updates) > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>> https://incubator.apache.org/guides/sites.html > >>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> > >>>> https://incubator.apache.org/guides/sites.html> > >>>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>> https://incubator.apache.org/guides/sites.html > >>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> > >>>> https://incubator.apache.org/guides/sites.html>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Some projects keep a separate > >>>> GitHub > >>>>>>>>> repository > >>>>>>>>>>>>>>>>> for > >>>>>>>>>>>>>>>>>>> their > >>>>>>>>>>>>>>>>>>>>>>> website. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * I would recommend that we move > >>>> the > >>>>>> docs > >>>>>>>> out > >>>>>>>>>> of > >>>>>>>>>>>>>>>>>> this > >>>>>>>>>>>>>>>>>>>> repo > >>>>>>>>>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>>>>>>>> at > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> least > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> remove the submodule. Working > >>>> within > >>>>> the > >>>>>>>>>> submodule > >>>>>>>>>>>>>>>>>> has > >>>>>>>>>>>>>>>>>>>> been > >>>>>>>>>>>>>>>>>>>>>>> quite a > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> difficult task.* > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> There is a lot wrong with the > >>>> current > >>>>>>>> website. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This page was put onto the > >>>> Incubator > >>>>>>> website > >>>>>>>>>> this > >>>>>>>>>>>>>>>>>> week. > >>>>>>>>>>>>>>>>>>>>> (It’s > >>>>>>>>>>>>>>>>>>>>>>> been > >>>>>>>>>>>>>>>>>>>>>>>>>>>> my > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> “distraction” the last few weeks.) > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>> https://incubator.apache.org/clutch/heron.html#errata > >>>>>>>>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://incubator.apache.org/clutch/heron.html#errata> > >>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>> https://incubator.apache.org/clutch/heron.html#errata > >>>>>>>>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>> https://incubator.apache.org/clutch/heron.html#errata > >>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Check out that almost all ASF > >>>> links, > >>>>>>>>> trademarks, > >>>>>>>>>>>>>>>>>>>>> disclaimer, > >>>>>>>>>>>>>>>>>>>>>>> and > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> copyrights are not correct on a > >>>> site > >>>>>> scan > >>>>>>>> that > >>>>>>>>>> is > >>>>>>>>>>>>>>>>>>>>>> periodically > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> performed. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>> https://whimsy.apache.org/pods/project/heron > >>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> https://whimsy.apache.org/pods/project/heron> > >>>> < > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>> https://whimsy.apache.org/pods/project/heron > >>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>>> https://whimsy.apache.org/pods/project/heron > >>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 3. If I remember correctly, some > >>>>> steps > >>>>>> in > >>>>>>>> the > >>>>>>>>>>>>>>>>>> Makefile > >>>>>>>>>>>>>>>>>>>> are > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> currently > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> broken for building the static > >>>>> assets. > >>>>>>>> Once > >>>>>>>>>>>>>>>>> those > >>>>>>>>>>>>>>>>>>>> issues > >>>>>>>>>>>>>>>>>>>>>> are > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> resolved > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> there anything else we need to > >>>> do to > >>>>>>>> release > >>>>>>>>>> new > >>>>>>>>>>>>>>>>> set > >>>>>>>>>>>>>>>>>>> of > >>>>>>>>>>>>>>>>>>>>>> docs? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Follow what I listed on 2. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> What technology is used to build > >>>>> assets > >>>>>>>>>> currently? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * It looks like is a mix of > >>>>>>> technologies.. > >>>>>>>>> The > >>>>>>>>>>>>>>>>> main > >>>>>>>>>>>>>>>>>>> one > >>>>>>>>>>>>>>>>>>>>>> being > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Gulp. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For generating java docs Bazel is > >>>> used > >>>>> to > >>>>>>>> query > >>>>>>>>>>>>>>>>>> targets. > >>>>>>>>>>>>>>>>>>>>>>> Generating > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> python > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> docs pdoc is used. * > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 4. Does updating the docs > >>>> require a > >>>>>> vote? > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Not normally. The Podling can > >>>> decide > >>>>> if > >>>>>>> you > >>>>>>>>> want > >>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>>> use > >>>>>>>>>>>>>>>>>>>> RTC > >>>>>>>>>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>>>>>>>> CTR. > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Since > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> everything is in version control I > >>>>> would > >>>>>>>> lean > >>>>>>>>> to > >>>>>>>>>>>>>>>>> CTR! > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Regards, > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Dave > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Josh > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>>>>>> Sent from A Mobile Device > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>>>> Sent from A Mobile Device > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>> Sent from A Mobile Device > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> -- > >>>> Sent from Gmail Mobile > >>>> > >>> > > >
