You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Greg Stein <gs...@gmail.com> on 2023/08/22 02:19:45 UTC
switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
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 <gs...@gmail.com> 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 <da...@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]
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by Ifo Ikede <af...@gmail.com>.
I am really happy to hear about this renewed uptake and interest in
reviving bloodhound.
I work fulltime as a linux sys admin, and also have used Trac
https://trac.edgewall.org back in 2008 and would love to be able to use it
to manage multiple projects.
SO you can count me in for helping with documentation , testing and also
managing or monitoring servers.
Regards,
ifo
On Fri, Aug 25, 2023 at 3:27 PM Greg Stein <gs...@gmail.com> wrote:
> 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 <ch...@apache.org> 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 <gs...@gmail.com> 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 <gj...@apache.org> 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 <gs...@gmail.com>
> > 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 <
> > > daniel@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]
> > > > >>
> > > > >
> > > >
> > >
> >
>
--
------------------------------------------------------
Ifo Ikede
Creating Wealthy, Healthy and Healing communities
http://eblog.ifomation.com (401) 314-8436 afrohealer@gmail.com
--------------------------------------
p.s . Want free leads? you can get free unlimited free leads forever
<http://ifomation.xyz>from http://ifomation.xyz
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by Greg Stein <gs...@gmail.com>.
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 <ch...@apache.org> 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 <gs...@gmail.com> 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 <gj...@apache.org> 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 <gs...@gmail.com>
> 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 <
> > daniel@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]
> > > >>
> > > >
> > >
> >
>
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by John Chambers <ch...@apache.org>.
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 <gs...@gmail.com> 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 <gj...@apache.org> 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 <gs...@gmail.com> 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 <
> daniel@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]
> > >>
> > >
> >
>
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by Greg Stein <gs...@gmail.com>.
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 <gj...@apache.org> 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 <gs...@gmail.com> 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 <da...@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]
> >>
> >
>
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by Gary Martin <gj...@apache.org>.
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 <gs...@gmail.com> 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 <da...@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]
>>
>
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by Greg Stein <gs...@gmail.com>.
Oh. ...
Looking: you're right. It requires signing into Confluence, which means
having an Apache account. Sorry about that. Investigating why it isn't
public.
Cheers,
-g
On Tue, Aug 22, 2023 at 5:55 AM Nikolay Tsanov <tz...@gmail.com> wrote:
> Fantastic idea!
>
> However, the Confluence page you provided responds with "We can't find that
> page. This could be because: * The page doesn't exist; *The page exists,
> but you don't have view permission for that space.".
>
> Is it because I am not on the contributors roster yet?
>
> Thanks,
>
> Nikolay
> +1-819-635-7198
>
> On Mon, Aug 21, 2023 at 10:20 PM Greg Stein <gs...@gmail.com> 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 <gs...@gmail.com> 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 <daniel@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]
> >
>
Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)
Posted by Nikolay Tsanov <tz...@gmail.com>.
Fantastic idea!
However, the Confluence page you provided responds with "We can't find that
page. This could be because: * The page doesn't exist; *The page exists,
but you don't have view permission for that space.".
Is it because I am not on the contributors roster yet?
Thanks,
Nikolay
+1-819-635-7198
On Mon, Aug 21, 2023 at 10:20 PM Greg Stein <gs...@gmail.com> 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 <gs...@gmail.com> 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 <da...@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]
>