I agree the PR [1] is ready to be merged (no conflicts anymore and minor
differences are resolved as
well now). Also, merging the pull requests doesn't automatically switch over
serving of community.a.o
from svn to git. It will only be served from git after [2] is merged.
So what I'd suggest:
-
On Tue, Mar 31, 2020 at 3:43 PM Rich Bowen wrote:
> ...There's a MASSIVE PR here -
> https://github.com/apache/comdev-site/pull/5
>
> I have recommended we just merge it, and then deal with the fallout of
> the handful of things that will probably break...
+1
I have stored an archive of the curr
+1 to merge
I believe it is better to move forward :)
On Tue, 31 Mar 2020 at 20:43, Rich Bowen wrote:
> So ... bringing it back to the list.
>
> We chatted about this on Slack briefly, and we are still in the forklift
> process. There's a MASSIVE PR here -
> https://github.com/apache/comdev-site
So ... bringing it back to the list.
We chatted about this on Slack briefly, and we are still in the forklift
process. There's a MASSIVE PR here -
https://github.com/apache/comdev-site/pull/5
I have recommended we just merge it, and then deal with the fallout of
the handful of things that wi
On Tue, Mar 31, 2020 at 3:34 PM Bertrand Delacretaz
wrote:
> ...Turns out the content has moved to Git, see
> https://github.com/apache/comdev-site/blob/master/WEBSITE-HOWTO.txt
I have started to update the README at
https://github.com/apache/comdev-site , if someone has more info
please update i
On Tue, Mar 31, 2020 at 3:20 PM Bertrand Delacretaz
wrote:
...
> > https://svn.apache.org/repos/asf/comdev/site/trunk/WEBSITE-HOWTO.txt
> > should help...
Turns out the content has moved to Git, see
https://github.com/apache/comdev-site/blob/master/WEBSITE-HOWTO.txt
Not sure if and how the websi
On Tue, Mar 31, 2020 at 3:17 PM Bertrand Delacretaz
wrote:
> https://svn.apache.org/repos/asf/comdev/site/trunk/WEBSITE-HOWTO.txt
> should help...
I just pushed some unpublished changes via
https://cms.apache.org/community/publish?diff=1 so it looks like
that's still active.
-Bertrand
-
On Tue, Mar 31, 2020 at 3:13 PM Rich Bowen wrote:
> ...Specifically, I'm trying to make an edit to the site, and it turns out I
> don't know how...
FWIW, If things haven't changed yet (and I haven't seen a mention of
actual changes),
https://svn.apache.org/repos/asf/comdev/site/trunk/WEBSITE-HOWT
Can you update us as to where this is?
Specifically, I'm trying to make an edit to the site, and it turns out I
don't know how. Can you please update
https://community.apache.org/about/#about-this-website and
https://community.apache.org/newbiefaq.html#websitecms with the info
necessary for m
Hi,
The community has voted on moving over the current community.apache.org website
from the
CMS/SVN to be Git/Hugo based [1]
The vote passed with the following results:
+1 Rich Bowen (binding)
+1 Sebb (binding)
+1 Austin Bennett (non-binding)
+1 Aizhamal Nurmamat kyzy (non-binding)
+1 Willem N
Adding my +1 as well
On 2020/03/07 03:37:07, Ming Wen wrote:
> +1 (non-binding)
>
> Xin Wang 于2020年3月7日 周六上午11:22写道：
>
> > +1 (non-binding)
> >
> > - Xin
> >
> > Manish Sharma 于2020年3月6日周五 下午11:52写道：
> >
> > > +1
> > >
> > > On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek
> > wrote:
> > >
> > >
+1 (non-binding)
Xin Wang 于2020年3月7日 周六上午11:22写道：
> +1 (non-binding)
>
> - Xin
>
> Manish Sharma 于2020年3月6日周五 下午11:52写道：
>
> > +1
> >
> > On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek
> wrote:
> >
> > > +1 (no-binding)
> > >
> > > T.
> > >
> > >
> > > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma
+1 (non-binding)
- Xin
Manish Sharma 于2020年3月6日周五 下午11:52写道：
> +1
>
> On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek wrote:
>
> > +1 (no-binding)
> >
> > T.
> >
> >
> > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma
> > wrote:
> > >
> > > +1 (no-binding)
> > >
> > > Thanks and Regards,
> > > Adit
+1
On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek wrote:
> +1 (no-binding)
>
> T.
>
>
> On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma
> wrote:
> >
> > +1 (no-binding)
> >
> > Thanks and Regards,
> > Aditya Sharma
> >
> > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote:
> > >
> > > +1 (non-binding
+1 (no-binding)
T.
On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma wrote:
>
> +1 (no-binding)
>
> Thanks and Regards,
> Aditya Sharma
>
> On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote:
> >
> > +1 (non-binding). Hugo is great! Git even more so.
> >
> > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang
+1 (no-binding)
Thanks and Regards,
Aditya Sharma
On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote:
>
> +1 (non-binding). Hugo is great! Git even more so.
>
> On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang wrote:
>
> > +1 (no-binding)
> > I developed ShardingSphere website using Hugo, I like it.
>
+1 (non-binding). Hugo is great! Git even more so.
On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang wrote:
> +1 (no-binding)
> I developed ShardingSphere website using Hugo, I like it.
>
> On 2020/02/22 11:11:15, Roy Lenferink wrote:
> > Hi all,
> >
> > After this week's proposal [1] I'd like to sta
+1 (no-binding)
I developed ShardingSphere website using Hugo, I like it.
On 2020/02/22 11:11:15, Roy Lenferink wrote:
> Hi all,
>
> After this week's proposal [1] I'd like to start a formal vote on moving over
> community.a.o from the
> current Apache CMS/SVN to Hugo/Git.
>
> Involved steps:
+1 (no-binding)
I developed Airflow website using Hugo. It's fantastic.
https://airflow.apache.org/
https://github.com/apache/airflow-site
On Wed, Mar 4, 2020 at 2:12 AM Willem Jiang wrote:
>
> +1 (no-binding)
> For moving to a modern website builder :)
>
> On Sat, Feb 22, 2020 at 7:11 PM Roy Len
+1 (no-binding)
For moving to a modern website builder :)
On Sat, Feb 22, 2020 at 7:11 PM Roy Lenferink wrote:
>
> Hi all,
>
> After this week's proposal [1] I'd like to start a formal vote on moving over
> community.a.o from the
> current Apache CMS/SVN to Hugo/Git.
>
> Involved steps:
> - Crea
+1 (non-binding)
Hugo is much easier to manage than Jekyll from my personal experience as a
non-developer.
On Tue, Mar 3, 2020 at 4:03 PM sebb wrote:
> +1
>
> I suggest taking a snapshot of the current website (e.g. tag SVN) so
> the page names/content can be compared with the new site.
>
> On
+1
I suggest taking a snapshot of the current website (e.g. tag SVN) so
the page names/content can be compared with the new site.
On Mon, 24 Feb 2020 at 14:57, Rich Bowen wrote:
>
>
>
> On 2/22/20 6:11 AM, Roy Lenferink wrote:
> > Hi all,
> >
> > After this week's proposal [1] I'd like to start
On 2/22/20 6:11 AM, Roy Lenferink wrote:
Hi all,
After this week's proposal [1] I'd like to start a formal vote on moving over
community.a.o from the
current Apache CMS/SVN to Hugo/Git.
Involved steps:
- Create a comdev-site gitbox repository which will be synced with the current
comdev-si
+1 (non-binding)
On Sat, Feb 22, 2020 at 4:48 AM Bertrand Delacretaz
wrote:
> On Sat, Feb 22, 2020 at 12:11 PM Roy Lenferink
> wrote:
> > [X ] +1 for moving over from the CMS/svn to Hugo/git...
>
> I'm not familiar with Hugo but it's well known and looking at
> https://github.com/apache/comdev-
On Sat, Feb 22, 2020 at 12:11 PM Roy Lenferink wrote:
> [X ] +1 for moving over from the CMS/svn to Hugo/git...
I'm not familiar with Hugo but it's well known and looking at
https://github.com/apache/comdev-site/pull/5 it doesn't look hard to
manage.
-Bertrand
--
+1 for moving to git
-0 for hugo, as I believe we would have a bigger set of familiar people
comfortable contributing to Jekyll based website based on its wide adoption
at other places ata Apache.
On Sat, Feb 22, 2020 at 12:11 Roy Lenferink wrote:
> Hi all,
>
> After this week's proposal [1] I'd
+1 (non-binding) to switching to a git-based website
+0 (non-binding) to switching to Hugo
While I'm more familiar with Jekyll than Hugo, the switch to a
git-based website creates a *super* low bar to contribute to now for
Apache Accumulo, the primary project I contribute to at Apache, that I
thin
Hi all,
After this week's proposal [1] I'd like to start a formal vote on moving over
community.a.o from the
current Apache CMS/SVN to Hugo/Git.
Involved steps:
- Create a comdev-site gitbox repository which will be synced with the current
comdev-site repo on
GitHub.
- Rename 'trunk' to 'master
Hi,
On Wed, Feb 19, 2020 at 1:52 PM Roy Lenferink wrote:
> ...With Hugo I was able to keep all current URLs working...
I think keeping existing URLs (or redirecting from them) is an
important requirement that we missed earlier.
The comdev site has been around for quite some time so we have lots
To be completely clear, I'm NOT saying "don't use Hugo", I'm just
wanting to be sure that we aren't going down a road that will make
contribution across the Foundation even more of a patchwork. It sounds,
from other responses, that Hugo already has wider adoption here, which
is awesome.
On 2/
On 19/02/2020 06.52, Roy Lenferink wrote:
Hi Daniel / Rich,
To be honest, I completely forgot the .asf.yaml was able to do such things, my
bad.
Currently the .asf.yaml supports both Jekyll and Pelican. My previous
experience with Jekyll is that
it is really slow at incrementally generating co
Thanks Bertrand!
At Celix we are using Hugo as well, which indeed works pretty well :)
https://github.com/apache/celix-site
On 2020/02/19 09:49:50, Bertrand Delacretaz wrote:
> On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink wrote:
> > ...An example (for demo purposes only) of Hugo its output is
Hi Daniel / Rich,
To be honest, I completely forgot the .asf.yaml was able to do such things, my
bad.
Currently the .asf.yaml supports both Jekyll and Pelican. My previous
experience with Jekyll is that
it is really slow at incrementally generating content when file changes are
made (running o
On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink wrote:
> ...An example (for demo purposes only) of Hugo its output is available here:
> http://comdev-site.roylenferink.nl/
Nice, thank you very much for working on this, I think it's long overdue!
Us being geeks, it'll be hard to agree on tools, IMH
hugo is great ,fast ,and simple . content just focus markdown.
Tomasz Urbaszek 于2020年2月19日周三 下午5:23写道：
> We are using Hugo for https://airflow.apache.org and it works pretty well
> :)
>
> T.
>
> On Tue, Feb 18, 2020 at 8:47 PM Daniel Gruno wrote:
>
> > There are pelican auto-builds and auto-pub
We are using Hugo for https://airflow.apache.org and it works pretty well :)
T.
On Tue, Feb 18, 2020 at 8:47 PM Daniel Gruno wrote:
> There are pelican auto-builds and auto-publishing via .asf.yaml files
> already, as well as custom build steps being introduced on builbot 2.
>
> see https://s.a
There are pelican auto-builds and auto-publishing via .asf.yaml files
already, as well as custom build steps being introduced on builbot 2.
see https://s.apache.org/asfyaml for starters...
On 18/02/2020 13.45, Rich Bowen wrote:
I would like to hear more about Hugo, since it's not one that I've
I would like to hear more about Hugo, since it's not one that I've heard
of before.
There are a zillion different content frameworks out there, and I have
no preference for any of them except that the underlying file format is
standard-ish. Markdown, or something similar that can be easily
co
Forgot to mention:
An example (for demo purposes only) of Hugo its output is available here:
http://comdev-site.roylenferink.nl/
On 2020/02/18 19:07:09, Roy Lenferink wrote:
> Hi fellow comdev-ers,
>
> The e-mail from a few days ago asking to change the year from 2018 -> 2020
> triggered me a
Hi fellow comdev-ers,
The e-mail from a few days ago asking to change the year from 2018 -> 2020
triggered me and I
thought how this could be improved. Also, an 'Edit this page' button will
already help people to
contribute changes to the current website.
One way of doing this could be to star
40 matches
Mail list logo
