2019-05-01 22:09:22 https://wiki.alpinelinux.org/wiki/Abuild_and_Helpers is out of date. See http://ix.io/1HN0 for current help output. 2019-05-02 12:02:10 hey tcely, that's on the wiki so you can feel free to update it, I'm mostly focusing on more long-form docs (except the planned manuals) at docs.a.o 2019-05-02 12:28:19 SpaceToast: I believe it ended up getting corrected by some kind person 2019-05-02 12:28:28 ah, good :) 2019-05-02 12:28:46 anyway, the nice thing with the wiki is that if something is wrong, you don't actually have to go through me to correct it 2019-05-03 15:26:49 i may need some help with moving some documentation for the alpine docker images 2019-05-03 15:27:09 any volunteer here? or should I ask in #alpine-devel 2019-05-03 15:34:49 any further details? 2019-05-03 15:34:58 for me it depends on what exactly is involved :) 2019-05-03 15:43:43 readme.md https://github.com/gliderlabs/docker-alpine 2019-05-03 15:44:04 and those: https://github.com/gliderlabs/docker-alpine/tree/master/docs 2019-05-03 15:44:52 compared to the new location with no documentation at all: https://github.com/alpinelinux/docker-alpine 2019-05-03 15:45:14 so it's not just about moving, then? 2019-05-03 15:45:34 move what can be moved and simplify what cannot 2019-05-03 15:45:51 aha 2019-05-03 15:46:14 and the gliderlabs doc should be more or less empty with the message: "repository moved to ..." 2019-05-03 15:46:14 if you want me to do it, I could, but I'd like to have license to change things I don't like :) 2019-05-03 15:46:54 ok 2019-05-03 15:46:54 (also, I would prefer moving it over to asciidoc and removing various "sponsored by X" - I think those are important, but don't think they should be in the docs; if we want to keep them, perhaps a ./SPONSORS file could work?) 2019-05-03 15:47:10 if all of that is ok, I'll get on it once I get off work 2019-05-03 15:47:57 im ok with all of it 2019-05-03 15:48:12 please note that the gliderlabs had some image generations scripts that we no longer use 2019-05-03 15:48:34 okay, if you could summarize various (code and sponsor) changes in here that would be helpful 2019-05-03 15:48:47 this onw no longer applies: https://github.com/gliderlabs/docker-alpine/blob/master/docs/build.md 2019-05-03 15:48:49 so I don't have to read/compare the sources to figure out what's out 2019-05-03 15:49:12 i guess you could leave the build bits out 2019-05-03 15:49:28 I'll just give generic "how to build a docker image" instructions, just so people don't complain :) 2019-05-03 15:49:30 maybe in the main readme 2019-05-03 15:50:41 we should have a doc explaining how to generate the official images 2019-05-03 15:50:45 https://github.com/alpinelinux/docker-alpine/blob/master/prepare-branch.sh#L115 2019-05-03 15:51:08 ok, so that replaces their build script 2019-05-03 15:51:25 yes 2019-05-03 15:51:42 they generated the image with apk.static (iirc) from scratch for x86 and x86_64 2019-05-03 15:51:50 but we now use the official release tarballs 2019-05-03 15:51:55 so it works on all arches 2019-05-03 15:52:07 so it is equal on all arches 2019-05-04 00:01:57 ncopa: got some first drafts over at https://github.com/5paceToast/docker-alpine/tree/docs (specifically https://github.com/5paceToast/docker-alpine/commit/b924dfa32619587d284eb5cc122af4513bbe7c11) 2019-05-04 00:02:17 please into feedback (or, if you find it adequate as-is, please do tell and I'll open a PR) 2019-05-04 00:24:25 SpaceToast: lgtm 2019-05-04 07:34:34 SpaceToast: can we have syntax higlight in adoc? 2019-05-04 07:34:49 something corresponding md: ````Dockerfile 2019-05-04 07:35:03 otherwise good 2019-05-04 10:11:13 yes, but I'm not sure if github does it right (i.e I did enable it for the "docker" tag, but it doesn't seem to be doing much) 2019-05-04 10:33:52 ncopa: done, had to go through github's html pipeline; looks like they don't recognize "docker" and demand "dockerfile" 2019-05-04 15:30:15 ok 2019-05-07 19:52:11 TBK[m]: (ref: https://matrix.org/_matrix/media/v1/download/matrix.org/PMNcLrtpzHpyHQPLssSVzJQW ) 2019-05-07 19:52:29 1: no; it's theoretically possible, but basically requires you to run your own search engine (such as elasticsearch) 2019-05-07 19:52:33 so really it's not a question for me 2019-05-07 19:52:42 2: I do not understand the question, please elaborate 2019-05-07 19:52:58 3: yes, but it will have to wait until I work on the from-scratch theme 2019-05-07 19:53:07 but tl;dr you can write any html/css you want 2019-05-07 19:53:17 if you want to work on it, you're welcome to coordinate with me, though 2019-05-07 19:55:07 1. https://gitlab.com/antora/antora-ui-default/issues/44#note_68053321 . I will look into that. 2019-05-07 19:56:00 algolia isn't open source, mind you 2019-05-07 19:56:03 so I'd rather avoid that specific option 2019-05-07 19:56:04 <_ikke_> What does something like readthedocs use as search technology 2019-05-07 19:56:06 <_ikke_> ?? 2019-05-07 19:56:27 _ikke_: they run elasticsearch 2019-05-07 19:56:29 https://docs.readthedocs.io/en/stable/features.html#search 2019-05-07 19:57:53 <_ikke_> and sphinx? 2019-05-07 19:57:53 2. Say I spot something that is incorrect or want to elaborate on, a direct link to the git repo would provide easy way to PR/MR/clone diff patch... 2019-05-07 19:58:18 which sphinx, python docs or search engine? 2019-05-07 19:58:24 <_ikke_> former 2019-05-07 19:59:16 not familiar with sphinx very much, but looks like "implement it yourself" http://www.sphinx-doc.org/en/master/usage/advanced/websupport/searchadapters.html 2019-05-07 19:59:48 <[[sroracle]]> sphinx uses some JS thing i think. not very sophisticated 2019-05-07 20:00:49 <[[sroracle]]> yes. it comes with OOB js-based search 2019-05-07 20:01:03 lunr? 2019-05-07 20:01:50 Just found Lunr for Antora - https://github.com/Mogztter/antora-lunr 2019-05-07 20:02:06 ah, by mogztter 2019-05-07 20:02:10 it'll probably be official one day, then 2019-05-07 20:02:36 still, looks like a not-my-problem thing :) 2019-05-07 20:07:22 hehe 2019-05-07 20:07:23 Looks like I need to setup an Antora instance :) 2019-05-07 20:08:10 it's not very difficult 2019-05-07 20:08:13 do you need any help? 2019-05-07 20:08:22 (it's basically a static site generator, if you discount the search feature) 2019-05-07 20:08:27 nah, just time :D 2019-05-07 20:08:56 I'm still thinking on what to do about the developer handbook stuff 2019-05-07 20:09:12 maybe I consider the reorg to be post-mortem and just move the repo like I don't care 2019-05-07 20:12:11 I am not fully aware of the issue(s) at hand. 2019-05-07 20:13:10 do you care/want a summary? 2019-05-07 20:13:24 yes 2019-05-07 20:13:57 the current state of alpine's organization has significant drawbacks, to the point that I would consider it to be a problematic situation 2019-05-07 20:14:13 I tried fixing it by making a formalized system for work distribution and governance 2019-05-07 20:14:45 it was going along normally (with lots of open discussion, and continuous improvement), until suddenly some section of the community decided I have bad intentions (I don't know why, they refuse to talk to me, and I don't even know who's in that group) 2019-05-07 20:15:14 this significantly slowed any progress (eventually to the point that two people left the project, and the discussion centered about how I should talk to try and avoid people horribly misunderstanding what I'm saying) 2019-05-07 20:15:49 I identified myself as an obstacle for furthering the improvement of the problematic situation (see above) and left the established working group, making sure everyone knows I'm available for any and all work/help, if I am asked 2019-05-07 20:16:50 that was about 1.5 weeks ago, and nothing has happened since then, which makes me conclude that the effort is officially dead (esp. given that the advice I gave was to have regular sessions ala scrum meetings to discuss what has been done and what is planned for the next sprint) 2019-05-07 20:17:17 the relation to the situation at hand is that the latest version of my proposal (not the only one discussed) is currently sitting at https://beta.docs.alpinelinux.org/developer-handbook/0.1a/index.html 2019-05-07 20:17:45 but it's become clear that it should be separate from the developer-handbook, (perhaps /governance/?), which means I can't work on the actual developer handbook very well :) 2019-05-07 20:18:04 since the effort is effectively dead, I'm considering just asking the infra people to `mv developer-handbook governance` and moving on with life 2019-05-07 20:18:19 does that clear it up? 2019-05-07 20:21:35 Yes. I have very loosely been following the ML. I sensed that not all wanted the direction but didn't express their wishes. It is hard to unify people :( 2019-05-07 20:23:07 something something Machiavelli has this fun quote about implementing new systems ;) 2019-05-07 20:23:49 if you want further details, you could go over the public logs of this channel, which should give you virtually all the information you need 2019-05-07 20:27:38 k, I will do that on a slow night. I think you should seek to split developer into its own thing (I would call it governance). 2019-05-07 20:28:41 that's what I'm thinking, yeah 2019-05-07 20:28:49 I just can't do it myself :) 2019-05-07 20:28:59 the other issue is that there are already links (the above one) floating around 2019-05-07 20:29:03 and I didn't want to break those 2019-05-07 20:29:12 but at this point, if nothing else is going to happen, it's probably not a big deal 2019-05-07 20:31:16 Can't it be solved by add a big colored notice about it having moved to a new url 2019-05-07 20:31:33 it could, but I don't want to do that 2019-05-07 20:31:52 I really dislike compromising work A for the sake of work B, or circumstances 2019-05-07 20:33:01 I can relate to that sentiment 2019-05-07 20:33:33 I do enough murdering of good projects for political reasons at work, I'm not going to do that when I volunteer to make something better, yaknow? :) 2019-05-07 20:35:25 hehe, reminds me that I need to read my xmas present "The Dictator's Handbook - Why bad behavior is almost always good politics" 2019-05-07 20:37:17 anyway, from all of the above, I'm guessing you wanna help out with docs? 2019-05-07 20:38:50 yup, do you have a todo of sorts? 2019-05-07 20:40:30 very rough 2019-05-07 20:40:34 right now the main 2 things are: 2019-05-07 20:40:52 - finalize editing process of the user handbook (typos, phrasing, about 33% done) 2019-05-07 20:40:59 - work on developer handbook (blocked by abovementioned) 2019-05-07 20:41:16 if you're interested, you could also try working on search (though I personally don't care), or try to plan out the from-scratch theme 2019-05-07 20:41:57 if patches are a question, I prefer they be put up on https://brpaste.xyz with a ?lang=diff link sent to me 2019-05-07 20:42:48 I plan to look at search and license head/footer 2019-05-07 20:42:51 k 2019-05-07 20:42:56 alrighty :) 2019-05-07 20:43:07 the current theme is on https://git.alpinelinux.org/user/daniel/alpine-antora-theme/ 2019-05-07 20:43:29 I don't have push access to that, but I'm sure you could convince someone from the infra theme to put that up 2019-05-07 20:43:34 for the from-scratch theme that should be under docs/ 2019-05-26 00:39:23 o 2019-05-26 00:43:49 <[[sroracle]]> p 2019-05-26 16:50:29 ping _ikke_, please do tell when you have some time for the git thing :) 2019-05-26 17:01:03 <_ikke_> SpaceToast: pong 2019-05-26 17:01:17 I've prepared as much as possible at this point 2019-05-26 17:01:34 first, we need to rm docs/developer-handbook (the updated and renamed "governance" repo is already up) 2019-05-26 17:01:46 once that's done I can push the new stub developer-handbook and start working on it 2019-05-26 17:01:46 <_ikke_> on the docs container? 2019-05-26 17:01:51 on the git host 2019-05-26 17:02:18 after that, on the docs container, a new mqtt-exec hook (same as for the other two, just for docs/governance) 2019-05-26 17:02:25 then I can push updated manifest for docs/docs.a.o 2019-05-26 17:02:28 <_ikke_> Can't you force push to the repo? 2019-05-26 17:02:45 I can, but that can sometimes leave artifacts, I'd rather just guarantee cleanup :) 2019-05-26 17:02:48 SpaceToast: can you post url of your changes for developer handbook 2019-05-26 17:02:57 <_ikke_> I don't have permissions on git.a.o 2019-05-26 17:03:00 ah, I see 2019-05-26 17:03:05 do you have the ability to "export" repos? 2019-05-26 17:03:23 <_ikke_> What do you mean with exporting it? 2019-05-26 17:03:32 https://git.alpinelinux.org/docs - see the difference between the top two and the bottom two :) 2019-05-26 17:03:50 mps: https://git.alpinelinux.org/docs/governance/log/ last 3 commits 2019-05-26 17:03:56 <_ikke_> different namespace? 2019-05-26 17:04:13 cgit requires some stuff to be present to allow them to be "visible" 2019-05-26 17:04:20 SpaceToast: thanks 2019-05-26 17:04:24 https://git.alpinelinux.org/ - the "Docs" section only lists the two 2019-05-26 17:04:36 <_ikke_> ah, I see 2019-05-26 17:04:38 and there're no descriptions 2019-05-26 17:05:19 mps: it's not really an update; mostly just moving the namespace so I can work on the *actual* dev docs 2019-05-26 17:05:56 <_ikke_> SpaceToast: What descriptions should they have? 2019-05-26 17:06:25 "Antora component for the Alpine Linux Developer Handbook." and "Antora component for the Alpine Linux Governance Document [DRAFT PROPOSAL]." 2019-05-26 17:06:51 the latter would get the "[DRAFT PROPOSAL]" part removed if/when the WG finishes and gets your variant ratified (at which point it'll go up there and become de-facto docs) 2019-05-26 17:07:51 SpaceToast: no, I will find some time to read it in current state 2019-05-26 17:08:00 ¯\_(ツ)_/¯ 2019-05-26 17:08:07 I'm pretty sure it's effectively dropped at this point 2019-05-26 17:08:12 s/no, /np, / 2019-05-26 17:08:23 <_ikke_> That's done 2019-05-26 17:08:28 I do think it's still the correct way to go (if *anything* it should be more democratic), but it's clearly politically infeasible 2019-05-26 17:08:44 _ikke_: two more things: 1. set up an mqtt-exec hook for docs/governance (on the docs container) 2019-05-26 17:08:53 same story as with the one for the other repos 2019-05-26 17:09:03 and 2. force rebuild :) 2019-05-26 17:09:26 (please tell me once 1 is done, I'll push docs.a.o manifest and see if it "just works", which it might) 2019-05-26 17:09:41 <_ikke_> looking now 2019-05-26 17:11:08 <_ikke_> I think it might already work 2019-05-26 17:11:18 <_ikke_> it reacts on anything in the docs/* namespace 2019-05-26 17:11:25 oh, cool 2019-05-26 17:11:29 let me try pushing manifest then 2019-05-26 17:11:47 it just worked :) 2019-05-26 17:11:50 <_ikke_> :-) 2019-05-26 17:11:56 thanks _ikke_ (and clandmeter, who I assume set that up) 2019-05-26 17:12:03 <_ikke_> yes, he did 2019-05-26 17:12:22 _ikke_: one last thing - if anyone asks where my proposal disappeared to, please point them to the right place? :) 2019-05-26 17:12:38 (I don't want to put a link into the new developer-handbook, because that'd break conceptual namespacing) 2019-05-26 17:12:53 <_ikke_> sure 2019-05-26 17:13:07 \o/ looks like we're done 2019-05-26 17:13:17 ta again, I'm going to go back to trying to regain full functionality 2019-05-26 17:13:28 <_ikke_> success with that