AND SO THERE WERE NOTES ----------------------- Agenda: 1. Design work 2. Migration from CVS 3. Content Design Work ----------- - People continue to appear on debian-www@l.d.o either complaining or offering re-designs - There are thousands of pages, it's not just a case of fixing the front page - We also need continued maintenance, not short-term contributors - CVS continues to be a barrier (more later) - Proposal: submit mockups to mailing list? - New designs should not leave the translations out as well - We should also discuss what part of our website is targeted for which kind of visitors. Migration from CVS ------------------ - CVS is extremely difficult to do radical things - There are differing opinions about how painful CVS is - May be dissuading others from helping - There is a cvs->git bridge by Samu - Conversion to git does make for a very large repository, so even small changes need a full clone (web services can help with this) - Does history matter? Is leaving history in CVS acceptable? - history preservation has been very useful at times - general consensus: keeping history is important - The current translation workflow depends on how CVS works (commits are always incremental) - this could be avoided - translators like having only one file to care about at at time - Steve's goal: migrate to git this year - Arrange periodic meetings to manage this process, not try to do the whole thing in one big chunk Build process ------------- - Desired: - not always pushing to mirrors straight away - not descending subdirectories - able to change just the top page - consensus: have a staging area and symlink or similar Content ------- - Is there too much content? - there is lots of duplicate information spread around - security section is enormous - Can some parts be broken out into distinct repositories? e.g. static security content - consensus: break into compartments which can be owned by teams - non-CVS would make it easier to remove content and be able to get it back - there is a [linklint](http://www.linklint.org/) already, probably needs checking - a human should also check that linked external content continues to be appropriate ---- paste of the IRC log (#debconf17-bo), later larjona will put the info in the corresponding items ----- [00:00:49] Debian web team BoF by Steve McIntyre in Bo has just begun https://debconf17.debconf.org/talks/159/ [00:02:35] I will happily take some notes [00:02:42] \o/ [00:04:19] where do we participate the remote people (chat)? here? or in the chat of the gobby? [00:04:44] both? [00:04:47] larjona: in here please if you want q to be verbal asked [00:04:53] gobby for notes [00:04:54] ok [00:09:11] er, if people are going to write random notes they should really have been raised in the room first [00:09:35] gobby is minutes, not a substitute for discussoin [00:10:13] -*- larjona raises hand, wants to say: [00:10:17] Some months ago, the mirror team moved the main file that they maintain (list of mirrors) into a git repo. That file is not translated. I think the experience is good, maybe we could try a git repo for all the nontranslatable files first [00:10:34] jmw: which bit are you taking issue with? [00:10:41] targetting [00:11:05] ah right [00:12:58] akward Sledge is awkward :) [00:13:31] I look at the history to understand why certain content came there, how old is that content (how long is unchanged...) [00:13:40] jmw: :) [00:14:09] larjona: discussion is going too fast i'm afraid [00:14:14] yes :/ [00:14:17] to relay your remark :( [00:14:31] joostvb: it has been raised [00:14:38] a ok, cool [00:14:57] the stream is slightly behind real time I think (understandably) [00:15:00] Continuous Key-Signing Party introduction by Gunnar Wolf in Buzz will start in 15 minutes https://debconf17.debconf.org/talks/73/ [00:15:06] yes, there is a bit of lag [00:15:09] about 15-20s for me [00:15:12] speed of light and all that [00:16:00] --> dondelelcaro joined #debconf17-bo [00:16:27] current workflow? run away! [00:16:30] ahem [00:16:34] -*- jmw should take this more seriously [00:17:44] bah, serious is boring [00:18:26] I basically edit, commit and wait for the next build to not crash :s - Sometimes I build locally -- www.debian.org/devel/website and subpages are my friends [00:18:39] RattusRattus: ^ [00:19:39] The translators workflow, at least for me, is very easy because it involves one file at a time [00:19:58] YES (the translation updates rely on CVS) [00:20:21] But some parts also use .PO files [00:20:35] ouch... [00:21:22] I've tried to make some small pages use mostly PO file (eg. partners section) but for some parts is very difficult, and the titles of pages cannot be translated using PO files [00:22:04] sure the first step is understanding what is happening for it to be slow? [00:22:06] oh sorry thaught you were saying PO not so good [00:23:07] the Security section is huge [00:25:00] Continuous Key-Signing Party introduction by Gunnar Wolf in Buzz will start in 5 minutes https://debconf17.debconf.org/talks/73/ [00:26:42] happy in here? [00:26:54] all ok move to git? [00:27:55] More than ok. :) [00:29:32] yes please [00:30:00] dinner in Cafeteria will start in 30 minutes [00:30:13] Continuous Key-Signing Party introduction by Gunnar Wolf in Buzz has just begun https://debconf17.debconf.org/talks/73/ [00:30:46] -*- larjona raises hand and wants to say: [00:30:46] compartmentalize all the things!!1! [00:31:18] loud and clear :) [00:32:02] More difficult thing for me is to get certain pace to work on the website, the big tasks require longer chunks of time, and repeat regurlarly. some times i have time, I spend it and begin to understand, try some things, my time is finished, and cannot come back to that after months, and then I forgot everything and i need to learn again... [00:32:19] So maybe we could set some periodical meetings to get things done [00:33:36] -*- jmw scribes furiously [00:34:03] someone owes jmw some gin :) [00:34:05] I can take later this channel log and complete the gobby [00:34:10] no suffer [00:34:27] larjona: please do. thanks! [00:34:28] later = from thursday on, before I'm entangled with things [00:34:58] we can surely automate broken link checking by now, it's 2017 [00:35:36] I suppose if one gets HTTP200 but the content is lies, that can't be caught automatically [00:35:39] human needs to check that [00:37:04] RattusRattus: no, I'm saying that the link may be valid but the content has moved on, which *does* need a human [00:37:21] 'k [00:38:31] (I think I am about 30s behind you guys) [00:38:40] -*- larjona too [00:38:43] :) [00:38:59] so much gobbying [00:39:07] thanks everybody [00:39:16] u 2 [00:39:24] afk food! [00:39:26] bloody digital worl - it buffers stuff and takes time to transcode