9:33 a.m.
Quack,
### A pinch of history
As a short introduction for those who do not know me as I rarely post
here: I'm part of Red Hat OSPO Comminfra Team (previously OSPO was
called OSAS) and currently hosting and taking care of the website.
This topic has been discussed many times: neither people writing the
site neither us for the maintenance are happy with the current state of
affair. But we had not real plan and picking a random tool which might
lead to similar problems and without any way to support it properly was
not very appealing. Moreover we tried migrating to Middleman 4, the
obvious path to modernization, but this happened to be more complicated
than expected and this new version had terrible performance problems. As
you now version 3 is already slow, and that's quite an understatement.
In the meanwhile a few things have changed, and people taking care of
the website too, so let's talk about the current situation.
(very short version of the history around this)
### Why now?
What has changed:
* several projects moved to Jekyll, a software we were already
investigating at the time and is being used by Google Pages (they
created it in fact), and they were very happy with the result; we
believe it has the necessary features, it is well maintained because
Google uses it heavily, and it's very fast
* we've tried Jekyll ourselves, we're happy too, and we do have the
Ansible playbooks and tooling to deploy it now
* over time the website had some waves of cleanup (still needs quite
some love though) and recently the blog moved to WordPress to get
comment support and a more friendly interface (see OVIRT-2652) which
allowed more cleanup (see #2030)
With the blog separated and a lot of custom Ruby code removed, the
tooling ready, I believe we can now work on migrating the content.
We may realize Jekyll is not the right tool, but people seemed to like
the idea at the time and current experience seem to indicate it should
improve things and be maintainable. The goal here is to experiment and
switch to production only if we're happy with it.
### Early work
I have started a branch called 'jekyll_migration' to put my work on it.
This is very early work (I just started), I already hit various
difficulties, and I can't commit 100% of my time on it so it will
require some time.
Several of my changes happened to not be really specific to the
migration, and the current site would benefit from these
fixes/cleanups/simplifications… thus I'll extracts these changes and
create separate PRs for master.
If you wish to help, then you can contact me directly or reply to this
thread. You may also create PRs to this topic branch, but please do not
push anything directly.
Regards.
\_o<
1:28 p.m.
Hi everyone,
This goes along with this thread and updates to the website. I've worked on
some redesign work for the website and opened an issue that features the
desktop and mobile wireframes for the proposed site redesign:
https://github.com/oVirt/ovirt-site/issues/1968 Feel free to check them out
and let me know what you think. Any feedback is welcome.
Best,
Laura
On Thu, Jul 25, 2019 at 3:35 AM Marc Dequènes (Duck) <duck(a)redhat.com>
wrote:
Quack,
### A pinch of history
As a short introduction for those who do not know me as I rarely post
here: I'm part of Red Hat OSPO Comminfra Team (previously OSPO was
called OSAS) and currently hosting and taking care of the website.
This topic has been discussed many times: neither people writing the
site neither us for the maintenance are happy with the current state of
affair. But we had not real plan and picking a random tool which might
lead to similar problems and without any way to support it properly was
not very appealing. Moreover we tried migrating to Middleman 4, the
obvious path to modernization, but this happened to be more complicated
than expected and this new version had terrible performance problems. As
you now version 3 is already slow, and that's quite an understatement.
In the meanwhile a few things have changed, and people taking care of
the website too, so let's talk about the current situation.
(very short version of the history around this)
### Why now?
What has changed:
* several projects moved to Jekyll, a software we were already
investigating at the time and is being used by Google Pages (they
created it in fact), and they were very happy with the result; we
believe it has the necessary features, it is well maintained because
Google uses it heavily, and it's very fast
* we've tried Jekyll ourselves, we're happy too, and we do have the
Ansible playbooks and tooling to deploy it now
* over time the website had some waves of cleanup (still needs quite
some love though) and recently the blog moved to WordPress to get
comment support and a more friendly interface (see OVIRT-2652) which
allowed more cleanup (see #2030)
With the blog separated and a lot of custom Ruby code removed, the
tooling ready, I believe we can now work on migrating the content.
We may realize Jekyll is not the right tool, but people seemed to like
the idea at the time and current experience seem to indicate it should
improve things and be maintainable. The goal here is to experiment and
switch to production only if we're happy with it.
### Early work
I have started a branch called 'jekyll_migration' to put my work on it.
This is very early work (I just started), I already hit various
difficulties, and I can't commit 100% of my time on it so it will
require some time.
Several of my changes happened to not be really specific to the
migration, and the current site would benefit from these
fixes/cleanups/simplifications… thus I'll extracts these changes and
create separate PRs for master.
If you wish to help, then you can contact me directly or reply to this
thread. You may also create PRs to this topic branch, but please do not
push anything directly.
Regards.
\_o<
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ERLDSOGZQGL...
--
Laura Wright
She/Her/Hers
UXD Team
Red Hat Massachusetts <https://www.redhat.com/>
314 Littleton Rd
lwright(a)redhat.com
<https://www.redhat.com/>
2:26 p.m.
Hi Marc,
Currently I don't find the blog content on the ovirt-site repository [1].
In which repository can it be found?
Thanks
[1] https://github.com/oVirt/ovirt-site
On Thu, Jul 25, 2019 at 2:30 PM Laura Wright <lwright(a)redhat.com> wrote:
Hi everyone,
This goes along with this thread and updates to the website. I've worked
on some redesign work for the website and opened an issue that features the
desktop and mobile wireframes for the proposed site redesign:
https://github.com/oVirt/ovirt-site/issues/1968 Feel free to check them
out and let me know what you think. Any feedback is welcome.
Best,
Laura
On Thu, Jul 25, 2019 at 3:35 AM Marc Dequènes (Duck) <duck(a)redhat.com>
wrote:
> Quack,
>
>
> ### A pinch of history
>
> As a short introduction for those who do not know me as I rarely post
> here: I'm part of Red Hat OSPO Comminfra Team (previously OSPO was
> called OSAS) and currently hosting and taking care of the website.
>
>
> This topic has been discussed many times: neither people writing the
> site neither us for the maintenance are happy with the current state of
> affair. But we had not real plan and picking a random tool which might
> lead to similar problems and without any way to support it properly was
> not very appealing. Moreover we tried migrating to Middleman 4, the
> obvious path to modernization, but this happened to be more complicated
> than expected and this new version had terrible performance problems. As
> you now version 3 is already slow, and that's quite an understatement.
> In the meanwhile a few things have changed, and people taking care of
> the website too, so let's talk about the current situation.
> (very short version of the history around this)
>
>
> ### Why now?
>
> What has changed:
>
> * several projects moved to Jekyll, a software we were already
> investigating at the time and is being used by Google Pages (they
> created it in fact), and they were very happy with the result; we
> believe it has the necessary features, it is well maintained because
> Google uses it heavily, and it's very fast
>
> * we've tried Jekyll ourselves, we're happy too, and we do have the
> Ansible playbooks and tooling to deploy it now
>
> * over time the website had some waves of cleanup (still needs quite
> some love though) and recently the blog moved to WordPress to get
> comment support and a more friendly interface (see OVIRT-2652) which
> allowed more cleanup (see #2030)
>
> With the blog separated and a lot of custom Ruby code removed, the
> tooling ready, I believe we can now work on migrating the content.
>
> We may realize Jekyll is not the right tool, but people seemed to like
> the idea at the time and current experience seem to indicate it should
> improve things and be maintainable. The goal here is to experiment and
> switch to production only if we're happy with it.
>
>
> ### Early work
>
> I have started a branch called 'jekyll_migration' to put my work on it.
> This is very early work (I just started), I already hit various
> difficulties, and I can't commit 100% of my time on it so it will
> require some time.
>
> Several of my changes happened to not be really specific to the
> migration, and the current site would benefit from these
> fixes/cleanups/simplifications… thus I'll extracts these changes and
> create separate PRs for master.
>
> If you wish to help, then you can contact me directly or reply to this
> thread. You may also create PRs to this topic branch, but please do not
> push anything directly.
>
>
> Regards.
> \_o<
>
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ERLDSOGZQGL...
>
--
Laura Wright
She/Her/Hers
UXD Team
Red Hat Massachusetts <https://www.redhat.com/>
314 Littleton Rd
lwright(a)redhat.com
<https://www.redhat.com/>
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MNNU5XETD3H...
9:25 p.m.
Quack,
On 8/4/19 9:26 PM, Eitan Raviv wrote:
Currently I don't find the blog content on the ovirt-site
repository [1].
In which repository can it be found?
The blog part migrated to WordPress as people wanted to have comments
and a more friendly interface for not-always-technical writers. Please
see ticket OVIRT-2652 on JIRA.
Maybe the documentation is lacking on this front though.
\_o<
9:38 p.m.
Quack,
It took some time to fix various things (even in the production site)
and adapt to the new system to have all the pieces together (knowing I'm
not a web designer at all), and it's now working fine I think.
I did not receive any comment of feedback so far but now I really need
your help. The site looks almost perfectly identical, mistake included,
so AFAIK it's working but I might have missed some things. Please test
the build and result and report problems on the PR.
I also adapted the documentation and gave some tips in the
CONTRIBUTING.md file.
In any case please do not push the merge button even if there's loads of
good reviews; I need to deploy the new builder and disable the old one
at the same time.
Regards.
\_o<
10:57 a.m.
On Mon, Aug 19, 2019 at 9:26 PM Marc Dequènes (Duck) <duck(a)redhat.com>
wrote:
Quack,
On 8/4/19 9:26 PM, Eitan Raviv wrote:
> Currently I don't find the blog content on the ovirt-site repository [1].
> In which repository can it be found?
The blog part migrated to WordPress as people wanted to have comments
and a more friendly interface for not-always-technical writers. Please
see ticket OVIRT-2652 on JIRA.
Maybe the documentation is lacking on this front though.
Unfortunately older blogs posts are not visible anymore, for example
https://blogs.ovirt.org/2017/12/host-deploy-customization/
Is it possible to fix this?
Thanks,
M.
\_o<
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FF2QFEBY56F...
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
1:58 p.m.
Quack,
On 8/21/19 5:57 PM, Martin Perina wrote:
Unfortunately older blogs posts are not visible anymore, for example
https://blogs.ovirt.org/2017/12/host-deploy-customization/
Is it possible to fix this?
All blog posts have been imported and should have the same URL. We found
some discrepancies, fixed them, and thought it was ok. Thanks for
letting us know.
Jason, could you have a look please?
\_o<
2:41 p.m.
Quack,
I was able to upgrade the current builder to a more recent OS and add a
builder instance for the migrated site. You can now check the result
exactly how it would appear on production:
https://www-ng.ovirt.org/
Btw, I also fixed the .htaccess generation and ensured the events data
are updated before generating the site. Contrary to the current system
it is not done when not in production to avoid people pushing PRs
including unrelated submodules updates (as happen from time to time).
Once again, please reach out to give feedback.
\_o<
8:31 p.m.
On Wed, Aug 21, 2019 at 4:58 AM Marc Dequènes (Duck) <duck(a)redhat.com> wrote:
Quack,
On 8/21/19 5:57 PM, Martin Perina wrote:
> Unfortunately older blogs posts are not visible anymore, for example
>
> https://blogs.ovirt.org/2017/12/host-deploy-customization/
>
> Is it possible to fix this?
That post is at
https://blogs.ovirt.org/2017/12/customizing-the-host-deploy-process/
-- I'm not sure what caused the different link -- we can set up a
redirect for broken links like this
All blog posts have been imported and should have the same URL. We found
some discrepancies, fixed them, and thought it was ok. Thanks for
letting us know.
Jason, could you have a look please?
\_o<
--
Jason Brooks
Community Infrastructure Team | https://osci.io
Red Hat Open Source Program Office (OSPO)
11:12 a.m.
Quack,
Well, it's now production.
The builder have been switched.
Tell me if you encounter any problem.
\_o<
1701
days inactive
1729
days old
9 comments
5 participants
participants (5)
-
Eitan Raviv -
Jason Brooks -
Laura Wright -
Marc Dequènes (Duck) -
Martin Perina