Re: [bloodhound-site] branch asf-site updated: stage the test

[Greg Stein]

Oh, and I didn't touch download.cgi and download.html, as Daniel switched
to using closer.lua ... the pages are still there, for when we want to
bring back a custom download page


On Fri, Aug 25, 2023 at 8:18 PM Greg Stein  wrote:

> My commit message was wrong. The test/staging site is:
> https://bloodhound-test.staged.apache.org/
>
> There are differences because I upgraded to Bootstrap 5.3.1 when moving to
> Pelican. So a good chunk of styling needs to be fixed.
>
> I did not convert index.html to Markdown at this time (tho it is sitting
> in index.md). It's still a bunch of raw HTML, wrapped by the page template
> at theme/templates/page.html
>
> Please feel free to submit Pull Requests to fix the (Bootstrap) styling,
> the site.css file, and move some stuff from HTML to Markdown. (and note
> that we're using GitHub Flavored Markdown; use those docs for syntax)
>
> When it "looks good", then we can pull the lever to publish to
> bloodhound.a.o instead of the staging site.
>
> Cheers,
> -g
>
> On Fri, Aug 25, 2023 at 8:13 PM  wrote:
>
>> This is an automated email from the ASF dual-hosted git repository.
>>
>> gstein pushed a commit to branch asf-site
>> in repository https://gitbox.apache.org/repos/asf/bloodhound-site.git
>>
>>
>> The following commit(s) were added to refs/heads/asf-site by this push:
>>  new 7a4eabb  stage the test
>> 7a4eabb is described below
>>
>> commit 7a4eabbd0a0170b85cfd195e40fe285041bf4b2e
>> Author: Greg Stein 
>> AuthorDate: Fri Aug 25 21:12:26 2023 -0400
>>
>> stage the test
>>
>> This should publish the site to bloodhound-test.a.o for review
>> ---
>>  .asf.yaml | 14 +++---
>>  1 file changed, 3 insertions(+), 11 deletions(-)
>>
>> diff --git a/.asf.yaml b/.asf.yaml
>> index a844ed3..4c4e3df 100644
>> --- a/.asf.yaml
>> +++ b/.asf.yaml
>> @@ -1,11 +1,3 @@
>> -pelican:
>> -  target:   asf-site
>> -  whoami:   main
>> -
>> -github:
>> -  description:  "Apache Bloodhound Website Repository"
>> -  homepage: https://bloodhound.apache.org/
>> -  labels:
>> -- bloodhound
>> -- website
>> -- pelican
>> +staging:
>> +  profile: test
>> +  whoami:  asf-site
>>
>>

Re: [bloodhound-site] branch asf-site updated: stage the test

[Greg Stein]

My commit message was wrong. The test/staging site is:
https://bloodhound-test.staged.apache.org/

There are differences because I upgraded to Bootstrap 5.3.1 when moving to
Pelican. So a good chunk of styling needs to be fixed.

I did not convert index.html to Markdown at this time (tho it is sitting in
index.md). It's still a bunch of raw HTML, wrapped by the page template at
theme/templates/page.html

Please feel free to submit Pull Requests to fix the (Bootstrap) styling,
the site.css file, and move some stuff from HTML to Markdown. (and note
that we're using GitHub Flavored Markdown; use those docs for syntax)

When it "looks good", then we can pull the lever to publish to
bloodhound.a.o instead of the staging site.

Cheers,
-g

On Fri, Aug 25, 2023 at 8:13 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> gstein pushed a commit to branch asf-site
> in repository https://gitbox.apache.org/repos/asf/bloodhound-site.git
>
>
> The following commit(s) were added to refs/heads/asf-site by this push:
>  new 7a4eabb  stage the test
> 7a4eabb is described below
>
> commit 7a4eabbd0a0170b85cfd195e40fe285041bf4b2e
> Author: Greg Stein 
> AuthorDate: Fri Aug 25 21:12:26 2023 -0400
>
> stage the test
>
> This should publish the site to bloodhound-test.a.o for review
> ---
>  .asf.yaml | 14 +++---
>  1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/.asf.yaml b/.asf.yaml
> index a844ed3..4c4e3df 100644
> --- a/.asf.yaml
> +++ b/.asf.yaml
> @@ -1,11 +1,3 @@
> -pelican:
> -  target:   asf-site
> -  whoami:   main
> -
> -github:
> -  description:  "Apache Bloodhound Website Repository"
> -  homepage: https://bloodhound.apache.org/
> -  labels:
> -- bloodhound
> -- website
> -- pelican
> +staging:
> +  profile: test
> +  whoami:  asf-site
>
>

Re: Apache Bloodhound will be moving to the Attic

[Greg Stein]

Applied, and live. Thanks!!


On Fri, Aug 25, 2023 at 3:02 PM Daniel Brownridge 
wrote:

> Hi Greg,
>
> I've focused on updating the content of the current site to make it a
> little more friendly to new comers who are currently presented with dead
> links.
>
> So here is a patch to the current static website. It only affects
> index.html.
>
> Created by:
>
> $ svn diff index.html > siteupdate.patch
>
> Summary of changes:
>
>- Replace dead links to live.bloodhound.apache.org with most recent
>web.archive.org capture.
>- All original links are still present in the code just commented out
>so can be easily switched back when needed.
>- Brought details of the mailing list onto the main page.
>- Added a brief note about current state of the project in the getting
>involved section.
>- Minor tweaks to wording to make the page make sense given current
>situation.
>- Some re-formatting of dense HTML to make it easy to work with for
>manual editing.
>
> I have noted that there has been consensus reached to switch to Pelican
> (which I don't know). I thought I'd submit this patch anyway since I've
> done it and it should be quick to apply in the meantime while you're
> looking at Pelican. If Pelican is pretty much ready to go then the content
> of this patch may still be useful.
>
> Please could you review and apply if appropriate.
>
> Many thanks,
>
> Daniel
>
> *Daniel Brownridge*
> dan...@freshnewpage.com
> +44 779 138 5626
> On 21/08/2023 18:08, Greg Stein wrote:
>
> https://svn.apache.org/repos/asf/bloodhound/site/
>
> It is read-only, but I can override that to apply any patches you send to
> dev@
>
> Cheers,
> -g
>
>
> On Mon, Aug 21, 2023, 01:17 Daniel Brownridge 
> wrote:
>
>> Hi Gary,
>>
>> Untill we can get live back it might be a good idea tput some more basic
>> info on the landing page and remove the dead links etc.
>>
>> How is the website (bloodhound.apache.org) hosted / updated / where does
>> the code live?
>>
>> Happy to take on maintenance if that helps would just need some help
>> getting started?
>>
>> If this can be done by email great but also can co-ordinate a time when
>> both on-line if that helps?
>>
>> Cheers,
>> Daniel
>>
>> On Mon, 21 Aug 2023, 03:47 Gary Martin,  wrote:
>>
>>> Hi,
>>>
>>> It is certainly good to see some interest in getting things going again.
>>> I should probably have said something sooner but Greg did summarise the
>>> situation pretty well.
>>>
>>> From the point of view of where code is submitted, I totally understand
>>> the desire to use git rather than subversion when that is what people are
>>> likely to be most used to. When this has been discussed before I'm pretty
>>> sure we came to the conclusion that use of git would reduce barriers to
>>> participation. I don't want to be forcing anyone to use subversion.
>>>
>>> The bloodhound-core repo is already git only and if GitHub PRs are what
>>> the development community wants to use, we should support that.
>>>
>>> Meanwhile, I can't say I know if the older bloodhound repo can accept
>>> changes via gitbox or GitHub. If it is not currently set up correctly for
>>> that, we may still want to delay making changes until we decide that we are
>>> going to continue 0.8 development.  I imagine that INFRA has made it easy
>>> to do but it feels better not to ask for work that may not prove necessary.
>>> That said, if enough people disagree with my suggestion here then I will
>>> get to requesting it.
>>>
>>> I think that in principle we can get live.bloodhound working again. I
>>> can of course look into this. Using GitHub for issues for a while is fine
>>> though.
>>>
>>> I noted some potential concern about this list getting busy because of a
>>> lack of an issue tracker. I would still be encouraging us to use this
>>> mailing list for some discussion when issue tracking is restored. It
>>> provides a good point of contact for people who don't want to go through
>>> all the tickets. That is not to say that everything has to be discussed but
>>> some commentary that allows others to be brought into the discussion about
>>> the direction we are taking should be useful.
>>>
>>> There is probably plenty I haven't addressed here but I think that the
>>> direction of the project is an important one to discuss further. My
>>> experimental code has certainly not got particularly far in its objectives
>>> at this point. There are obviously pros and cons to such an approach.
>>>
>>> In particular I would note that a clean(ish) break from Trac brings with
>>> it opportunities to control all of what it is to be the issue tracker while
>>> building on sane webserver frameworks. It does, however, lead to the
>>> question of what such a break would ultimately look like. Is feature parity
>>> something that would be desired? Would we at least be happy to avoid
>>> support for trac plugins?
>>>
>>> Obviously continuing the development of Apache Bloodhound 0.8 certainly
>>> is not out 

Re: Apache Bloodhound will be moving to the Attic

[Daniel Brownridge]

Hi Greg,

I've focused on updating the content of the current site to make it a 
little more friendly to new comers who are currently presented with dead 
links.


So here is a patch to the current static website. It only affects 
index.html.


Created by:

$ svn diff index.html > siteupdate.patch

Summary of changes:

 * Replace dead links to live.bloodhound.apache.org with most recent
   web.archive.org capture.
 * All original links are still present in the code just commented out
   so can be easily switched back when needed.
 * Brought details of the mailing list onto the main page.
 * Added a brief note about current state of the project in the getting
   involved section.
 * Minor tweaks to wording to make the page make sense given current
   situation.
 * Some re-formatting of dense HTML to make it easy to work with for
   manual editing.

I have noted that there has been consensus reached to switch to Pelican 
(which I don't know). I thought I'd submit this patch anyway since I've 
done it and it should be quick to apply in the meantime while you're 
looking at Pelican. If Pelican is pretty much ready to go then the 
content of this patch may still be useful.


Please could you review and apply if appropriate.

Many thanks,

Daniel

*Daniel Brownridge*
dan...@freshnewpage.com
+44 779 138 5626

On 21/08/2023 18:08, Greg Stein wrote:

https://svn.apache.org/repos/asf/bloodhound/site/

It is read-only, but I can override that to apply any patches you send 
to dev@


Cheers,
-g


On Mon, Aug 21, 2023, 01:17 Daniel Brownridge 
 wrote:


Hi Gary,

Untill we can get live back it might be a good idea tput some more
basic info on the landing page and remove the dead links etc.

How is the website (bloodhound.apache.org
) hosted / updated / where does the
code live?

Happy to take on maintenance if that helps would just need some
help getting started?

If this can be done by email great but also can co-ordinate a time
when both on-line if that helps?

Cheers,
Daniel

On Mon, 21 Aug 2023, 03:47 Gary Martin, 
wrote:

Hi,

It is certainly good to see some interest in getting things
going again. I should probably have said something sooner but
Greg did summarise the situation pretty well.

From the point of view of where code is submitted, I totally
understand the desire to use git rather than subversion when
that is what people are likely to be most used to. When this
has been discussed before I'm pretty sure we came to the
conclusion that use of git would reduce barriers to
participation. I don't want to be forcing anyone to use
subversion.

The bloodhound-core repo is already git only and if GitHub PRs
are what the development community wants to use, we should
support that.

Meanwhile, I can't say I know if the older bloodhound repo can
accept changes via gitbox or GitHub. If it is not currently
set up correctly for that, we may still want to delay making
changes until we decide that we are going to continue 0.8
development.  I imagine that INFRA has made it easy to do but
it feels better not to ask for work that may not prove
necessary. That said, if enough people disagree with my
suggestion here then I will get to requesting it.

I think that in principle we can get live.bloodhound working
again. I can of course look into this. Using GitHub for issues
for a while is fine though.

I noted some potential concern about this list getting busy
because of a lack of an issue tracker. I would still be
encouraging us to use this mailing list for some discussion
when issue tracking is restored. It provides a good point of
contact for people who don't want to go through all the
tickets. That is not to say that everything has to be
discussed but some commentary that allows others to be brought
into the discussion about the direction we are taking should
be useful.

There is probably plenty I haven't addressed here but I think
that the direction of the project is an important one to
discuss further. My experimental code has certainly not got
particularly far in its objectives at this point. There are
obviously pros and cons to such an approach.

In particular I would note that a clean(ish) break from Trac
brings with it opportunities to control all of what it is to
be the issue tracker while building on sane webserver
frameworks. It does, however, lead to the question of what
such a break would ultimately look like. Is feature parity
something that would be desired? Would we at least be happy to
avoid support for trac plugins?

Obviously continuing the development 

Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)

[Greg Stein]

And that makes (3) +1 binding votes. I've started setting up a
Pelican-based site. Should have it committed today or tomorrow.

I'll have it go to staging until it looks correct, then it will take over
as the source for the primary site.

Cheers,
-g


On Thu, Aug 24, 2023 at 10:20 AM John Chambers  wrote:

> I am happy enough to support moving the site to using Pelican and to having
> it's own repo to make life easier when maintaining it.
>
> Cheers
>
> John .
>
> On Tue, 22 Aug 2023 at 16:55, Greg Stein  wrote:
>
> > The site is outside of {trunks, tags, branches} so the auto-propagate
> > doesn't see it.
> >
> > The Pelican migration will be easy once we get a third binding vote
> > (myself, Gary so far).
> >
> > Daniel: please feel free to post site patches, rather than getting held
> up
> > awaiting migration.
> >
> > Cheers,
> > -g
> >
> >
> > On Tue, Aug 22, 2023 at 9:48 AM Gary Martin  wrote:
> >
> > > For some reason I thought that the site code might also be in the
> GitHub
> > > mirror of the main bloodhound.
> > >
> > > Anyway, personally I would be happy enough to support moving the site
> to
> > > its own repo and using pelican. Very good suggestions.
> > >
> > > Cheers,
> > > Gary
> > >
> > > On 22/08/2023 03:19, Greg Stein wrote:
> > > > Rather than using pure HTML/etc, I would suggest that we switch to
> > using
> > > > Pelican for site generation (sources move to markdown). Infra has
> > > provided
> > > > an automated workflow to move edits to published pages. See:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-PelicanCMS
> > > >
> > > > We can create a git repo named "bloodhound-site", and an edit/push
> of a
> > > .md
> > > > file would publish the page within a few seconds.
> > > >
> > > > There are a few publishing options, but Pelican is straightforward,
> > > > supported by Infra, and the tool is Python-based which is a "nice to
> > > have"
> > > > for this community (to better understand the tooling).
> > > >
> > > > Thoughts?
> > > >
> > > > Cheers,
> > > > -g
> > > >
> > > > On Mon, Aug 21, 2023 at 12:08 PM Greg Stein 
> wrote:
> > > >
> > > >
> > > >> https://svn.apache.org/repos/asf/bloodhound/site/
> > > >>
> > > >> It is read-only, but I can override that to apply any patches you
> send
> > > to
> > > >> dev@
> > > >>
> > > >> Cheers,
> > > >> -g
> > > >>
> > > >> On Mon, Aug 21, 2023, 01:17 Daniel Brownridge <
> > dan...@freshnewpage.com>
> > > >> wrote:
> > > >>
> > > >>
> > > >>> Hi Gary,
> > > >>>
> > > >>> Untill we can get live back it might be a good idea tput some more
> > > basic
> > > >>> info on the landing page and remove the dead links etc.
> > > >>>
> > > >>> How is the website (bloodhound.apache.org) hosted / updated /
> where
> > > does
> > > >>> the code live?
> > > >>>
> > > >>> Happy to take on maintenance if that helps would just need some
> help
> > > >>> getting started?
> > > >>>
> > > >>> If this can be done by email great but also can co-ordinate a time
> > when
> > > >>> both on-line if that helps?
> > > >>>
> > > >>> Cheers,
> > > >>> Daniel
> > > >>>
> > > >>>
> > > >> [snip]
> > > >>
> > > >
> > >
> >
>