| opendevreview | OpenStack Proposal Bot proposed openstack/openstack-manuals master: Imported Translations from Zanata https://review.opendev.org/c/openstack/openstack-manuals/+/947180 | 03:48 |
|---|---|---|
| *** jbernard_ is now known as jbernard | 13:30 | |
| opendevreview | Merged openstack/openstack-manuals master: install-guide: Add 2025.1 (Epoxy) release https://review.opendev.org/c/openstack/openstack-manuals/+/947060 | 14:11 |
| frickler | tc-members: if someone would want to look into potentially (near to) inactive projects, checking https://review.opendev.org/q/topic:%22create-2025.1%22+status:open and https://review.opendev.org/q/topic:%22reno-2025.1%22+status:open would seem like a good start | 14:20 |
| opendevreview | Merged openstack/security-doc master: Updated from openstack-manuals https://review.opendev.org/c/openstack/security-doc/+/947166 | 15:12 |
| frickler | tc-members: fungi: another point regarding the mass glossary updates, seems that this has caused a big stack of that now becoming un-translated and I wonder if translators will ever catch up with that https://review.opendev.org/c/openstack/openstack-manuals/+/947180 | 15:17 |
| frickler | IMO that is another argument to revert those changes | 15:17 |
| fungi | untranslated in openstack-manuals and any of the other docs repos it got replicated to as well | 15:18 |
| noonedeadpunk | well | 15:18 |
| noonedeadpunk | We either need to run with current unaligned state | 15:19 |
| noonedeadpunk | or need to do some work if we want to improve general feeling about docs state | 15:19 |
| noonedeadpunk | As the part I agree here, is that it does not look good right now | 15:20 |
| noonedeadpunk | but it also was not "enterprisish" before | 15:21 |
| noonedeadpunk | and overall our community docs should be up to par with some internal "platform" docs | 15:22 |
| noonedeadpunk | which may encourage to contribute to upstream rather then keep maintaining own versions of same things | 15:22 |
| fungi | i still don't understand why "looks enterprisish" is a priority, but i'll have to assume that for some people it is | 15:22 |
| noonedeadpunk | Yeah, well. I agree it's not priority for me at least :) | 15:23 |
| noonedeadpunk | But I can regonize and acknowledge the end goal | 15:23 |
| noonedeadpunk | given some commitment to it | 15:24 |
| noonedeadpunk | and any fixes in content will be in conflict with such change, so if discount for github-like flow which most ppl used to more then gerrit - it might be more understandable I guess why7 to start from this | 15:25 |
| noonedeadpunk | anyway | 15:26 |
| noonedeadpunk | I voted positively on rollback as well | 15:26 |
| noonedeadpunk | (fwiw I don't know these folks closely and not associated with them in any way) | 15:28 |
| spotz[m] | They've just been doing a lot of docs work | 15:31 |
| noonedeadpunk | but if they have more continious contribution plan to doc space - we can be a little bit more friendlier | 15:31 |
| noonedeadpunk | as this is obviously smth that we, as a project overall, lag behind a lot | 15:31 |
| fungi | yes, as i said yesterday, if they want to spend a lot of time helping maintain the docs, then reformatting to suit their personal preferences does make some sense | 15:32 |
| fungi | i'm just worried that too much focus on reformatting is needless churn when what we really need is content maintenance | 15:32 |
| noonedeadpunk | from what I heard, they want to avoid getting own documentation space and instead contribvute to maintenances of upstream docs | 15:33 |
| fungi | that would be great | 15:33 |
| fungi | it's what we had with rackspace essentially running the docs team back in the old days | 15:33 |
| fungi | maintaining documentation upstream meant that they could do less work downstream for their own product documentation | 15:34 |
| noonedeadpunk | yup | 15:34 |
| noonedeadpunk | pretty much the same they told in some discussion in some patch.... jsut that they're not in IRC makes things a bit harder | 15:35 |
| noonedeadpunk | but well | 15:35 |
| * noonedeadpunk also not excited about some aspects of org origin, but will not go into that not to violate Code of Conduct.... | 15:36 | |
| spotz[m] | They're very good about tagging for reviews:) | 15:37 |
| clarkb | one thing that might be helpful here is to be upfront about goals then agree on a common path towards that goal? | 15:37 |
| noonedeadpunk | ++ that sounds | 15:38 |
| clarkb | "be more enterprisey" isn't really a quantifiable goal. But things like increase the accuracy of existing docs, add documentation for features that is currently missing, correct typos, etc are | 15:38 |
| noonedeadpunk | I can't tell about someone else's goal | 15:38 |
| clarkb | right I'm just using hand wavy examples not trying to call you out | 15:39 |
| clarkb | but then we can decide if rewriting and updating things and breaking translations is worthwhile (I would argue ti is for accuracy and adding missing feature coverage) | 15:39 |
| clarkb | better to be accurate and complete in one language that can be translated by tools than be inaccurate in multiple languages and miss coverage | 15:39 |
| noonedeadpunk | yes, right | 15:40 |
| noonedeadpunk | I totally agree here and I think we indeed need to reach them out more centrally and invite for the dialog. | 15:44 |
| noonedeadpunk | align goals, commitment, etc | 15:45 |
| clarkb | if there weren't less obvious impacts then I don't think it would be that big of a deal. But there are so ensuring those affected by those impacts can get on board or at least accept that the sum is an improvement seems like a good idea to me | 15:46 |
| fungi | certainly goals of those proposing changes and those reviewing them need to align at least somewhat, or things will go nowhere | 15:56 |
| noonedeadpunk | btw about transaltions... can somebody point me to some redirect rules for docs site? As I fail to find them | 16:10 |
| noonedeadpunk | Pretty much situation: open osa docs, select some language, when trying to open contributor guide, you get completely wrong 301 redirect resulting in 404 | 16:10 |
| noonedeadpunk | Issue is not present in zuul artifacts or locally | 16:11 |
| gouthamr | https://opendev.org/openstack/openstack-manuals/src/branch/master/www/.htaccess | 16:11 |
| gouthamr | this thing? | 16:11 |
| noonedeadpunk | Yeah, I think it is, thanks! | 16:11 |
| cardoe | You know mkdocs-material looks pretty dang enterprise-y and it just works ;) | 16:12 |
| noonedeadpunk | I'm not sure it's about sphinx or theme | 16:12 |
| noonedeadpunk | https://paste.openstack.org/show/bpovA2jFakVo1IHc5LBt/ | 16:12 |
| cardoe | Similarly sphinx has plenty of themes | 16:12 |
| cardoe | We don't need to have our own is my point | 16:12 |
| noonedeadpunk | as again - works nicely until deployed | 16:13 |
| noonedeadpunk | as https://docs.openstack.org/openstack-ansible/2024.2/ -> https://docs.openstack.org/2024.2/latest is not realted to it... | 16:13 |
| noonedeadpunk | about overall doc experience... | 16:14 |
| noonedeadpunk | well. mnkdocs blow my mind and IDE linters by requirement of have double trailing space at the end of line to insert /n | 16:14 |
| noonedeadpunk | :D | 16:14 |
| noonedeadpunk | I actually tried to look for some nice sphinx themes... | 16:15 |
| noonedeadpunk | but somehow it felt a need for forking them anyway and extra adopt for needs | 16:15 |
| noonedeadpunk | I think this is what breaking translations: https://opendev.org/openstack/openstack-manuals/blame/commit/0d13b52d1c7dfe501aaae0607ecac06c1716dac8/www/.htaccess#L191 | 16:17 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!