Thank you, Enrico.
I have a co-worker is helping with designing the website with Jekyll now.
We will try to share with the community in a couple of days.
- Sijie
On Tue, Jun 27, 2017 at 12:22 PM, Enrico Olivelli
wrote:
> I read the wiki page and looks great.
> Let's do
I read the wiki page and looks great.
Let's do it.
I am not sure about the push via gut works but I will be happy to try.
If we approve this change I volunteer to do the migration if the website
from subversion to git.
Enrico
Il gio 22 giu 2017, 05:31 Jia Zhai ha scritto:
>
This is great to have a unified documentation place.
On Thu, Jun 22, 2017 at 10:31 AM, Sijie Guo wrote:
> FYI. I created a BP for this -
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=71012301
>
> - Sijie
>
> On Mon, Jun 5, 2017 at 10:45 AM, Sijie Guo
FYI. I created a BP for this -
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=71012301
- Sijie
On Mon, Jun 5, 2017 at 10:45 AM, Sijie Guo wrote:
>
>
> On Mon, Jun 5, 2017 at 10:20 AM, Enrico Olivelli
> wrote:
>
>> Il lun 5 giu 2017,
On Mon, Jun 5, 2017 at 10:20 AM, Enrico Olivelli
wrote:
> Il lun 5 giu 2017, 17:56 Sijie Guo ha scritto:
>
> > On Mon, Jun 5, 2017 at 3:07 AM, Flavio Junqueira wrote:
> >
> > > I don't have a super strong opinion here, but I'm not sure
Il lun 5 giu 2017, 17:56 Sijie Guo ha scritto:
> On Mon, Jun 5, 2017 at 3:07 AM, Flavio Junqueira wrote:
>
> > I don't have a super strong opinion here, but I'm not sure I understand
> > the concern. The textile files are stored in the repo, so any doc
On Mon, Jun 5, 2017 at 3:07 AM, Flavio Junqueira wrote:
> I don't have a super strong opinion here, but I'm not sure I understand
> the concern. The textile files are stored in the repo, so any doc changes
> should be reviewed and committed as any other code change, no? Granted
I don't have a super strong opinion here, but I'm not sure I understand the
concern. The textile files are stored in the repo, so any doc changes should be
reviewed and committed as any other code change, no? Granted that it is in the
hands of a committer to push the changes to the web site,
Our site is written using Textile, I found this
https://github.com/jekyll/jekyll-textile-converter maybe the switch to
Jekyll will be easy
The other problem will be to switch the cms, maybe just a request to
infra to switch to github pages will be enough
Enrico
2017-06-03 19:15 GMT+02:00 Sijie
I don't think there is any enforcements from Apache INFRA side. You can use
any technology for hosting website and documentation. I do see a lot of
projects using Jekyll-like solutions for the website, where they typically
have a separate XXX-site git repo and use gitpubsub (which is just a simply
It has been some time since you made this proposal, on some ticket.
At the moment I did not make any concrete proposal because I wanted to
study how to make the conversion.
I am in favour of switching to a more popular sokution like jekyll and
maybe markdown language
Using git will be good as
I'd like to raise another discussion about moving bookkeeper website from
CMS to other static generators (e.g. Jekyll, Hugo).
BookKeeper uses Apache CMS for generating the documentation and website
[1]. The website source code is hosted at a svn repo, which now becomes
obsolete from
our current
12 matches
Mail list logo