| sakrecoer_ | i've been following the process for kdenlive and i get lost in the path debian=>ubuntu=>flavours | 11:37 |
|---|---|---|
| sakrecoer_ | i think i'm unclear on what this feature freeze means. | 11:38 |
| sakrecoer_ | hm.. the wiki is weird today | 13:05 |
| sakrecoer_ | i seem to have lost editing priviledges... | 13:08 |
| sakrecoer_ | probably some maintainances got some werid error messages | 13:09 |
| flocculant | sakrecoer_: page? | 13:10 |
| flocculant | it was all read only yesterday - should be ok now afaik | 13:10 |
| sakrecoer_ | well, i'm struggling finding a page i can edit at all :D | 13:11 |
| sakrecoer_ | flocculant: so all pages :D | 13:11 |
| flocculant | oh right - well ctrl+r or f5 or whatever :) | 13:11 |
| sakrecoer_ | i should have in https://wiki.ubuntu.com/UbuntuStudio/Documentation at least... | 13:11 |
| flocculant | oh god | 13:12 |
| sakrecoer_ | well.. i tried that, yes, but... not working | 13:12 |
| flocculant | it's all immutable again | 13:12 |
| sakrecoer_ | seems so.. | 13:12 |
| flocculant | asked in sysyadmin channel - should be normal *soon* | 13:14 |
| sakrecoer_ | :) | 13:26 |
| sakrecoer_ | thanks flocculant | 13:26 |
| sakrecoer_ | \o/ flocculant | 14:00 |
| sakrecoer_ | back to normal | 14:00 |
| zequence | Zak har ju varit art lead och har gjort ett väldigt fint jobb med design osv. Men, han är lite speciell, alltså | 15:16 |
| zequence | Oops | 15:16 |
| knome | zequence, on other news, did you check the website updates yet? | 16:30 |
| zequence | knome: No, I haven't. I will probably not do that so much until some time after FF | 16:34 |
| zequence | But, I will come back to it. We are working on a unified design for our artwork, so some of that will be implemented there, I'm sure | 16:35 |
| knome | fair enough | 16:35 |
| knome | i've got interest from other teams and people now too, and they seem to be happy with it (so not so many bugs at this point) | 16:35 |
| knome | i hope to get this moving forward this month | 16:36 |
| zequence | ok, sounds good | 16:36 |
| zequence | I'm pretty happy with the latest version I tried, so should be fine | 16:37 |
| knome | yep, good | 16:37 |
| knome | and pushing the theme to production does not mean it can't get any updates; it just means it will be considerably slower | 16:38 |
| Rosco3 | OvenWerks: Thanks for giving 386 a spin. That saved me some time | 18:30 |
| Rosco3 | I have marked the ISOs for studio as ready after a quick smoke test on amd64 | 18:30 |
| sakrecoer_ | knome: I realy like the look so far! what i'm concerned about is the feature tour | 19:45 |
| sakrecoer_ | knome: blogroll in wikiformat is good for documentation and news, but if it is possible to break out of the format for the feature-tour, i think it would be very sweet | 19:48 |
| sakrecoer_ | maybe the feature tour could be subdomain: xenial.ubuntustudio.org which lands on feature tour and leadsback to ubuntustdio.org | 19:48 |
| sakrecoer_ | i'm just spinning ideas | 19:49 |
| knome | i'm not sure i know how to help you; i don't know what you are looking for from the feature tour, so i can't support doing that | 19:49 |
| sakrecoer_ | with a subdomain we can have static html5 site for displaying sexy creative suit | 19:49 |
| sakrecoer_ | ..without bothering our good wordpress engine with funky modules | 19:50 |
| knome | sure, if you want to maintain that subdomain separately | 19:50 |
| knome | remember, if it's within canonical hosting, all file changes go through IS | 19:50 |
| sakrecoer_ | knome: then the "feature-tour" link on frontpage would only need to be updated for current release subdomain. | 19:50 |
| sakrecoer_ | knome: mini html sites are easy to back up also | 19:51 |
| knome | i'm not disagreeing | 19:51 |
| knome | if you want something completely different, it's likely best to do so | 19:52 |
| sakrecoer_ | knome: right, through IS, that would imply submiting request in good time | 19:52 |
| knome | yes | 19:52 |
| sakrecoer_ | you are more experienced in me with the time-frames :) knome, what do you reckon? is it making things easier or more complicated? | 19:53 |
| sakrecoer_ | knome: perhaps you have a module-magic ace in your sleave, designed for sexy feature tour? :) | 19:54 |
| knome | whenever you bring in another person/team that is responsible for anything, it's always more prone for errors and slows the progress down (not only with IS) | 19:54 |
| sakrecoer_ | not that the website is not sexy, missunderstand me right | 19:54 |
| knome | again, it really depends what you are looking for | 19:55 |
| knome | i can support *some* features from within the theme reasonably | 19:55 |
| knome | outside that, you'll likely want to set up something else, whether it was a minisite outside wordpress or something different | 19:55 |
| knome | i mean i don't think it's very sensible to try to fit something very dynamic in nature into a wordpress plugin | 19:56 |
| knome | (or theme) | 19:56 |
| knome | too much modularity means the plugin/theme will just get bloated and doesn't really serve any purpose well | 19:56 |
| sakrecoer_ | that is why html5 minisites are great | 19:57 |
| knome | the aim of the theme i'm building is to offer an easy way to get a good-looking theme with an integrated look set up | 19:57 |
| knome | sure, but then it means you will need to edit the files anyway | 19:57 |
| knome | whether it was somehow from within wordpress or directly | 19:57 |
| sakrecoer_ | not if it is not ment to be edited | 19:57 |
| knome | IS won't allow forms which directly allow you to edit files on the filesystem | 19:57 |
| sakrecoer_ | i'm talking about the feature tour | 19:57 |
| knome | me too | 19:57 |
| sakrecoer_ | yeah, but i'm not talking about editing them | 19:58 |
| sakrecoer_ | i'm talking about having a static site | 19:58 |
| knome | i'm talking about editing them in the sense that when you create anything, it's editing | 19:58 |
| knome | and tbh, you *will* end up wanting changes to your static site | 19:58 |
| knome | trust me | 19:58 |
| knome | so you want to account for that | 19:58 |
| knome | or you can get a server set up somewhere else and ask IS to point a subdomain there | 19:59 |
| sakrecoer_ | i understand :) | 19:59 |
| knome | they can do that too | 19:59 |
| sakrecoer_ | oh.. | 19:59 |
| knome | but then you're obviously responsible for maintaining that server | 19:59 |
| sakrecoer_ | hehe | 19:59 |
| knome | we have several xubuntu.org subdomains pointed at a server we set up some time ago | 20:00 |
| sakrecoer_ | hm, i have to ask my budy, but i might be able to host such thing for a few years | 20:01 |
| sakrecoer_ | i'll have to think about this | 20:01 |
| sakrecoer_ | thanks for informing me knome | 20:02 |
| knome | no problem | 20:02 |
| knome | generally, the IS is willing to do "anything" for you; as long as you don't ask for silly things | 20:02 |
| sakrecoer_ | cool | 20:02 |
| knome | and some requests might take time | 20:02 |
| knome | but subdomain redirection isn't a problem | 20:02 |
| sakrecoer_ | :) but hosting it longterm is :) | 20:03 |
| sakrecoer_ | unless of course, we go thou IS each time | 20:04 |
| sakrecoer_ | but that, like you say imply slower process, and reduce editing possibility to ~0 | 20:04 |
| sakrecoer_ | hehe, so it would be publishing a website, like publishing a newspaper: better not have a typo, cuz there ain't no undo | 20:05 |
| knome | pretty much so | 20:06 |
| knome | that's why putting the content within wordpress makes sense | 20:06 |
| knome | because at least you have control over the content | 20:06 |
| knome | one thing we also do, which you might be interested of or not | 20:06 |
| knome | on the main website, we link to a css file that is on the subdomain we control ourself | 20:07 |
| knome | which means we have access to fix critical CSS issues when we need | 20:07 |
| knome | and do some other updates | 20:07 |
| knome | of course we then try to push them to the main server ASAP, but this leaves us some breathing space | 20:07 |
| knome | MAYBE with something like that you could almost set up the minisites even with wordpress as the backend | 20:08 |
| sakrecoer_ | knome: interesting | 20:11 |
| sakrecoer_ | knome: altho i'm open to work with the wordpress, magic can be made with images | 20:11 |
| sakrecoer_ | how would you go about for a feature tour on this wordpress theme? | 20:12 |
| sakrecoer_ | obviously there would be a post about the features, | 20:12 |
| knome | currently, it supports no thrills | 20:12 |
| knome | so you would have to tell me what you are looking for | 20:12 |
| sakrecoer_ | i'm thinking about site like these: http://ardour.org/ | 20:13 |
| sakrecoer_ | this one is funy (music on pageload, music is funy) http://cinelerra.org/2015/ | 20:13 |
| sakrecoer_ | ardour is way simpler, perhaps that is possible to achive in a wordpress post | 20:13 |
| sakrecoer_ | displaying only the post, and have it nicely layed out with good pictures | 20:14 |
| knome | on the ardour site, there's nothing you can't do with the theme except the sections that have a different color background that spans to the edge of the page | 20:14 |
| knome | ...though you can modify the theme to allow to do that | 20:14 |
| knome | the cinelerra site just looks weird to me | 20:16 |
| knome | they did parallax scrolling, which would be hard to do within a wordpress theme that didn't specifically support that | 20:16 |
| knome | bbl | 20:16 |
| sakrecoer_ | ok :) | 20:16 |
| sakrecoer_ | knome: i'm thinking more fullframe imagery, Title fonts and flash rubricus. website-content gets to background. in the feature tour the main menu is about the feature, the rest of the space is for sexy feature display | 20:18 |
| sakrecoer_ | fullframe image with sweet titling, minimal but effective i think | 20:19 |
| OvenWerks | sakrecoer_: remember also that xubuntu has more people helping to begin with. (it doesn't take many people to make it double) | 21:38 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!