| *** bananadev has joined #cip | 02:19 | |
| *** rajm has joined #cip | 07:10 | |
| *** patersonc has joined #cip | 07:18 | |
| rajm | just need to add the links and the deployment is complete #86 | 07:39 |
|---|---|---|
| *** toscalix has joined #cip | 07:56 | |
| toscalix | rajm: do you have a minute? | 08:29 |
| rajm | yes! | 08:30 |
| toscalix | about the known issues page | 08:30 |
| toscalix | there are two type of content that goes there | 08:30 |
| toscalix | known issues and how to workaround them | 08:31 |
| rajm | ok - needs some more workarounds? | 08:31 |
| toscalix | and other kind of things a user might face and that are not issues but we provide some guidance on how to approach them | 08:31 |
| toscalix | wait | 08:31 |
| rajm | (to the ones I added yesterday?) | 08:31 |
| toscalix | the first kind of content | 08:31 |
| toscalix | the issues+workarounds | 08:32 |
| toscalix | this page should be only a summary, a plce where you can check them all. Details should be on tickets | 08:32 |
| toscalix | so everything should be on the tickets and here we only summarise them | 08:32 |
| toscalix | so users have them in a central place and do not have to go over the whole ticket, specially if the have many comments | 08:33 |
| toscalix | we include the link to the comment with the detailed instructions of the workaround | 08:33 |
| toscalix | What I read in the wiki page is exactly the opposite strategy | 08:33 |
| toscalix | workaround is being described in the wiki page | 08:33 |
| toscalix | and I cannot see it in the ticket | 08:34 |
| rajm | I thought the issues page was fairly succint - are you saying some are too wordy? | 08:34 |
| rajm | though workarounds is in the title of the page? | 08:34 |
| toscalix | nothinng is too wordy | 08:34 |
| toscalix | this is about which one is the central place that holds the info and will be updated and which is the summary for users that is not meant to be updated | 08:35 |
| rajm | so I need to copy some of the workarounds into the tickets where they are missing? | 08:35 |
| rajm | and link to the ticket (where missing) in the wiki page | 08:35 |
| toscalix | In general, I would like to see less content in the wiki and more content in the tickets | 08:36 |
| toscalix | when talking about known issues | 08:36 |
| toscalix | that is the strategy that will reduce the maintenance effort | 08:36 |
| toscalix | wiki is expensive when it comes to maintenance | 08:36 |
| toscalix | I have no concrete suggestion on any specific known issue. I leave that to you | 08:37 |
| rajm | OK I'll trim and link, I had a work through unclosed tickets session yesterday and populate the issues page - I'll look at it | 08:37 |
| toscalix | This is the typical case in which the integration of the ticketing system and the wiki reduces the maintenance costs | 08:37 |
| toscalix | which we do not have here | 08:38 |
| toscalix | so we need to be carefull which these situation or we will need to put too much effort to keep them on sync | 08:38 |
| toscalix | with these... | 08:38 |
| toscalix | I went through the known issues last night and called my attention, that is all | 08:39 |
| toscalix | back to writing promo content | 08:39 |
| rajm | do you want me to focus on this or to get the links into #86 so we can email and close that ticket first? | 08:40 |
| toscalix | keep following the plan I will mention this in #44 | 08:41 |
| toscalix | and you will go over it later | 08:41 |
| toscalix | #86 is priority one | 08:41 |
| rajm | ok focussing back | 08:42 |
| rajm | there's a tick box for hashes in the acceptance for #86 the box hash as well as source hashes should go there? What about the gpg signature files? | 08:48 |
| toscalix | everything that will go on the download page | 08:48 |
| toscalix | yes | 08:48 |
| toscalix | ah, great, I cannot see the ticket description with my current firefox version | 08:50 |
| toscalix | after the last gitlab update | 08:50 |
| toscalix | I love the world of browsers and web | 08:50 |
| toscalix | it is so respectful with users | 08:50 |
| rajm | so it needs a new tick box/section called gpg signatures? | 08:52 |
| rajm | oh wonderful (on firefox & gitlab) :-( | 08:52 |
| *** kristerman has joined #cip | 08:55 | |
| rajm | I've assumed in the links in #86 that the link addresses identify what they are sufficiently or would you like them to be annotated or the address hiding behind a description of each? toscalix | 09:13 |
| toscalix | in the download page we will add them as links of a description | 09:14 |
| toscalix | so you can do that now so the download page can be done by someone else or you can do it then so you have to do the download page | 09:14 |
| toscalix | ;-) | 09:15 |
| toscalix | but no, the links are not self explanatory for a first time user | 09:15 |
| rajm | ok so #86 looks ok to you? and i'll followup the GM declaration with an announcement that the deployment is done? | 09:16 |
| rajm | ah I think it need sthe links as visible so I'll preface each with a couple of words description | 09:17 |
| toscalix | the links have to be visible here because we need to copy/paste them to the wiki | 09:20 |
| rajm | though you could do that via 'right'click and copy link address (but having them visible is also imho too better) | 09:22 |
| toscalix | you rule | 09:33 |
| toscalix | just think that they need to be copy pasted, that's all | 09:33 |
| toscalix | the main goal is to not forget any | 09:33 |
| rajm | I think they're all done now, looks to the email | 09:34 |
| toscalix | rajm: when communicating the end of a stage, it is a good practice to advance which one is the next one and a link to where it is described. Since we do not have the release howto yet, point people to the ticket... | 09:40 |
| toscalix | #37 | 09:41 |
| rajm | OK I'd got a mention of the documentaion as being next but will add the link | 09:43 |
| toscalix | check the answer I gave to your previous communication mail as reference | 09:44 |
| toscalix | feel free to give to it your own touch | 09:44 |
| rajm | It's now likely to be after the meeting just so I can check it thoroughly | 09:45 |
| *** patersonc has quit IRC | 10:00 | |
| *** patersonc has joined #cip | 10:01 | |
| *** rajm has quit IRC | 10:02 | |
| *** rajm has joined #cip | 10:03 | |
| *** patersonc has joined #cip | 10:23 | |
| rajm | #86 is now closed and thus deployment is complete | 10:57 |
| toscalix | \o/ | 11:01 |
| *** CTtpollard has quit IRC | 11:04 | |
| *** CTtpollard has joined #cip | 11:04 | |
| *** bananadev has quit IRC | 11:27 | |
| patersonc | :) | 12:01 |
| * rajm has updated/reorganised the setup deployment pages will find a coffee and then review them and hopes he hasn't lost anything | 13:38 | |
| toscalix | I am writing the blog post | 13:40 |
| *** kristerman has quit IRC | 14:00 | |
| *** kristerman has joined #cip | 14:17 | |
| toscalix | rajm: is falling in love with docuwiki, I guess | 14:25 |
| rajm | haha! | 14:27 |
| *** christoskaramits has joined #cip | 15:02 | |
| *** kristerman has quit IRC | 15:05 | |
| *** patersonc has quit IRC | 15:30 | |
| toscalix | rajm: for tomorrow/monday https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload | 15:47 |
| *** rajm has quit IRC | 15:50 | |
| toscalix | re-formatted the titles and notes on page https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevsetup | 16:39 |
| toscalix | same applies for the deployment page | 16:41 |
| toscalix | https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdeskdingledevdeployment | 16:41 |
| *** christoskaramits has quit IRC | 16:43 | |
| *** toscalix has quit IRC | 17:01 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!