16:00 < ricky> ====== BEGIN FEDORA WEBSITES MEETING ======
16:01 < ricky> Roll Call:
16:01 < ricky> Ricky Zhou
16:01 < JonRob1> ricky are you logging?!
16:01 < JonRob1> Jonathan Roberts
16:01 < ricky> Yup
16:02 < ricky> ianweller, giarc, quaid, anybody I forgot: ping
16:02 * ianweller
16:03 < ricky> All right, then: http://fedoraproject.org/wiki/Websites/Tasks
16:04 < ricky> So the planet matrix seems to be going well (thanks, ianweller)
16:04 < giarc> giarc
16:04 < ianweller> \o/
16:04 < ricky> :-)
16:04 < ianweller> i need to tally up browsers when i get a chance
16:04 < ricky> So what can we try to fix this problem now?
16:05 < ricky> Even with a good idea of what's failing, it's hard to test CSS changes without being able to try immediately.
16:05 < ricky> At least Firefox 3 on Fedora isn't particular rare in these parts ;-)
16:06 < giarc> can we get a test instance up that we could try changes on? ( one that has all the same blog posts as the live version)
16:06 < ricky> I've tried a bunch of things to catch that scrolling problem, but no luck :-( I'm semi-convinced that it's a Linux+Gecko bug
16:06 < ricky> giarc: Good idea - it should be as simple as wgetting a copy (and changing links) to a fedorapeople page
16:07 < giarc> i only get the scrolling problem sometimes, very hard to figure out what is causing it
16:08 < ricky> Weird, I can reproduce it 100% of the time
16:09 * quaid is here, thx
16:10 < giarc> my first page load seems to exhibit it, subsequent loads are seemingly more random
16:10 < ricky> For anybody that's interested in testing on a separate instance, cp -R ~ricky/public_html/planet ~/planet on people1
16:11 < ricky> And sed -i 's/ricky.fedorapeople.org/username.fedorapeople.org/g' ~/public_html/planet/index.html
16:11 < ricky> Sorry, I mean cp -R ~ricky/public_html/planet ~/public_html/planet
16:12 < ricky> So the goals for that are to either solve/work around the bug, or maybe even get a simplified test case if it does turn out to be a browser bug.
16:12 -!- stickster is now known as stickster_afk
16:13 < ricky> (Since no CSS is supposed to get that kind of behavior, I'm pretty certain *something* is wrong with the rendering)
16:13 < ianweller> brb
16:13 < giarc> ricky, OK
16:13 < ricky> Anybody have anything else to add about planet?
16:14 < ricky> daMaestro mentioned that the huge sidebar made mobile viewing difficult a while back
16:14 < ricky> (Huge scrolling, plus downloading a lot of usernames before getting and content)
16:15 < ricky> So part of that can be solved with CSS, but the other part is a markup thing)
16:15 < giarc> i think we can swap positions in the markup to solve that, but have not tried it yet
16:16 < giarc> also, should the planet code go into our git ?
16:16 < ricky> Hm, it probably should
16:17 < ricky> Do you think we need to setup an automatic sync from the git repo for that?
16:17 < giarc> i guess that could not hurt, but is probably not nesc at this point
16:18 < ricky> All right, then
16:18 < ricky> Do you think we could push this to CSS people on the list?
16:19 < ricky> A lot of people have expressed interest in helping with CSS, but I haven't been great with giving them tasks to start with
16:19 < ricky> This could be a pretty good chance to get more people involved :-)
16:20 < ianweller> ricky: should we shove a giant "patches welcome" message at the top of the matrix? hehe
16:20 < giarc> sure, if people want to help with it ...
16:20 < ricky> Go for it :-)
16:20 < ricky> It might also be a good idea to ping firefox people/their bugzilla about this.
16:21 < giarc> good thought ricky
16:21 < ricky> It feels like a bug, but who knows? It could be known/expected behavior.. somehow.
16:21 < ricky> All right, so after the meeting, I'll ask on irc.mozilla.org and see if it's something that we should file a bug over
16:21 < giarc> i hope not expected ... 0_o
16:21 < ricky> Yeah ;-)
16:21 < ricky> So anything more on the planet before we move to get-fedora?
16:22 < ianweller> not that i can see.
16:22 -!- stickster_afk is now known as stickster
16:23 < ianweller> other than i read stickster's great point in spevack's blog just now
16:23 < giarc> ianweller, got a link?
16:23 < ricky> ianweller: Ooh, can you paste a link?
16:23 < ianweller> http://spevack.livejournal.com/59491.html
16:23 < giarc> danke
16:23 < ianweller> "On a related note, Paul Frields made a great point earlier today -- we need a mechanism that automatically puts anything sent to fedora-announce-list on Planet Fedora."
16:23 < ricky> Ah, that - yeah
16:24 * ianweller researches existing mailman->rss interfaces
16:24 < ricky> All we need is somebody to subscribe to that list with an email2rss script of some sort
16:24 < ricky> It shoudn't be that hard to do on Fedora infrastructure, if that's the right place
16:24 * ricky might avoid mailman to RSS if it requires modification of Red Hat's mailman
16:25 < stickster> ianweller: We definitely don't want something more spammable as an intermediary
16:25 < stickster> i.e. mailbucket.org <== FAIL.
16:25 < stickster> heh
16:25 < ianweller> stickster: duh :D
16:25 < ianweller> ricky: noted
16:25 < stickster> spevack gave me too much credit, it was more his idea as I recall.
16:26 < ianweller> ricky: yeah maybe an internal email that then goes to generate rss feed.
16:26 < ricky> Ah, that's true
16:26 < ianweller> spevack: hehe
16:26 < ianweller> ricky: although it should probably filter out anything that wasn't sent to fedora-announce-list, just in case someone actually guesses the email by accident
16:26 < ianweller> brb
16:27 < ricky> Yeah - that's something to think about
16:27 < ricky> So get-fedora :-)
16:28 < ricky> Anybody know what the progress on that has been?
16:28 * ricky wonders if this falls under the "release early, release often" saying.
16:29 < ricky> It's only marginally more painful when you add "translate early, re-translate often" to it :-/
16:30 < JonRob1> is juank_prada around tonight?
16:30 < ricky> .seen juank_prada
16:30 < zodbot> ricky: juank_prada was last seen in #fedora-websites 1 week, 6 days, 23 hours, 10 minutes, and 20 seconds ago: <juank_prada> see you all later :)
16:31 < ricky> Wow, I forgot to ping mizmo-out too - this is the one she can make, right? :-)
16:32 < ricky> (spins.fedoraproject.org)
16:32 < ianweller> this is the early one, right?
16:32 < ricky> Yup
16:32 < ianweller> it doesn't look like she's been in at all today
16:32 < ricky> She mentioned that she had been working on that
16:32 < ricky> Is anybody currently working on CSS for her mockups?
16:32 < ianweller> no, but i will be soonish
16:32 < ianweller> i'm assigned to that task
16:33 < ricky> Ah, cool
16:33 < ricky> Try to tie in with fedora.css as much as possible
16:33 < ianweller> noted/agreed
16:33 < ricky> (We really need to start cleaning up our CSS usage)
16:33 < giarc> i have been out of touch a few meetings in a row now, where are mizmo-out 's mockups ?
16:34 < JonRob1> ianweller: css for spins or for pushing to fp.o in general?
16:34 < ianweller> JonRob1: spins.fp.o
16:35 < JonRob1> do we have html for spins to go with?
16:35 < ianweller> no. which i guess is also assigned to me
16:35 < ianweller> mizmo-out does the mockups, i'll turn that into magic^Wcode
16:35 < ianweller> that's how i understand it.
16:36 < ricky> Heh.
16:36 < ricky> Well, both HTML and CSS will build on fp.o stuff a bit, I gues
16:36 < ricky> **guess
16:36 < ianweller> yes, i hope so ;)
16:36 < ianweller> less work for me.
16:39 < ricky> Darn, I suddenly can't find the mockups
16:40 < giarc> brb
16:40 < giarc> $work call
16:40 < ricky> All right, to Websites Infrastructure, then
16:41 < ricky> quaid: Are you around?
16:42 < ricky> No updates on the build script
16:42 < ricky> We are moving to a different workflow, though
16:42 < ricky> The live branch no longer exists - anything pushed to the git repo goes live immediately.
16:43 < ricky> So the workflow I'm aiming for is: People have their own git repos (preferably public/fedorapeople) for testing their own changes, then they push up when they're ready
16:44 < ricky> So the makefile/README has been changed to reflect this.
16:44 < ricky> No more hideous merges/time-consuming typos :-)
16:45 < ianweller> have you shot that info to fedora-websites-list and fedora-infra-list
16:45 < ricky> Just websites (I've made all the necessary changes on the infra side)
16:45 < ricky> (Subject "fedora-web git workflow change")
16:46 < ricky> Anyway, those are all the updates from the infra side - I still haven't found a good solution for ugly templates yet.
16:47 < JonRob1> ricky, i must run, sorry i haven't been around much tonight but have had other commitments to fight with
16:47 < JonRob1> if you throw me the log i'll minute it up over the week
16:47 < JonRob1> and also, there's no new news on the license front
16:48 < ricky> I'm eagerly following http://genshi.edgewall.org/ticket/129, which will hopefully solve some problems
16:48 < ricky> JonRob1: No worries - see you later
16:48 -!- JonRob1 [n=jon(a)88-110-60-157.dynamic.dsl.as9105.com] has left #fedora-websites []
16:49 < ricky> So onto common look+feel
16:49 < ricky> giarc: Are you back?
16:49 < ricky> quaid and stickster might be interested in this too, since it says that docs.fp.o is first on the list :-)
16:49 < giarc> yep
16:50 < ricky> So how's it going with prettifying docs.fp.o? Are we going to try to do it within the current build system, or are we waiting for something less convoluted to work with?
16:51 < giarc> i have had no time for this yet, but was planning on this week... I am not at all familiar with how docs is built ...
16:52 < ricky> Prepare for "fun" ;-)
16:52 < giarc> what /who should i pester for help getting going with that?
16:52 < giarc> ok :-}
16:52 * ianweller prepares for said fun
16:52 < ricky> I'd guess that quaid and stickster (and fedora-docs-list) are the experts on that
16:53 * stickster here
16:53 < stickster> giarc: We have a CVS repository for docs, at cvs.fp.o:/cvs/docs
16:53 < stickster> It contains DocBook XML source for our documents, which are build to HTML and pushed (more or less, with some steps in between) to the /cvs/fedora repository.
16:54 < giarc> ok
16:54 < stickster> Tagged LIVE and then sync's on the server by a cronjob
16:54 < stickster> *sync'd
16:54 < giarc> so I guess I will be interested in the co and build part for starters ...
16:54 < ricky> Isn't that HTML seddde into a PHP file then converted into an HTML file at some point?
16:55 < ricky> **sedded
16:55 < ricky> (Or was I mixing it up with fedora.redhat.com?_
16:57 < ricky> giarc: Anyway, let me know if I can help with diving into makefiles and buildscripts and such :-)
16:57 < ricky> quaid: ping (Wiki Content Sponsorship - Plugin)
16:59 < ricky> :-/
17:00 < giarc> mm, i have followed these:
17:00 < giarc> https://fedoraproject.org/wiki/DocsProject/CvsUsage
17:00 < giarc> and it is challenging me for anonymous's password ?
17:00 < ricky> Blank?
17:00 < ricky> If that doesn't work, can you give me the command you're trying?
17:01 < giarc> blank
17:01 < giarc> thanks
17:01 < ricky> Ah, cool
17:01 < giarc> oh boy, this does look fun
17:02 < ricky> Hehe.
17:02 * ricky quickly get the last item in:
17:02 < ricky> Group join interstitial pages in FAS
17:03 < ricky> I think one problem is that FAS kind of breaks the step by step process of most join pages.
17:03 < ricky> So we need to make it more wizard-like, I guess.
17:06 < ricky> I guess we've hit the hour mark for now, so let's close this up
Meeting today at 20:00 UTC.
According to Communicate/FedoraMeetingChannel, #fedora-meeting is free,
so we'll be in there. If by chance someone else is in that room, go to
#fedora-websites
Here is your trusty task list, which I updated last week, so we'll take
it from there with whoever is around.
https://fedoraproject.org/wiki/Websites/Tasks
--Max
Hi all, two items of business that I want to bring up
1) We now have a bot on the wiki, appropriately named Wikibot, this can
be used for general repetitive tasks such as en-mass addition of
categories to pages, and some general clean-up tasks that needs
to/should happen once in a while.
2) Some pages are getting a bit too big, while some are getting useless
as time goes on (information for EOL releases. As such I propose the
addition of two new name spaces...
a) Archive: (without talk pages)
Purpose - To allow archiving wiki pages pertaining to EOL releases,
and/or are no longer relevant to the general user
Benefits - With proper setup (not searched by default for instance) we
can help speed up searches and remove old information from general end
users, BUT still be there for those interested. Pages like the old
Extras and FSA pages come to mind immediately.
b) Meeting: (with talk pages)
Purpose - Allow some separation of end-user based content and
board/committee/group meeting logs
Benefits - Marginal, similar to the purpose of Archive though,
basically, somewhere to keep meeting logs in a place where they can be
optionally searched but not by default
An alternative to a meeting name space is with proper logging of the
meeting channels automatically posting meeting logs on Fedora People (or
similar).
As for the large pages, well we have pages that are well in excess of
the 32KB recommended by the Mediawiki folk, stuff like
https://fedoraproject.org/wiki/ChristianIseli/PackageReviewStatus
(200KB+) would be better suited to Fedora People, but we don't really
have any mandate on this. (it'd be nice to have one).
Thoughts, Comments, Suggestions?
Nigel
Hi all,
Two questions concerning the method by which Fedora Weekly News is
turned from a wikipage into plaintext for email purposes:
1. If we use external wikilinks (such as [http://someurl.com Some URL]
in what format will these be rendered during export to plaintext?
2. How/where is the plaintext generated?
If someone can point me to appropriate reading material on this then
I'd be grateful. I Googled around for information on general
MediaWiki exporting and only found information about XML exporting. A
brief search of the last 5 months of this mailing list's archives also
revealed nothing.
Thanks for any assistance,
Oisin Feeley
Sorry for the delay, minutes are here:
http://fedoraproject.org/wiki/Websites/Meetings/2008-07-07
And log is below.
Best,
Jon
-----------------------------
--- Log opened Tue Jul 08 00:00:00 2008
--- Day changed Tue Jul 08 2008
00:00 < spevack> ====== BEGIN FEDORA WEBSITES MEETING ======
00:00 < spevack> ok everyone, let's begin
00:00 < spevack> JonRob: right on :00 for you :)
00:00 ... join!#fedora-websites ->
epkphoto(n=epkphoto(a)ip98-169-237-170.dc.dc.cox.net)
00:00 < spevack> for me it's even better -- 00:00:00 for the timestamp
00:00 < ricky> :-)
00:00 < spevack> let's do an official roll call, if you will
00:00 < JonRob> makes it all worthwhile!
00:00 < ianweller> ah, the magic of ntp...
00:00 < spevack> Max Spevack
00:00 * ianweller lurks
00:00 < JonRob> Jonathan Roberts
00:00 < ricky> Ricky Zhou
00:01 < epkphoto> Eric Kerby
00:01 < fchiulli> Frank Chiulli
00:01 < spevack> giarc around?
00:02 < spevack> epkphoto: at the risk of embarassing myself, I'll say
that I don't recognize your name immediately... have you been lurking
for a while, are you an old-timer who's not been around for a bit, or
am I just blind and dumb?
00:02 * quaid is here
00:02 < spevack> hey karsten
00:02 < epkphoto> lurking more or less
00:02 < spevack> well cool, good to have you here epkphoto
00:02 * spevack was expecting an answer of "I've been a Fedora
contributor since 2005, you insensitive clod!"
00:03 < spevack> ok... let's look at our agenda.
00:03 < epkphoto> one day after college stops consuming my life, I'll
be more recognizable :)
00:03 < spevack> http://fedoraproject.org/wiki/Websites/Tasks
00:03 < spevack> pull ^^^^^ up if you all will
00:03 < spevack> epkphoto: what year are you? where you located?
00:03 ... join!#fedora-websites -> ryanlerch(n=ryan(a)203.34.177.232)
00:03 < spevack> ok, let's start at the beginning.
00:03 < spevack> I was asked to add Planet to our task list
00:03 * abadger1999 here
00:04 < epkphoto> spevack: graduating in May 2009...located in
US/Eastern...specifically NY and VA
00:04 < spevack> namely, we need someone to go through and test
planet.fedoraproject.org on Macintoshes, Windows, etc. We need a
cross-platform and major-browser test matrix
00:04 < spevack> people have been traveling during the holidays, using
random computers, and seeing breakage.
00:04 < spevack> So, who's got access to something other than Fedora?
00:04 < ricky> And Firefox on Linux still has that stupid scrolling problem :-(
00:04 * ianweller has seen breakage on his home computer, on fedora,
on firefox-3.0-1 :(
00:04 * ricky could never find out what caused that
00:05 < ianweller> well, the scrolling problem, that is
00:05 < JonRob> i have a mac so can't test os x - though i'll have to reinstall
00:05 < JonRob> can*
00:05 < spevack> Well, I'd like to do this in a slightly organized way
00:05 < epkphoto> i may be able to do some Mac OS X testing
00:05 < spevack> 1) simple page on fp.org/wiki/Planet/Matrix that
lists the basic OSs and browsers we want to test look and feel in
00:05 < spevack> 2) a section under each where we can describe problems
00:06 < JonRob> ah ok, good idea!
00:06 < spevack> so that giarc or anyone else hacking on the CSS can
have a place to know what's going on... I'm trying to keep us away
from a trac instance
00:06 < spevack> that just feels like overkill to me
00:06 ... join!#fedora-websites -> giarc_touch(n=mobile(a)32.138.69.195)
00:07 < ricky> Speak of the devil :-)
00:07 < spevack> so would someone like to volunteer to create that
matrix, send a note to the list, and then get some volunteers to try
them out? This is not a complex task -- let's just hit the 4 or 5
highlights and then have a report to give giarc_touch
00:07 < spevack> giarc_touch: howdy
00:07 * ianweller could create the matrix tomorrow
00:07 < giarc_touch> hi
00:07 < ricky> giarc_touch: What different browsers/platforms do you
have access to?
00:07 < spevack> giarc_touch: we're talking about building a little QA
team for you to test planet.fedoraproject.org across a few different
browsers and platforms
00:08 < giarc_touch> cool
00:08 < spevack> ianweller: that would be great. but i'm a little
sensitive to giving you stuff this week, unless you're sure you have
time for it
00:08 < ianweller> tomorrow i've got nothing going on
00:08 < spevack> ianweller: sounds good, then. thanks!
00:08 < ianweller> shouldn't take too long to get ready
00:08 < spevack> I think you need:
00:08 < spevack> Windows -- IE & Firefox
00:08 < spevack> Mac -- Safari & Firefox
00:09 < giarc_touch> i
00:09 < spevack> Fedora -- Firefox and Epiphany
00:09 < giarc_touch> oops
00:09 < spevack> that probably covers most of it
00:09 < spevack> giarc_touch: go ahead
00:09 < ricky> And maybe Konqueror and possible Opera
00:09 < JonRob> + konq?
00:09 < spevack> ricky: +1
00:09 < ianweller> ok for internet exploder do we care about version 6?
00:09 * spevack presents himself to the KDE guys for a whipping
00:09 < giarc_touch> what issues are we having?
00:10 * spevack only cares about the latest version
00:10 < ricky> ianweller: We should really try to
00:10 < ianweller> i think we should definitely do $currentversion and
$currentversion-1
00:10 < spevack> giarc_touch: vague reports of "it looks bad on
non-Fedora firefox". That is why we're trying to get volunteers to
look at it and either be specific, or just have it go away :)
00:10 < spevack> ianweller: sure.
00:10 < giarc_touch> ok
00:11 < spevack> ianweller: shoot for the stars, and we'll see what
kind of volunteers we can rustle up.
00:11 < ianweller> will do.
00:11 < spevack> giarc_touch: i want to come to you with specific
cases and screenshots, or not bother you at all
00:11 < spevack> ianweller: ask people to include screenshots with
their complaints, it will help giarc_touch a lot
00:11 < ianweller> ok
00:11 < quaid> make sure there is room for >1 person to comment per matrix cell
00:12 < ricky> test case #1: press page down until you reach the
bottom - make sure that there are no problems
00:12 * ricky is semi-convinced that this is a Firefox bug
00:12 < ricky> Er, gecko
00:12 < spevack> yeah, it doesn't even have to be a table quaid. Just
various sections of the page where people can describe problems or
screenshots, etc.... i'm sure we'll work it out.
00:12 < ianweller> we could have a matrix that has anchor links to
different sections/pages
00:13 < quaid> +2
00:13 < spevack> ianweller: indeed. In cases like this, i advocate
the simplest tool that will allow us to solve the problem :)
00:13 < ianweller> i'm out, bbl
00:13 < ianweller> i'll read logs
00:13 < quaid> that would work nice
00:13 < quaid> ciao
00:13 ... nick!ianweller -> ianweller_afk
00:13 < spevack> ok, let's move on then, since this is pretty well resolved.
00:13 < spevack> ianweller_afk: thanks dude
00:14 < spevack> mizmo-out is not here, so we'll set aside spins.fp.o
for the moment.
00:14 < spevack> get-fedora is on the list... juank isn't here but
giarc_touch is... let me ask quickly, where do we currently stand on
mockups for the next iteration of get-fedora?
00:14 < spevack> i know there's something out there, but i have
forgotten where it is.
00:16 < spevack> while we wait on giarc_touch .... ricky, do you have
any Websites/Infrastructure topics you need to bring up tonight?
00:16 < spevack> am i all by myself?
00:16 < quaid> yes
00:16 * spevack screams into the ether
00:16 < ricky> I still haven't had much luck making the buildscript
friendlier :-(
00:16 < quaid> uh, I mean, no
00:17 < ricky> The few leads from before turned out to have problems
00:17 < spevack> ricky: what kind of problems?
00:17 < spevack> they didn't have enough programming chops to do stuff?
00:17 < ricky> The ${Markup(_(' '))} stuff - I still haven't been able
to shake it
00:18 < spevack> ricky: how does that relate to problems with the
leads we got from people who said they might be interested in helping?
00:18 < ricky> I don't completely remember what happened with those (I
was gone all last week)
00:19 < ricky> I think I've sent a few emails describing the problems
that we're facing, but no clear solutions yet
00:20 < fchiulli> ricky: what kind of help do you need?
00:20 < spevack> ricky: well, would you like me to follow up with
them, do you want to, or what? what is the best way, overall, that we
can help you out, either technically or from a recruiting point of
view?
00:21 < ricky> Mostly planning out how to handle translations well. I
don't think our current workflow is working as well as it could be.
00:21 < JonRob> i'm a bit clueless on this stuff
00:21 < JonRob> but does turbo gears make this kind of thing easier?
00:22 < JonRob> could we leverage toshio et al?
00:22 < ricky> I spoke with couf a while back (sent to the list with
subject "A conversation about website translation") that describes
some of the current problems.
00:23 < ricky> One question is whether po files works for website translations
00:24 < ricky> It's a pretty specific situation - unlike the
documentation team, we don't follow any specific schedule or anything.
00:25 < spevack> ricky: can glezos help here somehow?
00:25 < ricky> So what could be the costs/benefits to having some sort
of release cycle for the website?
00:25 < ricky> spevack: I haven't spoken to him recently - I'll
definitely see if he has any thoughts
00:26 < spevack> ricky: is it fair to say that we already have the
*basics* of a release cycle for the website, and perhaps just need to
beef up the process a bit?
00:27 < ricky> Maybe. I'm trying to think about all of this while
keeping my mind on the future of our website. Do we want to expand a
lot from what we have now in terms of content?
00:28 < quaid> specifically the problem with the markup is that it is
a pain to author in the original language
00:28 < quaid> since it makes PO files, that part is solved, right?
00:28 < ricky> Definitely - that's a specific technical problem that I
haven't been able to solve :-(
00:29 < quaid> I wonder if we are re-inventing a hamster wheel that
someone else (e.g. Drupal) has resolved ...
00:29 < quaid> s/Drupal/$CMS/
00:29 ... signoff!#fedora-websites -> tw2113("Never look down on
someone unless you're helping them up.")
00:31 < spevack> so what's the path forward here?
00:31 < spevack> i need something to write on the task page along with
a check in date
00:31 < spevack> :)
00:31 < spevack> 'cause that's how i roll
00:32 < JonRob> eh, we all love task lists - at least i do
00:33 < spevack> hello? ricky?
00:33 * spevack shakes the internet and smacks it like a malfunctioning toaster
00:33 < ricky> Heh, sorry
00:34 < ricky> Just thinking...
00:34 < ricky> quaid's CMS mention is sounding pretty tempting, honestly.
00:34 * quaid nods his head
00:35 < quaid> and if anyone says Plone ...
00:35 < quaid> I'll smack ya!
00:35 < ricky> Thank you :-P
00:35 < spevack> quaid: /nick mrT :)
00:35 * JonRob wonders hat happened to plone in the end
00:35 * JonRob ducks
00:36 < quaid> looks like there ht be some options written in TG
00:36 < spevack> so, should we make this topic #1 next week?
00:37 < spevack> if so, what do we need to do this week to have it be
useful conversation next week?
00:37 < ricky> I'm curious about what everybody's vision for the website is
00:37 < ricky> As in, how much will we expand from what we have now?
What should be on the wiki vs. on the website?
00:39 < spevack> static stuff that changes at release, with minor
updates mid-release == website
00:39 < spevack> everything else == wiki
00:39 < JonRob> do we want to pull docs etc into the same structure?
00:39 < ricky> This can help us decide how useful a CMS would be to us
and what to look for in a solution
00:40 < spevack> that's a vision for www.fedoraproject.org --
spins.fp.o is a totally separate creature.
00:40 < ricky> JonRob: I don't think docs and websites will end up
using the same tools
00:40 < spevack> but i assume ricky you are talking about www.fp.o
00:40 < ricky> That I am
00:40 ... signoff!#fedora-websites -> giarc_touch(Connection timed out)
00:41 < quaid> +1 to /*ANY*/ CMS for docs.fp.org
00:42 < ricky> But I mean content-wise - will it pretty much stay like
it is now?
00:42 < JonRob> ricky: there's a few small additions i'd like to make
at some point
00:42 < ricky> quaid: So we're not going to end up using publican to
just generate them all?
00:42 < JonRob> but i guess so
00:42 < spevack> two questions:
00:42 < quaid> ricky: publican only does part of the picture.
00:42 < spevack> 1) quaid, can't docs make a decision on CMS pretty
much "on its own"?
00:43 * quaid could see how to hack it with publican and cronjob, but
that is juts ore of the same
00:43 < spevack> 2) ricky, are you trying to get at whether www.fp.o
needs to run on top of a CMS or on top of custom build/publish
scripts?
00:43 < quaid> spevack: not without an army of code monkeys at my command
00:44 < ricky> spevack: That and what would the requirements be for a solution
00:44 < spevack> do we have a sitemap for www.fp.o similar to the one
mizmo-out made for spins.fp.o?
00:44 < spevack> if not, we need one.
00:44 < spevack> it will show us the present, and also the potential future
00:44 < spevack> and really help with a whole bunch of decisions that
need to be made
00:45 < spevack> agreed, or no? is that where this conversation
ultimately goes, in order to be able to make a smart decision
00:45 < spevack> ?
00:45 < JonRob> +1
00:46 < ricky> Yeah
00:46 < spevack> ok... /me makes a note of that.
00:46 < spevack> and jonrob will have it in the minutes too
00:46 * ricky notes the "Fedora Website" document in gobby
00:46 < quaid> yes, we need to see a massive site map that shows the
roles of sub-domains as well
00:47 < spevack> quaid: indeed
00:47 < quaid> so we can be clear wtf docs.fp.o is for, or realize
it's redundant or whatever
00:47 < quaid> btw, TG-based CMS doesn't seem in process; it was a
GSoC idea this year that no one is doing
00:48 < spevack> ok, this is a good task, and a very important one.
00:48 < quaid> if the TurboGears project says it's not really happening ...
00:48 * spevack was referring to the sitemap...
00:48 < quaid> http://www.pagodacms.org/
00:48 < quaid> right, sorry, jumping all over here
00:48 < spevack> ok, what else do we need to talk about tonight?
almost 1 AM for me and I am fading fast
00:49 < spevack> pagoda seems interesting
00:49 * quaid reads their trac instance
00:49 < ricky> Age: 8 months :-(
00:50 < spevack> what else, guys? any other business people want to bring up?
00:51 < JonRob> silence is golden!
00:52 < spevack> ok, then i declare this meeting over.
00:52 * JonRob hopes spevack logged again?
00:52 < ricky> I have a log if you need it
00:52 < spevack> I have some thinking/reorganizing/etc of our task
list to do this week. I think we need to cull the chaff, and focus on
planet and other L&F, spins, and www and that's it.
00:53 * spevack will try to get something together for folks to think
on this week
00:53 < spevack> JonRob: i'll send you the log.
00:53 < spevack> ===== MEETING OVER =====
00:53 < spevack> thanks for coming, everyone!
00:53 < JonRob> cool cheers
00:53 < spevack> really appreciate your time
00:53 < ricky> Thanks
Hey all,
I got a chance to sit down and work on the top nav bar and also on
making the home page look a little more like the one the design for
Fedora App DB but I could do with some help:
a) How can I get my local git repo into Fedora People so other people
can grab my version?
b) The colours don't look quite right to me. I've been using the
Fedora Logo colours...
c) There's some bits of the CSS that still need fixing, like the top
border on the content section covering the right background/border
image
There's a screenshot of what I've done so far at:
http://jonrob.fedorapeople.org/fp_home1.png
There's also a screenshot of an old take that no longer has code where
the top nav bar is a different colour and looks a little better to me:
http://jonrob.fedorapeople.org/fp_home.png
Best,
Jon
After all of that pain with the separate live branch, we're moving to
a slightly different workflow for the fedora-web git repo. Now,
anything pushed to ssh://git.fedorahosted.org/git/fedora-web.git will go
live within the hour. Testing should be done in your own repo (and you
are encouraged to make those public so that people can pull your changes
,etc.)
Thanks,
Ricky
Hello -
I'm getting this error no matter what username I type.
Any help would be great.
Thanks
Martin
-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
Hi,
I'm working on a web application called 'Fedora Applications'. I've
gotten to the point where I have a publicly available proof-of-concept
level web app available.
Fedora Applications is designed to be an easy way to find and install
applications for Fedora. The public instance is
at: http://publictest10.fedoraproject.org/amber
Feel free to poke around and get a feel for some of the functionality.
There's still a lot of warts and every ugly places. Any prettiness is
entirely due to help from Máirín. Mike Langlie is also going to be
helping me get it looking better.
One warning - this box isn't considered stable at all, and may go down
or implode at any time. If it doesn't work, try again in a few
minutes, and then send me an email.
The current plan is to style and brand it as a Fedora web application,
like Koji, Bodhi, package DB, et al. To that end, any help you guys can
give keeping Mike and I in line with the Fedora brand guidelines is
much appreciated.
The code running Fedora Applications is called 'Amber', and can be
found here:
https://fedorahosted.org/amber/
Along with a better product definition and other info. Patches
cheerfully accepted, of course. If anyone wants git commit access,
just apply to the 'gitamber' group in FAS.
Thanks,
-RN
--
Robin Norwood
Red Hat, Inc.
"The Sage does nothing, yet nothing remains undone."
-Lao Tzu, Te Tao Ching